RiftSaw 2.2.0.CR1 released

[objectiser]

The main highlights of this release include additional functionality in the BPEL console, including visual display of the execution path of an active process instance, and extending clustering support to management features, enabling processes to be activated or retired from any cluster node.

More detail about the release can be found here: http://riftsaw.blogspot.com/2010/11/riftsaw-220cr1-released-with-clustering.html

[cesarwbr]

Hi,

I use this version but I can't see the execution path and variables values like ActiveBpel show.

Is there a plugin or another bpel-console that I can use?

[objectiser]

Hi

As shown in the BPEL console section of the user guide (http://docs.jboss.org/riftsaw/releases/2.2.0.CR1/userguide/html/admin.html#d0e40), when you display the list of active process instances, and select a particular instance, you will see the 'Execution Path' and 'Instance Data' in the bottom right hand corner.

Regards

Gary

[cesarwbr]

I executed the esb sample (bpel_helloworld) with the bpel sample (bpel_helloworld). The data about the execution is all in the riftsaw database, but when I look in the bpel-console (Manage Instances -> HelloWorld) there is nothing in "Running" tab, I pressed the refresh button but nothing happend. What am I doing wrong?

Configuration:

Fedora 13

jboss-5.1.0.GA

jbossesb-4.9

riftsaw-2.2.0.CR1

mysql

Firefox 3.6 and Chrome 7.0

[objectiser]

Hi

Currently this functionality is only available for active process instances - so best to use the simple_correlation example, send the hello message and then look at the console.

Regards

Gary

[cesarwbr]

It works. But what do mean about "active process instances"?

[objectiser]

I mean process instances that have not yet completed.

We are planning on adding similar functionality for completed process instances - but this will be outside of the ODE process store, so this is on-going work.

I would encourage you to create feature requests in the riftsaw jira for any management features you are interested in, as this is the best way to ensure we are working towards functionality that users require.

Regards

Gary