OS 2200 TIP Application Configuration Properties

Refer to Communications Interface for Transaction Applications Configuration and Operations Guide for information on configuring CITA on the OS 2200 server.

The following properties apply to OS 2200 TIP data source projects:

Property	Description
Description	A description of the TIP COBOL application and data source project.
OS 2200 Host Name	The Domain Name Server (DNS) name on which CITA is configured to listen. By default, CITA listens on all IP addresses configured for the COMAPI process, in the CPComm/CPCommOS configuration. Alternatively, the CITA configuration may define an explicit IP address using the LIP parameter, so that CITA will only listen on the specified IP address. *Note:* To deploy an application on the ePortal platform and before staging the application, ensure that the host name matches the back-end server name that is configured in ePortal Manager. The deployment fails if the host name does not match the back-end server name.
OS 2200 Port Number	The port number used to connect to the TIP COBOL application. This number matches the port number configured in CITA. A port number must be an integer in the range 1-65535.
Use Secure Connection	If set to True, the application uses a secure connection when connecting to the ClearPath server. A port number must be an integer in the range between 1-65535.
Connection Timeout (Seconds)	The amount of time in seconds allowed for a connection to occur. Connection timeout value must be an integer in the range of 0-120. The default is 30 seconds.
Reply Timeout (Seconds)	The amount of time in seconds allowed for a reply to be received. The value can be any 32 bit integer. The default is 20 seconds.
Reuse Connection	If True (checked), when a connection is no longer needed, the connection is placed into a pool of unused connections so that it can be reused by a future request. The connection remains in the pool for the amount of time specified by the Reused Connection Timeout value. If False (unchecked), a connection is closed when it is no longer needed. The default value is True (checked).
Reused Connection Timeout (minutes)	The amount of time, in minutes, that an unused physical connection remains open if the Reuse Connection value is True (checked) The default value is 5 minutes.
OS 2200 Character Set	The character set used for the data that is transferred to and from the TIP COBOL application. Refer to Translation Considerations.
Default TIP Transaction Code	This value is optional and can be left blank. Whenever an ePortal server message is sent to the OS 2200, the value of the metadata field tiptrancode__ is used as the TIP transaction code. However, if the field tiptrancode__ is null or empty, then the value of the default TIP transaction code is used instead. Refer to Metadata Fields for more information.
Reconnect on Send Error	If selected, the TIP Connector closes the current connection when a failure occurs while sending a message to the ClearPath application. It then creates a new connection and attempts to send the message again. If this second retry fails, an error is reported to the client application. If cleared, the TIP Connector immediately reports an error back to the client application when a failure occurs while sending a message to the ClearPath application. *Note:* By default, the checkbox is selected to maintain compatibility with the previous behavior, which is to retry sending the message on a new connection; however, this may not be appropriate always depending on how the host application is designed. To select or clear the checkbox, consider the following: For stateless applications, it is generally appropriate to reconnect and send the message again. After a send failure, if you want the system to immediately retry sending the message, select the checkbox. If your application is stateful, it is recommended to clear this checkbox. A second attempt with a different host connection could either fail or it may be inappropriate within the new session context.
Validate New Connection	If selected, attempts to verify if the connection is usable after it is created. If cleared, attempts to use the connection after it is created. The software will assume that the connection is viable. *Note:* By default, the Validate New Connection checkbox is selected.
Enable Redundant Connections	If selected, the ePortal application is enabled to communicate with the redundant host applications at the same time.
Redundant Connection List	The string that specifies the redundant connections. Redundant connections are specified in a string. Each redundant connection specification is separated by a semicolon. Each connection specification consists of Name = Value strings, separated by commas. Name can be any DataSource epconfig tag name (varies by DataSource type). The Names are the element tag names in the DataSource.epconfig file. Names are case-sensitive. Example: HostName=Host1, PortNumber=1234; HostName= Host2, PortNumber=4567 *Note:* To deploy an application on the ePortal platform and before staging the application, ensure that the host name matches the back-end server name that is configured in the ePortal Manager. The deployment fails if the host name does not match the back-end server name.
Redundant Connection Load Balancing	Specifies the load balancing method used by this application. The possible values are: RoundRobin and FailOver. In the RoundRobin method, the Orchestration connect processing rotates in round-robin style to select the application connection to be used when establishing a session. For stateful connections, the selected connection is used throughout the session. If an application connection is unreachable during the connect processing, the next connection in the list is tried. If all connections are unreachable, the connect failed event is raised. An unreachable application connection is removed from the list of connections. In the FailOver method, the Orchestration connect processing always attempts to establish a session using the primary connection. If the connection is unreachable, then the connection is established using the next connection in the list. If all connections fail, the usual error is returned. If the primary connection becomes unreachable, the next reachable connection is promoted to primary connection.
Redundant Connection Retry Interval	The maximum time specified in minutes before retrying an unreachable connection. The actual time between connection retries will gradually increase until this value is reached. The value must be a non-negative integer value.