Scope
- Users of existing JobScheduler releases
- for Windows and Linux are not affected concerning their scheduling architecture.
- for AIX, Solaris, HP-UX should consider the following information for migrating to the new scheduling architecture.
Platform Support up to Release 1.9
Windows and Linux are supported platforms, while other Unix systems are platforms with limited support.
- Supported Platforms:
- Windows and Linux
- Explanation: Supported platform means that SOS compiles tests and ships the product for supported platforms. Set-up is available. Build support, installation support and product maintenance are provided for customers with commercial licenses.
- Platforms with limited Support:
- Solaris SPARC, AIX, HP-UX etc.
- Explanation: Limited Support means that users may build binaries from source code as there is no set-up available. Build support, installation support and product maintenance are provided for customers with commercial licenses.
- For more details please see this FAQ:
Platform Support starting from Release 1.10
The JobScheduler Universal Agent is platform-independent. This constitutes a major improvement to the role and functionalities of the JobScheduler Agents for Unix systems. The previous distinction between supported platforms and platforms with limited support will become obsolete.
- Supported Platforms
- Windows and Linux include the JobScheduler Passive Cluster, Active Cluster, Master / Agent Cluster and Supervisor.
- For Unix systems such as Solaris SPARC, AIX, HP-UX etc. the platform-independent JobScheduler Universal Agent is provided.
- Explanation: This means you will have to run your JobScheduler Master on either Windows or Linux, and then use any number of JobScheduler Universal Agents for other Unix platforms.
- Platform Support
- Support is available for all platforms, SOS provides binaries for all platforms.
- Explanation: The distinction between supported platforms and platforms with limited support is now obsolete. SOS compiles, tests and ships the product for supported platforms. Set-up is available. Build support, installation support and product maintenance are provided for customers with commercial licenses.
Strategy for Deployment
Deployment for JobScheduler in environments that include different operating systems such as Windows, Linux and other Unix systems can be applied in two steps.
- Step 1: Before migration to the JobScheduler Universal Agent:
- Update JobScheduler Master to a recent release for Linux/Windows
- Run JobScheduler Classic Agent for Unix (older release 1.3.x for AIX, Solaris, HP-UX)
- Explanation: this will allow you to use the current JobScheduler features, while the Agent of an earlier release is used until in Step 2 the new Universal Agent is used.
- See Master / Agent Compatibility
- Step 2: After migration of the JobScheduler Universal Agent:
- The JobScheduler Classic Agent (older release) used in Step 1 is replaced by the JobScheduler Universal Agent.
- For the migration to the JobScheduler Universal Agent no additional license fees will apply.
SOS provides Migration Services for commercial license holders.