importDeploymentManifest command

Use the importDeploymentManifest command to import a deployment manifest to an enterprise bundle archive (EBA) asset. When you import the file, the bundles are resolved. If the bundles cannot be resolved, the import does not complete and an exception message is generated.

To run the command, use the AdminTask object of the wsadmin scripting client.

Command-line help is provided:
  • For a list of the available OSGi Applications commands in Jython and a brief description of each command, enter the following command at the wsadmin prompt:

    print AdminTask.help('OSGiApplicationCommands')

  • For overview help on a given command, enter the following command at the wsadmin prompt:

    print AdminTask.help('command_name')

After using the command, save your changes to the configuration repository 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.
  • The bundles and their versions that are listed in the deployment manifest must be available, either within the EBA file or from a bundle repository.
  • If the asset has previously been updated, the bundle downloads for the previous update must have completed. 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.

Target object

None.

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.

Optional parameters

None.

Example

AdminTask.importDeploymentManifest('[-asset 
com.ibm.ws.eba.example.blabber.app.eba -file /test/temp/DEPLOYMENT.MF]')