JBoss configuration changed (#643782)
The way of configuring ConSol CM has been changed. The settings are not made in the configuration files anymore. Instead, new properties files which include the mandatory settings have been introduced:
- cm6-config.properties: standalone ConSol CM installation, and ConSol CM installation with CMRF in standalone mode (uncomment the respective lines if CMRF is used)
- cm6-domain-config.properties: cluster ConSol CM installation with CMRF (comment the respective lines if no CMRF is used)
- cm6-cmrf.properties: standalone ConSol CM installation with overlay CMRF installation
- cmrf-config.properties: standalone CMRF installation
They are located in the bin directory.
The configuration files have been adapted by introducing variables which can be referenced from the properties files. In addition, there is one configuration file for each database now:
- cm6.xml has been replaced by cm6-mysql.xml, cm6-oracle.xml and cm6-mssql.xml
- cm6-cmrf.xml has been replaced by cm6-cmrf-mysql.xml, cm6-cmrf-oracle.xml and cm6-cmrf-mssql.xml (used for CMRF overlay mode)
- cmrf.xml has been replaced by cmrf-mysql.xml, cmrf-oracle.xml and cmrf-mssql.xml (used for CMRF standalone mode)
- domain.xml has been replaced by cm6-mysql.xml, cm6-oracle.xml and cm6-mssql.xml
- host.xml has been replaced by master-host.xml and slave-host.xml
- The new files cm6-dwh-mysql.xml, cm6-dwh-oracle.xml and cm6-dwh-mssql.xml have been added. They are used for ConSol CM when CMRF is configured in standalone mode.
You need to edit the properties file for your setup and make the mandatory settings:
- Database user and password
- URL of the transactional and non-transactional datasource
- Host and jgroups settings (cluster only)
In addition, you can use the properties files to override the default settings from the XML configuration file, for example logging settings. You can override all the settings which contain variables with default values in the configuration file.
Example:
You want to change the log level of the index.log file to DEBUG.
-
Locate the respective handler in the configuration file (example from cm6-mysql.xml).
<periodic-size-rotating-file-handler name="INDEX_FILE" autoflush="true">
<level name="${handler.indexfile.level:INFO}"/>
<formatter>
<pattern-formatter pattern="%d %-5.5p [%30.-30c] [%X{username}-%X{context}-%X{sessionId}] %m%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="index.log"/>
<suffix value=".yyyy.MM.dd"/>
<max-backup-index value="${handler.indexfile.max.backup.index:1}"/>
<append value="true"/>
</periodic-size-rotating-file-handler>
-
Locate the variable for the log level.
This is ${handler.indexfile.level:INFO}.
-
Add an entry for this variable to the properties files, e.g. cm6-config.properties.
# logging overrides
handler.indexfile.level=DEBUG
These settings also affect the command to start ConSol CM. The properties file needs to be provided as -P parameter and the configuration file as -c parameter in the start command.
Example:
<JBOSS_HOME>/bin/standalone.sh -P <JBOSS_HOME>/bin/cm6-config.properties -c cm6-<DB>.xml