EJB resource references [Settings]

EJB resource references [Settings]

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.

Binding a resource reference maps a resource dependency of an enterprise bean to an actual resource available in the server runtime environment. At a minimum, we can achieve this mapping by specifying the JNDI name under which the resource reference is known in the runtime environment. By default, the JNDI name is retrieved from pre-existing bindings, or set to the value of the mapped-name specified in the resource definition.

If a JNDI name mapping for a resource reference is defined in an ibm-ejb-jar-bnd.xml file in the bundle, the corresponding JNDI name is displayed in the JNDI Name column for that reference, otherwise the JNDI name defaults to the resource reference name. We can modify the mappings, as required, by entering the appropriate values in the JNDI Name column.

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: Map EJB resource references to resources
Applications > Application Types > Business-level applications > application_name > composition_unit_name > [Additional Properties] EJB resource references

The Map EJB resource references to resources wizard step and the EJB resource references property are visible only if the OSGi application contains at least one resource reference, defined either in an ejb-jar.xml file, or through an @Resource annotation on an enterprise bean.

General Properties

Select

To modify the authentication method, or to set extended data source custom properties that apply to the database connection, select a single reference then click Modify Resource Authentication Method... or Extended Properties....

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.

EJB name

The name of the enterprise bean that declares the resource reference.

Resource Reference

The name of a resource reference used in the application, if applicable, and is declared in the deployment descriptor of the EJB bundle.

Resource Type

The type of the resource reference.
Use this panel to specify bindings for any resource-ref (resource reference) resource, as defined in the Java specification JSR-250: Common Annotations for the Java Platform. For example, the following are all types of resource-ref resource:

Data source
Generic JMS connection factory
Mail session
J2C connection factory
JMS queue connection factory for the JMS provider of IBM MQ
JMS topic connection factory for IBM MQ
Unified JMS connection factory for IBM MQ
URL configuration

JNDI name

The JNDI name of the resource that is the mapping target of the resource reference.

Login Configuration

The authorization type and the authentication method for securing the resource. Container-managed authorization indicates that the product signs on to the resource rather than the enterprise bean code.

Buttons

Label Action
Browse
To specify the JNDI name mapping for a specific EJB resource reference, use this option to select the resource reference from a list of available resources.

Modify Resource Authentication Method

We can select one of the following options:

None

Use default method (many-to-one mapping)

For information about the default mapping configuration, see J2EE connector security.

Select this option, then select an authentication alias from the list.

Use trusted connections (one-to-one mapping)

Use this option if your resource is a data source that has trusted context enabled.

Select this option, then select an authentication alias from the list that matches an alias already defined in the data source.

Use custom login configuration

For information about custom JAAS login configurations, see J2EE connector security.

Select this option, then select a JAAS login configuration from the list.

Extended properties

If our resource is a data source, and the back-end database supports extended data source custom properties, we can use this option to add, modify, or delete these properties. These are custom properties, in the form of name/value pairs, we can use to obtain a data source.
If we use multiple values for an extended data source property, we must enclose those values in quotation marks.
See Extended data source properties.

Mapping properties
Define arbitrary name and value pairs for extended data source properties that apply to the resource authentication method. This button is visible only if we have selected Use trusted connections or Use custom login configuration for the resource authentication method.

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: was54.html

prettyPrint();

Label	Action
Browse	To specify the JNDI name mapping for a specific EJB resource reference, use this option to select the resource reference from a list of available resources.
Modify Resource Authentication Method	We can select one of the following options: None Use default method (many-to-one mapping) For information about the default mapping configuration, see J2EE connector security. Select this option, then select an authentication alias from the list. Use trusted connections (one-to-one mapping) Use this option if your resource is a data source that has trusted context enabled. Select this option, then select an authentication alias from the list that matches an alias already defined in the data source. Use custom login configuration For information about custom JAAS login configurations, see J2EE connector security. Select this option, then select a JAAS login configuration from the list.
Extended properties	If our resource is a data source, and the back-end database supports extended data source custom properties, we can use this option to add, modify, or delete these properties. These are custom properties, in the form of name/value pairs, we can use to obtain a data source. If we use multiple values for an extended data source property, we must enclose those values in quotation marks. See Extended data source properties.
Mapping properties	Define arbitrary name and value pairs for extended data source properties that apply to the resource authentication method. This button is visible only if we have selected Use trusted connections or Use custom login configuration for the resource authentication method.