In this IBM® Redbooks® publication, you will gain an appreciation of the IBM CICS® Transaction Gateway (CICS TG) product suite, based on key criteria, such as capabilities, scalability, platform, CICS server support, application language support, and licensing model. Matching the requirements to available infrastructure and hardware choices requires an appreciation of the choices available. In this book, you will gain an understanding of those choices, and will be capable of choosing the appropriate CICS connection protocol, APIs for the applications, and security options. You will understand the services available to the application developer when using a chosen protocol. You will then learn about how to implement CICS TG solutions, taking advantage of the latest capabilities, such as IPIC connectivity, high availability, and Dynamic Server Selection. Specific scenarios illustrate the usage of CICS TG for IBM z/OS®, and CICS TG for Multiplatforms, with CICS Transaction Server for z/OS and IBM WebSphere® Application Server, including connections in CICS, configuring simple end-to-end connectivity (all platforms) with verification for remote and local mode applications, and adding security, XA support, and high availability.

The service-oriented architecture (SOA) style of integration involves breaking an application down into common, repeatable services that can be used by other applications (both internal and external) in an organization, independent of the computing platforms on which the business and its partners rely. In recent years CICS® has added a variety of support for SOA and now provides near seamless connectivity with other IT environments. This IBM® Redbooks® publication helps IT architects to select, plan, and design solutions that integrate CICS applications as service providers and requesters. First, we provide an introduction to CICS service enablement and introduce the architectural choices and technologies on which a CICS SOA solution can be based. We continue with an in-depth analysis of how to meet functional and non-functional requirements in the areas of application interface, security, transactional scope, high availability, and scalability. Finally, we document three integration scenarios to illustrate how these technologies have been used by customers to build robust CICS integration solutions.

This IBM® Redbooks® publication describes IBM TXSeries® for Multiplatforms, which is the premier IBM distributed transaction processing software for business-critical applications. Before describing distributed transaction processing in general, we introduce the most recent version of TXSeries for Multiplatforms. We focus on the following areas: The technical value of TXSeries for Multiplatforms New features in TXSeries for Multiplatforms Core components of TXSeries Common TXSeries deployment scenarios Deployment, development, and administrative choices Technical considerations It also demonstrates enterprise integration with products, such as relational database management system (RDBMS), IBM WebSphere® MQ, and IBM WebSphere Application Server. In addition, it describes system customization, reviewing several features, such as capacity planning, backup and recovery, and high availability (HA). We describe troubleshooting in TXSeries. We also provide details about migration from version to version for TXSeries. A migration checklist is included. We demonstrate a sample application that we created, called BigBlueBank, its installation, and the server-side and client-side programs. Other topics in this book include application development and system administration considerations. This book describes distributed IBM Customer Information Control System (IBM CICS®) solutions, and how best to develop distributed CICS applications.

This IBM® Redbooks® publication focuses on operational and managerial aspects for DataPower® appliance deployments. DataPower appliances provide functionality that crosses both functional and organizational boundaries, which introduces unique management and operational challenges. For example, a DataPower appliance can provide network functionality, such as load balancing, and at the same time, provide enterprise service bus (ESB) capabilities, such as transformation and intelligent content-based routing. This IBM Redbooks publication provides guidance at both a general and technical level for individuals who are responsible for planning, installation, development, and deployment. It is not intended to be a "how-to" guide, but rather to help educate you about the various options and methodologies that apply to DataPower appliances. In addition, many chapters provide a list of suggestions.

IBM® Workload Deployer provides a solution to creating, deploying, and managing workloads in an on-premise or private cloud. It is rich in features that allow you to quickly build and deploy virtual systems from base images, to extend those images, and to customize them for future use as repeatable deployable units. IBM Workload Deployer also provides an application-centric capability enabling rapid deployment of business applications. By using either of these deployment models, an organization can quickly instantiate a complete application platform for development, test, or production. The IBM Workload Deployer uses the concept of patterns to describe the logical configuration of both the physical and virtual assets that comprise a particular solution. The use of patterns allows an organization to construct a deployable solution one time, and then dispense the final product on demand. patterns are composed of an operating system and IBM software solutions, such as IBM WebSphere® Application Server and IBM WebSphere Virtual Enterprise. patterns are constructed to support a single application workload. The IBM Workload Deployer is shipped with a set of pre-loaded virtual images and virtual patterns. These images and patterns can be used to create comprehensive and flexible middleware solutions. They can also be cloned and customized to suit your specific needs. This IBM Redbooks® publication looks at two different aspects of customizing virtual systems for deployment into the cloud. First, it explores the capabilities of IBM Image Construction and Composition Tool to build and provide highly customized virtual images for use in virtual system patterns on the IBM Workload Deployer. Next, it looks at the virtual application capabilities of the IBM Workload Deployer, including those capabilities that allow you to deploy enterprise applications and database services to the cloud. It also introduces the IBM Workload Deployer Plugin Development Kit, which allows you to further extend the capabilities of the virtual application patterns.

This IBM® RedpaperTM publication provides information about how to build, deploy, and use IBM MQ as a service. The information in this paper includes the key factors that must be considered while planning the use of IBM MQ as a service. Through descriptions and examples, this paper explains how to apply as a service methodologies to an IBM MQ environment, and describes techniques and preferred practices for integrating IBM MQ into a self-service portal. This paper explains how to create and use an IBM MQ as a service self-service menu for a portal. It includes examples that show how to use an IBM MQ as a service catalog. This paper describes options and techniques for deploying IBM MQ as a service that is tailored to the specific enterprise messaging needs of an organization. Although these techniques can be employed in a cloud environment, they are equally applicable in an on-premises enterprise data center. This paper includes information about the various infrastructure options that can be selected when implementing IBM MQ as a service. The information in this paper helps infrastructure administrators to define services so that you can provision IBM MQ resources quickly. The target audiences of this paper are developers, infrastructure administrators, and line-of-business (LOB) professionals who want to provision IBM MQ resources to be accessed as services in small, medium, large, and complex implementations.