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.
|