Robotic Automation example: Shutting down emulator processes
For best results, all Pega Robotic Automation solutions that include a text adapter should also include logic that makes sure that no emulators are running before you start the robotic automation.
Some emulators do not shut down entirely and instead leave processes running. If processes are still running and your automation starts, the automation could connect to the wrong process and not work as designed.
To avoid this issue, add logic to the beginning of your automation to search for and shut down any running emulators. The following example solution provides an example of a solution that shuts down any Rumba emulators, and then starts Pega Robot Runtime.
Example solution for shutting down Rumba processes