A Build Manifest enables you to generate multiple types of outputs in multiple
languages, with multiple ditavals and build parameters, in one step.
Steps
In a view that lists the map for which you want to create the Build Manifest,
right-click the map and select Create Build
Manifest.
The Create Build Manifest window is displayed:
The following table describes the fields in the Build Manifest
window:
Table 1. Build Manifest window
Field
Description
Id
Id of the Build Manifest object. This field is generated
automatically and cannot be modified.
Title
Name of the Build Manifest.
Description
Description of the Build Manifest object. The description
will be added to the <shortdesc>
element of the object.
Mode
A flag that determines if the Build Manifest can be used
in IXIA CCMS Web, or if the
NightBuild script can generate output from the Build
Manifest.
For example, if the NightBuild script runs every night to
generate the output for the maps in your Content Store,
you can write a query that uses this field to determine
whether to generate an output from this Build
Manifest.
You can choose any of the following values:
Mode=Production: The NightBuild script
generates output for the Build Manifests that are in
Production mode. However, users cannot see these
Build Manifests when generating an output in
IXIA CCMS Web.
Mode=Manual: Users can select these Build
Manifests when generating an output in IXIA CCMS Web. However, the NightBuild
script does not run on these Build Manifests.
Mode=Both: Users can select these Build
Manifests when generating an output in IXIA CCMS Web, and the NightBuild
script generates output for these Build Manifests.
Mode=Debug: The NightBuild script does not
run on these Build Manifests, and users cannot see
them when generating an output in CCMS Web. This lets you debug
your Build Manifest using the interface without
impacting the night build or users.
Notify
Email address of the person to notify when the build is
completed. This does not have to be a user.
You can enter multiple addresses, separated by either a
space or a comma. The addresses can take any of the
following forms:
address@xyz.com
name <address@xyz.com>
<address@xyz.com> name
(name) address@xyz.com
address@xyz.com (name)
Note: For this feature, you must configure the notification
message as well as the SMTP information in the Output
Generator. See Configure Build Manifest
notifications in Installation &
Upgrade or Output Generator &
Scheduler documentation for more
information.
Mapref
ID of the map to generate.
Language
List of default languages into which to generate the
outputs.
Template
Template to use to create this Build Manifest object.
A template has any number of predefined outputs and
other parameters. Users can use a template to reduce the
amount of work required to configure a build
manifest.
Enter the fields as appropriate for your Build Manifest.
For example, the following diagram shows the window for a User Guide:
If you want users to be able to use this Build Manifest in
IXIA CCMS Web, select Manual or Both.
To open the Build Manifest after you created it and configure
the default values and output types, select Open
build manifest in default editor.
Click Create.
The Build Manifest object is created. If you selected
the Open build manifest in default
editor, the Build Manifest object is opened in the editor, as shown
below, and the values you entered in the Create Build Manifest window are
displayed:The Build Manifest window has the following tabs:
Default values:
Specifies general information about the Build Manifest. It also lets you
configure default values for ditaval files, languages, and user
parameters. The default values are used for all the output types defined
in the Build Manifest, unless you override them for a specific output
type.
Outputs:
Specifies the different types of output into which to transform the
source map. You can override the default ditaval, language, and user
parameter values for an output type in this tab.
XML Preview:
Provides the XML preview of the Build Manifest object. You cannot modify
the XML source.
Results
The next step is to set default values for ditaval files, languages, and user
parameters.