Network Deployment (Distributed operating systems), v8.0 > Reference > Sets > OSGi Applications administrative console panels
Import a deployment manifest into this application [Settings]
We can export the deployment manifest file from an application, then import the manifest file into another instance of the same application located somewhere else. This process is useful when an application moves from one environment to another, for example from a test environment to a production environment. 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 view this panel in the administrative console, click the following path:
Applications > Application Types > Assets > asset_name > [Additional Properties] Import a deployment manifest into this application
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.
We 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. Only use the export and import options in situations where you can treat the exported file as a "black box".
The file to import must be a valid deployment manifest file, using the naming format file_name.MF, for example DEPLOYMENT_TEST.MF. When you import the deployment manifest into the EBA asset, the file is renamed to DEPLOYMENT.MF. At this time, any new bundles that are required to provision the application are downloaded.
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
Check the bundle download status of an EBA asset.
Path to deployment manifest
Fully qualified path to the deployment manifest file to import. The file must be a valid deployment manifest, with a .MF file extension.
Select Local file system when the browser and the deployment manifest are on the same machine, whether or not the server is also on that machine.
Select Remote file system when the deployment manifest is on any node in the current cell context, or if the deployment manifest file is already on the machine that runs the application server.
Parent topic: OSGi Applications administrative console panels
Related concepts:
Enterprise bundle archives
Related tasks:
Import a deployment manifest
Related information:
Administrative console buttons
Administrative console preferences
Reference topic
Feedback
Copyright IBM Corporation 2009, 2011. All Rights Reserved.
This information center is powered by Eclipse technology.