test

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

ProcedureTo Verify that the Access Manager Load Balancer is Configured Properly

  1. Log in as root to the host AccessManager–1.

  2. Run the tail command to view the access log.


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

    If you see frequent entries similar to this one:


    xxx.xx.69.18--[12/Oct/2006:13:10:20-0700]
"GET/amserver/isAlive.jsp" 200 118

    then the custom monitor is configured properly. If you do not see “GET /amserver/isAlive.jsp” then you must troubleshoot the load balancer configuration.

  3. Log in as root to the host AccessManager-2.

  4. Run the tail command to view the access log.


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

    If you see frequent entries similar to this one:


    xxx.xx.69.18--[12/Oct/2006:13:10:20-0700]
"GET /amserver/isAlive.jsp" 200 118

    then the custom monitor is configured properly. If you do not see “GET /amserver/isAlive.jsp” then you must troubleshoot the load balancer configuration.

  5. Start a new browser and go to the internal-facing load balancer URL.

    Example: http://LoadBalancer-2.example.com:90/ . Do not supply the amserver prefix.

    If the browser successfully renders the default Sun Web Server default document root page, close the browser.