• Tutorial
    • AWS
    • Oracle
    • WordPress
    • Azure DevOps
  • About me
Tutorial
    AWS
    Oracle
    Wordpress
    Azure DevOps
About me
cedricleruth - It's still magic even if you know how it's done
  • Tutorial
    • AWS
    • Oracle
    • WordPress
    • Azure DevOps
  • About me

How to implement a global retry fault policy in SOA BPEL?

Implementing a global common fault policy is essential when building a SOA BPEL Composites architecture. As your number of production BPEL instances grows, the risk of losing critical data due to a BPEL process crashing in production increases. Especially with large architecture where unexpected usage surge can trigger slowness and failures. Implementing a simple retry fault policy allows the faulted instances to continue once the environment returns to normal.

Implementing a global common fault policy is essential when building a SOA BPEL Composites architecture.

Below is an example of a simple retry global fault policy that will retry up to 7 days for any BPEL instances in error due to a technical issue. To do so, update those three files as follow :

Want to be notified when there is more?

Get in touch:

Categories

  • AWS EC2
  • AWS Lambda
  • AWS S3
  • AWS Tutorials
  • Azure DevOps
  • Highlight
  • IT Architecture
  • Oracle ADF
  • Oracle Database
  • Oracle SOA Suite
  • Oracle Tutorials
  • Route53
  • Tutorials
  • Weblogic
  • Wordpress Tutorials

Read more about:

ADF Apache AWS Bean binding bpel Certificate cli cloud convert Database Deployment EC2 ERROR Exception file First Value GIT HTTPS Icons IllegalStateException iterator Java Jdevelopper lambda Oracle Oracle ADF Performance php programmatically RichTable route53 row S3 script sendRedirectforward soa sql SSL table View Criteria View Object VO weblogic WordPress