@Bryan Bende Do I have to use StandardSSLContextService to connect to IBM mq if my nifi.properties is configured with SSL Authentication for web browser? If I have to, could I use the same certificate that I created for web browser for IBM MQ (I use nifi.pfx for the web browser)? ... View more

update: I finally figured out how to setup IBM MQ for Nifi Here is my steps to setup IBM MQ for the Nifi connection 1) Create queue manager myMQManager using MQ Explorer 2) create Channel and queue using the following commands runmqsc myMQManager def chl(myMQChannel) chltype(svrconn) replace def chl(myMQChannel) chltype(clntconn) conname('localhost(1420)') QMNAME('myMQManager') replace def ql(myMQqueue) 2) Grant necessary authorization for a user using MQ Explorer 2.1 Queue Manager Authorities Setting right click your queue manager-->Object Authorities-->Add Role Based Authorities -->give the user access permission 2.2 Queue Authorities Setting right click your queue-->Object Authorities-->Manage Authority Records-->Specific Profiles--> your queue--> Accumulated authorities-->setup your user Access Permission for the queue 3) After the configuration and setup your Nifi ConsumeJMS processor, you should be able connect to IBM MQ ... View more

@ozhurakousky Here is the steps to setup IBM MQ for the Nifi connection 1) Create queue manager myMQManager using MQ Explorer 2) create Channel and queue using the following commands runmqsc myMQManager def chl(myMQChannel) chltype(svrconn) replace def chl(myMQChannel) chltype(clntconn) conname('localhost(1420)') QMNAME('myMQManager') replace def ql(myMQqueue) 2) Grant necessary authorization for a user using MQ Explorer 2.1 Queue Manager Authorities Setting right click your queue manager-->Object Authorities-->Add Role Based Authorities -->give the user access permission 2.2 Queue Authorities Setting right click your queue-->Object Authorities-->Manage Authority Records-->Specific Profiles--> your queue--> Accumulated authorities-->setup your user Access Permission for the queue 3) After the configuration and setup your Nifi ConsumeJMS processor, you should be able connect to IBM MQ ... View more

@ozhurakousky of course, I will post what I did on the IBM MQ here later today. ... View more

@ozhurakousky Hi Oleg, I finally got the connection between Nifi and IBM MQ working now. It's some configuration issue on MQ. Thank you very much for your help and time. I am very appreciated. Andy ... View more

@ozhurakousky Hi Oleg, I had re-installed IBM MQ and setting up the queue manager, Channel, listener, and queue. I will do more testing on Nifi and post the result. Thanks a lot Andy ... View more

@ozhurakousky Thanks a lot for taking time to help me. Yeah, I had tired your suggestion. and I just wrote a very detail message on what I did on the previous post. ... View more

@ozhurakouskyThanks for the advice and your time. I had setup the processor as the following: Controller Service and Processor For the IBM MQ side 1) I found the channel SYSTEM.ADMIN.SVRCONN , do I need to create a sender channel or it's already built in? 2) I already have a listener for Nifi (localhost:1419) 3) I create a local queue Q1 (do I have to set it's Usage to transmission?) 4) I got the following error: ConsumeJMS - JMSConsumer[destination:null; pub-sub:false;] ConsumeJMS - JMSConsumer[destination:null; pub-sub:false;] failed to process due to org.springframework.jms.UncategorizedJmsException: Uncategorized exception occured during JMS processing; nested exception is com.ibm.msg.client.jms.DetailedJMSException: JMSWMQ0018: Failed to connect to queue manager 'NifiMQ' with connection mode 'Client' and host name 'localhost(1419)'. Check the queue manager is started and if running in client mode, check there is a listener running. Please see the linked exception for more information.; nested exception is com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2540' ('MQRC_UNKNOWN_CHANNEL_NAME').; rolling back session: org.springframework.jms.UncategorizedJmsException: Uncategorized exception occured during JMS processing; nested exception is com.ibm.msg.client.jms.DetailedJMSException: JMSWMQ0018: Failed to connect to queue manager 'NifiMQ' with connection mode 'Client' and host name 'localhost(1419)'. Check the queue manager is started and if running in client mode, check there is a listener running. Please see the linked exception for more information.; nested exception is com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2540' ('MQRC_UNKNOWN_CHANNEL_NAME'). Is there Any other configuration that I missed? Thanks a lot. @ozhurakousky I am really appreciated for your help and your time. ... View more

@Matt Clarke I had read the posts at https://community.hortonworks.com/questions/35871/consumejms-failed-to-load-the-websphere-mq-native.html and https://community.hortonworks.com/questions/35871/consumejms-failed-to-load-the-websphere-mq-native.html I followed the instructions to configure the onsumeJMS and PublishJMS processors, but I cannot get it working. I wonder it's the configuration issue on the IBM MQ. For example, how could I set up the SYSTEM.ADMIN.SVRCONN for channel or is it build-in already? Do I need to create a transmission queue for the channel? ... View more