To Verify the J2EE Policy Agent Load Balancer Configuration is Working Properly

1. Restart the Application Servers.

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

   2. Change to the bin directory.

      # cd /usr/local/bea/user_projects/domains/ProtectedResource-1/bin

   3. Stop Application Server 1 managed instance.

      # ./stopManagedWebLogic.sh ApplicationsServer-1 t3://localhost:7001

   4. Stop the Application Server 1 administration server.

      # ./stopWebLogic.sh

   5. Start the Application Server 1 administration server.

      # ./startWebLogic.sh &

   6. Start Application Server 1 managed instance.

      # ./startManagedWebLogic.sh ApplicationServer-1 t3://localhost:7001

   7. Log out of the ProtectedResource–1 host machine.

   8. As a root user, log in to the ProtectedResource–2 host machine.

   9. Change to the bin directory.

      # cd /usr/local/bea/user_projects/domains/ProtectedResource-2/bin

   10. Stop the Application Server 2 managed instance.

       # ./stopManagedWebLogic.sh ApplicationsServer-2 t3://localhost:7001

   11. Stop the Application Server 2 administration server.

       # ./stopWebLogic.sh

   12. Start the Application Server 2 administration server.

       # ./startWebLogic.sh &

   13. Start the Application Server 2 managed instance.

       # ./startManagedWebLogic.sh ApplicationServer-2 t3://localhost:7001

   14. Log out of the ProtectedResource–2 host machine.

2. Access http://LoadBalancer-6.example.com:91/agentsample/index.html from a web browser.

   The Sample Application welcome page is displayed.

3. Click the J2EE Declarative Security link.

4. On the resulting page click Invoke the Protected Servlet.

   The policy agent redirects to the Access Manager login page.

5. Log in to the Access Manager console as testuser1.

   Username

   testuser1

   Password

   password

   If you can successfully log in as testuser1 and the J2EE Policy Agent Sample Application page is displayed, this first part of the test succeeded and authentication is working as expected.

6. Click the J2EE Declarative Security link to return.

7. On the resulting page, click Invoke the Protected Servlet.

   If the Successful Invocation message is displayed, this second part of the test has succeeded and the sample policy for the employee role has been enforced as expected.

8. Close the browser.

9. Open a new browser and access http://LoadBalancer-6.example.com:91/agentsample/index.html.

   The Sample Application welcome page is displayed.

10. Click the J2EE Declarative Security link.

11. On the resulting page click Invoke the Protected Servlet.

    The policy agent redirects to the Access Manager login page.

12. Log in to the Access Manager console as testuser2.

    Username

    testuser2

    Password

    password

    If the Access to Requested Resource Denied message is displayed, this third part of the test succeeded and the sample policy for the manager role has been enforced as expected.

13. Click the J2EE Declarative Security link to return.

14. On the resulting page, click Invoke the Protected EJB via an Unprotected Servlet.

    If the Successful Invocation message is displayed, the sample policy for the employee role has been enforced as expected.

15. Close the browser.