Open topic with navigation

ConSol CM File System Structure

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.

ConSol CM Data Directory

The following figure and list show examples from Windows and Linux systems:

Figure 490: ConSol CM - Data directory (Windows)

Figure 491: ConSol CM - Data directory (Linux)

Example directories:

• index

  This is the directory where all the indexes are stored (see also section Search Configuration and Indexer Management). Be sure to include it into your regular file system backup.

  • index.0

    In this directory, there is a subdirectory for each required index.

• mail

  This directory is only relevant when the system is operated in Mule/ESB mode. When NIMH is used, all data is stored in the database. Files that are relevant for incoming e-mails are stored in this directory.

  • reimported
    

    In this directory, e-mails are stored which had been stored in the unparsable directory and could then be re-imported by a manual action of the administrator.

  • unparsable
    

    In this directory, incoming e-mails that cannot be processed by the system are stored. They are listed under E-Mail Backups in the Admin Tool, see section E-Mail Backups.

• mule
  This is a directory which might be used for Mule (internal ESB) data.

JBoss 7 Application Server File Structure

The following directories are available in a JBoss 7 installation of ConSol CM:

Figure 492: ConSol CM - File structure in a JBoss 7 system

Example directories:

• modules\system\layers\base
  Subfolders contain the JDBC drivers:
  • com\microsoft\sqlserver\jdbc\main\sqljdbc4.jar
    (Microsoft SQL)
  • oracle\jdbc\main\ojdbc6-11.2.0.3.jar
    (Oracle)
  • com\mysql\jdbc\main\
    (MySQL JDBC driver destination, must be installed manually)
• standalone
  Configuration in single-server environments:
  • configuration
    Configuration of the DB connection and logging in the file cm6.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. Can be emptied, e.g., for error analysis and/or fixing.
• domain
  Configuration in domain environments
  • configuration
    Configuration of the DB connection and logging in the file domain.xml
  • servers/<server-name>/log
    Log files

Oracle WebLogic Application Server File Structure

In an Oracle WebLogic environment, ConSol CM is installed as a separate domain. ConSol CM and CMRF are managed servers. Please see the ConSol CM Operations Manual for details.

Here, only some directories are explained. If you want to administer ConSol CM as a WebLogic application, please also refer to general Weblogic tutorials.

Figure 493: ConSol CM - File structure in an Oracle WebLogic application server

Example directories:

• bin
  Start/stop scripts
• cm-logs
  All log files except for cmrf.log
• cmrf-logs
  • cmrf.log file
    Log messages for the CMRF (ConSol CM Reporting Framework)
• config
  Configuration files
• deployments
  Deployed applications, i.e., here: ConSol CM and CMRF as directories