After you deploy your OSGi application as a business-level application, newer versions of the bundles that the application uses might become available. You can check the bundle download status of an enterprise bundle archive (EBA) asset, and update the asset to pull in newer versions of bundles.
You cannot update an EBA asset until bundle downloads are complete from any previous update, and until the business-level application that uses the asset has picked up the previous updates by being restarted. Before you try to update bundle versions, you can check the bundle download status of the asset.
The bundles that your OSGi application uses are either contained in the asset, or pulled in by reference as shared bundles. Bundles are not updated automatically when new bundle versions become available, they are updated only when you issue explicit update instructions.
You must use an administrative console option, or the equivalent editAsset wsadmin command, to update the bundle versions for you. This process updates the EBA asset in the current environment. When you submit a configuration that resolves successfully, the runtime environment updates the configuration. Some bundle updates might be directly contained in the EBA asset for your application, and others might need to be downloaded, for example from an external bundle repository.
Remember that you specify the configuration information for the EBA asset when you add an EBA asset to a business-level application, and you cannot change it later. Configuration information includes the context roots, virtual hosts, security role mappings, and web module or Blueprint resource bindings for your OSGi application. Therefore, you cannot update an EBA asset and introduce anything that requires additional configuration. For example, if you update a bundle that introduces new resource references, those resource references will not be bound.