Create a Build Manifest template
IXIA CCMS includes a default Build Manifest template, but you can create a new one for your deployment.
You can predefine information that is common to all Build Manifest objects created from your template.
Important: Make configuration changes in a test
environment and confirm they work before copying them to a production
environment.
Some use cases include:
- Setting default user parameters in your template to avoid manual entry every time by your users. For example, the PDF transformation scenario at MadCap Software requires three user parameters, so a template that presets these user parameters makes sense.
- Setting default output types per product. For example, Product A documentation could be generated in three formats: PDF, xHTML, and online help, but Product B documentation only requires two formats: PDF and xHTML output. In such a case, you could create one template per product that defines appropriate output types.
The following code shows the structure of a sample Build Manifest template:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE build-manifest PUBLIC "-//IXIA//DTD CMS Build Manifest//EN" "build-manifest.dtd">
<build-manifest xml:lang="en-US" id="id">
<title>Build Manifest Template for Product A</title>
<globals>
<shortdesc>Build Manifest Template for Product A</shortdesc>
<mode otherprops="DEBUG"/>
<mapref></mapref>
<languages>
<language xml:lang="en-US"/>
</languages>
<rootcontext></rootcontext>
<ditaval/>
<properties id="id"></properties>
<notify/>
</globals>
<outputtypes>
<outputtype id="id" type="" status="ENABLED">
<description></description>
</outputtype>
</outputtypes>
</build-manifest>
Note: When you create a Build Manifest, the
xml:lang
attribute of the Build
Manifest object will be set to the xml:lang
attribute of the
template. Note that the language of the Build Manifest object is not related to the
languages for the Build Manifest output. The output languages are specified in the
<languages>
element.To create a Build Manifest template: