OS 2200 UTS Application Configuration Properties

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

Property

Description

Description

A description of the UTS application and data source project.

UTS Source Project Name

A read-only property that indicates the name of the UTS data source project that was given when the project was created.

Connection Timeout (Seconds)

The amount of time, in seconds, allowed for a connection to occur. The value can be any 32 bit integer.

The default is 30 seconds.

Reply Timeout (Seconds)

The amount of time, in seconds, allowed for a reply to be received. Connection timeout value must be an integer in the range of 0-120.

The default is 20 seconds.

Connector Type

A read-only property with a value of OS2200UTS.

OS 2200 Host Name

The Domain Name Server (DNS) name on which the TIPCSU, or RSDCSU processes are configured to listen in the CPComm/CPCommOS configuration.

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.

OS 2200 Port Number

The port number that is used to connect to the backend server.

Terminal Identifier Prefix

A unique, two-character prefix placed at the beginning of a dynamically generated terminal ID.

OS 2200 Host Operation Mode

The name of the host application or host operating mode to access.

Specify DEMAND for a demand session or an application name, such as UDSSRC for a TIP session.

Transport Server Access Point (TSAP)

The desired TSAP to be used.

Specify TIPCSU for a TIP connection or RSDSCU for a Demand connection.

Initial Transaction

The transaction code or executable file used to initiate the UTS application.

Use Secure Connection

If selected, the application uses a secure connection when connecting to the ClearPath server.

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 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.