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 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.

To view this panel in the administrative console, click one of the following paths:

• Applications > Application Types > Business-level applications > application_name > [Deployed assets] Add > Add Asset > asset_name > Wizard step: Bind Blueprint resource references
• Applications > Application Types > Business-level applications > application_name > composition_unit_name > [Additional Properties] Blueprint resource references

The Bind Blueprint resource references wizard step and the Blueprint resource references property are visible only if the bundle includes Blueprint resource reference declarations.

When we secure resource references, those resource references can be bound only to JCA authentication aliases that exist on every server or cluster on which the application is deployed. An OSGi application can be deployed to multiple servers and clusters in the same security domain. Therefore, each JCA authentication alias must exist in either the security domain of the target servers and clusters, or the global security domain.

We must declare the resource references in the Blueprint XML file. For example:

<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0" 
  xmlns:rr="http://www.ibm.com/appserver/schemas/8.0/blueprint/resourcereference">
  <!-- Other Blueprint declarations ... -->
  
  <rr:resource-reference id="resourceRef" 
          interface="javax.sql.DataSource"
          filter="(osgi.jndi.service.name=jdbc/Account)">
    <rr:res-auth>Container</rr:res-auth>
    <rr:res-sharing-scope>Shareable</rr:res-sharing-scope>
  </rr:resource-reference>
</blueprint>

This declaration includes the resource reference ID (for example resourceRef), the service filter (for example jdbc/Account), the authentication type (for example Container), and the sharing setting (for example Shareable).

The Blueprint resource references to authentication alias bindings for each bundle are stored in a file ibm-eba-bnd.xml in the META-INF directory of that bundle. If an OSGi application contains any of these files when it is deployed as an asset, these files provide the default authentication alias values used when binding the resource references. For example:

<eba-bnd>
  <resource-ref>
    <jndi-name>jdbc/Acount</jndi-name>
    <authentication-alias>Alias1</authentication-alias>
    <interface>javax.sql.DataSource</interface>
    <authentication>Container</authentication>
    <sharing-scope>Shareable</sharing-scope>
    <id>resourceRef</id>
  </resource-ref>
</eba-bnd>

General Properties

Composite bundle identifier

This identifier is displayed only if the EBA asset uses composite bundles. Each composite bundle is identified by a string in the following form: Composite bundle archive (CBA)'composite.bundle.symbolic.name_composite.bundle.version'. Bundles that are part of a composite bundle are listed beneath the composite bundle identifier.

Composite bundle symbolic name

The non-localizable name for this composite bundle.

Composite bundle version

The version of this composite bundle.

The symbolic name, together with the version, uniquely identifies a composite bundle.

Bundle identifier

Each bundle is identified by a string containing the bundle symbolic name and bundle version. Bundles that are part of a composite bundle are listed beneath the composite bundle identifier.

Bundle symbolic name

The non-localizable name for this bundle.

Bundle version

The version of this bundle.

The bundle symbolic name, together with the bundle version, uniquely identifies a bundle.

Resource reference ID

The ID of the resource reference as declared in the Blueprint.

Resource reference interface

The interface for this resource reference.

Your Blueprint application can use any of the following resource types:

• Default messaging JMS queues destinations
• Default messaging JMS topic destinations
• Data source
• Generic JMS connection factory
• Mail session
• J2C connection factory
• JMS queue connection factory for the JMS provider of IBM MQ
• JMS queue destination for IBM MQ
• JMS topic connection factory for IBM MQ
• JMS topic destination for IBM MQ
• Unified JMS connection factory for IBM MQ
• URL configuration

Resource reference service filter

The name of the service filter that is the mapping target of the resource reference. For example, jdbc/AccountDS2.

Resource reference authentication

The resource reference is either authenticated by the application, or by the container.

Resource reference sharing

The resource reference is either shareable or non-shareable.

Authentication alias

The authentication alias, if any, used for securing the resource reference.

For each reference, we can optionally select an authentication alias from the list. Default authentication aliases (from ibm-eba-bnd.xml files) are offered only if they exist on every target server or cluster.

Related:

JMS and OSGi Applications

Add an EBA asset to a composition unit by

Add an EBA asset to a composition unit using wsadmin commands

Modify the configuration of an OSGi composition unit

Administrative console buttons

Administrative console preferences

File name: was52.html

prettyPrint();