WHINT ProcessRestart Job


In case your BPM process is using an automated activity which can fail during processing (e.g. by calling an external service) and you did not set up any error handling (by managing boundary events), your process will fail and remains in status “Suspended”. Then you have to manually resume the process from the Process Monitoring. Or you use the following solution:

WHINT ProcessRestart Job is a solution that automatically looks for BPM Process Instances in error and resumes them automatically.


  • Works with SAP NetWeaver PO (BPM) version 7.3 EHP1 and higher (including 7.50)
  • Deploy the SCA/EAR file provided by Whitepaper InterfaceDesign using NWDS/JSPM/SUM/Telnet



  • Schedule the job from NWA -> Operations -> Jobs -> Java Scheduler or via quick link /nwa/jobs
  • Add Task with Job name ProcessRestartJob
  • Parameters (best is to look them in the Process Repository in PIMON -> Configuration -> Processes and Tasks):
    • Component: Name of the development component
    • Vendor: Name of the software vendor
    • ProcessName: Name of the BPM process
  • The scheduling should be done according to your business needs (e.g. hourly orMon-Fri between 8:00 and 18:00)





The job is executed and restarts a process in error by resuming it automatically:


The resume activity is shown in the process instance history (here the process becomes suspended again):


WHINT AggregateMessages byReceiver BPM Process



This BPM process collects (aggregates) messages for a system and then (after 5 minutes collecting) forwards them to a receiver (system/partner). It is a generic process that can collect any XML data (not only IDocs) and forward it to a receiver.


  • SAP Process Orchestration 7.3 EHP 1
  • SAP Process Orchestration 7.4
  • SAP Process Orchestration 7.5


  • Deploy the SCA file provided by Whitepaper InterfaceDesign using NWDS/JSPM/SUM/Telnet
  • Import the TPZ file provided by Whitepaper InterfaceDesign into ESR


  • ICO/iFlow 1 (Sender to BPM): Map your single message XML to the generic XML Structure and define the correlation under which the messages have to be aggregated (e.g. receiver partner id, vendor number, order number, …)
  • ICO/iFlow 2 (BPM to Receiver): Map the aggregated message XML to the final target structure before sending it to the receiver

SAP PO Integration Patterns & BPM content

SCN article about Integration Patterns for SAP NetWeaver Process Orchestration (PO)

  • stateless patterns via AEX connectivity
  • stateful via BPM connectivity

Download the enterprise pattern reference models for BPM modeling from SCN