File name: udat_maprrr.html
Resource references
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 .
- If your application uses any of the following resource types, you 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 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.
- To set your mappings:
- 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.
- 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.
- 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.
- 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 the product 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:
- Determine which resource configurations to designate with no authentication
method.
- Select the appropriate table rows.
- Select None from the list of authentication method options that
precede the table.
- Click Apply.
- If you select Default:
- 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.
- Select the appropriate table rows.
- Select Use default method from the list of authentication method
options that precede the table.
- Select an authentication data entry or alias from the list.
- Click Apply.
- If you select Use trusted connections (one-to-one mapping):
- You must have a data source server that is running DB2® Version 9.1 for z/OS®, and the data source must have trusted
context enabled.
- Select an authentication alias from the list that matches an alias that
is already defined in the DB2 data source. If you do not have an alias defined
that is suitable, you need to define a new alias.
- Select a data source from the table that has trusted context enabled.
- Click Apply.
- To edit the properties of the custom login configuration, click Mapping
Properties in the table cell.
- If you select Custom login configuration:
- 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.
- Select the appropriate table row.
- Select Use custom login configuration from the list of authentication
method options that precede the table.
- Select an application login configuration from the list.
- Click Apply.
- To edit the properties of the custom login configuration, click Mapping
Properties in the table cell.
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
Specifies location of the module relative to the root of the application
EAR file.
Resource Reference
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.
Target Resource JNDI name
The Java Naming and Directory Interface (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.
|
