Resource references

To designate how the resource references of application modules map to the actual resources that are configured for the application.

To view this admin console page, click Applications > Application Types > WebSphere enterprise apps > application_name > Resource references.

• 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 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

• The page is comprised 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, you 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 the references only if we bound them together during application assembly. We can modify those bindings on this admin console page.

• To set the mappings:

  1. Select a row. Be aware that if we check multiple rows on this page, the resource mapping target that you select in step 2 applies to all of those references.

  2. Click Browse to select a resource from the new page that is displayed, the Available Resources page. The Available Resources page shows all resources that are available mapping targets for the application references.

  3. Click Apply. The console displays the Resource references page again. In the rows that you previously selected, you now see the JNDI name of the new resource mapping target.

  4. Repeat the previous steps as necessary.

  5. Click OK. You now return to the general configuration page for your enterprise application.

• For data sources and connection factories: Sections for these resource types contain an additional set of steps for modifying the 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 WAS performs signon to the resource rather than the enterprise bean code. The reconfiguring process differs slightly for each authentication method option:

  • If we select None:

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

    2. Select the appropriate table rows.

    3. Select None from the list of authentication method options that precede the table.

    4. Click Apply.

  • If we select Default:

    1. Determine which resources to designate with the WAS DefaultPrincipalMapping login configuration. You must apply this option to each resource individually to designate different authentication data aliases. See the "J2EE connector security" Information center topic for more information on the default mapping configuration.

    2. Select the appropriate table rows.

    3. Select Use default method from the list of authentication method options that precede the table.

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

    5. Click Apply.

  • If we select Use trusted connections (one-to-one mapping):

    1. You must have a data source server that is running DB2 V9.1 for z/OS, and the data source must have trusted context enabled.

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

    3. Select a data source from the table that has trusted context enabled.

    4. Click Apply.

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

  • If we select Custom login configuration:

    1. Determine which resources to designate with a custom Java™ Authentication and Authorization Service (JAAS) login configuration. See the "J2EE connector security" Information center topic for more information on custom JAAS login configurations.

    2. Select the appropriate table row.

    3. Select Use custom login configuration from the list of authentication method options that precede the table.

    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.

Select

Select the check boxes of the rows to edit.

Module

The name of a module in the application.

EJB

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.

Data type

String

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.

---

 

Related tasks

Enable trusted context for DB2 databases
Set a resource reference