File system structure
This chapter describes the file system structure of the application server and the ConSol CM application.
Server
ConSol CM data directory
Most of the data concerning the configuration and operation of ConSol CM is stored in the ConSol CM database. However, some data is saved in the file system in the data directory entered during system setup.
Important directories:
-
index
This is the directory where all the indexes are stored (see also section Index). Be sure to include it into your regular file system backup.
Please note that you cannot just include the index directory in your daily CM backup! Rather you have to use the indexer-specific backup (and restore). Please refer to section Backup and recovery of the index.
-
index.0
In this directory, there is a subdirectory for each required index.
-
In case units (customer objects) could not be imported during a scene import, there might be .tmp files in the data directory.
JBoss application server file structure
In an JBoss EAP installation the following directories are relevant for ConSol CM, among others:
- bin
Settings for all environments:- Configuration of the database connection and logging in the file cm6-config.properties or cm6-domain-config.properties
- Configuration of environment variables in the file standalone.conf or standalone.conf.bat
- modules\system\layers\base
Subfolders contain the JDBC drivers:- com\microsoft\sqlserver\jdbc\main\mssql-jdbc-7.4.1.jre8.jar
(Microsoft SQL) - oracle\jdbc\main\ojdbc8.jar and oracle\jdbc\main\orai18n.jar
(Oracle) - com\mysql\jdbc\main\
(MySQL JDBC driver destination, must be installed manually)
- com\microsoft\sqlserver\jdbc\main\mssql-jdbc-7.4.1.jre8.jar
- standalone
Configuration in standalone environments:- configuration
Configuration of the database connection and logging in the files cm6-<DB>.xml, cm6-cmrf-<DB>.xml or cm6-dwh-<DB>.xml - data
Data for operation, e.g., tx-operation keys - deployments
Deployed applications, for example cm6.ear and cm-track.war - log
Log files, see section Log files. - tmp
Temporary data and also working copy of the application server files. When JBoss is stopped, it can be emptied, e.g. for error analysis and/or fixing.
- configuration
- domain
Configuration in domain (i.e. multi-server) environments- configuration
Configuration of the database connection and logging in the files cm6-<DB>.xml, and master-host.xml and slave-host.xml - servers/<server-name>/log
Log files
- configuration
Client
- <ENGINEER_HOME_DIR>\.cmas\wfeditorR1\var\log
The log output of the Process Designer is written to this file. This is only relevant for engineers who work with the Process Designer. - <JAVA_CLIENT_DIR>
The directory where the temporary Java cache is stored. This is used, e.g., for the .jnlp downloads of the Admin Tool and the Process Designer application.