Enterprise bundle archive update
After we import an enterprise bundle archive (EBA) file as an asset, newer versions of the OSGi bundles that it uses might become available. To have an OSGi application to use a later version of a bundle, specify this explicitly by configuring the asset.
The application manifest in an EBA file can define a list of application modules, together with a range of versions for each module. In this way, updates from the minimum to the maximum version of a module are allowed.
The deployment manifest, which is created automatically when we import the EBA file as an asset, specifies the exact version of each module, and ensures that each time an application server starts, the bundles that make up the application are the same. When newer versions of the bundles become available, they are not updated automatically, even if they are within the version range specified in the application manifest.
If an OSGi application requires a newer version of a bundle that has been installed into a configured bundle repository, the EBA asset must be explicitly updated to pull in that newer version. Otherwise, the application continues to use the original deployed bundle version.
Use the administrative console to list the bundles that make up the application and see the current versions in use. All the bundles except those that are provisioned by the runtime environment are listed. If later versions of any bundles are available in the configured bundle repositories, these versions are also listed, so we can choose to update to one of the later versions.
We can change the version of one or more bundles, then preview whether the changes resolve successfully. We can update a single bundle, or update the whole application. After you preview the update, we can commit or cancel the changes. If we commit the changes, the deployment manifest of the asset is updated. The changes take effect the next time that the business-level application containing the asset is started.
In a production environment, when we want to ensure that the same versions of bundles used for acceptance test are used in production, we can export the appropriate deployment manifest from the test environment to the production environment. When we do this, the application manifest and the deployment manifest are checked to make sure that they contain matching information.
Related:
Enterprise bundle archive installation Provisioning for OSGi applications Update bundle versions for an EBA asset Update bundle versions for an EBA asset using the editAsset command Preview bundle versions update [Settings] Update bundle versions in this application [Settings]
File name: was325.html
prettyPrint();