Sensors in BPEL

This is an excellent article by Peter Ebell on the usage of Sensors in BPEL.
http://technology.amis.nl/blog/3326/debug-logging-in-bpel-using-sensors-part-1

I could not find the Part2 of this article.

I intend to update this with more information.

Passing Userid and Password Credentials as SOAP Header in BPEL

Problem
There may be Services that have policies enforced to receive the userid/password as part of the requests. If you do not have a Service Bus then this informaton has to be passed from the BPEL.


Solution

1. Right click on the Web Service in Composite Design view
2. Select "Configue WS Policies"
3. Add Client Security Policy as applies to your case. I had to us "oracle/wss_http_token_client_policy"
4. Add the following Binding Properties from the Property Inspector
1. "oracle.webservices.auth.username" : admin
2. "oracle.webservices.auth.password" : admin

If you look at the source generated in the composite .xml, you would see the following

  <reference name="...Service" ui:wsdlLocation="....wsdl">
    <interface.wsdl  ...../>
    <binding.ws port="....."
    
      <property name="oracle.webservices.auth.username" type="xs:string"
                many="false" override="may">admin</property>
      <property name="oracle.webservices.auth.password" type="xs:string"
                many="false" override="may">admin</property>




    </binding.ws>
  </reference>

Increasing memory of JDeveloper IDE

Problem
JDeveloper 11.1.1.3 by default comes with 768M of Max memory. When you have lot of files or objects in memory(I noticed this during XSLT of a large structure) JDeveloper runs out of memory and cannot open the file.

Solution

1. Go to C:\JDeveloperStudio11113\jdeveloper\ide\bin
2. Open ide.conf
3. And increase the memory to 1024 : AddVMOption  -Xmx1024M
4. Restart the Jdeveloper and this should not cause any poblem.

Disabling WS Addressing in BPEL

Background and Problem
In BPEL, the WS Addressing seems to be enabled by default. The external Web Service that is invoked from BPEL Service receives the WS Addressing and first verifies the end point. For some reason this end point that was generated by BPEL is incorrect and so throws an error. The only way the communication can be successful is to disable the WS Addressing.

Solution
In SOA 11.1.1.3, this can be achieved by adding a binding property in the BPEL.

• Select the WebService and you will see the Property Inspector.
• Add the Property "oracle.soa.ws.outbound.omitWSA" and set it to true. As of this version this property is not available in the dropdown. So you need to add this.
• Save it and deploy the new Service to test it out.
• The Steps are shown below as an image

Oracle BPMN2.0 : Important Things To Know

Oracle 11gR1Ps2(11.1.1.3) was released on April 27,  and supports BPMN2.0.

The Oracle documentation for BPMN is available at http://oracle-bpel.blogspot.com/2009/09/oracle-bpel-informative-web-sites.html

Following are the important points worth remembering

• A BPM Process can be converted to BPEL process
• BPM Process is a Composite Application
• Different Types of Business process are
• Synchronous
• Asynchronous
• Manual
• To expose a process as a service, your process must begin with a message start event
• The message start event enables you to specify input and output arguments to a process.
• It supports Timer Start Event which can be scheduled to kickoff at a certain time
• If you are invoking a process or service synchronously, use the service task.

SOA : Design Patterns : Foundational Service Design Patterns

Note : These are Design Patterns from "SOA Design Patterns" by Thomas Earl. The intent here is to simplify the patterns to a few lines so that they can be referred for a quick glance and also to document my experiences over time. This is by no means an effort to explain these patterns and I believe that the book has done an excellent job at that.


Functional Decomposition (Service Identification Pattern)

• Decomposes the business processes/tasks/problems to smaller ones
• Applies the separation of concerns 
• Helps greatly in Service Analysis and Service Modelling

Service Encapsulation (Service Identification Pattern)

• If Service oriented design principles (http://oracle-bpel.blogspot.com/2010/04/soa-design-principles.html) can be applied to a meaningful extent then the logic can be encapsulated as a Service. 

Agnostic Context (Service Definition Pattern)


Non Agnostic Context (Service Definition Pattern)


Agnostic Capability (Service Definition Pattern)

SOA : Design Patterns : Inventory Centralization Design Patterns

Note : These are Design Patterns from "SOA Design Patterns" by Thomas Earl. The intent here is to simplify the patterns to a few lines so that they can be referred for a quick glance and also to document my experiences over time. This is by no means an effort to explain these patterns and I believe that the book has done an excellent job at that.


Process Centralization




Schema Centralization


Policy Centralization


Rules Centralization