My webMethods Server 10.2 | System Administrator Functions | My webMethods Server Configuration | Configuring My webMethods Server Cache | Modifying Cache Settings in the cache.xml File
 
Modifying Cache Settings in the cache.xml File
You use the cache.xml file for detailed configuration of My webMethods Server cache types. The cache.xml file is stored in the My webMethods Server database. Changes to the cache.xml file apply to all nodes in a My webMethods Server cluster.
The default storage location for a local copy of the file is Software AG_directory \MWS\server\serverName\config. To configure a My webMethods Server instance to use a copy of the cache.xml file, stored in a non-default location, add the following JVM property in the custom_wrapper.conf file for the instance:
-Dcom.webmethods.mws.cachemanager.configfile=path
where path is the path to the directory that contains the cache.xml file. For more information about configuring JVM properties, see Configuring JVM Settings for My webMethods Server.
Unless you specify custom settings in the cache.xml file, cache settings are applied using the OSGi properties of each cache type, stored in the OSGI-INF/ directory of the component jar for the type. You can configure cache settings individually for each component, as described in Modifying Cache Settings with Custom Property Files.
* To modify cache settings in the cache.xml
1. In a command line prompt, navigate to the bin directory of the server:
Software AG_directory\MWS\bin
2. Retrieve the cache.xml file from the My webMethods Server database using the getconfig command:
mws getconfig cache.xml
3. Open the cache.xml file in a text editor and edit cache settings as required.
The default download location of the cache.cml file is Software AG_directory \MWS\server\serverName\config.
4. Save and close the file.
5. To deploy the updated file to the My webMethods Server database, type the following command:
mws putconfig cache.xml
6. Delete the file local copy of the cache.xml file from the serverName\config directory.
If you do not delete the copy, this server instance will continue to use the local version of the configuration file.
7. Restart the node using the restart command:
mws -s serverName restart
Changes to configuration files apply after restarting the server.

Copyright © 2004-2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release