|Featured Blog Entries|
Connect the mobile world to your enterprise with new IBM® MessageSight™ v1.1!
AndrewSchofield 120000NJ3J Comment (1) Visits (4856)
Do you need to connect mobile devices to your enterprise? Do you want to use messaging for scalable machine-to-machine communication?
You need IBM®
Easily access enterprise applications from mobile devices
MessageSight has always supported JMS clients, but with this new release we’ve added a brand new resource adapter. This enables you to connect directly to MessageSight from a Java Enterprise Edition application server, such as IBM
One question we’re often asked is how to manage the difference in performance between MessageSight and existing middleware. With v1.1, we have a new way to spread messaging workload: shared subscriptions.
In most publish/subscribe systems, each subscription gets a separate stream of messages and each subscription has just a single consumer. If you add more consumers, each gets a separate subscription and you just multiply up the number of messages to process. This is where shared subscriptions come in.
A shared subscription still gets a separate stream of messages but there can be multiple consumers taking the messages. So, a shared subscription is useful in situations where a single consumer cannot keep up with the rate of messages being published.
The combination of the resource adapter and shared subscriptions is really powerful since it enables a stream of messages to be distributed among a set of application servers, such as a WebSphere Application Server cluster.
You can also use shared subscriptions from JMS clients, so we are updating the IBM
Control authorization using client certificates
Security is an important topic for mobile messaging and we’ve made some enhancements here. If you use client certificates to secure the connections from the clients, you’re now able to refer to information from inside the client certificates in the security policies on the server for authentication and authorization. So, the information used to identify the clients and control the resources they can access is encapsulated in the certificates that you have issued.
We’ve also made it possible to configure MessageSight so that it only permits connection using the latest NIST SP 800-131A security recommendations.
Notify mobile apps when messages arrive
And finally, there’s a new feature specifically aimed at mobile apps. It’s easy to use MQTT in mobile apps, but users tend to use these apps for a few minutes and then switch to another app. On most mobile operating systems, apps can only execute when they’re actually on screen. So how can you tell an inactive mobile app that there are MQTT messages waiting for it? This is where disconnected client notification comes in.
The idea is that a long-running service acts as a gateway between MessageSight and the platform-specific notification mechanisms such as Google Cloud Messaging. You can use IBM Worklight for this purpose, but you can easily write your own gateway instead. When an MQTT message is delivered to a subscription for which the client is currently disconnected, MessageSight publishes a message indicating that there’s a message waiting for the disconnected client. This is picked up by the gateway service which figures out which mobile device to notify and uses the platform-specific notification mechanism. Typically, the user sees a badge or toast notification on the mobile device which lets them know that there’s a message waiting when they go back into the mobile app.
Why not download IBM MessageSight for Developers v1.1 for free from IBM