Tip:
Highlight text to annotate it
X
Hi, my name is Pete Dally and I'm the development manager for CICS Transaction Gateway,
IBM's premier connectivity solution for CICS applications.
CICS Transaction Gateway has been in the marketplace for over 13 years
and has over 1500 customer installs worldwide.
This allows our clients to extend the investments they've made in CICS technologies
to new environments such as WebSphere application server.
I'm really excited to tell you that we've just released CICS Transaction Gateway version 9,
delivering more choice and capability than ever.
So what's new in version 9?
Well let's go and find some of the team to tell you more about it.
Our customers are demanding higher volumes of requests with larger payloads than ever before,
so we've added the capability for CICS Transaction Gateway for z/OS to operate within a 64-bit address space.
This means that using IPIC, CICS TG can now handle thousands of concurrent requests
with payloads that far exceed the 32K limit of EXCI.
Also, customers migrating away from EXCI to IPIC can now specify an ECI timeout for each IPIC connection
providing more flexibility than configurations using EXCI.
Security is a major focus of version 9.
CICS Transaction Gateway can now be configured to use SSL with IPIC connections in three-tier topologies.
We've also enhanced the .NET API to support SSL connections between .NET client applications and the gateway.
Additionally, password phrase support can now be used with EXCI connections.
For statistics we have added the ability on multiplatforms and desktop edition to record historical statistics to an XML file.
CICS Transaction Gateway version 9 takes advantage of the
WebSphere Cross Component trace facility, available in WebSphere Application Server version 8.5.
This allows an application request to be tracked through the different components of the enterprise,
facilitating problem diagnosis and performance tuning.
In version 9 we have enhanced existing support for dynamic server selection
by adding an additional monitoring exit which is invoked after DSS routing decisions have been made, but before a request is sent to CICS.
We have also made the client IP address available to CICS request exits,
allowing routing decisions to be made based off the location of the client.
CICS Request Exits now provide the same information for all types of ECI request in both XA and non-XA environments.
For application development, version 9 offers greater flexibility for the ECI and ESI version 2 APIs.
Remote client applications written in C and C++ can now operate as 64-bit processes.
In addition ECI version 2 now supports asynchronous ECI calls.
As you have just heard, the team have added some great new features in CICS Transaction Gateway version 9.
For further information, including the latest redbooks, datasheets, podcasts and other videos,
please visit the CICS Transaction Gateway web site.
And remember, you can also contact your IBM sales representative if you'd like some more information.
Thank you.