IBM Product Briefing 

Securely and reliably move data to where it needs to be, on premises, in clouds, or both.

IBM MQ acts as a messaging centre, reliably moving messages between applications, services and systems on varied platforms to reduce integration time and cost. IBM has expertly refined MQ over more than 25 years in the market. With MQ, if a message can’t be delivered immediately, it’s secured in a queue where it waits until delivery is assured.

• Connect virtually everything wherever it is, delivering messages once and once only. Never lose a message with MQ.
• Protect data at every stage of the journey – at rest, in-flight, and in-memory, protected through fine-grained authentication and powerful end-to-end encryption.
• Simplify and accelerate the development of applications with built-in transactionality, security, and connectivity capabilities that free developers to spend time on more critical initiatives.

Product names relevant to this briefing include IBM Integration, MQ Series, IBM MQ, MQIPT, WebSphere MQ.

IBM knowledge centre

Using MQIPT to securely pass MQ traffic through your DMZ

Business Drivers

Massive amounts of data move as messages between applications, systems, and services at any given time. If an application isn’t ready, or if there’s a service interruption, messages and transactions can be lost or duplicated, costing businesses time and money to make things right.

Only IBM MQ offers end-to-end, message-level encryption and the ability to deliver messages once and once only. Whereas other messaging providers have come and gone, IBM MQ has been reliably offering a strong messaging solution for over 25 years, and is backed by IBM’s exemplary support as well as multiple vibrant communities who are passionate about IBM MQ. That’s why over half of the Fortune 500 rely on IBM MQ, including 85% of the Fortune 100, 96% of the top 100 global banks, and 80% of the top 10 airlines.

Key Capabilities of IBM MQ

• A single, robust messaging backbone for dynamic, heterogeneous environments
• Once and once only delivery of messages
• End-to-end message-level encryption with TLS (Transport Layer Security) protecting messages on the move, and message-level encryption protecting the messages themselves (better than competitors who protect the disk rather than the message)
• Protection during downtime with High Availability and Disaster Recovery
• High-performance message transport to deliver business-critical and high-value data
• Integrated tooling and access to open standards
• Variety of deployment options: software, appliance, mainframe, clouds

Why would you be interested?

IBM MQ is used across all geographies and industries. Key industries are banking, financial, retail, insurance, pharmaceutical and government. If you need to move high value data that should not be compromised, lost or duplicated then consider MQSeries in your solution.

If you are concerned about;

• Meeting compliance with regulations and protect against breaches of inflight data
• Have a homegrown Messaging solution or JMS (Java Messaging Service) deployment
• Are currently moving files with FTP (File Transfer Protocol) or scripts
• Integrating both new and old applications together
• Have concerns about data loss
• Concerns about data security

Enterprise Architects

Enterprise Architects want a reliable and secure solution that will increase efficiency, save cost, and help the company to innovate. MQSeries is highly scalable and feature rich, this will ensure that future projects and requirements will be supported by the product.

MQ/IT Administrators

Administrators want to easily integrate and maintain their infrastructure, without being derailed by developers choosing rogue technologies or not understanding how to use it. Implementing a standard messaging solution that works across all platforms, reduces overall complexity of the IT infrastructure.

Application Developers using IBM MQ

Developers want to get coding quickly, IBM MQSeries offers Application Programming Interfaces (APIs) specific to particular operating systems that all use the same “VERBS” such as PUT & GET to place a message on a queue and read a message from a queue. So for example a .Net developer will code in .Net and ‘PUT’ messages on a queue and a Java developer will code in Java and “GET” message from the delivery queue. MQ can be configured to manage “code pages” and “endian-ness” if required. Since the MQSeries API uses the same “VERBS” it is simple for the two developers to view each other’s code and quickly understand what is happening.