To Prepare to Install Agent for BEA WebLogic Server 9.0/9.1

Perform the following pre-installation tasks:

1. Ensure that the Policy Agent 2.2 for BEA WebLogic Server 9.0/9.1 is supported on the desired platform as listed in Supported Platforms and Compatibility of Agent for BEA WebLogic Server 9.0/9.1.

2. Install BEA WebLogic Server 9.0/9.1 if not already installed.

   For more information about BEA WebLogic Server 9.0/9.1, see the product documentation available at the following web site: http://www.bea.com/.

3. Create a server domain.

   Using the configuration or domain wizard appropriate for your server version and operating system, create a new stand-alone server domain. Typically, the configuration wizard launch script or program is located in the respective directory as follows:

   UNIX–based systems (including Linux systems)

   bea-home/weblogic9/common/bin/config.sh

   Windows systems

   bea-home\weblogic9\common\bin\config.cmd

   where bea-home represents the directory in which BEA WebLogic Server 9.0/9.1 was installed.

4. Shut down the BEA WebLogic Server 9.0/9.1 instance that will be protected by the agent.

5. Create a valid agent profile in Access Manager Console if one has not already been created.

   For information on how to create an agent profile, see Creating a J2EE Agent Profile.

   To avoid a misconfiguration of the agent, ensure that you know the exact ID and password used to create the agent profile. You must enter the agent profile password correctly in the next step and you must enter the agent profile ID correctly when installing the agent.

6. Create a text file and add the agent profile password to that file.

   Ensure that this file is located in a secure directory of your choice. You will refer to this file during the agent installation process.

   With the agent profile password in this file, stored in a secure location, you do not need to enter sensitive information in the command line. A valid password file can have only one line that contains the agent profile password.

   You must decide what to do with this password file after the installation process is complete. You might choose to remove the file or provide restricted permissions to it. However, certain deployment-related tasks, such as installing multiple instances, require a password file. If you do remove the password file, create a new one if a future situation requires it.