Archive for the ‘Enterprise Manager’ 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


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 »

The following steps describes how to create a JNDI location so you can use it later on your DbAdapter
(The configuration is done on Oracle EM 10g( Application Server Control):

1. Create a Connection Pool

In the EM click on your OC4J server (where Bpel PM exists in):





Read Full Post »

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:


Read Full Post »

When running a bpel processes, you can sometimes end up with a fault state.
Later on, from “unknown reason” you see the faulted process being initiate again, and being run from the beginning.


Read Full Post »