Using SeeWhy with the JBoss SOA platform

Build 'intelligent applications' with SeeWhy and jBPM

The combination of SeeWhy and jBPM lets organizations build state-of-the-art ‘intelligent applications' using Service Oriented Architectures, making business processes relevant, personalized and responsive. SeeWhy gives business operations staff visibility of events streaming through the JBoss SOA platform, notifying them of problems and opportunities as they arise and initiating automatic responses via jBPM.

SeeWhy brings major benefits to your jBPM and SOA projects:

• Analysis triggered processes: build ‘smarts' into your processes by monitoring events for business risks and opportunities
• Real time alerts: identify problems immediately, and get early warning of imminent trouble
• Business Activity Monitoring (BAM): gives you visibility of processes executing in real time

Achieve all of these and more by deploying SeeWhy as part of your jBPM and SOA projects!

For example, business processes may be triggered based on an analysis of the very latest customer actions, or a process flow modified on, say, the occurrence of a customer related exception.
Coming soon: the new 'SeeWhy for JBoss jBPM'.

The forthcoming SeeWhy for jBPM product will make this even easier, but read on to find out how to get these benefits today.

Here's how

Step one: Publish events to SeeWhy

>> Click here for full size image

This screenshot shows how to publish events to SeeWhy from different points in a process.

To do this simply specify the point(s) in the process from which you want to send data, define the data to be sent, and set the target as the SeeWhy JMS queue. Other user services, such as an ESB, can also deliver the message to SeeWhy.

This screenshot shows jBPM's graphical process modeller running in Eclipse.

Step two: Configure SeeWhy

>> Click here for full size image

SeeWhy Designer (v3.0 and later) is used to set up metrics, alerts and actions, and deploy metrics in to the live event stream.

SeeWhy Designer's Metric Configuration module lets you quickly design advanced monitoring scenarios that automatically identify problems and exceptions.

Once you're happy with your monitoring scenarios, simply configure the alerts and actions so that the right people are notified of problems. Use SeeWhy Designer to define structured events for output onto a queue.

Step three: Set up an event queue listener in jBPM

>> Click here for full size image

If required, the monitoring scenario can directly initiate processes in jBPM. SeeWhy can use your own JMS listener, or we have a listener you can use. (Contact us at info@seewhy.com).

The screenshot on the right shows the listener picking up a SeeWhy alert and initiating a process based upon this event.