administrative agent

The administrator role is required for you to register or deregister a base node with the administrative agent.

The new administrative agent topology enables you to manage multiple base profiles efficiently on a single computing system.

Admin agent: Create an administrative agent profile that you will run in the DMZ and register the secure proxy with an administrative agent.

The administrative agent and its registered nodes join a XCF group that notifies group members when other members join or leave the group.

For each node registered with the administrative agent, the agent creates an administrative subsystem for the node.

When a node is deregistered from the administrative agent, it retains all configuration changes.

Administrative agent and flexible management topologies.

This enables the administrator to continue to use the base node without the ability to manage it with the administrative agent.

For each base node registered with the administrative agent, a new managed node configuration object is created.

After a base node is removed from a deployment manager federation, it can be registered with an administrative agent.

Register the base application server profile(s) with the administrative agent.

Each managed node has a name, unique within the administrative agent.

Conversely, after it is deregistered from an administrative agent, it can be federated with a deployment manager.

Create administrative agent and application server profiles using the Profile Management Tool.

The polling cycle time is configurable at the administrative agent or the deployment manager.

Job manager and administrative agent security