1.4 Relationship to Other Protocols

  • Article

COMA is built on top of DCOM, as described in [MS-DCOM].

The COM+ Tracker Service Protocol is another protocol that provides functionality for obtaining run-time information about instance containers (for more information, see [MS-COMT]). The COM+ Tracker Service Protocol makes obsolete that functionality provided by this protocol by enabling clients to obtain a richer set of information and by providing a push model.

The COM+ Event System Protocol is another protocol that provides functionality for configuring event classes and subscriptions (for more information, see [MS-COMEV]). The COM+ Event System Protocol makes obsolete that functionality provided by this protocol by enabling configuration for additional types of subscriptions.

COMA can be used to configure COM+ on a server. COMA partitions have a natural mapping to COM+ partitions, and many configuration properties of objects in the COMA catalog are designed to support configuration of COM+ behavior that is implementation-specific as described in [MS-COM].

COMA can be used to configure the COM+ Queued Components Protocol on a server (for more information, see [MC-COMQC]). Several configuration properties of objects in the COMA catalog are designed to support enabling the COM+ Queued Components Protocol as a transport for communication between components.

COMA can be used to configure system services (also known as daemons) for conglomerations. The Service Control Manager Remote Protocol is another protocol for configuring system services (for more information, see [MS-SCMR]). Neither protocol makes the other obsolete because each enables configuration that is not available in the other.

COMA provides limited management of CIFS file shares (for details, see [MS-CIFS]) for use in replication scenarios. COMA replication functionality is intended to be used alongside CIFS to copy conglomerations between COMA servers in these replication scenarios. Other COMA functionality requiring remote file operations might use CIFS, but this is not required by the protocol.