Use the administrative console to add an enterprise bundle
application (EBA) composition unit that consists of a previously-imported
EBA asset and configuration information. Configuration information includes the context roots, virtual hosts, security role mappings, and web module or Blueprint resource bindings for your OSGi application.
Before you begin
You can add an EBA asset to a business-level application
by using the administrative console as described in this topic, or
by using the addCompUnit command as described in Adding an EBA asset to a business-level application using the addCompUnit command.
An EBA asset can be added to only one business-level application. A business-level application is scoped to cell scope, so this means that only one instance of a given OSGi application can be deployed in a cell.
This
task makes the following assumptions:
- You have already imported the EBA file as an asset (as described
in Deploying an OSGi application as a business-level application), then saved
your changes to the master configuration (which causes any bundle
dependencies to be downloaded from configured bundle repositories).
- You have already defined the target virtual hosts. To check existing virtual hosts by using the administrative console, click .
- You have already created the JCA authentication alias that
you want to associate with each Blueprint resource reference. To check
existing JCA authentication aliases using the administrative console,
click .
About this task
An EBA composition unit consists of a previously-imported EBA asset, plus some or all of the following configuration information: - Mappings from the composition unit to a target application server,
web server or cluster.
- Configuration of the application's context roots or virtual
hosts.
- Bindings to any associated web modules or blueprint resource references.
- Mappings from security roles to particular users or groups.
You use the Set options settings wizard
to add a new EBA composition unit to a business-level application.
The contents of the asset determine the specific steps in the wizard. This topic includes a brief description of the main elements that you need to configure when adding an EBA asset. For a more
complete description of the elements that the wizard might prompt
you to configure, see Creating business-level applications with the console.
You specify the configuration information for the EBA asset during the following procedure and you cannot change it later. For example, if you subsequently update a bundle in an EBA asset, you cannot introduce anything that requires additional configuration, for example new resource references.
Procedure
- Start the administrative console.
- Add the previously-imported asset (the .eba file) as a deployed asset.
- If you have just created a new business-level application,
the general properties for the business-level application are already
displayed, including the option .
Otherwise, navigate to . A list of available assets is displayed.
- Select the asset to add, then click Continue. The Set options settings wizard is
displayed.
- Wizard step: Set options.
Change the composition
unit settings as needed, then click Next. For
more information, see Set options settings.
- Wizard step: Map composition unit to a target.
Select
the deployment target application server or web server, then click Next.
For more information, see Map target settings.
- Wizard step: Map context roots.
Select a web application bundle (WAB) from the list, then enter the context root for the WAB. For example, /sample. For more information, see Context root for web application bundles [Settings].
- Wizard step: Map modules to virtual hosts.
The list of available WABs in this asset is displayed. For each WAB, you can change the associated virtual host by selecting a different one from the list. If you specify an existing virtual host in the ibm-web-bnd.xml or .xmi file for a given WAB, the specified virtual host is set by default. Otherwise, the default virtual host setting is default_host. For more information, see Virtual hosts for web application bundles [Settings].
- Wizard step: Security role to user/group mapping
Change the security mapping as needed. For more information, see Security role to user or group mapping.
- Wizard step: Bind Blueprint resource references.
The list of available Blueprint resource references in this asset is displayed. For each reference, you can optionally select an authentication alias from the drop-down list. Default authentication aliases (from ibm-eba-bnd.xml files) are offered only if they exist on every target server or cluster. For more information, see Bind Blueprint resource references [Settings].
- Wizard step: Web module resource reference bindings.
The list of available web module resource references in this asset is displayed. 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. To specify the JNDI name mapping, either type the JNDI name into the box, or click Browse... then select the resource reference from the list of available resources. To set authentication properties and extended data source custom properties, select a single reference then click Modify Resource Authentication Method... or Extended Properties.... For more information, see Web module resource references [Settings].
- Wizard step: Summary
A summary of your selections
is displayed. To complete the creation of the EBA composition unit,
click Finish. If there are settings that you
want to change, click Previous to review the
settings.
- Save your changes to the master configuration.
Results
The product creates composition units for the application,
module, or shared library relationships. The unit names are shown
in lists of deployed assets on the settings page of your business-level
application. To view the settings page, click
.
What to do next
You are now ready to start your business-level application.