Process Server Services

Process Server services enable Process Servers to connect to external systems. The following Process Server services are available by default.

  • AS400Service: Connects to AS/400 systems.
  • JDBCService: Connects to databases.
  • JobChainService: Enables the execution of Chain Processes.
  • 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 processes.
  • SystemService: Enables the execution of system processes.
  • UserMessageService: Creates and processes User Messages.

When you create a Process Server, the required services are added automatically. The only exception is for Process Servers that are used for file events exclusively. For these, you must add the PlatformAgentService manually.

Note: SAP Process Servers work differently from other Process Servers, in that you cannot create them manually. Instead, create an SAP System, and RunMyJobs will create a Process 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 Process Server to have the Running status.

Mixing Process Server Services

You can mix Process Server services. You can, for example, add the ScriptService to an SAP Process 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 Process Server, and then you add the ScriptService to this Process Server, F:\\Some\\Directory must exist on the central RunMyJobs server or your processes will fail.

Also, if the central RunMyJobs server and the Platform Agent Process Server are not running on the same platform, and you have specified a DataRootDirectory parameter on the Process Server, do not mix services. Instead, create a separate Process Server with the ScriptService and put it in the same Queue(s) as the Platform Agent. Do not use the System Process 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.