5 Things to Know About IBM MQ As a Service
MarcelaAdanRochester 2700048UPS Visits (9299)
IBM MQ is a robust messaging middleware that simplifies and accelerates the integration of diverse applications and business data, which might be distributed over multiple platforms and geographies. Organizations can expose some of the key IBM MQ functions as a service to provide the agility, usability, efficiency, and consistency that today’s enterprises need to respond quickly to the demands of line of business units.
Here are five things you should know about deploying IBM MQ as a service. To learn more, see the IBM Redpaper publication IBM
What does IBM MQ as a service mean?
The term MQ as a service applies the principles of an as a service delivery model to an IBM MQ deployment. Traditionally IBM MQ is administered exclusively within an enterprise by a central messaging middleware team. As the number and complexity of the change requests submitted by the line of business increase it becomes very difficult for a central team to respond at the speed required by the business.
Enterprises can exploit IBM MQ as service capabilities to implement self-service portals that allow lines of business professionals and application developers to request changes to the messaging ecosystem. These changes might range from the creation or deletion of a queue to the provision of a highly available and scalable topology for a new business application.
Why to create a self-service IBM MQ?
The business pressures on the infrastructure team as a cost center is to reduce human activity to a minimum by automating their best practices. IBM MQ as a service can increase the speed at which the infrastructure team can deliver new IBM MQ infrastructure to developers, while ensuring that the needs of the business are met by the solution.
What are examples of typical use cases for IBM MQ as a service?
The following use cases illustrate how organizations can use IBM MQ as a service to address real business needs:
Use case example 1:
A large bank has deployed IBM MQ over a period of 20 years, during which time three smaller banks were acquired and absorbed into the enterprise, each with their own IBM MQ administrative practices, installations, and business applications. IBM MQ is used for every critical business transaction in the bank. Digital and mobile banking is driving the creation of new customer facing applications at a faster rate than at any time in the history of the bank.
The bank needs to elastically scale and rapidly provision development and production IBM MQ infrastructures for new or updated business applications. The bank requires each line of business unit to be able to use a self-service interface to provision the necessary infrastructure changes themselves within minutes or hours, not days or weeks.
Use case example 2:
A large retail outlet has over 2000 stores that are located throughout the United States. Each store has to connect to the headquarters to share information about stock levels, trades, and other business transactions. The company has deployed IBM MQ as the standard mechanism for interaction between stores and headquarters. When a new store is opened it is necessary to establish connectivity with the headquarters within a working day (5 to 8 hours) with limited support from IBM MQ administrators. A self-service interface is required that the store-based employees can use to achieve this goal.
What are advantages of using IBM MQ as a service?
Offering IBM MQ as a service can provide the following benefits to an enterprise:
Empowering line of business professionals to directly provision or update the messaging resources they require, reducing time to value by eliminating the dependency on manual activities that have traditionally been performed by a central infrastructure team.
Self-service interfaces provided to line of business professionals enable them to focus on their core requirements, such as what destinations they need and what quality of service is necessary. The complexity of satisfying these requirements can be hidden from users.
Automation that underpins a self-service interface allows to dynamically provisioning systems and messaging resources for test and development purposes. The use of automation can also simplify the activity of promoting changes from development to test, quality assurance, and production environments. Automation also allows resources to dynamically scale in response to changing business demands.
Exposing a self-service interface to the line of business units provides a single entry point for changes to the messaging configuration. This interface can exploit common routines and workflows to deploy the necessary changes, which allows enforcing standards and consistency.
How to use IBM MQ as a service?
The techniques necessary to use IBM MQ as a service include:
Lohitashwa Thyagaraj is a Senior Technical Staff Member (STSM) and Master Inventor for IBM Messaging working at the IBM Systems Middleware organization, IBM India Software Lab. Lohit is responsible for defining the strategy and development of IBM WebSphere® Application Server and IBM WebSphere Application Server Liberty messaging portfolio. Lohit is the lead author of the IBM Redpaper publication IBM