This plug-in allows Appian to connect with IBM Messaging Queue (MQ) version 7.5 and other brokers that support Advanced Message Queuing Protocol (AMQP).
It provides smart services to:
The download package includes the plug-in and its associated documentation
Version 2 (10-21-18) uses a different plug-in key and therefore will not affect the use of the previous version.
I have also had the same problem.
2024-09-12 00:46:53,056 [ActiveMQ VMTransport: vm://localBroker#1-1] DEBUG org.apache.activemq.broker.region.AbstractRegion - localBroker adding destination: topic://ActiveMQ.Advisory.Connection2024-09-12 00:46:53,061 [ActiveMQ VMTransport: vm://localBroker#1-1] DEBUG org.apache.activemq.broker.region.AbstractRegion - localBroker adding consumer: ID:swjpto4201tv-58836-1726102012812-4:1:-1:1 for destination: ActiveMQ.Advisory.TempQueue,ActiveMQ.Advisory.TempTopicException in thread "HandshakeCompletedNotify-Thread" java.lang.UnsupportedOperationException: This method is deprecated and marked for removal. Use the getPeerCertificates() method instead. at java.base/javax.net.ssl.SSLSession.getPeerCertificateChain(SSLSession.java:295) at java.base/javax.net.ssl.HandshakeCompletedEvent.getPeerCertificateChain(HandshakeCompletedEvent.java:173) at com.ibm.mq.jmqi.remote.impl.RemoteTCPConnection.handshakeCompleted(RemoteTCPConnection.java:2187) at java.base/sun.security.ssl.TransportContext$NotifyHandshake$1.run(TransportContext.java:701) at java.base/sun.security.ssl.TransportContext$NotifyHandshake$1.run(TransportContext.java:698) at java.base/java.security.AccessController.doPrivileged(AccessController.java:399) at java.base/sun.security.ssl.TransportContext$NotifyHandshake.run(TransportContext.java:698) at java.base/java.lang.Thread.run(Thread.java:842)
James Carter Hi! This plugin does not work in the new 24.2 Appian Version due JAVA 17. Other plugins like Advance Call WebService have been updated to solve this, could it be possible with this one too, thanks!
Thanks for asking this. Was there any success in using this plugin with IBM MQ 9.1?
James CarterPlease help me with tibco topic connection for messaging system
Please help me with tibco connection for messaging system
What does your Queue Config look like? I would expect the following to work as expected. A constant couldn't be used for the whole Queue Config, but they can be for the individual CDT attributes
'type!{urn:appian:ps:jms}IBMMQConfig'( host: cons!MQ_HOST, ...)
James Carter The plugin is working good for me. Currently I have hardcode the connection string in "Que Config" node of "JMS Message Producer". To generalize it, I am trying to use Constant to store the connection string, and make this this constant environment specific.
When I pass this connection string to the plug-in using constant, it throws below error .
"com.appiancorp.plugins.typetransformer.AppianPrimitive cannot be cast to com.appiancorp.plugins.typetransformer.AppianObject"
Can you please help if this can be reoslved?
Thanks Again.
April SchuppelCan you please let me know if there is any support form Appian to update the plug-in? Is there any sample/example that is developed to implement MQ connectivity using Integration SDK?
Also, any details on how to install this plug in would be helpful.
Thanks,
Pooja
Hi pooja.sudarshan,
This plug-in hasn't been updated since October 2018 and was created with the intention of using with IBM MQ 7.5 so it was likely not tested with v9.1.0.3. It may be worth updating this plug-in or using our Integration SDK that was released with Appian 19.1 to created a connected system to IBM MQ.