Search results

The CICS Transaction Gateway (CICS TG) is widely used to provide access to CICS COMMAREA-based programs and 3270 transactions from Java environments. This IBM Redbook shows you how to build a robust CICS TG configuration for a variety of different configurations. First we introduce the facilities of the CICS TG, followed by step-by-step explanations of how to use the different protocols (TCP/IP, TCP62, APPC and EXCI) used for communication with a CICS TS V2.2 region on z/OS, and how to secure your CICS region when receiving External Call Interface (ECI) or External Presentation Interface (EPI) requests. Next, we provide details on how to configure the CICS TG V5 on either z/OS or Linux to connect a Java client application to a CICS region. The use of the Secure Sockets Layer (SSL) protocol to encrypt the communication from the Java application to the CICS TG is included in these scenarios. Finally, we offer two scenarios to illustrate how to configure WebSphere Application Server V4 on the Windows or z/OS platforms, to use the supplied ECI resource adapter to allow J2EE applications to make ECI calls to CICS.

This IBM Redbooks publication focuses on application development using the CICS Transaction Gateway V7 programming interfaces for access to CICS, including Java, JCA, C, and .NET client development. This Redbooks publication also includes the exploitation of the new CICS TS V3 Channels and Containers programming model for exchange of large payloads, support for the J2C beans provided by Rational Application Developer, and the invocation of CICS programs from the .NET environment.

How can you manage your CICS Transaction Gateway systems on z/OS so as to meet the growing availability and performance requirements of your business? The CICS Transaction Gateway V7.1 provides a wealth of new systems monitoring functionality, and together with the new IBM Tivoli OMEGAMON XE for CICS TG product and the support for CICS TG statistics in CICS Performance Analyzer for z/OS (CICS PA), provides you with a set of enhanced capacity planning and problem determination capabilities. The first part of this IBM Redbooks publication concentrates on product installation and customization for both the CICS Transaction Gateway V7.1 for z/OS and IBM Tivoli OMEGAMON XE for CICS TG product. The second part of the book highlights the new systems monitoring functionality in CICS Transaction Gateway V7.1 for z/OS and how it is complemented by the new IBM Tivoli OMEGAMON XE for CICS TG product and the support for CICS TG statistics in CICS PA. A set of typical customer scenarios are used to demonstrate the practical usage of the new functions, in the following four problem determination areas: - Diagnosing common problems - Diagnosing system slow downs - High Availability with XA and OMEGAMON XE - Historical data analysis Together, these scenarios can be used to quickly determine the root cause of typical production problems and provide in-depth information to allow you to plan, build, and monitor a highly available CICS Transaction Gateway systems to provide SOA access to your existing CICS applications.

With the emergence of service-oriented architecture (SOA), the options for accessing the existing IBM Customer Information Control System (CICS) assets have become more varied than ever. With this variety comes the complexity of securing these assets. This IBM Redbook is intended for IT architects who are involved in the process of selecting, planning, and designing a secure SOA solution that makes use of CICS assets. This book introduces SOA and the options available for transforming CICS assets into SOA solutions. It then discusses the principles of security, followed by the different security technologies. The book then reviews each technology individually, discussing the security options that are available, the security architectures such as basic authentication, firewalls, and the use of Secure Sockets Layer (SSL) and public key infrastructure (PKI).

The CICS Transaction Gateway (CICS TG) is used widely to provide access to CICS programs from Java environments. It provides the IBM implementation of the J2EE Connector Architecture (JCA). This IBM Redbook introduces the new facilities of the CICS TG for z/OS V6.0 and V6.1, which provide improvements in the areas of transactional integration, systems management, performance, security, and ease of use. Included in this book are a set of configuration scenarios for a variety of different deployment topologies for integrating J2EE applications on WebSphere Application Server with CICS TS for z/OS. This book provides step-by-step explanations about how to configure connections between each tier of the test environment. We show you how to enable support for global transactions which span resources on different systems. We also cover the configuration of CICS TG security, including the use of JSSE for establishing secure SSL connections to the CICS TG.

This IBM Redbook (re)examines most connectivity scenarios between WebSphere Application Server for z/OS Version 6.01 and other application resources on z/OS and is an extension of and update on the WebSphere for z/OS V5 Connectivity Handbook, SG24-7064 . This book covers various connectivity scenarios from architecture, application development, and infrastructure points of view. New scenarios are introduced using WebSphere Default messaging, Web services, and SQLJ. We also updated all scenarios with the usage of Rational Application Developer Version 6. A brief summary of connectivity technology explained in this book is: -Database access using JDBC and SQLJ -JMS 1.1 and WebSphere Default messaging -Calling DB2 Stored Procedures using SOAP -Bi-directional Web services between WebSphere and CICS -J2C connectors to CICS and IMS -RMI-IIOP The technology is explained using sample code, available as additional material for this book.

The Patterns for e-business are a group of proven, reusable assets that can be used to increase the speed of developing and deploying Web applications. The pattern discussed in this redbook, Self-Service::Directly Integrated Single Channel application pattern, covers Web applications needing one or more point-to-point connections with back end applications. Part 1 of the redbook guides you through the process of selecting an Application and Runtime pattern. Next, the platform-specific product mappings are identified based upon the selected Runtime pattern. Part 2 of the redbook provides a set of guidelines for building your Web application with the enterprise tier using Web services, JCA and JMS. These guidelines include technology options, application design, application development, systems management, and security. Part 3 of the redbook teaches you by example how to design and build sample solutions using IBM WebSphere Application Server V4.0 with Web services, JCA and IBM CICS, and JMS and IBM MQSeries.

What is the best method for connecting a Java application to CICS? There are a wealth of options that are available, ranging from using the Java class libraries that are shipped with the CICS Transaction Gateway (CTG), to using the Common Client Interface (CCI) component of the Java 2 Enterprise Edition (J2EE) Connector Architecture. There are also important application development choices to make, such as whether to code to an API directly, or to use a tool such as VisualAge for Java's Enterprise Access Builder. This IBM Redbook examines the strategic Java connection methods for CICS. The focus is on the use of the J2EE Connector Architecture, which is a new Java standard for connecting to legacy Enterprise Information Systems such as CICS. This builds upon the previous IBM Common Connector Framework (CCF) and provides enhanced facilities for deploying into a managed environment, where connection pooling, transactions, and security are managed by a J2EE capable application server such as WebSphere Application Server. We provide comprehensive code examples for the J2EE CCI, as well as the CTG base classes, including the ECIRequest, ESIRequest, and the EPI support classes.

Web-to host integration has become a well-known term and is understood as an integral part of any e-business. A majority of business-critical data and applications reside on IBM host systems such as IBM S/390, IBM AS/400 and IBM RS/6000. Making this information available to new users and using it in new ways across intranets, extranets and the Internet enable companies to reduce costs, improve services, generate new sources of revenue and establish a competitive advantage. The term legacy application extension is used to describe the trend where companies quickly move existing host applications to the intranet, extranet and the Internet without modifying existing applications. IBM Host Integration products provide a complete solution to address the legacy application extension space with solutions to address the needs of all user groups. This book provides a high-level technical overview of IBM Host Integration solutions. It addresses the issues of choosing a solution. The book features WebSphere network products that can be used to integrate the Web with existing customer host systems, including Host On-Demand, Host Publisher, and Screen Customizer. The functions they provide are compared to other Web-to-host products and features such as CICS Transaction Gateway, IMS Connect, etc.

The Internet seems all-pervasive, and now it is in your CICS systems. This means, not just more work for you, but also more work for your CICS systems and your I/T infrastructure. How can you design your systems to handle it all? In this IBM Redbook we first provide an introduction to Web-enabling CICS, followed by a brief overview of the building-blocks that provide the backbone of IBM's workload management technologies. Included in this discussion are technologies such as DNS connection optimization, TCP/IP port sharing, and Sysplex Distributor (as provided by IBM OS/390 Communications Server); together with Network Dispatcher, CICSPlex SM and CICS dynamic routing, the CICS Universal Client workload manager, and VSAM Record Level Sharing. Following this, we explain how to use these components to design a load balancing solution for whichever CICS Web-enablement strategy you have chosen. Finally, we document three real life scenarios, where we designed, built, and tested three load balanced CICS Web-enabled solutions - a Web-aware CICS Web support application, and two servlet solutions using the CICS Transaction Gateway from both WebSphere Application Server for OS/390 and from WebSphere Application Server for Windows NT.