WebSphere® Message Broker V6.1 was released in December of 2007. This IBM® Redpaper publication discusses the new features and editions available with this release. It highlights several of the new features and provides information on how they can be used to enhance your messaging solutions. This paper is of interest to architects who are building messaging or enterprise service bus (ESB) solutions, as well as to the implementers of WebSphere Message Broker solutions.

Enterprise IT environments continue to grow in complexity, through natural expansion or mergers and acquisitions. As the pace of business demand accelerates, IT environments look more for opportunities to flexibly reuse existing applications, services, and data. With the IBM® connectivity portfolio of products, these IT environments can discover and reuse services, expose and use application services, and route and transform messages. The set of capabilities (in the IBM connectivity portfolio) supports client requests for a broad service-oriented architecture (SOA) infrastructure that addresses the need to bridge and streamline communication in heterogeneous IT environments. In this IBM Redpaper publication, we provide an overview of the IBM connectivity portfolio to market watchers who have a keen interest in understanding the most current connectivity technology releases, and how IBM is taking them to the next level. Specifically, we review the key benefits and features of the following products: IBM WebSphere® MQ IBM WebSphere Message Broker IBM WebSphere Enterprise Service Bus IBM WebSphere DataPower® IBM WebSphere Adapters IBM WebSphere Transformation Extender IBM WebSphere Service Registry and Repository

IBM® WebSphere® DataPower® SOA Appliances represent an important element in the holistic approach of IBM to service-oriented architecture (SOA). IBM SOA appliances are purpose-built, easy-to-deploy network devices that simplify, help secure, and accelerate your XML and Web services deployments while extending your SOA infrastructure. These appliances offer an innovative, pragmatic approach to harness the power of SOA. By using them, you can simultaneously use the value of your existing application, security, and networking infrastructure investments. This series of IBM Redbooks publications is written for architects and administrators who need to understand the implemented architecture in WebSphere DataPower appliances to successfully deploy it as a secure and efficient enterprise service bus (ESB) product. These papers give a broad understanding of the new architecture and traditional deployment scenarios. They cover details about the implementation to help you identify the circumstances under which you should deploy DataPower appliances. They also provide a sample implementation and architectural best practices for an SOA message-oriented architecture in an existing production ESB environment. Part 3 of the series, this part, describes how to use the DataPower appliance to secure incoming Web Services within an SOA environment, how to integrate your DataPower appliance with WebSphere Message Broker, and how to provide protection against security attacks by implementing the XML Denial of Service (XDoS)

This paper provides an overview of the fictitious JKHL Enterprises (JKHLE) company, that is referenced throughout a series of service-oriented architecture (SOA) scenario papers and related work products, for the purposes of a case study. This case study describes how to apply SOA scenario realization patterns to solve common business and IT challenges using SOA principles. Read the other case studies in this series that use JKHL Enterprises: <a href="http://www.redbooks.ibm.com/abstracts/redp4375.html">Case Study: Interaction and Collaboration Services SOA Scenario</a> <a href="http://www.redbooks.ibm.com/abstracts/redp4383.html">Case Study: Business Process Management SOA Scenario</a> <a href="http://www.redbooks.ibm.com/abstracts/redp4377.html">Case Study: Service Creation SOA Scenario</a> <a href="http://www.redbooks.ibm.com/abstracts/redp4378.html">Case Study: SOA Security and Management Scenario</a> <a href="http://www.redbooks.ibm.com/abstracts/redp4379.html">Case Study: SOA Design Scenario</a> <a href="http://www.redbooks.ibm.com/abstracts/redp4380.html">Case Study: Service Connectivity SOA Scenario</a> <a href="http://www.redbooks.ibm.com/abstracts/redp4381.html">Case Study: Process SOA Scenario</a> <a href="http://www.redbooks.ibm.com/abstracts/redp4382.html">Case Study: Information as a Service SOA Scenario</a> <a href="http://www.redbooks.ibm.com/abstracts/redp4384.html">Case Study: SOA Governance S

This IBM Redpaper provides step-by-step guides to implement IBM WebSphere MQ Secure Sockets Layer (SSL) channels in a variety of configurations: Microsoft Windows to and from Windows WebSphere MQ clients to WebSphere MQ queue managers (both on Windows) Any-to-any WebSphere MQ channel connections on IBM z/OS, AIX 5L, and Windows, using RACF as the certification authority WebSphere Message Broker Toolkit The aim is for you to learn the basics of WebSphere MQ SSL using simple connectivity examples.

Without doubt, Service-Oriented Architecture (SOA) is one of the most important topics on the agenda of any IT person. SOA involves a new vision of how to design, develop, and manage applications, but also puts new requirements on the underlying infrastructure. This Redpaper redbook describes the infrastructure challenges that SOA brings to the table and how the IBM System z platform and the z/OS operating system address those challenges. An effective SOA implementation requires very high Quality of Services (QoS) from the underlying environment, and users demand security, availability, and simplified management of the services. These are fundamental characteristics of System z and z/OS, making them an ideal platform on which to design an SOA. This paper presents an overview of SOA, describes the SOA reference architecture, and demonstrates how IBM System z and z/OS support the SOA requirements. Finally, it suggests an approach for SOA-enabling existing applications and provides several integration scenarios.

If you do not know what you are trying to accomplish, the task is even harder to do. If you do not know how to do the task, it is even more difficult. How many times have you started to develop a solution before understanding the requirements — input data formats, the arrival rates, processing needs, and the expected output? How much do you really know about the tools that you are using and the full power that those tools can bring to the solution? To make the best choices when designing and implementing message flows, you need a clear understanding of the requirements and the power of the tools that you are using. Message flows should be bullet proof, meaning that the design should provide the required functions and should also prevent errors from disrupting normal operations. For example, a message flow is bullet proof when: - A problem is recognized early and its impact is minimized. - A problem is diagnosed on the fly and corrective action taken. - Information about what was happening at the point of failure is collected and recorded. - The message flow takes proactive steps to notify someone about the problem with details about the problem. This paper examines some of the capabilities of WebSphere Message Broker and shows how to include these capabilities in your message flows. We use variations on a sample message flow using an MQInput node, several Compute nodes, and MQOutput nodes to show error path options, how the broker handles errors in various nodes, and the information available for analysis.

This Redpaper shows how to build an Enterprise Service Bus (ESB) using current IBM technology. The paper is based on a simple application scenario in which Web services invocations are used to implement a simplified supply chain process for a consumer electronics retailer. We add an ESB into the scenario between the service consumers and service providers, which provides greater flexibility and loose coupling. We explore design considerations for an ESB in a service-oriented architecture (SOA) and implement the Broker design pattern for this decoupling. We use WebSphere Business Integration Message Broker V5 to implement the ESB with services hosted on WebSphere Application Server. This Redpaper is divided into three sections: - Design guidelines - Development guidelines - Runtime guidelines This paper is an extension of the redbook Patterns: Implementing an SOA Using an Enterprise Service Bus, SG24-6346.

When designing and implementing a production grade Message Broker solution on z/OS, one of the most important factors to consider is high availability. This IBM Redpaper examines the design considerations inherent in configuring a highly available Message Broker environment. Also demonstrated is the use of the coupling facility for WebSphere MQ queue sharing groups (QSG) and Automatic Restart Management (ARM) in order to support WebSphere Business Integration Message Broker HA in a sysplex environment. Finally, examples of the behavior of Message Broker during failover are provided, including transaction rate measurements and throughput statistics.

WebSphere Business Integration Message Broker enables information, packaged as messages, to flow between different business applications. This broker product extends the messaging capabilities of WebSphere MQ by adding message transformation and routing features. For those familiar with the previous IBM messaging products, the functions of WebSphere MQ Integrator and WebSphere MQ Event Broker have merged into one product consisting of: WebSphere Business Integration Message Broker, providing broker functionality for point-to-point messaging WebSphere Business Integration Event Broker, providing publish/subscribe functionality This paper will help you understand what WebSphere Business Integration Message Broker is and what it does.