Hi,

I am really confused now about how the 24x7 remote control
and debugger works.

Am I correct in thinking that if I connect to a remote 24x7
scheduler host using the 24x7 remote control and within the
remote control client I select a script and run the debugger option
then the script/job should be run on the remote server and not the
local system from which the fremote control client is running ?

Jim

The debugger is always local.

In essence, when you connect using remote control the following happens:
Remote control grabs snapshot of the job database and global settings on the server and downloads it locally. It also downloads remote logs. When you save changes it sends incremental changes (delta) to the server. The server ensures that multiple users don't override each other's changes by looking at job timestamps. When you select a job to run it prompts you where, if you select local it runs it locally, it you select remote it submits the job to the remote just as any scheduler or agent does when executing remote jobs. The debugger can only run local jobs because it runs them interactive, line-by-line.

PS. Remote debugging should be available in version 4.

: Hi,

: I am really confused now about how the 24x7 remote control
: and debugger works.

: Am I correct in thinking that if I connect to a remote 24x7
: scheduler host using the 24x7 remote control and within the
: remote control client I select a script and run the debugger option
: then the script/job should be run on the remote server and not the
: local system from which the fremote control client is running ?

: Jim

Hi again,

You have confirmed what I had managed to figure out by trial and error.

Most of the problems I have experienced with the 24x7 product so far
have been more to do with poorly/undocumented restrictions rather than bugs.

Do you have a scheduled/estimated release date (and feature list?) for V4 ?

Thanks,

Jim

: The debugger is always local.

: In essence, when you connect using remote control the following happens:
: Remote control grabs snapshot of the job database and global settings on
: the server and downloads it locally. It also downloads remote logs. When
: you save changes it sends incremental changes (delta) to the server. The
: server ensures that multiple users don't override each other's changes by
: looking at job timestamps. When you select a job to run it prompts you
: where, if you select local it runs it locally, it you select remote it
: submits the job to the remote just as any scheduler or agent does when
: executing remote jobs. The debugger can only run local jobs because it
: runs them interactive, line-by-line.

: PS. Remote debugging should be available in version 4.

There is no official release date. We are still working on the beta. It was previously expected that the new version would be ready by the end of first quarter 2005. However we have hit some unexpected delays with some third-party components, which are not yet ready. I don't know if that delay will affect the original schedule. Some parts have been released ahead of schedule, for example the Event Server which is already available with the site license and also available separately.

: Hi again,

: You have confirmed what I had managed to figure out by trial and error.

: Most of the problems I have experienced with the 24x7 product so far
: have been more to do with poorly/undocumented restrictions rather than bugs.

: Do you have a scheduled/estimated release date (and feature list?) for V4 ?

: Thanks,

: Jim