You can 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 make it available for manual update before re-importing it.
You can export a deployment manifest by using the administrative console as described in this topic, or by using wsadmin commands, as described in Exporting a deployment manifest using the exportDeploymentManifest command.
A deployment manifest file is created automatically for an OSGi application when you install an EBA asset. The deployment manifest file lists all the bundles, at specific versions, that make up an 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. To save this information, or to make it available for manual update, you export the current deployment manifest for the EBA asset.
For more information about why you might want to export the deployment manifest from an EBA asset, see Maintaining bundle versions for an EBA asset.