Reference

The JCA LU 62 Connector uses dynamic link libraries (DLLs) to execute CPIC native calls to the communications server.

Different DLL files are provided for different operating systems and communications servers:

▪ lu62jwrap.dll for Windows version of IBM Communications Server.

▪ liblu62jwrap.so.aix for AIX . Rename liblu62jwrap.so.aix to liblu62jwrap.so.

▪ liblu62jwrap.so.aix64 for 64-bit AIX. Rename liblu62jwrap.so.aix64 to liblu62jwrap.so.

▪ liblu62jwrap.so.linux for LINUX. Rename liblu62jwrap.so.linux to liblu62jwrap.so.

▪ lu62jwrap.dll.winj2c_AIXLinuxClient for Windows Communication Server Remote API Client with the Server of CS on AIX or Linux. Rename lu62jwrap.dll.winj2c_AIXLinuxClient to lu62jwrap.dll

After you install UDTT, these DLL files are in the <toolkit_root>\lib\commsdirectory. Rename the appropriate DLL and install it in a directory that is accessible through the environment variable. Except lu62jwrap.dll.winj2c_AIXLinuxClient, the other DLLs can be used both on client and server of Communication Server.

The following table lists the protocols that the SNA JCA LU62 Connector uses to create and use an LU to LU session and provides information on the values you should use.

The managesResponse parameter determines whether the connector (true) or the connector's client application (false) handles the responses.

The following are the conversation states for sending and receiving messages. The normal flow for these messages is half-duplex flip-flop.

▪ The connector is in the RECEIVE state after it performs a successful connectionFactory.getConnection(establishConversation) with the outgoing attribute set to false.

▪ The connector is in the SEND state after it performs a successful connectionFactory.getConnection(establishConversation) with the outgoing attribute set to true. If the connector receives an Lu62Message after SYNC_RECEIVE(readData) has the CDI attribute set to true, the application enters the SEND state and is able to send data because its partner has entered the RECEIVED state.

▪ The SYNC_SEND(sendAndPrepareToReceive()) method sends the data to the partner and causes the local LU to enter the RECEIVE state.

The application must issue the closeConversation() method only when the connector is in the SEND state. Before the application finishes, it should properly close any conversations it used. If the application finishes without closing the conversations, the sessions and Lu62Conversation could end abnormally.

The recommended pacing value is 0. Other values may have a negative impact on performance.

The Communications Server provides session security for the LU62Conversation. Both sides of the session have the session security password defined and the connector and its client encrypt and exchange the password when establishing the LU-LU session.

The following table lists the attributes of the Lu62Connector tag. These attributes configure the LU-LU session. Set these attributes in the J2C property configuration in the application server resource adapter page or set it in the WSDL file when using WSIF to access the connector.

Name of the transaction program. Required only when outgoing="false", optional when outgoing="true". Note that the tpName property will override the TP name defined in the side information of Communication Server when outgoing=”true”.

The max connections of WAS connection factory pool. Required only when application use dynamic TP.

The max connections limitation for each TP. Required only when application use dynamic TP.

Side information name defined in Communication Server. Required only when outgoing="true".

Number of times the connector attempts to create the conversation before throwing an exception.

Number of milliseconds that the connector waits before retrying to create the conversation.

True to require a receipt from the receiver that confirms delivery of the message.

True if the connector is using chaining to handle messages that exceed the maximum RU size. The connector also builds SNA headers from the sent information message and sends the Change Direction Indicator (CDI) along with a Last In Chain (LIC).

Number of milliseconds that the connector waits before failing the attempt to create the conversation.

Indicates whether the code page is converted when tracing the message to/from host. Note the converting is only used for trace. The default value is true.

The code set of host used to translate code page between host and Application. The default value is Cp037.

The code Page of Application Sever used to translate code page between application and host. The default value is 8859_1.

Indicates whether to re-establish LU62 conversation for existing connection in WAS connection pool. The default value is false.

The SNA JCA LU62 Connector is packaged as a resource adapter module in the snalu62.rar file This file contains the classes and the deployment descriptor containing the resource adapter configuration attributes. The file is in <toolkit_root>\lib\comms directory. You can use the RAR file to deploy the connector as a standalone unit in the application server.

The UDTT JCA LU0/LU62 Connector supports the following versions of Communication Server and also supports the Remote API Client for these Communication Server:

▪ Communication Server for Windows

▪ Communication Server for AIX

▪ Communication Server for Linux

For Communication Server for AIX for Linux, the remote API client is on Windows(both 32bit and 64bit), Linux and AIX.

When using the remote API Client, the Communication Server Remote API Client is installed on the WebSphere Application Server, and the Communication Server resides on a remote machine.