Verifying the Application Server 9.1 / GlassFish 2.1 Agent in the Cluster

You can now test the cluster. This task uses the agentsample.ear sample application, which is in the following directory after you unzip the agent distribution file.

<BASE_DIR>/j2ee_agents/appserver_v9_agent/sampleapp/dist

To Verify the Application Server 9.1 / GlassFish 2.1 Agent in the Cluster

1. On the host where the DAS instance is running, deploy the agentsample.ear sample application to your cluster . For example, using asadmin with the deploy option:

   ./asadmin deploy --target agents30 --port 34848 --availabilityenabled=true
   /export/sun/j2ee_agents/appserver_v9_agent/sampleapp/dist/agentsample.ear

2. On the OpenSSO server, modify the Agent Filter Mode:

   1. Log in to the OpenSSO Administration Console.

   2. Click Access Control, realm-name, Agents, J2EE, and then the name of the agent profile (remotecluster).

   3. Under Agent Filter Mode, remove the value ALL and add the value SSO_ONLY.

      The SSO_ONLY value will ask only for authentication for the resource being accessed from the cluster URL, which is http://is-lb-2.example.com:38181/agentsample/index.html. When a user accesses this URL, the cluster will redirect the user to the OpenSSO server for authentication.

   4. Click Save.

3. Restart the DAS instance and cluster together with node agent to get the configuration changes propagated.

   Also, when you restart the node agent, specify the syncinstances=true option to have the configuration changes reflected in the remote instances.

See Also

You can use the agentsample.ear sample application to learn more about policy agents and OpenSSO server features. For information, see Deploying the Policy Agent Sample Application.