Administer OSGi applications

Configure an enterprise bundle archive (EBA) asset, and maintain the bundle versions used by the EBA asset. Administer bundles, composite bundles, composite bundle extensions, and bundle repositories.

This topic assumes that we have already packaged your OSGi application as an enterprise bundle archive (EBA) file, and imported it into WebSphere Application Server, as described in Developing an OSGi application. We might also have added one or more composite bundle extensions to the deployed application.

Subtopics

• 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.
• Maintaining an OSGi composition unit
  Whenever an enterprise bundle archive (EBA) asset is updated, we can (optionally) update the associated composition unit. We might also update a composition unit to add or remove a composite bundle extension. If any updates need configuration changes, we can also modify the configuration information for the composition unit.
• Checking the bundle download status of an EBA asset
  Updating an asset to use a new bundle version might require bundle downloads. We cannot update an asset until bundle downloads are complete from any previous update. Before we try and update bundle versions, we can check the bundle download status of the asset.
• Checking the update status of an OSGi composition unit
  When we change the versions of bundles or composite bundles an enterprise OSGi application uses, or add or remove a composite bundle extension, the bundles used by the deployed application can get out of synchronization with those bundles available. To check that your business-level application is running the most recent version of the EBA asset and any composite bundle extensions, you check the update status of the associated OSGi composition unit.
• Administer bundle repositories
  OSGi applications can share many common utility bundles. To simplify maintenance, and reduce the application footprint, the application does not have to include its own copy of each utility bundle. Instead, bundles can be hosted in a bundle repository, from where they are retrieved during deployment. We can administer bundles and composite bundles held in the internal bundle repository of the product, and also add links to external bundle repositories.
• Export and importing a deployment manifest file
  We can export the deployment manifest file from an application, then import the manifest file into another instance of the same application located somewhere else. This process is useful when an application moves from one environment to another, for example from a test environment to a production environment.

Related:

Enterprise bundle archives

OSGi applications

File name: was2971.html

prettyPrint();