See information about the latest product version
Mobile integration scenarios
WebSphere® Message Broker, in conjunction with IBM® Worklight®, provides your mobile applications with secure access to your back-end systems, and integration that is robust and can scale to handle the growing number of connections.

This topic provides links to a range of scenarios about using WebSphere Message Broker for mobile integration. The scenarios are provided in a variety of formats, including video and articles hosted on external sites.
Some scenarios, originally developed for WebSphere Message Broker, apply equally to WebSphere Message Broker.
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 to perform some actions on their accounts. To do this, 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 running on a range of devices to perform actions on their accounts; for example, to query the balance.
By using the WebSphere Message Broker Toolkit with the Worklight: Microsoft .NET request-response pattern 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 Microsoft .NET class, made available by an integration application running on WebSphere Message Broker. The developers select the methods to be exposed in the web service and, using the pattern and .NET class, the toolkit builds a mobile application and the mobile integration logic written for the Worklight platform.
Implementing the solution can be split into three parts:
Part 1:
- Create and define the service-enablement logic to be deployed
as applications onto mobile devices
- Create an instance of the Worklight: Microsoft .NET request-response pattern, assigning a unique name to the instance
- Edit the pattern, to specify parameter values that configure the mobile integration solution; for example, to identify the .Net class.
- Choose .Net methods that are to be exposed in the service, and configure the parameters for those methods
- Deploy the integration application, by dragging and dropping onto an execution group. This makes the web service available for applications to call.
This part also generates a mobile application project for use with IBM Worklight, and an Android version of the mobile application for use on mobile devices.
For an illustration
of this part, see the video WebSphere Message
Broker - Mobile Service Enablement Part1 (hosted on YouTube)
Part 2:
- Import into IBM Worklight Studio the project that was generated by the pattern chosen in part 1.
- Build the mobile application
- Examine the application artifacts, including:
- The adapter that allows you to publish or advertise the procedures and functions that mobile applications can call.
- The procedures to get balance, transfer money, and find missing account
- Invoke the adapter as a Worklight procedure, to simulate being a mobile application. This sends an HTTP JSON request to Worklight, which passes the request to the adapter, which then packages and sends the request to WebSphere Message Broker.
- Test the mobile application as a mobile web application. By previewing the application as a common resource, you run a working Android application within a web browser.
- Test the mobile application as an Android application, in the Android emulator provided by Worklight. This runs the application in the same way as it would work on a mobile device.
For an illustration of this part, see the video WebSphere Message Broker - Mobile Service
Enablement Part2 (hosted on YouTube)
Part 3
- In IBM Worklight Studio, ensure that system parameters and device drivers are installed and set up correctly, primarily the Android SDK and USB Drivers
- Ensure that your mobile device has the required ADB drivers and set up to deploy and test the mobile application
- Connect the mobile device to IBM Worklight
- In IBM Worklight Studio, run the mobile application as an Android application. This installs the application onto the mobile device, and can be used in the same way as in the Android emulator.
- Disconnect the mobile device, and then use the application as a standalone application on the mobile device
For an illustration of this part, see the video WebSphere Message Broker - Mobile Service
Enablement Part3 (hosted on YouTube)
More scenarios
A selection of more scenarios about using WebSphere Message Broker for mobile integration.
- WebSphere Message Broker integration with Siebel, SAP, CICS®, .Net and Worklight
- A two-part video demonstrating a Sales order management application integration, using WebSphere Message Broker 8.0.0.1, integrating with EIS such as Siebel, SAP and CICS, as well as .Net and Worklight.
- Part 1 describes the original, complex business case and how WebSphere Message Broker Version 8.0 makes the solution simpler and more modular. The video ends by demonstrating use of a mobile application to process a sales order through the integrated applications.
- Part 2 demonstrates developing message flows in the WebSphere Message Broker Toolkit and then deploying them to the runtime. The video ends by demonstrating use of a mobile application to process a sales order through the integrated applications.
- Integrating mobile applications with WebSphere Message Broker using IBM Worklight
- An IBM developerWorks® article that shows you how to use IBM Worklight and the Worklight server to develop hybrid mobile applications that invoke enterprise services deployed on WebSphere Message Broker.
- Using the WebSphere Message Broker Mobile Service Pattern with WebSphere Cast Iron® Web API Management
- An IBM developerWorks article that shows you how to use the Mobile Service pattern to quickly and easily take existing WebSphere Message Broker Version 8.0 services and expose them through WebSphere Cast Iron Web API Management.