Network Deployment (Distributed operating systems), v8.0 > Reference > Sets > OSGi Applications administrative console panels
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.
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] Bind Blueprint resource references
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.
We must declare the resource references in the Blueprint XML file. For example:
<blueprint xmlns="//publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.osgi.org/xmlns/blueprint/v1.0.0"
xmlns:rr="//publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://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 that are used when binding the resource references. For example:
<eba-bnd xmlns="//publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://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>
Parent topic: OSGi Applications administrative console panels
Related concepts:
JMS and OSGi Applications
Related tasks:
Add an EBA asset to a composition unit
Add an EBA asset to a composition unit using wsadmin
Modify the configuration of an OSGi composition unit
Related information:
Administrative console buttons
Administrative console preferences
General Properties
Composite bundle identifier
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.
Bundle identifier
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.
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 WebSphere MQ
- JMS queue destination for WebSphere MQ
- JMS topic connection factory for WebSphere MQ
- JMS topic destination for WebSphere MQ
- Unified JMS connection factory for WebSphere 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, 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.
Reference topic
Feedback
Copyright IBM Corporation 2009, 2011. All Rights Reserved.
This information center is powered by Eclipse technology.