OSGi applications administrative console panels

You can use these administrative console panels to manage your OSGi applications.

Add extensions [Collection]
After you import the enterprise bundle archive (EBA) file for your OSGi application as an asset, you can update versions of existing bundles but you cannot add extra bundles to the asset. However, after you have added the asset as a composition unit to a business-level application, you can extend the business-level application by adding one or more composite bundles to the composition unit.
Add extensions [Settings]
View read-only information about a composite bundle in the internal bundle repository that is currently available to be added as an extension to a composition unit.
Application OSGi frameworks [Collection]
This panel lists all the OSGi frameworks that are associated with an application.
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.
Bundle cache [Collection]
The bundle cache is a cell-wide store (or server-wide for single-server systems) of bundles that are referenced by OSGi applications, and that have been downloaded from both internal and external repositories. You can get an up-to-date list of the bundles in the bundle cache, check if all bundles are successfully downloaded, and request that one or more bundles be downloaded again.
Bundle cache [Settings]
The bundle cache is a cell-wide store (or server-wide for single-server systems) of bundles that are referenced by OSGi applications, and that have been downloaded from both internal and external repositories. For a given bundle, you can view the bundle size, the download status, and a list of the assets and composition units that use the bundle. You can also view and refresh the repository URL for the repository that hosts the bundle.
Bundle details [Settings]
This panel shows the details of a bundle, including identification information, the values of headers in the bundle manifest file, and bundle dependencies.
Bundles in OSGi framework [Collection]
This panel lists all the bundles in an OSGi framework.
Context root for web modules [Settings]
Context roots determine where the web pages of a particular web application bundle (WAB) are found at run time.
EJB environment entries [Settings]
For each simple environment entry that is defined in either an env-entry element in an ejb-jar.xml file or in an @Resource annotation in the composition unit, you can specify the value of the environment entry.
EJB JNDI names [Settings]
For each Session enterprise bean in the composition unit, you can specify the JNDI name by which the enterprise bean is known in the runtime environment.
EJB message destination references [Settings]
For each message destination reference and resource environment reference, specify the JNDI name under which the resource is known in the runtime environment.
EJB references [Settings]
For each EJB reference that is defined in either an ejb-jar.xml file, a web.xml file, or an @EJB annotation in the composition unit, you can specify the JNDI name by which the EJB reference is known in the runtime environment.
EJB 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.
Extensions for this composition unit [Collection]
Add composite bundle extensions to, or remove them from, a composition unit that contains an enterprise OSGi application.
Extensions for this composition unit [Settings]
View read-only information about a composite bundle that is currently added as an extension to this composition unit.
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 add a link to the repository to the set of external repositories listed on this panel. The provisioner can then retrieve the bundles when required.
External bundle repositories [Settings]
The external bundle repositories are bundle repositories that are available outside of WebSphere Application Server. Use this panel to configure a link (name and URL) to an external bundle repository. The provisioner can then retrieve from the repository any bundles that are pulled in by reference by your OSGi applications.
Import a deployment manifest into this application [Settings]
You 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. When you import the file, the bundles are resolved. If the bundles cannot be resolved, the import does not complete and an exception message is generated.
Internal bundle repository [Collection]
The internal bundle repository can store bundles that are referenced by OSGi applications running in WebSphere Application Server. You can install single bundles, composite bundles, and grouped-up sets of bundles.
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.
Listeners for message-driven beans [Settings]
For each message-driven bean (MDB) that is defined in either an ejb-jar.xml file or in an @MessageDriven annotation in the composition unit, you can specify the settings necessary to bind an MDB listener to the MDB.
Package details [Settings]
This panel shows the details of a package, including identification information, and the bundles that export and import the package.
Packages in bundle [Collection]
This panel lists all the imported packages and exported packages for an OSGi bundle.
Packages in OSGi framework [Collection]
This panel lists all the packages in an OSGi framework.
Preview bundle versions update [Settings]
A preview of the result of the proposed changes to the bundle versions in this application.
Preview composition unit upgrade [Settings]
A preview of the result of the proposed changes to the bundle versions for this composition unit.
RunAs roles for users [Collection]
You can map a specified user identity and password to a RunAs role. This mapping enables you to specify application-specific privileges for individual users, so that they can run specific tasks using another user identity.
Security role to user or group mapping [Settings]
You can specify the users and groups that are mapped to the security roles used with the OSGi application.
Service details [Settings]
This panel shows the details of a service, including identification information, the service interfaces, the bundles that have registered or that use the service, and the service properties.
Services in bundle [Collection]
This panel lists all the services that are registered, and all the services that are used, by an OSGi bundle.
Services in OSGi framework [Collection]
This panel lists all the services in an OSGi framework.
Update bundle versions in this application [Settings]
Update the versions of the bundles that comprise this application. You can configure the deployed asset to use an updated version of any bundle or composite bundle that is used by the asset. You can choose to use a specific bundle version, or to pull in the latest compatible version.
Upload bundle [Settings]
Upload a bundle into the internal bundle repository. You can upload single bundles, composite bundles, and grouped-up sets of bundles.
Virtual hosts for web modules [Settings]
Each web application bundle (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 message destination references [Settings]
For each reference, specify the JNDI name under which the resource is known in the runtime environment.
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.
Web module resource references: Available resources [Collection]
This panel lists the currently available resources that can be assigned to the resource reference selected on the previous panel.

Related tasks

Updating bundle versions for an EBA asset
Maintaining an OSGi composition unit
Checking the bundle download status of an EBA asset
Checking the update status of an OSGi composition unit
Administering bundle repositories
Exporting and importing a deployment manifest file