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

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.

1. 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.

2. 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.

   ---