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

ProcedureTo Configure the J2EE Policy Agents to Access the Distributed Authentication UI Server

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

    # cd /opt/j2ee_agents/am_wl9_agent/agent_001/config
  2. Make a backup of the file

  3. In the file, set the following properties:

    com.sun.identity.agents.config.login.url[0] =
  4. Save the file.

  5. Restart the Application Server.

    1. Stop Application Server 2.

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

      #cd /usr/local/bea/user_projects/domains/ProtectedResource-2/bin 
    3. Start the administration server.

      # nohup ./ &
      # tail -f nohup.out

      Watch for startup errors.

    4. Start Application Server 2.

      # nohup ./
      ApplicatoinServer-2 &
      tail -f nohup.out
  6. Verify that the agents are configured properly.

    1. Go to the sample application URL:

    2. In the left navigation bar, click “Invoke the Protected Servlet.”

      You are redirected to the Distributed Authentication UI server URL The Access Manager login page is displayed.

    3. Double-click the gold lock in the lower left corner of the browser.

      In the Properties page, you see certificate for LoadBalancer–

    4. Log in to the Access Manager console using the following information:





      You are redirected to the protected servlet of the Sample Application, and a success message is displayed. This indicates that authentication through the Distributed Authentication UI server was successful.