Cloud Pak for Integration

 View Only

  • 1.  ACE to MQ connectivity

    Posted Tue February 21, 2023 09:07 AM

    Hi All,

    I have installed a setup on a server for ACE and MQ where I am unable to establish a connection between them when I deploy an application with the MQ details using MQ Client Connection Properties where I specify all the details needed and run the application I get an MQRC 2035 error

    note: ACE is run as root user and my MQ has default mqm users. 

    If you have any suggestion kindly reach out to help.

    PFB error:

    Exception. BIP2230E: Error detected whilst processing a message in node 'mq.MQ Output'. : /build/jenkins_swg/slot0/product-build/WMB/src/DataFlowEngine/TemplateNodes/ImbOutputTemplateNode.cpp: 260: ImbOutputTemplateNode::processMessageAssemblyToFailure: ComIbmMQOutputNode: mq#FCMComposite_1_3 BIP2677E: Failed to make a client connection to queue manager 'QM_NEFT' using hostname '172.16.3.124' on port '8090': MQCC=2; MQRC=2035. : /build/jenkins_swg/slot0/product-build/WMB/src/DataFlowEngine/Connectors/mqconnector/MQConnection.cpp: 574: MQConnection::open:



    ------------------------------
    Ahmad Raza Khan
    ------------------------------



  • 2.  RE: ACE to MQ connectivity

    Posted Wed February 22, 2023 05:13 AM

    Hi

    How did you provide the MQ Client Connection information to your ACE Application? Did you use a MQEndpoint policy? If not, can you try that: MQEndpoint policy

    Regards 

    Niki

    <quillbot-extension-portal></quillbot-extension-portal>



    ------------------------------
    Niki Heyligen
    ------------------------------

    Original Message


  • 3.  RE: ACE to MQ connectivity

    Posted Wed February 22, 2023 09:33 AM

    If you have mq v 9 then by default queue manager chlauth is enabled. If you are on dev then disabled this at queue manager level.

    for higher environment set required auth permission on the channel you are using.



    ------------------------------
    sameep jangir
    ------------------------------

    Original Message


  • 4.  RE: ACE to MQ connectivity

    Posted Tue September 24, 2024 06:58 PM

    Hello, I have the same problem, I wanted to know if you found the solution



    ------------------------------
    Samuel Martinez
    ------------------------------

    Original Message


  • 5.  RE: ACE to MQ connectivity

    Posted Wed September 25, 2024 12:58 AM

    Are you running these under OCP (OpenShift)?  Did you check the MQ logs for what the actual error was and which Object(s) you do not have access?

    If you are running this outside of OCP, then the problem might be that ACE sends the user "aceuser" identification to the QMGR and if the QMGR does not have that user allowed then it will fail with a 2035 (Auth error).  You can add the necessary authrecs in MQ to overcome this.

    ACE and MQ on OCP: https://github.com/bpaskin/MQ-ACE-OCP-Demo

    ACE and MQ in containers: https://github.com/bpaskin/MQ-ACE-zCX

    Brian



    ------------------------------
    Brian S Paskin
    Sr. Technology Engineer
    IBM Cloud Engineering
    ------------------------------

    Original Message


  • 6.  RE: ACE to MQ connectivity

    Posted Fri September 27, 2024 02:38 PM

    Are you using an MQ Endpoint policy on ACE to connect to MQ? The error as quoted above is due to the MQ QMGR not having the permission to allow the connection in. You'll need to run these commands on MQ to start with, also ensure you have created a SVRCONN channel on MQ and specified the same in the MQ endpoint policy xml.

        set chlauth(*) TYPE(BLOCKUSER) USERLIST(*MQADMIN) ACTION(REMOVE)
        set chlauth(SYSTEM.ADMIN.SVRCONN) TYPE(ADDRESSMAP) ADDRESS(*) ACTION(REMOVE)
        alter authinfo(SYSTEM.DEFAULT.AUTHINFO.IDPWOS) authtype(IDPWOS) CHCKCLNT(NONE) CHCKLOCL(NONE)

        refresh security type(authserv)
        refresh security type(connauth)



    ------------------------------
    Abu Davis
    ------------------------------

    Original Message