Show TOC

Background documentationPartitions Locate this document in the navigation structure

 

Partitions are used to store objects in the repository and isolate them from one-another together with isolation groups. Partitions are known as shared when they have an isolation group that is null.

If the ProcessServerService.SAP.limit license key is set to 0, the following restrictions are in place:

  • one SAP System may be created per partition with one XBP client.

  • any partition with a null isolation group is read-only.

  • only the system can create partitions with a null isolation group.

  • all monitors from SAP (vi XAL) will be created in the appropriate isolation group.

  • SAP batch event will raise events in the isolation group only.

  • job control rules will function only for jobs from the defined XBP client, child jobs will be picked up regardless in which client they were created.

  • variant management will be limited to the defined XBP client.

  • BW restart will be possible, however, it requires the ProcessServerService.SAP.ProcessChainRestart license key

  • Mass activities will be possible, however, they require the ProcessServerService.SAP.MassActivities license key

  • Redwood transports will be available for mass activities

  • SAP Applications API will be available, however, they require the ProcessServerService.SAP.ApplicationsAPI license key

  • SAP_AbapRun, SAP_BW_ProcessChainRun and all the other SAP job definitions that run jobs will only allow ABAP reports, variants, and process chains that have been imported into SAP CPS