Multiple Agent Identities

Exercise 2:  Multiple Agent Identities

• Create a new agent identity for the secondary web server
• Add this new agent identity to your agent group
• Edit the Agent Configuration Object
  
  • Add an AgentName parameter
  • Add the new agent identity, host to the parameter
• Restart the secondary web server
• Using the secondary web server, attempt to access a resource
• Look in the profiler log to verify that your secondary agent is using the new agent identity

In this exercise, you will create a second agent identity for the agent residing on the secondary web server. Each agent identity will still share the same agent configuration object. In order for your agent to connect as a different identity, you will need to add the AgentName parameter to your agent configuration object and register any non-default agent identities in that parameter.

Using the agent dialog, create a new agent identity for the web agent on the secondary web server.

Note: Don’t forget to add this new agent to your agent group!

Edit the Agent Configuration Object that is shared by the two web agents. Click the Add button to add the AgentName parameter.

In the Edit parameter dialog:

• Specify the parameter name: AgentName
• Specify the value in the form of agentname,host where host can be an IP address or a fully qualified domain name

Note: in order to register multiple agent identities in the same agent configuration object, you would use the multi-value option to specify multiple agent,host values.

 

Now when the secondary web server attempts to access a resource, you should see the new agent identity in the policy server’s profiler log.

Now when the secondary web server attempts to access a resource, you should see the new agent identity in the policy server’s profiler log.

<< Back to Exercise 1