Sample interactions during default transformation scenario

The interaction among various files to obtain output begins with the Generate Output dialog.

Note: The Export output is only available to system administrators.

Consider a simplified transformation scenario that extracts the raw DITA content from the CMS and stores it in the zip file returned by CCMS Output Generator: the Export output type listed in the Generate Output dialog.

Example Admin selects Export from the Output Generator dialog. In response, CCMS Output Generator uses the outputtypes.xml file to locate the preprocessor associated with the selected output type. It uses the preprocessor name, export, and then locates the preprocessors.xml file to find the conductor-ixia.xml conductor file that contains the exporttarget to initiate.

Important: In the example, the flow only optionally includes an OT plugin. However, for custom output types, a plugin is required.
Note: The actual code in the target performs the transformation.
Figure: Interactions during an Export transformation process
  1. The output type for Export is defined in <outgen>/conf/outputtypes.xml and points to the preprocessor named export. The output name Export is what the user sees in the Generate Output dialog for an output type.
  2. The preprocessor named export is defined in <outgen>/conf/preprocessors.xml. It defines the conductor file using the value of parameter name buildfile and the target within the conductor using value of the parameter name target.
  3. The conductor is defined in <outgen>/data/conductor-ixia.xml and contains the target and transformation types necessary to generate the output.
    Note: This example is a default export output that requires no actual transformation, so it is not comparable to an output type you would add to customize your output. It does not call for a transformation type, or transtype, that you would normally specify in an OT plugin. That's because it runs the first step of extracting the content, then immediately returns the content to the user after bundling it into a zip file, rather than proceeding to send it for transformation.