Updating bundle versions for an EBA asset
After you import your OSGi application as an asset, newer versions of the bundles or composite bundles that the asset uses might become available. You can configure the deployed asset to use an updated version of any bundle or composite bundle that is used by the asset. You can choose to use a specific bundle version, or to pull in the latest compatible version.
Before you begin
You can update bundle and composite bundle versions for an EBA asset by using the administrative console as described in this topic, or by using wsadmin commands as described in Updating bundle versions for an EBA asset using the editAsset command.
About this task
When you first create an OSGi application, each bundle and composite bundle in the application is either directly contained in the EBA file or pulled in by reference. After you import your application as an asset, you can no longer change the direct contents of the asset. To update bundles and composite bundles that are specified in an asset, you add the updated versions to a repository then apply the updates to the asset. The asset is not updated automatically when new bundle versions become available; it is up to you to decide if and when to update the asset.
- Use a specific available bundle version.
- Use any version. In this case, the latest available version that is compatible with your selections for other bundles is used.
After you make your selections for this asset, the system tries to resolve the changes you have requested, and shows you the results. When you have selected a working configuration, you can commit your selections and the bundle version updates for the asset are applied.
You cannot update bundles that are provisioned by the runtime environment.
Procedure
What to do next
If you plan to update the composition unit at this time, check that all bundle downloads are complete. See Checking the update status of an OSGi composition unit.