JAMS has the ability to execute Linux and UNIX scripts through the JAMSAgentX or agent-less through pure SSH connections. There are four basic advantages to using the JAMS AgentX.
- The job can contain a script rather than a series of commands. (i.e. , if statements, while loops, etc). The SSH execution method isn't able to run a job as though it were a script; it runs it line by line as if a user were typing it into the command line. JAMSAgentX runs jobs as a shell script; running it as a script makes it act the way most people expect it to. That’s the main purpose of JAMSAgentX.
- File based Trigger mechanisms require the JAMSAgentX.
- Better exception capturing of the job processes are provided by JAMSAgentX.
- Automatic re-connections are supported through JAMSAgentX. With SSH, if something fails and in turn causes the JAMS server to disconnect the job will be reported as failing. With JAMSAgentX, the job continues and JAMS reconnects as if nothing ever happened.
Is it possible to run also from a windows server ?
Hello Giovanni, the SSH connection must be made from the Scheduler server.
Is SSH connection the only agent-less method to run a job?
@Doreen - It is the only way to run an agentless Linux job, yes. There are other execution methods that do not require an agent. If you have further questions about this please submit a ticket and we can help answer any questions you have.