You can use these administrative console panels to manage
your OSGi applications.
Subtopics
Bind Blueprint resource references [Settings] Blueprint components can access WebSphere® Application Server resource references.Each reference is declared in a Blueprint XML file, and can be secured using a Java™ Platform, Enterprise Edition (Java EE) Connector Architecture (JCA) authentication alias.Each bundle in an OSGi application can contain any number of resource reference declarations in its various Blueprint XML files.
External bundle repositories [Collection] The external bundle repositories are bundle repositories that are available outside of WebSphere Application Server. If your OSGi applications reference bundles that are stored in an external bundle repository, you must configure a link (name and URL) to the repository so that the provisioner can retrieve the bundles when required. When an OSGi application is imported as an asset, the provisioner attempts to satisfy all its dependencies by using the contents of the asset, the contents of the internal bundle repository, and the contents of any available external bundle repositories.
External bundle repositories [Settings] The external bundle repositories are bundle repositories that are available outside of WebSphere Application Server. If your OSGi applications reference bundles that are stored in an external bundle repository, you must configure a link (name and URL) to the repository so that the provisioner can retrieve the bundles when required. When an OSGi application is imported as an asset, the provisioner attempts to satisfy all its dependencies by using the contents of the asset, the contents of the internal bundle repository, and the contents of any available external bundle repositories.
Internal bundle repository [Collection] The internal bundle repository can store bundles that are referenced by OSGi applications running in WebSphere Application Server. When an OSGi application is imported as an asset, the provisioner attempts to satisfy all its dependencies by using the contents of the asset, the contents of the internal bundle repository, and the contents of any available external bundle repositories.
Internal bundle repository [Settings] The internal bundle repository can store bundles that are referenced by OSGi applications running in WebSphere Application Server. When an OSGi application is imported as an asset, the provisioner attempts to satisfy all its dependencies by using the contents of the asset, the contents of the internal bundle repository, and the contents of any available external bundle repositories.
Update bundle versions in this application [Settings] Update the versions of the bundles that comprise this application.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.
Upload bundle [Settings] Upload a bundle into the internal bundle repository. You
can add a bundle or composite bundle to the internal
bundle repository.
Virtual hosts for web application bundles [Settings] Each WAB that is contained in a deployed asset must be mapped to a virtual host. WABs can be installed on the same virtual host, or dispersed among several virtual hosts.
Web module resource references [Settings] For each reference, specify the JNDI name under which the resource is known in the runtime environment. Optionally, set authentication properties and extended data source custom properties, which affect how the resource is accessed at run time.