Something that would cure a lot headaches for me is the ability to create a task which triggers a job on a remote VisualCron server.

For example, if Server A has VisualCron installed with this job:

+ Job ABC
- Task X

then I'd like to be able to do something like this on Server B which also has VisualCron installed:

+ Job XYZ
- Task P - local SQL Task
- Task Q - local Execute Task
- Task R - trigger Task X from Job 1 on Server A
- Task S - local Execute Task

Task R would simply send a "start Task X" signal to Server A and it would run on Server A as if it had been started by a trigger there. Task R would wait for a response from Server A to say it had completed (or timed out).

At the moment I've only got VisualCron installed on Server B and I'm using a jumble of psexec, batch files and powershell scripts to recreate a poor-mans version of this behaviour. I know I could install VisualCron on Server A and set up task X on an independent schedule, but I need it to run in between Tasks Q and S on Server B (and also *not* run if task Q fails) so I have to use psexec like this.

Adding this feature would plug a hole that I fall into on practically every task I set up at the moment. I'd ditch psexec in a heartbeat and buy an additional VisualCron license for Server A (and servers C, D, E, etc) if it had this functionality.

In terms of security, you might need to configure an authorisation key or certificate or something to Server A which says "Server B is allowed to trigger jobs here" (either server-wide, or for specific jobs / tasks) to prevent unauthorised users triggering tasks on Server A from a rogue server.

Cheers,

Mike

Ok, I've been thinking about this a bit more. The most straightforward way implement it that I can think of is as follows:

+ Add a new type of trigger called "Remote Server Trigger" which takes the name(s) of remote VisualCron servers that are allowed to trigger the local job. You can then configure a trigger for Job ABC on Server A that listens for a signal from Server B.

+ Add a new type of task called "Send Remote Trigger" in which you specify the name of the remote server, job and task to run. You can then create Task R on Server B which sends a signal to Server A to launch Job XYZ.

The two servers would still need to be administered as separate VisualCron installations, but at least there would be a way of incorporating a task from Server A into the workflow of a job on Server B. This would be a massive win for me.

Cheers,

M

I love this idea. It would make my life easier ! 🤤

Please test this new version:

http://www.visualcron.co....aspx?g=posts&t=1834 

---