Transformation scenario customization sequence

To transform a DITA object, IXIA CCMS Output Generator uses transformation scenarios.

The sequence for customizing a transformation scenario with CCMS Output Generator is the same, whether you are using the DITA Open Toolkit or another build script.

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).

Table 1. Sequence to customize a transformation scenario
Sequence	Step	Description, related file	Function
1 (Choose one of the two options)	Create a custom transformation target	A customized target file, such as acme-sample-target.Samplewrapper, using the conductor-ot.xml or conductor-ixia.xml file as a template	Contains sets of Apache Ant tasks, called targets Note: You can use more than one version of the DITA-OT. A single version needs a target and a single conductor client file. For two or more versions, you need a target and a conductor client file for each version. Each conductor file defines the DITA-OT to use, so add a target to the appropriate conductor file. Important: If you need to change the behavior of a target, do not modify the target directly. Instead, copy the target from the source conductor file to your client conductor file, such as, conductor-acme.xml, rename it, modify it in your conductor file, and change the preprocessor to point to your conductor file. This prevents an overwrite of your customized file during updates to the IXIA CCMS Output Generator.
1 (Choose one of the two options)	Add the target to a conductor file	client conductor file, such as conductor-acme-sample.xml	Contains the targets to initiate for the transformation scenario Note: You can write a target using any standard Apache Ant tasks and properties, or you can use the MadCap Software custom Ant properties, targets, and tasks.
2	Add a custom preprocessor	preprocessors.xml	Links the conductor file to the output type selected by a user and defines system and user parameters that apply to the transformation process
3	Add a custom output type Note: Each `<outputtype>` defined in the conf/client/outputtypes.xml file points to a `<preprocessor>` in the conf/client/preprocessors.xml file.	outputtypes.xml	Provides users with output types for transforming their DITA files, such as PDF or HTML Note: If you make the transformation scenario visible to your users, then they see the output types available in the Output Generator dialog and can select from the list during output generation.
4	Add a new customization plugin (Optional)	Diverse	Leverages an open source or new plugin you create to manage your transformation scenarios