Internal bundle repository [Settings]

The internal bundle repository can store bundles that are referenced by OSGi applications running in WebSphere® Application Server. This panel records the details of a bundle that is installed in the internal bundle repository. The provisioner can then retrieve the bundle when it is included by reference in any of your OSGi applications. You can store bundles and composite bundles in the internal repository. If the bundle is a composite bundle, extra fields are visible.

To view this panel in the administrative console, click the following path:

Environment > OSGi bundle repositories > Internal bundle repository > bundle_name

When you import an enterprise bundle archive (EBA) file as an asset, or update an asset to use new bundle versions, or add a composite bundle as an extension to a composition unit, provisioning ensures that all the required OSGi bundles are available. An OSGi application can use bundles from external repositories, bundles from the internal repository, and bundles that are included in an EBA file or a composite bundle archive (CBA) file. If your bundle includes Blueprint XML files that specify service or reference elements, and the bundle is included in an EBA asset or installed in the internal bundle repository, then these elements are respected during provisioning and appropriate services are provisioned when needed. For more information, see Provisioning for OSGi applications.

Composite bundles can either be included directly in your applications, or provisioned from the internal bundle repository or from an external repository that can process composite bundles. If you install a composite bundle in a bundle repository, and the composite bundle includes bundles by reference, you must ensure that the referenced bundles are also available in the same repository. If you use the internal bundle repository, and the composite bundle directly contains bundles, the contained bundles are not listed separately and are only available as part of the composite bundle.

Configuration tab

The Configuration tab shows configuration properties for this object. These property values are preserved even if the runtime environment is stopped then restarted. See the information center task descriptions for information about how to apply configuration changes to the runtime environment.

The Configuration tab shows the following properties:

Bundle symbolic name: The non-localizable name for this bundle.
The bundle symbolic name, together with the bundle version, uniquely identifies a bundle.
Bundle version: The version of this bundle.
The bundle version is in the form n.n.n, for example 1.1.0. The bundle symbolic name, together with the bundle version, uniquely identifies a bundle.
Composite bundle manifest version: The manifest version of the COMPOSITEBUNDLE.MF file.
This field is only displayed if the bundle is a composite bundle. The composite bundle manifest version is in the form n.n.n, for example 1.1.0.
Bundle name: The name for this bundle in a form that users can understand.
This name can contain spaces.
Bundle description: A short description of this bundle.
Composite content: The bundles that are directly contained in this composite bundle.
This field is only displayed if the bundle is a composite bundle.
Imported packages: The imported packages for this bundle.
Exported packages: The exported packages for this bundle.
Imported services: Services that are imported by this composite bundle.
This field is only displayed if the bundle is a composite bundle.
Exported services: Services that are exported by this composite bundle.
This field is only displayed if the bundle is a composite bundle.
Required bundles: The list of other bundles that are required by this bundle.
This bundle is bound to all the exports of each required bundle, regardless of what those exports are.