Running Business Processes and Composite Applications : Administering My webMethods Server : Modifying Configuration Files : Modifying Configuration Files Stored in the Database
Modifying Configuration Files Stored in the Database
Many configuration files that could be found in the directory structure of earlier versions of My webMethods Server are now stored in the server database. You can get those configuration files from the database using the mws getconfig command.
Most of the configuration files are stored in the My webMethods Server database by default, instead of in the local file system. To edit any My webMethods Server configuration file, you need to download the file from the database. The following table shows the files you can download using the mws getconfig command.
Note:  
File names and file contents are case sensitive.
Configuration file
Purpose
cache.xml
Increase cache size.
cluster.xml
Contain configuration data for each node in a cluster.
defaultPortletAppWeb.xml
Modify properties of a web application.
defaultPartitionPortlets.properties
List the portlets affected by the phase provider for the default cluster partition. If you have multiple cluster partitions, it is possible to have multiple portlets properties files, each having the file name partitionNamePortletsProperties.xml
email.properties
Configure email servers.
iconMap.properties
Map mime types (Content types) to icons located in the ui\images directory.
jetty.xml
Configure the Jetty server.
log4j.init.properties
Turn internal debugging on or off (Apache Log4J logging package).
log4j.override.properties
Modify properties of the Apache Log4J logging package.
logging.properties
Customize logging folders, patterns, and so forth.
mimeTypes.properties
Customize mime types.
perfUtil.properties
Enable and disable the performance service
phaseProvider.xml
Modify the server polling interval. If you have multiple cluster partitions, it is possible to have multiple phase provider files, each having the file name partitionNamePhaseProvider.xml.
storageConfig.xml
Configure content services.
systemPaths.properties
Configure the location of logs or the temp folder.
systemProperties.properties
Contain persisted System.properties.
defaultPortletAppWeb.xml
Modify properties of a web application.
email.properties
Configure email servers.
websso.properties
Configure single sign-on for a third-party identity provider (IDP) using Security Assertion Markup Language (SAML).
Note:  
It is not necessary that a My webMethods Server instance be running, but the My webMethods Server database needs to be running.
To edit configuration files for My webMethods Server
1. At a command line prompt, type the following command to move to the server’s bin directory:
cd Software AG_directory\MWS\bin
2. To retrieve a configuration file from the My webMethods Server database, type this command:
mws getconfig fileName
where fileName is the name of the configuration file you intend to edit.
For example:
mws getconfig cluster.xml
mws getconfig logging.properties
3. Open the downloaded configuration file in a text editor and modify it as needed.
You can find the file at this location:
Software AG_directory \MWS\server\serverName\config
4. To deploy the revised file to the My webMethods Server database, type this command:
mws putconfig fileName
5. Delete the file from the \serverName\config directory.
If you do not delete the file, this server instance will continue to use the local version of the configuration file.
6. Restart the node using this command:
mws -s serverName restart
Changes to configuration files are not applied until after a restart.
Copyright © 2016 Software AG, Darmstadt, Germany.
Product LogoContact Support   |   Community   |   Feedback