Java / Oracle SOA blog

Installing Soa Suite 10.1.3.5.1 on Weblogic

2009-11-06T20:28:00.010+01:00

Yesterday Oracle released Soa Suite 10.1.3.5.1, the version which you can install on Weblogic 10.3.1 ( FMW11g version ). This is a full version so you don't early versions or extra patches to makes this work.

We need to download Weblogic 10.3.1 and Soa Suite 10.1.3.5.1

first step is to install Weblogic 10.3.1, I use C:\oracle\Soa10gWls as my wls middleware home folder

Now we can go to the Soa suite part, first we need to create a bpel, esb and wsm repository.

Extract the soa suite install zip and go to the rca folder located in ias_windows_x86_101351\Disk1\install\soa_schemas\irca

We need to set a database home for the jdbc driver.
set ORACLE_HOME=C:\oracle\product\11.1.0\db_1
We can use the jdk of the new weblogic install
set JAVA_HOME=C:\oracle\Soa10gWls\jdk160_11

Now we can start irca.bat

After a succesfull install of the repository we can start the soa suite installer in this folder ias_windows_x86_101351\Disk1

Very important the destination path must be in a folder of the just created wls middleware home so I use C:\oracle\Soa10gWls\soa10g

As weblogic home location use C:\oracle\Soa10gWls\wlserver_10.3

We are ready with the install

Now we to start script for wsm go to the C:\oracle\Soa10gWls\soa10g\config\ folder and start
configureSOA.bat

Last step is to create a Soa domain just like Soa Suite 11g and select the Soa Suite 10.1.3.5.1 option

Provide the orabpel and oraesb schema passwords.

Start the admin server and go to http://localhost:7001/console where we can take a look at the server. The soa suite server is called soa10g_server1

When we want to start the soa server we need to go the soa domain bin folder
C:\oracle\Soa10gWls\user_projects\domains\soa1013_domain\bin
and use "startManagedWebLogic.cmd soa10g_server1" to start the server.

This are the default installation url's of the Soa Suite applications
http://localhost:9700/esb
http://localhost:9700/BPELConsole
http://localhost:9700/ccore

And we need to use soaadmin as username to log in and use weblogic1 as password.

The issues that I had and luckily also solved.

Asynchronous routing fails with this error oracle.tip.esb.server.common.exceptions.BusinessEventRetriableException: Failed to enqueue deferred event "oracle.tip.esb.server.dispatch.QueueHandlerException: Publisher not exist for system "{0}"

Thanks to Juan Pablo

change the ESB_PARAMETER table on ORAESB schema the following parameters:

PROP_NAME_CONTROL_TCF_JNDI OracleASjms/ControlTCF
PROP_NAME_MONITOR_TCF_JNDI OracleASjms/MonitorTCF
PROP_NAME_ERROR_TCF_JNDI OracleASjms/ErrorTCF
PROP_NAME_ERROR_RETRY_TCF_JNDI OracleASjms/ErrorRetryTCF
PROP_NAME_DEFERRED_TCF_JNDI OracleASjms/DeferredTCF
PROP_NAME_ERROR_XATCF_JNDI OracleASjms/ErrorTCF
PROP_NAME_DEFERRED_XATCF_JNDI OracleASjms/DeferredTCF

to

PROP_NAME_CONTROL_TCF_JNDI ESB_CONTROL
PROP_NAME_MONITOR_TCF_JNDI ESB_MONITOR
PROP_NAME_ERROR_TCF_JNDI ESB_ERROR
PROP_NAME_ERROR_RETRY_TCF_JNDI ESB_ERROR_RETRY
PROP_NAME_DEFERRED_TCF_JNDI ESB_JAVA_DEFERRED
PROP_NAME_ERROR_XATCF_JNDI ESB_ERROR
PROP_NAME_DEFERRED_XATCF_JNDI ESB_JAVA_DEFERRED

and in the ESB console change the Property of Topic Location of every system to ESB_JAVA_DEFERRED

and see the comments for more fixes

Invoking Soa Suite 11g Service from java

2009-11-04T22:24:00.006+01:00

In Soa Suite 11g we can not call the composite service directly from java. We need to copy the service in the composite, change its binding to adf and wire this service to the component. All the credits goes to Jay's Blog and Clemens, Great work.

The first step is to open the composite xml and find your service.


<?xml version="1.0" encoding="UTF-8" ?>
<!-- Generated by Oracle SOA Modeler version 1.0 at [8/25/09 3:01 PM]. -->
<composite name="Helloworld"
          revision="1.0"
          label="2009-08-25_15-01-51_078"
          mode="active"
          state="on"
          xmlns="http://xmlns.oracle.com/sca/1.0"
          xmlns:xs="http://www.w3.org/2001/XMLSchema"
          xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
          xmlns:orawsp="http://schemas.oracle.com/ws/2006/01/policy"
          xmlns:ui="http://xmlns.oracle.com/soa/designer/">
 <import namespace="http://xmlns.oracle.com/HelloWorld/Helloworld/BPELProcess1"
         location="BPELProcess1.wsdl" importType="wsdl"/>

  <service name="bpelprocess1_client_ep" ui:wsdlLocation="BPELProcess1.wsdl">
    <interface.wsdl interface="http://xmlns.oracle.com/HelloWorld/Helloworld/BPELProcess1#wsdl.interface(BPELProcess1)"/>
     <binding.ws port="http://xmlns.oracle.com/HelloWorld/Helloworld/BPELProcess1#wsdl.endpoint(bpelprocess1_client_ep/BPELProcess1_pt)">
     </binding.ws>
  </service>

Copy this service and give it a unique name and now we need to add the binding.adf binding to this service instead of the binding.ws


  <service name="bpelprocess1_client_ep" ui:wsdlLocation="BPELProcess1.wsdl">
    <interface.wsdl interface="http://xmlns.oracle.com/HelloWorld/Helloworld/BPELProcess1#wsdl.interface(BPELProcess1)"/>
     <binding.ws port="http://xmlns.oracle.com/HelloWorld/Helloworld/BPELProcess1#wsdl.endpoint(bpelprocess1_client_ep/BPELProcess1_pt)">
     </binding.ws>
  </service>

  <service name="bpelprocess1_client_ep2" ui:wsdlLocation="BPELProcess1.wsdl">
    <interface.wsdl interface="http://xmlns.oracle.com/HelloWorld/Helloworld/BPELProcess1#wsdl.interface(BPELProcess1)"/>
   <binding.adf serviceName="{http://xmlns.oracle.com/HelloWorld/Helloworld/BPELProcess1}bpelprocess1_client_ep2"
                registryName=""/>
  </service>

Go back to the design mode and open the new adf binding service and select the same wsdl as your other service ( this will correct the serviceName ) and at last we need to wire the new service to the component

Now we only need to call this service from java


package nl.whitehorses.bpel.unit;

import java.util.Hashtable;
import java.util.UUID;
import java.util.List;

import javax.naming.Context;

import oracle.soa.management.facade.Locator;
import oracle.soa.management.facade.LocatorFactory;
import oracle.soa.management.facade.Composite;
import oracle.soa.management.facade.Service;
import oracle.soa.management.facade.CompositeInstance;
import oracle.soa.management.facade.ComponentInstance;


import oracle.fabric.common.NormalizedMessage;
import oracle.fabric.common.NormalizedMessageImpl;

import oracle.soa.management.util.CompositeInstanceFilter;
import oracle.soa.management.util.ComponentInstanceFilter;


import java.util.Map;

import javax.xml.transform.*;
import javax.xml.transform.dom.*;
import javax.xml.transform.stream.*;
import org.w3c.dom.Element;
import java.io.*;



public class StartProcess {
   public StartProcess() {
       super();

       Hashtable jndiProps = new Hashtable();
       jndiProps.put(Context.PROVIDER_URL, "t3://localhost:8001/soa-infra");
       jndiProps.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
       jndiProps.put(Context.SECURITY_PRINCIPAL, "weblogic");
       jndiProps.put(Context.SECURITY_CREDENTIALS, "weblogic1");
       jndiProps.put("dedicated.connection", "true");

       String inputPayload =
       "<process xmlns=\"http://xmlns.oracle.com/HelloWorld/Helloworld/BPELProcess1\">\n" +
       "   <input>hello</input>\n" +
       "</process>\n" ;


       Locator locator = null;
       try {
           // connect to the soa server
           locator = LocatorFactory.createLocator(jndiProps);
           String compositeDN = "default/Helloworld!1.0";

           // find composite
           Composite composite = locator.lookupComposite("default/Helloworld!1.0");
           System.out.println("Got Composite : "+ composite.toString());

           // find exposed service of the composite
           Service service = composite.getService("bpelprocess1_client_ep2");
           System.out.println("Got serviceName : "+ service.toString());

           // make the input request and add this to a operation of the service
           NormalizedMessage input = new NormalizedMessageImpl();
           String uuid = "uuid:" + UUID.randomUUID();
           input.addProperty(NormalizedMessage.PROPERTY_CONVERSATION_ID,uuid);

           // payload is the partname of the process operation
           input.getPayload().put("payload",inputPayload);

           // process is the operation of the employee service
           NormalizedMessage res = null;
           try {
              res = service.request("process", input);
           } catch(Exception e) {
              e.printStackTrace();
           }


           Map payload = res.getPayload();
           Element element = (Element)payload.get("payload");

           TransformerFactory tFactory = TransformerFactory.newInstance();
           Transformer transformer = tFactory.newTransformer();
           transformer.setOutputProperty("indent", "yes");
           StringWriter sw = new StringWriter();
           StreamResult result = new StreamResult(sw);


           DOMSource source =  new DOMSource(element);

           transformer.transform(source, result);
           System.out.println("Result\n"+sw.toString());

           System.out.println("instances");
          
          
           CompositeInstanceFilter filter = new CompositeInstanceFilter();
           filter.setMinCreationDate(new java.util.Date((System.currentTimeMillis() -  2000000)));
           // get composite instances by filter ..
           List<CompositeInstance> obInstances = composite.getInstances(filter);
           // for each of the returned composite instances..
           for (CompositeInstance instance : obInstances) {
               System.out.println(" DN: " + instance.getCompositeDN() +
                                  " Instance: " + instance.getId() +
                                  " creation-date: " + instance.getCreationDate() +
                                  " state (" + instance.getState() + "): " + getStateAsString(instance.getState())
                                  );
                                
               // setup a component filter
               ComponentInstanceFilter cInstanceFilter = new ComponentInstanceFilter();
               // get child component instances ..
               List<ComponentInstance> childComponentInstances = instance.getChildComponentInstances(cInstanceFilter);

               // for each child component instance (e.g. a bpel process)
               for (ComponentInstance cInstance : childComponentInstances) {
                   System.out.println("  -> componentinstance: " + cInstance.getComponentName() +
                                      " type: " + cInstance.getServiceEngine().getEngineType() +
                                      " state: " +getStateAsString(cInstance.getState())
                                      );
                   System.out.println("State: "+cInstance.getNormalizedStateAsString()  );                
               }
           }

       } catch (Exception e) {
           e.printStackTrace();
       }
   }



   private String getStateAsString(int state)
   {
       // note that this is dependent on wheter the composite state is captured or not
       if (state == CompositeInstance.STATE_COMPLETED_SUCCESSFULLY)
           return ("success");
       else if (state == CompositeInstance.STATE_FAULTED)
           return ("faulted");
       else if (state == CompositeInstance.STATE_RECOVERY_REQUIRED)
           return ("recovery required");
       else if (state == CompositeInstance.STATE_RUNNING)
           return ("running");
       else if (state == CompositeInstance.STATE_STALE)
           return ("stale");
       else
           return ("unknown");
   }


   public static void main(String[] args) {
       StartProcess startUnitProcess = new StartProcess();
   }
}

Working with Apache Tuscany, The Java SCA based platform part 1

2009-11-03T21:19:00.021+01:00

In this blogpost and future blogposts I will try to give you a jumpstart with Apache Tuscany Java SCA. If you follow my blog you may already know that I also work and make blogsposts over an other Service Component Architecture (SCA)-based SOA platform ( Oracle Soa Suite 11g). Soa Suite 11g has a different SCA approach and has much better designer support. But it is nice to take a look at Tuscany and see how this java SCA implementation works.

I will explain how you can make some composite applications. In this blogpost we start easy with building a composite application with

Simple java Component
Jax-ws component
Component with references to other components ( wires )
Service on a component
Using a second composite

Here a overview of my test project.

First we need to download Apache Tuscany Java SCA

We start with a simple java component with its interface.


package nl.whitehorses.tuscany.step1;

public interface JavaService {
    public String getData();
}

package nl.whitehorses.tuscany.step1;

public class JavaServiceImpl implements  JavaService {

    public String getData()  {
        return "Hello from java component";
    }
}

We can add this component in the step1 composite file and provide the java implementation class.


<?xml version="1.0" encoding="UTF-8"?>
<composite xmlns="http://www.osoa.org/xmlns/sca/1.0"
     targetNamespace="http://whitehorses" 
     name="step1">

    <component name="JavaCp">
        <implementation.java class="nl.whitehorses.tuscany.step1.JavaServiceImpl" />
    </component>

</composite>

Last part of step 1 is to run this composite application, now we have to load and test the composite application.


package nl.whitehorses.tuscany.step1;

import org.apache.tuscany.sca.host.embedded.SCADomain;

public class ClientStep1 {

    public final static void main(String[] args) throws Exception {

        SCADomain scaDomain = SCADomain.newInstance("step1.composite");
        JavaService javaService = scaDomain.getService(JavaService.class, "JavaCp");

        System.out.println("java: " + javaService.getData());

        scaDomain.close();
    }
}

In step 2 we will call a jax-ws webservice. In this step we also need to add a reference to the component.

To make this work I created first a jax-ws service and deploy this to an application server.


package nl.whitehorses.soa.ws;

import javax.jws.WebService;

@WebService
public class Helloworld {

    public String getResponse( String message){
      return message;
    
    }
}

In the tuscany client project we need to generate a webservice proxy client for this webservice.
Create an implemention class for this ws proxy client. In this class we need to add a reference with the name jaxws and a setter. We will use this in the composite xml


package nl.whitehorses.tuscany.step2;

import nl.whitehorses.soa.ws.proxy.Helloworld;
import org.osoa.sca.annotations.Reference;

public class HelloworldServiceImpl implements Helloworld{

        private Helloworld jaxws;
    
        @Reference 
        public void setJaxws(Helloworld jaxws) {
            this.jaxws = jaxws;
        }
        
        public String getResponse( String message){
          return jaxws.getResponse(message);
        
        }
}

create a new composite file where we will add this component and its reference. In the reference we need to provide the web service binding


<?xml version="1.0" encoding="UTF-8"?>
<composite xmlns="http://www.osoa.org/xmlns/sca/1.0"
     targetNamespace="http://whitehorses" 
     name="step2">

   <component name="HelloworldCp">
        <implementation.java class="nl.whitehorses.tuscany.step2.HelloworldServiceImpl" />
        <reference name="jaxws">
           <binding.ws wsdlElement="http://ws.soa.whitehorses.nl/#wsdl.port(HelloworldService/HelloworldPort)" 
            uri="http://localhost:7101/jaxws/HelloworldPort?wsdl#wsdl.interface(HelloworldService)"/>
        </reference>
    </component>

</composite>

And at last the test client


package nl.whitehorses.tuscany.step2;


import org.apache.tuscany.sca.host.embedded.SCADomain;
import nl.whitehorses.soa.ws.proxy.Helloworld;

public class ClientStep2 {

    public final static void main(String[] args) throws Exception {

        SCADomain scaDomain = SCADomain.newInstance("step2.composite");
        Helloworld helloworld = scaDomain.getService(Helloworld.class, "HelloworldCp");

        System.out.println("ws: " + helloworld.getResponse("hello"));

        scaDomain.close();
    }
}

In step 3 we will expose an component as a service. First step is to make an interface with the methods which we want to expose in this web service. We have to add Remotable annotation.


package nl.whitehorses.tuscany.step3;

import org.osoa.sca.annotations.Remotable;

@Remotable
public interface TuscanyService {

    public String getJaxwsResponse( String message);

    public String getJavaData();

    public String getJavaData2();
 
}

The implementatation of this component with the Service annotation and off course the references to the other components.


package nl.whitehorses.tuscany.step3;

import nl.whitehorses.soa.ws.proxy.Helloworld;

import org.osoa.sca.annotations.Reference;
import org.osoa.sca.annotations.Service;
import nl.whitehorses.tuscany.step1.JavaService;

@Service(TuscanyService.class)
public class TuscanyServiceImpl implements TuscanyService {

    private Helloworld helloworldComponent;
    private JavaService javaComponent;
    private JavaService javaComponent2;
    
    @Reference 
    public void setHelloworldComponent(Helloworld helloworldComponent) {
        this.helloworldComponent = helloworldComponent;
    }

    @Reference 
    public void setJavaComponent(JavaService javaComponent) {
        this.javaComponent = javaComponent;
    }

    @Reference 
    public void setJavaComponent2(JavaService javaComponent2) {
        this.javaComponent2 = javaComponent2;
    }


    public String getJaxwsResponse(String message) {
        return helloworldComponent.getResponse(message) ;
    }

    public String getJavaData() {
        return javaComponent.getData();
    }
    
    public String getJavaData2() {
        return javaComponent2.getData();
    }
}

The step3 composite file has a TuscanyServiceComponent with 3 references to the step 1 and 2 components and this component has also a service. In this service we have to provide the ws url.


<?xml version="1.0" encoding="UTF-8"?>
<composite xmlns="http://www.osoa.org/xmlns/sca/1.0"
     targetNamespace="http://whitehorses" 
     name="step3">

    <component name="TuscanyServiceComponent">
        <implementation.java class="nl.whitehorses.tuscany.step3.TuscanyServiceImpl" />
        <reference name="helloworldComponent" target="HelloworldCp" />
        <reference name="javaComponent" target="JavaCp" />
        <reference name="javaComponent2" target="JavaCp2" />
        <service name="TuscanyService">
           <binding.ws uri="http://localhost:8085/TuscanyService"/>
        </service>
    </component>

    <component name="JavaCp">
        <implementation.java class="nl.whitehorses.tuscany.step1.JavaServiceImpl" />
    </component>

    <component name="JavaCp2">
        <implementation.java class="nl.whitehorses.tuscany.step1.JavaServiceImpl" />
    </component>

    <component name="HelloworldCp">
        <implementation.java class="nl.whitehorses.tuscany.step2.HelloworldServiceImpl" />
        <reference name="jaxws">
           <binding.ws wsdlElement="http://ws.soa.whitehorses.nl/#wsdl.port(HelloworldService/HelloworldPort)" 
            uri="http://localhost:7101/jaxws/HelloworldPort?wsdl#wsdl.interface(HelloworldService)"/>
        </reference>
    </component>

</composite>

The client code which tests the main component and start the service on this component


package nl.whitehorses.tuscany.step3;

import java.io.IOException;
import org.apache.tuscany.sca.host.embedded.SCADomain;

public class ClientStep3 {

    public final static void main(String[] args) throws Exception {

        SCADomain scaDomain = SCADomain.newInstance("step3.composite");
        TuscanyService tuscanyService =  scaDomain.getService(TuscanyService.class, "TuscanyServiceComponent");

        System.out.println("ws: "+tuscanyService.getJaxwsResponse("hello"));
        System.out.println("java: "+tuscanyService.getJavaData());
        System.out.println("java2: "+tuscanyService.getJavaData2());

        try {
             System.out.println("ws service started (press enter to shutdown)");
             System.in.read();
         } catch (IOException e) {
             e.printStackTrace();
         }

        scaDomain.close();
    }    
}

Now we can use soapui to test this web service.

In the last step in this blog I will use a second composite which will be called by the first composite.
First we create a new composite xml. We will copy a java component from the step3 composite to this composite. Give this composite a new name and target namespace. We will use these values to import this composite. This component needs a service else we can not call it from the main composite.


<?xml version="1.0" encoding="UTF-8"?>
<composite xmlns="http://www.osoa.org/xmlns/sca/1.0"
     targetNamespace="http://whitehorses2" 
     name="step4_2">

    <service name="JavaCpService" promote="JavaCp"> 
        <interface.java interface="nl.whitehorses.tuscany.step1.JavaService"/>
    </service>

    <component name="JavaCp">
        <implementation.java class="nl.whitehorses.tuscany.step1.JavaServiceImpl" />
    </component>

</composite>

The main composite called step4_1 need the namespace of the second composite. The JavaCp2 component import the second composite by using the target namespace of the second composite and with its name. In the javaComponent2 reference of the TuscanyServiceComponent will call JavaCp2 component followed by the service name of the second composite.


<?xml version="1.0" encoding="UTF-8"?>
<composite xmlns="http://www.osoa.org/xmlns/sca/1.0"
     targetNamespace="http://whitehorses" 
     xmlns:whitehorses2="http://whitehorses2"
     name="step4_1">

    <component name="TuscanyServiceComponent">
        <implementation.java class="nl.whitehorses.tuscany.step3.TuscanyServiceImpl" />
        <reference name="helloworldComponent" target="HelloworldCp" />
        <reference name="javaComponent" target="JavaCp" />
        <reference name="javaComponent2" target="JavaCp2/JavaCpService" />
        <service name="TuscanyService">
           <binding.ws uri="http://localhost:8085/TuscanyService"/>
        </service>
    </component>

    <component name="JavaCp">
        <implementation.java class="nl.whitehorses.tuscany.step1.JavaServiceImpl" />
    </component>

    <component name="HelloworldCp">
        <implementation.java class="nl.whitehorses.tuscany.step2.HelloworldServiceImpl" />
        <reference name="jaxws">
           <binding.ws wsdlElement="http://ws.soa.whitehorses.nl/#wsdl.port(HelloworldService/HelloworldPort)" 
            uri="http://localhost:7101/jaxws/HelloworldPort?wsdl#wsdl.interface(HelloworldService)"/>
        </reference>
    </component>

    <component name="JavaCp2">
        <implementation.composite name="whitehorses2:step4_2"/>
    </component>
</composite>

and at last the step 4 test client.


package nl.whitehorses.tuscany.step4;

import nl.whitehorses.tuscany.step3.TuscanyService;
import java.io.IOException;
import org.apache.tuscany.sca.host.embedded.SCADomain;

public class ClientStep4 {

    public final static void main(String[] args) throws Exception {

        SCADomain scaDomain = SCADomain.newInstance("step4_1.composite");
        TuscanyService tuscanyService =  scaDomain.getService(TuscanyService.class, "TuscanyServiceComponent");

        System.out.println("ws: "+tuscanyService.getJaxwsResponse("hello"));
        System.out.println("java: "+tuscanyService.getJavaData());
        System.out.println("java2: "+tuscanyService.getJavaData2());

        try {
             System.out.println("ws service started (press enter to shutdown)");
             System.in.read();
         } catch (IOException e) {
             e.printStackTrace();
         }

        scaDomain.close();
    }    
}

Here you can download my jdeveloper 11G test project.

Securing Web Services with SAML Sender Vouches

2009-10-29T20:36:00.024+01:00

After securing you web applications with SAML is the next step to secure your web services with SAML Sender Vouches ws-security policy, this can be complex because you need to know a lot over the weblogic server configuration and its java security frameworks. For example you need to configure two Weblogic servers, the first is the Web Service server and the second server is the Secure Token Service ( STS ). After that you need to add some client credential providers to the generated web service proxy client. Thanks to Vishal Jain of Oracle who provided me a working example.
This is how SAML Sender Vouches works and what we need to do in weblogic / java.
The short version is, the web service proxy client call the STS server to get an SAML assertion on behalf of the User to call the Web Service.

The long version, the user provides its credentials to the ws proxy client and the ws proxy client calls the STS server and provides the username / password of the user and the client key.
The STS validates the user and the ws proxy client certificate and the STS returns the STS identity assertion to the ws proxy client. The ws proxy client uses this STS assertion together with the ws client and ws server certificate to call the web service.

First we need to have 3 certificates, the first is alice, this will be used in the ws proxy client and the second certificate is bob, this will be used in the Weblogic web service server and the last we use wssipsts certificate for the Weblogic STS server. Add these keys into a java keystore.

Setting up the Secure Token Service (STS)
Create a new Weblogic 10.3.1 domain and start the admin server. First we need to enable SSL in the general tab of the server and then add our keystores in the keystore tab.
Provide the STS certificate alias, in my case wssipprv

Go the myrealm security where we add the Alice user and provide a password, Very important the username must match with the CN of the Alice certificate. The user provides the credentials and must match with user in WLS and the ws proxy client provides the Alice certificate and this must match with the PKI Credential mapping.

Go to the Credential mapping tab of the Provider tab and add a PKI Credential Mapping where we import the keystore and Add a SAML Credential Mapping version 2 where we add the Web Service URL.

Open the just created PKI credential mapping and add the keystore.

Next we open the SAML Credential Mapping version 2 and provide the Issuer URL and Name Qualifier.

Add the public key of the wssipsts

Add a WSS/Sender-Vouches Relying Party

Enable this and provide the target url of the Web Service Url and assign assertions and include key info

That is all for the STS server and now we can deploy the STS web service.


package nl.whitehorses.sts;

import weblogic.jws.Policy;
import weblogic.wsee.security.saml.SAMLTrustTokenProvider;
import weblogic.wsee.security.wst.framework.TrustTokenProviderRegistry;

import javax.jws.WebMethod;
import javax.jws.WebService;

@WebService
@Policy(uri="policy:Wssp1.2-2007-Wssc1.3-Bootstrap-Https-UNT.xml")
public class StsUnt {

static {
init();
}

@WebMethod
@Policy(uri="policy:Wssp1.2-2007-SignBody.xml")
public String dummyMethod(String s) {
return s;
}

static void init() {
TrustTokenProviderRegistry reg = TrustTokenProviderRegistry.getInstance();
SAMLTrustTokenProvider provider = new MySAMLTrustTokenProvider();
reg.registerProvider("http://docs.oasis-open.org/wss/2004/01/oasis-2004-01-saml-token-profile-1.0#SAMLAssertionID", provider);
reg.registerProvider("http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.0#SAMLAssertionID", provider);
reg.registerProvider("http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV2.0",  provider);
reg.registerProvider("http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV1.0",  provider);
reg.registerProvider("http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV1.1",  provider);
}

static class MySAMLTrustTokenProvider extends SAMLTrustTokenProvider {

}
}

Configure the Weblogic server for the Web Services
Create a new Weblogic domain and use the same keystore, we don't need to setup SSL on this server.

Go the myrealm security and go to providers tab where we add a new PKI Credential Mapping in the credentials tab. ( Use the same setting as the STS server )
We need to add 2 authentication providers and change the 2 default providers.
Create a SAML Authentication and SAML Identity Assertion provider.

Every authentication provider need to have the SUFFICIENT control flag.

Change the SAML Identity Assertion by adding an asserting party and the STS public certificate

Import the STS certificate

Change the just create Sender-Vouches asserting party. Enable this and provide the target url of the web service and add the issuer url, signature required and expect the STS certificate and allow virtual user.

Change the defaultIdentityAsserter and add wsse:PasswordDigest and X.509 as active types.
In the provider specific tab we need to set CN in the Default User Name Mapper Attribute Type and enable Use Default User Name Mapper.

In the DefaultAuthenticator we need to set control flag to SUFFICIENT
And in the provider specific tab. Enable Password Digests and Minimum Password Length to 1.

That's all for the Web Service server. Now we can deploy the webservice.


package nl.whitehorses.sts.ws;

import weblogic.jws.Policies;
import weblogic.jws.Policy;
import javax.jws.WebService;

@Policies(
  {
    @Policy(uri = "policy:Wssp1.2-2007-Saml1.1-SenderVouches-Wss1.0.xml"),
    @Policy(uri = "policy:Wssp1.2-2007-SignBody.xml"),
    @Policy(uri = "policy:Wssp1.2-2007-EncryptBody.xml")
  }
)

@WebService
public class EchoService {
  public String echo( String hello){
    return hello;
  }
}

Generating the Web Service Proxy Client
The last step we need to generate a web service proxy client and add the username and the client credentials mappings.


package nl.whitehorses.sts.ws.client;

import java.io.InputStream;
import java.io.ByteArrayInputStream;

import java.security.cert.X509Certificate;

import java.util.ArrayList;
import java.util.List;
import java.util.Map;

import java.net.URL;
import javax.xml.namespace.QName;


import javax.xml.ws.BindingProvider;
import javax.xml.ws.WebServiceRef;

import weblogic.security.SSL.TrustManager;

import weblogic.wsee.message.WlMessageContext;
import weblogic.wsee.security.bst.ClientBSTCredentialProvider;
import weblogic.wsee.security.saml.SAMLTrustCredentialProvider;
import weblogic.wsee.security.unt.ClientUNTCredentialProvider;

import weblogic.xml.crypto.wss.WSSecurityContext;
import weblogic.xml.crypto.wss.provider.CredentialProvider;

public class EchoServicePortClient
{
 @WebServiceRef
 private static EchoServiceService echoServiceService;

   private static String stsUntPolicy =
   "<?xml version=\"1.0\"?>\n" +
   "<wsp:Policy\n" +
   "  xmlns:wsp=\"http://schemas.xmlsoap.org/ws/2004/09/policy\"\n" +
   "  xmlns:sp=\"http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702\"\n" +
   "  >\n" +
   "  <sp:TransportBinding>\n" +
   "    <wsp:Policy>\n" +
   "      <sp:TransportToken>\n" +
   "        <wsp:Policy>\n" +
   "          <sp:HttpsToken/>\n" +
   "        </wsp:Policy>\n" +
   "      </sp:TransportToken>\n" +
   "      <sp:AlgorithmSuite>\n" +
   "        <wsp:Policy>\n" +
   "          <sp:Basic256/>\n" +
   "        </wsp:Policy>\n" +
   "      </sp:AlgorithmSuite>\n" +
   "      <sp:Layout>\n" +
   "        <wsp:Policy>\n" +
   "          <sp:Lax/>\n" +
   "        </wsp:Policy>\n" +
   "      </sp:Layout>\n" +
   "      <sp:IncludeTimestamp/>\n" +
   "    </wsp:Policy>\n" +
   "  </sp:TransportBinding>\n" +
   "  <sp:SupportingTokens>\n" +
   "    <wsp:Policy>\n" +
   "      <sp:UsernameToken\n" +
   "        sp:IncludeToken=\"http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient\">\n" +
   "        <wsp:Policy>\n" +
   "          <sp:WssUsernameToken10/>\n" +
   "        </wsp:Policy>\n" +
   "      </sp:UsernameToken>\n" +
   "    </wsp:Policy>\n" +
   "  </sp:SupportingTokens>\n" +
   "</wsp:Policy>";

   public static void main(String[] args) {
       System.setProperty("com.sun.xml.ws.transport.http.client.HttpTransportPipe.dump", "true");
       try {

           String wsURL = "http://10.10.10.10:7011/saml-ws-context-root/EchoServicePort?WSDL";

           echoServiceService = new EchoServiceService(    new URL(wsURL) 
                                                        ,  new QName("http://ws.sts.whitehorses.nl/", "EchoServiceService"));
           EchoService echoService = echoServiceService.getEchoServicePort();

           System.setProperty("javax.net.ssl.trustStore", "C:/projecten/workspace/11g_prod/saml1.1_ws/wsttest1/certs/cacerts");

           Map<String, Object> requestContext = ((BindingProvider)echoService).getRequestContext();

           List<CredentialProvider> credList = new ArrayList<CredentialProvider>();

           // Add the necessary credential providers to the list
           InputStream policy = new ByteArrayInputStream(stsUntPolicy.getBytes("UTF-8"));
           requestContext.put(WlMessageContext.WST_BOOT_STRAP_POLICY, policy );

           String stsURL = "https://localhost:7022/sts/StsUntPort";
          
          
           requestContext.put(WlMessageContext.STS_ENDPOINT_ADDRESS_PROPERTY, stsURL);
           requestContext.put(WSSecurityContext.TRUST_MANAGER,
                              new TrustManager() {
                                   public boolean certificateCallback(X509Certificate[] chain, int validateErr) {
                                   // need to validate if the server cert can be trusted
                                       return true;
                                   }
                               });

           credList.add(new SAMLTrustCredentialProvider());

           String username = "Alice";
           String password = "weblogic1";
           credList.add(new ClientUNTCredentialProvider(username.getBytes(), password.getBytes()));

           // ClientBSTCredentialProvider
           String defaultClientcert = "C:/projecten/workspace/11g_prod/saml1.1_ws/wsttest1/certs/Alice.cer";
           String clientcert = System.getProperty("target.clientcert", defaultClientcert);
           String defaultClientkey =  "C:/projecten/workspace/11g_prod/saml1.1_ws/wsttest1/certs/Alice.prv";
           String clientkey = System.getProperty("target.clientkey", defaultClientkey);
              
           String defaultServerCert = "C:/projecten/workspace/11g_prod/saml1.1_ws/wsttest1/certs/Bob.cer";
           String serverCert = System.getProperty("target.serverCert", defaultServerCert);

           credList.add(new ClientBSTCredentialProvider(clientcert, clientkey, serverCert));

           requestContext.put(WSSecurityContext.CREDENTIAL_PROVIDER_LIST, credList);

           // Add your code to call the desired methods.
           System.out.println(echoService.echo("Hello"));

       } catch (Exception ex) {
           ex.printStackTrace();
       }
   }

   }

JMS Request Reply Interaction Pattern in Soa Suite 11g

2009-10-20T23:05:00.010+02:00

In Soa Suite 11g the JMS adapter has support for request reply operations. You can use this operation in synchronous or asynchronous mode. In this blog I will show you both modes. I start with a Asynchronous example and at the end I describe the synchronous mode.

Asynchronous Request / Reply
First we start with a simple Asychronous request and reply JMS adapter. Add a JMS adapter to the references site of the composite.

Choose Request/ Reply and off course asynchronous

Select a request queue ( need to create this in the wls console ) and provide the jndi name of jms resource adapter ( define this in the jms resource adapter ) . Very important use a xa transacted jms connection factory in the jms resource adapter and leave the rest as default.

In the Reply we provide the response queue and use the same jms resource adapter jndi name of the request

Provide the request and response element.

With this as result.

Now we can use this jms adapter in a asynchronous Mediator or in a synchronous BPEL process.
First we start with the mediator. Add a Mediator with the same input and output as the jms adapter
Wire the JMS adapter to this Mediator so we can define the routing rules.

With this as result.

Because this asynchronous service is hard to test, so I will also make a synchronous BPEL process which calls this asynchronous jms adapter with a invoke and receive activity.
Add a BPEL process with the same input and output as the jms adapter

Here an overview of the BPEL process with the invoke and receive activity

Picture of my test composite

For testing we need to transfer the jms message from the request queue to the reply queue. So I add a mediator with a consume and produce jms adapter.

Very important, we need to assign the message id of the jms message to the correlation id of the reply jms message. Do this in the assign of the routing rule.

Last thing is to test the BPEL process in the enterprise manager

With this as result.

Synchronous Request / Reply
The synchronous request reply jms adapter works a bit different then asynchronous.
In step 6 we now select synchronous

In step 7 we can provide the request and reply queue. But very important we to provide the jndi name of a jms resource adapter which has transacted on true and use a jms connection factory which is not xa transacted.
With synchronous jms adapter I had to switch the request and response element. Very strange ( is it a bug ).

This synchronous jms message is a bit different, this message has the JCA_JMSReplyTo field which contains the reply queue name.

Now for testing we also need to add an extra mediator with reads the request queue , set the correlation id and put the message in the reply queue.

Add a synchronous mediator and wire to the synchronous jms adapter, complete the routing rule and finally test this in the enterprise manager.

Oracle OpenWorld 2009 Fusion middleware highlights

2009-10-15T22:53:00.005+02:00

The most important news is that Oracle plans to release JDeveloper 11g R1 PS1 in November. This so called patch set is more a new release ( more then 550+ new features ) then a patch
Here is my quick overview of the features and products I noticed at OOW.

ADF
- Oracle improved the ADF Event mechanism, so the Task Flow fragment regions can communicate much better, You can define the event on a JSF item and not manually in the pagedef, define your own payload. For example in an ADF tree with employees and departments you can send an event when the user select an item in the tree and this number will be passed on to the right task flow. And you even can fire events with drag and drop. For more info buy the coming book of Frank Nimphius, he wrote a whole chapter about this subject.
- ADS active data services pushing the data to the page, Frank N. and Matthias W. made a great demo
- Maybe Maven support.
- Better EJB support in ADF

ADF Mobile
Build your web application just like a normal ADF web application on deploy this on weblogic server. These mobile jsf pages which work on every phone in the native look of the phone, the so called the browser version. With mobile you can also build native applications for blackberry and windows mobile ( just make the right deployment profile ) and this will work with the black berry and windows mobile services and these services will sync with the oracle lite server. So this technology makes it possible to make an offline ADF application, when there are enough customers who wants this feature then Oracle will build this. ADF mobile is now only supported with ADF BC and the next versions will have also have web services support.
For more info see the Amis blog

Soa Suite 11G
-The soa suite is becoming more and more complete, the next version will have a spring context component, this component is in this version only available as technical preview. But this is a good start and there are talks about supporting C code in the composite.
- EDN Event Delivery Network now only works with AQ but there will be also a JMS implementation.
For more info see the blog of Torsten and Hajo

BPM 11G
In one of the hands-on sessions we could play with BPM 11g and it is really great. You can now use JDeveloper to configure it and BPM is an composite component in the Soa Suite. So you can take a look or change it at the BPM level or go to the composite level. BPM uses the human task flows components of the soa suite for the human interaction, Next we can import this human task in jdeveloper to create an task flow which can be deployed in the worklist application. And BPM introduces the BPM composer which is a web application ( don't need jdeveloper ) where you can change your process. Oracle thinks to release it early 2010.

Continuous build with Soa Suite 11g and Hudson

2009-10-04T23:12:00.010+02:00

With Soa Suite 11g we can add unit tests (test suites) to our composite applications and start these tests with the ant scripts provided by Oracle. The soa test ant script can start and generate an junit xml which can be read for the result of the test. For more info see my previous blogpost about the ant scripts and the testsuite option in Soa Suite 11g.

So the last step is to combine the test suite feature and the ant scripts of mine and Oracle so we can use it in a continuous build system. I will use Hudson for this.

We start by downloading the lastest hudson war.

Start hudson by setting the java home and path
set JAVA_HOME=c:\java\jdk160_05
set PATH=%JAVA_HOME%\bin;%PATH
java -jar hudson.war

this will start Hudson and open a browser and go to http://localhost:8080.

First we install Hudson as a windows service. Just provide the location. I will use c:\java\hudson

This will restart hudson. Now we can configure Hudson

Provide the ant and java location of the jdeveloper 11g R1 home.

Put the soa projects and ant scripts in subversion, so Hudson can check this out

This is how it looks. Very important my ant scripts need this folder paths.

Now we can create a new job.

Configure this new job. We start by adding the svn url.

Then add the ant script ( build.xml ) and fill the target ( deployAll) and for the oracle ant scripts we need to set the basedir java parameter to the jdeveloper bin folder.

And provide the location where Hudson can find the junit xml files.

Now we have to add ant-contrib-1.0XXXX.jar the to the jdeveloper\ant\lib folder and add a environment variable to the ant.bat

set CURRENT_FOLDER=%CD%

I need this for the ant scripts so I can use relative paths.

Let's press build now and look at the result. My example composite application contains two tests, in my case they are both succesfull.

Look at the test.
And the performance.

That's all. This will save you a lot of testing time and off course Hudson can blame the person who checked in as last.
Here is my test project and ant scripts

Deploy Soa Suite 11g composite applications with Ant scripts

2009-09-26T13:06:00.019+02:00

With Soa Suite 11g you can deploy your composite applications from JDeveloper or with Ant. In this blog I will do this with the soa 11g Ant scripts. These ant scripts can only deploy one project so I made an Ant script around the soa ant scripts which can deploy more composites applications to different Soa enviroments. So now you can use it to automate your deployment or use it in your build tool. In my ant script I will compile, build and package the composite application and deploy this to the soa server, after this I use an ant script to start the unit tests and generate a junit result xml. This junit xml can be used in your continious build system. You can easily extend this build script so you use it to manage the composite applications.
For more info over ant deployment see the official deployment documentation .
The official ant scripts are located in the jdeverloper\bin folder. Here is a summary what are and can do

ant-sca-test.xml, This script can start the test suites of the composite and generates a juinit report and not Attaches, extracts, generates, and validates configuration plans for a SOA composite application, The official documentation description is not correct.
ant-sca-compile.xml, Compiles a SOA composite application ,this script is also called in the package scrip, so we don't need to call this directly.
ant-sca-package.xml, Packages a SOA composite application into a composite SAR file and also validates and build the composite application.
ant-sca-deploy.xml, Deploys a SOA composite application.
ant-sca-mgmt.xml, Manages a SOA composite application, including starting, stopping, activating, retiring, assigning a default revision version, and listing deployed SOA composite applications.

Here is the main build.properties where you have to define the jdeveloper and your application home, which composite applications you want to deploy and to which environment dev or acc.


# global
wn.bea.home=C:/oracle/MiddlewareJdev11gR1
oracle.home=${wn.bea.home}/jdeveloper
java.passed.home=${wn.bea.home}/jdk160_11
wl_home=${wn.bea.home}/wlserver_10.3

# temp
tmp.output.dir=c:/temp

applications.home=C:/projecten/workspace/11g_prod
applications=HelloWorld,SoaEjbReference

deployment.plan.environment=dev

# dev deployment server weblogic
dev.serverURL=http://laptopedwin:8001
dev.overwrite=true
dev.user=weblogic
dev.password=weblogic1
dev.forceDefault=true

# acceptance deployment server weblogic
acc.serverURL=http://laptopedwin:8001
acc.overwrite=true
acc.user=weblogic
acc.password=weblogic1
acc.forceDefault=true

Every application can have one or more soa projects so the main ant script will load the application properties file which contains all the project with its revision number.
Here is a example of SoaEjbReference.properties file


projects=SoaEjb,SoaEjb2
SoaEjb.revision=1.0
SoaEjb2.revision=1.1

Because in my example I have two soa environments so I need to create two configuration plans. With this plan ( which look the wls plan ) can change the url of endpoints so it matches with the environment.
Select the composite application xml and generate a configuration plan.
Add the dev or acc extension to the file name.
Here you see how the plan looks like.

And here is the main ant build script which can do it all and calls the Oracle Ant scripts.


<?xml version="1.0" encoding="iso-8859-1"?>
<project name="soaDeployAll" default="deployAll">


    <property file="build.properties"/>  
    <property environment="env"/> 

    <taskdef resource="net/sf/antcontrib/antcontrib.properties"/>


    <import file="${basedir}/ant-sca-deploy.xml"/>
    <import file="${basedir}/ant-sca-package.xml"/>
    <import file="${basedir}/ant-sca-test.xml"/>



   <target name="deployAll"> 
     <foreach list="${applications}" param="application" target="deployApplication" inheritall="true" inheritrefs="false"/>
   </target>


    <target name="deployApplication">
        <echo>deploy application ${application}</echo>
        <property file="${application}.properties"/>   
        <foreach list="${projects}" param="project" target="deployProject" inheritall="true" inheritrefs="false"/>
    </target>

    <target name="deployProject">
        <echo>deploy project ${project} for  environment ${deployment.plan.environment}</echo>

        <property name="proj.compositeName" value="${project}"/>
        <property name="proj.compositeDir" value="${applications.home}/${application}"/>
        <propertycopy name="proj.revision" from="${project}.revision"/>

        <echo>deploy compositeName ${proj.compositeName}</echo>
        <echo>deploy compositeDir ${proj.compositeDir}</echo>

        <antcall target="package" inheritall="false">
             <param name="compositeDir" value="${proj.compositeDir}/${project}"/>
             <param name="compositeName" value="${proj.compositeName}"/>
             <param name="revision" value="${proj.revision}"/>
             <param name="oracle.home" value="${oracle.home}"/>
             <param name="java.passed.home" value="${java.passed.home}"/>
             <param name="wl_home" value="${wl_home}"/>
             <param name="sca.application.home" value="${proj.compositeDir}"/>
             <param name="scac.application.home" value="${proj.compositeDir}"/>
             <param name="scac.input" value="${proj.compositeDir}/${proj.compositeName}/composite.xml"/>
             <param name="scac.output" value="${tmp.output.dir}/${proj.compositeName}.xml"/>
             <param name="scac.error" value="${tmp.output.dir}/${proj.compositeName}.err"/>
             <param name="scac.displayLevel" value="3"/>
        </antcall>  



        <property name="deploy.sarLocation" value="${proj.compositeDir}/${proj.compositeName}/deploy/sca_${proj.compositeName}_rev${proj.revision}.jar"/>
        <property name="deploy.configplan"  value="${proj.compositeDir}/${proj.compositeName}/${proj.compositeName}_cfgplan_${deployment.plan.environment}.xml"/>

        <propertycopy name="deploy.serverURL"    from="${deployment.plan.environment}.serverURL"/>
        <propertycopy name="deploy.overwrite"    from="${deployment.plan.environment}.overwrite"/>
        <propertycopy name="deploy.user"         from="${deployment.plan.environment}.user"/>
        <propertycopy name="deploy.password"     from="${deployment.plan.environment}.password"/>
        <propertycopy name="deploy.forceDefault" from="${deployment.plan.environment}.forceDefault"/>

        <echo>deploy on ${deploy.serverURL} with user ${deploy.user}</echo>
        <echo>deploy sarFile ${deploy.sarLocation}</echo>

        <antcall target="deploy" inheritall="false">
             <param name="wl_home" value="${wl_home}"/>
             <param name="oracle.home" value="${oracle.home}"/>
             <param name="serverURL" value="${deploy.serverURL}"/>
             <param name="user" value="${deploy.user}"/>
             <param name="password" value="${deploy.password}"/>
             <param name="overwrite" value="${deploy.overwrite}"/>
             <param name="forceDefault" value="${deploy.forceDefault}"/>
             <param name="sarLocation" value="${deploy.sarLocation}"/>
             <param name="configplan" value="${deploy.configplan}"/>
        </antcall>  

        <antcall target="test" inheritall="false">
             <param name="scatest.input" value="${project}"/>
             <param name="scatest.format" value="junit"/>
             <param name="scatest.result" value="${tmp.output.dir}"/>
             <param name="jndi.properties.input" value="${deployment.plan.environment}.jndi.properties"/>
        </antcall>  

        
    </target>


</project>

And finally the cmd script to run this ant script. To make this work we need the ant-contrib libray and put this in the classpath.


set ORACLE_HOME=C:\oracle\MiddlewareJdev11gR1
set ANT_HOME=%ORACLE_HOME%\jdeveloper\ant
set PATH=%ANT_HOME%\bin;%PATH%
set JAVA_HOME=%ORACLE_HOME%\jdk160_11

set ANT_CONTRIB=ant-contrib-1.0b3.jar
set CLASSPATH=%CLASSPATH%;%ANT_CONTRIB%

ant -f build.xml deployAll

Here is the zip with all the files and extract this and put this all in the jdeveloper/bin folder.

Job scheduling in Weblogic

2009-09-22T21:30:00.007+02:00

This blog is about how you can run a batchjob on a specific time in the Weblogic application server and as extra, I made an ADF page in which you can stop or start the jobs. This job schedular can start for example some Soa processes at a specific time.
The scheduling is done with the help of the CommonJ API which is standard in Weblogic. This example works perfectly in a managed node but if you want to do the same in a Weblogic Cluster then you should not read this blog and go the James Bayer's blog . And for more information about Timer API see the official Weblogic documentation.

Very important, this job scheduling only works within in a web application.
First we start by adding the TimerManager to the web.xml


 <resource-ref>
   <res-ref-name>tm/TimerManager</res-ref-name>
   <res-type>commonj.timers.TimerManager</res-type>
   <res-auth>Container</res-auth>
   <res-sharing-scope>Unshareable</res-sharing-scope>
 </resource-ref>
</web-app>

Now we done this we can add a servlet which start this TimerManager and its jobs. Important that the servlet is automatically started when the webapp is started.


 <servlet>
   <display-name>timer</display-name>
   <servlet-name>timer</servlet-name>
   <servlet-class>nl.whitehorses.wls.schedular.TimerServlet</servlet-class>
   <load-on-startup>100</load-on-startup>
 </servlet>
 <servlet-mapping>
   <servlet-name>timer</servlet-name>
   <url-pattern>/timer</url-pattern>
 </servlet-mapping>

Then the servlet code which start the TimeManager and the two example batches. In this example the job is started again when it is finished after 30 seconds. If you want to do this at a specific time then use scheduleAtFixedRate


package nl.whitehorses.wls.schedular;

import java.io.IOException;
import java.io.PrintWriter;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.servlet.ServletConfig;
import javax.servlet.ServletException;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import commonj.timers.*;

/**
* TimerServlet demonstrates a simple use of commonj timers
*/
public class TimerServlet extends HttpServlet {

  
   public void init(ServletConfig config) throws ServletException {

       super.init(config);
       System.out.println("timer servlet is initialized  ");
       try {
           InitialContext ic = new InitialContext();
           TimerManager tm = (TimerManager)ic.lookup("java:comp/env/tm/TimerManager");

           Timer batchRun1Timer = null;
           Boolean batchRun1TimerIsRunning = false;
           Timer batchRun2Timer = null;
           Boolean batchRun2TimerIsRunning = false;

           // Execute timer every 30 seconds starting immediately
           batchRun1Timer = tm.schedule(new Batch1(), 0, 30 * 1000);
           batchRun1TimerIsRunning = true;

           batchRun2Timer = tm.schedule(new Batch2(), 0, 30 * 1000);
           batchRun2TimerIsRunning = true;

           config.getServletContext().setAttribute("batch1",batchRun1Timer);
           config.getServletContext().setAttribute("batch2",batchRun2Timer);
           config.getServletContext().setAttribute("batch1Running",batchRun1TimerIsRunning);
           config.getServletContext().setAttribute("batch2Running",batchRun2TimerIsRunning);

       } catch (NamingException ne) {
           ne.printStackTrace();
       }
   }

   public void service(HttpServletRequest req,  HttpServletResponse res) throws IOException {
      res.setContentType("text/html");
       PrintWriter out = res.getWriter();
       out.println("Timer servlet is working!");
   }
}

Here is an example of a batch job. The timerExpired method is fired every time when the job time has passed. Here you can put in your own code and when the job is canceled then the TimerCancel method is fired.


package nl.whitehorses.wls.schedular;

import commonj.timers.*;
import java.io.Serializable;

public class Batch1 implements Serializable, TimerListener, CancelTimerListener {

   public void timerExpired(Timer timer) {
       System.out.println("Batch1 timer expired called on " + timer);
   }
   public  void timerCancel(Timer timer) {
       System.out.println("Batch1 timer cancelled called on " + timer);

   }
}

And finally the JSF page with its backing bean to control the jobs.


<?xml version='1.0' encoding='windows-1252'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
         xmlns:f="http://java.sun.com/jsf/core"
         xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
 <jsp:directive.page contentType="text/html;charset=windows-1252"/>
 <f:view>
   <af:document id="d1">
     <af:form id="f1">
       <af:panelHeader text="Timers" id="ph1">
         <af:panelFormLayout id="pfl1">
           <af:panelGroupLayout id="pgl6" layout="horizontal">
             <af:panelGroupLayout id="pgl8" layout="vertical">
               <af:poll id="poll1">
                 <af:panelGroupLayout id="pgl5" layout="vertical">
                   <af:outputLabel value="#{TimerBean.tmStatus}" id="ol4"
                                   partialTriggers="poll1"/>
                   <af:outputLabel value="#{TimerBean.batch1Status}" id="o22"
                                   partialTriggers="poll1"/>
                   <af:outputLabel value="#{TimerBean.batch2Status}" id="o23"
                                   partialTriggers="poll1"/>
                 </af:panelGroupLayout>
               </af:poll>
             </af:panelGroupLayout>
             <af:panelGroupLayout id="pgl7" layout="vertical">
               <af:commandButton text="Time Manager On / Off" id="cb1"
                                 actionListener="#{TimerBean.timerManager}"/>
               <af:commandButton text="Batch 1 On / Off" id="cb2"
                                 actionListener="#{TimerBean.Batch1}"/>
               <af:commandButton text="Batch 2 On / Off" id="cb3"
                                 actionListener="#{TimerBean.Batch2}"/>
             </af:panelGroupLayout>
           </af:panelGroupLayout>
         </af:panelFormLayout>
       </af:panelHeader>
     </af:form>
   </af:document>
 </f:view>
</jsp:root>


package nl.whitehorses.wls.backing;

import commonj.timers.Timer;
import commonj.timers.TimerManager;

import javax.faces.event.ActionEvent;
import javax.naming.InitialContext;
import javax.naming.NamingException;

import nl.whitehorses.wls.schedular.Batch1;
import nl.whitehorses.wls.schedular.Batch2;

import javax.faces.context.FacesContext; 
import javax.servlet.ServletContext;

public class TimerBean {


   private InitialContext ic = null;
   private TimerManager tm = null;

   private Timer batchRun1Timer = null;
   public Boolean batchRun1TimerIsRunning = false;
   private Timer batchRun2Timer = null;
   public Boolean batchRun2TimerIsRunning = false;


   public TimerBean() {
       try {
           ic = new InitialContext();
           tm = (TimerManager)ic.lookup("java:comp/env/tm/TimerManager");

          FacesContext ctx = FacesContext.getCurrentInstance();
          ServletContext servletContext = (ServletContext) ctx.getExternalContext().getContext();
        
          batchRun1Timer = (Timer)servletContext.getAttribute("batch1");
          batchRun2Timer = (Timer)servletContext.getAttribute("batch2");
          batchRun1TimerIsRunning = (Boolean)servletContext.getAttribute("batch1Running");
          batchRun2TimerIsRunning = (Boolean)servletContext.getAttribute("batch2Running");
          System.out.println("init end");

      } catch (NamingException e) {
           e.printStackTrace();
       }
   }

   public void timerManager(ActionEvent actionEvent) {
       // Add event code here...
       if ( tm.isSuspended() ) {
           tm.resume();       
       } else {
           tm.suspend();
       }
   }

   public void Batch1(ActionEvent actionEvent) {
       // Add event code here...
       if (  batchRun1TimerIsRunning ) {
             batchRun1Timer.cancel();
             batchRun1TimerIsRunning = false;
       } else {
              batchRun1Timer = tm.schedule(new Batch1(), 0, 10 * 1000);
              batchRun1TimerIsRunning = true;
       }
      
   }

   public void Batch2(ActionEvent actionEvent) {
       // Add event code here...
       if (  batchRun2TimerIsRunning ) {
             batchRun2Timer.cancel();
             batchRun2TimerIsRunning = false;
       } else {
              batchRun2Timer = tm.schedule(new Batch2(), 0, 10 * 1000);
              batchRun2TimerIsRunning = true;
       }
   }
  
   public String getTmStatus () {
       if ( tm.isSuspended() ) {
          return "TimerManager is stopped";       
       } else {
          return "TimerManager is running";       
       }
   }

   public String getBatch1Status () {
      Long time = batchRun1Timer.getScheduledExecutionTime();
      java.util.Date date = new  java.util.Date(time);
      if ( batchRun1TimerIsRunning ) {
        return "Batch1 scheduled time "+date.toString();
      } {
        return "Batch1 stopped";
      }
   }
  
   public String getBatch2Status () {
      Long time = batchRun2Timer.getScheduledExecutionTime();
      java.util.Date date = new  java.util.Date(time);
       if ( batchRun2TimerIsRunning ) {
         return "Batch2 scheduled time "+date.toString();
       } {
         return "Batch2 stopped";
       }   
   }


   public Timer getBatchRun1Timer(){
     return batchRun1Timer;
   }

   public void setBatchRun1Timer(Timer batchRun1Timer ){
     this.batchRun1Timer = batchRun1Timer;
   }

   public Timer getBatchRun2Timer(){
     return batchRun2Timer;
   }

   public void setBatchRun2timer(Timer batchRun2Timer ){
     this.batchRun2Timer = batchRun2Timer;
   }
}

Here is the example workspace.

WSM in Fusion Middleware 11G

2009-09-16T23:12:00.011+02:00

Probably you already knew the Web Service Manager of Soa Suite 10.1.3, The 10.1.3 version was mainly used in combination with Soa Suite because this was the only way to secure the BPEL and ESB Services. In FMW 11g Oracle changed WSM so it is fully integrated in all the Fusion Middleware components. Now you can use WSM in ADF, in the Services and References of Soa Suite and in the jax-ws services or proxy clients.
In FMW 11G you can also define your own ws-security policies ( just use a wizard in the EM website) or use the standard policies, So it can always comply to your security requirements.

In this blog entry I will show you how to setup FMW on Weblogic and define security on a BPEL service, call this service with an ADF Web Service Datacontol and a java web service proxy client.

Special thanks to Vishal Jain of Oracle who helped to solve the issues and explained how WSM works with keystores.

First we need to generate a keystore with a self signed certificate. Somehow certificates with generated with OpenSSL fails in FMW.
keytool -genkey -keyalg RSA -keystore C:\test_keystore.jks -storepass password -alias client_key -keypass password -dname "CN=Client, OU=WEB AGE, C=US" -keysize 1024 -validity 1460

Now here comes the trick , copy this keystore to fmwconfig folder ( domain_name/config ) of the soa suite domain

Go the Enterprise Manager Website where we can configure the just created keystore. We have to select the weblogic domain and go to the security menu / credentials.

Here we can change maps or passwords which will be stored in the cwallet.sso file. If you see the oracle.wsm.security map then you can delete this map. This map contains the keystore password.

Go the Security Provider Configuration menu item in the security menu where we will add the keystore to FMW
Press the Configure button in the keystore part of the screen.

Here we can add the keystore details. Use ./ as keystore path. This will fill the oracle.wsm.security map in the credentials menu.

Go back to the Credentials where we will add an extra entry in the wsm map. Create a new key basic.credentials with as username weblogic and with password weblogic1

Restart the Weblogic server.

Next part is to add a wsm policy to a BPEL Service.

Select the server policy you like to use and deploy this to the soa suite server.

Now we can make a jax-ws proxy client so we can test the policy. In this client we will use the matching client policy. If this fails check your libraries.


package nl.whitehorses.wsclient;

import java.util.Map;

import javax.xml.ws.BindingProvider;
import javax.xml.ws.WebServiceRef;

import oracle.webservices.ClientConstants;

import weblogic.wsee.jws.jaxws.owsm.SecurityPolicyFeature;

public class BPELProcess1_ptClient
{
 @WebServiceRef
 private static Bpelprocess1_client_ep bpelprocess1_client_ep;

 public static void main(String [] args)
 {
   bpelprocess1_client_ep = new Bpelprocess1_client_ep();
  
     SecurityPolicyFeature[] securityFeature = new SecurityPolicyFeature[] {
                      new SecurityPolicyFeature("oracle/wss10_message_protection_client_policy") };

     BPELProcess1 port = bpelprocess1_client_ep.getBPELProcess1_pt(securityFeature);
    
    
     Map reqContext = ((BindingProvider) port).getRequestContext();
     reqContext.put(ClientConstants.WSSEC_KEYSTORE_TYPE, "JKS");
     reqContext.put(ClientConstants.WSSEC_KEYSTORE_LOCATION, "C:\\test_keystore.jks");
     reqContext.put(ClientConstants.WSSEC_KEYSTORE_PASSWORD, "password");
     reqContext.put(ClientConstants.WSSEC_SIG_KEY_ALIAS, "client_key");
     reqContext.put(ClientConstants.WSSEC_SIG_KEY_PASSWORD, "password");
     reqContext.put(ClientConstants.WSSEC_ENC_KEY_ALIAS, "client_key");
     reqContext.put(ClientConstants.WSSEC_ENC_KEY_PASSWORD, "password");
     reqContext.put(ClientConstants.WSSEC_RECIPIENT_KEY_ALIAS, "client_key");
     System.out.println("output = " + port.process("aaaa"));
 
 }
}

If all went well then we can do same with a ADF Web Service Datacontrol.

To add the client policy select the DataControls.dcx and go to the structure window.

Here we can define web service security

Select the right client policy and in this case we need to override properties, press the button and fill in the recipient with your key alias. Else you will get a orakey error.

And at last deploy this webapplication with a ear profile to the Soa Suite server and test your webapp.

SSO with WebLogic 10.3.1 and SAML2

2009-09-14T00:42:00.008+02:00

In a previous blog entry I already explained how to setup Single Sign On (SSO) with SAML1.1. In this blogpost I do the same but then with SAML version 2 or SAML2 in Weblogic 10.3.1 server.
First we start with the SAML2 Identity Provider, in SAML1.1 this is called the source site. Because we can't do anything in the federation tab of the serve, we need to create a Credential Mapping Provider ( go to myrealm security, Providers , Credential Mappings. )
and choose the SAML2 credential mapping.

Fill the provider specific details and use the demoidentity keystore ( this is default)

Now we can go the Federation Services tab of the server configuration and create a SAML2 profile for this server, We need to save this to a file and import this later in the other SAML2 Service Providers.
The published site url is very important , choose url of this server , use http or https and add saml2 to this url. SAML needs this url to communicate with the other SAML services.

Second part of the SAML2 profile

Save this profile to a xml

Go the Identity provider tab and fill in these fields
Go to the second Weblogic server, this is called the Service provider or in SAML1.1 the destination. Here we need to create a new SAML2 Authentication provider ( Go to the myrealm Security realm , Providers and then Authentication )

Now we done this we can go the Federation Services Tab of this weblogic server and fill in this SAML2 profile. The published url is very important and it must match with the server url and have to end with saml2

Second part of this SAML profile

Save this metadata to a xml. This needs to be imported in the Credential Mapping Provider of the Identity Provider ( the first weblogic server).

Next step is to go the SAML2 Service Provider tab.
Go back to the SAML2 authentication provider where we will import the identity provider metadata xml.

Select the identity metadata xml.

You have to enable this and most important, fill in all the url's of your applications who needs SAML authentication.

Now we do the same for metadata xml of the service provider, We need to import this in the Credential Mapper provider of the Identity Provider
Select the Service Provider metadata xml

enable this Service Provider.

That's all

In this example I use http but it shoud also work with https and when it fails, please check your url's , don't mix localhost or pc name. Same for the domain name.

For more debug information in your server.log and set these java parameters in your setDomainEnv
set EXTRA_JAVA_PROPERTIES=-Dweblogic.debug.DebugSecuritySAMLAtn=true -Dweblogic.debug.DebugSecuritySAMLLib=true -Dweblogic.debug.DebugSecuritySAML2Service=true -Dweblogic.debug.DebugSecuritySAML2CredMap=true -Dweblogic.debug.DebugSecuritySAML2Atn=true %EXTRA_JAVA_PROPERTIES%

Starting SOA Suite Testcases from java

2009-08-25T21:51:00.005+02:00

In a previous blog I already explained how to unit test a Soa Suite 11g composite application. In that blog entry I create a Test Suite with a testcase but I had to start this testcase and watch the results of the test in the Enterprise Manager Website. In this blog I will start the TestSuite with the Testcases from the Soa Suite java API. This can be handy when you have a continious build system like Hudson or Apache Continuum. Now you can build your test in JDeveloper and run the test in the Continious Build System.
In this test I made a simple Test Suite with two testcases and deployed this to the Soa Suite Server.
Create a test project with the following libraries
And create a java class like this example class.


package nl.whitehorses.bpel.unit;

import java.util.Hashtable;
import java.util.List;

import javax.naming.Context;

import oracle.soa.management.facade.Locator;
import oracle.soa.management.facade.LocatorFactory;

import oracle.soa.management.util.TestSuiteFilter;
import oracle.soa.management.util.TestRunOptions;

import oracle.soa.management.facade.tst.TestSuite;
import oracle.soa.management.facade.tst.TestCase;
import oracle.soa.management.facade.tst.TestRunResults;
import oracle.soa.management.facade.tst.TestSuiteResult;
import oracle.soa.management.facade.tst.TestCaseResult;


public class StartUnitProcess {
 public StartUnitProcess() {
     super();

     Hashtable jndiProps = new Hashtable();
     jndiProps.put(Context.PROVIDER_URL, "t3://localhost:8001/soa-infra");
     jndiProps.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
     jndiProps.put(Context.SECURITY_PRINCIPAL, "weblogic");
     jndiProps.put(Context.SECURITY_CREDENTIALS, "weblogic1");
     jndiProps.put("dedicated.connection", "true");

     Locator locator = null;
     try {
         // connect to the soa server
         locator = LocatorFactory.createLocator(jndiProps);

         TestSuiteFilter testFilter = new TestSuiteFilter();
         testFilter.addSuiteName("HelloTest");
         String compositeDN = "default/Helloworld!1.0";
         List testSuites = locator.getTestSuites(compositeDN,testFilter);
      
         for (TestSuite testSuite : testSuites) {
             System.out.println("Found TestSuite name: "+testSuite.getName()+" description: "+testSuite.getDescription());
          
             List testcases = testSuite.getTestCases();
             System.out.println("Total TestCases: " +testcases.size());
         
             for (TestCase testCase : testcases) {
                 System.out.println("Contains TestCase: " +testCase.getName());
             }
          
             TestRunOptions testRunOptions = new TestRunOptions();
             testRunOptions.setTestRunId("123");
             testRunOptions.setTestRunName("name123");
          
             TestRunResults result =  locator.executeTestCases(compositeDN,testRunOptions,testcases);
             System.out.println("total errors: "+ result.getNumErrors() +
                                " status: "+ result.getStatus());

             List testSuiteResults = result.getTestSuiteResults() ;
             for (TestSuiteResult testSuiteResult : testSuiteResults) {
                 System.out.println("TestSuite name: "+testSuiteResult.getSuiteName()+
                                    " success: "+testSuiteResult.getNumSuccesses()  +
                                    " errors: "+ testSuiteResult.getNumErrors() );
                 List testCaseResults = testSuiteResult.getTestResults() ;
                 for (TestCaseResult testCaseResult : testCaseResults) {
                     System.out.println("TestCase name: "+testCaseResult.getTestName()+
                                        " status: "+testCaseResult.getStatus()   );
                 }                 
             }             
         }
     } catch (Exception e) {
         e.printStackTrace();
     }
 }

 public static void main(String[] args) {
     StartUnitProcess startUnitProcess = new StartUnitProcess();
 }
}

Here is an example of the result of invoking the TestSuite in java

HTC Hero ( Android ) Thetering

2009-08-17T23:08:00.023+02:00

This blog is about how to setup your PC and HTC Hero android phone, so you can use your phone as a proxy server. This is called Thetering.

First we need to download the latest HTC Sync Software. Use this url.
Now we can open the HTC Sync on your PC. You will see that the buttons are not enabled even when you connect your phone with an USB cable.

Connect your the USB cable so the HTC Hero and your PC are connected.

Open the status bar of your phone and press HTC Sync and watch how the buttons are accessible in your HTC Sync PC application.

When you take a look at your hardware then you will see an Android USB Device.

Download Proxoid for free from the Market ( on your HTC Hero ) and install this app on your phone.

Download the android utilities for your PC :
for 32 bits : http://www.baroukh.com/proxoid/proxoid-adb.zip
for 64 bits : http://www.baroukh.com/proxoid/proxoid-adb64.zip
and save it on your disk and unpack this in a folder.

Go to this folder

open check.bat or adb.exe devices to see the connected devices

open start-tunnel.bat or adb.exe forward tcp:8080 tcp:8080
open Proxoid on your phone and start Proxoid.

and set the proxy server in your favorite browser
that's all, happy browsing

CRUD operations with a Bind Entity variable in BPEL

2009-08-13T17:56:00.009+02:00

With Soa Suite 11G ( FMW 11G R1) you can now use the Bind Entity activity in a BPEL process, which can do your CRUD operations for you. This Bind Entity is connected to a web service reference, this WS has to have SDO types just like an ADF BC SDO service interface. Now you can use an normal Assign activity to retrieve or update data from the Entity variable instead of an invoking a lot of Partner Links.

First we need to make a SDO web service. For more details then this short description, see my previous blog or this blog of Andrejus .

I made an simple ADF BC Model project with an Employee viewobject based on the employees table in the HR sample schema.

Create a Service Interface on this Employees Viewobject and select all the basic operations.

JDeveloper 11G generates SDO types on this employees viewobject and generates a Web Service on this Application Module. We will use this WS in the BPEL process.

Create a new Service Interface deployment profile

Deploy this to a Weblogic Server

The Web Service is ready and we can create a new SOA Project. I use a XSD with a simple request and response. The input will be the EmployeeId and the BPEL process returns the lastname

We don't need use the ADF-BC service adapter, just add the Web Service Adapter to the Composite. Use the WSDL of the Employee WS in the WS Reference adapter

Wire the WS adapter reference to the BPEL process
Open the BPEL process and add a new variable

Select the partnerlink in the entity variable.

Select the Employee WS
Now we need to define the element in this variable. Select the Employees SDO element

Add the Bind Entity activity to the BPEL process, This will map the Primary Key on the just created variable.

Select the just created employee variable
Select the Primary Key Element of the Employee XSD. In my case is this EmployeeId

And use the BPEL request (input) variable as value to this PK column. This will lookup the right employee

We are ready with the configuration of the Bind Entity. We can now use Assign Activities to retrieve or update the Employee record. In my case I will get the lastname of the employee and return this as response

that's all , just deploy this to the Soa Server and test this in the EM website. Use for example 199

This returns Grant as lastname

Here you can download the test workspace

JDeveloper 11G improvements for the Mediator component

2009-08-02T14:10:00.007+02:00

With JDeveloper 11G FMW R1 Oracle made life a little bit easier when you are working with the Mediator component. In 10.1.3 the ESB Router can do a lot but you didn't have IDE support to configure this.
The first big change is the Assign option in the routing rules. In 10.1.3 you can change the header properties of a adapter by setting these values in the XSLT transformation of a routing.

In 11G you can't set a adapter property in a routing rule transformation. You need to do this in the assign option. This is a great feature, the transformation doesn't contain any hidden logica.

This assign wizard summarize all the possible header properties you can set. In 10.1.3 you have to search the internet what properties you can use.

The ESB XSLT header functions are now being replaced by the Mediator Get Functions. The Set functions are replaced by the Assign option.

In 11G you can create a Domain Value Map in JDeveloper. In 10.1.3 we had to do this in the ESB console, this is great for the DVM lookup XSLT function. You can use the looking glass button to select the right values.

The XSLT GetProperty function also summaries all the adapter properties.

In 10.1.3 we have a ESB request parameter to see the original request in the reply transformation. In 10.1.3 we have to do this all manually with JDeveloper 11G you have now an Include Request option in the reply Transformation.

In the XSLT editor you can use the request values in your reply transformation.

Using Shared Object in Soa Suite 11g with MDS

2009-07-22T23:41:00.023+02:00

Inspired by Eric Elzinga , who was wondering how MDS can work in Soa Suite 11g , I made some screenshots how you can use a XSD from a central MDS repository in your composite application. Clemens already blogged about re-using common metadata and he made a great ant utility to import or delete MDS files.
First I make a local MDS repository. If you install the Soa plugin you already have a seed folder in the integration folder. Under this folder create an new folder called apps. ( this have has to be apps else you will get a permission denied error ) . Under this apps folder we can create our own definitions.

To use my local SOA-MDS repository I create a new MDS File Connection

I want to re-use these common objects in every Soa project so I choose for the resource palette option

select the seed folder in the integration folder

Here we can see our common application objects.
Open the application resources window and open the adf-config.xml

Here we define a new metadata namespace with apps as path. And use the integration folder as metadata-path value.

We are ready to use these common objects in a mediator.. Here I will use a schema from the local MDS as input parameter for the mediator.

Import a new schema
Select the resource browser and here we can select our schema from the local MDS

I uncheck the Copy to project option, because this XSD already exists in the MDS

Our Project is ready but If we want to deploy this Soa project, we will receive a error, it can't find the schema. So we need to export the local MDS files to the SOA Suite database MDS.
To do this we have 2 options , the first option is to create a MAR deployment ( Application properties ) or do this with Ant.
I stripped the Clemens ant project so this ant build file has only two tasks , add and delete. It uses the adf-config.xml ( config folder) for the location of the target MDS and I use the local MDS as source.

Here is the target adf-config.xml which is located in the config folder

Change the build.properties so it matches your environment

This will import your local MDS object to the remote MDS. After this you can deploy your Soa Suite project.
Here you can download my ant project. Thanks to Clemens.

MDS repository for ADF 11G

2009-07-21T21:07:00.007+02:00

With Fusion Middleware 11G the MDS repository plays a important role for ADF customizations and SOA shared objects. In this blog I explain how you can create a MDS database repository, deploy customizations to this MDS database and what you can do with MDS in the Enterprise manager website.

First we need to download the RCU repository creation utility and install a MDS repository in a Oracle Database.
Use a sysdba account

We only have to select the Metadata Services and provide a prefix

Next we need to install Weblogic with the Soa, Webcenter or Application development runtime extension. This extension gives us the Enterprise Manager website where we can configure the MDS repository. Select your Weblogic domain and select the MDS menu option.

Register the just created MDS repository. In my case I will call this repository adf

The EM website automatically create a datasource which we can use later.

If we have an ADF application with customizations and we deploy this to the Weblogic Server then JDeveloper detects the MDS repository

JDeveloper automatically creates a new MDS partition and uses your ear deployment name as partition name. It also uses the just created datasource to fill the MDS database. Just press deploy

When we go back to the EM website we can see the just created MDS partition.

The EM website also provides MBeans with some MDS operations.

For example we can query the partitions of a MDS repository.
When we select our just deployed ADF application and go to the MDS menu option, we can administer the MDS partition of this application.

We can export the MDS customization and import this to a different Weblogic server which has the same ADF application.
At last we can take a look at the MDS repository, here we can see that all the customizations entries are registered in the database. But the customizations xml are still located on the server, a bit strange I would suspect that with a MDS repository in the database that everything is loaded in the database.

Using an EJB Service / Reference in Soa Suite 11G

2009-07-18T16:58:00.029+02:00

With Oracle Soa Suite 11G ( FMW11G R1 ) we can finally use the EJB adapter. This adapter can be used as a service or reference. This means we can start a BPEL process by calling a EJB session method or use an EJB to lookup or change data. Using an EJB as service or reference is very cool because it is fast ( RMI ) and we can use the same EJB's ( Multi Tier ) for your Java Web applications and your composites ( Who needs the Database Adapter now?)

Here is a picture of the composite application with an EJB adapter as Service and Reference.

In this blog I will explain you first, how the SDO EJB is created and then how we use this as a Reference and as a Service

Create SDO Eclipse EJB

First step is to create an EJB entity with Eclipselink as persistence provider. For this example I used the Employees table of the HR schema. Next step is to create an EJB Session Bean.

Here is an overview of my EJB model project.

Select the Session Bean and generate a service interface on this

Now it goes totally wrong with the JDeveloper wizard 11G R1.

First step is fix the packages names of the SDO and SDOImpl classes, then we can refactor these classes and move it to the entities package. With this as result.

Select the session bean again and generate for the second time the service interface. Now we will get the WSDL.

Move the EJB WSDL and XSD to the Session bean package. With this as result.

Open the Entity XSD and change the target namespace and xmlns namespace to the same name as the package name in my case /nl/whitehorses/hr/ejb/entities/.

before

after

Open the XSD of the WSDL and import the entity schema and fix the namespace.
Change /nl.whitehorses.hr.ejb.services/ to /nl/whitehorses/hr/ejb/services/ in every java, XSD or WSDL file

Create a Datasource to the HR schema in Weblogic and make sure you are using the XA Oracle Driver and target this Datasource to the Soa suite server.

Deploy the EJB to the Soa Suite instance.

Using the SDO Ejb as a reference in Soa Suite 11g

Open the composite application and drag the EJB adapter on the reference part of the composite.

Fill in the JNDI of the EJB on soa suite server , select the EJB jar and provide the Remote EJB interface class name.

Select the WSDL , Go the classes folder of the EJB model project and select the Session bean WSDL. This will copy the WSDL and the XSD to the local project folders and also import the jar. That's all , now you can invoke this in a BPEL process.

Using the SDO Eclipselink Ejb as a Service in Soa Suite 11g

We can use the same EJB as starting point of our composite application. This time Soa Suite only uses the interface and does nothing with the Session Bean methods.

Drag the EJB adapter to the Services side of the composite overview.

The Service ID is very important because we need this name in serviceFactory.createService, The rest is the same as in the reference part. Use this EJB Service in a BPEL process.

Now we only have to make a simple java class where we call this EJB composite service.


package nl.whitehorses.soa.ejb.service;

import commonj.sdo.helper.DataFactory;

import java.util.Properties;

import javax.naming.Context;
import javax.naming.InitialContext;

import nl.whitehorses.hr.ejb.entities.EmployeesSDO;
import nl.whitehorses.hr.ejb.services.HrEmployeeEJB;

import oracle.integration.platform.blocks.sdox.ejb.api.SOAServiceFactory;
import oracle.integration.platform.blocks.sdox.ejb.api.SOAServiceInvokerBean;

import oracle.jbo.common.sdo.SDOHelper;


public class callejb {
public callejb() {
super();
}

public static void main(String[] args) {
try {
   // very important to load every schema you use in the EJB
   try {
       SDOHelper.INSTANCE.defineSchema("nl/whitehorses/hr/ejb/entities/", "EmployeesSDO.xsd");
       SDOHelper.INSTANCE.defineSchema("nl/whitehorses/hr/ejb/services/", "HrEmployeeEJBBeanWS.xsd");


   } catch (Exception ex) {
       ex.printStackTrace();
   }

   Properties props = new Properties();
   props.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");

 // soa suite server
      props.put(Context.PROVIDER_URL, "t3://localhost:8001");
   InitialContext ctx = new InitialContext(props);
   SOAServiceInvokerBean invoker = (SOAServiceInvokerBean)ctx.lookup("SOAServiceInvokerBean#oracle.integration.platform.blocks.sdox.ejb.api.SOAServiceInvokerBean");

   //--  Create a SOAServiceFactory instance
   SOAServiceFactory serviceFactory = SOAServiceFactory.newInstance(invoker);

// use the Service Id in the EJB service adapter
   HrEmployeeEJB hrEmployeeEJB =  serviceFactory.createService("EmployeeService", HrEmployeeEJB.class);



   EmployeesSDO employeesSDO =  ( EmployeesSDO )DataFactory.INSTANCE.create(EmployeesSDO.class);
   employeesSDO.setDepartmentId(1L);
   employeesSDO.setEmail("aaa@aa.nl");
   employeesSDO.setEmployeeId(1L);
   employeesSDO.setFirstName("edwin");
   employeesSDO.setJobId("aa");
   employeesSDO.setLastName("biemond");
   employeesSDO.setPhoneNumber("123");
   employeesSDO.setSalary(1000);

   EmployeesSDO resultEmployeesSDO = hrEmployeeEJB.persistEmployeesSDO(employeesSDO);

} catch (Exception ex) {
   ex.printStackTrace();
}
}


}

Here is the result of a EJB service instance.

Here the link to official EJB adapter documentation. ( This can be a lot better )
Download here the EJB project I used and here the Soa Suite project.

Using AQ ( JMS Text message ) in WLS 10.3.1

2009-07-13T07:30:00.001+02:00

In Oracle Application Server 10.1.3 ( OC4J) you can use OJMS to expose AQ with JMS (text) Message as type and use it as a normal JMS Queue or Topic in Soa Suite or a Message driven Bean. See my previous blog for more details. With the release of Weblogic 10.3.1 ( WLS FMW11g ) we can do the same with a Foreign JMS Server. Before 10.3.1 we had to make a startup class to achieve this.
First create a Queue and Queue table with SYS.AQ$_JMS_MESSAGE as payload type in your Oracle Database and make sure you enable enqueue /dequeue on this Queue.
In Weblogic we have to create a JMS server and a JMS module.
Create a new JDBC datasource with a schema user which can enqueue or dequeue the just created queue. Use the XA JDBC driver, with this driver you can use global and local transactions. with NON-XA driver you can only use local transactions, this can be problem when you want to use this Queue in Soa Suite.
Select your JMS module in the WLS Console and create a new Foreign Server.
Open the Foreign Server so we can configure this AQ server.
Change JNDI Initial Context Factory to oracle.jms.AQjmsInitialContextFactory and we have to provide the jndi datasource name in the JNDI Properties field, For Example datasource=jdbc/scottDS

Create a JMS connection factory
As local JNDI name you can choose what you like. For Remote you have to choose one of these values. QueueConnectionFactory, TopicConnectionFactory, ConnectionFactory, XAQueueConnectionFactory, XATopicConnectionFactory or XAConnectionFactory

Now we can create a new Destination.
As Local JNDI name you can choose any name but as Remote JNDI it needs to start with Queues or Topics after that add a / with the database queue or topic name.

We are ready to use this AQ Queue in a Soa Suite Composite application. Where we will use the JMS adapter.
Select Oracle Advanced Queuing as OEMS

and select the Foreign Server Destination.

For more Weblogic AQ JMS details see the official documentation.

ADF web applications and Oracle Enterprise Manager a perfect match

2009-07-05T12:45:00.006+02:00

In the release of Oracle Fusion Middleware 11g the old Enterprise manager website is back. And this EM website is the bomb for ADF web applications. ( Well done) . In FMW11g EM you can off course do the standard things like deploy and undeploy, but Oracle added some extra to this site. You can now the measure performance of your ADF BC applications modules, Servlets , Web application and Task Flows. Change or tune the BC4J config parameters , change MDS or security settings ( add WSM policies ) or change the endpoint of your web service client.
Too bad this EM website is not available in the internal WLS of JDeveloper 11g ( It can be handy for performance tuning).
But we can install weblogic 10.3.1 and add the ADF Runtime and EM website to this WebLogic Domain. For this we need to download Application Development Runtime

Create a new WebLogic Domain and enable the Oracle Enterprise Manager / JRF options

When you want to deploy your ADF application to this WLS server then you probably missing some java libraries. To solve this change your war deployment so the required jars are added to the web-inf/lib.

We need to deploy the ear and not the war else the adf connections and security settings are not deployed. You can only deploy the ear from the application menu.

Here is a picture of the EM website ( http://localhost:7001/em ) where we can see our ADF applications

Overview of the deployed ADF application.

we can go the ADF settings by selecting ADF menu option

Here we can see the ADF BC AM performance
Overview of the Task Flow performance

We can change the BC4J configuration properties.

My application has a web service client and here we can change the endpoint or add some WS-Security policies.

And off course see the total ADF application performance.

Customize and personalize your JSF pages with MDS / FMW 11G

2009-07-02T19:00:00.003+02:00

In a previous post ( TP4 ) I already showed how you an application user can personalize the JSF pages of the ADF 11G application and that ADF will persists these username, role or site changes in a file or database. In TP4 I had to configure MDS manually. With the July release of JDeveloper 11g we can do this with a few wizards.

First we need to enable Customizations the viewcontroller project options. Enable User and Seeded Customizations
Open the adf-config.xml where we have to select the type of customization. We can choose user , role or site. You can always make your own customization class and select this class instead of the default options.

I choose for UserCC, this means I need to enable and configure ADF Security

Select Tag Configuration and choose for example column. This mean the user can change the properties of a table column.
In this case I want to enable that the user can change the column order and the width of the column.

The last step is to configure MDS or the Metadata repository. for this we need to go the application properties.

Make a new MAR deployment profile.

Select the MDS option where we can select the just created MAR profile.
Finally we can run your ADF application and change the column order of a ADF table. We can see these changes on our file system. ( JDEV_USER_HOME JDeveloper\system11.1.1.1.33.54.07\o.mds.dt\adrs )

Unit Test your composite application with Test Suite in Soa Suite 11g

2009-07-01T18:51:00.011+02:00

With the release of Soa Suite 11g you can make a unit tests to test your Soa Composite Application. In this blog I will show all the steps you have to do, to make a successfull unit test. For this I made a simple Composite application which retrieves the last name of an employee. The Composite application with an exposed BPEL process has EmployeeId as input and BPEL invokes a database adapter to get the Employee’s lastname and return this as response.
First we start by making a XML schema with a input and response element

Add a BPEL process to the Composite xml and use the above XML schema as input and output and expose this BPEL as a webservice. After this I created a Database adapter which has employeeId as input and returns the lastname of the employee. Add a wire between the BPEL process and the Database adapter so I can invoke this adapter in the BPEL process

Open the BPEL process and add the invoke operation. I use an assign operation to fill the input variable of the database adapter and an other assign operation to retrieve the lastname and add this to the response of the BPEL process

The employee Composite application is finished and now I can create a new Test Suite.

The Test Suite creates a copy of the Composite xml.

Select the Exposed Service where we can create a new input request

In this dialog I can generate a sample xml and change the EmployeeId with a real value

Select the wire of the database adapter where we add a input and output assertion so the unit test can compare this to the adapter values

First we create the input assert, use the generate Sample button and change the employeeId value

Do the same for the output of the Database adapter.
Do the same for the exposed Service and the BPEL process

In this wire I want to compare the output of the BPEL process with the Callback Assert.

Now we only have to deploy the whole composite application. The just created Test Suite is part of this deployment.

To test this unit test I have to go to the new improved EM website of the Soa Suite server where I can select the Employee Composite

Select the Unit Test tab of the Employee Composite and select the testcase and press the Execute Button

Take a look at the Test Runs to see the results of the test.

We can see the test4 is successfull and the assertions are succesfull too.

Finally we can compare the expected and actual Value by selecting an assertion

That’s all

WS security in OSB

2009-06-24T20:55:00.017+02:00

In OSB you can protect your WSDL proxy services with XML Signature / encryption, authentication or your own custom ws-policy. In this blog entry I will give you all the information how to do this.
First we start by adding a standard OSB WS-Policy. Open the WSDL of a proxy service where we add for example the signing policy. We always need to add wsp:UsingPolicy element else OSB won't detect the wanted security policy


<?xml version="1.0" encoding="UTF-8"?>
<definitions targetNamespace="http://saml.ws.whitehorses.nl/"
name="HelloWorldService" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://saml.ws.whitehorses.nl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy">
<wsp:UsingPolicy wsdl:Required="true" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"/>
<types>
 <xsd:schema>
  <xsd:import namespace="http://saml.ws.whitehorses.nl/" schemaLocation="Helloworld.xsd"/>
 </xsd:schema>
</types>

Add the Signing policy to a operation or put this in a other part of the WSDL see this url for more information. In this case I can use wsp:Policy with a PolicyReference and the URI is policy:Sign.xml . If you want encryption then you can use policy:Encrypt.xml as URI or use policy:Auth.xml for ws authentication. Off course you can combine policies.


<binding name="HelloWorldServiceSoapHttpPortBinding" type="tns:HelloWorldService">
 <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
 <operation name="sayHello">
       <wsp:Policy>
         <wsp:PolicyReference URI="policy:Sign.xml"/>
       </wsp:Policy>

You don't have to use the OSB standard policies, you can also add your own ws-policy ( in OSB 10.3 you can only use the policy definition of WLS 9, so don't expect you can make policies which uses the 2005 or 2007 WS-Security standard). Here is a example of a custom policy.


<?xml version="1.0"?>
<wsp:Policy wsu:Id="X509v3"
xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<sp:InitiatorToken>
 <wsp:Policy>
  <sp:X509Token
   sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient">
   <wsp:Policy>
    <sp:RequireThumbprintReference />
    <sp:WssX509V3Token10 />
   </wsp:Policy>
  </sp:X509Token>
 </wsp:Policy>
</sp:InitiatorToken>
<sp:RecipientToken>
 <wsp:Policy>
  <sp:X509Token
   sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/Never">
   <wsp:Policy>
    <sp:RequireThumbprintReference />
    <sp:WssX509V3Token10 />
   </wsp:Policy>
  </sp:X509Token>
 </wsp:Policy>
</sp:RecipientToken>
<sp:AlgorithmSuite>
 <wsp:Policy>
  <sp:TripleDesRsa15 />
 </wsp:Policy>
</sp:AlgorithmSuite>
<sp:Layout>
 <wsp:Policy>
  <sp:Strict />
 </wsp:Policy>
</sp:Layout>
<sp:IncludeTimestamp />
<sp:OnlySignEntireHeadersAndBody />
</wsp:Policy>

The value of the wsu:Id attribute if important for the WS policy reference in the WSDL of the proxy service


<binding name="HelloWorldServiceSoapHttpPortBinding" type="tns:HelloWorldService">
 <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
 <operation name="sayHello">
       <wsp:Policy>
         <wsp:PolicyReference URI="policy:X509v3"/>
       </wsp:Policy>

In this case the URI has policy:X509v3 as value

The next step is to make some keystores for WebLogic and OSB. We need to create 509 v3 certificates and import these certificates in a java 1.6 keystore for signing and encryption.
We need to have 509 version 3 certificates because we need the SubjectKeyIdentifier extension. This is only supported in version 3 of 509 and only OpenSSL can generate these certificates.

You can use self signed v3 certificates, for more info see this Glen Mazza's weblog. I'll use a CA.
#first make a CA request
C:\tools\OpenSSL\bin\openssl genrsa -des3 -out C:\projecten\certs2\ca.key 4096 -rand random
#self sign our CA certificate
C:\tools\OpenSSL\bin\\openssl req -new -x509 -days 3650 -config C:\projecten\certs2\ca.conf -key C:\projecten\certs2\ca.key -out C:\projecten\certs2\ca.crt

# make serial.txt file in C:\projecten\certs2\ and add 01 in this file

# make an empty index.txt file in C:\projecten\certs2\

Download the ca.conf which will be used to sign the certificates

# generate a server request and use servername with the domain name as common name CN
c:\tools\openssl\bin\openssl genrsa -des3 -out C:\projecten\certs2\server.key 4096
c:\tools\openssl\bin\openssl req -newkey rsa:1024 -nodes -keyout C:\projecten\certs2\server.key -out C:\projecten\certs2\server.csr -config C:\projecten\certs2\ca.conf

# sign the server request with your CA key
c:\tools\openssl\bin\openssl ca -in C:\projecten\certs2\server.csr -out C:\projecten\certs2\server.pem -keyfile C:\projecten\certs2\ca.key -cert c:\projecten\certs2\ca.crt -config C:\projecten\certs2\ca.conf

# export server
c:\tools\openssl\bin\openssl pkcs12 -export -inkey C:\projecten\certs2\server.key -in C:\projecten\certs2\server.pem -out C:\projecten\certs2\server.p12 -name server

C:\java\jdk160_05\bin\keytool -importkeystore -destkeystore C:\projecten\certs2\keystore.jks -deststorepass welcome -srckeystore C:\projecten\certs2\server.p12 -srcstorepass welcome -srcstoretype pkcs12
C:\java\jdk160_05\bin\keytool -list -keystore C:\projecten\certs2\keystore.jks -storepass welcome
C:\java\jdk160_05\bin\keytool -exportcert -alias server -storepass welcome -keystore C:\projecten\certs2\keystore.jks -file C:\projecten\certs2\server.cer
C:\java\jdk160_05\bin\keytool -printcert -file C:\projecten\certs2\server.cer

# generate client request
c:\tools\openssl\bin\openssl genrsa -des3 -out C:\projecten\certs2\client.key 4096
c:\tools\openssl\bin\openssl req -newkey rsa:1024 -nodes -keyout C:\projecten\certs2\client.key -out C:\projecten\certs2\client.csr -config C:\projecten\certs2\ca.conf

# sign client request
c:\tools\openssl\bin\openssl ca -in C:\projecten\certs2\client.csr -out C:\projecten\certs2\client.pem -keyfile C:\projecten\certs2\ca.key -cert c:\projecten\certs2\ca.crt -config C:\projecten\certs2\ca.conf

# export client
c:\tools\openssl\bin\openssl pkcs12 -export -inkey C:\projecten\certs2\client.key -in C:\projecten\certs2\client.pem -out C:\projecten\certs2\client.p12 -name client

C:\java\jdk160_05\bin\keytool -importkeystore -destkeystore C:\projecten\certs2\keystore.jks -deststorepass welcome -srckeystore C:\projecten\certs2\client.p12 -srcstorepass welcome -srcstoretype pkcs12
C:\java\jdk160_05\bin\keytool -list -keystore C:\projecten\certs2\keystore.jks -storepass welcome
C:\java\jdk160_05\bin\keytool -exportcert -alias client -storepass welcome -keystore C:\projecten\certs2\keystore.jks -file C:\projecten\certs2\client.cer
C:\java\jdk160_05\bin\keytool -printcert -file C:\projecten\certs2\client.cer

# make a truststore with the ca and the public keys
C:\java\jdk160_05\bin\keytool -import -file c:\projecten\certs2\ca.crt -alias ca -trustcacerts -keystore C:\projecten\certs2\trust.jks -storepass welcome -keypass welcome
C:\java\jdk160_05\bin\keytool -import -file C:\projecten\certs2\client.cer -alias client -keystore C:\projecten\certs2\trust.jks -storepass welcome -keypass welcome
C:\java\jdk160_05\bin\keytool -import -file C:\projecten\certs2\server.cer -alias server -keystore C:\projecten\certs2\trust.jks -storepass welcome -keypass welcome
C:\java\jdk160_05\bin\keytool -list -keystore C:\projecten\certs2\trust.jks -storepass welcome

The next step is to configure Weblogic. First we add the new keystores and configure SSL and add a new PKI Credential mapping provider. The PKI Credential mapping provider will be used by OSB for the XMLsignature and encryption. The trust keystore will be used to check if the signer certificate is trusted.
Go to the OSB server in the WLS console
In the keystore tab we will add our keystores

In the SSL tab we will use the server certificate which has the server + domain name as Common name so Internet explorer won't complain that the certificate and server name does not match.

Select the myrealm Security Realm where we will add a new PKI Credential Mapping provider

In the Providers tab we will create a new PKI Credential Mapping
Select the just created PKI credential mapping and fill the values in the Provider Specific tab. Use the keystore and not the trust keystore for this

We are finished in the Weblogic Console and we can go the OSB console where we have to create a new Service Key provider and configure the Proxy service so it uses this provider.

Create a new Service Key provider. This how it looks like in the Workshop but this does not work because eclipse can't retrieve the certificates of the PKI credential mapping provider.

So we have to use the OSB console to add the right certificate for signing and encryption to the Service Key Provider.
Now we see the certificates of the Weblogic PKI Credential mapping. If you don't see this then probably you don't use 509 version 3 certifcates.

The last step is to configure the proxy service. Here we have to disable XOP/MTOM support
And select the Service Key Provider

Now we can test the proxy service by invoking the WS and selecting the Service Key Provider.

With this as result

And this is how the WSDL with signing looks like

That's all.

If you want to use OSB 10.3 security with Soa Suite 11g R1 then you should read this 11g documentation, This explains how to change the OSB encrypt and sign policy so it works with FMW 11g.

OSB & ESB Performance comparison

2009-06-15T21:07:00.016+02:00

With the release of OSB 1.3.1 with JCA adapter support I can finally compare the OSB with the ESB. I will run this performance test on my Dell laptop ( Core2Duo T9400 2.53 GHz with 3,5 Gb memory ) and try to use the same components in the OSB and the ESB. For example I will use a memory JMS Queue in the Oracle Application server as starting point for the ESB and a file based JMS Queue in WLS as starting point for the OSB process. Both OSB and ESB processes has to fill the same four tables in the Oracle 11G database and they will use the same Toplink database mappings.
For the test I will disable the JMS adapter in the ESB console or stop the queue consumption in the WLS console. Then fill the Queues and start the Service Bus processes . Before the test I will do some test runs so I know everything is alright and the Service Bus is warmed up.
Here is a picture of the ESB process. This process reads the Queue and pass it asynchronous to the next Router. This message with a XML anytype element is transformed with XSLT to a specific message schema and the last Router transforms it to the database adapter XSD.

The OSB process works almost the same as the ESB process but in the OSB I will use XQuery instead of XLST and use Proxy Services as Routers and a Business service as Database Adapter.
Here you see a process schema of Messaging proxy service. It start with a PipelinePair to do some XSD validation on the incoming message. Then the Proxy Service determines the message type in in the RouteNode, do the first XQuery transformation to make the specific message XML and start the next specific Message Proxy Service.

The specific message Proxy Service validates the XML and in the RouteNode ( Mapped to the JCA database adapter Business Service ) the next XQuery takes place, so the Business Service get the right XML for the Toplink database mapping.

Here are my test results
OSB 10.3.1 with JRocket JVM

Total Messages	Size Message in KB	Time in Seconds With validation	Time in Seconds
10	1100	9	5
20	1100	19	18
10	2000	12	10
20	2000	35	28
10	2700	15	12
1000	4	19

ESB 10.1.3.4 MLR7

Total Messages	Size Message in KB	Time in Seconds With validation	Time in Seconds
10	1100	15	14
20	1100	33	28
10	2000	23	18
20	2000	48	44
10	2700	35	28
1000	4	22

Conclusion

The OSB is the overall winner with 15% a 90% better performance than the ESB. Off course this is not the best testcase and there are other areas of the Service Bus where you can do tests for, but with this case the OSB is much faster especially with big messages ( even with JRockit ) . This OSB process does even more then the ESB process, the OSB process returns a message with the result of the database adapter and put this message in a WLS Queue.
Don't know why OSB has a better performance, maybe Weblogic is faster or the ESB instance logging is the problem. In the next Soa Suite patchset 10.1.3.5, I can test the ESB processes on WebLogic server and compare this with these results.

Using AQ in an OSB 10.3.1 Proxy Service

2009-06-11T00:15:00.013+02:00

In my previous blogpost I already showed you how to use a JCA Database adapter in a Business Service. In this blog I will use the AQ resource adapter in a OSB 10.3.1 Proxy Service. To make this work I use the Oracle Workshop for the OSB configuration and JDeveloper 10.1.3.4 for AQ adapter configuration. I heard from Oracle that in one of the next 11g releases you can do this all in JDeveloper.
We start in the WLS console of the OSB Server. Go to the deployments and find the AqAdapter resource adapter.
Open the AqAdapter and select the configuration Tab where we will create a new outbound connection pool.
Provide the JNDI name, I'll use the JDeveloper name convention. eis/AQ/xxxx , xxxx is the database connection name in JDeveloper.

Give the resource adapter plan a unique name and save this AQ plan.

Select the just created JDNI configuration.

We have provide the xADatasourceName. This is a datasource of WLS which connects to a Oracle schema user which has access to the AQ queues. Or you can provide the jdbc url , username and password.

We are finished with the Weblogic configuration and we can switch to JDeveloper 10.1.3.4 where we will make the AQ configuration files which we have to import in our OSB project.
Make a new ESB project where we will add the AQ adapter to the ESB configuration. The JNDI name in the AQ adapter wizard must match with the JNDI eis name of the AQ resource adapter in the WLS console.

This OSB proxy service read from the queue so we need to dequeue.

Browse or provide the schema /queue name

And select a XSD which matches with the AQ messages.

Delete the router service we don't need this.

The last part is to use this AQ queue in a OSB proxy service, Start the Oracle workshop and import AQ wsdl's and schema's into your OSB project.

Create a new Proxy service and use the AQ WSDL. OSB will detect the JCA adapter configuration.

Now we only have to provide the JNDI name in my case eis/AQ/xxxxx
That's all for the AQ configuration.