Menu

User guide

aeternaict

1. Quick installation (windows os)

ScriptScheduler use tcp protocol and ScriptScheduler.cfg time file programmation to execute local or remote batch/script. It reads ScriptScheduler.cfg file and programs the execution of all script active.
Performed the last script, it does auto-exit from system processes.

Follow these steps:

  1. Download zip file
  2. Extract two folders: ScriptScheduler (is application server folder) and ScriptSchedulerClient
  3. Copy ScriptSchedulerClient folder on a PC connected network

1.1 Client/Server quick configuration (windows os)

1.1.1 ScriptScheduler Configuration (server)

On your server, follow these steps:
1.. Create shortcut of ScriptScheduler.jar and in the destination property set follow parameter:
"yourpathdir\ScriptScheduler\ScriptScheduler.jar" /10 /8888
where

/10 = max number executable script
/8888 = TCP port

2.. Edit ScriptScheduler.cfg (time programmation) according to your needs, for example:
192.168.0.128;Test1.bat;00:00:10
192.168.0.128;Test2.bat;00:00:20
where

192.168.0.128 = remote PC Internet protocol on which runs ScriptSchedulerClient
Test1.bat = script's name (case sensitive): all script must be present in the same directoy in which is located ScriptSchedulerClient.jar
00:00:10 = execution time 10s after pressing "Run Script" button, format hh:mm:ss = it's execution time, after pressing "Run Script" button

3.. Run shortcut described above and eventually allow execution setting firewall

1.1.2 ScriptSchedulerClient Configuration

On your PC client:
1.. Create shortcut of ScriptSchedulerClient.jar and in the destination property set follow parameter:
"yourpathdir\ScriptSchedulerClient\ScriptSchedulerClient.jar" /8888
where

/8888 = client TCP port

2.. Run shortcut described above and eventually allow execution setting firewall
3.. On your server press "Run Script" button

2. Quick installation (linux os)

Follow these steps:

  1. Download zip file
  2. Extract two folders: ScriptScheduler (is application server folder) and ScriptSchedulerClient
    Extract ScriptScheduler on your linux desktop
  3. Copy ScriptSchedulerClient folder on a PC connected network, for example on your linux desktop

2.1 Client/Server quick configuration (linux os)

2.1.1 ScriptScheduler Configuration (server)

On your server, follow these steps:
1.. Create a script launcher "ScriptScheduler.sh" with text editor and write follow command:
cd /home/youraccountname/desktop/ScriptScheduler
java -jar ScriptScheduler.jar /10 /8888
where

/10 = max number executable script
/8888 = TCP port

2.. Save script launcher and enable "allow executing file as program" in its property

2.. Edit ScriptScheduler.cfg (time programmation) according to your needs, for example:
192.168.0.128;Test1.sh;00:00:10
192.168.0.128;Test2.sh;00:00:20
where

192.168.0.128 = remote PC Internet protocol on which runs ScriptSchedulerClient
Test1.sh = script's name (case sensitive): all script must be present in the same directoy in which is located ScriptSchedulerClient.jar
00:00:10 = execution time 10s after pressing "Run Script" button, format hh:mm:ss = it's execution time, after pressing "Run Script" button

3.. Run script launcher described above and eventually allow execution setting firewall

2.1.2 ScriptSchedulerClient Configuration

On your PC client:
1.. Create a script launcher "ScriptSchedulerClient.sh" with text editor and writes follow command:
cd /home/youraccountname/desktop/ScriptSchedulerClient
java -jar ScriptSchedulerClient.jar /8888
where

/8888 = client TCP port

2.. Save script launcher and enable "allow executing file as program" in its property

3.. Run script launcher above and eventually allow execution setting firewall
4.. On your server press "Run Script" button

2. Mixed installations (linux/windows - windows/linux os)

For mixed os installations follow above instructions, according to your operative system.
Windows ScriptScheduler server can run script on linux and vice versa

3. Direct ScriptScheduler execution

ScriptScheduler can be set to run immediately batches/scripts.

3.1 Direct ScriptScheduler execution (windows os)

Create shortcut of ScriptScheduler.jar and in the destination property set follow parameter:
"yourpathdir\ScriptScheduler\ScriptScheduler.jar" /10 /8888 /RUN_NOW

In this mode, ScriptScheduler executes instantly scripts according to your ScriptScheduler.cfg time programmation.

3.2 Direct ScriptScheduler execution (linux os)

Create a script launcher "ScriptScheduler.sh" with text editor and write follow command:
cd /home/youraccountname/desktop/ScriptScheduler
java -jar ScriptScheduler.jar /10 /8888 /RUN_NOW

In this mode, ScriptScheduler executes instantly scripts according to your ScriptScheduler.cfg time programmation.

4. ScriptScheduler.cfg time programmation file

With ScriptScheduler.cfg you can perform some operations as close remote ScriptSchedulerClient on PC and execute local script on the server.

4.1 Configuring ScriptScheduler.cfg to close remote ScriptSchedulerClient

1.. On the server, open criptScheduler.cfg and add this command
192.168.0.128;CLOSE_REMOTE_CLIENT;00:00:20
where

192.168.0.128 = remote PC Internet protocol on which runs ScriptSchedulerClient
CLOSE_REMOTE_CLIENT = command (case sensitive) to close ScriptSchedulerClient on remote PC
00:00:20 = when the command is executed, in this case 20s after press "Run Script" button

4.2 Configuring ScriptScheduler.cfg to execute local script

1.. On the server, open criptScheduler.cfg and add this command
localhost;Test2.bat;00:00:30
where
localhost = PC on which runs ScriptScheduler
Test2.bat = script's name (case sensitive): all script must be present in the same directoy in which is located ScriptSchedulerClient.jar
00:00:30 = when the command is executed, in this case 30s after press "Run Script" button


MongoDB Logo MongoDB