Configuring BEA WebLogic Server/Portal 9.2 Instance With Agent Classpath and Agent Java Options (Sun Java System Access Manager Policy Agent 2.2 Guide for BEA WebLogic Server/Portal 9.2)

Sun Java System Access Manager Policy Agent 2.2 Guide for BEA WebLogic Server/Portal 9.2

Configuring BEA WebLogic Server/Portal 9.2 Instance With Agent Classpath and Agent Java Options

This section applies to both BEA WebLogic Server 9.2 and BEA WebLogic Portal 9.2 and provides a lot of background information and explanation. However, if you are interested only in the key information required to configure the agent classpath and agent Java options, see Configuring BEA WebLogic Portal 9.2 Instance With Agent Classpath and Agent Java Options.

During agent installation, the installer creates an environment variable script in domain-directory named as follows:

UNIX Platforms: setAgentEnv_server-instance.sh
Windows Platforms: setAgentEnv_server-instance.cmd

domain-directory

a place holder that represents the domain name associated with the BEA WebLogic Server/Portal 9.2 instance. The following is the default full path name of domain-directory:

/usr/local/bea/user_projects/domains/mydomain

server-instance

a place holder that represents the BEA WebLogic Server/Portal 9.2 instance name entered during installation. For example Server1 or Server2.

The agent environment variable script, setAgentEnv_server-instance.sh, is an environment script which is called up during the server's start up sequence.

This agent environment variable script is associated with Agent for BEA WebLogic Server/Portal 9.2 and is used to set up the environment for the agent. This script is called up during the server's start up sequence and sets the classpath and Java options for the agent. The following instructions describe how to configure the BEA WebLogic Server/Portal 9.2 start up script to call the agent environment variable script.

To Configure BEA WebLogic Server/Portal 9.2 Instance With Agent Classpath and Agent Java Options

Note –

This step is required. Agent for BEA WebLogic Server/Portal 9.2 will not work if the agent startup script is added incorrectly to the BEA WebLogic Server/Portal 9.2 instance start up script. If the agent startup script does not get invoked properly from the BEA WebLogic Server/Portal 9.2 start up script, BEA WebLogic Server/Portal 9.2 will not function appropriately after the Agent Authenticator is set.

To the BEA WebLogic Server/Portal 9.2 instance start up script, add the path of the agent environment variable script.

The substeps that follow provide the details of adding the agent-environment-variable-script path to the BEA WebLogic Server/Portal 9.2 start up script.

Note –
Throughout this guide scripting files apply to both UNIX platforms and Windows platforms even when the script for Windows platforms is not expressly mentioned. The difference is that scripts for UNIX platforms have the .sh extension while scripts for Windows platforms have the .cmd extension.
1. Using the text editor of your choice, access the applicable BEA WebLogic Server/Portal 9.2 instance start up script.
  
  The full path to the start up script required for this configuration is as follows:.
  
  UNIX Platforms
  
  domain-directory/bin/startWebLogic.sh
  
  Windows Platforms
  
  domain-directory\bin\startWebLogic.cmd
  
  where domain-directory is a place holder that represents the domain name associated with the BEA WebLogic Server/Portal 9.2 instance. Be certain that you provide the full path name of domain-directory.
  
  Caution –
  Ensure that you access the startWebLogic file in the bin directory. Do not access the startWebLogic file available directly in domain-directory.
2. After the line, . ${DOMAIN_HOME}/bin/setDomainEnv.sh $*, add the path to the agent environment variable script.
  
  The following examples, for both UNIX platforms and Windows platforms, demonstrate the process of adding the agent-environment-variable-script path by specifying the fully qualified path. See the important explanation that follows these examples about the variables ${SERVER_NAME} and %SERVER_NAME%.
  - UNIX Platforms
    . domain-directory/setAgentEnv_${SERVER_NAME}.sh
    For this scenario, the following is a conceivable line if the domain directory is named mydomain:
    . /usr/local/bea/user_projects/domains/mydomain/setAgentEnv_${SERVER_NAME}.sh
    Therefore, in this scenario, the start up script would then, amongst other lines, contain these two lines as shown:
    . ${DOMAIN_HOME}/bin/setDomainEnv.sh $* . /usr/local/bea/user_projects/domains/mydomain/setAgentEnv_${SERVER_NAME}.sh
  - Windows Platforms
    call "domain-directory\setAgentEnv_%SERVER_NAME%.cmd"
    For this scenario, the following is a conceivable line if the domain directory is named mydomain:
    call "C:\bea\user_projects\domains\mydomain\setAgentEnv_%SERVER_NAME%.cmd"
    Therefore, in this scenario, the start up script would then contain, amongst other lines, these two lines as shown:
```
call "%DOMAIN_HOME%\bin\setDomainEnv.cmd" %*
call "C:\bea\user_projects\domains\mydomain\setAgentEnv_%SERVER_NAME%.cmd"
```
  ${SERVER_NAME} or %SERVER_NAME%
  
  a variable for the BEA WebLogic Server/Portal 9.2 instance that is dynamically replaced. Do not replace or modify this variable. Therefore, ensure that the variable is entered and remains character for character as ${SERVER_NAME} for UNIX platforms and %SERVER_NAME% for Windows platforms.

Restart the BEA WebLogic Server/Portal 9.2 instance.

Caution –
Restarting the BEA WebLogic Server/Portal 9.2 instance at this point is necessary. Otherwise, upcoming tasks will fail.