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.

Using the CCMS Desktop, create a Build Manifest with the content that will be common to all Build Manifest objects based on this template.
Open the Build Manifest.
From within the TEXTML Administration perspective, select File > Export from the menu.
The Select window appears:
Figure: Exporting a Build Manifest
Select General > File System and click Next.
In the File system dialog box, browse to your desktop and click Finish.
The file is saved and given a system name and the suffix .bmanifest.
Rename the file as appropriate (for example, ProductATemplate.bmanifest).
Open the TEXTML Administration perspective by clicking the TEXTML Administration shortcut on the tool bar. If the shortcut is not displayed, follow these steps:
1. Select Window > Perspective > Open Perspective > Other
2. Click TEXTML Administration.
3. Click Open.
In the TEXTML Administration view, double-click the server. If your server is not displayed in the view, you must add it to the view.
When the Connect as dialog opens, type your username and password and click OK.
Double-click the name of your Content Store to open a connection to it.
Navigate to /system/templates/bmanifests.
Right-click the bmanifests collection and select Insert Documents.
The Insert Documents Dialog appears.
Click Add File and browse to your desktop.
1. Select the file.
2. Click Open.
The file path and name appear under Import As.
Click OK.
The file is imported into the /templates/bmanifests collection.
Inform users of the changes.
The changes will be applied automatically once users close and then reopen their IXIASOFT CCMS Desktop. Users can also apply the changes without restarting their CCMS Desktop by clicking IXIASOFT CCMS > Synchronize Configuration.