You can remove an on-premises Events Service from individual nodes or all at once. An embedded Events Service is uninstalled along with the Controller.

Uninstall the Events Service with the Enterprise Console

You can uninstall the Events Service through the GUI on the Events Service page.

To do so through the CLI, you can use the uninstall-events-service command, which removes the Events Service software and data from all cluster nodes:

bin/platform-admin.sh submit-job --job uninstall --service events-service --platform-name <name_of_the_platform>
bin\platform-admin.exe cli submit-job --job uninstall --service events-service --platform-name <name_of_the_platform>
After uninstalling Events Service, the only trace of the Events Service remaining on the host may be a file named orcha-modules.log. It appears in the logs directory at the former installation root directory. To remove all traces of the Events Service, manually remove the log file after removing the Events Service with the Enterprise Console.  

To uninstall the Events Service from a single node with the Enterprise Console, see the Removing a Node section on Administer the Events Service.

Uninstall the Events Service as a Windows Service

You can remove the Events Service as a Windows service after installation through the GUI. You can also use the following command to retain the Events Service on the machine.

To remove the Events Service as a Windows service: 

  1. Use the list service command to find the service name for the Events Service: bin\events-service.exe service-list

    Starting the ZooKeeper alone only brings up the process that manages index rollover. The Events Service node is not fully started until you start the API-Store process as well, as described next. 

  2. Use the name returned for the service as the -s parameter argument to the following command: bin\events-service.exe service-uninstall -s "<Name from service-list>"

    Be sure to enclose the name in double-quotes.