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, database change, etc.. Performing maintenance on this prevents confusion when sending data between applications and email alerts being sent due to false-negative connection checks ( discarded event notification )

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

   1) 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 ( via admin console ) :

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

   2) Remove the "old" remote event subscriptions

When we figure out what is wrong ( review the subscriber ID's from the query above to identify those with inappropriate host / port information ) we will execute the following server utility script :

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>

   3) 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.