My presentations at Oracle Open World 2012

Oracle Open world 2012 is already past and I’m back in Europe. Here is just a quick wrap up of my involvements at OOW 2012. 

Oracle Fusion Middleware Live Application Development (UGF10464)

For the fourth time, the Live FMW Application Development show has been held. This time at Oracle Open World 2012,  during the ADF EMG community event on Sunday organised by Chris Muir. I joined the team for the first time, as due to my injury in last december, I was not able to be part at UKOUG 2011. For three hours, we demonstrated the audience (around 100 participants) how an application can be created across the tiers – UI (ADF), Process (BPM), Service Integration (SOA Suite) and the Database. Because we had only one beamer available, we first presented for each tier how the development works and then in the second phase, we presented how some changes/addons can be applied to the 1st iteration. I was part of the Service Integration team, together with Ronald.

The slides of the show are available on slideshare. Only a few, the real value was of course in the live demo!

A photo of me and Ronald during Lucas introduction: 

IMG 2648

It was fun to be part of the team, hope we can repeat it soon somewhere else! Thanks to Lucas, Chris and Duncan for organising the show!

There were also some discussion about further using the material, such as some videos on youtube, writing an article series….

Effective Fault handling in SOA Suite 11g (CON4832)

In this co-presentation with Ronald van Luttikhuizen we presented how the built-in functionality of Oracle SOA Suite and Oracle Service Bus can help to implement fault handling and fault prevention. We used an example scenario, which is complex enough to show some real live problems in a service-oriented solution with a mix of services, technologies and platforms. 

Use case with possible fault szenarios

The session was pretty well attended, and with an extended Q&A sessions at the end. We got quite a lot of interesting questions and I even had to leave earlier, as I had my next presentation just after this one.  

The slides are available on slideshare. We are currently writing a series of articles which will dive deeper into the subjects of error handling and error prevention and show how the SOA Suite 11g platform can help. 

Five Cool use cases for the Spring component of Oracle SOA Suite (CON6210)

My last presentation at Open World 2012 was about the Spring component of the Oracle SOA Suite.

The Spring component makes it possible to embed Java code as a Service Component Architecture (SCA) first-class citizen through the Spring component implementation type. Thereby the coarse-grained components of Oracle SOA Suite (such as BPEL, Mediator) can be extended by much-finer-grained Spring beans wrapped inside the Spring component. The goal of the session was to show how and why you want to use the Spring component and to hopefully inspire attendees to use it for their own projects.

There is of course a question what “cool” means. Cool and practice-related doesn’t always match and of course I wanted to also show some use cases which are actually useful at daily work. 

It took me quite some time to put the use cases together and to make them working. Especially because I have not previously worked with some libraries/frameworks i have used. At the end I presented the following use cases:

  • Advanced Configuration through JMX
  • Dynamic Routing in SOA Suite (i.e. publish/subscribe)
  • Integration of MongoDB NoSQL database
  • Integration of Twitter to send update messages
  • Integration of Twitter to receive mentioned messages

As you can see on slide 40, I had some other ideas, but just not enough time to do them as well. Maybe I will do it for a session on another conference. 

The slides are available on slideshare. I have also planed to write some further blog articles, one for each use case I have presented and to show step by step how the use case can be implemented.


It was a lot of work to prepare the session, but enjoyed it! 

WebLogic Server, JDev, SOA, BPM, OSB and CEP (PS3) available!

Today 11R1 Patchset 3 of WebLogic Server, JDeveloper and ADF, Oracle SOA Suite, Oracle Service Bus (OSB) and Complex Event Processing (CEP) has been released!

The following links provide information about new features and bug fixes for the different products/components:

Here is my list of top new features:

  1. With Patchset 3 Oracle supports the IBM WebSphere platform!
    • Both Oracle ADF and Oracle SOA Suite can run on the IBM application server!
    • Will be interesting to see the impact of that!
  2. BPEL 2.0 is now supported in JDeveloper
    • The BPEL editor in JDeveloper now generates BPEL 2.0 code and introduces several new activities.
  3. BPEL got a new Assign activity dialog
    • New Assign Activity supports the same drag & drop paradigm used for the XSLT mapper
    • this greatly streamlines the task of assigning multiple variables
  4. Single JVM developer install
    • Oracle SOA Suite can now be targeted to the WebLogic admin server
    • there is no requirement to also have a managed server
    • Minimizes the memory footprint for development environments!
    • Possible before by manually intervening the setup of the domain, but now supported through a template.
  5. You can start downloading the software from the Oracle SOA Suite Download tab:

Expand “Prerequisites & Recommended Install Process” and you will see the links for the download of the single products.

Be prepared to download several GB of software, so you better be connected to a fast network!

Using the event API to publish an event to the Event Delivery Network (EDN) – the Spring way

The Event Delivery Network (EDN) in Oracle SOA Suite 11g provides a declarative way to use a publish/subscribe model to generate and consume business events without worrying about the underlying message infrastructure. Events can be published / subscribed from a variety of programming environments such as Java, PL/SQL, SOA Composites, and ADF-BC applications

In his blog Clemens showed how the Event API can be used to publish an event programmatically to the Event Delivery Network (EDN). I took the sample code Clemens provided and did some refactoring to make it more “Spring like”.

My idea is to use some of the features of the Spring Framework to simplify the publishing of Business Events to EDN from Java, without worrying about the details of the Java event API. The following features are of interest:

    The goal is to make publishing an Business Event to EDN from Java as simple as that:
// create a new customer
Customer cust = new Customer();

Address adr = new Address();
adr.setStreet("Papiermuehlestrasse 73");

// create a new customer event, passing the customer object as the payload
NewCustomerEvent event = new NewCustomerEvent(this, cust);

// publish the event through the Spring Event Handling mechanism

    We just use simple Java objects (POJOs) to create an event and its payload and then publish it through the Spring application context as a standard Spring event.
    Sounds interesting to you? Yes, but what is needed behind the scene to make this work?
    Before we start to dig into the Java implementation, let’s first create the Business Event inside the Oracle SOA Suite 11g and implement a composite subscribing to this event.

    First, you need to define the data-shape of the event. This is done conventionally through the usage of XML Schema (File customer.xsd).

    <?xml version="1.0" encoding="windows-1252" ?>
    <xsd:schema xmlns:xsd=""
      <xsd:element name="customer">
            <xsd:element name="id" type="xsd:integer"/>
            <xsd:element name="firstName" type="xsd:string"/>
            <xsd:element name="lastName" type="xsd:string"/>
            <xsd:element name="address">
                  <xsd:element name="street" type="xsd:string"/>
                  <xsd:element name="city" type="xsd:string"/>
                  <xsd:element name="zipCode" type="xsd:integer"/>
                  <xsd:element name="country" type="xsd:string"/>


    After that the Business Event can be defined using the Event Definition Language (EDL).

    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <definitions xmlns=""
      <schema-import namespace=""
      <event-definition name="NewCustomer">
        <content xmlns:ns0=""


    At last we can publish/subscribe to that event from a SOA Suite composite. For our example, I have defined a simple Mediator component listening on the NewCustomer event, which is then sent to a BPEL component for processing.



      After deploying this SCA composite to the server, we are ready on the SOA Suite side to consume NewCustomer events. Now let’s implement the producer side in Java.

      Defining the Event in Java

      We start with the payload (the information) of the event. As shown in the Java snippet above, the goal is to pass the event payload as a normal Java object, without having to worry about the XML representation necessary for publishing the event through the API.

      The act of converting an XML document to/from an object is called Object/XML Mapping or O/X Mapping for short. There are quite a lot of Java frameworks supporting this Object/XML Mapping, like JAXB, Castor, XMLBean, JiBX or XStream. For this post I will use the JiBX framework, as it offers a flexible approach when starting with an XML Schema.

      In my previous post Using the new Object/XML Mapping Support of Spring 3.0 with JiBX and Maven I have presented how to work with JiBX from Spring using Maven as the build tool. The same approach I will use here as well.

      With the XML Schema customer.xsd used for the BusinessEvent definition above as input, the JiBX framework generates the two Java classes Customer and Address defining the payload of our event in Java.

      public class Customer
          private int id;
          private String firstName;
          private String lastName;
          private Address address;
          // public getter and setter method not shown
      public class Address
          private String street;
          private String city;
          private int zipCode;
          private String country;
          // public getter and setter method not shown

      Next let’s define the NewCustomerEvent class, which defines the event itself and acts as a wrapper for the event payload.

      public class NewCustomerEvent extends AbstractApplicationEventForEDN {
      	private Customer customer;
      	private final static String NAMESPACE = "";
      	private final static String NAME = "NewCustomer";
      	public NewCustomerEvent(Object source, Customer customer) 
                                throws XmlMappingException, ParserConfigurationException, IOException {
      		super(source, NAMESPACE, NAME, customer);

      The payload, customer in the case here, can be passed in the 2nd argument of the constructor. The other properties necessary for a Business Event in EDN (namespace and name) are defined as constant values, passed to the constructor of the parent class.
      NewCustomerEvent inherits from AbstractApplicationEventForEDN, the base class for all events to be published to EDN. It defines the common properties of an Business Event, like namespace, local name, content, event id and conversation id.

      public abstract class AbstractApplicationEventForEDN extends ApplicationEvent {
      	private String namespace;
      	private String name;
      	private Object content;
      	private Object eventId;
      	private Object conversationId;
      	public AbstractApplicationEventForEDN(Object source, String namespace, String name, Object content) throws ParserConfigurationException, XmlMappingException, IOException {
      		this.namespace = namespace; = name;
      		this.content = content;
      		this.eventId = UUID.randomUUID();
      		this.conversationId = UUID.randomUUID();
      	// setter method not shown

      AbstractApplicationEventForEDN itself inherits from ApplicationEvent, a class provided by the Spring event handling mechanism. This means that such a Java Business Event is automatically a Spring ApplicationEvent so that it can be published in the Spring event handling mechanism like any other Spring event.

      So far we have a Java representation of the Business Event with its payload and we are able to publish these events through Spring.
      Next we will see how we can connect to EDN and publish the Business Events in a Spring way.

      Creating a FactoryBean to abstract away the creation of a BusinessEventConnection

      First let’s start with the link from Java to the Event Delivery Network. To talk to EDN, we need an instance of oracle.fabric.blocks.event.BusinessEventConnection. To create such an instance, the EDN Java API provides a factory interface named BusinessEventConnectionFactory together with an implementation through SAQRemoteBusinessEventConnectionFactory.
      I use such a FactoryBean to wrap the creation of a BusinessEventConnection.

      public class BusinessEventConnectionFactoryBean implements FactoryBean, InitializingBean {
      	DataSource dataSource;
      	BusinessEventConnectionFactory businessEventConnectionFactory;
      	public void setDataSource(DataSource dataSource) {
      		this.dataSource = dataSource;
      	public void afterPropertiesSet() throws Exception {
              businessEventConnectionFactory = 
                  new SAQRemoteBusinessEventConnectionFactory(
                      dataSource, dataSource, null);
      	public Object getObject() throws Exception {
      		return businessEventConnectionFactory.createBusinessEventConnection();
      	public Class getObjectType() {
      		return BusinessEventConnection.class;
      	public boolean isSingleton() {
      		return false;
      BusinessEventConnectionFactoryBean  declares a dependency to a DataSource, which is necessary for creating a BusinessEventConnectionFactory. This means that the DataSource needs to be injected through Spring, so a bean configuration is necessary in the Spring context XML definition
    <context:property-placeholder location=""/>
    <bean id="businessEventConnection" class="com.trivadis.soa.BusinessEventConnectionFactoryBean">
    	<property name="dataSource" ref="dataSource"/>
    <bean id="dataSource" class="oracle.jdbc.xa.client.OracleXADataSource">
    	<property name="user" value="${jdbc.username}"/>
    	<property name="password" value="${jdbc.password}"/>
    	<property name="URL" value="${jdbc.url}"/>
    	<property name="implicitCachingEnabled" value="false"/>


    The DB connection properties can be externalized into a properties file ( by using the Spring context:property-placeholder element.


    When running in an Java EE application server, the DataSource can easily be retrieved via JNDI by switching the bean configuration as follows

    <bean id="dataSource" class="org.springframework.jndi.JndiObjectFactoryBean">
        <property name="jndiName" value="jdbc/MyDataSource"/>


    With the BusinessEventConnection bean set up, let’s see how the Java event classes (i.e. NewCustomerEvent) can be published to EDN.


      Publishing the Event to the Event Delivery Network (EDN)

    According to Spring Best Practices we first define an interface which the event publisher implementation will need to implement. The publishEvent() method declares a parameter of type AbstractApplicationEventForEDN, so any child class extending it will be accepted and published.

    public interface BusinessEventPublisher {
    	public abstract void publishEvent(AbstractApplicationEventForEDN applicationEvent)
    			throws XmlMappingException, IOException;


    My implementation of the BusinessEventPublisher can be seen below with the BusinessEventPublisherEDN class. The publishEvent() method first marshals the payload (content property) of the AbstractApplicationEventForEDN into an XML document using the Spring O/X Mapping support. The Marshaller implementation to be used is injected by Spring at initialization time (for more information see my other blog post).

    After that an instance of oracle.fabric.common.BusinessEvent is created and published via the BusinessEventConnection, which is also injected by Spring (i.e. the bean declared before).

    public class BusinessEventPublisherEDN implements BusinessEventPublisher {
    	private BusinessEventConnection conn;
    	private Marshaller marshaller;
    	public void setBusinessEventConnection(BusinessEventConnection conn) {
    		this.conn = conn;
    	public void setMarshaller(Marshaller marshaller) {
    		this.marshaller = marshaller;
    	public void publishEvent(AbstractApplicationEventForEDN applicationEvent) throws XmlMappingException, IOException {
    		DocumentBuilderFactory documentBuilderFactory = DocumentBuilderFactory
    		DocumentBuilder builder = null;
    		try {
    			builder = documentBuilderFactory.newDocumentBuilder();
    		} catch (ParserConfigurationException e) {
    		Document document = builder.newDocument();
    		DOMResult result = new DOMResult(document);
    		marshaller.marshal(applicationEvent.getContent(), result);
    		Element payload = document.getDocumentElement();
    		BusinessEvent event = buildEvent(applicationEvent, payload);
    		conn.publishEvent(event, 3);
    	private BusinessEvent buildEvent(
    			AbstractApplicationEventForEDN applicationEvent, Element payload) {
    		BusinessEventBuilder beb = BusinessEventBuilder.newInstance();
    		QName eventName = new QName(applicationEvent.getNamespace(), applicationEvent
    		beb.setProperty(BusinessEvent.EVENT_ID, applicationEvent.getEventId());
    		beb.setProperty(BusinessEvent.PROPERTY_CONVERSATION_ID, applicationEvent
    		beb.setProperty(BusinessEvent.PRIORITY, 1);
    		BusinessEvent be = beb.createEvent();
    		return be;


    I could use this EventPublisher implementation directly to publish events by injecting it all the event producer beans.

    But my idea is to use the Spring event handling mechanism as the base event transport inside the Spring application and to have one common/central place where all Spring event of type AbstractApplicationEventForEDN are forwarded to Oracle EDN.

    For that I have implemented the Spring ApplicationListener using the AbstractApplicationEventForEDN base class as the type parameter. This has the effect that the listener does only subscribe to subclasses of AbstractApplicationEventForEDN, i.e. all my Java EDN events. The listener uses the injected BusinessEventPublisher instance to publish the events to EDN. This listener implementation basically acts as a bridge from the Spring event handling mechanism to the Event Delivery Network.

    public class ApplicationEventListenerEDN implements ApplicationListener<AbstractApplicationEventForEDN> {
    	private BusinessEventPublisher businessEventPublisher;
    	public void setBusinessEventPublisher(
    			BusinessEventPublisher businessEventPublisher) {
    		this.businessEventPublisher = businessEventPublisher;
    	public void onApplicationEvent(AbstractApplicationEventForEDN applicationEvent) {
    		try {
    		} catch (XmlMappingException e) {
    		} catch (IOException e) {

    The configuration of this classes as Spring beans and the dependencies between them is shown here:

    <bean id="applicationEventListener" class="com.trivadis.soa.ApplicationEventListenerEDN">
    	<property name="businessEventPublisher" ref="businessEventPublisher"/>
    <bean id="businessEventPublisher" class="com.trivadis.soa.BusinessEventPublisherEDN">
    	<property name="businessEventConnection" ref="businessEventConnection"/>
    	<property name="marshaller" ref="marshaller"/>
    <oxm:jibx-marshaller id="marshaller" target-class="com.trivadis.cdm.product.Product"/>


    That’s it! The Java event producer implementation is ready to be tested.


      Testing the publishing of an Event

      I have used the Spring Integration Testing support to test the event publishing. The test class PublisherTest implements the Spring ApplicationContextAware interface. This will force the class to implement the setApplicationContext() method, so that the Spring ApplicationContext will be injected at runtime. This ApplicationContext is necessary to publish an event to the Spring event handling mechanism.

      //ApplicationContext will be loaded from "classpath:/com/trivadis/soa/PublisherTest-context.xml"
      public class PublisherTest implements ApplicationContextAware  {
      	private ApplicationContext context;
      	public void setApplicationContext(ApplicationContext context) throws BeansException {
      		this.context = context;
      	public void testPublishNewCustomer() throws Exception {
      		Customer cust = new Customer();
      		Address adr = new Address();
      		adr.setStreet("Papiermuehlestrasse 73");
      		NewCustomerEvent event = new NewCustomerEvent(this, cust);

      The test method uses the code shown at the beginning of this post. So the goal of simplifying the event publishing to EDN from Java has been achieved!

      The Enterprise Manager console proves that the event publishing to EDN works!


    Above the Flow Trace overview and below the details for the EventConsumer is shown. 



        Source code


        The code shown in this post is only a proof-of-concept and before using it in a real project, some things like error handling need to be improved. All the source code can be downloaded from here.

        In addition to the NewCustomerEvent shown above, the downloadable version implements two other events, UpdateCustomerEvent and NewProductEvent.

      The download contains he following projects:

        Project IDE/Build Description
        spring-edn Eclipse/Maven all reusable classes described in my post
        spring-edn-sample Eclipse/Maven simulates a Spring application with the Business Event class definition. Depends on the spring-edn project and references these classes when setting up the Spring context at startup time.
        maven-local-repo Maven Handles JAR’s not available in public Maven Repositories but necessary for the build of the two projects. There is a script which will install these JARs into the local repository on your machine. Except of the jms.jar, the JAR files are not provided here (because I don’t know if I would be allowed to), they are copied from your own local installation when running the script.
        EDNProject JDeveloper SOA Suite 11g project defining the Business Event for the Event Delivery Network (EDN) and the composite subscribing to the event on EDN.
        In order for the JiBX customization to work when building the spring-edn-sample project, a patched version of the JiBX maven plugin ( is necessary, downloadable from here. For more information see my previous post. For the deployment of the projects, follow these steps:
      1. deploy the EDNProject to a SOA Suite 11g instance.
      2. install the missing JAR’s into your local maven repository by running maven-local-repo/install-jars.bat. Don’t forget to change the environment variable to point to your local installation of FMW
      3. install the necessary artifacts to your local maven repository
      4. create the spring-edn project using mvn install
      5. create the spring-edn-sample project using mvn install.

      Now you can test the installation by running the unit test class as shown above! Hope your are successful!

      Solving “javax.naming.NameNotFoundException: Unable to resolve ‘jdbc.SOAAppUserDataSource’ “ with Oracle SOA Suite 11g Adapter Services

      I ran into this rather “stupid user error” a couple of times already. It’s very easy to solve, however it’s also very easy to do it wrong when configuring Oracle SOA Suite 11g Adapter services through the WebLogic Console.

      I hope this blog entry will help new users when running into this problem:

      You get the following error in the SOA Server Log when testing your Adapter service:

      Exception occured when binding was invoked.
      Exception occured during invocation of JCA binding: “JCA Binding execute of Reference operation ‘insert’ failed due to: Could not create/access the TopLink Session.
      This session is used to connect to the datastore.
      Caused by Exception [TOPLINK-7060] (Oracle TopLink – 11g Release 1 ( (Build 091016)): oracle.toplink.exceptions.ValidationException
      Exception Description: Cannot acquire data source [jdbc/SOAAppUserDataSource].
      Internal Exception: javax.naming.NameNotFoundException: Unable to resolve ‘jdbc.SOAAppUserDataSource’. Resolved ‘jdbc’; remaining name ‘SOAAppUserDataSource’.

      The invoked JCA adapter raised a resource exception.


      The setup of the Adapter Connection Factory configuration


      as well as the corresponding DataSource (i.e. jdbc/SoaAppUserDataSource) seems to be correct at first sight.


      But you might have forgotten to select the server, on which the JDBC data source should be deployed when adding the DataSource in the first place. This is possible when clicking the Finish button too early, before the last step which would ask to select a target server!

      The missing target information for the SoaAppUserDataSource is clearly shown in the summary page of the JDBC Data Sources.


      To fix that, just edit the Data Source, click on the Targets tab and select the servers or cluster it should be deployed on (i.e. soa_server1 in my case):


      After that the error should disappear!

      I think it would be good to get an error/warning on the console when trying to add a DataSource without selecting a target server!