+

Search Tips   |   Advanced Search

Map data sources for all 2.x CMP beans settings

Map container-managed persistence (CMP) 2.x beans of an application to data sources available to the application.

From the admin console, click...

        Applications > Application Types > WebSphere enterprise applications > 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 you bound them together during application assembly. For every data source displayed, we see the corresponding security configuration.


Set Multiple JNDI names

Specify the 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.

Information Value
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 WebSphere Application Server 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:


Select

Select the check boxes of the rows to edit.


Bean

The name of an enterprise bean in the application.


Module

The name of the module containing 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:

  • Java EE connector security
  • Enable trusted context for DB2 databases
  • Configure Kerberos as the authentication mechanism
  • Configure enterprise application files