Resource references

Use this page to designate how the resource references of application modules map to the actual resources configured for the application.

From the admin console, click...

        Applications > Application Types > WebSphere enterprise applications > application_name > Resource references.

We can also view this page during the Map resource references to resources step when we install an application.

• If the application uses any of the following resource types, we can set or reset their mapping configurations:
  • 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

• The page is composed of sections that correspond to each applicable resource type. Each section heading is the class name for the resource. If the application contains only one applicable resource type, we see only one section.
• Each section contains a table. Each table row depicts a resource reference within a specific module of the application.

• The rows contain the JNDI names of resource mapping targets for our references only if you bound them together during application assembly. We can modify those bindings on this administrative console page.

• To set your mappings:

  1. Select a row. To apply the same mapping to multiple rows, complete the steps in the section, Set multiple JNDI names.

  2. Click Browse to view a new page listing of all resources that are available mapping targets for the application references.

  3. Select a resource and click Apply. The console displays the Resource references page again. The JNDI name of the selected resource mapping displays in the Target Resource JNDI Name field.

  4. Repeat the previous steps as necessary.

  5. If we are editing the resource references of an existing enterprise application, click OK. You now return to the general configuration page for our enterprise application. If we are installing the application and have completed the Map resource references to resources step, continue to the next step.

• For data sources and connection factories: Sections for these resource types contain an additional set of steps for modifying our security settings. Use the last column in the displayed table to view the authorization type for each resource configuration per application module. We can modify the corresponding authentication method only if the authorization type is container. Container-managed authorization indicates that the product performs signon to the resource rather than the enterprise bean code. The reconfiguring process differs slightly for each authentication method option:

  • When we want to assign no authentication method to a resource:

    1. Determine which resource configurations to designate with no authentication method.

    2. Select the appropriate table rows.

    3. Click Modify Resource Authentication Method and select None from the authentication method options displayed.

    4. Click Apply.

  • When we want to assign the WAS DefaultPrincipalMapping login configuration to a resource:

    1. We must apply this option to each resource individually to designate different authentication data aliases. See the topic, J2EE connector security, for more information about the default mapping configuration.

    2. Select the appropriate table rows.

    3. Click Modify Resource Authentication Method and select Use default method from the list of authentication method options displayed.

    4. Select an authentication data entry or alias from the list.

    5. Click Apply.

  • When we want to assign a trusted context to a resource:

    1. We must have a data source running at least DB2 v9.1 for z/OS, and the data source must have trusted context enabled.

    2. We must have a data source server running at least DB2 v9.1 for z/OS, and the data source must have trusted context enabled.

    3. Select the appropriate table rows that have trusted context enabled.

    4. Click Modify Resource Authentication Method and select Use trusted connections from the authentication method options displayed.

    5. Select an authentication alias from the list that matches an alias already defined in the DB2 data source. If we do not have an alias defined that is suitable, define a new alias.

    6. Click Apply.

    7. To edit the properties of the custom login configuration, click Mapping Properties in the table cell.

  • When we want to assign a custom JAAS login configuration to a resource:
    1. See the topic, J2EE connector security, for more information about custom JAAS login configurations.

    2. Select the appropriate table row.

    3. Click Modify Resource Authentication Method and select Use custom login configuration from the authentication method options displayed.

    4. Select an application login configuration from the list.

    5. Click Apply.

    6. To edit the properties of the custom login configuration, click Mapping Properties in the table cell.

Button	Resulting action
Set Multiple JNDI Names	Display a list of JNDI names. Select a JNDI name to set the same JNDI name on multiple resources with one operation. The selected JNDI name is applied to the Target Resource JNDI Name field of all the selected rows of the table.
Use Java EE Default Bindings	For data source, connection factory, and work manager resources, sets the resource JNDI name to the default Java EE binding for the resource type. The JNDI name is applied to the Target Resource JNDI Name field of the table. The resource module must be installed on a server on a version 9.0 node.
Modify Resource Authentication Method	If the authorization type is container, displays authentication method options. We can change the security settings by selecting a different authentication method. The last column in the displayed table lists the authorization type for each resource configuration for an application module. For information about changing the security settings, see instructions in the For data sources and connection factories section.
Extended Properties	Display the Extended data source properties page, in which we can set additional properties for the selected resource. Use these properties to enable an application to extend the custom properties for a data source or override any non-core properties that already exist for that data source.

Select

Select the check boxes of the rows to edit.

Module

The name of a module in the application.

Bean

The name of an enterprise bean contained by the module.

URI

Specifies location of the module relative to the root of the application EAR file.

Resource Reference

The name of a resource reference used in the enterprise bean, if applicable, and is declared in the deployment descriptor of the application module.

Target Resource JNDI name

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

Login configuration

This column applies to data sources and connection factories only and refers to the authorization type and the authentication method for securing the resource.

Enable trusted context for DB2 databases

Extend DB2 data source definitions at the application level

Extended data source properties