The boring part..... You can check files using their UNC names like
\\REMOTESERVER\REMOTESHARE\FOLDER\FILE This is the best method. If you cannot do that use FTPFileExists in a "checker" job running every x minutes. From that job you can trigger the main job using either
JobRemoteRun job_id
or
RunAndWait "24x7 /JOB job_id", "", 0, process commands I guess \\\\appServerName\\shareName\\folder\\filename didn't work because the remote share is not shared or you don't have permissions for that. Now...... Here is the best part. If instead of 24x7 Windows edition you run 24x7 RA Server Java edition (on the remote server) you can then check files, read and write them over the network as if they were local files. I mean the job will run on the local server while checking files, saving them and running processes on the remote.
For more details read "24x7 Linux & UNIX RA Server Reference" manual. Although the code is targeted mostly to Unix systems, it can be also run on Windows. : I am working on migrating from just running 24x7 locally to running it on a
: seperate scheduling server. I have jobs that check for the existence of other
: files on the Remote Agent's server. Is there some syntax I can use to check
: for
: those files using "Run this job: when certain files are found" or
: will I have
: to change my scripts to use the FTPFileExists command and set up FTP access
: to
: those folders? My team does not own the scheduling server and I do not think
: we will be allowed to create mapped drives on the scheduling server. : Also if I need to create files on the application server is there a simpler
: way
: of doing it than creating it locally on the scheduling server, FTPing it to
: the
: correct location on the application server and then deleting the local copy?
: I
: tried FileSave "\\\\appServerName\\shareName\\folder\\filename",
: "", but that did
: not work.
|
