Deployment Example 1: Access Manager 7.1 Load Balancing, Distributed Authentication UI, and Session Failover

ProcedureTo Install the J2EE Policy Agent 2 on Application Server 2

Before You Begin

You must stop both the WebLogic Server 2 managed instance and the WebLogic Server 2 administration server before beginning the installation process.

  1. As a root user, log into the ProtectedResource–2 host machine.

  2. Stop the WebLogic Server 2 administration server and the WebLogic Server 2 managed instance.


    # cd /usr/local/bea/user_projects/domains/ProtectedResource-2/bin
    # ./stopManagedWebLogic.sh ApplicationServer-2 t3://localhost:7001
    # ./stopWebLogic.sh
    
  3. Ensure that your system is properly patched.

    Read the appropriate policy agent Release Notes for your web container to determine the latest patches you might need to install before beginning installation. In this case, no patch is required.


    Note –

    You can search for patches directly at http://sunsolve.sun.com. Navigate to the PatchFinder page, enter the patch number, click Find Patch, and download the appropriate patch.


  4. Change into the J2EEPA2 directory.


    # cd /export/J2EEPA2
    
  5. Download the J2EE policy agent bits for WebLogic Server from http://www.sun.com/download/index.jsp.


    # ls -al
    
    total 8692
    drwxr-xr-x   2 root     root         512 Sep 13 13:19 .
    drwxr-xr-x   5 root     sys          512 Aug 13 17:08 ..
    -rw-r--r--   1 root     root     4433920 Sep 13 13:19 SJS_Weblogic_92_agent_2.2.tar
    
  6. Unpack the J2EE policy agent bits.


    # /usr/sfw/bin/gtar -xvf /export/J2EEPA2/SJS_Weblogic_92_agent_2.2.tar
    

    Tip –

    Use the gtar command and not the tar command.


  7. Run the J2EE policy agent installer.


    # cd /export/J2EEPA2/j2ee_agents/am_wl92_agent/bin
    # ./agentadmin --install
    
  8. When prompted, provide the following information.


    Please read the following License Agreement carefully:

    Press Enter to continue. Continue to press Enter until you reach the end of the License Agreement. 


    Enter startup script location.

    Enter . 


    /usr/local/bea/user_projects/domains/
    ProtectedResource-2/bin/
    startwebLogic.sh
    

    Enter the WebLogic Server instance name: [myserver]

    Enter ApplicationServer-2.


    Access Manager Services Host:

    Enter LoadBalancer-3.example.com.


    Access Manager Services port: [80]

    Enter 7070.


    Access Manager Services Protocol: [http]

    Accept the default value. 


    Access Manager Services Deployment URI: [/amserver]

    Accept the default value. 


    Enter the Agent Host name:

    ProtectedResource-2.example.com


    Enter the WebLogic home directory: 
    [/usr/local/bea/weblogic92]

    Accept the default value. 


    Enter true if the agent is being 
    installed on a Portal domain:

    Accept false, the default value.


    Enter the port number for 
    Application Server instance [80]:

    Enter 1081.


    Enter the Preferred Protocol for 
    Application instance [http]:

    Accept the default value. 


    Enter the Deployment URI for 
    the Agent Application [/agentapp]

    Accept the default value. 


    Enter the Encryption Key 
    [j8C9QteM1HtC2OhTTDh/f1LhT38wfX1F]:

    Accept the default value. 


    Enter the Agent Profile Name:

    j2eeagent-2


    Enter the path to the password file:

    Enter /export/J2EEPA2/agent.pwd.


    Are the Agent and Access Manager installed on 
    the same instance of Application Server? [false]:

    Accept the default value. 


    Verify your settings and decide from 
    the choices below:
    1. Continue with Installation
    2. Back to the last interaction
    3. Start Over
    4. Exit
    Please make your selection [1]:

    Accept the default value. 

    The installer runs and, when finished, creates a new file in the bin directory called setAgentEnv_ApplicationServer-2.sh.

  9. Modify the startup script setDomainEnv.sh to reference setAgentEnv_ApplicationServer-2.sh.


    Tip –

    Backup setDomainEnv.sh before you modify it.


    1. Change to the bin directory.


      # cd /usr/local/bea/user_projects/domains/ProtectedResource-2/bin
      
    2. Insert the following line at the end of setDomainEnv.sh.


      . /usr/local/bea/user_projects/domains/ProtectedResource-2/
      bin/setAgentEnv_ApplicationServer-2.sh
    3. Save setDomainEnv.sh and close the file.

  10. Change permissions for setAgentEnv_ApplicationServer-2.sh.


    # chmod 755 setAgentEnv_ApplicationServer-2.sh
    
  11. Start the WebLogic Server administration server.


    # ./startWebLogic.sh &
    

    Watch for startup errors.

  12. Log out of the ProtectedResource–2 host machine.