About Job Servers

A Job Server is a type of Object that lets RunMyJobs run Jobs, watch for File Events, and monitor system performance on a connected system. There are two types of Job Server:

  • Platform Job Servers: If the connected system is an operating system platform (for example, a Windows or Unix server), a piece of Redwood software called a Platform Agent must be installed on the server so that it can communicate with RunMyJobs. There is a 1:1 relationship between such Job Servers and their Platform Agents.

  • Standard Job Servers: If the connected system is something other than an operating system platform (for example, an SAP system or a database), no additional software needs to be installed: The Job Server can handle the job on its own.

For more information, see How Job Servers Work.

Platform Job Servers

Platform Job Servers are made up of two independent but interacting parts.

  • Part one is a process running on the RunMyJobs server. The Job Server process is usually started when the RunMyJobs is started, but can also be started with a Start command issued via an API or the GUI.
  • Part two is a Platform Agent running on a computer inside the customer network. The Platform Agent is usually started as part of the operating system boot sequence.
    • On Windows, a service controls the Platform Agent and automatically restarts it when it stops.
    • On UNIX, the native init system controls and restarts the Platform Agent, and the platform-agent script makes sure all necessary OS processes are running.

Both parts are started independently. Although either can run alone, the system works only when both parts are running and the Job Server has established a TCP connection to the Platform Agent.

SAP Job Servers

There can be one or more Job Servers for every instance of an SAP System in your environment. For example, you might have one per interface (XBP, XMW, XAL, or PI) or one per instance/client. This allows SAP Systems and interfaces to be managed in a granular manner, and makes it possible to manage scheduling on both a per-system and a per-interface basis.

To create an SAP Job Server, define an SAP System object in Redwood Server.

There is one Job Server for each SAP System or Platform Agent. This allows Platform systems, SAP Systems and interfaces to be managed in a granular manner. For SAP Systems, this also makes it possible to manage scheduling on both a per-system and a per-interface basis.

License Keys

Job Servers that schedule workload or use file events require at least one of the following license keys:

  • ProcessServerService.External.limit: Sets the maximum number of external Job Servers (Platform Agents, distinct web service endpoints, and SAP Connectors).
  • ProcessServerService.OS.limit: Sets the maximum number of Unix and Windows Platform Agents that can be configured. HP OpenVMS and AS/400 are not affected by this license key.