App Connect

 View Only

 ACE 11 - what are the topic and subscription strings for monitoring events for a standalone Integration Server?

John Ormerod's profile image
John Ormerod posted Fri September 26, 2025 11:08 AM

I have successfully worked with pub/sub for monitoring events when used with an Integration Node. But, for a standalone server, I have driven myself crazy.

I find the IBM manual ambiguous, by only providing generic values and no examples (might save me asking this).
I have read this related post https://community.ibm.com/community/user/discussion/topic-string-for-event-monitoring-using-an-independent-integration-server

Unfortunately, the questioner ends by saying that  he had the correct subscription string - but doesn't was what it was.


I have a standalone Int Server ('njamsDemoSA') defined using the Toolkit. I have modified its server.conf.yaml as follows:

Monitoring: 
  MessageFlow: 
    eventFormat: 'MonitoringEventV2'
    publicationOn: 'active'    

When I look in the Toolkit and browser admin, monitoring is shown as active and monitoring profile is shown as part of the related policy/.

I have defined a number of subscription strings - none of which work.

$SYS/Broker/njamsDemoSA/Monitoring /#
$SYS/Broker/njamsDemoSA/Monitoring /+/+/+
$SYS/Broker/integration_server/Monitoring/+/+/+
$SYS/Broker/integration_server/Monitoring/#
$SYS/Broker/#/Monitoring/#

This last one, is so general that, as I anticipated, it gets monitoring events from an Int Server owned by an Int Node and writes then to my queue for standalone events.

I have defined and applied a monitoring profile to my test message flow. Also,removed that and explicitly defined Txn Start and Txn End events in the msg flow and deployed it.

I can't get any monitoring events to be published.

I hope someone can help,

John

Peter Von Hirschfeld's profile image
Peter Von Hirschfeld posted Mon September 29, 2025 02:13 AM

Hi John

I should have provided a more complete answer when I posted in 

https://community.ibm.com/community/user/discussion/topic-string-for-event-monitoring-using-an-independent-integration-server

Here's the string I used for an independent IS:

$SYS/Broker/integration_server/Monitoring/<IS name>/<application name>/#

Peter

John Ormerod's profile image
John Ormerod posted Mon September 29, 2025 05:24 AM

Hi Peter

Thanks very much for your speedy response. I have created a Sub for the string, and still not getting any events.
At least, I now know what my target Sub string should be. 

I see you did some MQ tracing, which as a Java developer, I have never done. I got some clues from Chat and Grok - but I have often found their answers to be wrong! I will find out.

All the best, John

John Ormerod's profile image
John Ormerod posted Mon September 29, 2025 10:57 AM

I can't see a way to add another post to my last one, so I have answered my original question.

The main reason I wasn't getting any monitoring events for the  standalone Int server, was  because I based my server.conf.yaml override on the values I had in one for a server under a node.
This meant that I missed the important step of enabling Events: > BusinessEvents:!!

When I corrected this, I was getting multiple events for my various subscriptions.

In case it helps, this is my server.conf.yaml in the overrides folder:

(spaces, no tabs for the yaml)
-------

defaultQueueManager: 'ACE11MGR'    # Set non-empty string to specify a default queue manager
RestAdminListener:
   port: 7602
ResourceManagers:
  HTTPConnector:
    ListenerPort: 7802              # Set non-zero to set a specific port, defaults to 7800
  HTTPSConnector:
    ListenerPort: 7845              # Set non-zero to set a specific port, defaults to 7843
  JVM:
    jvmDebugPort: 6512
Events:
  BusinessEvents: # Business monitoring events
    MQ:
      enabled: true           # Set true or false, default false
    MQTT:
      enabled: true             # Set true or false, default false
Monitoring:
  MessageFlow:
    publicationOn: 'active'          # choose 1 of : active|inactive, default inactive
                                     # Ensure Events.BusinessEvents.MQ|MQTT is set
    eventFormat: 'MonitoringEventV2' # choose 1 of : MonitoringEventV2|WMB

------

John

Related Content