Process Server Services 
Process servers have services to execute specific job definition types (see the documentation shipped with SAP CPS for more information on this feature) or connect to specific external systems. A process server can have one or more services to enable it to carry out these specific tasks. SAP process servers are special, in that you cannot create them manually. You have to create an SAP System, which creates a process server for the SAP System.
The following services are available by default:
AS400Service - connects to AS/400 systems
JobChainService - allows execution of job chain jobs
JXBPService - allows execution of Message-Driven Beans jobs
MailService - allows creation of custom emails
PlatformAgentService - connects to Platform agents
SAPPIService - allows control of communication channels
SAPR3Service - connects to SAP Systems
ScriptService - allows execution of RedwoodScript jobs
System - allows execution of System jobs
Services have a status, which can be one of the following:
Connecting - the service is attempting to connect the remote server
Running - the service is operational; for connecting services, this status means that the connection has been established between the remote system and the Central Scheduler
Shutdown - the process server is shutdown
Note
All services of a scheduler need to have a Running status for the process server to have the Running status.
Note
When you create or edit a process server, the required services are added automatically to the process server based on the job definition types or the SAP interfaces you configured, so there is no need to change services on a process server. The only exception is for process servers that are used for file events exclusively, there you do not need to specify a job definition type, however, the PlatformAgentService has to be added manually.
Mixing Process Server Services
You may mix process server services, however, you must be careful when doing so. You can, for example, add the ScriptService to an SAP process server. You should watch out, however, when 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 you add the ScriptService to this process server, the directory has to exist on the Central Scheduler (where RedwoodScript jobs are processed) or the jobs will fail. If the Central Scheduler and the platform agent process server are not running on the same platform (Windows, Unix, HP OpenVMS), you should not mix services if you have specified a DataRootDirectory parameter on the process server. You should create separate a process server with the ScriptService and put it in the same queue(s) as the platform agent as using the System process server for this is not recommended (you cannot stop it).
The following services store files on the Central Scheduler
AS400Service - connects to AS/400 systems
JXBPService - allows execution of Message-Driven Beans jobs
MailService - allows creation of custom emails
SAPPIService - allows control of communication channels
SAPR3Service - connects to SAP Systems
ScriptService - allows execution of RedwoodScript jobs
System - allows execution of System jobs
The following service stores files on remote systems
PlatformAgentService - connects to Platform agents