Deployment Example: Single Sign-On, Load Balancing and Failover Using Sun OpenSSO Enterprise 8.0

ProcedureTo Create a Monitoring File on Each Host Machine for Load Balancer 4

In order to configure the web policy agents to point to Load Balancer 4, create a file to be used by Load Balancer 4 for monitoring and modify the web agent properties — adding Load Balancer 4 as the virtual host. Instructions on how to create a monitoring file are in the following procedure. Instructions on how to modify the web agent properties are in To Add Load Balancer 4 as a Virtual Host by Modifying the Web Policy Agent Properties.


Note –

We can alternately use the default Web Server index.html rather than create monitor.html but in this deployment, index.html is used to represent the resource protected by the web policy agent.


  1. As a root user, log in to the pr–1 host machine.

  2. Change to the config directory.


    # cd /opt/SUNWwbsvr/https-pr-1.example.com/docs
    
  3. Create a monitor.html file to be used by the load balancer.


    # cat > monitor.html
    
    <HTML>
    </HTML>
    
    Hit Control D to terminate the command
    
    ^D
    
  4. Run the tail command.


    # cd /opt/SUNWwbsvr/https-pr-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 - - [30/Jul/2008:13:59:48 -0700] "GET /monitor.html" 200 15

    Tip –

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


  5. Log out of the pr–1 host machine.

  6. As a root user, log in to the pr–2 host machine.

  7. Change to the config directory.


    # cd /opt/SUNWwbsvr/https-pr-2.example.com/docs
    
  8. Create a monitor.html file to be used by the load balancer.


    # cat > monitor.html
    
    <HTML>
    </HTML>
    
    Hit Control D to terminate the command
    
    ^D
    
  9. Run the tail command.


    # cd /opt/SUNWwbsvr/https-pr-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 - - [30/Jul/2008:13:59:48 -0700] "GET /monitor.html" 200 15

    Tip –

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


  10. Log out of the pr–2 host machine.