SAP Systems 
SAP CPS communicates with the satellite SAP Systems over a number of internal and external interfaces provided by SAP.
These can be configured from a single point: 
Environment → SAP Systems 
.
This allows each of the following interfaces to be configured:
Interface |
Description |
XBP |
Client configuration for XBP. |
XBP |
Job intercept rules for individual clients. |
XBP |
Event Control Rules. |
External Interface for Alert Management (XAL) |
Monitor synchronization from the SAP CCMS monitoring infrastructure. |
External Monitoring Write (XMW) |
Monitor synchronization to the SAP CCMS monitoring infrastructure. |
Java eXternal Batch Processing (JXBP) |
Control and monitor jobs deployed on AS Java. |
Generic Request and Message Generator (GRMG) |
Monitor the availability of technical components and entire business processes. |
SAP API |
Interface that allows SAP Systems to interact with SAP CPS, this is the interface that enables Closing Cockpit. |
Note
SAP CPS supports the SAP Generic Request and Message Generator (GRMG) protocol, however this must be configured through Computing Center Management System (CCMS) on the Central Monitoring System (CEN) in the landscape.
The standard job definition SAP_AbapRun allows you to run ABAP reports in an SAP System. When you submit this job definition, parameters like ABAP report name, a variant to run the report with, SAP print and archive parameters among others are required. Once you set the parameters, this job can be submitted to an SAP System, where a CCMS job (SM36) with the provided characteristics is created and started. This job is then monitored by SAP CPS until its completion. If requested, the SAP job log and the spool list of the report are retrieved, and the job is deleted in the SAP System.
It is also possible to import jobs from an SAP System via the standard job definition SAP_ImportCcmsJobs. For each of the imported jobs, a new job definition is created, and the characteristics of the SAP job are stored as default values in the job definition. For SAP jobs with more then one step, a job definition for each step is created, and a job chain is generated that runs the job definitions. This allows you to run the SAP job in different SAP Systems, as long as they provide the same environment like variants, SAP printers, and so on.
Platform Systems
Platform systems is a generic term used to specify Unix, Windows and OpenVMS systems. SAP CPS can connect and schedule workload on these systems, provided you have the Platform Module and a spare unit in the values of the ProcessServerService.External.limit and ProcessServerService.OS.limit license keys. To be able to connect to platform systems, you also need to install platform-specific software, known as a platform agent, on the nodes. The software is available for download in SAP CPS in Configuration → Software . Platform systems can also be used for load balancing SAP Systems, this requires you to install the platform agent on the nodes where SAP is installed and requires the above module and license keys.
Note
When you install platform-specific software on the host of an SAP System, you will need additional ProcessServerService.External.limit and ProcessServerService.OS.limit license keys. In fact, you will use two ProcessServerService.External.limit units, one for the SAP process server and one for the platform agent process server.
Platform systems allow you to create complex process scheduling scenarios integrating SAP and non-SAP jobs in one process; reducing the time between jobs to seconds regardless of where the jobs run. They also allow you real-time load balancing across SAP servers; the load is assigned to the system that has the most free resources. The platform system load balancing is not round-robin-based like SAP load balancing.