Tags

I would like to talk about the every popular and common features of TWSearch and saved searches for IBM Business Process Manager (BPM). Searching! Searching for instances and tasks is a common operation in IBM BPM. Three common methods are with the TWSearch JS API ( example 2 ), exposed saved search , and the REST API searches ( saved search and query ). Something we see in Support is "How and why are my searches taking a long time?" Sometimes the performance issue is the query itself and how the query... [More]

The running of business processes and services in IBM Business Process Manager (BPM) involves persisting data in multiple tables in different cardinalities in the BPM Process Server schema (assuming Oracle as the database in this blog) including the persistence of the process instances, tasks, variables etc. Once these processes are completed or terminated, the data is of little use to the functional needs of the business. At a given point in time, a process can assume the following states Active-1 Failed -3 Suspended -6 Terminated -4... [More]

As you know IBM Business Process Manager is built upon Java technology whose performance is highly impacted by garbage collection. Usually IBM Business Process Manager would recommend to use generational concurrent garbage collection strategy (-Xgcpolicy:gencon) which is well suited to an application that creates many short-lived objects, you can read this section in the product documentation to better understand this policy: Generational Concurrent Garbage Collector . Analyzing the textual verbose GC information recorded in... [More]

I've been working on some PMRs (Problem Records) lately for threads either completing slowly or being reported as "may be hung" in WebSphere Application Server and many of the products that run on it. A very common scenario is seeing threads in socketRead: For example: [9/15/14 9:32:13:492 PDT] 00000023 ThreadMonitor W WSVR0605W: Thread "WebContainer : 0" (00000021) has been active for 692481 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung.... [More]

I often hear claims of CPU Starvation: Me: "How have you met this conclusion?" Client: "There are 'CPU Starvation' messages in the SystemOut.log." Me: "Does the CPU monitor report high CPU?" Client: "No." Me: "Do the end users report slowness when using the application?" Client: "No." Me: "Is this a virtual environment?" More often the answer to the last question is "Yes". In this case it is important to check the virtual environment host... [More]

By default, Business Process Manager (BPM) currently permits ONLY ONE administrative account to log in to the Performance Admin Console; the administrator account and password that was specified on the Administrative Security page during IBM BPM profile creation. Even deployment environment administrators or users who belong to the tw_admins group also cannot access Performance Admin Console. Here I will prove this by using 'admin' user id which is created during profile creation and other administrative ID to access Performance... [More]

When you experience long elapse times for Business Process Manager (BPM) REST calls, you could check the BPM server SystemOut log to find out which calls they are and how long they took. This dW Answers link shows what these messages in SystemOut look like. Many BPM REST call performance problems are related to user security, so let me elaborate a bit on the background: To execute a REST call, BPM must authenticate the calling user, in case the REST call is not part of a http session already. BPM must do that to check the user's... [More]

If you are experiencing a very Slow WebSphere Application Server Startup and/or possibly WSAdmin command executions or Administrative Console operations are taking a very long time to complete, regardless of what product version you are currently running, the issue could be IP Address lookup and Hostname resolution related. This is contingent upon finding supporting evidence of relevant java/net/Inet6AddressImpl.getLocalHostName(Native Method) involvement in the associated Java cores, Thread dumps or System logs for the java process in... [More]

This article is about APAR JR53733 which will be published soon and there is a very useful workaround for this APAR. The workaround is to manually fix the problem by changing the code in Process Portal application in Process Designer. As you may know, Process Portal Application is a system Application of Process Portal UI and this workaround could give you some hints about how Process Portal system application code is associated with corresponding UI dashboard functions. Problem: In BPM 8.0.1.3, when we login to Process... [More]

This is the process of investigating cpu utilization for a JAVA™ application server in response to a need to resolve a performance problem or to determine a base line for the application. Specifically, this investigation applies to AIX, linux, Solaris, HPUX, UNIX® like systems, and Windows. This will uncover the amount of cpu resources reported in use, the amount of available cpu used by each process, and the amount of cpu used by threads in processes. We use this process very often in WebSphere Application Server Support, but... [More]

I wanted to list some steps below to help Identify a High CPU or possible Hang condition in WebSphere Application Server on AIX resulting from non-thread safe HashMap usage. The Hashmap APIs contributing to High CPU or Hung Threads at the top of the java ™ stack, can include removeEntry(), getEntry() or findNonNullKeyEntry() function calls. * Note that this issue can prevail on any OS platform and that the naming convention for the files shown below does vary. 1) Collect the Performance Hang High CPU MustGather data... [More]

IBM Business Process Manager (BPM) supports powerful, high-performance business process management while providing a simple way to model business processes. BPM is based on WebSphere Application Server and includes many components. So it can be complicated when you hit a performance issue, as the performance issue can occur in any component. This blog will discuss the required information and data for troubleshooting the performance issue by yourself or the IBM Support team. Benchmark your application before putting it into production... [More]

In IBM Business Process Manager, there are 2 types of navigation methods for a BPEL process: One type is JMS navigation, which was introduced in the early releases of WebSphere Process Server and another type is named Work Manager Based Navigation. In this blog, I'd like to give a brief instruction about how Work Manager Based Navigation works. Work Manager Based Navigation is the default navigation method of IBM Business Process Manager Advanced for the BPEL processes. The introduction of Work Manager Based Navigation has only one purpose:... [More]

The purpose of this article is to discuss a specific performance optimization related to the use of the Dojo toolkit in WebSphere Lombardi Edition. WebSphere Lombardi Edition V7.x and IBM Business Process Manager V7.5 ship with a JavaScript library called Dojo ( www.dojotoolkit.or g). This tool provides JavaScript widgets that are used by both the portal and coaches. The default for this tool from dojotoolkit.org, as well as from IBM inside the products, is to ship with a separate .js file per widget. In cases where network latency is an... [More]