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

ProcedureTo Create an Access Manager Site on Access Manager 1

It is not necessary to repeat this procedure on Access Manager 2.

  1. Access http://AccessManager-1.example.com:1080/amserver/console in a web browser.

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

    Username

    amadmin

    Password

    4m4dmin1

  3. Under the Access Control tab, click example, the top-level Realm Name.

  4. Enter LoadBalancer-3.example.com, the name of the internal load balancer, in the Realm/DNS Aliases field and click Add.


    Caution – Caution –

    Do not remove the host names AccessManager-1 and AccessManager-2 from the alias list. These allow administrators to log in to the console directly in the event of a load balancer failure.


  5. Enter loadbalancer-3.example.com, a second entry for the same host name in all lowercase, and click Add.


    Caution – Caution –

    The Access Manager site will not be configured properly unless you use all lowercase when entering this second host name. This is a known issue.


  6. Click Save.

  7. Click Back to Realms.

  8. Click the Configuration tab.

  9. Under System Properties, click Platform.

  10. Under Site Name, click New, and enter the following values for the external load balancer.

    Server:

    https://loadbalancer-3.example.com:9443

    Site Name:

    11

  11. Click OK.

  12. Click Save

  13. Under Site Name, click New again, and enter the following values for the internal load balancer.

    Server:

    http://loadbalancer-3.example.com:7070

    Site Name:

    12

  14. Click OK.

  15. Click Save

  16. On the same Platform page, under Instance Name, click AccessManager-1.example.com:1080.

    Change the site ID to 01|11|12

  17. Click OK.

  18. Click Save

  19. On the Platform page again, under Instance Name, click AccessManager-2.example.com:1080.

    Change the site ID to 02|11|12

  20. Click OK.

  21. Click Save

  22. Log out of the Access Manager console.

  23. Log in to the AccessManager–1 host machine and restart Access Manager for the changes to take effect.


    # cd /opt/SUNWwbsvr/https-AccessManager-1.example.com/bin
    # ./stopserv; ./startserv
    
  24. Log in to the AccessManager–2 host machine and restart Access Manager for the changes to take effect.


    # cd /opt/SUNWwbsvr/https-AccessManager-2.example.com/bin
    # ./stopserv; ./startserv
    
  25. Log out of both Access Manager host machines.