ActiveBPEL the "Easy Way"

Well, if I wanted to get people to use ActiveBPEL and get up to speed quickly. I think I should document what I did to get the application up and running.

If I can only make a couple people have an easier time getting a BPEL process going quickly, my task will be done.

I have documented how one can get ActiveBPEL installed and deploy the Vendor Selection application. I would think that it could be done relatively quickly.

The Vendor Selector BPEL process can be found at http://techinitiatives.blogspot.com/2007/03/vendor-selector-activebpel-bpel-process.html

You can download the Vendor Selector User Manual

Please let me know if you have any comments on the "Vendor Selector User Manual"

The Vendor Selector ActiveBPEL BPEL process

Vendor Selector BPEL process

I finished the ActiveBPEL process I was working on from the ground up. This was part of a project I am working on for COMP 689(Advanced Distributed Systems) at the University of Athabasca. I have one course this summer and then a Thesis to write in the fall to graduate from the Masters of Information Systems program. I would like to do research in the area of SOA. That is why I proposed this idea for this course's project.

It always seems like a fair bit of work to get that first application working in the new environment. It always seems very simple after the fact :-).

My advice is go all the way with the ActiveBPEL Designer. Work through the from the ground up tutorial to build the loan approval example.

Vendor Selector BPEL process:

1 BPEL process (Coordinate the workflow)
2 Vendor Web Services (Provide quotes and allow purchasing of products)

This BPEL process helps facilitate the purchase of up to 3 products and 3 quantities. There are 2 vendors each with 2 methods, one to provide a bid price on the tender and another to actually make the purchase. The BPEL process will query both vendors then select the vendor with the lowest price and then call that vendor to actually make the purchase.

The BPEL and Web Service Clients are included in the Java source under the package
com.smith.client


I will provide 2 versions of the application.
1. With a MySQL 5.0 backend database (Available here)
2. Another which does not require a database (random bid quotes produced along with hard coded security authentication) (Available here)

My preferred setup:
Install ActiveBPEL Designer
Install Ant
Get a Java 1.5 jdk
If installing the database version of the Vendor Selector:
Install MySQL 5.0 (if using the database version)
and the MySQL java db driver

Scrum Presentation and Sample Scrum Backlog

I recently read "Agile Software Development with Scrum" by Schwaber and Beedle. It is an interesting agile methodology. The key to monitoring
progress is through a document called a Sprint backlog.

If you don't have the time to read a book on scrum, I did distill what I thought were the important ideas in a power point presentation.

The Sprint backlog tracks the status of project tasks over the duration of the Sprint (usually 30 days). Progress is shown visually with a "burndown chart" with hours of estimated work along the y axis and work time along the x axis.

Doug Tillman (http://www.dugthawts.com/) has had some interesting experiences implementing scrum.

I was determined to find a sample backlog and figure out how it worked. It is pretty much based on formulas summing columns. The sample can be found here . This is based on a sample I found on the web.

I used it to show how hypothetically I should work to finish a "Distributed Systems" course I am currently taking.

The LOADING tab shows all available resources and time available.
The SPRINT BACKLOG tab shows the work(assignments)
The BURNDOWN chart section shows the current progress
- if you are above the line you are currently behind schedule
- if you are below the line you are ahead of schedule

Also, interestingly, the rate of falling behind or catching up is shown by the burndown graph.
A nice visual tool indeed.

What I find interesting about the burndown chart is that it is a very visual way of seeing how the project is going and what steps might need to be taken.