SAP Systems
Redwood Server 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".
This allows each of the following interfaces to be configured:
| Interface | Description |
|---|---|
| XBP | Job monitoring, scheduling, and intercept rules for individual clients. |
| XBP | Event Control Rules. |
| Generic Request and Message Generator (GRMG) | Monitor the availability of technical components and entire business processes. |
| SAP API (SAP Inbound) | Interface that allows SAP Systems to interact with Redwood Server, this is the interface that enables Closing Cockpit. |
| SAP BusinessObjects (SOAP) | Schedule BusinessObjects Crystal Reports, Web Intelligence, and Data Services jobs |
| SAP PI/XI | Control communication channels |
| SAP BI/BW | Monitor, intercept, schedule, and restart process chains and infopackages |
| SAP ISU | Schedule mass activities |
note
Redwood Server 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 process definition SAP_AbapRun allows you to run ABAP reports in an SAP System. When you submit this process 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 process can be submitted to an SAP System, where a CCMS job ( SM36 ) with the provided characteristics is created and started. This process is then monitored by Redwood Server 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 process definition SAP_ImportCcmsJobs. For each of the imported jobs, a new process definition is created, and the characteristics of the SAP job are stored as default values in the process definition. For SAP jobs with more then one step, a process definition for each step is created, and a chain definition is generated that runs the process 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. You can select which parameters (print, archive, recipient) you would like to add to the imported definition; note that it is good practice to only select the parameters you need, fewer parameters improves performance.
Platform Systems
Platform systems is a generic term used to specify Unix, Windows and OpenVMS systems. Redwood Server can connect and schedule native 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 Redwood Server in Configuration > Software.
note
When you want to schedule platform-specific workload (batch or shell scripts, for example) or use file events 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. These are not required for monitoring only.
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.