Network Deployment (Distributed operating systems), v8.0 > Reference > Sets

OSGi Applications administrative console panels

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

Subtopics

• 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 we 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.
• Blueprint resource reference bindings [Settings]
  Blueprint components can access WAS resource references. Each reference is declared in a Blueprint XML file, and can be secured using a 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. We can get an up-to-date list of the bundles in the bundle cache, check if all bundles have been 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. We can also view and refresh the repository URL for the repository that hosts the bundle.
• Context root for web application bundles [Settings]
  Context roots determine where the web pages of a particular web application bundle (WAB) are found at run time.
• External bundle repositories [Collection]
  The external bundle repositories are bundle repositories that are available outside of WAS. If your OSGi applications reference bundles that are stored in an external bundle repository, 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 WAS. 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]
  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. 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 WAS. We 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 WAS. 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. We can store bundles and composite bundles in the internal repository. If the bundle is a composite bundle, extra fields are visible.
• Manage extensions for this composition unit [Collection]
  Add composite bundle extensions to, or remove them from, a composition unit that contains an enterprise OSGi application.
• Manage 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.
• Map RunAs roles to users [Collection]
  We can map a specified user identity and password to a RunAs role. This enables you to specify application-specific privileges for individual users, so that they can run specific tasks using another user identity.
• 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.
• Security role to user or group mapping [Settings]
  We can specify the users and groups that are mapped to the security roles used with the OSGi application.
• Update bundle versions in this application [Settings]
  Update the versions of the bundles that comprise this application. 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.
• Upload bundle [Settings]
  Upload a bundle into the internal bundle repository. We can upload single bundles, composite bundles, and grouped-up sets of bundles.
• Virtual hosts for web application bundles [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 and resource environment reference bindings [Settings]
  For each reference, specify the JNDI name under which the resource is known in the runtime environment.
• Web module resource reference bindings [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.

Parent topic: Administer OSGi Applications
Reference topic Feedback
Copyright IBM Corporation 2009, 2011. All Rights Reserved.
This information center is powered by Eclipse technology.

+

Search Tips   |   Advanced Search