Implications of Specific Deployment Scenarios for the Application Server 8.2/9.0/9.1 Agent

The following sections refer to specific deployment scenarios involving the Application Server 8.2/9.0/9.1 agent. These scenarios can affect how you respond to prompts during the installation process.

• Installing an Application Server 8.2/9.0/9.1 Agent on Multiple Application Server 8.2/9.0/9.1 Instances

• Installing an Application Server 8.2/9.0/9.1 Agent on a Different Server Domain

• Installing the Application Server 8.2/9.0/9.1 Agent on a Remote Application Server 8.2/9.0/9.1 Instance

• Installing the Application Server 8.2/9.0/9.1 Agent on the Access Manager Web Container

Installing an Application Server 8.2/9.0/9.1 Agent on Multiple Application Server 8.2/9.0/9.1 Instances

Once a J2EE agent is installed for a particular domain configuration directory, you can install the agent on more than one Application Server 8.2/9.0/9.1 instance associated with the same domain by running the agentadmin --install command. Once prompted to enter the appropriate server instance name, enter the domain configuration directory and unique instance name that will enable the agent to distinguish the first instance from consecutive instances.

Installing an Application Server 8.2/9.0/9.1 Agent on a Different Server Domain

Once a J2EE agent is installed for a specific domain, the J2EE agent binaries cannot be used on that same Application Server installation for a different Application Server 8.2/9.0/9.1 domain. If you attempt to use previously installed J2EE agent binaries on the same Application Server installation, but on a different domain, the installation fails.

J2EE agents associate a specific set of agent binaries with a particular domain for Application Server 8.2/9.0/9.1. If you want to install a J2EE agent on a different domain, unzip a new set of bits and copy them to a separate location before running the agentadmin --install command for the second domain.

Installing the Application Server 8.2/9.0/9.1 Agent on a Remote Application Server 8.2/9.0/9.1 Instance

The agent installation for each remote Sun Java System Application Sever 9/9.1 instance requires one installation run on the remote host and one configuration run for the remote agent on the DAS host. The following installation steps are based on the assumption that the remote instance has been set up correctly.

For information about installing the agent, see Installing the Application Server 8.2/9.0/9.1 Agent.

To Install the Application Server 8.2/9.0/9.1 Agent on a Remote Application Server 8.2/9.0/9.1 Instance

Before You Begin

Shutdown both the DAS domain and remote server instance before installing the Application Server 8.2/9.0/9.1 agent.

1. Install the Application Server 8.2/9.0/9.1 agent on the remote server instance host.

   During installation, answer the following questions as indicated:

   Enable this field only when the agent is being installed on a remote server 
   instance host.
   [ ? : Help, < : Back, ! : Exit ]
   Is Domain administration server host remote ? [false]: true

   Enter true only if agent is being installed on a remote instance from the
   Domain Administration server host.
   [ ? : Help, < : Back, ! : Exit ]
   Is the agent being installed on the DAS host for a remote instance ? [false]: false

2. Install the Application Server 8.2/9.0/9.1 agent on the DAS host for the same remote server instance.

   During installation, answer the following questions as indicated:

   Enable this field only when the agent is being installed on a remote server 
   instance host.
   [ ? : Help, < : Back, ! : Exit ]
   Is Domain administration server host remote ? [false]: false

   Enter true only if agent is being installed on a remote instance from the
   Domain Administration server host.
   [ ? : Help, < : Back, ! : Exit ]
   Is the agent being installed on the DAS host for a remote instance ? [false]: true

   The following two questions are asked only when the answer to the previous question is true:

   Enter the value of the agent instance name provided by the agent installation 
   on the remote instance.
   [ ? : Help, < : Back, ! : Exit ]
   Agent instance name []: Agent_001

   Note: Agent_001 is the agent instance name generated in Step 1 for the remote server instance. The agent installation generates an agent instance name, which is displayed at the end of installation and is available in the install log. The instance name must be valid.

   Enter the value of the agent install directory on the remote instance host.
   [ ? : Help, < : Back, ! : Exit ]
   Agent install directory on remote instance host
   [/opt/j2ee_agents/am_as81_agent]:

   Enter the directory where the agent has been installed on the remote server instance host. This is the agent binary directory on the remote server instance host instead of the agent binary directory on DAS host.

3. Edit the following files to allow the agent to work on the remote server instance:

   1. On the DAS host, edit the DAS domain's domain.xml file.

      For example: /var/opt/SUNWappserver/domains/domain1/config/domain.xml

      In the domain.xml file, find and change the following text:

      <jvm-options>
      -Djava.util.logging.config.file=agent-deploy-directory-on-DAS-host
      /j2ee_agents/appserver_v9_agent/config/AMAgentLogConfig.properties
      </jvm-options>

      to

      <jvm-options>
       -Djava.util.logging.config.file=
      agent-deploy-directory-on-remote-server-instance-host/j2ee_agents/appserver_v9_agent
      /config/AMAgentLogConfig.properties
      </jvm-options>

   2. On the DAS host, edit the DAS domain's server.policy file.

      For example: /var/opt/SUNWappserver/domains/domain1/config/server.policy

      In the server.policy file, find and change the following text:

      grant codeBase "file:agent-deploy-directory-on-DAS-host
      /j2ee_agents/appserver_v9_agent/lib/*" {
             permission java.security.AllPermission;
      };

      to

      grant codeBase "file:agent-deploy-directory-on-remote-server-instance-host
      /j2ee_agents/appserver_v9_agent/lib/*" {
             permission java.security.AllPermission;
      };

4. Start the DAS domain and remote server instance.

Installing the Application Server 8.2/9.0/9.1 Agent on the Access Manager Web Container

The Application Server 8.2/9.0/9.1 agent and Access Manager should not be installed on the same Application Server 8.2/9.0/9.1 instance. Therefore, when you install the agent, always choose false (the default) for the following question:

Enter true if the Agent is being installed on the same instance of Application
Server on which Access Manager is deployed. Enter false if that is not the
case.
[ ? : Help, < : Back, ! : Exit ]
Are the Agent and Access Manager installed on the same instance of
Application Server ? [false]: