SoftTree Technologies SoftTree Technologies
Technical Support Forums
RegisterSearchFAQMemberlistUsergroupsLog in
Problem with Remote control for Windows

 
Reply to topic    SoftTree Technologies Forum Index » 24x7 Scheduler, Event Server, Automation Suite View previous topic
View next topic
Problem with Remote control for Windows
Author Message
Dean Logan Wood



Joined: 04 Aug 2005
Posts: 25

Post Problem with Remote control for Windows Reply with quote

I'm trying to connect to a Java Scheduler running on
Solaris using the Windows 24x7 Remote Control. I have
set-up a Remote Host and successfully tested the
connection. When I actually try to connect I get a
MicroSoft Error Report dialog shortly after entering
the username/password. Remote control exist after I
press the "Don't Send" button. I running Windows XP SP2

Fri Aug 05, 2005 11:00 am View user's profile Send private message
SysOp
Site Admin


Joined: 26 Nov 2006
Posts: 7975

Post Re: Problem with Remote control for Windows Reply with quote

You are again trying something unsupported.

Let me clarify the situation.

There are 2 sibling versions of 24x7 Scheduler: one is Windows version, another is Java version that looks and feels mostly like the Windows sibling. There are functional differences between these 2 versions (see last paragraph below)

Each version can run both local and remote jobs. Each version can run in the scheduler and in the agent mode, but …

The Windows version can use its own agents (scheduler in agent mode) as well as use other non-Windows agents that can run on a variety of platforms. These other agents are separate software pieces that are not related to the Java version of the scheduler. Some off these agents are created in Java, but again don't confuse them with 24x7 Scheduler Java edition. However script type jobs can in theory use the available API to communicate with the Java version and run remote jobs.

The Java version doesn't need other agents (other software) as it can run itself on a variety of platforms. It can also reuse 24x7 Scheduler for windows as agents (uses special mode)

All these types of agents are provided so that you can build any topology you want for running network jobs. The most common case if to have one central scheduler and use multiple agents. This way you can manage and audit jobs in just one central place. You can also link jobs running on different computers into 1 business process using job dependencies feature.

The Windows version does support 2 remote graphical management interfaces: 24x7 Remote Control and web-based interface.

The Java version supports web-based interface only. It cannot be managed using 24x7 Remote Control from the Windows sibling. On the other hand when run on Unix under X-Windows server it is possible to use remote GUI to manage it fro ma different terminal.

Web-based interface is available in 2 versions (ASP and JSP) – ASP version can run on Microsoft IIS web server (a.k.a.Windows) and only be used with 24x7 Scheduler Windows version, while the JSP can run on Apache and other web servers capable to run JSP and this version can be used with both 24x7 Windows and Java versions.

Main functional differences between schedulers (current versions)
1. Windows version can run built-in script type jobs including JAL script and VBScript. It supports the built-in Script Library and auto-deployment features.
Java version can run external scripts only (batch, shell, Perl, etc…) it runs them as program type jobs

2. Windows version comes with a number of native database interfaces for running database jobs
Java version by default supports ODBC interface only. For other interfaces you must obtain proper JDBC drives from the database vendor. You can then use them with the scheduler

3. Java version supports multiple business calendars
Windows version doesn't. Although you can use the built-in scripting to implement the required business logic.

4. Java version can potentially run on more platforms then agents available for Windows version (the current difference is z/OS and OS/390 mainframe support)

5. 24x7 Event Server better integrates with the Windows version.

6. Different methods are used with Windows and Java versions for scheduler failovers.

Just listing "same" features is going to take a lot of pages, please see the docs for details.

: I'm trying to connect to a Java Scheduler running on
: Solaris using the Windows 24x7 Remote Control. I have
: set-up a Remote Host and successfully tested the
: connection. When I actually try to connect I get a
: MicroSoft Error Report dialog shortly after entering
: the username/password. Remote control exist after I
: press the "Don't Send" button. I running Windows XP SP2

Fri Aug 05, 2005 11:43 am View user's profile Send private message
Dean Logan Wood



Joined: 04 Aug 2005
Posts: 25

Post Re: Problem with Remote control for Windows Reply with quote

Thanks for that. Now I understand the architecture a
little better, perhaps you can suggest the best configuration
for our environment? We'd like to get access to the
script functionality, but we only use Solaris in our
Production environment, so it sounds like running the
Java Edition is not appropriate. We could run the
Windows version - we have a number of Windows 2000 servers
which could used for this. From what you say we would
then need to run the related Solaris agent on each
managed server.

Is there any other option that would still enable us to use
scripting and run remote jobs on Solaris?

Are these non-Windows agents available for download?

: You are again trying something unsupported.

: Let me clarify the situation.

: There are 2 sibling versions of 24x7 Scheduler: one is Windows version,
: another is Java version that looks and feels mostly like the Windows
: sibling. There are functional differences between these 2 versions (see
: last paragraph below)

: Each version can run both local and remote jobs. Each version can run in the
: scheduler and in the agent mode, but …

: The Windows version can use its own agents (scheduler in agent mode) as well
: as use other non-Windows agents that can run on a variety of platforms.
: These other agents are separate software pieces that are not related to
: the Java version of the scheduler. Some off these agents are created in
: Java, but again don't confuse them with 24x7 Scheduler Java edition.
: However script type jobs can in theory use the available API to
: communicate with the Java version and run remote jobs.

: The Java version doesn't need other agents (other software) as it can run
: itself on a variety of platforms. It can also reuse 24x7 Scheduler for
: windows as agents (uses special mode)

: All these types of agents are provided so that you can build any topology you
: want for running network jobs. The most common case if to have one central
: scheduler and use multiple agents. This way you can manage and audit jobs
: in just one central place. You can also link jobs running on different
: computers into 1 business process using job dependencies feature.

: The Windows version does support 2 remote graphical management interfaces:
: 24x7 Remote Control and web-based interface.

: The Java version supports web-based interface only. It cannot be managed
: using 24x7 Remote Control from the Windows sibling. On the other hand when
: run on Unix under X-Windows server it is possible to use remote GUI to
: manage it fro ma different terminal.

: Web-based interface is available in 2 versions (ASP and JSP) – ASP version
: can run on Microsoft IIS web server (a.k.a.Windows) and only be used with
: 24x7 Scheduler Windows version, while the JSP can run on Apache and other
: web servers capable to run JSP and this version can be used with both 24x7
: Windows and Java versions.

: Main functional differences between schedulers (current versions)
: 1. Windows version can run built-in script type jobs including JAL script and
: VBScript. It supports the built-in Script Library and auto-deployment
: features.
: Java version can run external scripts only (batch, shell, Perl, etc…) it runs
: them as program type jobs

: 2. Windows version comes with a number of native database interfaces for
: running database jobs
: Java version by default supports ODBC interface only. For other interfaces
: you must obtain proper JDBC drives from the database vendor. You can then
: use them with the scheduler

: 3. Java version supports multiple business calendars
: Windows version doesn't. Although you can use the built-in scripting to
: implement the required business logic.

: 4. Java version can potentially run on more platforms then agents available
: for Windows version (the current difference is z/OS and OS/390 mainframe
: support)

: 5. 24x7 Event Server better integrates with the Windows version.

: 6. Different methods are used with Windows and Java versions for scheduler
: failovers.

: Just listing "same" features is going to take a lot of pages,
: please see the docs for details.

Fri Aug 05, 2005 12:05 pm View user's profile Send private message
SysOp
Site Admin


Joined: 26 Nov 2006
Posts: 7975

Post Re: Problem with Remote control for Windows Reply with quote

Sure, this message board is a best place for such questions.

In order to answer your "best configuration" question you would need to know the following estimates:
1. Total number of jobs you are going to run
2. How many jobs will run on the Windows and Solaris sides?
3. What kind of jobs are you going to run? If you know that which particular scripting functions you are going to use that are not readily available "outside" of the scheduler?
4. What topology would you like to have (1 central scheduler, multiple independent schedulers, multiple scheduler somewhat dependent on each other)?
5. Are you going to run interactive and on-demand jobs or just automated processes?
6. Who will be primary users of the system? developers and system admins or other users?

Here is the requested link to the site where you can find downloads for remote agents (look for Remote Automation Servers for Linux and Unix, this is what you want).
http://www.24x7automation.com

Again there are 2 flavors of agents are available for Solaris - native code version (e.g TCP daemon) and Java version (runs as a server).

: Thanks for that. Now I understand the architecture a
: little better, perhaps you can suggest the best configuration
: for our environment? We'd like to get access to the
: script functionality, but we only use Solaris in our
: Production environment, so it sounds like running the
: Java Edition is not appropriate. We could run the
: Windows version - we have a number of Windows 2000 servers
: which could used for this. From what you say we would
: then need to run the related Solaris agent on each
: managed server.

: Is there any other option that would still enable us to use
: scripting and run remote jobs on Solaris?

: Are these non-Windows agents available for download?

Fri Aug 05, 2005 12:24 pm View user's profile Send private message
Dean Logan Wood



Joined: 04 Aug 2005
Posts: 25

Post Re: Problem with Remote control for Windows Reply with quote

1. We'll have something like 200 jobs every day
2. Initially all on Solaris. We may use it for
Windows at some stage in the future, though this
will essentially be to support administrative and
development activities
3. We'd certainly make use of FTP capabilities, though
I think we would need advice as to whether things like
this are just as easy to do with Unix shell scripts etc
4. I think we would want a single primary scheduler with
if possible a standby scheduler for failover
5. Both, thugh primarily automated processes
6. Developer and Sys Admins, though Sys Admins really for
for monitoring and problem correction

One definite requirement we have is for integration with
HP OpenView Operations, as this is the primary console
used by Sys Admins/Operations.

: Sure, this message board is a best place for such questions.
: In order to answer your "best configuration" question you would
: need to know the following estimates: 1. Total number of jobs you are
: going to run
: 2. How many jobs will run on the Windows and Solaris sides?
: 3. What kind of jobs are you going to run? If you know that which particular
: scripting functions you are going to use that are not readily available
: "outside" of the scheduler?
: 4. What topology would you like to have (1 central scheduler, multiple
: independent schedulers, multiple scheduler somewhat dependent on each
: other)?
: 5. Are you going to run interactive and on-demand jobs or just automated
: processes?
: 6. Who will be primary users of the system? developers and system admins or
: other users?

: Here is the requested link to the site where you can find downloads for
: remote agents (look for Remote Automation Servers for Linux and Unix, this
: is what you want).
: http://www.24x7automation.com

: Again there are 2 flavors of agents are available for Solaris - native code
: version (e.g TCP daemon) and Java version (runs as a server).

Fri Aug 05, 2005 1:26 pm View user's profile Send private message
SysOp
Site Admin


Joined: 26 Nov 2006
Posts: 7975

Post Re: Problem with Remote control for Windows Reply with quote

It sounds like the best solution for this task is to use the 24x7 Scheduler Java because most of your jobs are Unix based.

You could have 24x7 running as Master Scheduler on one server where you got most jobs and using other 24x7 running in agent modes to run jobs on other Unix machines and possibly run jobs on Windows.

In the options on the Master you could enable real-time HTML status reports and choose a directory on your web server (or simply run local Apache or Sun's web server) where you want 24x7 to land these reports. This way your users and sys admins can monitor all jobs across all servers in one place and all they would need is just a web browser.

I would also recommend installing the web-based interface (Warning: you must get a site license to use this feature) so that jobs can be managed and monitoring also from anywhere.

Regarding the scripting. A newest version of the Java scheduler planned for release later this error will support JavaScript with extensions so certain scripting options will be available to you.. By the way scripting FTP in Unix is an easy task. You can find tons of examples on the Internet.

My recommendation: unless you really need JAL or VBScript which are available in the Windows version only, or need to automate Windows processes that require sending keystrokes or mouse clicks, you are better off with a 24x7 Scheduler Java. That's probably also the simplest solution.

As for the fail-save, you will need a spare standby server connected to the primary by a serial cable to implement the fail over feature.

: 1. We'll have something like 200 jobs every day
: 2. Initially all on Solaris. We may use it for
: Windows at some stage in the future, though this
: will essentially be to support administrative and
: development activities
: 3. We'd certainly make use of FTP capabilities, though
: I think we would need advice as to whether things like
: this are just as easy to do with Unix shell scripts etc
: 4. I think we would want a single primary scheduler with
: if possible a standby scheduler for failover
: 5. Both, thugh primarily automated processes
: 6. Developer and Sys Admins, though Sys Admins really for
: for monitoring and problem correction

: One definite requirement we have is for integration with
: HP OpenView Operations, as this is the primary console
: used by Sys Admins/Operations.

Fri Aug 05, 2005 2:12 pm View user's profile Send private message
Display posts from previous:    
Reply to topic    SoftTree Technologies Forum Index » 24x7 Scheduler, Event Server, Automation Suite All times are GMT - 4 Hours
Page 1 of 1

 
Jump to: 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


 

 

Powered by phpBB © 2001, 2005 phpBB Group
Design by Freestyle XL / Flowers Online.