IBM Integration Bus, Version 10.0.0.1 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS


.NET integration scenarios

IBM® Integration Bus supports Microsoft and .NET integration, making it simple to integrate your Microsoft assets with the rest of your services and applications within small to mid-size or large departmental enterprises.

This topic links to a range of scenarios about using IBM Integration Bus for .NET integration. The scenarios are provided in various formats, including video and articles that are hosted on external sites.

Some scenarios, originally developed for WebSphere® Message Broker, apply also to IBM Integration Bus.

Featured scenario: .NET service enablement for mobile applications

Background

Company A is a retail banking business that uses a Microsoft .NET application to work with accounts. The company wants to enable its customers to use mobile devices for their account functions. The company is looking to reuse the existing .NET code and class, wrapping them as a web service, and providing a mobile application.

The solution

Customers can use a mobile application that runs on a range of devices to access functions on their accounts; for example, to query the balance.

By using the IBM Integration Toolkit with the Worklight®: Microsoft .NET request-response pattern that is provided, the application developers create a production-ready solution in a matter of minutes. The solution is based on a web service, which wraps around the existing .NET class, made available by an integration application that runs on IBM Integration Bus. The developers select the methods to be exposed in the web service. By using the pattern and .NET class, the toolkit builds a mobile application and the mobile integration logic for the Worklight platform.

Implementing the solution can be split into three parts:

Part 1 demonstrates the aspects that are related to the .NET service enablement. Parts 2 and 3 demonstrate the mobile integration that uses the .NET service.

For part 1, see the video Video linkWebSphere Message Broker - Mobile Service Enablement Part1 (hosted on YouTube).

For the entire part 1 to part 3, see the full scenario that is outlined in Featured scenario: .NET service enablement for mobile applications.

More scenarios

A selection of more scenarios about using IBM Integration Bus for .NET integration.

WebSphere Message Broker V8 .NET integration
This video demonstrates how quick and easy it is to create a message flow that starts an existing .NET assembly on a Windows system, by using WebSphere Message Broker Version 8.0. With the easy-to-use tools provided, this can be completed in less than 5 minutes. Although the text-to-speech example is unlikely to be useful in an integration solution, this scenario shows just how easy it can be to invoke a .NET assembly that is already available.
Using Microsoft .NET in WebSphere Message Broker V8
This scenario, presented as a series of four tutorials on IBM developerWorks®, demonstrates the support for Microsoft .NET that was new in WebSphere Message Broker Version 8.0.
Part 1: Using the .NETCompute node sample shows you how to use the .NETCompute node to filter, modify, and create messages, and provides a sample scenario along with explanatory C# code snippets.
Part 2: Integrating with Microsoft Word shows you how to create a simple web service definition by using a WSDL file that you drag onto a message flow. This flow can be called by a web service client by using SOAP over HTTP. The request message sent to the flow represents a sales order for various items from a store. When the message flow receives the data, it uses C# code within a .NETCompute node to create a short Microsoft Word document that contains the detail of the sales order in a table. The Word document is written to a directory, and then the message flow sends an acknowledgement message back to the web service client.
Part 3: Integrating with Microsoft Excel shows you how the IBM Integration Bus .NETCompute node can use the Open XML SDK API to interact with Microsoft Excel. A message flow receives an input XML file and records the hierarchy of the data into a Microsoft Excel spreadsheet. When the message flow receives and parses the data, it uses C# code within a .NETCompute node to update a Microsoft Excel spreadsheet.
Part 4: Using the .NETCompute node for exception handling shows you how to use the .NETCompute node for exception handling, by using examples that build in complexity as extra exception conditions are deliberately produced and then handled.
WebSphere Message Broker and Microsoft .NET in Midmarket Solutions
An IBM Redbooks® solution guide that describes the ability to use WebSphere Message Broker Version 8.0 to integrate Microsoft .NET applications into a broader connectivity solution.
This solution guide highlights two usage scenarios:
  • Creating a single interface that can connect and integrate heterogeneous data stores for transforming data.
  • Accessing a Windows Communication Foundation service from a message flow.

ab20649_.htm | Last updated 2015-05-28 20:49:41