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

ProcedureTo Configure the J2EE Policy Agent for SSL

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

    # cd /opt/j2ee_agents/am_wl9_agent/agent_001/config

  2. Make a backup of the AMAgent.properties file.

  3. In the AMAgent.properties, set the following properties:

    com.sun.identity.agents.config.login.url[0] = 
    https://LoadBalancer-3.example.com:9443/amserver/UI/Login?realm=users 
    com.sun.identity.agents.config.cdsso.cdcservlet.url[0] = 
    https://LoadBalancer-3.example.com:9443/amserver/cdcservlet 
    com.sun.identity.agents.config.cdsso.trusted.id.provider[0] = 
    https://LoadBalancer-3.example.com:9443/amserver/cdcservlet 
    com.iplanet.am.naming.url=
    https://LoadBalancer-3.example.com:9443/amserver/namingservice 
    com.iplanet.am.server.protocol=https 
    com.iplanet.am.server.port=9443
  4. Save the file.

  5. Stop Application Server 1 .

    # cd /usr/local/bea/user_projects/domains/ProtectedResource-1/bin
    # ./stopManagedWebLogic.sh ApplicationsServer-1 t3://localhost:7001 
  6. Stop the administration server.

    # ./stopWebLogic.sh
  7. Start the administration server.

    # nohup ./startWebLogic.sh &
    # tail -f nohup.out
  8. Start Application Server 1.

    # nohup ./startManagedWebLogic.sh 
    ApplicationServer-1 http://ProtectedResource-1.example.com:7001 &