Support for mulitple WSDL operations within one BPEL process

Today, as I was writing on a technote, I found a nice sample again, built some time ago for a danish customer. I thought to share it with you.

It's about having a BPEL process offering multiple operations such as createCustomer, deleteCustomer and so on ..

Usually you get a wsdl from a service provider, that already contains bindings and services (of course - someone already implemented it :-D)

When you try to import it now as client PLNK - the bpel designer (and compiler) will complain? Why? Because you are going to be the service provider and not the service consumer.

In a nutshell, delete the binding(s) and service(s) section in the wsdl, and try again, it will work.

Ok, back to the beginning ..

Start with a new BPEL project (type empty process). Add a new partnerlink, and name it client - base it on your new wsdl (that is by now binding/service - less). Step one is done, the new face of your process contains all the nice operations defined in the wsdl.

Afterwards create an initial pick activity (and flag it to create a new instance). From the pick, delete the onAlarm branch (as it is initiating!), and for each operation add a new branch, to do whatever the process might require. Choose in each branch an operation from the partnerlink and add the callbacks accordingly (invoke/reply - as defined)

Voila, you multi operation BPEL process is ready to rock..

Having questions? send your feedback on multiple operations in one bpel process here