Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer OSGi applications > Export and importing a deployment manifest file > Export a deployment manifest
Export a deployment manifest using the exportDeploymentManifest command
We can use this command to 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.
Before you begin
We can export a deployment manifest by using wsadmin commands, as described in this topic, or by using the administrative console, as described in Export a deployment manifest.
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
- Start the wsadmin scripting client if it is not already running.
- Use the
exportDeploymentManifest command. For example:
AdminTask.exportDeploymentManifest('[-asset com.ibm.ws.eba.example.blabber.app.eba -path /test/temp/]')
Results
The current deployment manifest for the application is exported.
What to do next
The deployment manifest is available to import into an EBA asset. See Import a deployment manifest using the importDeploymentManifest command.
Subtopics
- exportDeploymentManifest command
Use the exportDeploymentManifest command to export the current deployment manifest, the DEPLOYMENT.MF 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.
Parent topic: Export a deployment manifest
Related concepts:
About OSGi Applications
Enterprise bundle archives
Related tasks:
Secure OSGi Applications
Deploy an OSGi application as a business-level application
Related reference:
OSGi Applications: Troubleshooting tips
OSGi deployment manifest file
Task topic
Feedback
Copyright IBM Corporation 2009, 2011. All Rights Reserved.
This information center is powered by Eclipse technology.