easyTravel can be set up to execute procedures remotely. This is done by having a non-GUI Launcher application executing on all participating machines, which creates a Master-Slave-Launcher setup. Communication then takes place via REST solely from the Master Launcher to the Slave Launchers.
This is used for two use cases:
Overall the system will consist of multiple machines, each running a Master or a Slave node of easyTravel. There should be exactly one Master-node and a number of slave nodes.
ℹ️ Only one instance of Slave/Master can run on one machine at one time as they use the same networking ports and thus would cause conflicts.
rem Specify where easyTravel WebLauncher is available cd weblauncher rem Set the hostname/IP-Address of the machine where the rem master-launcher is executing, rem don't specify localhost here! set WEBLAUNCHER=stockhausen rem Set the hostname/IP-Address of the machine where the rem dynaTrace Server is running set DTSERVER=dynasprint rem Specify where each procedure should be started rem use localhost for running it locally set FRONTEND=dynasprint set BACKEND=localhost set DOTNETBACKEND=dynasprint set DOTNETFRONTEND=localhost
If it all starts up, you see the remote Hostnames/IP Addresses displayed for each of the remotely started procedures as follows: