Solution 1.
Create a JAL script job that dynamically transfers and executes your batch file
For example,
computer A runs 24x7 Scheduler
computer B runs 24x7 Remote Agent
On A setup a remote agent profile (Tools/Remote Agents menu). Let's say the profile name is "AgentB"
On A schedule a local job Job1 of program type with [no schedule] for the schedule and the following command line c:\temp\my_batch.bat
On A schedule a local job Job2 (any schedule) of JAL script type with the following script //////////////////
FileTransferEx "ToRemote", "AgentB", "c:\\scripts\\my_batch.bat", "c:\\temp"
JobRemoteRun "Job1", "AgentB"
////////////////// Solution 2: (a much more simple way to do the same thing)
On A schedule a remote job of JAL or VBScript script type, Select AgentB as a host.
In the job script implement the logic of your current batch file. Note that in the second solution, no batch file is needed and everything is deployed automatically. Also just 1 job is required for the same processing. : Hi, : I am new to this. I am trying out 24x7 Scheduler
: and I want to do the following: I want to run a windows command script
: that is stored locally on the server machine
: on a remote machine. : How do I do this? Currently I have to
: first place the script on the remote
: machine and then run the job. : Thanks
: Sotiris
|
