CCMS Output Generator directory structure

When you extract CCMS Output Generator files, the following directory structure results:

Note: In a dedicated SaaS deployment, your access to the Output Generator is limited. Some tasks require the use of the Output Generator Access Tool (OGAT).
Figure: CCMS Output Generator directory
Output Generator directory
Directory Description Requires restart?1
bin Contains the programs for installing, starting, and uninstalling CCMS Output Generator. Yes
conf Contains the CCMS Output Generator configuration. Yes
conf\client Contains the client configuration Yes
data Contains the transformation scenarios as well as the DITA Open Toolkit. No
data\resources\ client Contains the client resource files. No
libs Contains binary files required by CCMS Output Generator. Yes
libs\client Contains client binary files. Yes
logs Contains the CCMS Output Generator log files. No
temp Contains the temporary files created during the output generation process. No
pid Contains the .pid file (Linux only). No

1 Indicates whether the CCMS Output Generator needs to be restarted if changes are made to files in this directory.

The CCMS Output Generator directory structure is organized so that your configuration changes are not lost between upgrades.

Files that you need to modify are provided in one of the following formats:
  • *.empty files (for example, corba.properties.empty): Many configuration files are provided in the initial installation with the .empty suffix. Use these files as a template, and remove the .empty suffix when saving them (keeping the original .empty file unmodified for backup).

    The *.empty files are required by CCMS Output Generator. You must configure them otherwise CCMS Output Generator will not work.

  • *-client.xml.orig files (for example, data/conductor-client.xml.orig): Some of the Ant conductor files are provided in the initial installation with the -client.xml.orig suffix. Use these files as a template, and rename the -client suffix to your company name (for example, conductor-acme.xml).

    The *.orig files are optional.

  • *.orig files in the conf/client directory (for example, conf/client/outputtypes.xml.orig): The configuration files in the conf/client directory are provided with the .orig suffix. Use these files as a template, and remove the .orig suffix when saving them (keeping the original .orig file unmodified for backup).

    The *.orig files are optional.