Corticon installs groups of properties that specify the property names and default values of most user-configurable behaviors in Corticon Studio and Corticon Servers. When you launch Studio or Server, the groups of default property name=value pairs are loaded in the following order:
Controls behaviors of the Corticon Deployment Console functions.
Reserved for licensed OEM customers to override vendor-specific properties.
Reserved for internal use.
These properties pages are not intended for user access. Instead, the file brms.properties, installed by every product at the root of [CORTICON_WORK_DIR], enables you to add your override settings to be applied after the default settings have been loaded.
Note: A running instance of Corticon Server can modify certain properties through API method calls, as discussed in the Administrative API section. While settings in brms.properties persist across Corticon Server sessions, changes applied through APIs only remain in effect for that Corticon Server session. When Corticon Server starts a new session, it will look to the default settings and the override properties file.
Corticon Servers use mostly the Common and Server properties. See those topics for information on the possible settings and values that you might want to add to your override properties file for deployed servers.
Properties used by Deployment Console
The Deployment Console, installed with each of the Corticon Servers, uses mostly the Common and Deployment properties. See those topics for information on the possible settings and values that you might want to add to your override properties file for deployment consoles.
Note: Preferred technique for overriding default properties - In earlier releases, updates were made to the default properties in the CcConfig.jar. That practice is now discouraged because it prevents reversion to initial values when you are trying to resolve problems. Use the brms.properties file installed at the work directory root, or -- for Studio -- the location specified in Eclipse preferences. For backward compatibility, all previous locations of property settings are checked, and will continue to be supported; however, if you use those classic techniques, the brms.properties at the work directory root will trump all others.