Importing a deployment manifest using the importDeploymentManifest command

You can use this command to import a suitable 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.

Before you begin

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.

You can import a deployment manifest by using the wsadmin commands, as described in this topic, or by using administrative console, as described in Importing a deployment manifest.

About this task

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. You can import a deployment manifest to an EBA asset, and overwrite the current deployment manifest.

For more information about why you might want to import a deployment manifest to an EBA asset, see Maintaining bundle versions for an EBA asset.

Procedure

  1. Start the wsadmin scripting client if it is not already running.
  2. Use the importDeploymentManifest command. For example:
    AdminTask.importDeploymentManifest('[-asset 
    com.ibm.ws.eba.example.blabber.app.eba -file /test/temp/DEPLOYMENT.MF]')
    The deployment manifest is checked to ensure that the bundles that it lists can be resolved.
  3. Save your changes to the master configuration.
    To save your configuration changes, enter the following command:
    AdminConfig.save()
    The deployment manifest is imported into the EBA asset and any new bundles that are required to provision the application are downloaded. The file name changes to DEPLOYMENT.MF.
  4. Optional: The business-level application that uses this asset picks up the changes the next time it is restarted. To pick up the changes as soon as possible, wait until bundle downloading is complete for the asset then restart the business-level application.

Icon that indicates the topic type Task topic

Terms and conditions for information centers | Feedback


Timestamp icon Last updated: Saturday, 20 October 2012
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v700osgijpa&product=was-nd-mp&topic=ta_depmf_import_wsadmin

Copyright IBM Corporation 2009, 2012.
This information center is powered by Eclipse technology. (http://www.eclipse.org)