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

ProcedureTo Configure J2EE Properties for the Sample Application

  1. Log in as a root user to Protected Resource 2.


    # cd /opt/j2ee_agents/am_wl9_agent/agent_001/config
  2. Make a back up the AMAgent.properties file.

  3. Set the following properties:


    com.sun.identity.agents.config.notenforced.uri[0] =
       /agentsample/public/*
       com.sun.identity.agents.config.notenforced.uri[1] =
       /agentsample/images/*
       com.sun.identity.agents.config.notenforced.uri[2] =
       /agentsample/styles/*
       com.sun.identity.agents.config.notenforced.uri[3] =
       /agentsample/index.html
       com.sun.identity.agents.config.notenforced.uri[4] = 
       /agentsample
       com.sun.identity.agents.config.access.denied.uri =
       /agentsample/authentication/accessdenied.html
       com.sun.identity.agents.config.login.form[0] =
       /agentsample/authentication/login.html
       com.sun.identity.agents.config.login.url[0] = 
       http://LoadBalancer-3.example.com:7070/amserver/UI/Login?realm=users
  4. Save the file.

  5. Restart the Application Server 2.

    1. Stop Application Server 2 .

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

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

      # nohup ./startWebLogic.sh &
      # tail -f nohup.out
    4. Start Application Server 2.

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