Show TOC

Background documentationConfiguring the Central and Satellite Systems Locate this document in the navigation structure

 

The SAP module allows you to connect to SAP Systems, and provides the default SAP job definitions.

SAP CPS requires an RFC user on every SAP AS (ABAP) system with specific privileges and connection details which are stored in SAP Systems repository objects.

The Free of Charge license uses only the built-in functionality of the interfaces of the connected SAP release; the Chargeable SAP CPS takes advantage of so-called Redwood transport files that enhance the functionality of the following interfaces:

  • XBP 0.1 to 2.0

  • Industry Solutions (IS) mass activities

For more information on the transport files, see Enhanced SAP Interfaces with Redwood Transports.

Note Note

If you are using an isolation group, you will be restricted from accessing more than one SAP System if the license key ProcessServerService.SAP.limit is set to 0.

End of the note.

  1. Understanding The Different XBP Interface Releases

  2. Enhanced SAP Interfaces with Redwood Transports

  3. Configuring an SAP System for Central Process Scheduling

    1. Enabling XBP 2.0 features

  4. Connecting to SAP Systems

    1. Intercepting SAP Jobs

    2. Controlling Batch Input Sessions

    3. Interacting with SAP Events

    4. Parsing Log Files to set Job Status of SAP Jobs

    5. Integrating SAP Monitors

    6. Sending Monitoring Data to SAP Systems

    7. Controlling Communication Channels with SAP CPS via PI/XI

    8. Monitoring SAP CPS Availability in CEN

    9. Configuring the Message Driven Beans Scheduling Interface

  5. Creating a SAP CPS RFC Server

    1. Integrating Into Closing Cockpit