Map data sources for all 2.x CMP beans settings

To map container-managed persistence (CMP) 2.x beans of an application to data sources that are available to the application.

To view this admin console page, click Applications > Application Types > Websphere enterprise apps > application_name > Map data sources for all 2.x CMP beans.

Each table row corresponds to a CMP bean within a specific EJB module. A row shows the JNDI name of the data source mapping target of the bean only if we bound them together during application assembly. For every data source that is displayed, you see the corresponding security configuration.

Set Multiple JNDI names

Specify the Java™ Naming and Directory Interface (JNDI) name for multiple EJB modules. Select one or more EJB modules from the table, and select a JNDI name from this list to configure the EJB modules with that JNDI name.

Data type

Drop-down list

Set Authorization Type

Specify the authorization type for securing the data source. Select one or more EJB modules from the table to set the authorization type.

Select either Container or Application from the displayed list. Container-managed authorization indicates that WAS performs signon to the data source. Application-managed authorization indicates that the enterprise bean code performs signon.

Modify Resource Authentication Method

Specify the authorization type and the authentication method for securing the data source. Select one or more EJB modules from the table to modify the resource authentication method.

We can choose between the following authentication methods:

• None:

  1. Determine which data source 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.

• Use default method (many-to-one mapping):

  1. Determine which data source configurations to designate with the WAS DefaultPrincipalMapping login configuration. Apply this option to each data source individually to designate different authentication data aliases. See the information center topic on J2EE Connector security for more information on the default mapping configuration.

  2. Select the appropriate table rows.

  3. Select Use default method (many-to-one mapping) 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.

• Use Kerberos authentication: Specifies to use the Kerberos authentication method.

  1. Ensure that we have configured the Kerberos authentication mechanism in the appserver.

  2. Select the appropriate table row.

  3. Select Use Kerberos authentication 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.
  The appserver will attempt to verify that we are connecting to the correct type of database when you select this option.

• Use trusted connections (one-to-one mapping):

  1. Determine which data source configurations to designate with a custom Java Authentication and Authorization Service (JAAS) login configuration. See the information center topic on J2EE Connector security for more information on custom JAAS login configurations.

  2. Select the appropriate table row.

  3. Verify the database to which the modules will connect is configured for trusted connections.

  4. Select Use trusted connections (one-to-one mapping) from the list of authentication method options that precede the table.

  5. Select an application login configuration from the list.

  6. Click Apply.
  The appserver will attempt to verify that we are connecting to the correct type of database when you select this option.

• Custom login configuration:

  1. Determine which data source configurations to designate with a custom Java Authentication and Authorization Service (JAAS) login configuration. See the information center topic on J2EE Connector security 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.

EJB

The name of an enterprise bean in the application.

EJB Module

The name of the module that contains the enterprise bean.

URI

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

Target resource JNDI name

Resource to which the CMP bean is bound.

Resource authorization

Current setting for the resource authorization type.

Modify this setting with Set authorization type.

---

 

Related concepts

J2EE connector security

 

Related tasks

Enable trusted context for DB2 databases
Set Kerberos as the authentication mechanism
Set enterprise application files