Deployment Example 2: Federation Using SAML v2

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

  1. In a browser, go to the following URL:

    https://LoadBalancer-11.siroe.com:6443/index.html

    The load balancer redirects the request to the Access Manager login page.

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

    Username

    spuser

    Password

    spuser

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

  3. Verify that Load Balancer 11 monitors are monitoring the Web Servers properly.

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

    2. Run the tail command.


      # cd /opt/SUNWwbsvr/https-ProtectedResource-3.siroe.com/logs
      # tail -f access

      If you see frequent entries similar to this one:


      192.18.69.18 - - [06/Oct/2006:13:53:07 -0700] "GET /launch.html" 200 8526

      then the custom monitor is configured properly. If you do not see "GET /launch.html", then you must troubleshoot the load balancer configuration.

    3. Log in as root to Protected Resource 4.

    4. Run the tail command.


      # cd /opt/SUNWwbsvr/https-ProtectedResource-4.siroe.com/logs
      # tail -f access

      If you see frequent entries similar to this one:


      192.18.69.18 - - [06/Oct/2006:13:53:07 -0700] "GET /launch.html" 200 8526

      then the custom monitor is configured properly. If you do not see "GET /launch.html", then you must troubleshoot the load balancer configuration.