Simple BPEL Integration with BPM

The SeeWhy BPM Integration Kit as a generic toolkit showing you how you can integrate SeeWhy with BPM products. Using Business Process Execution Language (BPEL) the kit guides you through the steps needed to initiate processes within BPEL complaint BPM products, to use SeeWhy as an analytic process step and how to configure you BPM product so that SeeWhy can monitor and alert on processes at runtime. 

The kit is designed for a technical audience, familiar with BPEL and BPM products, and includes code samples and screenshots to enable you to deploy SeeWhy into a BPM environment rapidly.  

• To download your copy of the SeeWhy BPM Integration Kit click here.

SeeWhy for JBoss jBPM

The soon to be released SeeWhy for jBPM is the Business Activity Monitoring (BAM) component of the JBOSS Service Oriented Architecture (SOA) platform and is built on SeeWhy's experience from the currently available SeeWhy BPM Integration Kit.  

SeeWhy for jBPM greatly simplifies adding Business Activity Monitoring and Event Driven Business Intelligence to your JBoss SOA and JBoss jBPM projects. 

Find out more here

Example BPM integrations using SeeWhy

The combination of SeeWhy and BPM products enables organizations to build state- of-the-art ‘intelligent applications’ using Service Oriented Architectures. This enables relevant, personalized and responsive business processes, automatically tailored to individual; customers or products based on continuous analytics.  

For example, a stock replenishment process can be made much more efficient by basing reorder quantities on actual real time sales data rather than estimates.   SeeWhy enables business operations staff to gain visibility of the events streaming through their middleware, to be notified of problems and opportunities as they arise, and for automated responses to be initiated via their BPM product of choice.  

Here’s how: 

• Step one: Publish events to SeeWhy. 

To publish events from different points in a process to SeeWhy you specify the point(s) in the process from which you want to send data, the data to be sent, and the target, which is the SeeWhy JMS queue. This may also use other user services, such as an ESB to deliver the message to SeeWhy.

• Step two: Configure SeeWhy Using the SeeWhy Designer:

Set up metrics, alerts and actions, and deploy metrics in to the live event stream. The SeeWhy Designer’s Metric Configuration module enables you to quickly design advanced monitoring scenarios to enable you to automatically identify problems and exceptions. Once you’re happy with your monitoring scenarios, you configure the alerts and actions so that the right people are notified of problems. SeeWhy enables events to be structured and output onto a queue.   

• Step three: Set up an event queue listener in your BPM tool:

If you want the monitoring scenario to initiate processes, then provide a JMS listener, or contact SeeWhy where we have a listener you can use. The screenshot on the right shows the process that will be initiated by the SeeWhy alert.

• To download your copy of the SeeWhy BPM Integration Kit click here .

Coming soon: the new 'SeeWhy for JBoss jBPM'.