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

To view this administrative console page, click Applications > Enterprise Applications > application_name > Map resource references to resources .

Guidelines for using this administrative console page:

• If your application uses any of the following resource types, you can set or reset their mapping configurations:

  • Mail session

  • URL configuration

  • Data source

  • 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

  • Generic JMS connection factory

• The page is comprised of sections that correspond to each applicable resource type. Each section heading is the class name for the resource. If your 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 your application.

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

  1. To set your mappings:

     1. Select a row. Be aware that if you 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 your application references.

  2. 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.

     Repeat the previous steps as necessary.

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

• To modify your mappings if this console page displays a drop-down list of JNDI names for configured resources:

  1. Select one or more rows in this table to edit. If you select multiple rows, the configured resource that you choose as the new mapping target is bound to every resource reference in your selection.

  2. From the list, select the Java Naming and Directory Interface (JNDI) name of the resource that you want to designate as the new mapping target.

  3. Click Apply . You now see the JNDI name of the new mapping target in the table row(s).

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

  • If you 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 you select Default :

    1. Determine which resources to designate with the WebSphere Application Server DefaultPrincipalMapping login configuration. You must apply this option to each resource individually if you want 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 you 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.

Table column heading descriptions:

Select

Select the check boxes of the rows that you want to edit.

Module

The name of a module in the application.

EJB

The name of an enterprise bean that is contained by the module.

URI

When resolved relative to the application Uniform Resource Locator (URL), the Uniform Resource Identifier (URI) specifies the location of the module archive contents on a file system.

Reference binding

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

JNDI name

The Java Naming and Directory Interface (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.