Updating bundle versions in the current environment

You can configure each bundle in an enterprise bundle archive (EBA) asset to use a specific bundle version, or to pull in the latest available version that is compatible with your selections for other bundles. This process updates the EBA asset in the current environment.

Before you begin

If the asset has previously been updated, the bundle downloads for the previous update must have completed, and the business-level application must have picked up the previous updates by being restarted. For more information, see Checking the bundle download status of an EBA asset.

You can update bundle versions by using the administrative console as described in this topic, or by using wsadmin commands as described in Updating bundle versions using the editAsset command.

You can also update bundle versions by exporting, manually modifying, and re-importing the deployment manifest file as described in Maintaining bundle versions for an EBA asset.

About this task

For each bundle deployed in your EBA asset you can select either of the following options:
  • 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. Some bundle updates might be contained in your application, whereas other might need to be downloaded from a bundle repository.

When an EBA asset is updated, the update does not immediately affect the running business-level application that contains the associated EBA composition unit. When the business-level application is next restarted, the deployed content of the EBA composition unit is updated to reflect the updated configuration of the underlying asset. Because it can take time to download new bundle versions, you must wait until the bundle downloads for the asset are complete before you restart the business-level application. If you restart a business-level application before the bundle downloads are complete, the business-level application uses the previous configuration.

You cannot update bundles that are provisioned by the runtime environment, that is, that are listed in the Provision-Bundle header in the deployment manifest.

Procedure

  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 in this asset.

    The current bundle download status for all bundles in 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 have completed, and the business-level application has picked up the previous updates by being restarted, then the option to update bundle versions is displayed 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 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, you can select the update preference for each bundle from a list. You can choose either of the following options:
    • Choose a specific available bundle version. For example, "1.0.0".
    • Choose "No preference". If you select this option, the latest available version that is compatible with your other bundle selections is used.
  6. Click Preview. A version of the 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 versions resolved successfully and can be committed." Otherwise, the message displayed is "The selected versions could not be resolved, so they cannot be committed."
  7. Optional: If the changes are not all resolved successfully resolved, 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 you have selected a working configuration, click Commit. The bundle version updates for the asset are applied.
  9. Optional: The business-level application that uses this asset picks up the changes the next time it is restarted. To pick up the changes as soon as possible, wait until bundle downloading is complete for the asset then restart the business-level application.

Icon that indicates the topic type Task topic

Terms and conditions for information centers | Feedback


Timestamp icon Last updated: Saturday, 20 October 2012
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v700osgijpa&product=was-nd-mp&topic=ta_admin_maint_bundle_ver_console

Copyright IBM Corporation 2009, 2012.
This information center is powered by Eclipse technology. (http://www.eclipse.org)