This IBM® Redbooks® publication is for anyone needing to increase WebSphere® messaging availability, especially people interested in the new capabilities of WebSphere MQ and WebSphere Message Broker. It discusses and demonstrates solutions to provide high availability for WebSphere Messaging solutions. For the distributed platforms, this ranges from the traditional PowerHATM for AIX® to the new WebSphere MQ multi-instance queue managers and WebSphere Message Broker multi-instance brokers. For the appliance users, we included solutions for WebSphere DataPower®. For enterprises that need continuous availability of WebSphere MQ messages, MQ Queue Sharing Groups and the CICS® Group Attach features are demonstrated. The book includes guidance on HA options, such as when you might need PowerHA (or a similar solution for your platform), when the multi-instance features work for your applications, and when duplexing the coupling facility structures might be appropriate.

With ever-increasing workloads on production systems from transaction, batch, online query and reporting applications, the challenges of high availability and workload balancing are more important than ever. This IBM® Redbooks® publication provides descriptions and scenarios for high availability solutions using the Q Replication technology of the IBM InfoSphere® Data Replication product on the IBM z/OS® platform. Also included are key considerations for designing, implementing, and managing solutions for the typical business scenarios that rely on Q Replication for their high availability solution. This publication also includes sections on latency analysis, managing Q Replication in the IBM DB2® for z/OS environment, and recovery procedures. These are topics of particular interest to clients who implement the Q Replication solution on the z/OS platform. Q Replication is a high-volume, low-latency replication solution that uses IBM WebSphere® MQ message queues to replicate transactions between source and target databases or subsystems. A major business benefit of the low latency and high throughput solution is timely availability of the data where the data is needed. High availability solutions are implemented to minimize the impact of planned and unplanned disruptions of service to the applications. Disruption of service can be caused by software maintenance and upgrades or by software and hardware outages. As applications' high availability requirements evolve towards continuous availability, that is availability of the data 24 hours a day and 7 days a week, so does the Q Replication solution, to meet these challenges. If you are interested in the Q Replication solution and how it can be used to implement some of the high availability requirements of your business scenarios, this book is for you.

This IBM Redbooks publication describes the fundamental concepts and benefits of message queuing technology. This book is an update of a very popular Redpaper (REDP-0021) based on IBM WebSphere MQ Versions 5.0 to 5.2. This publication provides a design-level overview and technical introduction for the established and reliable WebSphere MQ product. A broad technical understanding of the WebSphere MQ product can improve design and implementation decisions for WebSphere MQ infrastructures and applications. To reduce the time required to gain this understanding, this book summarizes relevant information from across the WebSphere MQ product documentation. We also include hands-on security and troubleshooting sections to aid understanding and provide a reference for common administrative actions performed when building and maintaining WebSphere MQ infrastructures. In the appendix, we provide a summary of the new features in WebSphere MQ Version 6.0.

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.

The differences between well-designed security and poorly designed security are not always readily apparent. Poorly designed systems give the appearance of being secure but can over-authorize users or allow access to non-users in subtle ways. The problem is that poorly designed security gives a false sense of confidence. In some ways, it is better to knowingly have no security than to have inadequate security believing it to be stronger than it actually is. But how do you tell the difference? Although it is not rocket science, designing and implementing strong security requires strong foundational skills, some examples to build on, and the capacity to devise new solutions in response to novel challenges. This IBM® Redbooks® publication addresses itself to the first two of these requirements. This book is intended primarily for security specialists and IBM WebSphere® MQ administrators that are responsible for securing WebSphere MQ networks but other stakeholders should find the information useful as well. Chapters 1 through 6 provide a foundational background for WebSphere MQ security. These chapters take a holistic approach positioning WebSphere MQ in the context of a larger system of security controls including those of adjacent platforms' technologies as well as human processes. This approach seeks to eliminate the simplistic model of security as an island, replacing it instead with the model of security as an interconnected and living system. The intended audience for these chapters includes all stakeholders in the messaging system from architects and designers to developers and operations. Chapters 7 and 8 provide technical background to assist in preparing and configuring the scenarios and chapters 9 through 14 are the scenarios themselves. These chapters provide fully realized example configurations. One of the requirements for any scenario to be included was that it must first be successfully implemented in the team's lab environment. In addition, the advice provided is the cumulative result of years of participation in the online community by the authors and reflect real-world practices adapted for the latest security features in WebSphere MQ V7.1 and WebSphere MQ V7.5. Although these chapters are written with WebSphere MQ administrators in mind, developers, project leaders, operations staff, and architects are all stakeholders who will find the configurations and topologies described here useful. The third requirement mentioned in the opening paragraph was the capacity to devise new solutions in response to novel challenges. The only constant in the security field is that the technology is always changing. Although this book provides some configurations in a checklist format, these should be considered a snapshot at a point in time. It will be up to you as the security designer and implementor to stay current with security news for the products you work with and integrate fixes, patches, or new solutions as the state of the art evolves.

This IBM® Redbooks® publication brings together subject matter experts with experience using the leading IBM customer interaction platform for cross-channel and online commerce, IBM WebSphere® Commerce, with the powerful IBM Sterling Order Management, which coordinates order fulfillment from all channels and across the extended enterprise. An integrated solution was built in the lab that illustrates how these products can be integrated to benefit IBM customers. This publication focuses on the integration of the IBM high-volume commerce solution designed to address enterprise commerce needs by delivering a rich, robust multi-channel customer experience, with Sterling Order Management, designed to enable supplier collaboration with management and order fulfillment process optimization. By integrating WebSphere Commerce and Sterling Order Management with out-of-the-box components, we prove that customers are provided an end-to-end solution to address a complete opportunity for a fulfillment life cycle that is cost effective and easy to implement. This publication targets a technical audience for the documentation of the integration approach by explaining the solution architecture and the implementation details. However, this publication also contains introductory chapters that contain executive summary material and provides well-documented scenarios with use cases for business analysts whose domain would be these systems.

Dramatic forces of change continue to sweep the financial services industry. The age of the empowered customer is here and are changing the way financial products are delivered, sold, and serviced, which are making relationships more complex than ever. The explosion of data and intense competition, which is combined with slow or inconsistent economic conditions, makes it imperative for financial institutions to find new and cost effective ways to increase market share, renew customer trust, and drive profitable growth. In this new business environment, the transaction processing arm of the industry is facing increased pressure to reduce float, better manage liquidity, and provide regulators and clients with increased transparency. At the same time, the industry must effectively manage the risks that are associated with introducing customer-focused and regionalized products and services. Financial Transaction Manager enables the management, orchestration, and monitoring of financial transactions during their processing lifecycle. Financial Transaction Manager provides the capability to integrate and unify financial transactions in various industry formats (including ISO 20022, SWIFT, NACHA, EDIFACT, ANSI X12 and others). By using Financial Transaction Manager, financial institutions gain visibility into message processing, balance financial risk, and facilitate effective performance management. This IBM® Redbooks® publication outlines how Financial Transaction Manager is deployed to realize the benefits of transaction transparency, increase business agility, and allow for innovation that is built on a robust and high-performance environment.

& • Details the JMS API, covering the latest version 1.1, and discusses application development based on IBM WebSphere implementations & & • Key coverage on WebSphere MQ, Websphere MQ Event Broker, JMS administration tasks, and common usage scenarios & & • Examples coding JMS in servlets, portlets, EJBs and communicating with non-JMS applications

This IBM Redbooks publication describes and demonstrates common, prescriptive scenarios for setting up disaster recovery for common workloads using IBM WebSphere Application Server, IBM DB2, and WebSphere MQ between two IBM PureApplication System racks using the features in PureApplication System V2. The intended audience for this book is pattern developers and operations team members who are setting up production systems using software patterns from IBM that must be highly available or able to recover from a disaster (defined as the complete loss of a data center).