Output a Build Manifest

To output a Build Manifest, you use the Build Manifest output generator type.

Note: You must release the Build Manifest to get the most recent content.

This procedure describes how to output a Build Manifest using the Generate Output command in the DITA CMS Eclipse Client. You can also use the NightBuild script to generate the output. For more information, contact IXIASOFT Support.

Output a Build Manifest in multiple languages

When you output a Build Manifest in multiple languages, the localized content must be in the Localization:done state (or the equivalent in your deployment), otherwise the output will not be generated for this language. This ensures that only final localized content is output (as opposed to content that is partially translated).

Configure the Auto-save option

Generating a Build Manifest can take a long time, depending on the size of your maps and the number of output types/languages configured. Therefore, IXIASOFT recommends that you configure an output directory and select the Auto-Save option so that the Build Manifest outputs are saved automatically when the operation is completed. See Configure import and export directories for more information.

To output a build manifest in the DITA CMS Eclipse Client:

  1. Right-click the Build Manifest to output and select Generate Output.
    The Generate Output window is displayed.
  2. Select the BuildManifest output type and click Create.
The outputs are generated for this map.
Note: This operation may take hours, depending on the number of output type/languages and map sizes.

When the output is completed, it is saved in a file called:

<build_manifest_title>.BuildManifest.<authoring_language>.zip

For example:

DITA_CMS_User_Guide-Build_Manifest.BuildManifest.English.zip
The zip file includes the following:
  • The Build Manifest file in XML format (for example, mte1425048934103.bmanifest)
  • A log file for the output operation (for example, mte1425048934103.build.html)
  • Directories for all the output types, as follows:
<output_type_1>
     authoring  --> Contains output 1 for the source language
     localization
          <language1> --> Contains the output for the localized language 1
          ...
          <languagex> --> Contains the output for the localized language x
...
<output_type_x>
     authoring  --> Contains output X for the source language
     localization
          <language1> --> Contains the output for the localized language 1
          ...
          <languagex> --> Contains the output for the localized language x

For example, the 18 outputs for the DITA CMS User Guide might be packaged as follows:

Sample Directory Structure