Managing Remote Event Subscriptions

This article details how to remove "remote event subscriptions" that are no longer applicable. The need for this may arise due to a recent server migration or database migration. Performing maintenance on this prevents confusion when sending data between applications and email alerts being sent due to false-negative connection checks, known as discarded event notifications.

To clean up any old remote event subscriptions that may be lingering in the database, the following steps may be performed.

Viewing existing remote event subscriptions 

Determine what the "new" and "old" remote event subscriptions should look like. This may be identified easily by looking at the URL listing. To accomplish this, the following query may be executed against the product database.

select SUBSCRIBERID, EVENTTYPE from EVENTSUBSCRIPTION where APPDOMAIN = 'Remote';

To run this through Assure's SQL UI, access your SQL Console.

Your output will list the server names and ports of the Insight and Perceive servers that Assure will output to. This list will grow over time as more Insight and Perceive instances connect with an Assure instance. If an Insight or Perceive instance is decommissioned, commonly part of a parallel upgrade where the server names change, Assure will still have an event subscription record for the old Insight and Perceive servers. These will need to be manually removed.

Remove old remote event subscriptions

When you identify which subscriber ID's from the query above have an inappropriate host / port combination, the following server utility script can be used to remove specific records. 

remoteeventadmin.sh -delete -host <hostname> -port <portnumber>

Please note, the <hostname> / <portnumber> value will be the "old" URL host / port we are looking to remove ( "-port" argument is optional ). The "remoteeventadmin" shell and batch scripts may be found within the following directory :

<infogix_home>/server-util/<jvm>/<product>

Confirm successful removal of "old" remote event subscriptions

This may be confirmed by once again performing the query defined within the first step. Once executed, only the "new" remote event subscriptions should remain ( if processing has occurred ). Ensure event subscriptions are being created with the correct URL moving forward.