Configuration tab
Scope
Specifies the scope of the resource adapter that connects
applications to an enterprise information system (EIS) through this
connection factory. Only applications that are installed within this
scope can use this connection factory.
Provider
Specifies the resource adapter that WebSphere Application
Server uses for this connection factory.
Provider is displayed in this location only when you create
a new connection factory. The list shows all of the existing resource
adapters that are defined at the relevant scope. Select one from the
list if you want to use an existing resource adapter as Provider.
Create New Provider
Provides the option of configuring a new resource adapter
for the new connection factory.
Create New Provider is displayed only when you create, rather
than edit, a connection factory.
Clicking Create New Provider triggers the console to display
the resource adapter configuration page, where you create a new adapter.
After you click OK to save your settings, you see the connection
factory collection page. Click New to define a new connection
factory for use with the new resource adapter; the console now displays
a configuration page that lists the resource adapter as the new connection
factory Provider.
Name
Specifies the name of this connection factory.
This is a required property.
JNDI Name
Specifies the JNDI name of this connection factory.
For example, the name could be eis/myECIConnection.
After you set this value, save it and restart the server. You can
see this string when you run the dumpNameSpace tool. This is
a required property. If you do not specify a JNDI name, it is filled
in by default using the Name field.
Data type |
String |
Default |
eis/display name |
Important: Adhere to the following requirements for JNDI
names:
- Do not assign duplicate JNDI names across different resource types
(such as data sources versus J2C connection factories or JMS connection
factories).
- Do not assign duplicate JNDI names for multiple resources of the
same type in the same scope.
Description
Specifies a text description of this connection factory.
Connection Factory Interface
Specifies the fully qualified name of the Connection Factory
Interfaces supported by the resource adapter.
This is a required property. For new objects, the list of available
classes is provided by the resource adapter in a drop-down list. After
you create the connection factory, the field is a read only text field.
Data type |
Drop-down list or text |
Category
Specifies a string that you can use to classify or group
this connection factory.
Component-managed Authentication Alias
Specifies authentication data for component-managed signon
to the resource.
Select an alias from the list.
To define a new alias that is not displayed in
the list:
- Click Apply. Under Related Items, you now see a listing
for J2EE Connector Architecture (J2C) authentication data entries.
- Click J2EE Connector Architecture (J2C) authentication data
entries.
- Click New.
- Define an alias.
- Click OK. The console now displays an alias collection
page. This page contains a table that lists all of your configured
aliases. Before the table, this page also displays the name of your
connection factory.
- Click the name of your J2C connection factory. You now see the
configuration page for the connection factory.
- Select the new alias in the Component-managed authentication alias
list.
- Click Apply.
Note: The alias that you configure for component-managed authentication
does not apply to all clients that must access the secured resource.
External Java clients with Java Naming and Directory Interface (JNDI)
access can look up a Java 2 Connector (J2C) resource such as a data
source or Java Message Service (JMS) queue. However, they are not
permitted to take advantage of the component-managed authentication
alias defined on the resource. This alias is a default value used
when the user and password are not supplied on the getConnection()
call. Therefore, if an external client needs to get a connection,
it must assume responsibility for the authentication by passing it
through arguments on the getConnection() call.
Authentication Alias for XA Recovery
This optional field is used to specify the authentication
alias that should be used during XA recovery processing.
If the resource adapter does not support XA transactions, then
this field will not be displayed. The default value will come from
the selected alias for application authentication (if specified).
- Use Component-managed Authentication Alias
- Selecting this radio button specifies that the alias set for component-managed
authentication is used at XA recovery time.
- Specify:
- Selecting this radio button enables you to choose an authentication
alias from a drop-down list of configured aliases.
Container-managed Authentication Alias (deprecated)
Specifies authentication data (a string path converted
to userid and password) for container-managed signon to the resource.
Deprecated feature: Beginning with WebSphere Application Server
Version 6.0, the container-managed authentication alias is superseded
by the specification of a login configuration on the resource-reference
mapping at deployment time, for components with
res-auth=Container.
depfeat
Select an alias from the list.
To define a new alias that is not displayed in
the list:
- Click Apply. Under Related Items, you now see a listing
for J2EE Connector Architecture (J2C) authentication data entries.
- Click J2EE Connector Architecture (J2C) authentication data
entries.
- Click New.
- Define an alias.
- Click OK. The console now displays an alias collection
page. This page contains a table that lists all of your configured
aliases. Before the table, this page also displays the name of your
connection factory.
- Click the name of your J2C connection factory. You now see the
configuration page for the connection factory.
- Select the new alias in the Container-managed authentication
alias list.
- Click Apply.
Authentication Preference
Specifies the authentication mechanisms defined for this
connection factory.
This setting specifies which of the authentication mechanisms defined
for the corresponding resource adapter applies to this connection
factory. Common values, depending on the capabilities of the resource
adapter, are: KERBEROS, BASIC_PASSWORD, and None.
If None is chosen, the application component is expected to manage
authentication (<res-auth>Application</res-auth>). In this
case, the user ID and password are taken from one of the following:
- The component-managed authentication alias
- UserName, Password Custom Properties
- Strings passed on the getConnection method
For example, if two authentication mechanism entries are defined
for a resource adapter in the
ra.xml document:
- <authentication-mechanism-type>BasicPassword</authentication-mechanism-type>
- <authentication-mechanism-type>Kerbv5</authentication-mechanism-type>
the authentication preference specifies the mechanism to use
for container-managed authentication. An exception is issued during
server startup if a mechanism that is not supported by the resource
adapter is selected.
Data type |
Pick-list |
Default |
BASIC_PASSWORD |
Mapping-Configuration Alias (deprecated)
Specifies the authentication alias for the Java Authentication
and Authorization Service (JAAS) mapping configuration that is used
by this connection factory.
Deprecated feature: Beginning with WebSphere Application Server
Version 6.0, the Mapping-Configuration Alias is superseded by the
specification of a login configuration on the resource-reference mapping
at deployment time, for components with
res-auth=Container.
depfeat
Click Security > Secure administration,
applications, and infrastructure > Java Authentication and
Authorization Service > Application logins and select an
alias from the table.
The DefaultPrincipalMapping JAAS configuration maps the
authentication alias to the userid and password. You may define and
use other mapping configurations.