Managing remote scheduler(s)

We developed the commandline module on a Windows system and tested it by controlling scheduler engines running on MacOSX, Linux and Solaris.  You can manage remote scheduler(s) either by:
1.  Using only the CLM
2.  Using the CLM in combination with the user interface & Ftp

Managing Remote Systems using the CLM in combination with Local User Interface & Ftp
The easiest way to setup or view data on a remote system is via the user interface itself on your local system.  To prevent confusion, it helps to understand and organize the data well on your local system to prevent confusion between the programs data on your local system and the remote system.

1.  The main install directory contains an 'data' folder
2.  All the data files are in this 'data' folder.  The user interface saves all your updates to data files in this folder.
3.  Create new folders in the folder called  'data_remote1' , 'data_remote2', 'data_remote3' etc..  for each remote system that you will control.  In our case, we used 'data_mac', data_solaris', and data_linux'.
4.  Create a new folder in the main install folder called 'data_localhost' for your local system, if you also run tasks on your local system.
5.  If the scheduler is also running tasks on your local system, shut down the scheduler & shut down the user interface.  Then Backup (copy) all the data from the 'data' folder to 'data_localhost'
6.  If you wish to view data from 'remote2', you can either copy the data from 'data_remote2' to the 'data' folder or by ftp directly FROM the 'data' folder on the 'remote2' system.
7.  Launch the user interface to create the tasks and schedules for 'remote2'
8.  After you have modified the data for 'remote2', you can backup the 'data' folder to 'data_remote2' and ftp directly TO the 'data' folder on the remote system.
9.  Then use the CLM module to STOP and then START the engine on 'remote2'.  This will force the engine to load the new data.
10.  If the scheduler is also running tasks on your local system, you can restore your local systems program data from 'data_localhost' to 'data'.