Book description
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.
Please note that the additional material referenced in the text is not available from IBM.
Table of contents
- Front cover
- Contact an IBM Software Services Sales Specialist
- Notices
- Preface
- Chapter 1. WebSphere Message Broker for mid-market solutions
-
Chapter 2. Introduction to WebSphere Message Broker V8
- 2.1 Runtime architecture of WebSphere Message Broker
- 2.2 Development environment of WebSphere Message Broker
- 2.3 Connectivity options
- 2.4 Transformation interfaces
- 2.5 Administering WebSphere Message Broker
- 2.6 Deploying applications
- 2.7 Getting started
- 2.8 Creating WebSphere MQ queue managers and queues
- Chapter 3. Using the tools for WebSphere Message Broker and .NET Integration
- Chapter 4. Scenario: Bridging WebSphere MQ and Microsoft Message Queuing
-
Chapter 5. Scenario: Calling Microsoft Dynamics CRM from a message flow
- 5.1 Scenario overview
-
5.2 Creating the message flow
- 5.2.1 Setting up the environment
- 5.2.2 Creating and connecting the nodes
- 5.2.3 Configuring the node properties
- 5.2.4 Broker configuration for SAP request nodes
- 5.2.5 Writing the code for the SAP nodes
- 5.2.6 Coding the ESQL for the Compute nodes
- 5.2.7 Coding the Filter Request .NETCompute node
- 5.2.8 Writing the code for the database operations
- 5.2.9 Writing the code for accessing Microsoft Dynamics CRM Online
- 5.2.10 Writing the code for the .NETCompute node (Create) - DB<->CreateCRMOnlineCustomer
- 5.3 Deploying the message flow
- 5.4 Testing the message flow
- 5.5 Troubleshooting tips
-
Chapter 6. Scenario: Integration Windows Communication Foundation in message flows - Part 1
- 6.1 ClaimsProcessingWcfService overview
- 6.2 Windows Communication Foundation
-
6.3 Developing the WCF Service
- 6.3.1 Creating a Microsoft Visual Studio 2010 project for the WCF Service
- 6.3.2 Setting the namespace for the project
- 6.3.3 Modifying the classes created by the New Project Wizard
- 6.3.4 Creating the required datatypes
- 6.3.5 Creating private methods to serialize and deserialize the Datatypes
- 6.3.6 Designing and implementing the service contract
- 6.3.7 Building the WCF Service
- 6.3.8 Configuring the WCF service
- 6.3.9 Testing the WCF Service using the WCF Test Client
- 6.4 Obtaining information about the service using MEX
- 6.5 Generating WCF client code from a MEX enabled WCF service
- 6.6 WCF hosting options
-
Chapter 7. Scenario: Integrating Windows Communication Foundation in message flows - Part 2
- 7.1 Scenario overview
- 7.2 Creating the message flow
- 7.3 Using the Mapping node to transform the input to the Canonical Message Format
- 7.4 Transforming the SOAP input message
-
7.5 Creating a .NETCompute node to consume the ClaimsProcessingWcfService
- 7.5.1 Creating a constant to hold the namespace prefix
- 7.5.2 Adding the MEX-generated WCF client to the project
- 7.5.3 Developing helper methods to interact with the WCF service
- 7.5.4 Concurrency
- 7.5.5 Handling exceptions when invoking the WCF service
- 7.5.6 Ensuring that the serviceClient is closed on flow deletion
- 7.5.7 Creating methods to add datatypes to the message tree
- 7.5.8 Creating a helper method to build Customer object from the Logical Message Tree
- 7.5.9 Preparing the ClaimsProcessingRequest object
- 7.5.10 Adding the information from the WCF response into the message tree
- 7.5.11 The CallWCFNode.Evaluate() method
- 7.5.12 Handling failed tree navigations in the Evaluate() method
- 7.5.13 Handling FaultExceptions in the Evaluate() method
- 7.5.14 Verifying the completed CallWCFNode
- 7.6 Routing the output
- 7.7 Writing a .NETCompute node class to generate a payment message
- 7.8 Processing incomplete results for the ViewOutstandingClaims operation
- 7.9 Creating a Word document for email and print
- 7.10 Using the Mapping node to transform the Canonical message to the output format
- 7.11 Using a Compute node to transform the Canonical Message into a SOAP message
- 7.12 Handling exceptions in the flow
- 7.13 Building and deploying the Visual Studio project
- 7.14 Updating the properties for the .NETCompute nodes
- 7.15 Building and deploying the Message Broker application
- 7.16 Testing the WebSphere Message Broker application
- 7.17 Altering the scenario to use a SOAP over HTTP based binding
-
Chapter 8. Integrating file transfer with WebSphere MQ FTE into the message flow
- 8.1 Scenario overview
- 8.2 Overview of the WebSphere MQ File Transfer edition
- 8.3 Preparing the broker environment for this scenario
- 8.4 Applications emulated in this scenario
-
8.5 Creating the main message flow
- 8.5.1 Message flow overview
- 8.5.2 Creating and connecting the nodes
- 8.5.3 Creating a message definition
- 8.5.4 Using FTE nodes
- 8.5.5 Using aggregation in WebSphere Message Broker
- 8.5.6 Producing multiple messages from the compute node
- 8.5.7 Accessing databases from the database nodes
- 8.5.8 Creating the queues for the FTESample application
- 8.6 Running the scenario
- 8.7 Extending the scenario
- Chapter 9. Integrating file transfer using Sterling Connect:Direct with your message flow
- Appendix A. Additional material
- Related publications
- Back cover
Product information
- Title: Using WebSphere Message Broker V8 in Mid-Market Environments
- Author(s):
- Release date: August 2012
- Publisher(s): IBM Redbooks
- ISBN: 9780738437002
You might also like
book
IBM WebSphere Application Server 8.0 Administration Guide
With your C++ skills and our writers’ know-how, you’re well on your way to using the …
book
IBM WebSphere MQ V7.1 and V7.5 Features and Enhancements
This IBM® Redbooks® publication is divided into four parts: Part 1 introduces message-oriented middleware and the …
book
End-to-end Integration with IBM Sterling B2B Integration and Managed File Transfer solutions
Across numerous vertical industries, enterprises are challenged to improve processing efficiency as transactions flow from their …
book
Secure Messaging Scenarios with WebSphere MQ
The differences between well-designed security and poorly designed security are not always readily apparent. Poorly designed …