Troubleshooting Symptom 3

Symptom: Instances of Agent for Sun Java System Web Server 7.0 are not effective after the modification of the Sun Java System Web Server 7.0 configuration using the Administration Console.

Possible Cause: Modifications to the configuration of the Web Server's configuration files (obj.conf, magnus.conf) might be overwritten by the server, which would disable the web agent completely.

Possible Solution:

1. Check whether multiple files named obj.conf exist in the config directory of the Sun Java System Web Server 7.0 instance.

2. If multiple files exist, then look for <object-file> in the server.xml file for which obj.conf is referenced.

3. If the referenced file is different from the default obj.conf file, then copy agent-related configuration settings to the new obj.conf file.

   The following settings need to be added. Use the default obj.conf file as a reference for where to add these settings:

PathCheck fn=validate_session_policy

<Object ppath="*/dummypost/sunpostpreserve*">
Service type=text/* method=(GET) fn=append_post_data
</Object>
<Object ppath="*/UpdateAgentCacheServlet*">
Service type=text/* method=(POST) fn=process_notification
</Object>