I have several machines that I could put the remote agent on
and setup a master server.
But I want to be able to also have 24x7 on programmers servers so they can
a) monitor the master server job logs
b) to be able to execute jobs on request on the remote machines similar to the master server

can I do this, and if so, do I have to set up a separate remote agent on the remote machines,
and have a parallel system, or is there some other way of doing it

You can use different setups. Three most common setups are described below:

1. You run 1 master scheduler (24x7 running with the server option enabled on the "central" server) and you run 24x7 Remote Agents on other computers. On the master scheduler you configure agent profile for each agent, schedule jobs and assign different jobs to different agents.
To monitor/modify/run jobs all your developers would connect to the same central master scheduler using 24x7 Remote Control.

Let's call this one-to-many schema.

The big advantage of this method, all jobs, logs, settings are concentrated in one place, while jobs can run in many places.

2. You setup multiple schedulers running on different computers with the server option enabled. They can run completely independent or they can "talk" to each other and run both local and remote jobs.
To monitor/modify/run jobs on each server your developers would connect to different servers.

Let's call it many-to-many schema.

The big advantage of this method is that each server is independent. No matter what happens to other servers or to the network it can continue running jobs.

3. You setup multiple schedulers and multiple agents that are shared by these schedulers.

Now, in order to work with schedulers and jobs remotely each developer would need 24x7 software installed on the workstation. Each 24x7 computer installation regardless of how it is used requires a separate installation license. If you simply want to monitor jobs and respond to abnormal situations you can avoid installing 24x7 on developers workstations by enabling HTML status reports option on the central server. This and related options can be used to make 24x7 write real-time HTML files to some place on the network where they can be accessed directly or through a web server (see example here http://www.ccpo.odu.edu/~chris/24x7/index.htm)

Another option is to use central 24x7 Web-based Management Console on your departmental web server. This way you don't need to install 24x7 on developers computers, but the console itself requires a site license which could be more expensive then the other option. For details please see docs at http://www.softtreetech.com/24x7/documents.htm

: I have several machines that I could put the remote agent on
: and setup a master server.
: But I want to be able to also have 24x7 on programmers servers so they can
: a) monitor the master server job logs
: b) to be able to execute jobs on request on the remote machines similar to
: the master server

: can I do this, and if so, do I have to set up a separate remote agent on the
: remote machines,
: and have a parallel system, or is there some other way of doing it

thanks, I managed to test option 1, and this works correctly
I think this is the better option as it has only one db
although I would like some developers to have their own macros not accessable
to the master server, could I have them have a option to go to option 2?

: You can use different setups. Three most common setups are described below:
: 1. You run 1 master scheduler (24x7 running with the server option enabled
: on the "central" server) and you run 24x7 Remote Agents on other
: computers. On the master scheduler you configure agent profile for each
: agent, schedule jobs and assign different jobs to different agents.
: To monitor/modify/run jobs all your developers would connect to the same
: central master scheduler using 24x7 Remote Control.

: Let's call this one-to-many schema.

: The big advantage of this method, all jobs, logs, settings are concentrated
: in one place, while jobs can run in many places.

: 2. You setup multiple schedulers running on different computers with the
: server option enabled. They can run completely independent or they can
: "talk" to each other and run both local and remote jobs.
: To monitor/modify/run jobs on each server your developers would connect to
: different servers.

: Let's call it many-to-many schema.

: The big advantage of this method is that each server is independent. No
: matter what happens to other servers or to the network it can continue
: running jobs.

: 3. You setup multiple schedulers and multiple agents that are shared by these
: schedulers.

: Now, in order to work with schedulers and jobs remotely each developer would
: need 24x7 software installed on the workstation. Each 24x7 computer
: installation regardless of how it is used requires a separate installation
: license. If you simply want to monitor jobs and respond to abnormal
: situations you can avoid installing 24x7 on developers workstations by
: enabling HTML status reports option on the central server. This and
: related options can be used to make 24x7 write real-time HTML files to
: some place on the network where they can be accessed directly or through a
: web server (see example here
: http://www.ccpo.odu.edu/~chris/24x7/index.htm )

: Another option is to use central 24x7 Web-based Management Console on your
: departmental web server. This way you don't need to install 24x7 on
: developers computers, but the console itself requires a site license which
: could be more expensive then the other option. For details please see docs
: at http://www.softtreetech.com/24x7/documents.htm

Sure. They can run local copies of the scheduler with local db and whenever needed submit locally created jobs for execution on a remote agent or remote scheduler. They can pick where to send the job before they run it.

Also, for non-local "shared" schedulers they can use password protection to prevent other people from accessing and/or running their "personal" jobs for whatever reason. Job definitions and scripts are compressed and encrypted and nobody can see or change them inside or outside of the system, except peope who know the right password. Different jobs can have different passwords.

: thanks, I managed to test option 1, and this works correctly
: I think this is the better option as it has only one db
: although I would like some developers to have their own macros not accessable
: to the master server, could I have them have a option to go to option 2?

Hi,

Does this mean that If I've purchaset the 24x7 Automation Suite that I have to pay extra to use the Web Console ?

Jim

: thanks, I managed to test option 1, and this works correctly
: I think this is the better option as it has only one db
: although I would like some developers to have their own macros not accessable
: to the master server, could I have them have a option to go to option 2?

If you have a site license then no. If you don't you will need to upgrade to the site license.

: Hi,

: Does this mean that If I've purchaset the 24x7 Automation Suite that I have
: to pay extra to use the Web Console ?

: Jim

Good,

We're running under a site license - next question how do I access the web console ? Is it installed by default or is a seperate task required ?

Thanks,

Jim

: If you have a site license then no. If you don't you will need to upgrade to
: the site license.

The console is not installed by default. Contact support to obtain the most recent version. Please indicate whether you would like to run ASP version or JSP version. ASP version is for MS Internet Information Server and compatible servers capable to run Active Server Pages (ASP). JSP is for Apache, and other servers capable to run Java Server Pages (JSP), The last one requires that JDK/or JRE version 1.4.1 or better is installed on the webserver.

: Good,

: We're running under a site license - next question how do I access the web
: console ? Is it installed by default or is a seperate task required ?

: Thanks,

: Jim