OSGi applications in enterprise bundle archive (EBA) files
are installed using the business-level application framework.
Installation is a three step process:
- Import the EBA file as an EBA asset.
- Create a new business-level application.
The first two steps
can be in either order.
- Add the asset to the business-level application. The application
is configured and associated with the server that it will run on.
During installation, if the EBA file does not contain a deployment
manifest, a deployment manifest is generated. If the EBA file contains
a deployment manifest, it is checked against the application manifest,
and installation continues if the information in the manifests match.
The following information is checked:
- The Application-SymbolicName and Application-Version in the deployment
manifest must match the corresponding entries in the application manifest.
- The list of bundles in the Deployed-Content header in the deployment
manifest must be the same as the list of bundles in the Application-Content
header in the application manifest.
- The version of each bundle that is listed in the Deployed-Content
header in the deployment manifest must be within the version range
for the corresponding bundle that is listed in the Application-Content
header in the application manifest.
- All bundles that are listed in the Deployed-Use-Bundle header
in the deployment manifest must be in the list of bundles in the Use-Bundle
header in the application manifest. (The Use-Bundle header can list
more bundles than the Deployed-Use-Bundle header).
- The version of each bundle that is listed in the Deployed-Use-Bundle
header in the deployment manifest must be within the version range
for the corresponding bundle that is listed in the Use-Bundle header
in the application manifest.