We have played enough with mashups of google maps and flickr photos. But how this new technology can help enterprises or more specifically how mashup can be used to reduce the famous "enterprise information overload".Mashup seems to be a new found way of finding information in right form (presentation) i.e. craigslist rental apartments in google map or with flickr photos. But recently people
When developing any BPEL based solution, good practice dictates that you take a modular approach to process design, which allows the sharing of sub-processes among higher level processes. For example a payment process may be used by both the Expenses Process and Order Process.
As a result you will often end up with BPEL processes that you only intend to be called by other BPEL processes, and typically BPEL processes with at least some knowledge about the underlying process. So how do you prevent other ‘clients’ from directly invoking these processes?
Recently I was working with a client who wanted to implement a recursive process (i.e. one that calls itself). Now Recursion is a classic programming pattern, and in theory it should be pretty straight forward for a process to call itself. However at first sight it’s not so obvious.
The issue here is that the way a BPEL Process calls out to another process is to drag a Partner Link on to your BPEL Process and then use the Service Browser to select the deployed process that you wish to call.
I recently had the pleasure of presenting the Oracle Key Note at the Butler Business Process Management & Integration symposium. The subject of the keynote was to look at how we can use business analytics to enable us modify processes already in-flight.
When you consider the traditional closed loop BPM Lifecycle, as illustrated below, the emphasis has always been very much on using analytics about how processes have performed in the past, in order that we can modify the actual process definition in order to improve / optimize future versions of the process.
The notification service in Oracle BPEL Process Manager allows you to send a notification by email (as well as voice message, fax, pager, or SMS) from a BPEL process.
However another requirement is to be able to use the receipt of an email to initiate a BPEL process. This is the subject of this blog, many thanks to Muruga Chinnananchi on whose original example this is based.
Essentially we want to create a simple process EMailActivation which recieves an email sent to a particular email address. To achive this there are two basic steps:
When developing any BPEL based solution, you soon find that you are defining a common set of data objects that are used across multiple processes.
The most obvious place to define those data objects is in one or more XML Schemas which can then be referenced by each of your BPEL Processes.
Oracle BPEL PM 10.1.3 now provides the ability to import these Schemas as part of the BPEL Project Creation Wizard (in previous versions you had to import the Schema after the project was created – which you can of course still do in 10.1.3).
When debugging BPEL processes it can sometime be very useful to see the actual messages flowing between processes.
Now, often the audit trail in the BPEL Console provides sufficient information to see whats going on, and by clicking on the appropriate invoke, receive or reply activity you can see the content of the payload that was sent or received.
However this is only half the story as it doesn’t show details of the actual soap message exchanged and in particular details such as the SOAP headers used for WS-Security and WS-Addressing.
In a posting on Meeraj Kunnumpurath's weblog , I read that the Java Servlet specification 2.5 (still in maintaince version) will have the ability to inject dependencies to classes whose lifecycle are maintained by the container. This means that you can just inject and use resources, like EJBs and DataSources, in the same way as you can do now in the EJB3.o specification (still in beta-version).