Skip Navigation Links | |
Exit Print View | |
Remote Administration Daemon Developer Guide Oracle Solaris 11.1 Information Library |
Each operation that a client can perform against a rad server has its own request and response payloads. To facilitate processing without needing to fully decode the payload, these payloads are communicated as variable-lengthed opaque data in the REQUEST and RESPONSE.
For consistency and flexibility, all ADR data referenced by these payloads is communicated as OPTIONAL-DATA, which in turn is wrapped as opaque data.
Table A-39 PAYLOAD-DATA
|
INVOKE makes a method call against a rad object, identified by its object ID.
Table A-40 INVOKE-REQUEST
|
Table A-41 INVOKE-RESPONSE
|
INVOKE can fail for the following reasons:
The method call was made but failed for an object-specific reason.
objectid is not a known object ID or the object does not have the method mname.
The wrong number of arguments were provided, or a non-nullable argument was missing.
The server had insufficient resources to complete the operation.
An unexpected internal error occurred.
GETATTR reads an attribute of a rad object identified by its object ID.
Table A-42 GETATTR-REQUEST
|
Table A-43 GETATTR-RESPONSE
|
GETATTR can fail for the following reasons:
An attempt to read the attribute was made, but failed for an object-specific reason.
objectid is not a known object ID or the object does not have the attribute aname.
aname refers to a write-only attribute.
The server had insufficient resources to complete the operation.
An unexpected internal error occurred.
SETATTR reads an attribute of a rad object identified by its object ID. The response payload for a SETATTR request is empty.
Table A-44 SETATTR-REQUEST
|
SETATTR can fail for the following reasons:
An attempt to write the attribute was made, but failed for an object-specific reason.
objectid is not a known object ID or the object does not have the attribute aname.
aname has a non-nullable value and value was NULL.
aname refers to a read-only attribute.
The server had insufficient resources to complete the operation.
An unexpected internal error occurred.
LOOKUP attempts to find the named object in the server's namespace, returning the object and interface IDs of the object if it exists. Because an object is not usable until its interface has been defined, the client may request the interface definition be provided as part of the LOOKUP response. For the same reason, the server may unilaterally decide to provide the interface definition if it believes the client has not seen it yet.
Table A-45 LOOKUP-REQUEST
|
Table A-46 LOOKUP-RESPONSE
|
LOOKUP can fail for the following reasons:
name does not exist.
The server had insufficient resources to complete the operation.
An unexpected internal error occurred.
DEFINE requests a definition of the specified interface ID.
Table A-47 DEFINE-REQUEST
|
Table A-48 DEFINE-RESPONSE
|
DEFINE can fail for the following reasons:
interfaceid isn't a known interface ID.
The server had insufficient resources to complete the operation.
An unexpected internal error occurred.
LIST requests an enumeration of all objects present in the server that match the specified object name pattern. The empty string matches all server objects.
Table A-49 LIST-REQUEST
|
Table A-50 LIST-RESPONSE
|
LIST can fail for the following reasons:
The server had insufficient resources to complete the operation.
An unexpected internal error occurred.
.
SUB and UNSUB subscribe and unsubscribe, respectively, to the named event of the specified object. The response payload for a successful SUB or UNSUB is empty.
Note that it is possible to receive an EVENT that has been unsubscribed even after a successful UNSUB operation.
Table A-51 SUB-REQUEST
|
Table A-52 UNSUB-RESPONSE
|
SUB can fail for the following reasons:
objectid is not a known object ID or the object does not have the event event.
The client is already subscribed to event.
The server had insufficient resources to complete the operation.
An unexpected internal error occurred.
UNSUB can fail for the following reasons:
objectid is not a known object ID the object does not have the event event, or the client isn't subscribed to event.
The server had insufficient resources to complete the operation.
An unexpected internal error occurred.