Generating the manifest.yml file

To push an application created in TIBCO BusinessWorks™ Container Edition or TIBCO Cloud™ Integration to Pivotal Platform the application manifest (manifest.yml) file is required. In TIBCO BusinessWorks Container Edition the manifest.yml file can be created from the Context menu option, Create Manifest YML for an application in the Project Explorer view.

Manifest File Editor

The Application Details tab has the following fields:
Application Details
Field Description
Name The name is auto populated when the manifest file is created. This is an editable field. When you rename the application module, then the name is updated in the Manifest.yml.
Memory The memory field, to specify the memory limit for all instances of an app, is auto populated when file is created. The default value is 512M.

This attribute requires a unit of measurement: M , MB , G , or GB , either in uppercase or in lowercase followed by the numeric value

Timeout The timeout field is auto populated with default value as 60. Only numeric values are allowed for timeout.
Build Pack The build pack name needs to be specified by the user. By default, it is empty.

Environment Variables

To select environment variables, click the variable chooser button on the right hand side of the table. Environment variables can still be used if there are no default environment variables listed.

Services

The services can be selected from the chooser feature. The services that are present in Pivotal Platform environment is displayed in the chooser. The Add button is also used to define the services. Specify the service name once a new service is added.

Note: The files can be edited from the source view. If there is an error while editing the file in the source view, the simplified editor will become read-only until the error is resolved in the source view.

Exporting the EAR file

The Manifest.yml file is exported when you create an EAR file using the Create Enterprise Archive option. The Manifest.yml file is copied to the same directory as the EAR file and it will not be present in the Jar file inside the EAR file. If a Manifest.yml file already exists in that directory, then it is overwritten. The EAR path attribute is updated automatically in the exported manifest.yml file.

Exporting the EAR using bwdesign CLI

The Manifest.yml file can also be exported through bwdesign CLI using the export command, in the manner similar to the Create Enterprise Archive command on the Tibco BusinessWorks Studio GUI.