Create a Build Manifest template
IXIASOFT CCMS includes a basic Build Manifest template, but you can create a new one for your deployment.
You create templates to predefine information that will be common to all Build Manifest objects created from this template.
Some use cases include:
- Setting default user parameters in your template so that your users do not have to enter them manually every time. For example, the PDF transformation scenario at IXIASOFT requires three user parameters. We could create a template that presets these parameters.
- Setting default output types per product. For example, ProductA's documentation could be generated in three formats (PDF, xHTML, and Eclipse help), but ProductB's documentation is created in PDF and xHTML. You could create one template per product with the appropriate output types already defined.
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 language(s) in which
the Build Manifest is output. The output languages are specified in the <languages>
element.Note: You should make these configuration changes in the Test environment and test them before copying them to the Production environment. In a dedicated SaaS deployment, after testing the changes, ask IXIASOFT Customer Support to copy the changes to the Production environment.