#bpel

The OpenAPI Specification OAS and its Open API Initiative (OAI)—the governing body—have been around for 10 years, and of course, OAS’s foundation, Swagger, has been around a lot longer. OpenAPI is very much a mature proposition. But the OAI community hasn’t stood still. Two standards have been developed, the first being Overlays and the latter being Arazzo. Overlays Overlays support the Arazzo…

Oracle BPEL Error: SOAPException: javax.xml.soap.SOAPException: Message send failed: Read timed out

  Received the following error in the Oracle BPEL composite. The BPEL Web Service adapter throws the following error while calling one of the Oracle Primavera Web Services.

    We have the following errors in the SOA_SERVER.OUT log file

    <Unable to dispatch request to

Process Auditor and Forecaster (PAF) is a tool that provides a graphical representation of workflow composites that are currently in progress and composites that are applicable in future. The various composites displayed in the PAF Dashboard include:

BPEL Process Components

Rule Decision Components

Human Task Components

With this solution in place, the user (workflow author or workflow tracker) can now perform following actions from the PAF Dashboard:

Monitor the Business Process progress: PAF Dashboard displays business processes have been completed, which steps are currently active and business processes that are yet to be triggered

Monitor and modify the Human Task assignment: PAF Dashboard displays the human tasks in its current state. The user has the option to fetch the entire task history for better clarity

Perform additional actions over these composites: PAF Dashboard empowers the user to perform additional viz. sending reminders, notifications, etc. for the designated composite.

Recover faulted Business Processes: PAF Dashboard has this unique feature for recovering faulted business processes, through this the user can perform custom recovery actions viz. retrigger, remove, etc.

Asynchronous interaction in Oracle BPEL and BPM. WS-Addressing and Correlation sets by Maarten Smeets

  There are different ways to achieve asynchronous interaction in Oracle SOA Suite. In this blog article, I’ll explain some differences between WS-Addressing and using correlation sets (in BPEL but also mostly valid for BPM). I’ll cover topics like how to put the Service Bus between calls, possible integration patterns and technical challenges.

I will also shortly describe recovery options. You…

How to terminate an instance after transaction rollback and return response to caller by Rajeev Misra

We have seen in several customer scenarios where a Parent BPEL process calls a child BPEL process asynchronously.  If child process runs into any kind of business or system fault,  fault handler sends callback to parent process with failure information.   Please note, since parent had invoked child process asynchronously,  child can’t throw fault back to parent.  Callback is only mechanism to…

Synchronizing databases through BPEL services by Lykle Thijssen

  Introduction

This blog post is about how to synchronize two databases through BPEL, focusing on transaction, rollback and fault handling.

During a project, I’ve encountered a situation where we wanted to migrate from an old database to a new one. However, in order to gradually move external systems from the old to the new database, it was required that both databases would be kept in sync for a…

BPEL-> Mediator -> BPEL: Passing Business Errors back thru Mediator by Niall Commiskey

  Scenario:

Sync BPEL1 calls Mediator that calls Sync BPEL2.

SyncBPEL2 throws a Business Error, Mediator needs to pass this back to SyncBPEL1.

In the following example I have the following components –

Sync BPEL 1 = BPELProcess3

Mediator = Route2BPEL1

Sync BPEL 2 = ErrorThrower

Here they are, in all their grandeur –

ErrorThrower

Note the explicit definition of the fault in the wsdl –

Read the…

Tornando um processo BPEL Síncrono para Assíncrono

Um processo BPEL pode ser Síncrono ou Assíncrono, apenas para entendimento vamos definir basicamente o que é um Processo BPEL Síncrono e um Processo BPEL Assíncrono: Um Processo BPEL Síncrono bloqueia o cliente (aquele que está usando o processo) até que o processo termine e retorne um resultado para o cliente. (more…)