getting started with oracle soa x doc

7/27/2019 Getting Started With Oracle SoA X Doc

1/80

Getting Started with Oracle SoA

Implement Fault Policies Lab#10

Description:BISP is committed to provide BEST learning material to the beginners and

advance learners. In the same series, we have prepared a complete end-to end

Hands-on Beginners Guide for Oracle SoA. The document focuses on steps involved

in creating 1st Oracle SoA Project. Join our professional training program and learn

from experts.

History:Version Description Change Author Publish Date0.1 Initial Draft Shiva Kant Pandey 21st Aug 20120.1 Review#1 Amit Sharma 29th Aug 2012

www.bispsolutions.com www.bisptrainigs.com www.hyperionguru.com Page 1
http://www.bispsolutions.com/http://www.bisptrainigs.com/http://www.bispsolutions.com/http://www.bisptrainigs.com/


2/80

ContentsContents....................................................................................................................................... 2

Overview...................................................................................................................................... 3

Stepwise procedure to implement fault policies file..................................................................... 4

Fault handling (fault policies) in Student Project:.......................................................................10



3/80

OverviewThe purpose of the Fault Management Framework is to provide error handling that is external

to SOA and does not impact the SOA/BPEL design or runtime. The framework is implemented

using policies defined in XML. These policies are reusable across composites/components and

can catch both runtime and business faults. Once a fault is caught, the policy defines actions

that can be used for the SOA instance such as retry, human intervention, replay scope, rethrow

fault, abort, and custom Java actions. When human intervention comes into play, the EnterpriseManager provides a GUI for managing the faulted instance.

When the policies have been defined and bound to composites and/or components, theframework will intercept the fault before the standard fault handler comes into play. Forexample: if a BPEL process has defined standard BPEL fault handling and a fault policy hasbeen defined/bound to the BPEL process, when a fault occurs the framework will intercept thefault allowing any of the supported actions to be applied to the instance:



4/80

Stepwise procedure to implement fault policies fileStep 1: Download & install Notepad++ setup to edit files.

Step 2: Open folder containing fault-binding & Fault-Policy files

Step 3: Open Fault-Policy.xml with Text Editor



5/80

Step 4: Observe faultPolicies is the root node & it is register with namespace

xmlns="http://schema.oracle.com/bpel/faultpolicy"

Step 5: Now fault Policies consists of many faultpolicy but here we have taken

"TestFaultPolicy" as example for simplification



6/80

Step 6: Every fault policy is a set of

Conditions (When to act upon )

Actions (What to do )

These conditions consists of various system faultNames with their namespaces & prefix as

shown below:



7/80

Now Actions consists of various types of action to be perform. Example of some action id's

ora-human-intervention

ora-rethrow-fault

ora-retry

Step 7: Now every faultName consists of set of condition associated with action .



8/80

Step 8: Explore next faultName with name binding fault has set of condition & action , now

this action is defined in Actions example ora-retry is action for condition of binding fault &

hence ora-retry is defined in Actions.

Step 9: Explore actions one by one & see how these actions are defined



9/80

Similarly write for rethrow actions

Step 10: Observe how ora-retry action is defined inside



10/80

Retry count is five 7 it can be varied

retry interval is the interval between two successive retries in seconds

exponentialbackoff is the time wait

example 2^0 , 2^1 , 2^2 ..... & so on .

etry failure action that is if this retry completes all its counts & fault for that action is still

not recovered then finally it will call the failure action referred to ora-human-intervention to

invoke the admin.We can also referenced here an action for successful retry action .

So in this way we can develop fault policies .

Fault handling (fault policies) in Student Project:Step 1: Create new projectNew --->All Technologies--->SOA Tier --->SOA project --->OK ---> Project Name(TopperStudentOneWayProject) ---> ADF Business Component---> SOA--->Next -->Compositewith BPEL Process)---> Finish.



11/80

Step 2: Fill all its blank spacesName (TopperStudentOneWayProcess) ---->NameSpace (Leave as it is)--->Template(SelectOne Way BPEL process)----> Service Name(TopperStudentOneWay Service)----> mark Exposeas a SOAP service --->Click Ok



12/80

Step 3: Open Composite.xml & observe BPEL Process



13/80

Step 4: Click on TopperStudentOnewayProcess.xsd & it is automatically generated xsd for one

way bpel process .

Step 5: Go to Home ---> open jdeveloper ---> my work ----> SOAApplication --->

TopperStudentproject---> xsd---->

copy [Error.xsd ,Student.xsd,StudentList.xsd]

Step 6: Paste all xsd's inside physical location of TopperStudentOneWay Project xsd .



14/80

Step 7: Observe all three pasted xsd .

Step 8: Click on Refresh icon two three times & observe all three copied is displaying inside

TopperStudentOneWay xsd.



15/80

Step 9: Open TopperStudentOneWay. xsd & Right Click on target namespace & click import

Step 10: Click on source mode & Import StudentList.xsd & also register it as shown below :



16/80

Step 11: Click on design mode & observe imported xsd .

Step 12: Click on Process Element & rename it as TopperStudentOnewayRequest as shown

below:



17/80

Step 13: Expand TopperStudentOneWayRequest & rename Input Element as StudentList &

give slobj: StudentListType as its Type .



18/80



19/80

Step 14: Open TopperStudentOneWayProcess.wsdl & observe error since we have renamed it

in xsd but it is still present in wsdl

Step 15: Rename Process as topperStudentOneWayRequest as shown below:



20/80

Step 16: Open its bpel process

Step 17: Create variables , click (x)---> +



21/80

Step 18: Create CountVar , IndexVar, TopMarks all assigned as integer Type then click OK

Step 19: Drag & Drop Assign Activity & rename it as AssignTempVar & click to edit it .



22/80

Step 20: : To assign CountVar click on expression Drag & Drop on CountVar as shown below:

Step 21: : Explore Functions ----> BPEL XPath Extension Functions ----> CountNodes--->InserInto Expression--->select Student under Input Variable---> Insert into expression .Deletebpws:getVariabledata which is shown by green box



23/80

Step 22: Now xpath expression is set for countVar , Click OK



24/80

Step 23: Drag & drop Exression into IndexVar

Step 24: Assign 1 for IndexVar

Step 25: Drag & drop Exression into TopMarks



25/80

Step 26: Assign 0 for TopMarks .

Step 27: Click OK.



26/80

Step 28: Drag & drop While Activity & click on it to set while condition

Step 29: Click on Expression



27/80

Step 30: Assign looping condition hereClick IndexVar ---> insert into expression ---> Less equals --> insert into expression --->CountVar---> insert into expression---> Click Ok



28/80

NOTE: Since we want to invoke third party web service (ProcessStudentService) so we need to

copy concreate wsdl of ProcessStudentProcess.wsdl from TopperstudentProject.

Step 31: Copy concreate ProcessStudentProcess.wsdl from TopperStudentProject as shown

below

Step 32: Paste it inside TopperStudentOneWayProject



29/80

Step 33: Click refresh button & u can see ur copied wsdl inside TopperStudentOnewayproject



30/80

Step 34: Open bpel process &right click anywhere on partner link portion ,select Create

PartnerLink

Step 35: Fill all required field as shown below & click OK



31/80

Step 36: Created Partner Link Successfully

Step 37:Here observe that the wiring betweenTopperstudentOneWayProcess &

ProcessStudentReference



32/80

Step 38: Drag & Drop Invoke Activity Inside While Activity & click on it to edit

Step 39: Fill all required Blanks as shown below :



33/80

Step 40: Drag & drop Assign Activity & rename it as below :



34/80

Step 41: Assign Invoke Input from input variables to ProcessStudentReference_InputVariables

as shown below :



35/80

Step 42: Also make changes on TopperStudentOneWayProcess.bpel in source mode & add

[$IndexVar] after Student everywhere as shown below :



36/80



37/80

step 43: Drag & drop Switch activity from component palette& click on Condition

step 44: Click on Function icon to set switch condition



38/80

Step 45::Browse under BPEL Variables ProcessStudentRefence_OutputVariable ---> expandit & select Total --->Insert Into Expression ----> Browse under Functions-->AdvancedFunctions---> Logical Functions---> greater equals ----> Insert Into Expression----> Browse under BPELVariables TopMarks---> Insert Into Expression---->Click ok



39/80


40/80

Step 47: Drag & Drop Assign Activity & rename it as AssignTopMarks & click to edit it .

Step 48: Assign from ProcessStudentReference_OutputVariable then Total To TopMarks &click OK

Step 49: Click on TopperStudentOneWayProcess.xsd in source mode & register Student

namespace as shown below :



41/80

Step 50: In design mode create TopperStudent Element as stdobj: StudentResultType

Step 51: Open bpel process & click on , Create Variable TopperStudent ----> mark on

Element radio & browse by clicking on browse icon



42/80

Step 52: Select TopperStudent under Project Schema Files & click Ok

Step 53: Created TopperStudent variable



43/80

Step 54: Click again on assign TopMarks & edit it



44/80

Step 55: Assign output inside Topper Student from ProcessStudentReference_OutputVariable

to TopperStudent as shown below :



45/80

Step 56: Drag & drop Empty Activity & rename it as Donothing



46/80

Step 57: Drag & Drop Assign Activity & rename it as AssignIncrementIndex & click to edit it .

Step 58: Drag & drop expression into IndexVar

Step 59: Increment it by 1



47/80

Step 60: Drag & Drop Email Activity & rename it as EmailTopperStudent & click to edit it .

Step 61: Click fx icon for "To"



48/80

Step 62: Select Email under TopperStudent & Click insert into Expression



49/80

Step 63: Similarly browse for Subject & select Name under TopperStudent & Click insert into

Expression



50/80

Step 64: Similarly browse for Body & select client:Topperstudent under TopperStudent & Click

insert into Expression

Step 65: Diagnosis required input data & click ok



51/80

Step 66: Click on compile

Step 67: Build successful .



52/80

Compilation successful with 0 errors & 0 warnings .

Step 68: Create a new file for faultpolicy , Right click on desktop ---> Empty file



53/80

NOTE: We can also use notepad as text editor & save file as .xml to make it xml file .

Step 69: Open this file in Text Editor



54/80

Step 70: Write Fault policies as explained earlier



55/80



56/80

Step 71: Click on file & Save As

Step 72: Save as faultpolicy.xml (.xml extension ) ---> click save

Step 73: Now faultpolicy.xml file is successfully saved on desktop .



57/80

Step 74:Similarly write FaultPolicyBindings

Step 75: Click on file & Save As



58/80

Step 76: Save as faultbindings.xml (.xml extension ) ---> click save

Step 77: Now faultbindings.xml file is successfully saved on desktop .

Step 78: Copy both the files



59/80

Step 79: Paste these files inside TopperStudentOneWay Project

Step 80: Observe your recently pasted files inside TopperStudentOneWayProject



60/80

Step 81: Refresh twice or thrice , look faultbinding.xml & Faultpolicy.xml inside

TopperStudentOneWayProject .



61/80

Step 82: See faultbinding.xml in source mode inside j developer

Step 83: : See faultPolicy.xml in source mode inside j developer



62/80



63/80

Step 84::Deploy project by clicking TopperStudentOneWayProject to devsoa



64/80

Step 85: Build successfull

Deployed finished

Step 86: Click on Browser icon shown below:



65/80

Step 87: Start your enterprise manager by writing url http: //localhost:7001/em/

Note : Here localhost is application server & 7001 is a port in which enterprise manager isrunning.

Step 88 : Login using credentialsUser Name :weblogic

Password : welcome1click on login



66/80

Step 89: We have successfully login inside Enterprise manager 11g (Farm_dev_soa)we can clearly observe here that admin server is up & all deployment status is also up it meansthat our admin server is running .Now In left pane of window under Farm_dev_soa click on SOA radio button now again expand& under default we can easily see all the deployed projects. Click on ProcessStudent

Step 90: Shutdown ProcessStudent by clicking shutdown tab .



67/80

Step 91: Click yes

Step 92:Open TopperStudentOneWay composite & Click on test button



68/80

Step 93: Fill all the required fields & click Test WebService

Step 94: Since there is remote fault (system fault) hence bpel process catches faults &

displaying here as shown below :



69/80

Step 95: Open Flow trace & check that the fault is recoverable or not



70/80

Step 96: Come back to the instances & Click show details on BPEL Message Recovery Required

Warning & copy the ECID code & click ok .



71/80

Step 97: Go to the composite & same warning is available there so click on " Go TO BPEL

Recovery Console " also judge that the instance is in running state. It means fault policies are

working and system is retrying to recover fault .

Step 98: Click on Recovery & set duration All times ,ComponentName BPEL , ECID then click

below Conversation ID to select component then click on Recover



72/80

Step 99: It will ask to continue click YES



73/80

Step 100: Come to the Instances window & observe that total number of service retries are

five

Step 101: Click on Deployed Composites & see how many composites & services are up So

since here Process Student Process composite is down so for this reason it showing remote

fault . Click on ProcessStudentProcess



74/80

Step 102: Click on Start Up .



75/80

Step 103: Click YES



76/80

Step 104: Click again on TopperStudentOneWayProject & Click on Test

Step 105:

: Fill all the required fields & click Test WebService



77/80

Step 106: Since ProcessStudentProcess Composite is up & hence remote fault is recovered

after five retries now all the instance are in completed state with no faults .



78/80

Step 107: Open Flow Trace 7 now there are no fault found .



79/80

Step 108: See the notification send through email activity after five retries & then retries

failure invokes admin through fault policies

Step 109: Shut Down the Topper Student One Way Project Composite



80/80

Step 110: Shut Down Confirmation

getting started with oracle soa x doc

Documents