{toc:outlinh1. true|printablefalse|stylh1. none|indent20px}
Mixed operation of SSH and JobScheduler Agents is possible.
The most important aspects that can be viewed as pre-or disadvantage, are shown in the following table:
{table}
{tr}
{td}Aspect{td}
{td}SSH{td}
{td}Agent{td}
{tr}
{tr}
{td}1) Execute jobs with different user ids{td}
{td}yes{td}
{td}no{td}
{tr}
{tr}
{td}2) Central Job configuration{td}
{td}yes{td}
{td}yes{td}
{tr}
{tr}
{td}3) Internal API Jobs available{td}
{td}no{td}
{td}yes{td}
{tr}
{tr}
{td}4) Real-time log{td}
{td}no{td}
{td}yes{td}
{tr}
{tr}
{td}5) Runs without installation{td}
{td}yes{td}
{td}no{td}
{tr}
{tr}
{td}6) Operating system independent{td}
{td}no{td}
{td}yes (only API-Jobs){td}
{tr}
{tr}
{td}7) no server-based licensing costs{td}
{td}yes{td}
{td}no{td}
{tr}
{table}
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 agent are assigned through the "process class" to one node (a JS 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 for 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 psexec (http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx) though without ssh. We know an installation in which a central JobScheduler controls 700 servers via psexec.
Look at http://www.sos-berlin.com/modules/cjaycontent/index.php?ih1. 222&pageosource_scheduler_howto_remote_en.htm for further information and jobs examples.
The documentation of the SSH Job is available here: http://www.sos-berlin.com/doc/jobdoc/SOSSSHJob2JSAdapter.xml
Overview
Content Tools