+

Search Tips   |   Advanced Search

Update bundle versions for an EBA asset

After we import your OSGi application as an asset, newer versions of the bundles or composite bundles that the asset uses might become available. We can configure the deployed asset to use an updated version of any bundle or composite bundle used by the asset. We can choose to use a specific bundle version, or to pull in the latest compatible version.

We can update bundle and composite bundle versions for an EBA asset using the administrative console as described in this topic, or using wsadmin commands as described in Update bundle versions for an EBA asset using the editAsset command.

When we 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 we import the application as an asset, we can no longer change the direct contents of the asset. To update bundles and composite bundles specified in an asset, we 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.

For each bundle or composite bundle specified by your EBA asset we can select either of the following options:

After we make your selections for this asset, the system tries to resolve the changes we have requested, and shows you the results. When we have selected a working configuration, we can commit your selections and the bundle version updates for the asset are applied.

We cannot update bundles that are provisioned by the runtime environment.

When an EBA asset is updated, the update does not automatically affect the running business-level application. To update the running application, you update the composition unit of the business-level application containing the asset.

For users who are moving from a previous version: In the WebSphere Application Server v7 Feature Pack for OSGi Applications and Java Persistence API 2.0, bundle changes to the asset are applied by restarting the business-level application, rather than by updating the composition unit. The current approach means that many bundle changes can be applied in place, without restarting the running business-level application.


Tasks

  1. Start the administrative console.

  2. Navigate to Applications > Application Types > Assets > asset_name.

    The Asset settings panel is displayed.

  3. Check the current bundle download status for all bundles and composite bundles for this asset.

    If the asset has previously been updated, the bundle downloads for the previous update must have completed.

    The current bundle download status for all bundles and composite bundles for this asset is displayed in the EBA Dependencies section. This status is either "Bundles downloading...", "Bundle downloads are complete", or "No bundles downloads are required".

    If the bundle downloads for any previous update are complete, the option to update bundle versions is available under the Additional Properties section.

  4. Click [Additional Properties] Update bundle versions in this application. The Update bundle versions in this application [Settings] panel is displayed. This panel contains a tabular overview of the bundles and composite bundles currently deployed in the asset. Application bundles are listed separately from use bundles.

  5. Choose the update bundle version preference for each bundle in this application.

    In the table, we can select the update preference for each bundle from a list. We can choose either of the following options:

    • Choose a specific available bundle version. For example, "1.0.0".

    • Choose "No preference". If we select this option, the latest available version that is compatible with your other bundle selections is used.

  6. Click Preview. A similar table is displayed in the Preview bundle versions update [Settings] panel, showing the result of the proposed changes to the bundle versions in this application. If the changes resolve successfully, the following message is displayed: "The selected bundle versions can be resolved, so we can now create a new deployment with the proposed bundle versions. The new deployment will not affect any composition units for this asset until the composition units are updated to use the new deployment." Otherwise, the message displayed is "The selected versions cannot be resolved, so we cannot create a new deployment with the proposed bundle versions."

  7. Optional: If the changes are not all resolved successfully, click Cancel to return to the Update bundle versions in this application [Settings] panel, then select a different update preference for each bundle that could not be resolved.

  8. When we have selected a working configuration, click Create. The bundle and composite bundle version updates for the asset are applied.

  9. Save changes to the master configuration. The bundle updates are downloaded.


What to do next

If we 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.


Subtopics


Related:

  • Enterprise bundle archives
  • Enterprise bundle archive update
  • Application bundles, use bundles and provision bundles
  • Provisioning for OSGi applications
  • OSGi bundles and bundle archives
  • Bundle and package versioning
  • Maintaining an OSGi composition unit
  • Checking the bundle download status of an EBA asset
  • Checking the update status of an OSGi composition unit
  • Administer bundle repositories
  • Exporting and importing a deployment manifest file
  • Update an OSGi composition unit
  • Add an EBA asset to a composition unit by
  • Add an EBA asset to a composition unit using wsadmin commands
  • Preview bundle versions update [Settings]
  • Update bundle versions in this application [Settings]




    File name: was2973.html

    prettyPrint();