Export and importing a deployment manifest file
We can export the deployment manifest file from an application, then import the manifest file into another instance of the same application located somewhere else. This process is useful when an application moves from one environment to another, for example from a test environment to a production environment.
A deployment manifest file, META-INF/DEPLOYMENT.MF, is created automatically when we import an EBA asset. The deployment manifest file lists, at specific versions, all the bundles and composite bundles that make up the application, including bundles that are determined following dependency analysis. The manifest file is used to ensure that each time an application server starts, the bundles that make up the application are the same.
We can export the current deployment manifest from an EBA asset, then import the deployment manifest into another asset containing the same application. The target asset then uses the imported manifest instead of the generated manifest. This is useful during application development, when an application is fully tested and moves to a production environment. By importing the deployment manifest from the test environment, you ensure that the bundles and their versions that make up the application in the production environment are exactly the same as the bundles that make up the application in the test environment.
- Do not edit an exported manifest file. Use the export and import options only in situations where we can treat the exported file as a "black box".
- If we deploy an application and subsequently extend it by adding one or more composite bundles, information about the composite bundles is not included in the exported deployment manifest file.
Tasks
- Export the deployment manifest file from an EBA asset.
We might want to do this to save the information, or to import it into another identical application.
- Import the deployment manifest file to an EBA asset.
When we import the file, the bundles are resolved. If the bundles cannot be resolved, the import does not complete and an exception message is generated.
Subtopics
- Export a deployment manifest
We can export the current deployment manifest file from an enterprise bundle archive (EBA) asset. We might want to do this to save the information, or to import it into another identical application.- Import a deployment manifest
We can import a suitable deployment manifest to an enterprise bundle archive (EBA) asset. When we import the file, the bundles are resolved. If the bundles cannot be resolved, the import does not complete and an exception message is generated.
Update bundle versions for an EBA asset Maintaining an OSGi composition unit Checking the bundle download status of an EBA asset Checking the update status of an OSGi composition unit Administer bundle repositories Add or removing extensions for an OSGi composition unit
File name: was2974.html
prettyPrint();