3.3.4 Message Processing Events and Sequencing Rules
This DCOM interface inherits the IUnknown interface. The method opnum field values start with 3; opnum values 0 through 2 represent the IUnknown_QueryInterface, IUnknown_AddRef, and IUnknown_Release methods, respectively, as specified in [MS-DCOM].
Methods with opnum field values 3 through 33 are defined in section 3.1.4, and field value 40 is defined in section 3.5.4.
The IMSAdminBase2W RPC interface extends the IMSAdminBaseW interface, adding functionality for metabase importing and exporting, history management, and secure data encryption on backup. The IMSAdminBase2W protocol does not maintain client state information.
An RPC sequence is a client/server session that includes a security context phase and requests to call remote procedures. For connection-oriented RPC, the session also includes a binding phase. The RPC client supplies the necessary security information and for a connection-oriented RPC, it also supplies binding information such as interface name and server endpoint. The sequence of subsequent RPC calls in the session is implementation-specific.
Methods in RPC Opnum Order
|
Method |
Description |
|---|---|
|
Backs up the metabase to a specified location, using a supplied password to encrypt all secure data. Opnum: 34 |
|
|
Restores the metabase from a backup, using a supplied password to decrypt the secure data. Opnum: 35 |
|
|
Exports the metabase from a supplied location to a specific file name. Opnum: 36 |
|
|
Imports a previously exported metabase into an existing one. Opnum: 37 |
|
|
Restores a metabase history entry for a specific history version. Opnum: 38 |
|
|
Returns an enumerated history entry with a supplied index. Opnum: 39 |
When a remote call is made, the UUID and version number of the interface are specified in the abstract_syntax and abstract_syntax_vers fields of the incoming RPC_BIND packet, as specified in [MS-RPCE].