Sun Java System Reference Configuration Series: Portal Service on Application Server Cluster

ProcedureTo Verify Load Balancing for the Gateway Service

This procedure verifies that you can interact with Gateway instances through the load balancer and that the load balancer provides service failover when a Gateway instance fails.

  1. Start the Gateway instances on sra1 and sra2, if they are not already running.

    # /opt/SUNWportal/bin/psadmin start-sra-instance -u amadmin -N default -t gateway --restrictive

    When prompted, type the access-manager-admin-password.

  2. Start a browser.

  3. Go to the Access Manager login page by using the load balancer URL

    The Access Manager login page opens.

  4. Log in to the portal by typing the following values and clicking Login.

    Input Field 


    User ID 




    The Developer Sample desktop opens, which confirms that the load balancer has routed the login request to one of the Gateway instances.

  5. Determine the Gateway instance handling the login request in Step 4.

    1. Open the log file on sra1.

      # cd /var/opt/SUNWportal/logs/sra/default

      # tail —f portal.gateway.0.0.log

    2. Open the log file on sra2.

      # cd /var/opt/SUNWportal/logs/sra/default

      # tail —f portal.gateway.0.0.log

    3. Note which log file displays more output.

      Whichever Gateway instance is servicing the request will cause more output to be generated.

  6. Simulate a failure of the Gateway instance that was noted in Step 5.

    In the configuration interface for your load balancer (, disable the Gateway instance that you identified in Step 5 (or otherwise remove it from the service group).

  7. Refresh the browser page.

    If service failover is working correctly, the Access Manager login page opens, confirming that the load balancer has routed the request to the remaining online Gateway instance.

  8. Recover the simulated failure of your original Portal Server instance.

    Return to the configuration interface for your load balancer, and replace the real server instance that you removed in Step 6 to the load balancer service group.