Chapter 12. J2EE Connector Architecture scenario 435
address space, such as a native Java process running under the z/OS UNIX
service, to invoke a CICS transaction. The CICS program is invoked using a
mirror transaction that resides in the same CICS region as the CICS application.
EXCI calls can be routed to any CICS region within a sysplex, which means that
the CICS application can reside in a different z/OS system from the CICS
Transaction Gateway.
Figure 12-27 Remote CICS Transaction Gateway on z/OS
12.5.2 WebSphere Application Server V6 configuration
This section describes the runtime setup for the application in WebSphere
Application Server V6. It consists of the following steps:
򐂰 Installing a CICS ECI resource adapter
򐂰 “Configuring a connection factory” on page 437
򐂰 Configure the bus
Installing a CICS ECI resource adapter
To install the CICS ECI resource adapter in WebSphere Application Server:
1. Locate the CICS ECI J2C resource adapter archive (RAR) file.
The CICS ECI adapter we used is available with the Rational Application
Developer and Rational Software Architect in the following location:
<Rational_Install>\Resource Adapters\cics15\cicseci.rar
2. Open the WebSphere administrative console and select Resources
Resource Adapters in the navigation tree.
3. Click the Install RAR button to install the .rar file into WebSphere.
4. Browse to the cicseci.rar file and click Next. See Figure 12-28 on page 436.
TCP
CICS Transaction
Gateway
JNI
CICS Server
CICSECI
Resource
Adapter
WebSphere Application
Server
EJB
CCI
Distributed platform
Gateway
Daemon
z/OS
EXCI
436 Patterns: Implementing Self-Service in an SOA Environment
Figure 12-28 Installing the RAR file
5. In the next panel, leave all the fields blank so that WebSphere uses the
values from the RAR file deployment descriptor. Click OK. This installs the
resource adapter file. You will see an entry in the resource adapter list called
ECIResourceAdapter. Next we add the resource adapter definition.
6. Click New.
7. In the Resource Adapters Configuration form:
Set the Name to cicseci.
Select the following archive path:
${CONNECTOR_INSTALL_ROOT}/cicseci.rar
Click OK.
Create a J2C authentication data entry
The authentication data entry will be used to access the CICS system.
To add a J2C authentication data entry, do the following tasks:
1. Select Security Global Security.
2. Under the Authentication section expand JAAS configuration and select
J2C Authentication data/
Chapter 12. J2EE Connector Architecture scenario 437
3. Click New.
4. Provide an alias for use when defining this to a resource, and supply a user ID
and password with the authority to access CICS.
Configuring a connection factory
To add a connection factory for the application, perform the following tasks:
1. Select Resources Resource Adapters in the navigation tree.
2. Click the new cicseci in the resource adapter list.
3. Under Additional Properties click J2C Connection factories.
4. In the J2C Connection factories form click New.
5. In the J2C Connection factories General Properties form, shown in
Figure 12-29, provide the following information:
Figure 12-29 J2C Connection Factories General Properties
–Name: MartAccountCFRef
JNDI name: eis/MartAccountCF
Select the authentication data entry you created in the drop-down list for
the component-managed authentication alias.
Click OK.
6. Click the new MartAccountCFRef in the J2C Connection Factories list.
7. Under Additional Properties click Custom Properties and complete the
required connection properties for CICS:

Get Patterns: Implementing Self-Service in an SOA Environment now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.