Before you can test your Java™ application with a
CICS® region, you must check that the required tools are
installed and also configure your local work environment.
About this task
Stabilized feature:
Consider updating applications to use JCICS Link as an alternative. See also Stabilization notices and discontinued functions.
6.3
beta The JCA ECI adapter in
Liberty JVM server is removed as of CICS TS 6.3.
6.16.2The JCA ECI adapter in Liberty JVM server
is stabilized.
To create a local work environment where you can test your Java applications with a CICS region, complete the
following steps.
Procedure
-
Download and install the Eclipse IDE for Java EE
Developers with WebSphere® Developer Tools (WDT). Then,
install a local WebSphere Liberty
server instance, create the Hello World JavaServer Pages (JSP) and test by deploying the Hello World
web application on the server.
For more information, see
Get Started available at
Open Liberty®.
-
Install the JCA remote ECI resource adapter from the Liberty Repository. You can install a feature from the repository by using the installUtility
command:
<liberty_install>/bin/installUtility install
--acceptLicense jcaRemoteEci-1.0
-
Add the usr:jcaRemoteEci-1.0 , localConnector-1.0 ,
and webProfile-6.0 features to the server.xml file.
For example, in Eclipse expand the WebSphere Liberty project and
then expand servers . Double-click defaultServer to
edit server.xml . Click the source tab and add the
following features:
<featureManager>
...
<feature>usr:jcaRemoteEci-1.0</feature>
<feature>localConnector-1.0</feature>
<feature>webProfile-6.0</feature>
...
</featureManager>
-
Add a connectionFactory and
properties.com.ibm.cics.wlp.jca.remote.eci to server.xml.
The connectionFactory jndiName is used by the application to create a
connection. The properties.com.ibm.cics.wlp.jca.remote.eci is used to configure
the JCA remote ECI resource adapter and at a minimum must specify serverName
with the host name and port number of the IPIC connection defined by the TCPIPSERVICE resource.
Note: You might need to specify extra parameters. For example, to use Secure Sockets
Layer (SSL) and a user ID and password. Table 1 lists the available parameters. Table 2 lists the
ECI resource adapter deployment parameters that are not supported by the JCA remote ECI resource
adapter. For more information, see
ECI resource adapter deployment parameters.
<server>
...
<connectionFactory id="com.ibm.cics.wlp.jca.local.eci" jndiName="eis/ECI">
<properties.com.ibm.cics.wlp.jca.remote.eci serverName="tcp://
hostname
:
port"/>
</connectionFactory>
...
</server>
Table 1 shows the JCA remote ECI resource adapter properties that are supported.
Table 1. Supported JCA remote ECI resource adapter
properties
| JCA object: property |
Notes |
|
applid
|
|
|
applidQualifier
|
This property is required. |
|
cipherSuites
|
|
|
ipicHeartbeatInterva l |
|
|
ipicSendSessions
|
This property default is 5. |
|
keyRingClass
|
|
|
keyRingPassword
|
|
|
password
|
|
|
socketConnectTimeout
|
|
|
serverName
|
This property is required. |
|
traceLevel
|
|
|
traceRequest
|
|
|
userName
|
|
Table 2 shows CICS Transaction Gateway ECI resource adapter deployment parameters that are not supported by the JCA remote ECI resource adapter.
Table 2. JCA remote
ECI resource adapter properties that are not supported
| JCA object: property |
|
interceptPlugin
|
|
portNumber
|
|
tPNName
|
|
tranName
|