Deployment manifest files

The deployment manifest, META-INF/DEPLOYMENT.MF, specifies all the bundles that make up the application, including bundles that are required following dependency analysis. The deployment manifest specifies the actual version of each bundle that is used in the application. It is created automatically when an EBA asset is installed and it ensures that each time an application server starts, the bundles that make up the application are the same.

After an application is installed, the version of a bundle can be updated by configuring the EBA asset.

The following code is an example of the contents of a deployment manifest file:
Manifest-Version: 1.0
Deployed-Content: bundle1;deployed-version=1.0.0.qualifier
Application-SymbolicName: bundle.app
Application-Version: 1.0.0.qualifier
Import-Package: javax.servlet.jsp;version="2.0.0",javax.persistence;ve
 rsion="0.0.0",javax.servlet.http;version="2.5.0",javax.servlet;versio
 n="2.5.0",javax.servlet.jsp.el;version="2.0.0",javax.servlet.jsp.tage
 xt;version="2.0.0",javax.el;version="2.0.0"
A deployment manifest contains the following headers:
Manifest-Version
A version number for the manifest format.
Application-SymbolicName
The unique symbolic name of the application, which uses similar package notation to Java™. This symbolic name matches the Application-SymbolicName value in the application manifest.
Application-Version
The version of the application, which uses OSGi syntax for a bundle version. This version matches the Application-Version value in the application manifest.
Deployed-Content

A comma-separated list of the symbolic names of the bundles and the exact versions to be used.

The list includes all the bundles that are listed in the Application-Content header in the application manifest, and bundles that are imported by dependency analysis. Non-OSGi module types are included using the symbolic name of the converted bundle.

The Deployed-Content header has the following directive:
deployed-version
The exact version of the bundle, which is specified by using OSGi syntax for a version.
Deployed-Use-Bundle
A list of bundles or composite bundles that satisfy the package dependencies of bundles in the Deployed-Content list. Each element in the Deployed-Use-Content list must provide at least one package to at least one bundle in the Deployed-Content list. The Deployed-Use-Bundle list is an exact subset of the Use-Bundle list. These bundles are loaded into the shared bundle space at run time. An administrator can update bundles that are mapped into the Deployed-Use-Bundle list from the Use-Bundle list after application deployment.
Provision-Bundle
A list of additional bundles and composite bundles that are required as a result of resolving the OSGi application. Each bundle or composite bundle is loaded into the shared bundle space at run time; however, they might not be required. An administrator cannot update bundles in the Provision-Bundle list after application deployment.
Import-Package
A list of the packages that the bundles in the Deployed-Content list consume from the bundles and composite bundles in the Deployed-Use-Bundle and Provision-Bundle lists. For packages that are consumed from the Deployed-Use-Bundle list, the package import has ;bundle-symbolic-name and ;bundle-version attributes.
Icon that indicates the type of topic Concept topic
Timestamp icon Last updated: July 17, 2017 21:58

File name: cdeploymentmf.html