Changes to conductor file targets

Because the build.bat and build.properties file now replace the build.xml file, the targets in the conductor files themselves have also changed. If you want to generate output in IXIA CCMS Web, you must upgrade your conductor files.

Comparison of conductor files

As an example, here is a comparison of the dita2pdfwrapper target in the conductor-ot.xml file for IXIA CCMS Output Generator 7.2 and pre-7.2 version of CCMS Output Generator.

Difference Description 
<property name="outgen.job.build.filename" 
		location="${outgen.job.dir}/build.xml"/>
	<property name="outgen.job.build.template.filename" 
		location="${outgen.resources.dir}/job-buil
			d-template.xml"/>
	<property name="outgen.job.build.otlog.filename" 
		location="${outgen.job.ot.log.dir}/${out
			gen.job.source.name.noext}.ot.log"/>
 These three properties are no longer present in CCMS Output Generator 7.2.

The first two properties specified the location of the now-deprecated files build.xml and job-build-template.xml. CCMS Output Generator 7.2 uses a different method for generating the log file, so the third property is also no longer needed.

 
<antcall target="ot_build_create"/>
 This antcall has been removed.

It created the build.xml file, which is no longer used in CCMS Output Generator 7.2. 

<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"/>
 These antcalls have been replaced by macros.

The antcalls have been replaced by macros because when you do an antcall to a subtarget and set a property in that subtarget, the property is no longer available outside of that subtarget after the antcall completes. This is a problem because those properties are needed within the main target to create the properties file. Using macros instead of antcalls avoids this issue.

 
<ot_build_add_pdfrenderer/>
<ot_build_add_ditaval_ifpresent/>
<ot_build_clean_ot_temp/>
<ot_build_keep_topicfo/>
 These macros replace the antcalls.

These macros are defined in commontargets-system.xml.

 
<update-ot-build-file buildfile="${outgen.job.build.filename}">
   <param name="transtype" value="pdf"/>
   <param name="args.rellinks" value="none"/>
   <param name="args.draft" value="no"/>
</update-ot-build-file>
 The update-ot-build-file section has been replaced by individual ot_build_set_parameter macros, also defined in commontargets-system.xml. 
<ot_build_set_parameter name="transtype" value="pdf2"/>
<ot_build_set_parameter name="args.rellinks" value="none"/>
<ot_build_set_parameter name="args.draft" value="no"/>
<ot_build_set_parameter name="bigcorp.module" value="${outgen.job.userparam.bigcorp.module}"/>
 The ot_build_set_parameter macro defined in commontargets-system.xml.

If you have defined your own user properties for the Generate Output screen, you add them as before in this same section, such as the example line in bold.

 
<antcall target="dita_startcmd_ot_build"  inheritRefs="true"/>
<antcall target="clean_ot_output"/>
 These two antcalls have also been replaced by corresponding macros defined in commontargets-system.xml. 
<dita_startcmd_ot_build/>
<clean_ot_output/>
 Two macros that replace antcalls. The dita_startcmd_ot_build macro is what starts the build process.

Updating your conductor files

All these changes are in each of the generic targets in the conductor-ot.xml file and the MadCap Software-specific targets in the conductor-ixia.xml and conductor-ixia-cr.xml files.

When you add your own targets to the conductor-client.xml file, follow the pattern of the targets in these three files.