IBM WebSphere® Message Broker is a lightweight, advanced enterprise service bus (ESB) that provides a broad range of integration capabilities that enable companies to rapidly integrate internal applications and connect to partner applications. Messages from business applications can be transformed, augmented and routed to other business applications. The types and complexity of the integration required will vary by company, application types, and a number of other factors. Processing logic in WebSphere Message Broker is implemented using message flows. Through message flows, messages from business applications can be transformed, augmented, and routed to other business applications. Message flows are created by connecting nodes together. A wide selection of built-in nodes are provided with WebSphere Message Broker. These nodes perform tasks that are associated with message routing, transformation, and enrichment. Message flows are created and tested using the Message Broker Toolkit, a sophisticated, easy-to-use programming tool that provides a full range of programming aids. This IBM® Redbooks® publication focuses on two specific integration requirements that apply to many midmarket companies. The first is the ability to use WebSphere Message Broker to integrate Microsoft.NET applications into a broader connectivity solution. WebSphere Message Broker V8 introduces the ability to integrate with existing Microsoft .NET Framework applications. A .NET assembly can be called from within a message flow and the WebSphere Message Broker runtime can host and run .NET code. Solutions explored in this book cover connectivity to applications using Windows Communications Framework (WCF), Microsoft Message Queuing, Microsoft Dynamics CRM, and other Microsoft applications. The second is the ability to integrate WebSphere Message Broker with file transfer networks, specifically with WebSphere MQ File Transfer Edition and IBM Sterling Connect Direct.

This IBM® Redbooks® publication is divided into four parts: Part 1 introduces message-oriented middleware and the WebSphere® MQ product. It explains how messaging technologies are implemented in WebSphere MQ and shows how to get started with configuring a WebSphere MQ environment. This part briefly lists the new features of WebSphere MQ V7.1 and V7.5. Part 2 introduces the enhancements to WebSphere MQ in Version 7 Release 1. It provides a description of the new features, their business value, and usage examples. It describes enhancements to WebSphere MQ for multiplatforms and z/OS®. Examples of features that are discussed in this part include multiple installation support for multiplatforms, enhanced security with channel authentication records, enhanced clustering, improved availability and scalability on z/OS, and more. Part 3 introduces the enhancements to WebSphere MQ in Version 7 Release 5 for multiplatforms. It provides a description of the new features, their business value, and usage examples. Examples of enhancements that are discussed in this part include new installation options, such as the bundling of WebSphere MQ Advanced Message Security and WebSphere MQ Managed File Transfer. Part 4 contains practical scenarios that demonstrate how the new features and enhancements work and how to use them. In summary, the introduction gives a broad understanding of messaging technologies and WebSphere MQ. It helps you understand the business value of WebSphere MQ. It provides introductory information to help you get started with WebSphere MQ. No previous knowledge of the product and messaging technologies is assumed. The remaining parts of this book discuss enhancements to previous versions of WebSphere MQ. The information helps you understand the benefits of upgrading to WebSphere MQ V7.1 and V7.5 and how to implement the new functions. Knowledge of WebSphere MQ V7.0 and earlier versions is assumed. This book provides details about IBM WebSphere MQ product features and enhancements that are required for individuals and organizations to make informed application and design decisions prior to implementing a WebSphere MQ infrastructure or begin development of a WebSphere MQ application. This publication is intended to be of use to a wide-ranging audience.

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.

MQ Telemetry Transport (MQTT) is a messaging protocol that is lightweight enough to be supported by the smallest devices, yet robust enough to ensure that important messages get to their destinations every time. With MQTT devices such as smart energy meters, cars, trains, satellite receivers, and personal health care devices can communicate with each other and with other systems or applications. This IBM® Redbooks® publication introduces MQTT and takes a scenario-based approach to demonstrate its capabilities. It provides a quick guide to getting started and then shows how to grow to an enterprise scale MQTT server using IBM WebSphere® MQ Telemetry. Scenarios demonstrate how to integrate MQTT with other IBM products, including WebSphere Message Broker. This book also provides typical usage patterns and guidance on scaling a solution. The intended audience for this book ranges from new users of MQTT and telemetry to those readers who are looking for in-depth knowledge and advanced topics.

The power of IBM® MQ is its flexibility combined with reliability, scalability, and security. This flexibility provides a large number of design and implementation choices. Making informed decisions from this range of choices can simplify the development of applications and the administration of an MQ messaging infrastructure. Applications that access such an infrastructure can be developed using a wide range of programming paradigms and languages. These applications can run within a substantial array of software and hardware environments. Customers can use IBM MQ to integrate and extend the capabilities of existing and varied infrastructures in the information technology (IT) system of a business. IBM MQ V8.0 was released in June 2014. Before that release, the product name was IBM WebSphere® MQ. This IBM Redbooks® publication covers the core enhancements made in IBM MQ V8 and the concepts that must be understood. A broad understanding of the product features is key to making informed design and implementation choices for both the infrastructure and the applications that access it. Details of new areas of function for IBM MQ are introduced throughout this book, such as the changes to security, publish/subscribe clusters, and IBM System z exploitation. This book is for individuals and organizations who make informed decisions about design and applications before implementing an IBM MQ infrastructure or begin development of an IBM MQ application.

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.