{"id":2708,"date":"2011-07-18T10:21:17","date_gmt":"2011-07-18T15:21:17","guid":{"rendered":"http:\/\/jianmingli.com\/wp\/?p=2708"},"modified":"2015-04-17T13:56:35","modified_gmt":"2015-04-17T18:56:35","slug":"soa-11g-tutorial-policy-based-fault-handling","status":"publish","type":"post","link":"https:\/\/jianmingli.com\/wp\/?p=2708","title":{"rendered":"SOA 11g Tutorial: Policy Based Fault Handling"},"content":{"rendered":"

This is part of the Oracle SOA11g hands on tutorials<\/a>.<\/p>\n

Overview<\/h2><\/span>\n

* See this post<\/a><\/p>\n

Fault Types<\/h3><\/span>\n

System Faults<\/h4><\/span>\n

* Examples
\n– Service not available
\n– Network failure<\/p>\n

Business Faults<\/h4><\/span>\n

* Examples
\n– Invalid data
\n– Violation of business rules<\/p>\n

Fault Handling Policies<\/h3><\/span>\n

* They are attached to composite.
\n* They are not defined in code.<\/p>\n

Define a Policy<\/h3><\/span>\n

* Fault policies are defined in a file called fault-policies.xml.
\n* Fault policies are attached to composite via a binding file called fault-bindings.xml.
\n* A fault policy consists of:
\n– Fault policy name
\n– A list of faults
\n– A set of fault conditions
\n– A set of fault recovery actions<\/p>\n

Simulate Service Unavailable<\/h2><\/span>\n

Shutdown validateioniForCC Service<\/h3><\/span>\n

* Login EM
\n* Click validationForCC application (SOA -> soa-infra -> default -> validationForCC[1.0])
\n* On right panel, click Shut Down… button and click yes button on confirmation dialog.<\/p>\n

Test POProcessing App<\/h3><\/span>\n

* Input message<\/p>\n

\r\n\r\n    \r\n        \r\n            1111<\/ns1:CustID>\r\n            2222<\/ns1:ID>\r\n            iPod shuffle<\/ns1:productName>\r\n            Electronics<\/ns1:itemType>\r\n            145<\/ns1:price>\r\n            30<\/ns1:quantity>\r\n            Initial<\/ns1:status>\r\n            Mastercard<\/ns1:ccType>\r\n            1234-1234-1234-1234<\/ns1:ccNumber>\r\n        <\/ns1:PurchaseOrder>\r\n    <\/soap:Body>\r\n<\/soap:Envelope>\r\n<\/pre>\n
* Click Launch Flow Trace button to see the message flow.<\/p>\n
\r\nFaulted while invoking operation \"execute\" on provider \"getCreditCardStatus\". \r\n<\/pre>\n
Create a Fault Policy<\/h3><\/span>\n
* Create a new XML file named fault-policies.xml in POProcessing application:<\/p>\n
\r\n\r\n\r\n  \r\n    \r\n      \r\n         \r\n        \r\n            \r\n       <\/condition>\r\n    <\/faultName>\r\n      \r\n     \r\n     \r\n     \r\n          \r\n    <\/Conditions>\r\n    \r\n    \r\n      \r\n      \r\n      \r\n      \r\n        \r\n          \r\n        <\/javaAction>\r\n      <\/Action>\r\n      \r\n      \r\n      \r\n        \r\n          4<\/retryCount>\r\n          2<\/retryInterval>\r\n          \r\n        <\/retry>\r\n      <\/Action>\r\n      \r\n      \r\n      \r\n        \r\n      <\/Action>\r\n      \r\n      \r\n      \r\n        \r\n      <\/Action>\r\n      \r\n      \r\n      \r\n        \r\n      <\/Action>\r\n      \r\n    <\/Actions>\r\n    \r\n    \r\n    \r\n      \r\n      \r\n        myfaulthandler.log<\/property>\r\n        c:\\po\\log<\/property>\r\n      <\/propertySet>\r\n      \r\n      \r\n\r\n    <\/Properties>\r\n  <\/faultPolicy>\r\n<\/faultPolicies>\r\n<\/pre>\n
* Create a new XML file named fault-bindings.xml in POProcessing application. This file binds POProcessingFaults policy to composite.xml since they reside in the same directory.<\/p>\n
\r\n\r\n\r\n  \r\n<\/faultPolicyBindings>\r\n<\/pre>\n
* Handle all remoteFault occurrences<\/p>\n
\r\n     \r\n    \r\n        \r\n   <\/condition>\r\n<\/faultName>\r\n<\/pre>\n
Test Fault Policy<\/h3><\/span>\n
* Redeploy POProcessing application
\n* Retry test input xml fle
\n* Click Launch Flow Trace button to see the message flow.<\/p>\n
\r\n[FAULT RECOVERY] Marked Invoke activity as \"pending manual recovery\".\r\n<\/pre>\n
Manual Recover<\/h3><\/span>\n
* Start validationForCC application<\/p>\n
Retry<\/h3><\/span>\n
* Click on last POProcessing instance ID to open flow trace page.
\n* Click approveLargeOrder BPEL process
\n* Click Fault tab
\n* Click on the row containing the previous fault.
\n* Click Recover button
\n* Click on Yes on confirmation dialog
\n* Check that process is recovered.<\/p>\n
Handle BPEL Exceptions<\/h2><\/span>\n
* Simulate credit card validation application error.
\n* Learn how to handle BPEL exception.<\/p>\n
Create VALIDATECC Stored Function<\/h3><\/span>\n
* Login Oracle database as soademo
\n* Run the following script:<\/p>\n
\r\ncreate or replace FUNCTION VALIDATECC(cc_number IN VARCHAR2) \r\nRETURN VARCHAR2 AS\r\n    l_status  CREDITCARDINFO.STATUS%TYPE;\r\nBEGIN\r\n     select status\r\n     into  l_status\r\n     from   creditcardinfo\r\n     where  ccnumber = cc_number;\r\n     RETURN l_status;\r\nEXCEPTION\r\n      WHEN NO_DATA_FOUND THEN\r\n          raise_application_error(-20001, 'UNKNOWN CREDIT CARD');\r\nEND VALIDATECC;\r\n\/\r\n<\/pre>\n
Create a New DB Adapter: validateCC<\/h3><\/span>\n
* Open ValidationForCC application
\n* Open composite.xml
\n* Drag and drop a Database Adapter onto External References lane.
\n* Configure db adapter with following values:
\n– Service Name: validateCC
\n– Connection: soademoDatabase
\n– Schema: select SOADEMO
\n– JNDI Name: eis\/DB\/soademoDatabase
\n– Operation Type: Call a Stored Procedure or Function
\n– Procedure: Browse and select VALIDATECC<\/p>\n
Wire up RouteRequest to validateCC Database Adapter<\/h3><\/span>\n
* Wire RouteRequest mediator component to validateCC database adapter.
\n* Open RouteRequest mediator by double clicking it.
\n* Add a filter for getCreditValidation::getCreditValidationSelect to route all requests whose credit card numbers don’t<\/strong> start with 2.<\/p>\n
\r\nnot(starts-with($in.creditcardStatusRequestPart\/inp1:creditcardStatusRequest\/inp1:CCNumber, '2'))\r\n<\/pre>\n
* Add a filter for validateCC::validateCC to route all requests whose credit card numbers do<\/strong> start with 2.<\/p>\n
\r\nstarts-with($in.creditcardStatusRequestPart\/inp1:creditcardStatusRequest\/inp1:CCNumber, '2')\r\n<\/pre>\n
* Create a new transformation for validateCC route. Map inp1:CCNumber to db:CC_NUMBER
\n*Save all<\/p>\n
Test<\/h3><\/span>\n
* Redeploy validationForCC application.
\n* Test with credit card number  1234-1234-1234-1234. Should return VALID status.
\n* Test with credit card number  2234-1234-1234-1234. Should get UNKNOWN CREDIT CARD exception.<\/p>\n
\r\n...\r\nCause: java.sql.SQLException: ORA-20001: UNKNOWN CREDIT CARD\r\n...\r\n<\/pre>\n
Handle Application Error in BPEL<\/h3><\/span>\n
Add a Scope Fault Catcher<\/h4><\/span>\n
* Open POProcessing composite.xml file.
\n* Open approvelargeOrder BPEL process by double clicking it.
\n* Add a new scope activity under assignCCNumber and above invokeCCStatusService. Rename it to checkCC (double clicking it to set value).
\n* Move invokeCCStatusService into the scope.
\n* On the new scope’s left side vertical bar, click the Add Catch icon (third one from top) to add a Catch branch.
\n* Double click Catch icon to bring up the Catch dialog.
\n– Click the magnifying glass inside Fault Name panel, browse to System Faults -> BindingFault.
\n~ Namespace URI: http:\/\/schemas.oracle.com\/bpel\/extension
\n~ Local Part: bindingFault
\n– Click green plus sign to the right of Fault Variable to bring up the Create Variable dialog. Accept all default name.
\n~ Fault Variable: FaultVar
\n– Click OK
\n* Drop a Switch activity inside the catch block.
\n* Click new switch activity’s condition block and enter
\n– Label: InvalidCreditCard
\n– Condition: bpws:getVariableData(‘FaultVar’)  = ‘20001’
\n* Add an Assign activity inside InvalidCreditCard branch. Name it AssignUnknownCC.
\n* Assign ‘UNKNOWN CC’ string to  invokeCCStatusService_execute_OutputVariable -> creditCardStatusPart -> creditcardStatus.
\n* Drag and drop a Throw activity in the otherwise block. Name it Throw_Binding_Fault.
\n* Double click Throw icon to bring up the Throw dialog.
\n– Click the magnifying glass inside Fault QName panel, browse to System Faults -> BindingFault.
\n~ Namespace URI: http:\/\/schemas.oracle.com\/bpel\/extension
\n~ Local Part: bindingFault
\n– Click magnifying glass sign to the right of Fault Variable and select previously created FaultVar variable.
\n~ Fault Variable: FaultVar
\n– Click OK
\n* Save all<\/p>\n
Configure fault-policies.xml to Catch Fault Code<\/h4><\/span>\n
* Open fault-policies.xml and add to conditions block:<\/p>\n
\r\n       \r\n           \r\n                   \r\n                  $fault.code=\"20001\"<\/test> \r\n                   \r\n          <\/condition> \r\n      <\/faultName>\r\n<\/pre>\n
Test BPEL Fault Catcher<\/h4><\/span>\n
* Redeploy POProcessing application.
\n* Input message (note that credit card number stats with 2):<\/p>\n
\r\n\r\n    \r\n        \r\n            1111<\/ns1:CustID>\r\n            2222<\/ns1:ID>\r\n            iPod shuffle<\/ns1:productName>\r\n            Electronics<\/ns1:itemType>\r\n            145<\/ns1:price>\r\n            30<\/ns1:quantity>\r\n            Initial<\/ns1:status>\r\n            Mastercard<\/ns1:ccType>\r\n            2234-1234-1234-1234<\/ns1:ccNumber>\r\n        <\/ns1:PurchaseOrder>\r\n    <\/soap:Body>\r\n<\/soap:Envelope>\r\n<\/pre>\n
* Click Launch Flow Trace button to see the message flow.<\/p>\n
\r\nFaulted while invoking operation \"execute\" on provider \"getCreditCardStatus\". \r\n<\/pre>\n
Errors<\/h2><\/span>\n
{http:\/\/schemas.oracle.com\/bpel\/extension}bindingFault not defined<\/h3><\/span>\n
* BPEL compiler error:<\/p>\n
\r\nWSDL messageType \"{http:\/\/schemas.oracle.com\/bpel\/extension}bindingFault\" of variable \"CheckCCFaultVar\" is not defined in any of the WSDL files\r\n<\/pre>\n
* Possible cause:
\nFault variable CheckCCFaultVar was auto-generated from Catch diaglog.
\n* Fix:
\nRedefine CheckCCFaultVar variable:
\n– Locate CheckCCFaultVar variable.
\n– Double click it to open the Edit Variable dialog.
\n– Click magnifying glass icon to the right of Message Type field.
\n– Click Import WSDL File… icon on the upper right corner of Type Choose dialog.
\n– Click the magnifying glass search icon on the import WSDL file dialog.
\n– Browse to RuntimeFault.wsdl file in the C:\\Oracle\\Middleware\\jdeveloper\\integration\\seed\\soa\\shared\\bpel directory.
\n– Click OK
\n– Check Copy to Project and click OK on import WSDL file dialog.
\n– Click OK on Localize Files dialog.<\/p>\n
Custom Java Fault Handler<\/h2><\/span>\n
Create Custom Java Fault Handler<\/h3><\/span>\n
\r\npublic class MyFaultHandler implements IFaultRecoveryJavaClass {\r\n    public MyFaultHandler() {\r\n        super();\r\n    }\r\n\r\n    public void handleRetrySuccess(IFaultRecoveryContext ifc) {\r\n        ...\r\n    }\r\n\r\n    public String handleFault(IFaultRecoveryContext ifc) {\r\n        ...\r\n    }\r\n\r\n<\/pre>\n
Install Custom Java Fault Handler<\/h3><\/span>\n
* Copy myfalthandler.jar to soa domain lib direcotry: \/opt\/oracle\/Middleware\/home_11gr1\/user_projects\/domains\/soa_domain\/lib
\n* Restart soa server<\/p>\n
Use Custom Java Handler<\/h3><\/span>\n
* Modify fault-policies.xml
\n– Add condition to use custom handler<\/p>\n
\r\n    \r\n         \r\n        \r\n            \r\n       <\/condition>\r\n    <\/faultName>\r\n...\r\n<\/pre>\n
– Define custom action:<\/p>\n
\r\n    \r\n      \r\n      \r\n        \r\n          \r\n        <\/javaAction>\r\n      <\/Action>\r\n...\r\n<\/pre>\n
– Set custom handler properties:<\/p>\n
\r\n    \r\n      \r\n      \r\n        myfaulthandler.log<\/property>\r\n        \/tmp\/po\/log<\/property>\r\n      <\/propertySet>\r\n...\r\n<\/pre>\n
Test<\/h3><\/span>\n
* Redeploy
\n* Test with input message<\/p>\n
\r\n\r\n    \r\n        \r\n            1111<\/ns1:CustID>\r\n            2222<\/ns1:ID>\r\n            iPod shuffle<\/ns1:productName>\r\n            Electronics<\/ns1:itemType>\r\n            145<\/ns1:price>\r\n            30<\/ns1:quantity>\r\n            Initial<\/ns1:status>\r\n            Mastercard<\/ns1:ccType>\r\n            2234-1234-1234-1234<\/ns1:ccNumber>\r\n        <\/ns1:PurchaseOrder>\r\n    <\/soap:Body>\r\n<\/soap:Envelope>\r\n<\/pre>\n
* Check log file at \/tmp\/po\/log\/myfaulthandler.log<\/p>\n
Handle Mediator Faults<\/h2><\/span>\n
* Policy based fault handler is the only way to catch and handle mediator exceptions.<\/p>\n
Configure Fault Policy for Mediator<\/h3><\/span>\n
* Add to fault-policies.xml
\n– Add condition to use custom handler<\/p>\n
\r\n    \r\n      \r\n        \r\n          \r\n        <\/condition>\r\n      <\/faultName>\r\n...\r\n<\/pre>\n
– Define mediator fault action:<\/p>\n
\r\n    \r\n      \r\n        \r\n          \r\n          <\/returnValue>\r\n        <\/javaAction>\r\n      <\/Action>\r\n...\r\n<\/pre>\n
– Set mediator handler properties:<\/p>\n
\r\n    \r\n      \r\n      \r\n         mediator- faults. log<\/property>\r\n        \/tmp\/po\/log<\/property>\r\n      <\/propertySet>\r\n...\r\n<\/pre>\n
Configure Mediator Component<\/h3><\/span>\n
* Open routePO mediator component (routePO.mplan)
\n* Change price * quantity < 1000 route from sequential to parallel. This is needed in order for fault policy handler to intercept the exception.\n\n\n\n
Test<\/h3><\/span>\n
* Redeploy POProcessing
\n* make log directory un-writable: chmod -w \/tmp\/po
\n* Test with input message that has price * quantity < 1000\n\n\n
\r\n\r\n    \r\n        \r\n            1111<\/ns1:CustID>\r\n            2222<\/ns1:ID>\r\n            iPod shuffle<\/ns1:productName>\r\n            Electronics<\/ns1:itemType>\r\n            145<\/ns1:price>\r\n            30<\/ns1:quantity>\r\n            Initial<\/ns1:status>\r\n            Mastercard<\/ns1:ccType>\r\n            1234-1234-1234-1234<\/ns1:ccNumber>\r\n        <\/ns1:PurchaseOrder>\r\n    <\/soap:Body>\r\n<\/soap:Envelope>\r\n<\/pre>\n
* Check log file at \/tmp\/po\/log\/mediator- faults. log<\/p>\n","protected":false},"excerpt":{"rendered":"
This is part of the Oracle SOA11g hands on tutorials. Overview * See this post Fault Types System Faults * Examples – Service not available – Network failure Business Faults * Examples – Invalid data – Violation of business rules … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[100],"tags":[],"class_list":["post-2708","post","type-post","status-publish","format-standard","hentry","category-soa11g"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p8cRUO-HG","_links":{"self":[{"href":"https:\/\/jianmingli.com\/wp\/index.php?rest_route=\/wp\/v2\/posts\/2708","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jianmingli.com\/wp\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jianmingli.com\/wp\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jianmingli.com\/wp\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/jianmingli.com\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2708"}],"version-history":[{"count":12,"href":"https:\/\/jianmingli.com\/wp\/index.php?rest_route=\/wp\/v2\/posts\/2708\/revisions"}],"predecessor-version":[{"id":10657,"href":"https:\/\/jianmingli.com\/wp\/index.php?rest_route=\/wp\/v2\/posts\/2708\/revisions\/10657"}],"wp:attachment":[{"href":"https:\/\/jianmingli.com\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2708"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jianmingli.com\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2708"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jianmingli.com\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2708"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}