MCP COBOL Application Configuration Properties

The following properties apply to MCP COBOL data source projects:

Property	Description
Description	A description of the functionality of the MCP COBOL data source project.
Window Name	The Transaction Server window name to which the ePortal server message connects. The window must be a registered in Transaction Server as a valid window name.
Server Name	The Domain Name Server name of the MCP server on which the COBOL application resides. *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.
Connector PSH Endpoint	The port number that is used to connect to the MCP COBOL application. This value must match the endpoint used by the Connector PSH on the MCP system. The value can be between 1 and 65535. The default value is 7952.
Station Prefix	The Station Prefix property is used to specify the station prefix to be used when the Connector PSH, on the MCP, creates a station name for the connection from the ePortal application to the Transaction Server window. This resulting station name can be used to monitor activity on the MCP server. If no value is specified, a default value of CPEPORTAL is used. When ePortal establishes a new connection, by default the Connector PSH software on the MCP automatically appends /<uniquenum> to the end of the station prefix to generate a unique station name, where <uniquenum> is a unique number. Optionally, you can configure one or more variable references in the station prefix. These variable references are resolved at runtime as follows: $IPADDRESS variable ePortal replaces each reference to $IPADDRESS in the Station Prefix property with the IP address of the client user (for example, the system where the user is running the Web browser), if known. *Notes:* ePortal does not know the IP address for Web service consumers. Therefore, if your presentation is a Web service application, $IPADDRESS is replaced with the empty string. If the browser IP address is the loopback address (i.e., 127.0.0.1 for IPv4, or ::1 for IPv6), $IPADDRESS is replaced with the empty string. This should never occur when the application is deployed to the ePortal platform. However, this occurs when testing on your development system with IIS Express.
	*Notes:* The client system (for example, the system where the user is running the Web browser) provides the IP address. If this address is an IPv4 address, then the replacement follows the IPv4 address replacement rule described below. If this address is an IPv6 address, then the replacement follows the IPv6 replacement rules described below. IPv4 address replacement rule: Each period character (.) is replaced with an underscore character (_). IPv6 address replacement rules: Link Local or Site Local IP addresses can include a Zone ID. A Zone ID consists of a percent character (%) followed by a number. If the IPv6 address contains a percent character, $IPADDRESS is replaced with the empty string. Each colon character (:) is replaced with a hyphen character (-). So each node of the IPv6 address is separated by a hyphen character instead of a colon. However, a maximum of three nodes of the IPv6 address can be placed in each node of the resolved station name. So, a forward slash character (/) is used to separate every third node. Any lowercase characters are converted to uppercase.
	# variable The Connector PSH on the MCP will replace the first reference to # character with a unique number so that the resulting station name is unique. *Notes:* This feature requires the CONNECTORPSH-054.1A.2 IC or higher. If the Station Prefix property contains the character #, then Connector PSH will not append /uniquenum as described above. Connector PSH will replace only the first occurrence of #. If # appears more than once, the result will be an invalid station name, and your application will receive a runtime exception. If the Station Prefix property contains a number next to the # character, a duplicate station name may result. For example, you get a duplicate station name when specifying the station name prefixes of CPEPORTAL#1 and CPEPORTAL1#, as the station name CPEPORTAL11 can be formed by both of these station name prefixes. If a duplicate station name occurs, your application will receive a runtime exception. The resulting station name must adhere to the Transaction Server station name format; otherwise, your application will receive a runtime exception. Examples: You do not configure anything for the Station Prefix property. When the first connection occurs, the station name will be CPEPORTAL/1. If another connection occurs while the first connection is still active, it will use the station name CPEPORTAL/2. You configure the Station Prefix as MYPREFIX. When the first connection occurs, the station name will be MYPREFIX/1. If another connection occurs while the first connection is still active, it will use the station name MYPREFIX/2.
	You configure the Station Prefix as IP$IPADDRESS/WEB#. Your presentation application is a Web service. When the first connection occurs, the station name will be IP/WEB1. If another connection occurs while the first connection is still active, it will use the station name IP/WEB2. Your presentation application is a Web presentation or a mobile Web application presentation. You perform development tests under the Visual Studio debugger. Visual Studio starts IIS Express to host your application. When the first connection occurs, the station name will be IP/WEB1. If another connection occurs while the first connection is still active, it will use the station name IP/WEB2. The IP address of the browser client is the IPv4 address 192.63.246.114. When the first connection occurs, the station name will be IP192_63_246_114/WEB1. If another connection occurs from the same client while the first connection is still active, it will use the station name IP192_63_246_114/WEB2. The IP address of the browser client is the IPv6 address fec0::5:588f:aa0a:391a:2019. When the first connection occurs, the station name will be IPFEC0--5/588F-AA0A-391A/2019/ WEB1. If another connection occurs from the same client while the first connection is still active, it will use the station name IPFEC0--5/588F-AA0A-391A/2019/ WEB2.
Connect Timeout (seconds)	The amount of time before a connection times out. The value can be any 32 bit integer. The default is 30 seconds.
Reply Timeout (seconds)	The amount of time allowed for a reply to be received. The value can be any 32 bit integer. The default is 20 seconds.
Reuse Connections	If checked, allows a stateless application to reuse a physical connection when the same security credentials are met. Requests are made to the same station ID and when not in use, the connections are pooled for the time specified by the Reused Connection Timeout value.
Socket No Delay	If checked, sets the NoDelay flag for the underlying socket connection to true. If NoDelay is true, the Nagle algorithm is disabled. Disabling the Nagle algorithm may improve response time when sending small packets.
Reused Connection Timeout (minutes)	The amount of time in minutes that an unused physical connection remains open if the Reuse Connection is checked. The default value is 1 minute.
Application Character Set	The character set used for the data that is transferred to the MCP server.
Character Set for COMS Configuration	The character set used on Transaction Server specific items such as window name, user code and password. If the Transaction Server configuration for the MCP application includes a particular converter name set, set this field to match that value. The allowable values are the same as the Character Set values with the default being EBCDIC-ASERIES.
Uses EGI to denote last send	If checked, indicates that the Transaction Server configuration for the MCP application allows an End-Of-Group indicator to be sent after the last message of a group of multiple messages has been sent. This allows the MCP application to send a variable number of outputs in response to a single input.
Discard Open Window Response	If checked, indicates that the ePortal MCP COBOL runtime ignores the record returned when the window is started.
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.