Share via

3.3.3 Initialization

  • Article

The MSDTC Connection Manager: OleTx Transports Protocol partner when initiating the IXnRemote Server role, MUST perform the following actions.

  • Initialize the Server TCP Port data element by retrieving it directly from the registry, as defined in [MS-CMOM] section 3.3.1.2.1.<12>

  • Initialize the Service Network Protocols data element by retrieving it directly from the registry, as defined in [MS-CMOM] section 3.3.1.2.3.

  • For each supported RPC protocol on the Service Network Protocols data element:

    • If the supported RPC protocol is TCP/IP and the Server TCP Port data element is supported, then register for an RPC dynamic endpoint using the port number defined on the Server TCP Port.<13>

    • If the supported RPC protocol is TCP/IP and the Server TCP Port local data element is not supported, then register for an RPC dynamic endpoint using the port number automatically assigned by the endpoint mapper.

    • If the supported RPC protocol is not TCP/IP, then register for an RPC dynamic endpoint.

    • If registration of the dynamic endpoint succeeds, then register the interface with the RPC endpoint mapper. During this registration, the local contact identifier (CID) of the interface is specified as the object identifier. See [C706].

    • If registration of the dynamic endpoint does not succeed, then the MSDTC Connection Manager: OleTx Transports Protocol partner MUST NOT be initialized.

  • If an "ncalrpc" RPC protocol endpoint was not registered, then register a dynamic endpoint using this protocol. This endpoint SHOULD be registered even when the "ncalrpc" RPC protocol sequence is not included as an entry in the Service Network Protocols data element.

  • Initialize the Server Security Settings data element by retrieving the RPC Security Provider data element value from an implementation-specific source.<14>

  • Start the RPC server, using the Server Security Settings, to listen for RPC calls.