- Scope
- Specifies the level to which this resource definition is visible
-- the cell, node, or server level.
Resources such as JDBC Providers, Namespace bindings, or shared libraries
can be defined at multiple scopes, with resources defined at more specific
scopes overriding duplicates which are defined at more general scopes.
Note that no matter what the scope of a defined resource, the resource's
properties only apply at an individual server level. For example, if you define
the scope of a data source at the Cell level, all users in that Cell can look
up and use that data source, which is unique within that Cell. However, resource
property settings are local to each server in the Cell. For example,
if you define max connections to 10, then each server in that Cell
can have 10 connections.
- Cell
- The most general scope. Resources defined at the Cell scope
are visible from all Nodes and servers, unless they are overridden. To view
resources defined in the cell scope, do not specify a server or a node name
in the scope selection form.
- Node
- The default scope for most resource types. Resources defined
at the Node scope override any duplicates defined at the Cell scope and are
visible to all servers on the same node, unless they are overridden at a
server scope on that node. To view resources defined in a node scope, do not
specify a server, but select a node name in the scope selection form.
- Server
- The most specific scope for defining resources. Resources
defined at the Server scope override any duplicate resource definitions defined
at the Cell scope or parent Node scope and are visible only to a specific
server. To view resources defined in a server scope, specify a server name
as well as a node name in the scope selection form.
When resources are created, they are always created into the current scope
selected in the panel. To view resources in other scopes, specify a different
node or server in the scope selection form.
- Name
- Specifies a list of connection factory display names.
- 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 dumpNameSpace.
Data type |
String |
Default |
eis/display name |
- Description
- Specifies a text description of this connection factory.
- Category
- Specifies a string that you can use to classify or group this connection
factory.
- 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 thrown during server startup if a mechanism
that is not supported by the resource adapter is selected.
Data type |
Pick-list |
Default |
BASIC_PASSWORD |
- Component-managed Authentication Alias
- Specifies authentication data for component-managed signon to the
resource.
Choose from aliases defined under
Security > JAAS Configuration > J2C Authentication Data.
To define a new alias not already appearing in the pick list:
- Click Apply to expose Related Items.
- Click J2C Authentication Data Entries.
- Define an alias.
- Click the connection factory name at the top of the J2C Authentication
Data Entries page to return to the connection factory page.
- Select the alias.
- Container-managed Authentication Alias
- Specifies authentication data (a string path converted to userid and password) for container-managed signon to the
resource.
Choose from aliases defined under
Security > JAAS Configuration > J2C Authentication Data.
To define a new alias not already appearing in the pick list:
- Click Apply to expose Related Items.
- Click J2C Authentication Data Entries.
- Define an alias.
- Click the connection factory name at the top of the J2C Authentication
Data Entries page to return to the connection factory page.
- Select the alias.
- Mapping-Configuration Alias
- Allows users to select from the
Security > JAAS Configuration > Application Logins Configuration list.
The DefaultPrincipalMapping
JAAS configuration maps the authentication alias to the userid and password.
You may define and use other mapping configurations.