Exporting a deployment manifest using the exportDeploymentManifest command
You 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
You can export a deployment manifest by using wsadmin commands, as described in this topic, or by using the administrative console, as described in Exporting 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.
You 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. Use the export and import options only in situations where you can treat the exported file as a black
box
.