Has anyone successfully connected the 4.x version of RocketMQ to IBM MQ queues on Z/OS using the JMS connectivity? What issues did you encounter and what were the specific use cases/patterns enabled? Thank you in advance for your responses.
Related
Recently i restarted amazonmq machine, all the queues were lostðŸ˜.I see only the activeMQ has support for storage using EBS/EFS. is there anything am i missing ?
RabbitMQ is durable with EBS.
"RabbitMQ brokers can be created as single-instance brokers or in a cluster deployment. For both deployment modes, Amazon MQ provides high durability by storing its data redundantly."
RabbitMQ Broker Documentation
Console Reboot
Is there a way to find the count of messages in IBM MQ in Mule.
Thanks in advance
It is not possible. The Mule IBM MQ Connector has operations to read and publish messages, but none for performing queue management functions or queries.
It is because the connector implementation uses the Java JMS API application which has that limitation.
Note that usually client's of message brokers consume messages but don't attempt to query or control que queues.
You can find IBM MQ admin commands to query the information.
Axon Framework supports Distributing Events which should allow to post events to the external message broken and read events from message broker.
Amazon provides two different messaging services
Amazon Simple Queue Service (SQS)
Amazon MQ
Questions:
What Amazon messaging service might be used (SQS, MQ or may be both) as message queue with Axon Framework?
What is the best practice for implementing distributed Axon message processing in Amazon EC2 cloud?
It looks like that Amazon MQ should work fine with Axon Framework as message queue because it supports AMQP. But I failed to find any references about any practical experience using MQ with Axon.
Any messaging service implementation which supports, AMQP should work just fine with the Axon Framework. More specifically together with the axon-amqp dependency, as you might already have found out.
Without personally having any experience with Amazon SQS or MQ, I did a quick search on both, and it seems Amazon MQ is indeed the go to solution to distributed your events on Amazon EC2.
I do not have or heard any best practices for distributed your Axon Framework events over Amazon EC2 specifically, sadly enough, but I can share this.
All the Axon Framework (when adding the axon-amqp dependency) does, is subscribe to the EventBus and publish any incoming events on a queue; no further specifics.
Hence I'd say any best practices for general use of Amazon MQ should apply on your second question.
We are using mainframe application and from mainframe we write lots of messages to MQ to send to downstream. We are planning to migrate from MQ to Solace on mainframe. Is it possible? Solace supports mainframe applications?
How can we put messages to solace from mainframe batch and online(IMS transactions)?
Thanks,
Praveen.
Solace does not support mainframe applications directly but Solace can be easily integrated with IBM DataPower appliances which can interface with mainframe applications. The DataPower appliance can handle the transformation requirement of the service and the Solace appliance can handle the messaging portion to provide quick and efficient message delivery downstream.
The 'Solace Integration with IBM Datapower' integration guide, available on the Solace Developer Portal, has more information on this:
http://dev.solacesystems.com/integration-guides/ibm-datapower/
You may also be able to use Solace's REST interface, depending on your Mainframe application. Solace's REST interface allows communication using standard POST HTTP requests.
There are also guides for Solace's REST interface available on the Solace Developer Portal:
http://dev.solacesystems.com/docs/open-apis-protocols-docs/
Old thread, but Mainframe is a long lasting tech.
Solace now provide an open-source bridge for IBM MQ Bridge, so MainFrame<->IBM MQ<->Solace is possible.
Datapower integration using JMS to connect to Solace is still possible.
Solace REST Messaging API is still possible.
And finally OpenLegacy can help here :
https://www.openlegacy.com/
I have an activeMQ network with 2 instances. Those 2 instances are running 5.5 version of activeMQ. I want to add a new server in 5.9 version. Is this feasible? What should I have in mind? Any gotchas?
Thanks.
We don't test the network of brokers between versions. It may work but we encourage users to upgrade all their brokers to the latest release once the messages contained in those broker's stores have been migrated to a new broker. You can do this by networking an older broker to a newer one and then creating a subscription on any destination that has messages on the old broker on the new one and letting the demand drain the old broker.