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.
The Bind Blueprint resource references option is only visible if the bundle includes Blueprint resource reference declarations.
When you 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 that are 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.
<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).
<eba-bnd xmlns="http://www.ibm.com/blueprintbinding.xsd"> <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>
This identifier is only displayed 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.
The symbolic name, together with the version, identifies a unique composite bundle.
Each bundle is identified by a string that contains the bundle symbolic name and bundle version. Bundles that are part of a composite bundle are listed beneath the composite bundle identifier.
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 list. Default authentication aliases (from ibm-eba-bnd.xml files) are offered only if they exist on every target server or cluster.