Developers are all used to finding bugs in common programming languages, but how does this work for graphical models? This article explains in detail how to solve your process issues by using the tools shipped with SAP NetWeaver Composition Environment.
SAP NetWeaver Business Process Management (SAP NetWeaver BPM), as part of SAP NetWeaver Composition Environment 7.2, offers new ways of modeling business processes using the Business Process Modeling Notation (BPMN) standard. At the same time, SAP NetWeaver BPM brings the modeled processes to execution. In this sense BPMN is used as a kind of graphical programming language. Although graphical programming brings many benefits to the developer community (such as productivity gains), it is still unavoidable that errors will make their way into the models.
The SAP NetWeaver Business Process Management (SAP NetWeaver BPM) design and runtime environment, which uses the Business Process Modeling Notation (BPMN) for process modeling, improves developer productivity significantly because it takes over much of the cumbersome and error-prone development tasks. Although many error conditions are checked during development time, bugs often still make their way into the final executable model. During runtime, your process might either hang or throw exceptions.
Then the key question is: How can I figure out what went wrong? I’ll give you some tips and tricks that help you to find out why your process model is not working. This article is for developers who are in charge of implementing innovative processes for their companies. See how the tooling shipped with SAP NetWeaver BPM helps you to identify the root causes of your errors. I assume that you are familiar with the modeling environment of SAP NetWeaver BPM and you know how to model, deploy, and run BPMN-based processes.