a RECEIVER channel is for qmgr to qmgr connection. If you want your application to connect to the qmgr, you need to define a SVRCONN type channel on the queue manager that the app will use.
Original Message:
Sent: Wed January 22, 2025 08:37 AM
From: Tomáš Matúšek
Subject: IBM ACE 12 integration with IBM MQ 9.4
Thanks for response. Yes the main problem seems to be described by this error from IMB MQ Events Viewer:
1/22/2025 12:30:45 - Process(19096.2) User(tmatusek) Program(rationServer.exe) Host(DESKTOP-CTVKRTC) Installation(Installation1) VRMF(9.4.1.0) Time(2025-01-22T11:30:45.575Z) CommentInsert1(SYSTEM.AUTO.RECEIVER)Type of remote channel not suitable for action requested. The operation requested cannot be performed because channel 'SYSTEM.AUTO.RECEIVER' on the remote machine is not of a suitable type. For example, if the local channel is defined as a sender the remote machine must define its channel as either a receiver or requester. Check that the channel name is specified correctly. If it is, check that the remote channel has been defined correctly.
Questions is what is expected type of channel ? What type is IBM ACE expecting ? The one we used is of type "Receiver", is that correct ? OR can it be defined in IBM ACE ? So it match the chennel type in IBM MQ ?
------------------------------
Tomáš Matúšek
Bratislava
Original Message:
Sent: Wed January 22, 2025 06:54 AM
From: keara will
Subject: IBM ACE 12 integration with IBM MQ 9.4
Hi Tomáš,
It looks like you're on the right track by aiming to log HTTP input/output data into IBM MQ for monitoring purposes. When integrating IBM ACE 12 with IBM MQ 9.4, ensuring the connection works properly between the two is crucial.
For your setup, here are a few things to check that might help resolve the connection issues:
Verify IBM MQ Configuration: Double-check that your MQ Queue Manager is properly configured to accept connections from IBM ACE. Ensure that the connection details in your IBM ACE Policy profile match your IBM MQ Queue Manager's setup, including the correct hostname, port, and queue names.
Monprofile.xml Configuration: Since you're looking to use monprofile.xml
to capture data, make sure that the necessary configurations for logging HTTP request/response data are correctly set in that file. It's important that the file is placed in the correct directory and the overrides are accurately defined in your Integration Service.
Permissions: Confirm that the IBM MQ server has the necessary permissions to read and write to the queues you're working with. You might need to adjust the user access rights for the ACE integration server to successfully interact with MQ.
Firewall & Ports: Ensure there are no firewall issues or port restrictions between IBM ACE and IBM MQ. This can sometimes be a cause of connection failures, especially in a local development environment.
Log Files: Check the logs for both IBM ACE and MQ for any error messages related to the connection issue. They often provide more specific details about the underlying problem.
By resolving the connection issue and ensuring all configurations are correct, you should be able to test your solution in the local environment before moving to production.
------------------------------
keara will
Original Message:
Sent: Wed January 22, 2025 06:38 AM
From: Tomáš Matúšek
Subject: IBM ACE 12 integration with IBM MQ 9.4
Hi,
we are trying to achieve a goal of logging all HTTP Input / Output request / response data into IMB MQ for business data monitoring, for now just for local environment to test the solution. We are planning to use monprofile.xml at the level of override folder inside Integration Service to achieve that.
My local dev env:
- Windows 11 Pro 24H2
- IBM App Connect Enterprise Toolkit Version: 12.0.12.4
- IBM MQ for Windows Version 9.4.1.0
- IBM MQ Explorer Version: 9.4.1.0
1) Step one for us is to make connection from IBM App Connect Enterprise Toolkit Version: 12.0.12.4 but we are facing some issues.
Here is IBM ACE Policy profile that id deployed to the local Integration Server:
<?xml version="1.0" encoding="UTF-8"?><policies> <policy policyType="MQEndpoint" policyName="ibm-mq2" policyTemplate="MQEndpoint"> <connection>CLIENT</connection> <destinationQueueManagerName>QM1</destinationQueueManagerName> <queueManagerHostname>127.0.0.1</queueManagerHostname> <listenerPortNumber>1414</listenerPortNumber> <channelName>IBMACE_RECEIVER</channelName> <securityIdentity></securityIdentity> <useSSL>false</useSSL> <SSLPeerName></SSLPeerName> <SSLCipherSpec></SSLCipherSpec> <CCDTUrl></CCDTUrl> <SSLCertificateLabel></SSLCertificateLabel> <MQApplName></MQApplName> <reconnectOption>default</reconnectOption> </policy></policies>
But from console.log we are getting this kid of error:
2025-01-22 10:31:04.224357: An error occurred publishing integration node event on topic '$SYS/Broker/integration_server/ResourceStatistics/TEST_SERVER/' using the 'MQ' transport. 2025-01-22 10:31:04.224476: Failed to make a client connection to queue manager 'QM1' using hostname '127.0.0.1' on port '1414': MQCC=2; MQRC=2539.
Here is detail of IMB MQ configuration where we defined QM1 and IBMACE_RECEIVER channel:
And this is error detail from IMB MQ server:
1/22/2025 12:30:45 - Process(19096.2) User(tmatusek) Program(rationServer.exe) Host(DESKTOP-CTVKRTC) Installation(Installation1) VRMF(9.4.1.0) Time(2025-01-22T11:30:45.575Z) CommentInsert1(SYSTEM.AUTO.RECEIVER)Type of remote channel not suitable for action requested. The operation requested cannot be performed because channel 'SYSTEM.AUTO.RECEIVER' on the remote machine is not of a suitable type. For example, if the local channel is defined as a sender the remote machine must define its channel as either a receiver or requester. Check that the channel name is specified correctly. If it is, check that the remote channel has been defined correctly.
So my questions is what we are doing wrong and if there is any step by step guider from connecting IBM MQ to the Integration Server and how to configure IBM MQ correctly because based on the error detail it looks like IBM ACE or IMB MQ Queue manager is incorrectly configured.
It would be great if anyone can help us to figure out what's wrong.
If you need any further details, configuration, versions and so on, please let us know.
THANKS!
------------------------------
Tomáš Matúšek
------------------------------