CICSConnection configurable service

Select the objects and properties that you want to change for the CICSConnection configurable service.

For CICSConnection configurable services, you must stop and start the integration server for a change of property value to take effect.

Supplied configurable services that are created for each integration node	Properties for each configurable service that is defined	Description of properties
None	cicsServer	The value that is used by the CICSRequest node to determine the connection to CICS® Transaction Server for z/OS®. One of the following connection methods can be specified: A direct connection to CICS (two-tier): If making a direct connection from IBM® Integration Bus to CICS, the cicsServer property must contain the URL of the CICS Transaction Server for z/OS region where the program exists. The URL allows you to specify a protocol, host name, and port number, which is the minimum information you need to connect to the CICS target region. The URL must be made up of the following structure: `protocol`://`hostname`:`port` Where: `protocol` can be tcp or ssl. `hostname` is the Internet Protocol version 4 (IPv4) TCP/IP address or DNS-resolvable host name of the CICS host. `port` is the port number of the TCPIPSERVICE listener in CICS that is listening for IP InterCommunications (IPIC) protocol requests over TCP/IP or Secure Sockets Layer (SSL) protocol. You can enter an integer in the range 1 - 65535. For example: tcp://mycicsregion.com:12345 or ssl://mycicsregion.com:56789. You can obtain the `hostname` and `port` values from the IPIC TCPIPSERVICE definition in the CICS target region. A connection to CICS through a CICS Transaction Gateway (three-tier): If you make connections to CICS through a Transaction Gateway (CICS TG), The gatewayURL property must contain the URL for the CICS TG to use for the connection, and The cicsServer property must contain the `CICS server definition` that you have specified in the CICS TG (.INI) initialization file. For example, the property can specify the particular CICS region that you want the transaction gateway to connect to. For more information about the two-tier and three-tier connection models, see CICS Transaction Server for z/OS overview for a high-level overview, or CICS Transaction Server for z/OS two-tier connectivity and CICS Transaction Server for z/OS three-tier connectivity for detailed conceptual information.
	clientApplid	The APPLID by which IBM Integration Bus is known to the CICS region. This is not the APPLID of the CICS region. You can enter a maximum of 8 characters. This property is optional.
	clientQualifier	The APPLID qualifier by which IBM Integration Bus is known to the CICS region. You can enter a maximum of 8 characters. This property is optional.
	securityIdentity	The name of the security identity object that is created and configured by the mqsisetdbparms command, which contains the user ID and password to be used by the integration node to authenticate the connection to CICS. For more information about CICS security identity support, see Security identities for integration nodes connecting to external systems.
	connectionTimeoutSecs	The timeout value that is used by the CICSRequest node to set the expiry time in seconds for IBM Integration Bus to establish a connection to the CICS region. The default value for this property is 30, indicating that the CICSRequest node waits for 30 seconds. You can enter an integer in the range 0 - 2147483. Where 0 indicates that no timeout is applied. This property is optional.
	requestTimeoutSecs	The timeout value that is used by the CICSRequest node to set the expiry time in seconds for the CICS program to respond. The default value for this property is 120, indicating that the CICSRequest node waits for 120 seconds. This period does not include the connection time period. You can enter an integer in the range 0 - 2147483. Where 0 indicates that no timeout is applied. This property is optional. When setting this property for a specified configurable service, for example `myCICSConnection`, it is important to remember that the defined value overrides the CICSRequest node Request timeout Basic property value for all nodes that are using the `myCICSConnection` configurable service.
	gatewayURL	The URL to use to connect to CICS Transaction Gateway. If this property is specified, the cicsServer property must contain the `CICS server definition` that you have specified in the CICS TG .INI initialization file. The gatewayURL property allows you to specify a protocol, host name, and port number, which is the minimum information you need to connect to CICS TG. The URL must be made up of the following structure: `protocol`://`hostname`:`port` Where: `protocol` can be tcp or ssl. `hostname` is the Internet Protocol version 4 (IPv4) TCP/IP address or DNS-resolvable host name of the CICS TG host. `port` is the port number of the TCP/IP or SSL protocol listener for the gateway daemon of CICS TG. You can enter an integer in the range 1 - 65535. For example: tcp://mycicstransactiongateway.com:12345 or ssl://mycicstransactiongateway.com:56789. If using SSL, the integration node keyring must trust the CICS TG middle tier. You can obtain the `hostname` and `port` values from the CICS TG .INI initialization file. The default for this property is local, which indicates a direct two-tier connection to CICS.
	keystoreFile	This property specifies the fully-qualified path to the location of the keystore that is to be used when using an SSL connection. If this value is not specified, the keystore that is configured for the integration server will be used. The CICSRequest node uses this as the store for the private and public certificates used to secure the connection to CICS.
	keystorePass	This property specifies the security identity to be used for accessing the keystore.
	egForXARecovery	In a globally-coordinated transaction, the name of the integration server that establishes a connection to CICS for XA recovery. If XA is being used, only the specified integration server can use the configurable service. The clientApplid and the clientQualifier fields must also be configured. Note: This property is not supported on z/OS.