22Five Tools for Debugging Oracle SOA Suite
by Adam Mead 1/22/15
Have you ever completed a software project and had nothing go wrong? Neither have I. Projects using Oracle’s SOA Suite are no different than Java projects and you will need to debug issues at some point. Here are five tools for debugging issues on Oracle SOA Suite: 1. Flow Trace and Audit Trail If you have an issue with a specific instance, or instances that follow a specific path, both the flow trace of the composite instance and audit trail of the component instances are extremely helpful. Flow traces and audit trails help you pinpoint a location to look in your code. You can look at the location of the error and step back through the flow trace and audit trail from that point to trace back to the cause of the issue.
22BPM 11g - Using two dates to calculate and implement a SLA
by Suyash Khot 1/22/15
A very common use case for using an SLA (Service Level Agreement) is when there is a start date-time (not necessarily the current date-time) and an end date-time and you want to use the time difference between those two dates as your SLA in your BPM process. In the good old BPM 10g days you could do that easily. You could take the two dates and subtract one from the other and the result could be used as a SLA value. Unfortunately, the same cannot be done in BPM 11g as easily but we do have a solution.
15Why your Initiator Task is not Visible in the Oracle BPM Workspace
by Dan Atwood 1/15/15
Everyone getting started with Oracle BPM struggles getting the link for a process's Initiator task to appear in the Workspace's Applications tab at one time or another. This short video goes over the six (ok - really seven) most common reasons that this occurs and how each is resolved.
13Decoupling Oracle BPM Process Instance Information
by Dan Atwood 1/13/15
Separating Oracle BPM business processes from their underlying data is a topic that comes up regularly with customers. When first starting out, most customers create a large set of process data objects that carry the payload of each work item instance throughout the life of a process and its subprocesses. While it is tempting to begin this way, the work item instance process data should be kept light by storing an ID field that can be used to look up information from a relational database when it is needed. What Information Should be Stored in the Process Instance’s Payload Although you should always strive to keep the process instance’s payload small, you can go overboard. Each work item instance should contain variables that provide:
06Message Aggregation in Oracle SOA Suite 12c
by Jennie DeRosa 1/6/15
Within the Oracle SOA Suite, message aggregation is a concept that allows for multiple messages to be routed to the same BPEL process, based on a value(s) defined within the incoming payload. This is implemented within BPEL through the use of correlation sets. To implement this, a correlation set is defined and will contain one or more properties. These properties have aliases to values within the input payload message (i.e. PurchaseOrderNumber), which are used for the correlation of messages.