PaaS Partner Community

  • July 15, 2015

Managing Idempotence in SOA Suite by Waslley Souza

Juergen Kress
PaaS Partner Adoption

clip_image002According to the SOA Suite 12c documentation, an idempotent activity is an activity that can be safely retried. It means if your BPEL Process fails, a rollback operation will be executed and all data won’t be persisted in the database. OK, but sometimes you want to persist some data even your BPEL Process fails. How can you achieve it? Set the operation as nonidempotent and the Dehydration will occur after this operation. In this post, you will learn how to set an operation as nonidempotent. As a starting point, let’s use the application created here: Using DB Adapter in SOA Suite 12c. We will add a new Database Adapter to manage the jobs table, and when we try to add a new employee with a new job, the job will be persisted even if the BPEL Process fails. Download the sample application: SOAIdempotentApp.zip. Open the EmployeeProject file. To create the Database Adapter, right-click External References section, and choose Insert > Database. In Step 1, set the name as JOBSDbReference and click Next. hIn Step 2, choose the Database Connection, set the JNDI Name and click Next. In Step 3, choose Insert Only and Select By Primary Key options, and click Next. Read the complete article here. SOA & BPM Partner Community For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center. Blog Twitter LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.