SMS Invision

The SMS Invision communication point connects to a remote TN3270 server using the LU2.1 protocol and listens for connections on the port specified by the Remote Host and Remote Port properties. The optional properties Local Address and Local Port can be used to force the communication point to connect using a specific interface and local TCP/IP port number.

Generally, the TN3270 server is a Microsoft® SNA server or IBM communications server. The Remote Port for these systems is generally 23.

The SMS Invision communication point also needs to know which Logical Unit (LU) (also known as the terminal ID) to connect to, and the CICS log-on string. The LU is normally an 8 character string and for SMS outbound interfaces this would be the terminal ID for the interface.

The CICS log-on string determines whether the connection is to the Test or Production system. This string can be the CICS region to connect to or be of the form:

LOGON APPLID=CICS????

For communicating between two Transaction Programs (TPs) using the LU6.2 protocol, use the SNA LU6.2 communication point.

Supported Operational Modes: Input, Output.

Configuration Properties

Property	Description
Remote Host	The hostname or IP address of the TN3270 server to which you want to connect.
Remote Port	The port number on the remote host to which to connect. This should generally be set to `23`.
Local Address	The hostname orIP address of the local interface to which to bind the socket connection (all interfaces if empty).
Local Port	The port number to which to bind the local socket.
Use SSL	Options: `True`, `False`. Default: `False` If `True`, the secure socket layer is used for this connection and all messages are encrypted. Refer to TLS/SSL Support in Rhapsody for details on TLS/SSL (Transport Layer Security/Secure Sockets Layer) support in Rhapsody. Refer to http://en.wikipedia.org/wiki/Ssl for details on SSL. It is recommended that SSL be enabled for TCP Client communication points whenever it is supported by the remote server.
SSL Protocol Mode	The SSL Protocol Mode that should be used. Defaults to `TLSv1.2` for newly created communication points. Refer to SSL Protocol Versions for details.
SSL Cipher Suites	Limits the SSL cipher suites that can be used, allowing a minimum encryption level to be set: `Very Strong Cipher Suites (AES-256)`. `FIPS Cipher Suites (AES-128, AES-256, TripleDES-168)` (default). `Strong Cipher Suites (AES-128, AES-256, TripleDES-168, RC4-128)`. `Weak Cipher Suites (AES-128, AES-256, TripleDES-168, RC4-128, DES-56, DES-40, RC-40)`. Refer to SSL Cipher Suites for details.
Use SSL Client Mode	Options: `True`, `False`. Default: `False` If `True`, SSL client mode is implemented.
Secure Keys	Identifies the private keys used for authenticating Rhapsody's end of the SSL connection. When configured with a private key, the SSL client supports SSL client authentication if requested by the SSL server. Refer to Client Authentication for details.
Trusted Certificates	Identifies the trusted certificates used at the non-Rhapsody end of the SSL connection. If it is not configured with the SSL server's certificate, then this SSL client operates in anonymous server authentication mode. It is highly recommended that the server's certificate always be provided here to allow server authentication to be performed. Refer to Server Authentication for details.
CICS Logon String	The string to send to the mainframe once connected to the LU.
LU Name	The name of the 'Logical Unit' to which to connect. If empty, then the TN3270 server automatically chooses one for you.
Use SC63 Compression	Options: `True`, `False`. Default: `False` If `True`, the messages sent are compressed using SC63 space compression and received messages are decompressed.
Region Code	The two character region code configured on the SMS Invision system.
Hospital Code	The two character hospital code configured on the SMS Invision system.
System ID	The two character system ID that determines the destination of the messages sent to the SMS Invision system.
Log Connections	Options: `True`, `False`. Default: `False` If `True`, establishing and dropping of all connections to the communication point are logged to the log file specified in the Connection Log File property. Use of this logging facility slows the communication point down considerably. It is intended for debugging purposes and should not generally be used.
Log Data	Options: `True`, `False`. Default: `False` If `True`, all data passed over the connections of the communication point is logged to the log file. This is potentially a lot of data.
Log Data As Hex	Options: `True`, `False`. Default: `False` If `True`, the hexadecimal representation of the data is logged to the log file. If `False`, the data is logged exactly as it is as it passes over the communication point connection.
Connection Log File	The full file name (path and file name) of the file on the server to which to log the information.
Extra Information	Specify if timestamps should be logged with each event.