Using the CCI API to Develop Applications
Integrating OracleAS Adapter for IMS/TM with OC4J 2-3
Using the CCI API to Develop ApplicationsYou can develop applications to run adapter interactions using the Common Client
Interface (CCI) API.
Perform the following steps to use the CCI API with the J2CA 1.5 IMS/TM adapter:
1. Select a ConnectionFactory for the J2CA 1.5 IMS/TM adapter.
serverName Sets the TCP/IP address or host name where the Oracle Connect
daemon is running. The daemon runs on the computer specified
at the beginning of "Setting Up the IBM OS/390 or z/OS Platform
in Oracle Studio" on page 6-14.
See Also: Appendix C, "Advanced Tuning of the Daemon" for
details about the daemon.
workspace Specifies the name of an Oracle Connect server workspace to use.
The default workspace is Navigator.
See Also: "Workspaces" on page C-7 for details about workspaces.
portNumber Specifies the TCP/IP port where the Oracle Connect daemon is
running on the server. The default port is 2552.
userName
(optional)
Specifies a user who can access the Oracle Connect server. The
user is defined in the Oracle Connect daemon configuration.
See Also: "Daemon Security" on page C-5 and "WS Security" on
page C-16 for details about users allowed to access an Oracle
Connect server.
password
(optional)
Specifies a valid password for the user..
persistentConnecti
on
(optional)
Set to true or false. When set to true, connections can persist
across multiple requests or connection context changes. It is
recommended to set this property to true.
keepAlive
(optional)
Set to true or false. When set to true, the socket used for the
connection is always kept open. It is recommended to set this
property to true.
firewallProtocol
(optional)
Specifies the firewall protocol used: either none or fixedNat (the
Nat protocol using a fixed address for the daemon). The default
value is none.
connectTimeout
(optional)
Specifies the connection timeout in seconds. The default is 0,
meaning that there is no connection timeout.
encryptionProtocol
(optional)
Specifies the name of encryption protocol to use. The default is
null. The RC4 protocol is supported.
encryptionKeyName
(optional)
Specifies the name of the symmetric encryption key to use.
encryptionKeyValue
(optional)
Specifies the value of the symmetric encryption key to use.
fakeXa Set to true of false. When set to true, the XA APIs are
internally converted to local transaction APIs.
Table 2–1 (Cont.) OC4J Connection Properties
Property Description