Installing the WebSphere Application Server/Portal Server Agent on Each Application Server Instance

To Install the WebSphere Application Server/Portal Server Agent on Each Application Server Instance

1. Ensure that the WebSphere Application Server 6.1 or 7.0 Network Deployment is down.

2. On the machine running the Application Server instances, install the WebSphere Application Server/Portal Server agent onto each Application Server instance, as described in Installing the WebSphere Application Server/Portal Server Agent.

   Installation considerations are:

   • Use the agentadmin --custom-install option.

   • Several prompts specific to this installation are:

   Prompt	Description
   Instance Config Directory	Path to the configuration directory for the WebSphere Application Server instance. For example:  /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/ hostnameCell01/nodes/hostnameNode01/servers/server1
   Server Instance name	Name of the WebSphere Application Server instance. For example: server1
   Agent URL	Agent URL, including the deployment URIs. For example:  http://agenthost.example.com:9080/agentapp The agent application (agentapp.war) is a housekeeping application used by the agent for notifications and other functions such as cross domain single sign-on (CDSSO) support. For more information, see Deploying the Agent Application.

3. Copy the Application Server server1 server.xml file to overwrite its corresponding copy under the Deployment Manager's profile.

   For example, copy:

   /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/
   hostnameCell01/nodes/hostnameNode01/servers/server1/server.xml

   to overwrite:

   /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/
   hostnameCell01/nodes/hostnameNode01/servers/server1/server.xml

   Note: The above two server.xml files should be synchronized before installation, so this copy operation will not cause a mismatch. Otherwise you must find out the changes in server.xml (compared with original copy with a name such as server.xml-preAmAgent-timestamp) by the agent installer and merge the changes with its corresponding copy in the Deployment Manager's profile.

   If the Node Agent is on a remote host from the Deployment Manager, its server.xml file on the remote host should be copied or FTPed to the host of the Deployment Manager and overwrite its own corresponding copy in the Deployment Manager profile as above.

   Caution: Each Application Server instance has its own copy of server.xml in Deployment Manager, and overwriting a file mistakenly can cause the other server instances to malfunction.