You can use the editAsset command to 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.
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 wsadmin commands as described in this topic, or by using the administrative console as described in Updating bundle versions in the current environment.
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.
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, 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.