3.1.4 Message Processing Events and Sequencing Rules
This DCOM interface inherits the IUnknown interface. 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 34 through 39 are defined in section 3.3.4, and field value 40 is defined in section 3.5.4.
This protocol MUST indicate to the RPC runtime that it is to perform a strict Network Data Representation (NDR) data consistency check at target level 5.0, as specified in [MS-RPCE] section 3.
Methods in RPC Opnum Order
Method |
Description |
---|---|
Creates a node and adds it to the metabase as a subnode of an existing node at the specified path. Opnum: 3 |
|
Deletes a node and all its data from the metabase. All of the node's subnodes are recursively deleted. Opnum: 4 |
|
Deletes all subnodes of the specified node and any data they contain. It also recursively deletes all nodes below the subnodes. Opnum: 5 |
|
Enumerates the subnodes of the specified node. Opnum: 6 |
|
Copies or moves a node, including its subnodes and data, to a specified destination. The copied or moved node becomes a subnode of the destination node. Opnum: 7 |
|
Renames a node in the metabase. Opnum: 8 |
|
Sets a data item for a particular node in the metabase. Opnum: 9 |
|
Returns a data entry from a particular node in the metabase. Opnum: 10 |
|
Deletes specific data entries from a node in the metabase. Opnum: 11 |
|
Enumerates the data entries of a node in the metabase. Opnum: 12 |
|
Returns all data associated with a node in the metabase, including all values that the node inherits. Opnum: 13 |
|
Deletes all or a subset of local data associated with a particular node. Opnum: 14 |
|
Copies or moves data between nodes. Opnum: 15 |
|
Returns the paths of all nodes in the subtree relative to a specified starting node that contains the supplied identifier. Opnum: 16 |
|
Opens a node for read access, write access, or both. The returned handle can be used by several of the other methods in IMSAdminBaseW. Opnum: 17 |
|
Closes a handle to a node. Opnum: 18 |
|
Changes permissions on an open handle. Opnum: 19 |
|
Explicitly saves the metabase data to disk. Opnum: 20 |
|
Returns information associated with the specified metabase handle. Opnum: 21 |
|
Returns the number of changes made to data since the metabase was created. Opnum: 22 |
|
Returns all the data set numbers associated with a node in the metabase. Opnum: 23 |
|
Sets the last change time associated with a node in the metabase. Opnum: 24 |
|
Returns the last change time associated with a node in the metabase. Opnum: 25 |
|
Receives a pair of encrypted client nodes and returns server encryption and session keys. Opnum: 26 |
|
Receives the encrypted client session and hash keys in response to R_KeyExchangePhase1 and returns the encrypted server hash keys. Opnum: 27 |
|
Backs up the metabase to a specified location. Opnum: 28 |
|
Restores the metabase from a backup. Opnum: 29 |
|
Enumerates the metabase backups in a specified backup location, or in all backup locations. Opnum: 30 |
|
Deletes a metabase backup from a backup location. Opnum: 31 |
|
Unmarshals a reference to the IMSAdminBaseW interface. Opnum: 32 |
|
Returns the GUID for the IIS instance that is running. Opnum: 33 |
Structures
The Message Processing Events and Sequencing Rules interface defines the following structures.
Structure |
Description |
---|---|
Defines information about a handle to a metabase entry. |
|
Defines information about a metabase entry. |
|
Defines an analogous structure to METADATA_RECORD but is used only to return data from a call to the R_GetAllData method. |
|
Defines a block of opaque data, possibly encrypted, for RPC marshaling between IIS and a client. |