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.
April Schuppel The documentation does not have information about version compatibility.
I would like to know if this is feasible to use for version 9.1.0.3?
Our functionality is to send message to destination system from application developed in Appian.
Thanks April.
Hi pooja.sudarshan, the documentation is included in the download package.
Can we use this plugin for MQ version 9.1.0.3?
Where can I find documentation for IBM MQ setup in Appian?
Thanks,
Pooja
The previous Problem was solved by restarting the Server. Now we have a Problem reading the message but we are going to try to solve it through the professional Services team
Hi there,
We are using the plugin jms-2.0.0.jar to send a message to an IBM MQ Queue in the way described in the documentation. However we always see the following error message in the log:
2019-02-11 15:13:48,256 [Appian Work Item - 8674 - execution01 : UnattendedJavaActivityRequest] WARN com.appiancorp.process.engine.UnattendedJavaActivityRequest - An error occurred while executing activity: id=268451385, classname=com.appiancorp.ps.jms.smartservice.MessageProducerSmartService. This action will be retried until it succeeds or the maximum retry period is reached. Details: com.ibm.msg.client.jms.DetailedJMSException: JMSWMQ0018: Failed to connect to queue manager 'BA74' with connection mode 'Client' and host name 'blbmq-ba74(19074)'.
We have checked with the MQ Team that the Queue Connection Settings are correct:
[host=blbmq-ba74, port=19074, queueManager=BA74, channel=JAVA.BPMS.BA74.1, cipherSuite=, clientId=, queue=MQBP0001.APPIAN.REQUEST.TO.IB, topic=, subscriptionName=]
Any idea about why it could fail? The MQ Team says that the channel Name is incorrect, with an extra blank space " JAVA.BPMS.BA74.1" which was a Problem at the beginning but the model was corrected and published. Old instances have been deleted but still we cant connect.
Any idea would be highly appreciated!