Job Server Services

Job Servers host Services, which allow them to run processes of different types.

Note: In some circumstances, you might want to assign a Service but no Job Definition Type to a Job Server. For example, you might want to do this with a Job Server that is used only used for File Events.

Supported Job Types

The types of Job supported by RunMyJobs include the following.

  • SAP ABAP jobs (via XBP) in R/3 and InfoPackages and Process Workflows (via BW-SCH) in BI and Mass Activities in IS/U
  • System Jobs (locally) for maintenance tasks
  • SAPPI jobs with SAPPI Job Servers
  • Platform Job Servers , which can run the following types of scripts:
    • UNIX shell scripts
    • Windows CMD scripts
    • HP OpenVMS scripts
  • Perl scripts
  • AS/400 jobs
  • z/OS jobs via JES (FTP)

Note: Some Job Definitions are part of a module and require a specific license.

Available Services

The following Job Server services are available by default.

  • AS400Service: Connects to AS/400 systems.
  • JDBCService: Connects to databases.
  • JobChainService: Enables the execution of Workflows.
  • MailService: Enables the creation of custom emails.
  • OraAppsService: Connects to Oracle Applications (Oracle EBS) systems.
  • OracleJobService: Connects to local Oracle databases.
  • OraOhiService: Connects to Oracle Health Insurance systems.
  • PeopleSoftService: Connects to SAP PeopleSoft systems.
  • PlatformAgentService: Connects to Platform Agents.
  • PublishService: Publishes files to Report2Web or Archive Server systems.
  • ReportService: Generates reports.
  • SAPBOBJService: Connects to SAP BusinessObjects systems.
  • SAPPIService: Connects to SAP PI/XI systems.
  • SAPR3Service: Connects to SAP systems.
  • ScriptService: Enables the execution of RedwoodScript Jobs.
  • System: Enables the execution of system Jobs.
  • UserMessageService: Creates and processes User Messages.

Note: SAP Job Servers work differently from other Job Servers in that you cannot create them manually. Instead, create an SAP System, and RunMyJobs will create a Job Server for the SAP System.

Services have three possible statuses: Connecting, Running, and Shutdown. All services of a scheduler need to have a Running status for the Job Server to have the Running status.

Mixing Job Server Services

You can mix Job Server Services. You can, for example, add the ScriptService to an SAP Job Server. However, be careful if you mix Services that save their files remotely with Services that save their files locally. If you override the default settings of DataRootDirectory, the resulting value must be valid on all systems involved. For example, if you set DataRootDirectory to F:\\Some\\Directory on a Platform Agent Job Server, and then you add the ScriptService to this Job Server, F:\\Some\\Directory must exist on the central RunMyJobs server or your Jobs will fail.

Also, if the central RunMyJobs server and the Platform Agent Job Server are not running on the same platform, and you have specified a DataRootDirectory parameter on the Job Server, do not mix Services. Instead, create a separate Job Server with the ScriptService and put it in the same Queue(s) as the Platform Agent. Do not use the System Job Server for this, because there is no way to stop it.

The following Services store files on the central Redwood Server.

  • AS400Service
  • JDBCService
  • JobChainService
  • MailService
  • OraAppsService
  • OracleJobService
  • OraOhiService
  • PeopleSoftService
  • PublishService
  • ReportService
  • SAPBOBJService
  • SAPPIService
  • SAPR3Service
  • ScriptService
  • SystemService
  • UserMessageService

The following Service stores files on remote systems.

  • PlatformAgentService

Security

A Service cannot be modified by a user, can be seen by all users, and has no privileges.

When you are configuring a Job Server, the Services tab lets you select which Services are assigned to that Job Server.