Also, keep in mind, you your provided connection factory impl is wrong since you lower-cased the last part while it supposed to be the usual camel-case - https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.javadoc.doc/WMQJMSClasses/com/ibm/mq/jms/MQQueueConnectionFactory.html Also, the url beginning with 'http'. . . I do not believe that is correct. At least I've not seen a configuration like that. Anyway, please reach out to your MQ administrator to get proper values for the required properties. Also, if you be so kind please include the error logs relevant to the controller service (CS). What you are attaching above is related to inability of processor to start which is understandable since it can not start due to the fact that dependent CS is disabled. The real question why the dependent CS is disabled, I mean we do know already that there is configuration issue, but he logs may shed some lights as to what those issues are. ... View more

Andy Sorry to hear you're having some issues. It appears this is a configuration issue. I just dug up some notes from when I was implementing it and it appears you have issues with ConnectionFactory configuration as well as some additional properties required by IBM that would need to be supplied as dynamic properties (see 'IBM specific properties as Dynamic Properties' below). Please see below and let me know. Would love ti help you put this matter to rest. Processor (required properties): - Destination Name: <topic or queue name> (e.g., queue://MYQUEUE) - Destination Type: QUEUE or TOPIC - Session Cache size: 1 (read its doc for more details) - Connection Factory service: <the name of the controller service for CF> (e.g., IBMMQ) Controller Service (e.g., IBMMQ) - MQ Connection Factory Implementation: com.ibm.mq.jms.MQConnectionFactory - MQ Client Libraries path: <path to client JARs from UBM> - Broker URI: <uri to MQ broker> (e.g., foo.bar:1234) Then you would have to configure IBM specific properties as Dynamic Properties: - channel: <name of the channel> (e.g., SYSTEM.ADMIN.SVRCONN) - queueManager: <name of queue managere> (e.g., FOO) - transportType: <identifier of the transport type> (make sure you put '1' as a value which states that TCP/IP will be used) ... View more

Michal The NiFi's convention is to look at attribute -> system-property -> env-variable - in that order. Basically what it means that if it can't find attribute in the FlowFile it will check for system property with the same name and if it can't find one it goes to env-variable etc. Is that what you were looking for? Basically you can declare sys-prop or env-variable and have inbound processors like ConsumeKafka or GetFile to be more dynamic. Cheers Oleg ... View more

Yes, I understand and that's why I am having second thoughts about the check in the processor. In other words we may need to remove it ... View more

Assume nothing 😉 and validate instead. So let's try one step at the time. This documents https://www.rabbitmq.com/management-cli.html describes how you can list exchanges, bindings and queues. $> rabbitmqadmin list queues See if you can see your queue there since the exception you see makes me believe that it is not. ... View more

Is queue "research_test_ defined? Remember that AMQP has a fundamentally different model then your typical messaging. Publisher publishes message NOT on the queue but to the "exchange" from which it gets routed to the queue(s) based on the bindings. So those have to be setup ahead of time. So I am essentially trying to figure out what help are you looking for specifically? Setting up queues, exchanges and bindings is usually the administrative task in Rabbit. Is that the help you need? Getting to the right documentation? ... View more