Skip to main content

I often see software developers getting pressed to get things done quickly and efficiently as possible. This takes a step back to see how developers can work more efficiently as individuals and as part of a team.

Imagine your SOA/BPM application is consuming a service (internal or third party) that takes more than 5 minutes to reply, which is more than the default JTA timeout. What would happen in this situation? The result is a faulted instance.

Documentation. Hardly anybody wants to write it, but it is one of the most important deliverables in a software project. Without documentation, it becomes very difficult to understand why things were done the way they were and if the project is operating as expected. 

Best practices for interfacing Java to external systems through Oracle BPEL components.

To remain competitive, companies have to continually drive down costs while maintaining value in the products and services they offer. One area where companies look to reduce costs is in Business Process Management (BPM).

When it comes to IT expenditures, some companies may invest a small fortune in BPM, while others may simply rely on basic tools, such as spreadsheets and Post-it notes. Regardless of the amount spent, if the tools are hard to use or the process is cumbersome then your business has become shackled and is wasting time and energy.

Back in mid-2014, Oracle was releasing Oracle BPM 11g Bundle Patch 3 and with it, the first version of its BPM REST APIs. That first cut was a good starting point, but it just offered a limited amount of functionality (find my previous post here). In this post, we’ll take a look at the BPM REST APIs version, released in August 2016, and see how they evolved after 2 years. 

The BPMN complex gateway's functionality can be duplicated in Oracle PCS using a multi-instance subprocess modeling pattern. 
Instead of using the default process swimlane Application Roles to assign a task to people, the Oracle Integration Cloud's Process Cloud Service (PCS) processes can be made more flexible and reusable when a User task in a process is set to be performed by different people dynamically. 
This blog explains why some exceptions are not caught by the error boundary events in PCS and why this is not necessarily a bad thing.
The 4-Eyes Principle is the term used when you want to insure that a task is approved by more than one person. This blog explains how excluding previous lane participants from approving tasks in a process that they approved upstream is done differently in Oracle BPM 12c processes than it was in 11g.
Subscribe to BPM