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

ProcedureTo Verify the Web Policy Agents Load Balancer Configuration is Working Properly

  1. Access http://loadbalancer-5.example.com:90/index.html, the Access Manager load balancer, from a web browser.

  2. Log in to the Access Manager console as testuser1.

    Username

    testuser1

    Password

    password

    If the default Web Server index.html page is displayed, the load balancer is configured properly.

  3. Verify that Load Balancer 5 monitors are monitoring the Web Server instances properly.

    1. Log in as a root user to the ProtectedResource–1 host machine.

    2. Run the tail command.


      # cd /opt/SUNWwbsvr/https-ProtectedResource-1.example.com/logs
      # tail -f access
      

      If you see frequent entries similar to the one below, the custom monitor is configured properly.


      IP_address - - [21/Sep/2007:13:59:48 -0700] 
      "GET /monitor.html" 200 15

      If you do not see "GET /monitor.html", you must troubleshoot the load balancer configuration.

    3. Log in as a root user to the ProtectedResource–2 host machine.

    4. Run the tail command.


      # cd /opt/SUNWwbsvr/https-ProtectedResource-2.example.com/logs
      # tail -f access
      

      If you see frequent entries similar to the one below, the custom monitor is configured properly.


      IP_address - - [21/Sep/2007:13:59:48 -0700] 
      "GET /monitor.html" 200 15

      If you do not see "GET /monitor.html", you must troubleshoot the load balancer configuration.

    5. Log out of both Protected Resource host machines after you have verified that the monitors are working properly.