Customize an existing IXIASOFT CCMS transformation scenario

If you need to change the behavior of a target that is located in a IXIASOFT CCMS conductor file, do not modify the target directly.

Instead, copy the target from the IXIASOFT CCMS conductor file to your client conductor file, rename it, modify it in your client conductor file, and set your client preprocessor to point to your conductor file. This ensures that any updates to the IXIASOFT Output Generator software will not overwrite your customization.

The following procedure describes how to customize the Dita2PDF transformation scenario so that:

<draft-comment> elements are included in the output
Only reltable links are included in the output

Open your client conductor file (for example, %OutputGenDir%/data/conductor-acme.xml).
Open the conductor file that contains the target you want to modify (for example, for the Dita2PDF transformation scenario, open %OutputGenDir%/data/conductor-ot.xml).
Copy the contents of the target to modify from the IXIASOFT CCMS conductor file (for example, %OutputGenDir%/data/conductor-ot.xml) to your client conductor file (for example, %OutputGenDir%/data/conductor-acme.xml).
For example, for the Dita2PDF transformation scenario, copy the dita2pdfwrapper target.
Edit the target name to indicate that the target was customized for your company.
IXIASOFT recommends that you add your company name before the target name. For example:
```
<target name="acme.dita2pdfwrapper" depends="default_dependencies, flatten, resolve_container_keyref, extract_HiRes_images">

   ...
```

Modify the target in your client conductor file.

For example, to include <draft-comment> elements and reltable links only in the output, configure the args.rellinks and args.draft parameters as follows:

<target name="acme.dita2pdfwrapper" depends="default_dependencies, flatten, resolve_container_keyref, extract_HiRes_images">

   <property name="outgen.job.build.filename" 
             location="${outgen.job.dir}/build.xml"/>
   <property name="outgen.job.build.template.filename" 
             location="${outgen.resources.dir}/job-build-template.xml"/>
   <property name="outgen.job.build.otlog.filename" 
             location="${outgen.job.ot.log.dir}/${outgen.job.source.name.noext}.ot.log"/>

   <antcall target="ot_build_create"/>
   <antcall target="ot_build_add_pdfrenderer"/>
   <antcall target="ot_build_add_ditaval_ifpresent"/>
   <antcall target="ot_build_clean_ot_temp"/>
   <antcall target="ot_build_keep_topicfo"/>

   <update-ot-build-file buildfile="${outgen.job.build.filename}">
      <param name="transtype" value="pdf2"/>
      <param name="args.rellinks" value="nofamily"/>
      <param name="args.draft" value="yes"/>

   </update-ot-build-file>

   <antcall target="dita_startcmd_ot_build"/>

   <antcall target="clean_ot_output"/>

</target>

Save and close your client conductor file.
Open your client preprocessor file (for example, %OutputGenDir%/conf/client/preprocessors.xml).
Open the %OutputGenDir%/conf/preprocessor.xml file.
Copy the contents of the preprocessor to modify from the IXIASOFT CCMS preprocessor file (i.e., %OutputGenDir%/conf/preprocessor.xml) to your client preprocessor file (i.e., %OutputGenDir%/conf/client/preprocessors.xml).
For example, for the Dita2PDF transformation scenario, copy the dita2pdf preprocessor.

Set the buildfile and target parameters to point to the new target.

For example:

<preprocessor name="dita2pdf" class="com.ixiasoft.outputgenerator.preprocessor.AntProcessor" >
   <parameters>
      <system>
         <parameter name="buildfile" value="/conductor-acme.xml"/>
         <parameter name="target" value="acme.dita2pdfwrapper"/>
         <parameter name="clean" value="job_postprocess"/>
         <parameter name="keep.log.files" value="true"/>
      </system>
   </parameters>
</preprocessor>

To test the transformation scenario, restart the IXIASOFT Output Generator service.