Connectors and Agents

idmgr connectors run as part of the Provisioning Server and communicate with the systems managed in your environment. A connector acts as a gateway to a native endpoint type system technology. For example, machines running Active Directory Services (ADS) can be managed only if the ADS connector is installed on a connector server with which the Provisioning Server can communicate. Connectors manage the objects that reside on the systems. Managed objects include accounts, groups, and optionally, endpoint type specific objects.
cim1265
connectors run as part of the Provisioning Server and communicate with the systems managed in your environment. A connector acts as a gateway to a native endpoint type system technology. For example, machines running Active Directory Services (ADS) can be managed only if the ADS connector is installed on a connector server with which the Provisioning Server can communicate. Connectors manage the objects that reside on the systems. Managed objects include accounts, groups, and optionally, endpoint type specific objects.
Some connectors require agents on the systems they manage to complete the communication cycle. The two categories of agents are as follows:
  • Remote agents are installed on the managed endpoint systems.
  • Environment agents are installed on systems, such as CA ACF2, CA Top Secret, and RACF.
The following C++ connectors work on UNIX and Windows:
  • UNIX (ETC, NIS)
  • Access Control (ACC)
    Note:
    The UNIX ACC connector can manage only UNIX ACC endpoints. The Windows ACC connector is required to manage Windows ACC endpoints but can also manage UNIX ACC endpoints.
  • CA ACF2
  • RACF
  • CA Top Secret
Other C++ connectors can be accessed from a Provisioning Server installed on Solaris, by relying on the Connector Server Framework (CSF). The CSF allows a Provisioning Server on Solaris to communicate with connectors running on Windows.
The CSF must run on Windows to use these connectors.