Additional Configurations Requiring the ServerPath Parameter

Situations that may require the ServerPath to be set are as follows:

The Web Agent tracks shared memory using a semaphore. A semaphore is a value in operating system (or kernel) storage that each process can check to see if a resource is available or not, and then change. The semaphore is not generated uniquely, so multiple Agents would try to point to the same area of memory, causing the Agent to function improperly. Naming a server path gives the root of an instance, which allows the Web Agent to find the files used for creating unique keys for semaphores.
For multiple server instances (all platforms except Windows), the Agent fails to execute one of the following:
- To encrypt agent name (00-0012 error)
- To encrypt SMSESSION or SMIDENTITY cookies
- To get agent key updates at start up
With Apache (all platforms except Windows), the Agent does not release its six shared memory segments (semaphores) when Apache is restarted.
If each Web Agent is configured for a different web server type on the same system, such as an Apache 2.0 server and an IIS 6.0 server, you are required to specify a unique ServerPath value for each server's configuration. Different web server types cannot share Agent resources.