The application server uses the classes and other code
that comprise a resource adapter archive (RAR) to support the resource
adapters that you configure.
Before you begin
A RAR file, which is often called a Java™ EE
Connector Architecture (JCA) connector, must comply with the JCA Specification.
You can meet these requirements by using a supported assembly tool
to assemble a collection of Java archive
(JAR) files, other runnable components, and utility classes into a
deployable resource adapter archive (RAR). You can then install the
RAR file in the application server. When you are using optimized local adapters, set up
your server environment in the daemon group before installing the ola.rar file
in the application server. The ola.rar file is located in
the WAS_HOME/installableApps directory.
You can also use the wsadmin scripting file, olaRar.py,
to install the RAR file.
To read about setting
up your server environment, see the topic, Enabling the server environment
to use optimized local adapters. You can read about the olaRar.py script
in the topic, olaRar.py scripting file.
About this task
A resource adapter archive provides the classes and other
code to support a resource adapter for access to a specific EIS, such
as the Customer Information Control System (CICS®).
Therefore, you can only configure resource adapters for an EIS after
you install the appropriate RAR file.Important: When you
use the Install RAR dialog to install a RAR
file, the scope you select on the Resource Adapters collection page
has no effect on where the RAR file is installed. You can install
RAR files only at the node level, which you specify on the Install
RAR page. To create a resource adapter instance at a scope other than
node, after you install the RAR file on each node, create a new resource
adapter instance from the RAR file with the desired scope.
Procedure
- Navigate to the Resource adapter panel.
Click .
- Install a new resource adapter archive.
- Click Install RAR.
A
dialog opens for installing a RAR file and configuring the associated
resource adapter. Only click New if you want to configure a
new resource adapter for a previously installed RAR file.
- Browse to find the appropriate RAR file.
- If your RAR file is located on your local workstation, select Local
path, and browse to find the file.
- If your RAR file is located on your server, select Remote
file system, and specify the fully qualified path to the
file.
- Click Next.
- Configure the resource adapter name and any other properties
needed under General Properties.
For more details
on the settings that you can configure, such as the J2C connection
factories, see the topics Installing resource adapters within applications
and Configuring resource adapters.
- Click OK.
- Optional: Create a new resource adapter instance
from the installed RAR file with a different scope level.
After
you install the RAR file on each node, you can create another resource
adapter from it with any valid scope other than node.
Note:
- If you do not create a resource adapter instance from the installed
RAR at the cluster scope, then you must create identical factories
(connection factories, admin object, and activation specifications)
at the node level on each of the nodes in the cluster. By creating
a cluster-scoped resource adapter instance from the RAR, you provide
a placeholder for your factories and circumvent the need to create
identical factories at the node level for each of your nodes in the
cluster.
- You must install the RAR on each node using the Install RAR procedure in order for the
cluster-scoped resource adapter to function properly on each node.
- Click Resources.
- Click Resource Adapters.
- Select the scope level and then click NEW.
- Choose the RAR file from the installed archive path.
- Click OK.
Results
You have installed a resource adapter archive that provide
access to the EIS when it is properly configured. If you must configure
more settings, or change some settings that were configured during
the installation process, refer to the topic on configuring a resource
adapter in the administrative console for more information.