Feeds:
Posts
Comments

Archive for the ‘Development’ Category

In this post I will show how to create and deploy your composite with a simple BPEL process. The main goal is to describe the deployment process in the local SOA environment. The steps are very simple and almost the same as in 11g version.
If you haven’t yet install the environment or started the server, go to my previous post Oracle SOA Suite 12c Installation.

For this post I’ve create a SOA application with new project, and selected a BPEL component:

SOA 12c New Application

Create SOA Application - Step 2 of 3

Create SOA Application - Step 3 of 3

(more…)

Read Full Post »

While trying to run a deployed composite you are getting the below error:

java.lang.Exception: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: oracle.fabric.common.PolicyEnforcementException: PolicySet Invalid: WSM-02557 oracle.wsm.policymanager.accessor.BeanAccessor The documents required to configure the Oracle Web Services Manager runtime have not been retrieved from the Policy Manager application (wsm-pm), possibly because the application is not running or has not been deployed in the environment. The query “&(policysets:global/%)(@appliesTo~=”WS-Client()”)” is queued for later retrieval. at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:813) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:385) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:302)

This error is a bit tricky because you might consider it as a bug.
There are 2 possible reasons for this error:

  1. Mismatch or missing listen address in the Admin/Managed server.
  2. The local host(pc) name is different than the host name you’ve defined while installing SOA Suite (or other Middleware components).
    You can see example for that while trying to test you processHost

Both reasons causes the server to NOT listen the correct address.
The solution, is to update the host name listen address under the installed Admin/Managed servers:
Go to WL console -> Environment -> Servers -> Under the configuration tab click the Admin server -> fill the Listen Address.
Repeat it for all other managed servers, and restart the servers.

Note: If there is a mismatch between your host and PC name, you might consider to fill out the local host IP address and not the DNS.

Good Luck

Read Full Post »

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 »

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 »

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 »