Deploying the first agent and testing a response file that includes connector configurations comprises most of the work in agent deployment. By leveraging that work, you can roll out the remaining agents with much less effort.
Preparing additional hosts and installing the agents requires that you repeat some of the procedures you performed when installing the first two agents. Consider these tasks when deploying each remaining agent that is based on the first agent.
This step is not needed if you elected to use common elements where possible.
When you install an agent or create a response file on an AIX system, you specify values for the five parameters listed on the following table. If you copy this file for reuse on other systems, you can edit the original values as needed, or if appropriate, use the original values.
To edit the response file
Field |
Description |
---|---|
ELM_SERVER |
The Host name or IP address of the CA Enterprise Log Manager server. Enter the host name if the CA Enterprise Log Manager server gets its IP address dynamically through DHCP. |
INSTALL_DIR |
The full path to the agent root directory. Default: /opt/CA/ELMAgent. |
AGENT_AUTHKEY |
The Agent Authentication Key. Select the Agent Authentication Key button in the Agent Explorer under Administration to view or set this key. Note: If the key value you enter during installation does not match the entry in the UI, the agent service will not start after installation. |
AGENT_USER |
The user name for running the CA Enterprise Log Manager agent. We recommend that you create a lower-privilege user account to run the agent before starting the agent installation. Default: root |
FIPSMODE |
Indicates if the Agent runs in FIPS mode. Default: OFF |
DEFAULT_CONNECTORS |
The exported file containing connector configurations, including the path. Leave this field blank if the Connectors.xml file is not available. Default: <blank> |
Copyright © 2011 CA. All rights reserved. | Email CA Technologies about this topic |