The Appspy client side needs 3 configuration files :
Those files are loader by a configuration loader. There is one configuration loader for each file.
By default, Appspy uses the org.appspy.client.common.config.FileConfigLoader which look in the Appspy home directory.
You can alternatively use the org.appspy.client.common.config.ClasspathConfigLoader to load one or more files.
This can be achieved by setting the following servlet context parameters :
Example to load the webapp collector configuration part from the classpath instead of the appspy home directory :
<context-param>
<description>Appspy config loader for webapp collector part</description>
<param-name>org.appspy.webappConfigLoader</param-name>
<param-value>org.appspy.client.common.config.ClasspathConfigLoader</param-value>
</context-param>
You can change the name of the configuration files by setting the following servlet context parameters :
Where {0} will be replaced at runtime by the value of the system property appspy-mode (default if not set). This is useful if you want to use different configurations (environment code or different collector URL for instance) on different servers.
Example to load the webapp collector configuration part from the file "my-own-webapp-configuration-file.xml" (independently of the value of the system property appspy-mode) :
<context-param>
<description>Appspy config file for webapp collector part</description>
<param-name>org.appspy.webappConfigPattern</param-name>
<param-value>my-own-webapp-configuration-file.xml</param-value>
</context-param>