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 within 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 the following path:
An OSGi application can be deployed to any number of servers and clusters. All of these targets must fall within the same security domain. Resource references can be bound only to JCA authentication aliases that exist on every target server or cluster. That is to say, they must each exist in either the target server security domain, or the global security domain.
<blueprint xmlns:rr="http://www.ibm.com/appserver/schemas/8.0/blueprint/resourcereference"> <!-- Other Blueprint declarations ... --> <rr:resource-reference id="resourceRef1" interface="javax.resource.cci.ConnectionFactory" filter="(osgi.jndi.serviceName=jdbc/AccountDS2)"> <rr:res-auth>Application</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 resourceRef1), the service filter (for example jdbc/AccountDS2), the authentication type (for example Application), and the sharing setting (for example Shareable).
Each bundle's Blueprint resource references to authentication alias bindings are stored in a file ibm-eba-bnd.xml within that bundle's META-INF directory. 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.
Links marked (online) require access to the Internet. Each link starts a search for the topic in the online information center. When search results are listed, select the topic that corresponds best to your configuration.
Check for updates to this topic (online)
The version of this bundle.
The bundle symbolic name, together with the bundle version, identifies a unique bundle.
The interface for this resource reference.
The name of the service filter that is the mapping target of the resource reference. For example, jdbc/AccountDS2.
The resource reference is either authenticated by the application, or by the container.
The authentication alias (if any) that is used for securing the resource reference.
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.