Removing or disabling a post event handlerAdded by IBM on March 25, 2013 | Version 1 (Original, Show current)
|This section describes the process to remove (or disable) an event handler, previously added in events-config.xml. Note that removing pre-configured events handlers shipped with IBM Connections is not supported - only third party event handlers can be removed.
Removing (or disabling) a post event handler
This section describes the process to remove (or disable) an event handler, previously added in events-config.xml. Note that removing pre-configured events handlers shipped with IBM Connections is not supported and may break Connections capabilities- only third party event handlers should be removed.
The process to remove an event handler is in three steps:
1. Open events-config.xml and locate the event handler you wish to remove. Take a note of the eventName, source and type attributes of all "subscription" nodes located under the "subscriptions" node under the "postHandler" node in events-config.xml
2. Remove the durable subscriptions at WebSphere
® Application Server Service Integration Bus level corresponding to the subscription noted in step 1.
a. Log in the to the WebSphere Application Server Integrated Solutions Console.
b. Expand Service integration -> Buses.
c. Click "ConnectionsBus" and then click "Destinations" (right-end side) under "Destination resources."
d. In the table of "Destinations" page, click the link "connections.events" ("Identifier" column). You may have to navigate to the second page to locate the "connections.events" destination.
e. Click "Publication points" on the right-end side.
f. Click the link named "connections.events@" where "<clusterName>" is the name of the cluster hosting the IBM Connections News application.
g. Select the "Runtime" tab and then click "Subscriptions"
h. Select (check boxes) ALL the subscriptions whose name is in the form "external##-
3. Update the file events-config.xml to remove the event handler. You can remove the entire "postHandler" node or simply set the attribute "enabled" to false. Please refer to step 8 in Deploying an event handler
to check out and in the events-config.xml file prior and after editing the file.