You 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:
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.
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.
Specifies the fully qualified path to the deployment manifest file that you want 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.