Export (0) Print
Expand All

3.2.4.3 Cluster Registry

In order to access the cluster registry, a client MUST establish an RPC interface connection to an active node, as specified in section 3.2.3. Operations on the cluster registry begin with the client calling ApiGetRootKey (section 3.1.4.1.29 for protocol version 2, or 3.1.4.2.29 for protocol version 3) to open the cluster registry root key. After this key is opened, an RPC context handle is associated with this opened key, as specified in [MS-RPCE], and this handle is returned to the client. The client MAY then perform operations on this key, such as:

  • Open the key: ApiOpenKey (section 3.1.4.1.31 for protocol version 2, or 3.1.4.2.31 for protocol version 3)

  • Create subkeys: ApiCreateKey (section 3.1.4.1.30 for protocol version 2, or 3.1.4.2.30 for protocol version 3)

  • Read values associated with this key: ApiQueryValue (section 3.1.4.1.35 for protocol version 2, or 3.1.4.2.35 for protocol version 3)

  • Set values associated with this key: ApiSetValue (section 3.1.4.1.33 for protocol version 2, or 3.1.4.2.33 for protocol version 3)

  • Delete subkeys: ApiDeleteKey (section 3.1.4.1.36 for protocol version 2, or 3.1.4.2.36 for protocol version 3)

After finishing operations, the client MAY call the ApiCloseKey (section 3.1.4.1.38 for protocol version 2, or 3.1.4.2.38 for protocol version 3) method for each opened key.

When enumerating keys or values, a client MAY first invoke ApiEnumKey (section 3.1.4.1.32 for protocol version 2, or 3.1.4.2.32 for protocol version 3) or ApiEnumValue (section 3.1.4.1.37 for protocol version 2, or 3.1.4.2.37 for protocol version 3) with the index set to 0. Then the client MAY continue calling ApiEnumKey or ApiEnumValue, incrementing the index on each call, until 0x00000103 (ERROR_NO_MORE_ITEMS) is returned.

 
Show:
© 2014 Microsoft