Friday, 25 May 2012

Variable transformation

Problem: When you try to perform a transformation between two variables that are declared like simpleType the you will receive a message:

"Enable to get schema information for source"

Solution: Define an element of the type that you want on the XSD and then declare the variable of that defined type. i.e:

On XSD add these elements:

        <element name="var1" type="string"/>
        <element name="var2" type="string"/>

Create the variables with correspondent Element Type..

try to do the transformation and should work.

Friday, 4 May 2012

Webcenter automated deployment using ant

Webcenter automated deployment is not compatible yet with ojdeploy.

So it will be necessary to use WLST deploy. For that we can use an ant script to call a wlst script file (py) to prepare the mds application


1. Create a file as below:


def deployAll():
     print 'TESTING!'
     archive = getMDSArchiveConfig(='C:/wcportal-1.0.ear')

# Deploy script init

    print "Unexpected error: ", sys.exc_info()[0]

2. Change the build.xml file as below:

<target name="deploy" description="deploy" >
<exec executable="${ofm.home}/oracle_common/common/bin/" spawn="false" failonerror="true">
<arg value="/refresh/oracle/testcases/ant_test/"/>
<arg value="${earlocation}"/>
<arg value="${wc.mds.repository}"/>
<arg value="${}"/>
<arg value="${wc.mds.repository.type}"/>
<arg value="${wc.mds.repository.jndi}"/>
<arg value="${wls.username}"/>
<arg value="${wls.password}"/>
<arg value="${wls.server}"/>

Thursday, 3 May 2012

Setting up Active Directory Lightweight Directory Service as a Weblogic Authentication Provider

One more fantastic white-papper, now about how to configure BPM to use multiple identity providers. The BPM's libOVD its used as a lightweight directory service.

Functional Testing and Loop Request

To archive such needs use test soapUI capabilities.

In that project there’s included a test case that can be configured to insert n users defined in a properties file.

The script will then create n user joining n to user id (i.e. j.doe23).

To be able to execute this step perform  the following steps:

1.       Edit service endpoint
2.       Expand testsuite existant inside testcase SoapUI project
3.       Expand Test Steps
4.       Double-Click CreateUserProperties
5.       Change the properties according to your needs and saves to the selected properties target file
6.       Double-clicktest-case
7.       Select Run this Test Case (Green play button on left top corner of click test-case)

NOTE: To implement WSSecurity Header on request please change CreateUserRequest test step on test-case.

Groovy code snipped to perform a loop request

// run ten random requests"In the BC2 Create User Setup Script")

def userIdInStep = testRunner.testCase.getTestStepByName( "CreateUserProperties" )
def firstName = userIdInStep.getPropertyValue( "FirstName" )
def lastName = userIdInStep.getPropertyValue( "LastName" )
def userId = userIdInStep.getPropertyValue( "userId" )
def nTests = userIdInStep.getPropertyValue( "UsersToCreate" )"Number total of tests: " + nTests)"Company Mkey: " + nTests)"Company Address MKey: " + nTests)

def groovyUtils = new

for( i in 1..nTests.toInteger())
  def holder = groovyUtils.getXmlHolder( "CreateUserRequest#Request" )
  holder.setNodeValue( "//urn:userId", userId + i)
  holder.setNodeValue( "//urn:lastName", lastName + i)
  node = holder.getNodeValue("//urn:userId") ("Created user: " + node)
  node = holder.getNodeValue("//urn:lastName") ("Created user last name: " + node)

To use properties directely on request xml


Tuesday, 24 April 2012

Maven: Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to deploy artifacts/metadata: No connector available to access repository snapshots

Running maven the access to your local repository is inaccessible. Somehow it can't be accesses by Maven to copy the artifacts.

Verify that you have file: protocol defined on repository path on maven/conf/setting.xml file:


Wednesday, 21 March 2012

Using Ant the project doesn't compile


When using ant and deploying using OjDeploy the project doesn't compile and generates an empty JAR. Even when parameter nocompile=false.


In this case, setting the flag nocompile to false is not enought. It is necessary to be sure that the parameter is not on this ojdeploy target.

Thursday, 15 March 2012

Error in getting XML input stream: file after adding Business Rule


After adding a Business Rule with service interface I got:

Error: Error in getting XML input stream: file:/D:/PATH/ing/xsd/this.xsd:  D:/PATH/ing/xsd/this.xsd (The system cannot find the path specified) among a great quantity of exceptions on the project when compiled.


Check the WSDL for the service interface. It is pointing to a wrong location /ing/

Performance and Tunning Guide for 11g

Oracle Official Guide for tunning SOA environments

Wednesday, 14 March 2012

Could not find registry for the application _JBOServiceRegistry


When using  ADF-BCon your composites you have to specify the registry service used to registry the bc. So for that you have to provide on the reference the <app-name>__JBOServiceRegistry.

The application name can be found on the application deployment profile of the sdo project.

When running the composite, if you get "Could not find registry for the <aap-name>_JBOServiceRegistry"


In your weblogic-application.xml of the SDO application, make sure you added the JBO listener:


Now you are able to register the application on JBO listener

Thursday, 8 March 2012

OER Error when using Assets Editor or Import/Export external tool


Accessing the assets editor or import/export client of OER it is necessary to download jnpl files to java web start initiate the necessary applications. Sometimes, the jnpl files cannot access the hosted jar files. Connection refused: connect

at Source)
at Source)

or Unable to load resource: http://localhost:7101/oer-web/webstart/impexp/client.importtool-
at Source)
at Source)
at Source)
at Source)
at Source)
at Source)
at com.sun.javaws.LaunchDownload$ Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$ Source)
at Source)


Edit the impexp.jnlp or registrartool.jnlp download files to reference the host name instead of localhost or other non reachable host.

Oracle Enterprise Repository 11.1.6

Error after refactoring BPM project

“<Feb 18, 2012 12:56:26 PM EET> <Error> <> <BEA-000000> <<.> Invalid task definition.
The task definition at default/This!1.0*soa_f7aa9b39-1458-41c2-9c78-8b6de5f875a6/ThisHT could not be read. The task definition is associated with workflow defa
Make sure that the task definition is available at the specified URL and that it is a valid XML document.”


1.       Log to soainfra schema
2.       Check in BPM_CUBE_PROCESS for record with the PROCESSNAME equals to the process and STATUS = 1
3.       Change the status to -1 for all these records
4.       Redeploy

Best practice document

Start Small, Grow Fast

by Edwin Biemond, Ronald van Luttikhuizen, and Demed L'Her
A set of pragmatic best practices for deploying a simple and sound SOA footprint that can grow with business demand.

Wednesday, 7 March 2012

Events and sdo losing transactions


When triggering composites using events and on this composite there are transation management over SDO's some transactions are not commited


Be sure that the events have Consistency set to one and only one and no set on Run as Publisher.

SOA Suite:

Attaching policies using the configuration plan

It is possible to attach policies to composites or components on deployment time using configuration plans.

To do that:

<service name="bpelprocess1_client_ep">
<binding type="ws">
<attribute name="port">
<wsp:PolicyReference URI="oracle/wss_username_token_service_policy"
<wsp:PolicyReference URI="oracle/log_policy"

SOA Suite:

General Configuration Plan mixing endpoints


While using global config plan, the deployer is mixing endpoints


What makes the cfg_plan act like this was this entry on the file:

<!--Template repository path references-->
<reference name="*">
<property name="........
<!-- // -->

With this entry I was trying to attribute to all references the same configuration.

To avoid the unexpected behaviour described put all referencing of this kind after all references included on the configuration file.

Why sometimes we needed to add dehydration point after reply

Reply handling

We normally think of reply as causing the response to be sent back to the client, and if the transaction was initiated by the BPEL service engine, then it would be committed as part of the reply. In most cases, this is an accurate description of the end result, but this is not actually what happens. When a reply is reached, the response message is marked as available for returning to the requestor, but it is not returned to the requestor. Instead the BPEL engine will continue to process activities until it reaches a dehydration point. On reaching the dehydration point, the current thread (which was also the requesting thread) will return the reply message to the requestor. Note that this results in a delay in the returning of the result to the requestor, and it also causes the transaction scope to extend past the reply activity.

SOA Suite:

Tuesday, 6 March 2012

XSL code erase empty nodes, trim spces and normalize strings

XSLT code snippet to trim all spaces, normalize strings and erase all empty nodes.

<xsl:template match="node()">
<xsl:if test="count(descendant::text()[string-length(normalize-space(.))>0]|@*)">
<xsl:apply-templates select="@*|node()"/>

<xsl:template match="@*">

<xsl:template match="text()">
<xsl:value-of select="normalize-space(.)"/>

Deployment over different environments

Use ORAMDS for all XSD / WSDL files on the project (oramds:...) in all composite.xml and wrappers on location tag. Doing that you will garantee that you can deploy anywhere even when you don't have remote access to a environment. And in this way it is not necessary to change endpoints on composite.xml on compilation time (by script for instance)

then use configuration plans.

Deploying EJB using Worklist API

When deploying fro Jdev I got the error:

[EJB:011023]An error occurred while reading the deployment descriptor. The error was:
[11:57:04 AM] Caused by: java.lang.NoClassDefFoundError: oracle/bpel/services/workflow/task/model/Task


Be sure that you have a EJB JAR project deployment profile and a EAR Application Deployment Profile.

Add these library entry on weblogic-application.xml file accessible go on Application Resources view on Jdeveloper / descriptors / META-INF


Wednesday, 29 February 2012

Segmentation fault ./runInstaller $*

When deinstalling SOA Suite from Middleware I got:Segmentation fault ./runInstaller $*

The solution is to run the installer on Oracle_SOA/oui/bin with jreLoc option defined.

./runInstaller -deinstall -jreLoc /u01/app/oracle/product/Middleware/jdk1.6.0_31