Skip to Main Content
Merative Ideas Portal

Shape the future of Merative!

We invite you to shape the future of Merative, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the Merative team to refine your idea

Help Merative prioritize your ideas and requests

The Merative team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at Merative works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at Merative, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.


Merative External Privacy Statement: https://www.merative.com/privacy

Status Delivered
Created by CLAIRE MCGAFFEY
Created on Aug 3, 2022

Support for IBM MQ Certified Containers

As part of the SPM Migration to Liberty, research performed by the SPM Cloud team highlighted that the JMS message engine that comes with Liberty does not offer high availability or failover in the same fashion as WebSphere. As a result, SPM is bundled with MQ and can only be used as part of the Cloud Deployment.


We reached out to our top ten customers trying to understand their needs with respect to support for MQ. When customers were asked about hosting IBM MQ as Docker containers, 64% of our customers responded with yes.


Scotland

Once Cloud migration and containerization are planned, I think IBM MQ is a replacement for the current JMS engine (from OOTB product). When we go with the approach of SPM Cloud Journey and Containerization, it will be slightly tricky to explain why MQ alone has to be in a separate offering on a VM. I don't see a strong reason at this point why this can't be an offering?


MSD

Detail not provided but unclear why MQ could not be containerized


Minnesota

Currently the proposed architecture has MQ in the VM which is a tradeoff from cloud native architecture and puts extra strain in maintaining the middleware. Ideally it should be managed as a docker container.


City of New York

I think, it is important for all dependent services to be deployable in K8 to make SPM completely Cloud native.


Customer Name IBM Corp
Market Segment WH Government
Type of Request Idea
Market Opportunity

TBD

  • Attach files