Sharing Fault Policies Across Your Oracle BPM 11g Projects

We keep all our shared metadata across projects ( for example, some shared xsd files) in this SOA application. The shared fault policy files can be a part of the same application.

Lets create a new application (I call it SharedMetaDataApp) of type SOA Application.

• 2. Create a SOA project (I call it SharedMetadata) in the SOA application with an empty composite

 3. Create a new folder in the SOA project ( I call it FaultPolicies).

This is where we will be placing the Fault Policy and Binding Files.

4. Create the Fault Policy  and Binding files in this folder

Here is a starter Fault Policy file.

<?xml version=’1.0′ encoding=’UTF-8′?>

<faultPolicies xmlns=”http://schemas.oracle.com/bpel/faultpolicy“>

<faultPolicy

version=”2.0.1″ id=”EnterpriseFaultPolicy”               xmlns:env=”http://schemas.xmlsoap.org/soap/envelope/”

xmlns:xs=”http://www.w3.org/2001/XMLSchema”

xmlns=”http://schemas.oracle.com/bpel/faultpolicy”

xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance“>

<Conditions>

<faultName xmlns:bpelx=”http://schemas.oracle.com/bpel/extension”

name=”bpelx:remoteFault”>

<condition>

<action ref=”ora-human-intervention”/>

</condition>

</faultName>

</Conditions>

<Actions>

<Action id=”ora-human-intervention”>

<humanIntervention/>

</Action>

</Actions>

</faultPolicy>

</faultPolicies>

Here is a starter Fault Policy Binding file

<?xml version=”1.0″ encoding=”UTF-8″?>

<faultPolicyBindings version=”2.0.1″

xmlns=”http://schemas.oracle.com/bpel/faultpolicy”

xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance“>

<composite faultPolicy=”EnterpriseFaultPolicy”/>

</faultPolicyBindings>

This is how your folder structure should look at this point.

5.  Publish the Fault Policy and Binding Files to MDS

      a. Create a Jar Deployment Profile for the project.

Navigate to  Project Properties /Deployment.

You should see a SOA-SAR File deployment profile

Delete this profile.

Create a new Deployment Profile of type Jar file

In the Deployment Profile properties, deselect the include Manifest file

From Contributors, deselect Project Output Directory and Project Dependencies and add the Sharedmetadata project folder as a Contributor.

Set the filters to select only the files you want to publish to MDS

That should be it for creating the Jar deployment profile.

b. Create a SOA-Bundle deployment profile

Navigate to Application Properties/Deployment and click on new deployment profile.Create a new Deployment Profile of Archive Type SOA Bundle. In the Dependencies select the Jar deployment profile we created in step (a).

 6.  Create a SOA-MDS Connection in JDeveloper, so that you can view the contents in MDS, once we deploy.

Make sure you select the soa-infra partition.

You will now see the connection in the Resource Palette , IDE Connections.

Expand the /apps folder and you should see that its empty (except for perhaps a readme file, which you can ignore)

7.  Deploy the policy files to MDS

Navigate to Application/Deploy/SharedMetadataBundle…

Deploy to Application Server

Deploy to SOA server

After a successful deployment, refresh and expand the apps folder in your SOA-MDS connection ( in Resource Palette/IDE Connections).

You should now see the FaultPolicy folder in there with the FaultPolicy and Binding files.

8. Setting the reference to the Fault Policy in a BPM or SOA application that wants to use this policy.

Add these references in your Composite.xml

  <property name=”oracle.composite.faultPolicyFile”>

oramds:/apps/FaultPolicy/FaultPolicy.xml

</property>

<property name=”oracle.composite.faultBindingFile”>

oramds:/apps/FaultPolicy/FaultPolicyBinding.xml

</property>

Its important that you add these lines  after the last service definition and before the first component definition, otherwise the xml will not validate.

<service name=”SimpleWithNoLoggingService.service”

ui:wsdlLocation=”SimpleWithNoLoggingService.wsdl”>

<interface.wsdl interface=”http://xmlns.oracle.com/bpmn/bpmnProcess/SimpleWithNoLoggingService#wsdl.interface(SimpleWithNoLoggingServicePortType)”

callbackInterface=”http://xmlns.oracle.com/bpmn/bpmnProcess/SimpleWithNoLoggingService#wsdl.interface(SimpleWithNoLoggingServicePortTypeCallBack)”/>

<binding.ws port=”http://xmlns.oracle.com/bpmn/bpmnProcess/SimpleWithNoLoggingService#wsdl.endpoint(SimpleWithNoLoggingService.service/SimpleWithNoLoggingServicePort)”/>

<callback>

<binding.ws port=”http://xmlns.oracle.com/bpmn/bpmnProcess/SimpleWithNoLoggingService#wsdl.endpoint(SimpleWithNoLoggingService.service/SimpleWithNoLoggingServicePortTypeCallBack_pt)”/>

</callback>

</service>

<property name=”oracle.composite.faultPolicyFile”>oramds:/apps/FaultPolicy/FaultPolicy.xml</property>

  <property name=”oracle.composite.faultBindingFile”>oramds:/apps/FaultPolicy/FaultPolicyBinding.xml</property>     

<component name=”Simple”>

<implementation.bpmn src=”processes/Simple.bpmn”/>

</component>

9. Deleting the FaultPolicy from MDS.

Here are the steps when you need to do this…in case any  folder structure in MDS is obsolete or not correct and you want to recreate it.

Start WLST from the /Middleware /Oracle_SOA1/common/bin

execute the following command from the wlst prompt.

sca_removeSharedData (‘http://oelhost:8001‘, ‘FaultPolicy’, ‘weblogic’, ‘welcome1’)

first parameter : SOA Server url

second parameter : Folder under ‘apps’ you want to delete

third parameter: user id

fourth parameter: password