Business Process Model and Notation (BPMN) Archives

BPMN Undeployment with NWDS

By Maximilian | 2017-08-17 | Comments 0 Comment

Scenario

If you do not need a process anymore, it makes sense to undeploy a BPMN to free some resources.

Undeployment of a BPMN with NWDs

A BPMN can be undeployed with the help of the Netweaver Developer Studio (NWDS). Simply follow the steps below:

Open the NWDS and connect to your PO system
Open the “Deployment” perspective
Wait till the list of BPMNs on the left side is loaded, click on your process and drag the object into the “Undeployment list” on the right side
Click on the “Start” button
NWDS: Process undeployment
After some seconds the process should be undeployed

Find complete BPMN error traces

By Maximilian | 2017-07-31 | Comments 0 Comment

Scenario

During the development of a BPMN on SAP Process Orchestration you will probably arrive at a point where your Process does not work as expected. One way to find the issue is to check the traces in the Log Viewer, to find out more about the error.

Find the traces in the Log Viewer

Triggered the BPMN to run again
To check the BPM Status open PIMON (http://your.po:port/pimon)
Go to Monitoring -> Processes and Tasks -> Manage Process
Open the “History” Tab and select “Show: Advanced”. You can find the Log ID in the log entries below.
Manage Processes: Find Log Id

If the following message is shown:

For more details, decrease severity of log controller as described in SAP Note 1753560.

Please check the section Increase BPMN Trace level and afterwards start again with step 1.
Open the NetWeaver Administrator (http://your.po:port/nwa)
Got to Troubleshooting -> Logs and Traces -> Log Viewer
Open View -> Open View -> System Logs and Traces
Open “System Logs and Traces” view in Log Viewer
Add a filter for Log ID and enter the Log ID out of the “Manage Processes” View
NWA Log Viewer: Filter for Log ID
You can find the whole error trace in the filtered results.

Increase BPMN trace level

To increase the BPMN trace level follow the steps below:

Open the NetWeaver Administrator (http://your.po:port/nwa)
Go to Configuration -> Infrastructure -> Log Configuration
Select “Show: Tracing Locations”
Click on “Open Filter” and filter for Location “BPMNException”
Change Severity for location “ExceptionAdapter$BPMNException” to “ALL”
NWA Log Configuration: Increase Severity for ExceptionAdapter$BPMNException
Click on “Save Configuration” and trigger your BPMN again

Also, check out SAP Note 1753560.

“Start Process” in Process Repository is disabled

By Maximilian | 2017-07-26 | Comments 0 Comment

Scenario

If you develop a BPMN, you probably have to manually trigger the process multiple times to check that everything works as expected. One way to trigger a BPMN is the usage of the “Start Process” function in the Process Repository.

You can find the Process Repository in the NetWeaver Administrator -> Processes and Tasks -> Process Repository.

Error

The “Start Process…” button in the Process Repository is disabled.

"Start Process..." button in Process Repository is disabled — “Start Process…” button in Process Repository is disabled

Solution

The role “SAP_BPM_SuperAdmin” is necessary to use the “Start process…” function. To add the role to your user, follow the steps below:

Open the NetWeaver Administrator (http://your.pi/nwa)
Go to Configuration -> Security -> Identity Management
Select you User and open the “Assigned Roles” Tab
Click on “Modify” and search for the role “SAP_BPM_SuperAdmin”
Select the role, click on “Add” and afterwards on “Save”
Add role SAP_BPM_SuperAdmin to user

After refreshing the repository browser, the “Start Process…” button should be available.

Error during BPMN deployment

By Maximilian | 2017-07-20 | Comments 0 Comment

Scenario

Developing and debugging a BPMN can be a nightmare. The build and redeployment of a BPMN can take up to five minutes and lead to multiple errors.

After multiple successful deployments, it was no longer possible to deploy or undeploy a process.

Error

The following error message was shown in the deployment log of SAP NetWeaver Developer Studio:

Description: Description: 1. Adapter com.sap.glx.adapter.internal.Transformer has refused deploy unit e5853c8198e860817e261ae672f4bfc4 using configuration mode DEPLOYMENT

-> Transformer could not get lock within 60 seconds

Solution

Restart the Galaxy Core Service to fix the issue. This can be done like this:

Open the NetWeaver Administrator (http://your.pi:port/nwa)
Go to Operations -> Systems -> Start & Stop -> Java Services
Search for Name “Galaxy Core Service”
Select your Instance and click on Restart
Wait some seconds and try to deploy your service again