Thursday, May 28, 2015

All you want to know about IBM BPM Event Manager - Performance tuning


If anything most irritating in IBM BPM product is its lake of documentation of user manual for the product. I have spend long time on finding information about different component of IBM BPM and believe me its bit tough to find good article or manual. 

Yesterday, I found a very good article on IBM BPM Event Manager by BP3 and it has almost everything we want to know about IBM BPM Event Manager.

Which includes topics like below.

Event Manager Design

In the Event Manager (EM) design the database the master of everything.
The important Event Manager related table in BPMDB are:
lsw_em_instance - A row for each EM scheduler.
lsw_em_task - A row for each non-completed task, includes a reference to lsw_em_instance to indicate which scheduler owns each task.
lsw_em_task_keyword - One-to-many table mapping a task to its associated keywords
lsw_em_sync_queue - A row for each sync queue, includes a reference to lsw_em_instance to indicate which scheduler owns each sync queue.
lsw_uca_blackout - A row for each blackout period, including the next transitions into and out of blackout
The database knows what schedulers exist, what sync queues exist, what tasks exist, what states the tasks are in, etc. So, basically Event Manager uses the database’s transaction guarantees as much as possible to ensure a consistent view across all machines in a cluster. In addition, Event Manager uses the database’s system clock as the master, to avoid problems with time-syncing among machines in a cluster.
You can find full Article at below link which is very informative and intresting. 

Saturday, May 23, 2015

what to do when a Service or BPD in loop in IBM BPM and kill process does not work

Question

During testing and development, a business process definition or service might accidentally enter into an infinite loop. What is the procedure to clean up these unnecessary instances and tasks and stop the looping?

Cause

IBM Business Process Manager is a development platform and has many of the same programming structures and features that are found in traditional programming, such as looping, recursion, and so on. Looping on a service or business process definition is possible. As with any looping event, an exit condition must exist. Sometimes during development or production runtime, an infinite loop can occur.
IBM Business Process Manager has a component called the Event Manager. The Event Manager moves tokens in the business process definition engine and the service engine. The Event Manager continues to process a looping event until the event manager is stopped or the loop stops.

Answer

http://www-01.ibm.com/support/docview.wss?uid=swg21622584