Map data sources for all 2.x CMP beans

Use this page to set the default data source mapping for EJB modules containing 2.x container-managed persistence (CMP) beans. Unless you configure individual data sources for the 2.x CMP beans, this default mapping applies to all beans within the module.

To view this administrative console panel, click Applications > Application Types > Websphere enterprise applications > application_name > Map data sources for all 2.x CMP beans .

This panel displays a table that depicts the EJB modules in the application containing 2.x CMP beans. Each table row corresponds to a module. A row shows the JNDI name of the data source mapping target of the EJB module only if you bound them together during application assembly. For every data source that is displayed, you see the corresponding security configuration.

Set Multiple JNDI Names

Specifies the JNDI name to bind to one or more modules. Select one or more modules, click Set Multiple JNDI Names, and select the JNDI name for the resource to which you would like to bind the module.

Set Authorization Type

Authorization type that you to use for the modules. Select one or more modules, click Set Authorization Type, and select the authorization type.

We can choose:

• Per application - indicates that the enterprise bean code performs signon.

• Container - indicates that the application server performs signon to the data source.

Modify Resource Authentication Method

Resource authentication method for the modules that we have configured with container-managed authorization. Select one or more modules, click Modify Resource Authentication Method, and select the 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 application server.

  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 application server will attempt to verify that you 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. Ensure that 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 application server will attempt to verify that you 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.

Extended Datasource Properties

When selected, you will be directed to a panel on which we can specify extended properties that the module can use for the DB2 data source.

The application server will attempt to verify that you are connecting to the correct type of database when you select this option.

Select

Select the check boxes of the rows to edit.

Module

Name of the module containing the 2.x enterprise beans.

Bean

Name of an enterprise bean contained by the module

URI

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

Target Resource JNDI Name

Specifies the JNDI name of the default data source for the EJB module.

Information	Value
Data type	String

Resource authorization

Authorization type and the authentication method for securing the data source.

Related tasks

Configure Kerberos as the authentication mechanism using the administrative console