Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer OSGi applications
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.
About this task
A deployment manifest file, META-INF/DEPLOYMENT.MF, is created automatically when you 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 that contains 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. Only use the export and import options in situations where you can treat the exported file as a "black box".
Procedure
- Export the deployment manifest file from an EBA asset.
You 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 you 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. You 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 you import the file, the bundles are resolved. If the bundles cannot be resolved, the import does not complete and an exception message is generated.
Parent topic: Administer OSGi Applications
Related concepts:
About OSGi Applications
Related tasks:
Update bundle versions for an EBA asset
Maintain an OSGi composition unit
Check the bundle download status of an EBA asset
Check the update status of an OSGi composition unit
Administer bundle repositories
Secure OSGi Applications
Related reference:
OSGi Applications: Troubleshooting tips
Task topic
Feedback
Copyright IBM Corporation 2009, 2011. All Rights Reserved.
This information center is powered by Eclipse technology.