Hi All,

As the subject of this article suggests, I am just going to highlight the Features & Advantages of the popular ‘BPM System Overview’ section of the Server which is available on the NetWeaver Administrator which is one of the most important tools for a Business Process Administrator to monitor the performance of the BPM Processes and Task-instances on the Server.

Log-in to the NWA of the server with Administrator rights. Make sure you have either ‘BPM_SuperAdmin’ role if not ‘NWA_SuperAdmin’ to be able to view and perform operations through this option.

Go to ‘Availability & Performance’  –>  ‘BPM System Overview’. The screen should look like this:

BSO.jpg

As you can see, this is a one-stop workshop for any BPM Administrator and a handy tool for everyday monitoring.

On the right hand side of the screen you can see the total number of process instances running on the server. Also, they are segregated according to the error status of the process instance: Error, Failed, Suspended, Completed, Cancelled and In-Progress.

If you observe closely, the number which indicates the number of process instances against each error status, is a link. When you click on this number, it will open the ‘Manage Processes’ section, but with all the process instances with the corresponding error status, irrespective of the Development Component of the Process Instance.

Similar is the case for Task-instances. The corresponding links will open the ‘Manage Tasks’ section.

All this sure saves the effor to go to separate sections such as ‘Manage Processes’/’Manage Tasks’/’Process Repository’ and then perform an action on an instance after searching and filtering through hundreds of instances based on Development Components.

Both the sections have the manual ‘Refresh Option’.

Note: You can perform normal operations from here just like you perform any action on any Process/Task instance from ‘Manage Processes’ or ‘Process Repository’.

Now, if you observe the Left hand side of this screen, you will see all the configuration settings and their current server status which may be a cause of concern for any BPM Admin.

I am not trying to impart any knowledge through this blog but my primary aim is to make people aware of this tool which may come handy for any BPM Administrator/Monitor. It sure does come in handy for me. 🙂

Please let me know if I have gone wrong somewhere and provide your inputs if I have missed out on anything.

Regards,

Siddhant

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. Anja Böhm

    Hi Siddhant,

    thanks for your blog. I haven’t yet fully understood the tables shown via link ‘process instance memory threshold’. What exactly mean the values in the columns of the first table ‘total number of process instances of server node’? On our server we have a few hundred up to thousand process instances per process definition actually in status ‘in progress’. However the table in column ‘normal’ shows the numbers 1 or 2. Does it mean number of process instances on which actually system threads are working on?

    If column ‘error’ shows the number 3, does it mean that maximum number of process instances are in status ‘in progress’ and these 3 attempts to start a process instance failed? Or does it mean that just in this moment maximum number of process instances loaded to memory were exceeded and no more process instances get started? Is the data of the failed process instances stored in a queue and will they get started once the number is back below the threshold?

    Thanks.

    Regards

    Anja

    (0) 

Leave a Reply