SOA Suite | Oracle Fusion Middleware

Posts Tagged ‘SOA Suite’

Oracle SOA Suite 12c Installation

Posted in Installation, JDeveloper, SOA Suite, tagged 12c, Installation, oracle soa suite 12c, SOA Suite, weblogic domain on June 6, 2015| 1 Comment »

With the latest version of SOA/BPM Suite 12c (12.1.3), Oracle provides installations in 2 modes: Development and Production.
In the Development mode, and unlike previous versions, with 12c you can choose to download, install and run a complete environment on your local machine. All with only 1 installation file.
The production mode, on the other hand, includes full sets of components that allows you to set a production environment (or TEST/UAT).
In this post I will describe in few steps, how to download and install Oracle SOA suite 12c in development mode.

Please follow the next step in order to complete you Development environment preparation:

(more…)

Read Full Post »

The Use Of Variable In An XSL Code

Posted in Bpel, Development, tagged 10g, 11g, bpel, JDeveloper, Oracle SOA Suite, SOA Suite, transformation activity, xsl on January 10, 2013| Leave a Comment »

In this post I will explain how to add a variable into a XSL code. I will also explain why do we need it at all.
(This option exists on both Oracle SOA Suite 10g and 11g versions. Some of the screens might be a little bit different. Below I’ve attached print screens from 11g)

If you are using a transformation activity in your process, you probably need to do some mapping for multiple records data.
Like in other developing languages, there are cases where you want to declare a variable once, assign to it a value, and use it later on in your code.
When using xsl for mapping source to target, it is the same behavior.

Let’s take 2 scenarios:

(more…)

Read Full Post »

Improve EM Instances Load Performance

Posted in Bpel, Enterprise Manager, tagged bpel, composites, em, instances, Oracle SOA Suite, SOA, SOA Suite on December 10, 2012| Leave a Comment »

When dealing with large amount of instances (on one composite application or more), you can end up with slow performance
on the instances load.

I will describe, how a simple configuration can increase the performance for this issue.

Before, I would like to emphasize: performance issues on EM, can be caused from many reasons, like – wrong process plan, DB growth, lack of infra structure resources etc.
When planning processes, there is a need to take in a consideration, all of the parameters.

So, how to set those parameters – very simple:

(more…)

Read Full Post »

Adding A Custom Fault To A Bpel Process

Posted in Activities, Bpel, Development, tagged 10g, 11g, bpel, fault management, oracle, Oracle SOA Suite, SOA Suite, Throw Activity on November 3, 2012| 4 Comments »

When creating and planning bpel processes, you must always consider using Fault Management.
Bpel process management provides many options and ways to handle and manage fault.
Sometimes, there can be a requirement to throw a custom fault – one that does not exist in the built in system fault that is being provided in the Throw Activity list.
In this post I will describe how to do it, in the most simple way.
I created my example in SOA suite 11g (11.1.1.6), but that’s the way to go on all bpel versions.

(more…)

Read Full Post »

Error When Trying To Add New Message With XSD Simple Type Message Part

Posted in Bpel, Development, JDeveloper, tagged 11.1.1.5, 11.1.1.6.0, bpel, JDeveloper, message, message part, Oracle SOA Suite, SOA, SOA Suite, wsdl on October 13, 2012| 1 Comment »

While developing on JDeveloper 11.1.1.6 I’ve noticed a strange behavior, that I consider as a bug.
(I could find this problem also on 11.1.1.5 version, but not on previous versions)
When I tried to add another message type to my bpel component, I got a compilation error:

XML-20190: (Fatal Error) Whitespace required.

The above error was the main error, followed by other errors like:

Error(15,84): Cannot find Port Type “{http://xmlns.oracle.com/MyWorkBpel/Project3/BpelProcess1” for “project_client_ep” in WSDL Manager

The error was generated because my main bpel wsdl was corrupted.
The question now is what happened?!

(more…)

Read Full Post »