Khanderao on Emerging And Integration Technologies

Wednesday, June 24, 2009

Fusion Middleware AS11 would be launched in the next week (First week of July 2009)

You may have heard this in Oracle's quarterly conference call yesterday. As per Charles Philip, the Co-President of Oracle, " We are rolling out a major new release next week called Fusion Middleware 11G," he explained. "We'll launch that in Washington, DC and eight other cities around the world and then we'll follow-on with a tour in 107 cities." Finally all the hard work of last three plus years in building this great well integrated, feature rich and standards-based product would be available for customers to use! Feeling product!

Add to Technorati Favorites

Save This Page on del.icio.us

Tuesday, June 23, 2009

BPEL: Resolving ConflictingReceive Issue while using the same PL in the branches of Flow or FlowN

Issue: 

Developers often encountered conflictingReceive fault while using the same partnerlink in different branches of Flow or FlowN.

Details following:

"{http://schemas.xmlsoap.org/ws/2003/03/business-process/}conflictingReceive"
has been
thrown."{http://schemas.xmlsoap.org/ws/2003/03/business-process/}conflictingReceive"
has been thrown.



*summary*">
Conflicting receive. A similar receive activity is being
declared in the same process. Another receive activity or
equivalent (currently, onMessage branch in a pick activity) has
already been enabled with the partnerLink "Dummy", operation name
"processResponse" and correlation set "" (or conversation ID).
Appendix A - Standard Faults in the BPEL 1.1 specification
specifies a fault should be thrown under these conditions.
Redeploy the process after removing the conflicting receive
activities.




Solution:
Instead of defining the partnerlink as a global partner link, declare it within a scope of each parallel branch.

Add to Technorati Favorites

Save This Page on del.icio.us

Friday, June 19, 2009

BPEL: Links to synchronize a process flow

"link" is a construct to synchronize the BPEL process flow. However, for some unknown reasons, "link"s are lightly used in practice by most of the customers. One of the reason can be in its understanding and, other could be due to its usability. There is no specific UI icon in BPEL designer to represent the links. Its probably because, unlike other constructs, the artifacts related to links need to injected in multiple places. For example, First, a link needs to be defined, then source and target to the link needs to be defined. May be I should post an example covering it.





Add to Technorati Favorites

Save This Page on del.icio.us