Previous Topic: Known IssuesNext Topic: Migration Notes


Agent Registration

The Client Automation agent registers with the MDB by providing the following information:

With Agent Bridge, the host UUID is provided by the legacy agent, and the legacy agent is registered to the Client Automation system using the Agent Bridge. The agent registration method used by Client Automation and Agent Bridge maps the legacy information to that in Client Automation. For example, an asset management 8-byte file ID is mapped to a Client Automation formatted, 32-byte alphanumeric host UUID. The host UUID that is generated for a legacy agent is common to both asset management and asset management agents, and is stored in the common usage file.

If a legacy agent does not provide a unique host UUID and the UUID generator is not enabled, it is not registered by the Agent Bridge, and the agent is treated as an invalid agent.

If the UUID generator is enabled, the correct procedures for registering asset management and software delivery legacy agents are as follows:

To register legacy agents, some of which may not report their own UUIDs

In general, the majority of Unicenter Asset Management 4.0 agents and Unicenter Software Delivery 4.0 agents report host UUIDs when registering with the server.

Asset Management Agents

The registration of all legacy Unicenter Asset Management 4.0 agents is supported by Agent Bridge in Client Automation.

Mobile PDA agents require the application of patch T434066 before they can work with Agent Bridge. This patch can also be obtained from CA Online Support at http://ca.com/support.

Software Delivery Agents

The registration of all legacy Unicenter Software Delivery 4.0 agents is supported by the agent registration method used by Client Automation and Agent Bridge.