Use the importDeploymentManifest command
to import a deployment manifest to an enterprise bundle archive (EBA)
asset. If you have changed the bundle versions that are specified in the manifest, the import process checks that the bundles can be resolved, then updates the asset with the new manifest and any bundle downloads that are required.
To run the command, use the AdminTask
object of the wsadmin scripting client.
Command-line help is provided for OSGi Applications commands:
After using the command, save your changes to the
master configuration by using the following command:
AdminConfig.save()
Purpose
This command imports a deployment
manifest to an EBA asset.
For the import to succeed, the following conditions must be met:- The deployment manifest to import must correspond with the application manifest of the OSGi application that is contained in the EBA asset. For more information, see the section "Importing or exporting a deployment manifest" in Enterprise bundle archives.
- The bundles and their versions that are listed in the deployment manifest must be available to be resolved.
- If the asset has previously been updated, the bundle downloads for the previous update must have completed, and the business-level application must have picked up the previous updates by being restarted. For
more information, see Checking the bundle download status of an EBA asset.
When the deployment manifest is successfully imported to the
EBA asset, its file name changes to
DEPLOYMENT.MF,
and any new bundles that are required to provision the application
are downloaded.
Required parameters
- -asset
- The name of the EBA asset to import the deployment manifest into.
This must be an installed EBA asset.
- -file
- The fully qualified file path for the location of the deployment
manifest to import.
Conditional parameters
None.
Example
AdminTask.importDeploymentManifest('[-asset
com.ibm.ws.eba.example.blabber.app.eba -file /test/temp/DEPLOYMENT.MF]')