CICS TG V9.1 enables simple and rapid mobile integration of your enterprise CICS Transaction Server (CICS TS) family or TXSeries™ environment. You can build on your existing, proven architecture to quickly provide mobile connectivity to back-end systems by using JavaScript™ Object Notation (JSON) web services.
A complete overview of the IBM CICS Transaction Gateway V9.1 products:
CICS Transaction Gateway for z/OS V9.1
CICS Transaction Gateway for Multiplatforms V9.1
CICS Transaction Gateway Desktop Edition V9.1
Product datasheet: https://ibm.biz/cicstg91datasheet
Other attributes of interest (from http://www-01.ibm.com/support/knowledgecenter/SS7K4U_8.5.5/com.ibm.websphere.zseries.doc/ae/cdat_dsfailover.html?cp=SS7K4U_8.5.5%2F1-3-0-22-3-0-0-2):
failureThreshold
Values: Must be an integer and > 0.
Description: The failureThreshold property is only read if the failureNotificationActionCode or alternateResourceJNDIName property is set to valid value. If the failureThreshold property is not set or is set to an invalid number the default value of 5 is used. The integer value specified for the failureThreshold is the number of consecutive resource exceptions that must occur for a particular resource before notification is sent or failover occurs.
The following is an example of how this value works: If the failureThreshold property is set to 5 for data source B, then data source B must get five consecutive resource exceptions while attempting to establish connections, with no successful attempts in-between these failures, before notification is sent or the resource can fail over. An attempt to send the notification or fail over is made after five consecutive resource exceptions occur. However, in a multi-threaded environment, after the failure threshold value is reached, the timing of the notification or fail over might occur after additional resource exceptions.Attention: Resource exception counters are not shared between resources. Resource exceptions must be consecutive to reach failure threshold.
alternateResourceJNDIName
Values: String value containing a direct JNDI name.
Description: An alternate connection factory or data source resource should be like the primary resource. Provide the JNDI name of the alternate resource to enable the fail over feature.
Advanced fail over properties
resourceAvailabilityTestRetryInterval
Values: int value, default is 10.
Description: The test connection interval by default is 10 seconds. Every 10 seconds, the test connection thread attempts to test the primary resource. Depending on system resources, this value can be change from 1 -MAXINIT seconds.
enablePartialResourceAdapterFailoverSupport
Values: boolean value, default is false.
Description: If this value is true, fail over to the alternate resource occurs, but fail back to the primary is manual. This property can be set if the resource adapter being used does not meet the requirements for connection fail over, for example, it does not have testConnection implemented or it throws a not supported exception.
disableResourceFailOver
Values: boolean value, default is false.
Description: If this value is true, automatic fail over does not occur.
disableResourceFailBack
Values: boolean value, default is false.
Description: If this value is true, automatic fail back does not occur.
populateAlternateResource
Values: boolean value, default is false.
Description: If this value is true, the alternate resource is populated with connections to maximum connections. Every attempt is made to keep the alternate resource at maximum connections. If the database goes down for the alternate resource, the stale connections are removed and the populate thread repopulates the alternate resource when the database is available. You can dynamically enable and disable the populate alternate resource using the Mbean operations, disablePopulateAlternateResource and enablePopulateAlternateResource.Attention: You might see performance gains during a failover with populate alternate resource enabled, but, the cost is high to keep the alternate resource populated. Most of the cost is in keeping twice the number of connections typically required for one data source. Because connections are large objects, keeping the connections uses additional memory resource on the server and extra resource on the database.
<number>
The Common Language Runtime (CLR) is the virtual machine component of Microsoft's .NET framework
Point to John’s library page.. As it has public links to all TG related articles…