I followed everything mentioned in the below blog but couldn't see any messages in the event queue.. any suggestions for making this work. I need help as soon as possible.

https://community.ibm.com/community/user/integration/blogs/amar-shah1/2023/05/12/configuring-ibm-app-connect-enterprise-for-publish 

Thanks in advance.

Hi Shreya,

There are quite a few steps in Amar's blog so it's difficult to precisely answer your question immediately. To help narrow down the problem it would be helpful to know if the message flow itself is successfully processing messages (aside from publishing events!) ... The example uses a simple flow to take messages from one queue and write them to an output queue. An MQEndpoint policy is used to define the relationship with the queue manager (the hostname of the queue manager, port number etc). Do you see messages going between the queues? If not, can you check the open input count of the input queue (when the flow is started you should see this go from 0 to 1) ? If the connection to MQ is all good, then the next thing to check is that there were no typos in the event publish/subscription configuration such as the correct topic string and destination queue. If these look good, then you could try publishing from another app to ensure that the settings really are right. You could then investigate the other parts of the ACE configuration - is the server.conf.yaml syntactically correct? Are there any errors reported by the integration server when it starts? Note that the server.conf.yaml settings should be made before starting up the server. Finally, when configuring the event settings in the message flow, did you definitely associate the events with the correct terminals on the nodes? Hopefully the above comments might give you a few things to check next - let us know how you get on!

I followed everything mentioned in the below blog but couldn't see any messages in the event queue.. any suggestions for making this work. I need help as soon as possible.

https://community.ibm.com/community/user/integration/blogs/amar-shah1/2023/05/12/configuring-ibm-app-connect-enterprise-for-publish 

Thanks in advance.

Hi Ben, first of all thanks a lot for writing me back.

So, as you suggested I tried following the steps taking care of all the points you mentioned, and I am able to see the messages coming in my queue now!! :)

But now my next concern is this - So in my service we have a code written (it is for a migration project so I cannot change the code) to log the details from the destination queue into the DataBase table. I followed the similar steps for my application and the messages are received in the destination queue. But the only challenge is, it is only getting received in the queue named as EVENTS and not in EVENT.IN even after changing the destination queue name in subscription to EVENT.IN. Does it have anything to do with the naming convention? or there is something else that I should check to resolve this issue.

Hi Shreya,

There are quite a few steps in Amar's blog so it's difficult to precisely answer your question immediately. To help narrow down the problem it would be helpful to know if the message flow itself is successfully processing messages (aside from publishing events!) ... The example uses a simple flow to take messages from one queue and write them to an output queue. An MQEndpoint policy is used to define the relationship with the queue manager (the hostname of the queue manager, port number etc). Do you see messages going between the queues? If not, can you check the open input count of the input queue (when the flow is started you should see this go from 0 to 1) ? If the connection to MQ is all good, then the next thing to check is that there were no typos in the event publish/subscription configuration such as the correct topic string and destination queue. If these look good, then you could try publishing from another app to ensure that the settings really are right. You could then investigate the other parts of the ACE configuration - is the server.conf.yaml syntactically correct? Are there any errors reported by the integration server when it starts? Note that the server.conf.yaml settings should be made before starting up the server. Finally, when configuring the event settings in the message flow, did you definitely associate the events with the correct terminals on the nodes? Hopefully the above comments might give you a few things to check next - let us know how you get on!

I followed everything mentioned in the below blog but couldn't see any messages in the event queue.. any suggestions for making this work. I need help as soon as possible.

https://community.ibm.com/community/user/integration/blogs/amar-shah1/2023/05/12/configuring-ibm-app-connect-enterprise-for-publish 

Thanks in advance.

Hi Shreya,

Great to hear that you managed to get the steps described in the article working correctly. I don't see any problem with the name "EVENT.IN" so I dont think the queue name can be blamed for why you are not appearing to receive messages once you have updated your subscription.  Some things you could check ...

1. Did the update to the subscription complete successfully - ie did you receive any error message when you attempted this? How did you make the update (through a UI or using a command?) ? Did the userid with which you made the update have sufficient authority to update the subscription successfully? 

2. If you go back and look at the configuration, has the destination queue name been updated and is it showing as EVENT.IN ? Were there any typos in the name you supplied? 

3. Do you see the same behaviour (no publications) if you create an entirely new subscription which uses the same topic string but sets the EVENT.IN queue name?

4. Also worth checking - you are sending fresh messages through the main flow (which should cause the events to be published) ? Is that flow working correctly still (do you see messages coming through the queues used by the main flow?) ? 

5. Also worth checking the open input count of the EVENT.IN queue ... is it possible that the publications are in fact happening but maybe another application is perhaps reading the messages already and attempting to process them so you don't see them on the queue?

Cheers,

Ben

Hi Ben, first of all thanks a lot for writing me back.

So, as you suggested I tried following the steps taking care of all the points you mentioned, and I am able to see the messages coming in my queue now!! :)

But now my next concern is this - So in my service we have a code written (it is for a migration project so I cannot change the code) to log the details from the destination queue into the DataBase table. I followed the similar steps for my application and the messages are received in the destination queue. But the only challenge is, it is only getting received in the queue named as EVENTS and not in EVENT.IN even after changing the destination queue name in subscription to EVENT.IN. Does it have anything to do with the naming convention? or there is something else that I should check to resolve this issue.

Hi Shreya,

There are quite a few steps in Amar's blog so it's difficult to precisely answer your question immediately. To help narrow down the problem it would be helpful to know if the message flow itself is successfully processing messages (aside from publishing events!) ... The example uses a simple flow to take messages from one queue and write them to an output queue. An MQEndpoint policy is used to define the relationship with the queue manager (the hostname of the queue manager, port number etc). Do you see messages going between the queues? If not, can you check the open input count of the input queue (when the flow is started you should see this go from 0 to 1) ? If the connection to MQ is all good, then the next thing to check is that there were no typos in the event publish/subscription configuration such as the correct topic string and destination queue. If these look good, then you could try publishing from another app to ensure that the settings really are right. You could then investigate the other parts of the ACE configuration - is the server.conf.yaml syntactically correct? Are there any errors reported by the integration server when it starts? Note that the server.conf.yaml settings should be made before starting up the server. Finally, when configuring the event settings in the message flow, did you definitely associate the events with the correct terminals on the nodes? Hopefully the above comments might give you a few things to check next - let us know how you get on!

I followed everything mentioned in the below blog but couldn't see any messages in the event queue.. any suggestions for making this work. I need help as soon as possible.

https://community.ibm.com/community/user/integration/blogs/amar-shah1/2023/05/12/configuring-ibm-app-connect-enterprise-for-publish 

Thanks in advance.

Hello Ben,

Is it possible to use the Monitoring Profile.xml file to define the node's terminals to be monitored instead of adding the terminals in "Monitoring" tab? If yes.. do we have any IBM documentation o  how to do it on the ACE 12 hosted on OCP?

Hi Shreya,

Great to hear that you managed to get the steps described in the article working correctly. I don't see any problem with the name "EVENT.IN" so I dont think the queue name can be blamed for why you are not appearing to receive messages once you have updated your subscription.  Some things you could check ...

1. Did the update to the subscription complete successfully - ie did you receive any error message when you attempted this? How did you make the update (through a UI or using a command?) ? Did the userid with which you made the update have sufficient authority to update the subscription successfully? 

2. If you go back and look at the configuration, has the destination queue name been updated and is it showing as EVENT.IN ? Were there any typos in the name you supplied? 

3. Do you see the same behaviour (no publications) if you create an entirely new subscription which uses the same topic string but sets the EVENT.IN queue name?

4. Also worth checking - you are sending fresh messages through the main flow (which should cause the events to be published) ? Is that flow working correctly still (do you see messages coming through the queues used by the main flow?) ? 

5. Also worth checking the open input count of the EVENT.IN queue ... is it possible that the publications are in fact happening but maybe another application is perhaps reading the messages already and attempting to process them so you don't see them on the queue?

Cheers,

Ben

Hi Ben, first of all thanks a lot for writing me back.

So, as you suggested I tried following the steps taking care of all the points you mentioned, and I am able to see the messages coming in my queue now!! :)

But now my next concern is this - So in my service we have a code written (it is for a migration project so I cannot change the code) to log the details from the destination queue into the DataBase table. I followed the similar steps for my application and the messages are received in the destination queue. But the only challenge is, it is only getting received in the queue named as EVENTS and not in EVENT.IN even after changing the destination queue name in subscription to EVENT.IN. Does it have anything to do with the naming convention? or there is something else that I should check to resolve this issue.

Hi Shreya,

There are quite a few steps in Amar's blog so it's difficult to precisely answer your question immediately. To help narrow down the problem it would be helpful to know if the message flow itself is successfully processing messages (aside from publishing events!) ... The example uses a simple flow to take messages from one queue and write them to an output queue. An MQEndpoint policy is used to define the relationship with the queue manager (the hostname of the queue manager, port number etc). Do you see messages going between the queues? If not, can you check the open input count of the input queue (when the flow is started you should see this go from 0 to 1) ? If the connection to MQ is all good, then the next thing to check is that there were no typos in the event publish/subscription configuration such as the correct topic string and destination queue. If these look good, then you could try publishing from another app to ensure that the settings really are right. You could then investigate the other parts of the ACE configuration - is the server.conf.yaml syntactically correct? Are there any errors reported by the integration server when it starts? Note that the server.conf.yaml settings should be made before starting up the server. Finally, when configuring the event settings in the message flow, did you definitely associate the events with the correct terminals on the nodes? Hopefully the above comments might give you a few things to check next - let us know how you get on!

I followed everything mentioned in the below blog but couldn't see any messages in the event queue.. any suggestions for making this work. I need help as soon as possible.

https://community.ibm.com/community/user/integration/blogs/amar-shah1/2023/05/12/configuring-ibm-app-connect-enterprise-for-publish 

Thanks in advance.

Hi Arun,

Yes you can use a monitoring profile to define the monitoring events you would like ... The following page documents how this can be configured (the nominated profile can be specified as a default in server.conf.yaml which is probably the most convenient way for containers as it allows the specific profile to be chosen as a piece of configuration as part of instantiating the container). The entry defines a chosen monitoring profile defined as an xml file, for example, monitoringProfileName.monprofile.xml which is placed inside a policy project ... which can be made available to the container in the normal way (either carried into the container within a BAR file, or as part of the policies which are laid on disk in the container by the App Connect Operator). Details about the monitoring profile itself are in the documentation here:

https://www.ibm.com/docs/en/app-connect/12.0?topic=basics-monitoring-profiles

Cheers,

Ben

Hello Ben,

Is it possible to use the Monitoring Profile.xml file to define the node's terminals to be monitored instead of adding the terminals in "Monitoring" tab? If yes.. do we have any IBM documentation o  how to do it on the ACE 12 hosted on OCP?

Hi Shreya,

Great to hear that you managed to get the steps described in the article working correctly. I don't see any problem with the name "EVENT.IN" so I dont think the queue name can be blamed for why you are not appearing to receive messages once you have updated your subscription.  Some things you could check ...

1. Did the update to the subscription complete successfully - ie did you receive any error message when you attempted this? How did you make the update (through a UI or using a command?) ? Did the userid with which you made the update have sufficient authority to update the subscription successfully? 

2. If you go back and look at the configuration, has the destination queue name been updated and is it showing as EVENT.IN ? Were there any typos in the name you supplied? 

3. Do you see the same behaviour (no publications) if you create an entirely new subscription which uses the same topic string but sets the EVENT.IN queue name?

4. Also worth checking - you are sending fresh messages through the main flow (which should cause the events to be published) ? Is that flow working correctly still (do you see messages coming through the queues used by the main flow?) ? 

5. Also worth checking the open input count of the EVENT.IN queue ... is it possible that the publications are in fact happening but maybe another application is perhaps reading the messages already and attempting to process them so you don't see them on the queue?

Cheers,

Ben

Hi Ben, first of all thanks a lot for writing me back.

So, as you suggested I tried following the steps taking care of all the points you mentioned, and I am able to see the messages coming in my queue now!! :)

But now my next concern is this - So in my service we have a code written (it is for a migration project so I cannot change the code) to log the details from the destination queue into the DataBase table. I followed the similar steps for my application and the messages are received in the destination queue. But the only challenge is, it is only getting received in the queue named as EVENTS and not in EVENT.IN even after changing the destination queue name in subscription to EVENT.IN. Does it have anything to do with the naming convention? or there is something else that I should check to resolve this issue.

Hi Shreya,

There are quite a few steps in Amar's blog so it's difficult to precisely answer your question immediately. To help narrow down the problem it would be helpful to know if the message flow itself is successfully processing messages (aside from publishing events!) ... The example uses a simple flow to take messages from one queue and write them to an output queue. An MQEndpoint policy is used to define the relationship with the queue manager (the hostname of the queue manager, port number etc). Do you see messages going between the queues? If not, can you check the open input count of the input queue (when the flow is started you should see this go from 0 to 1) ? If the connection to MQ is all good, then the next thing to check is that there were no typos in the event publish/subscription configuration such as the correct topic string and destination queue. If these look good, then you could try publishing from another app to ensure that the settings really are right. You could then investigate the other parts of the ACE configuration - is the server.conf.yaml syntactically correct? Are there any errors reported by the integration server when it starts? Note that the server.conf.yaml settings should be made before starting up the server. Finally, when configuring the event settings in the message flow, did you definitely associate the events with the correct terminals on the nodes? Hopefully the above comments might give you a few things to check next - let us know how you get on!

I followed everything mentioned in the below blog but couldn't see any messages in the event queue.. any suggestions for making this work. I need help as soon as possible.

https://community.ibm.com/community/user/integration/blogs/amar-shah1/2023/05/12/configuring-ibm-app-connect-enterprise-for-publish 

Thanks in advance.