Comparison of SSH and JobScheduler Agent usage
Mixed operation of SSH and JobScheduler Agents is possible.
The most important aspects that can be viewed as advantages or disadvantages are shown in the following table:
| Aspect | SSH | JobScheduler Agent | |
|---|---|---|---|
| 1 | Execute jobs with different user IDs | yes | no |
| 2 | Central job configuration | yes | yes |
| 3 | Internal API jobs available | no | yes |
| 4 | Real time log | no | yes |
| 5 | Runs without installation | yes | no |
| 6 | Operating system independent | no | yes (only API jobs) |
It should be noted further that the addressing of the server on which the job should be run in both procedures is different. Jobs to be executed by an JobScheduler Agent are assigned through the "process class" to one node (a JobScheduler instance on a server), an authentication is not provided - the jobs run under the user ID and the privileges of the JobScheduler instance.
SSH jobs have parameters to define the server as well as the authentication.
SSH can be used under Windows with copSSH (http://www.itefix.no/i2/copssh), an openSSH implementation. An alternative would be PSexec (http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx) though without SSH. We have knowledge of an installation in which a central JobScheduler controls 700 servers via psexec.
See also
- See http://www.sos-berlin.com/modules/cjaycontent/index.php?id=222&page=osource_scheduler_howto_remote_en.htm for further information and jobs examples.
- The documentation of the SSH job is available at: http://www.sos-berlin.com/doc/jobdoc/SOSSSHJob2JSAdapter.xml .
- The documentation of the source code is at: SOSSSHJob2JSAdapter.