MANIFEST file

A MANIFEST file provides information about the applications and services packaged in a Genero Archive (gar) file. It must be included in the Genero Archive file.

Depending on your requirements, here are some options to consider.

  • If you need to package a limited number of applications and services, you can run the fglgar tool with the gar command, and specify the --application option for each application to include and the --service option for each service to include. This creates a Genero Archive (.gar) file that includes a autogenerated MANIFEST file.
  • If you have many applications and services to package, you may find it easier to create the MANIFEST by hand. The fglgar tool checks if a MANIFEST file is present in the archive directory and uses it to create the Genero Archive.
    Important:

    Do not use fglgar command options that provide for the generation of a MANIFEST (such as --application and --service options) when a MANIFEST already exists; errors will be raised.

    Note:

    For more information on using fglgar, see the fglgar topic in the Genero Business Development Language User Guide.

Syntax

A MANIFEST file is an XML file. It has a MANIFEST element at its root. 
<MANIFEST>
   <DESCRIPTION></DESCRIPTION>
   [<TRIGGERS>...</TRIGGERS>]
   [<RESOURCES></RESOURCES>]
   [<APPLICATION></APPLICATION>] [...]
   [<SERVICE></SERVICE>] [...]
</MANIFEST>

Child elements

Important:

Element order. If child elements are present, they must be set in the order listed or as shown.

Child elements can include the following:

MANIFEST file

<MANIFEST>
  <DESCRIPTION>This archive contains one app and one service</DESCRIPTION>
  <TRIGGERS component='comp_name'>
    <DEPLOY>deploy.sh</DEPLOY>
    <UNDEPLOY>undeploy.sh</UNDEPLOY>
  </TRIGGERS>
  <RESOURCES>res_dir</RESOURCES>
  <APPLICATION xcf='app.xcf'></APPLICATION>
  <SERVICE xcf='webserviceApp.xcf'></SERVICE>
</MANIFEST>