Yes, the web interface is available but it requires a site license.
Here is the link to web-based interface manual
http://www.softtreetech.com/24x7/24x7web_gui.pdf Your statement about asynchronous / synchronous mode isn't correct. 24x7 keeps tracks of async. jobs and knows their completion status. The only exception is program type async. jobs which kick off external processes and let them go. As opposite to that, sync. program type jobs monitor started processes and capture their exit code. Database and script type jobs always know they completion state regardless of how they run. If you need to run an external process async. And still capture the exit code use JAL or VBScript. Several templates are available for that. For more info see RunAndWait topic and examples in the on-line help To run multiple jobs synchronously and simultaneously use multiple job queues (using multiple queues is like using multiple independent scheduling systems running at the same time on the same machine) yet, these jobs can be linked and managed together.
As for multiple agents/queues you don't have to assign jobs to a specific host. Just assign different jobs to different queues and use [Least busy] for the host property. Again, if needed, you can always setup jobs to run asynchronous (e.g. in the background). : Thanks for you help so far. I am continuing to work on the test environment,
: but I have a set of specific questions that I need answered for my
: manager. : 1. Is there a web interface that is separate for the menu-driven interface?
: I'm looking specifically for separate views that would show what reports
: have completed, what errors are outstanding (some sort of error log), and
: a control panel where specific processes can be fired off. Do these
: interfaces exist separately (so that not all of them are public) on a
: webpage? : 2. Multiple jobs - I know I've already asked this question, but I'm still not
: clear. It sounds like with the asynchronous option the scheduler isn't
: able to track the status of the job once it's begun and also that it is an
: "expensive" operation to run. Given that, it sounds like
: synchronous would be the better option. The main drawback that I can see
: with synchronous mode is that it is not able to run more than one process
: at a time on one remote agent. In the answer you had given me previously,
: you recommended a job queue for each PC that we would be running jobs on.
: This wouldn't work for what we are hoping to accomplish. We are looking
: for a way to avoid assigning a job to a specific host. Am I perhaps not
: understanding your reply? : 3. Is it possible to offset a group of jobs? For exampple, if I have 3 jobs
: scheduled for 9:00 AM, 10:00 AM, 11:00 AM, is it possible to quickly and
: easily offset them all by an hour?
|
