Configure Java EE Connector connection factories in the administrative console
To access an enterprise information system (EIS), configure connection factories, which instantiate resource adapter classes for establishing and maintaining resource connections.
An application component uses a connection factory to access a connection instance, which the component then uses to connect to the underlying enterprise information system (EIS). Examples of connections include database connections, Java Message Service connections, and SAP R/3 connections.
(ZOS) If we are using optimized local adapters, we can use the olaRar.py script file to configure the adapter connection factories. See the topic, olaRary.py script file for more information.
Tasks
- Click Resources > Resource Adapters > Resource adapters.
- In the Resource adapters panel, select the resource adapter to configure.
- From the Additional Properties heading, click J2C connection factories.
- Click New.
- Specify any properties for the connection factory in the General Properties panel.
- Select the authentication preference.
- Select the aliases for Component-managed authentication, Container-managed authentication, or both. Some choices for the mapping-configuration alias do not use a container-managed authentication alias, so we will not be able to select a container-managed alias if one of those mapping-configuration aliases is selected.
If we have defined security domains in the application server, we can click Browse... to select an authentication alias for the resource that we are configuring. Security domains allow us to isolate authentication aliases between servers. The tree view is useful in determining the security domain to which an alias belongs, and the tree view can help you determine the servers that will be able to access each authentication alias. The tree view is tailored for each resource, so domains and aliases are hidden when we cannot use them.
If the resource adapter supports XA, an option for Authentication alias for XA recovery will be available. If there are no aliases available, or we want to define a different alias:
- Click Apply to save the current settings.
- Click JAAS - J2C authentication data from the Related Items heading.
- Click New.
- Define the properties for the alias in General Properties.
- Click OK.
- Click OK.
- Click the name of the J2C connection factory that we created.
- From the Additional Properties heading, click Connection pool properties.
- Change any values by clicking the property name. For more information on the settings for connection pools, read the topic Tuning connection pools, or the topic, Connection pool settings.
- Click OK.
- Click Custom properties from the Additional Properties heading.
- Click any property name to change its value. If the UserName and Password properties are defined, they will be overridden by the component-managed authentication alias specified in the previous step.
- Click Save.
- Restart the Deployment Manager and the node agent for the changes to take effect.
Subtopics
- Configure connection factories for resource adapters within applications
To access an enterprise information system (EIS), configure connection factories, which instantiate resource adapter classes for establishing and maintaining resource connections.- Directory conventions
References in product information to app_server_root, profile_root, and other directories imply specific default directory locations. Become familiar with the conventions in use for WAS.- Connection pool settings
Configure connection pool settings.- Connection pool advanced settings
Specify connection pooling related settings.- Connection pool (Version 4) settings (deprecated)
Create a connection pool for a Version 4.0 data source.- J2C Connection Factories collection
View Java 2 Connector (J2C) connection factories, which represent sets of connection configuration values.- J2C connection factories settings
Specify settings for a connection factory.- J2C Connection Factory advanced settings
Specify settings for a Java 2 Connector (J2C) connection factory.- Resource workload routing
Use this topic to learn how to enable resource routing in the environment.- Data source resource definition in applications
Applications can define data sources in annotations or in the deployment descriptor. This topic reviews similarities and compatibility with WAS data sources defined at the server, node, cluster, or cell level. Optional features in data source definition are also discussed.- Bean validation in RAR modules
WAS validates resource adapter archive (RAR) JavaBeans constraints in compliance with the Java Connector Architecture (JCA) version 1.6 specification.- Troubleshoot bean validation in RAR modules
RAR beans that fail validation are not placed into service. When constraint violations occur, applications encounter resource connectivity issues that are different according to the bean type and how the RAR is deployed. This topic explains how to understand, service, and prevent these known issues.- JCA 1.6 support for annotations in RAR modules
The Java Connector Architecture (JCA) Version 1.6 specification adds support for Java annotations in resource archive (RAR) modules. Annotations are a means of specifying metadata, or configuration data, for a RAR module in the class files that make up the module.- Connection factory JNDI name practices
Observe the conventions of the JNDI service in WAS when we create connection factory JNDI names.- Configure connection factories for resource adapters within applications
To access an enterprise information system (EIS), configure connection factories, which instantiate resource adapter classes for establishing and maintaining resource connections.- Directory conventions
References in product information to app_server_root, profile_root, and other directories imply specific default directory locations. Become familiar with the conventions in use for WAS.- Connection pool settings
Configure connection pool settings.- Connection pool advanced settings
Specify connection pooling related settings.- Connection pool (Version 4) settings (deprecated)
Create a connection pool for a Version 4.0 data source.- J2C Connection Factories collection
View Java 2 Connector (J2C) connection factories, which represent sets of connection configuration values.- J2C connection factories settings
Specify settings for a connection factory.- J2C Connection Factory advanced settings
Specify settings for a Java 2 Connector (J2C) connection factory.- Resource workload routing
Use this topic to learn how to enable resource routing in the environment.- Data source resource definition in applications
Applications can define data sources in annotations or in the deployment descriptor. This topic reviews similarities and compatibility with WAS data sources defined at the server, node, cluster, or cell level. Optional features in data source definition are also discussed.- Bean validation in RAR modules
WAS validates resource adapter archive (RAR) JavaBeans constraints in compliance with the Java Connector Architecture (JCA) version 1.6 specification.- Troubleshoot bean validation in RAR modules
RAR beans that fail validation are not placed into service. When constraint violations occur, applications encounter resource connectivity issues that are different according to the bean type and how the RAR is deployed. This topic explains how to understand, service, and prevent these known issues.- JCA 1.6 support for annotations in RAR modules
The Java Connector Architecture (JCA) Version 1.6 specification adds support for Java annotations in resource archive (RAR) modules. Annotations are a means of specifying metadata, or configuration data, for a RAR module in the class files that make up the module.- Connection factory JNDI name practices
Observe the conventions of the JNDI service in WAS when we create connection factory JNDI names.
Related:
Connection pooling Relational resource adapters and JCA (ZOS) olaRar.py script file Tune connection pools Disable statement pooling Configure multiple security domains Java EE resource provider or connection factory custom properties collection