• an Apache ODE instance (preferably deployed in Tomcat)
• Maven 2.2.0
• JDK 1.6
• Netbeans 6.8,
• Mule CE 2.2.2-SNAPSHOT

Of course, it might work with other version but these are the versions I used.

Step 1: Create a running BPEL process

The first step is to create a running BPEL example. I use the latest version of Netbeans for that and
this post. To make use of the SOA wizards in the new Netbeans you have to enable this as an extension as described here.
To create the BPEL example perform the following steps:

1. Creating a new BPEL module named 'TextModule'
   
2. Add a WSDL to the project

Add a WSDL that describes the web service (remark: I wasn't able to create a document-literal web service with the wizard in Netbeans so I edited the source by hand afterwards). Here is my WSDL.

3. Add a BPEL process to the module, name it 'txtLengthProcess'
   

   This created process is empty so add functionality to it by following the guidelines as in this post. I ended up with the following process diagram:
   
   The mapping in the assignment step looks like this:
   
   I created the necessary variables to assign the values to in the 'receive' and 'reply' step.

4. Create a file 'deploy.xml'
   My file has the following content:
   PLAIN TEXT
   XML:

   1. <?xml version="1.0" encoding="UTF-8"?>
   2. <deploy xmlns="http://www.apache.org/ode/schemas/dd/2007/03"
   3.     xmlns:pns="http://www.redstream.nl/TxtLengthProcess"
   4.     xmlns:wns="http://www.redstream.nl/TxtLengthService">
   5.  
   6.     <process name="pns:TxtLengthProcess">
   7.         <active>true</active>
   8.         <provide partnerLink="TxtLengthPartnerLink">
   9.             <service name="wns:TxtLengthServiceService" port="TxtLengthServicePort"/>
   10.         </provide>
   11.     </process>
   12. </deploy>

5. Deploy it to the Tomcat instance that is running Apache ODE
   To deploy the process create a directory named 'TxtLengthService' under '/webapps/ode/WEB-INF/processes'. Copy the three files (deploy.xml, TxtLengthProcess.bpel and TxtLengthService.wsdl) to this directory. When your deployment was successful you’ll see the 'TxtLengthService.wsdl' at http://localhost:8080/ode/services/listServices:
   
6. (Optional) you can test the service with SoapUI
   With a successful request-response you will get the following result:
   

If you want more details on how to set up a Apache ODE service have look here. It goes into more detail then I am in this post.

Step 2: Generate Java client for web service to start ODE process

We use Metro for this because we had some bad experiences when using CXF for this. It is described here how to do this in combination with Maven.
I created a new Maven project with this 'pom.xml'.
When the client is generated you can test it with a test class like this:

PLAIN TEXT
JAVA:
1. package nl.redstream.ws.test;
2.  
3. import nl.redstream.txtlengthservice.TxtLengthService;
4. import org.junit.Test;
5.  
6. /**
7. *
8. * @author pascal
9. */
10. public class TestService {
11.  
12.     @Test
13.      public void testIt()
14.     {
15.         TxtLengthService service = new TxtLengthService();
16.  
17.         String value = service.getTxtLengthServiceSOAP11PortHttp().txtLengthOperation("RedStream");
18.  
19.         System.out.println("result = " + value);
20.     }
21. }

Step 3: Create the Mule project

To let Mule call the BPEL process I created a new Maven project that is able to test the call with a Mule client. The project is based on this 'pom.xml'.
The used 'ode-test-config.xml' looks like:

PLAIN TEXT
XML:
1. <?xml version="1.0" encoding="UTF-8"?>
2. <mule xmlns="http://www.mulesource.org/schema/mule/core/2.2"
3.        xmlns:spring="http://www.springframework.org/schema/beans"
4.        xmlns:test="http://www.mulesource.org/schema/mule/test/2.2"
5.        xmlns:vm="http://www.mulesource.org/schema/mule/vm/2.2"
6.        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
7.        xsi:schemaLocation="
8.        http://www.mulesource.org/schema/mule/core/2.2 http://www.mulesource.org/schema/mule/core/2.2/mule.xsd
9.        http://www.mulesource.org/schema/mule/test/2.2 http://www.mulesource.org/schema/mule/test/2.2/mule-test.xsd
10.        http://www.mulesource.org/schema/mule/vm/2.2 http://www.mulesource.org/schema/mule/vm/2.2/mule-vm.xsd
11.        http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd">
12.  
13.     <model name="mule-ode">
14.         <service name="start">
15.             <inbound>
16.                 <vm:inbound-endpoint path="msg-in" synchronous="true"/>
17.             </inbound>
18.             <component class="nl.redstream.mule.BpelProcessClient" />
19.         </service>
20.     </model>
21. </mule>

The created component class that handles the call to the SOAP client looks like:

PLAIN TEXT
JAVA:
1. package nl.redstream.mule;
2.  
3. import nl.redstream.txtlengthservice.TxtLengthService;
4.  
5. /**
6. *
7. * @author pascal
8. */
9. public class BpelProcessClient {
10.  
11.     public String callProcess(String request) {
12.         return new TxtLengthService().getTxtLengthServiceSOAP11PortHttp().txtLengthOperation(request);
13.     }
14. }

And the used test class looks like:

PLAIN TEXT
JAVA:
1. package nl.redstream.mule;
2.  
3. import org.junit.Test;
4. import org.mule.api.MuleException;
5. import org.mule.api.MuleMessage;
6. import org.mule.module.client.MuleClient;
7. import org.mule.tck.FunctionalTestCase;
8.  
9. public class BpelProcessClientTest extends FunctionalTestCase {
10.  
11.     private MuleClient client = null;
12.    
13.     protected MuleClient getClient() {
14.         try {
15.             if (client == null) {
16.                 client = new MuleClient();
17.             }
18.         } catch (MuleException e) {
19.             throw new RuntimeException(e);
20.         }
21.         return client;
22.     }
23.  
24.    protected final String getConfigResources() {
25.         return "config/ode-test-config.xml ";
26.     }
27.    
28.     @Test
29.     public void testBpelTest() throws MuleException
30.     {
31.         MuleMessage msg = getClient().send("vm://msg-in", "123456789012345", null);
32.         System.out.println("payload = " + msg.getPayload());
33.     }
34. }

When the test class is executed this results in the following output:

**********************************************************************
* Mule ESB and Integration Platform *
* Version: 2.2.2-SNAPSHOT Build: 15252 *
* MuleSource, Inc. *
* For more information go to http://mule.mulesource.org *
* *
* Server started: 12/17/09 8:34 PM *
* Server ID: 3d3eb71b-eb43-11de-bca6-7b92b51f04e0 *
* JDK: 1.6.0_17 (mixed mode) *
* OS encoding: MacRoman, Mule encoding: UTF-8 *
* OS: Mac OS X (10.6.2, x86_64) *
* Host: macbook-van-pascal-alma.local (192.168.1.204) *
* *
* Agents Running: None *
**********************************************************************
INFO 2009-12-17 20:34:50,730 [main] org.mule.module.client.MuleClient: Using existing MuleContext: org.mule.DefaultMuleContext@1d6b6c55
INFO 2009-12-17 20:34:50,756 [main] org.mule.transport.vm.VMMessageDispatcher: Connected: endpoint.outbound.vm://msg-in
payload = 15
INFO 2009-12-17 20:34:51,784 [main] org.mule.transport.vm.VMConnector: Removing listener on endpointUri: vm://msg-in
INFO 2009-12-17 20:34:51,784 [main] org.mule.transport.vm.VMMessageReceiver: Disconnected: VMMessageReceiver{this=5a56182f, receiverKey=msg-in, endpoint=vm://msg-in}
INFO 2009-12-17 20:34:51,785 [main] org.mule.component.DefaultJavaComponent: Stopping: org.mule.component.DefaultJavaComponent component for: SedaService{start}
INFO 2009-12-17 20:34:51,785 [main] org.mule.model.seda.SedaService: Mule Service start has been stopped successfully
INFO 2009-12-17 20:34:51,787 [main] org.mule.transport.vm.VMConnector: Stopping: VMConnector{this=75d709a5, started=true, initialised=true, name='connector.VM.0', disposed=false, numberOfConcurrentTransactedReceivers=4, createMultipleTransactedReceivers=true, connected=true, supportedProtocols=[vm], serviceOverrides=null}
INFO 2009-12-17 20:34:51,787 [main] org.mule.transport.vm.VMConnector: Disconnected: VMConnector{this=75d709a5, started=false, initialised=true, name='connector.VM.0', disposed=false, numberOfConcurrentTransactedReceivers=4, createMultipleTransactedReceivers=true, connected=false, supportedProtocols=[vm], serviceOverrides=null}
INFO 2009-12-17 20:34:51,787 [main] org.mule.transport.vm.VMConnector: Stopped: VMConnector{this=75d709a5, started=false, initialised=true, name='connector.VM.0', disposed=false, numberOfConcurrentTransactedReceivers=4, createMultipleTransactedReceivers=true, connected=false, supportedProtocols=[vm], serviceOverrides=null}
INFO 2009-12-17 20:34:51,788 [main] org.mule.util.queue.TransactionalQueueManager: Stopping ResourceManager
INFO 2009-12-17 20:34:51,788 [main] org.mule.util.queue.TransactionalQueueManager: Stopped ResourceManager
INFO 2009-12-17 20:34:51,788 [main] org.mule.transport.vm.VMConnector: Disposing: VMConnector{this=75d709a5, started=false, initialised=true, name='connector.VM.0', disposed=false, numberOfConcurrentTransactedReceivers=4, createMultipleTransactedReceivers=true, connected=false, supportedProtocols=[vm], serviceOverrides=null}
INFO 2009-12-17 20:34:51,788 [main] org.mule.transport.vm.VMMessageDispatcher: Disconnected: VMMessageDispatcher{this=1915470e, endpoint=vm://msg-in, disposed=false}
INFO 2009-12-17 20:34:51,788 [main] org.mule.transport.vm.VMConnector: Disposed: VMConnector{this=75d709a5, started=false, initialised=false, name='connector.VM.0', disposed=true, numberOfConcurrentTransactedReceivers=4, createMultipleTransactedReceivers=true, connected=false, supportedProtocols=[vm], serviceOverrides=null}
INFO 2009-12-17 20:34:51,789 [main] org.mule.config.spring.MuleApplicationContext: Closing org.mule.config.spring.MuleApplicationContext@356f144c: display name [org.mule.config.spring.MuleApplicationContext@356f144c]; startup date [Thu Dec 17 20:34:49 CET 2009]; root of context hierarchy
INFO 2009-12-17 20:34:51,789 [main] org.springframework.beans.factory.support.DefaultListableBeanFactory: Destroying singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@29abc69: defining beans [customEditorConfigurer,_muleObjectNameProcessor,_mulePropertyPlaceholderProcessor, _muleSimpleRegistryBootstrap,_muleNotificationManager,_muleConfiguration,._muleNotificationManager: notification.1,._muleNotificationManager:notification.2,._muleNotificationManager:notification.3, ._muleNotificationManager:notification.4,._muleNotificationManager:notification.5,._muleNotificationManager: notification.6,._muleNotificationManager:notification.7,._muleNotificationManager:notification.8, ._muleNotificationManager:notification.9,._muleNotificationManager:notification.10,_muleSystemModel, _muleQueueManager,_muleSecurityManager,_muleProperties,_muleEndpointFactory,_muleStreamCloserService, _defaultThreadingProfile,_defaultMessageDispatcherThreadingProfile,_defaultMessageRequesterThreadingProfile, _defaultMessageReceiverThreadingProfile,_defaultServiceThreadingProfile,_defaultRetryPolicyTemplate, mule-ode,start,.start:inbound.11,.start:inbound.11:inbound-endpoint.12,.start:component.13]; root of factory hierarchy
INFO 2009-12-17 20:34:51,995 [main] org.mule.DefaultMuleContext:
**********************************************************************
* Mule shut down normally on: 12/17/09 8:34 PM *
* Server was up for: 0 days, 0 hours, 0 mins, 1.318 sec *
**********************************************************************
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.103 sec

So by finishing this post you should be able to execute a (simple) BPEL process in Apache ODE by using Mule. However, it is not certain we will use Apache ODE like this. I think we would like Intalio|server more because of the handy features/tooling they have added to Apache ODE.

]]> http://blog.redstream.nl/2009/12/18/combining-mule-with-a-bpel-engine/feed/ 0 http://blog.redstream.nl/2009/07/05/error-import-wsdl-in-soapui/ http://blog.redstream.nl/2009/07/05/error-import-wsdl-in-soapui/#comments Sun, 05 Jul 2009 10:08:46 +0000 Pascal Alma http://www.pascalalma.net/?p=920 Although it has been a while since I posted about SoapUI I am still receiving questions about the tool. The most frequently asked question is how to solve the error 'Error import WSDL' so I will post the steps I took in the past to solve this error, hoping that this might help you. The first step I usually take is to try to open the WSDL in a web browser.
If this is also not working and the WSDL runs on a machine on the world wide web then you have 3 options:
1. No access to internet

Easy to check if that is the case but you might just want to check it out to make sure

2. the link to the wsdl is dead

This often occurs if the source where you got the link from is rather old, like an article on the net that was posted in 2005.

3. a typo is made in the link

Make sure you have the right url with all '?' and '/' in the right place

If the WSDL in the browser is also not working and the WSDL runs on a machine in your local network then please check the following:

1. Make sure you can access the machine over HTTP

Try to ping the machine name or IP address to see if it is accessible from your machine. Although there is a chance the machine is accessible without being ping-able it often gives a good indication.

2. Make sure the web server hosting the wsdl (and webservice) is up

Point your browser to the machine and check if there is a web server running on port 80/8080/8000 or something like that. If the web server is down also the WSDL will not be found.

3. a typo is made in the link

Make sure you have the right url with all '?' and '/' in the right place

If the WSDL is showing up in the browser and the WSDL runs on a machine on the world wide web then you might check the following:

• Need a proxy to access the net

Check to see if your web browser uses a proxy to get access to the net. This is very common if your computer is connected to a companies network. If so, then add this proxy to the preferences in Soap UI so it will use the same proxy.

• a typo is made in the link

Make sure you have the right url with all '?' and '/' in the right place. I also recently heard leading or trailing spaces might lead to unexpected behaviour in SoapUI so please make sure to remove them.

If the WSDL is showing up in the browser and the WSDL runs on a machine in your local network then please check the following:

• a typo is made in the link

Make sure you have the right url with all '?' and '/' in the right place. I also recently heard leading or trailing spaces might lead to unexpected behaviour in SoapUI so please make sure to remove them.

• use the host's IP address instead of host name

I once got the situation it was only working with the IP address, but apparently not able to resolve the host name, so you could try this.

So, these are the things you could check. I know there will be much more reasons why this error might show up (how about https access for example), but I hope that in your case these steps will help to solve it. If you know other solutions to this problem just let me know, so I can add them to this list.

]]> http://blog.redstream.nl/2009/07/05/error-import-wsdl-in-soapui/feed/ 1 http://blog.redstream.nl/2009/01/20/testing-oracle-wsms-web-service-signing-and-verifying-with-soapui/ http://blog.redstream.nl/2009/01/20/testing-oracle-wsms-web-service-signing-and-verifying-with-soapui/#comments Tue, 20 Jan 2009 11:03:07 +0000 Pascal Alma http://www.pascalalma.net/?p=395 This will be the last 'hands-on' article about testing Oracle WSM setup with SoapUI. I have posted about two other examples here and here. In this example Oracle WSM is configured to verify the signature of the incoming SOAP message (request) and to add a digital signature to the outgoing message (response). How to arrange this in Oracle WSM is described in the book so I won't describe that here. What I will show is how to setup SoapUI to test the OWSM setup.
The WSDL for which I created a new project in SoapUI is:
PLAIN TEXT
XML:
1. <definitions name="TimeService" targetNamespace="urn:Test:TimeService" xmlns:tns="urn:Test:TimeService" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/">
2.    <message name="getTime0SoapIn">
3.       <part name="format" type="xsd:string"/>
4.    </message>
5.    <message name="getTime0SoapOut">
6.       <part name="Result" type="xsd:string"/>
7.    </message>
8.    <portType name="TimeServiceSoap">
9.       <operation name="getTime" parameterOrder="format">
10.          <input name="getTime0SoapIn" message="tns:getTime0SoapIn"/>
11.          <output name="getTime0SoapOut" message="tns:getTime0SoapOut"/>
12.       </operation>
13.    </portType>
14.    <binding name="TimeServiceSoap" type="tns:TimeServiceSoap">
15.       <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
16.       <operation name="getTime">
17.          <soap:operation soapAction="getTime" style="rpc"/>
18.          <input name="getTime0SoapIn">
19.             <soap:body use="encoded" namespace="urn:Test:GetTime" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
20.          </input>
21.          <output name="getTime0SoapOut">
22.             <soap:body use="encoded" namespace="urn:Test:GetTime" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
23.          </output>
24.       </operation>
25.    </binding>
26.    <service name="TimeService">
27.       <port name="TimeServiceSoap" binding="tns:TimeServiceSoap">
28.          <soap:address location="http://localhost:3115/gateway/services/SID0003004"/>
29.       </port>
30.    </service>
31. </definitions>

The configuration for the verification of the SOAP request is configured in Oracle WSM like this:


To have SoapUI adding a signature to the outgoing request I took the following steps:

• added my keystore to the project:
  

• added a configuration step called 'SignRequest' to the project as Outgoing WS-Security Configuration:
  
• added a configuration step called 'verifySignature' to the project as Incoming WS-Security Configuration:
  
• configured the SOAP request with which the OWSM is tested:
  

Now with all this in place I sent the request and received the following response:

PLAIN TEXT
XML:
1. <soap-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
2.    <soap-ENV:Body>
3.       <soap-ENV:Fault>
4.          <faultcode xmlns:p="http://schemas.oblix.com/ws/2003/08/Faults">p:Client.GenericFault</faultcode>
5.          <faultstring>WS-Security process failure:null</faultstring>
6.          <detail/>
7.       </soap-ENV:Fault>
8.    </soap-ENV:Body>
9. </soap-ENV:Envelope>

It took some time before I realized the error was not my configuration of SoapUI. In the log file of OWSM I found this stacktrace:

2009-01-17 20:23:03,452 WARNING [HTTPThreadGroup-8] wssecurity.SecurityBaseStep - Failure while applying XML Security
java.lang.NullPointerException
at oracle.security.xmlsec.util.XMLNode.removeChild(Unknown Source)
at com.cfluent.policysteps.security.wssecurity.OSDTWSSecurity.decryptVerify(OSDTWSSecurity.java:538)
at com.cfluent.policysteps.security.wssecurity.VerifyStep.performXmlSecurity(VerifyStep.java:147)
at com.cfluent.policysteps.security.wssecurity.SecurityBaseStep.execute(SecurityBaseStep.java:238)
at com.cfluent.pipelineengine.container.DefaultPipeline.executeStep(DefaultPipeline.java:124)
at com.cfluent.pipelineengine.container.DefaultPipeline.execute(DefaultPipeline.java:97)
at com.cfluent.pipelineengine.container.DefaultPolicy$DeferredPipeline.execute(DefaultPolicy.java:63)
at com.cfluent.pipelineengine.container.DefaultPolicy$DeferredPipeline.access$300(DefaultPolicy.java:18)
at com.cfluent.pipelineengine.container.DefaultPolicy.execute(DefaultPolicy.java:126)
at com.cfluent.pipelineengine.container.PipelineContainer.execute(PipelineContainer.java:114)
at com.cfluent.agent.Agent.intercept(Agent.java:123)
at com.cfluent.agent.AgentRuntime.intercept(AgentRuntime.java:200)
at com.cfluent.pipelineengine.util.PolicyInvoker.execute(PolicyInvoker.java:30)
at com.cfluent.pipelineengine.util.InvokerChain.execute(InvokerChain.java:30)
at com.cfluent.gateway.Invoker.execute(Invoker.java:118)
at com.cfluent.gateway.listener.ProtocolListener$ListenerTask.run(ProtocolListener.java:272)
at com.cfluent.gateway.listener.ProtocolListener.invoke(ProtocolListener.java:110)
at com.cfluent.gateway.listener.GatewayRuntime.invoke(GatewayRuntime.java:32)
at com.cfluent.gateway.listener.http.HttpListener.invoke(HttpListener.java:30)
at com.cfluent.gateway.listener.http.ServicesServlet.handlePost(ServicesServlet.java:34)
at com.cfluent.common.servlet.BaseServlet.doPost(BaseServlet.java:264)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:711)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)

Now this appears to be a bug (5897046) in OWSM as discussed here. Unfortunately I do not have access to MetaLink at the moment, so I cannot check for solutions or patches. The workaround I did was to skip the deletion of the signature in the incoming request:


Now when I send the request I get the response as expected:

PLAIN TEXT
XML:
1. <soap:Envelope soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:oas="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
2.    <soap:Header>
3.       <wsse:Security soap:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
4.          <wsse:BinarySecurityToken ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" wsu:Id="_b5MY1ev1b2sj4s0nZL2VDg22" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">MIICBDCCAW0CBElt0WUwDQYJKoZIhvcNAQEFBQAwSTELMAkGA1UEBhMCTkwxETAPBgNVBAoMCHBhbG1hLWl0MRIwEAYDVQQLDAlkZXZlbG9wZXIxEzARBgNVBAMMCnBhc2NhbGFsbWEwHhcNMDkwMTE0MTE0OTU3WhcNMDkwNzEzMTE0OTU3WjBJMQswCQYDVQQGEwJOTDERMA8GA1UECgwIcGFsbWEtaXQxEjAQBgNVBAsMCWRldmVsb3BlcjETMBEGA1UEAwwKcGFzY2FsYWxtYTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEApSBk3VobSFPMBuzkWpHvVsQLxWcICzOXWuhescOPqgvkQRfBl6g99v/O+73l0eJjrS/ayUf9fNs/VpUWrgHJ2AMD2/tRKrjfOV9YpG9HcupGB74ygpJ4lDy9VY6KxDDnNF0G6q1oJEZWhHkfupTZIZh70DzRVXqrzf6WqXOzd7MCAwEAATANBgkqhkiG9w0BAQUFAAOBgQAGJAPB24oqfBSlUXXBg/krsKKKPKgpxKV5mpoSf+G9WVjIgK1lplURht2Wyecze91MKhQONMqecHqyIorzXmnO0DWa+ND7exDjcGw+tsagVrxIr1FG85QzJqic+l/uX2+8c5a5m85+o0qPLQeKAwc8DWuANJXIh7/Fy76H7CAMvg==</wsse:BinarySecurityToken>
5.          <dsig:Signature xmlns="http://www.w3.org/2000/09/xmldsig#" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
6.             <dsig:SignedInfo>
7.                <dsig:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
8.                <dsig:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
9.                <dsig:Reference URI="#519sSPHD1xaC8TcH23RKyA22">
10.                   <dsig:Transforms>
11.                      <dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
12.                   </dsig:Transforms>
13.                   <dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
14.                   <dsig:DigestValue>lzj1qOFAUqEnuIqM2VGOfLDJ1x8=</dsig:DigestValue>
15.                </dsig:Reference>
16.                <dsig:Reference URI="#42uhaWCT0QoDrDGlwKsyZA22">
17.                   <dsig:Transforms>
18.                      <dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
19.                   </dsig:Transforms>
20.                   <dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
21.                   <dsig:DigestValue>8qR3lN2UDPj2EknUuxaf5Xf+8Ic=</dsig:DigestValue>
22.                </dsig:Reference>
23.             </dsig:SignedInfo>
24.          <dsig:SignatureValue>g9S4GajLoXFtNkLJHRDponTv3ubZe432onBI0xfqHQ1zqtt2lalDwnyxbitBjbLaBcu94Fr0FeL7vst50e6KoujrAwt3lCT3sCsKBnvTFZKRKicKf6AdqAkq+d2PyIr0w2gpGJD5ejot8HaYUhJyXI/ogPiYxUmHqXkJVGcZzQ0=</dsig:SignatureValue>
25.             <dsig:KeyInfo>
26.                <wsse:SecurityTokenReference wsu:Id="_Gn6xvVFEyg5rUp3hrpAfYg22" xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
27.                   <wsse:Reference URI="#_b5MY1ev1b2sj4s0nZL2VDg22"/>
28.                </wsse:SecurityTokenReference>
29.             </dsig:KeyInfo>
30.          </dsig:Signature>
31.          <wsu:Timestamp wsu:Id="42uhaWCT0QoDrDGlwKsyZA22" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:oas1="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
32.             <wsu:Created>2009-01-19T10:09:33Z</wsu:Created>
33.          </wsu:Timestamp>
34.       </wsse:Security>
35.    </soap:Header>
36.    <soap:Body wsu:Id="519sSPHD1xaC8TcH23RKyA22" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
37.       <n:getTimeResponse xmlns:n="urn:Test:GetTime">
38.          <result xsi:type="xsd:string">11:09 AM</result>
39.       </n:getTimeResponse>
40.    </soap:Body>
41. </soap:Envelope>
]]> http://blog.redstream.nl/2009/01/20/testing-oracle-wsms-web-service-signing-and-verifying-with-soapui/feed/ 1 http://blog.redstream.nl/2009/01/16/testing-soap-encrypting-and-decrypting-with-soapui/ http://blog.redstream.nl/2009/01/16/testing-soap-encrypting-and-decrypting-with-soapui/#comments Fri, 16 Jan 2009 08:47:23 +0000 Pascal Alma http://www.pascalalma.net/?p=367 As said before I am currently going through the book 'Oracle Web Service Manager'. In chapter 5 of this book an example is given how to configure OWSM to encrypt outgoing and decrypt incoming soap messages for a web service. To test this setup a dotNet client is created. In this post I will show you how you can test the setup by using SoapUI instead.
The first step (assuming that SoapUI is already installed) is to create a keystore on the client machine. This keystore must also be used in the OWSM configuration in the example. To create the keystore and necessary key-pair I use Portecle. I created a new keystore (PKCS based) and added a key for 'pascalalma' to it. Here is the screenshot with all the necessary info:


In SoapUI I have created a new project based on the WSDL in the example. At the project level I enter the WS-Security parameters and actions that must be performed. Since the gateway expects the soap message to be encoded I have to encode the outgoing message in SoapUI and decode the incoming response message.
Here is the security configuration at project level. First select the keystore to be used by SoapUI:


Then define the outgoing encryption action:


And the last one, define the incoming decryption action:


Now everything at project level is set. The next step is to tell the request it should use these settings. This is a step that took some time for me to discover. But when you click at the 'Auth' tab at the request window you can define the actions that must be executed by SoapUI for the request (and response) of the SOAP call. Here you can find the tab:


And here are the parameters set for the security:


Now, this should be it. Actually kind of straightforward.... But not in my case. I am using SoapUI2.5 and when I sended the request I go the following response back:

PLAIN TEXT
XML:
1. <soap-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
2.    <soap-ENV:Body>
3.       <soap-ENV:Fault>
4.          <faultcode xmlns:p="http://schemas.oblix.com/ws/2003/08/Faults">p:Client.GenericFault</faultcode>
5.          <faultstring>WS-Security process failure:FAULT CODE: UnsupportedSecurityToken FAULT MESSAGE: An unsupported token was provided</faultstring>
6.          <detail/>
7.       </soap-ENV:Fault>
8.    </soap-ENV:Body>
9. </soap-ENV:Envelope>

After an extensive search I found out it was a version problem in the SOAP header. OWSM gateway expects an element 'wsse:Reference' with attribute
ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"
but SoapUI was sending the request with ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v1"
When I knew what caused the error the solution was quickly found here. I downloaded the older version of the WSS4J library (wss4j-1.5.3.jar) and put that in the SoapUI/lib/ directory. I also modified the SoapUI/bin/soapui.bat file so the correct version is loaded by SoapUI. And this time the call worked like a charm. The response I got back now was (decrypted by SoapUI of course):

PLAIN TEXT
XML:
1. <soap:Envelope soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
2.    <soap:Header>
3.       <wsse:Security soap:mustUnderstand="1" xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
4.          <wsse:BinarySecurityToken EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" wsu:Id="asKWwEekHdcXDlFgYL5yP3w22" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">MIICBDCCAW0CBElt0WUwDQYJKoZIhvcNAQEFBQAwSTELMAkGA1UEBhMCTkwxETAPBgNVBAoMCHBhbG1hLWl0MRIwEAYDVQQLDAlkZXZlbG9wZXIxEzARBgNVBAMMCnBhc2NhbGFsbWEwHhcNMDkwMTE0MTE0OTU3WhcNMDkwNzEzMTE0OTU3WjBJMQswCQYDVQQGEwJOTDERMA8GA1UECgwIcGFsbWEtaXQxEjAQBgNVBAsMCWRldmVsb3BlcjETMBEGA1UEAwwKcGFzY2FsYWxtYTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEApSBk3VobSFPMBuzkWpHvVsQLxWcICzOXWuhescOPqgvkQRfBl6g99v/O+73l0eJjrS/ayUf9fNs/VpUWrgHJ2AMD2/tRKrjfOV9YpG9HcupGB74ygpJ4lDy9VY6KxDDnNF0G6q1oJEZWhHkfupTZIZh70DzRVXqrzf6WqXOzd7MCAwEAATANBgkqhkiG9w0BAQUFAAOBgQAGJAPB24oqfBSlUXXBg/krsKKKPKgpxKV5mpoSf+G9WVjIgK1lplURht2Wyecze91MKhQONMqecHqyIorzXmnO0DWa+ND7exDjcGw+tsagVrxIr1FG85QzJqic+l/uX2+8c5a5m85+o0qPLQeKAwc8DWuANJXIh7/Fy76H7CAMvg==</wsse:BinarySecurityToken>
5.          <xenc:EncryptedKey xmlns="http://www.w3.org/2001/04/xmlenc#" xmlns:xenc="http://www.w3.org/2001/04/xmlenc#">
6.             <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-1_5"/>
7.             <dsig:KeyInfo xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
8.                <wsse:SecurityTokenReference xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
9.                   <wsse:Reference URI="#asKWwEekHdcXDlFgYL5yP3w22" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"/>
10.                </wsse:SecurityTokenReference>
11.             </dsig:KeyInfo>
12.             <xenc:CipherData>
13.                <xenc:CipherValue>aSM+UvvqfsS/2Damu9pgg2U1oea1O5CjYZ08pKOG0U8IKTJaRgWIDVfjXZI+Gq4Wmsbsz0oWc6wKYawH23clYedt/ScX1ZpEAAHhSEzV8e/+hl3/vZ8Iq7UfLz3DRAat0cn0B00qW8VI+2j94hdTMQJ1v+EjH+7eQpnq0i09UBg=</xenc:CipherValue>
14.             </xenc:CipherData>
15.             <xenc:ReferenceList>
16.                <xenc:DataReference URI="#_o8iRaqZLI6bBw6wR009kLQ22"/>
17.             </xenc:ReferenceList>
18.          </xenc:EncryptedKey>
19.       </wsse:Security>
20.    </soap:Header>
21.    <soap:Body>
22.       <n:getTimeResponse xmlns:n="urn:Test:GetTime">
23.          <result xsi:type="xsd:string">12:23 PM</result>
24.       </n:getTimeResponse>
25.    </soap:Body>
26. </soap:Envelope>
]]> http://blog.redstream.nl/2009/01/16/testing-soap-encrypting-and-decrypting-with-soapui/feed/ 1 http://blog.redstream.nl/2009/01/15/testing-ws-security-authentication-with-soapui/ http://blog.redstream.nl/2009/01/15/testing-ws-security-authentication-with-soapui/#comments Thu, 15 Jan 2009 15:35:31 +0000 Pascal Alma http://www.pascalalma.net/?p=358 Last week I started to have a look at the product 'Oracle Web Server Manager'. I am reading a packtpub book about this product and am halfway now. I will post more about this book later but one thing I one to mention already is that there are several examples described which are tested by creating a web service client with .Net. I am not familiar with .Net (and do not have the intention to change that) so I used my favorite tool SoapUI as client to test the Oracle gateway.
The first example is created in chapter 4. In this example basic authentication is added to a web service. The book describes in detail how you do this with Oracle WSM. To test this setup I will use SoapUI. The first step is to create a project in SoapUI based on the web service's WSDL. I accept the defaults so an example request is generated.
The WSDL of the web service looks like this:
PLAIN TEXT
XML:
1. <definitions name="TimeService" targetNamespace="urn:Test:TimeService" xmlns:tns="urn:Test:TimeService" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/">
2.    <message name="getTime0SoapIn">
3.       <part name="format" type="xsd:string"/>
4.    </message>
5.    <message name="getTime0SoapOut">
6.       <part name="Result" type="xsd:string"/>
7.    </message>
8.    <portType name="TimeServiceSoap">
9.       <operation name="getTime" parameterOrder="format">
10.          <input name="getTime0SoapIn" message="tns:getTime0SoapIn"/>
11.          <output name="getTime0SoapOut" message="tns:getTime0SoapOut"/>
12.       </operation>
13.    </portType>
14.    <binding name="TimeServiceSoap" type="tns:TimeServiceSoap">
15.       <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
16.       <operation name="getTime">
17.          <soap:operation soapAction="getTime" style="rpc"/>
18.          <input name="getTime0SoapIn">
19.             <soap:body use="encoded" namespace="urn:Test:GetTime" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
20.          </input>
21.          <output name="getTime0SoapOut">
22.             <soap:body use="encoded" namespace="urn:Test:GetTime" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
23.          </output>
24.       </operation>
25.    </binding>
26.    <service name="TimeService">
27.       <port name="TimeServiceSoap" binding="tns:TimeServiceSoap">
28.          <soap:address location="http://localhost:3115/gateway/services/SID0003001"/>
29.       </port>
30.    </service>
31. </definitions>

If I don't configure anything in SoapUI and just send the request I get the response:

PLAIN TEXT
XML:
1. <soap-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
2.    <soap-ENV:Body>
3.       <soap-ENV:Fault>
4.          <faultcode xmlns:p="http://schemas.oblix.com/ws/2003/08/Faults">p:Client.AuthenticationFault</faultcode>
5.          <faultstring>Invalid username or password</faultstring>
6.          <detail/>
7.       </soap-ENV:Fault>
8.    </soap-ENV:Body>
9. </soap-ENV:Envelope>

which is logical, because I have to supply credentials. These credentials must be added to the SOAP call according to the WS-Security specs. Luckily this is done by SoapUI by default. Here is the configuration of the call in SoapUI:


The SOAP request that is send now looks like this (the raw xml):

PLAIN TEXT
XML:
1. <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:Test:GetTime" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
2.    <soapenv:Header>
3.       <wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
4.          <wsse:UsernameToken wsu:Id="UsernameToken-32950583" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
5.             <wsse:Username>palma</wsse:Username>
6.             <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">alma23</wsse:Password>
7.             <wsse:Nonce>Ekgk+pK0FhRj8EnzWxFsKg==</wsse:Nonce>
8.             <wsu:Created>2009-01-15T08:37:08.005Z</wsu:Created>
9.          </wsse:UsernameToken>
10.       </wsse:Security>
11.    </soapenv:Header>
12.    <soapenv:Body>
13.       <urn:getTime soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
14.          <format xsi:type="xsd:string">?</format>
15.       </urn:getTime>
16.    </soapenv:Body>
17. </soapenv:Envelope>

As you might notice a SOAP header is now added with the credentials information. The result now is:

PLAIN TEXT
XML:
1. <soap:Envelope soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
2.    <soap:Body>
3.       <n:getTimeResponse xmlns:n="urn:Test:GetTime">
4.          <result xsi:type="xsd:string">09:37 AM</result>
5.       </n:getTimeResponse>
6.    </soap:Body>
7. </soap:Envelope>

So this works!

The next example in the book for which I use SoapUI is about encrypting and decrypting the message. This has some more configuration to setup so I will show this in a separate post.

]]> http://blog.redstream.nl/2009/01/15/testing-ws-security-authentication-with-soapui/feed/ 2 http://blog.redstream.nl/2007/08/14/could-it-be-true-a-bug-in-soap-ui/ http://blog.redstream.nl/2007/08/14/could-it-be-true-a-bug-in-soap-ui/#comments Tue, 14 Aug 2007 16:51:03 +0000 Pascal Alma http://www.pascalalma.net/?p=57 While performing the load test of our web service (of course with my favourite tool SoapUI) I was getting some errors when I used a number of threads at a time to call my service. Most error messages were related to an invalid XML format of the incoming message. I was told this probably had something to do with SoapUI (that would be the first drawback with it...). When multiple threads are used in SoapUI to sent the messages, they somehow would get mixed up and invalid SOAP messages were sent. So I was told.
After a few weeks I finally got some time to look in to it. To check if Soap UI was indeed messing up the SOAP messages, we made a Filter that outputted the incoming HTTP request to a log file. This filter was configured to receive the request before it would be received by the XFire servlet, but after it was decoded (we are using HTTPS for our web service communication). I will handle the code for this filter in another post, since it might be handy in other situations too.
After our tests with the filter in place we could only conclude that Soap UI was working correctly (what a surprise ;) ) and that all messages were sent in the correct SOAP format. So that forced us to look for the problem in another direction, may be even our own code ;). Looking for the cause of the problem we soon found out that all errors were traced back to one class (one of our own), the SchemaUtils.java. Here is the main part of the code:
PLAIN TEXT
JAVA:
1. import java.io.IOException;
2.  
3. import javax.xml.parsers.DocumentBuilderFactory;
4. import javax.xml.parsers.ParserConfigurationException;
5. import javax.xml.transform.Source;
6. import javax.xml.transform.stream.StreamSource;
7. import javax.xml.validation.Schema;
8. import javax.xml.validation.SchemaFactory;
9. import javax.xml.validation.Validator;
10.  
11. public class SchemaUtils {
12.  
13.   private static final Validator VALIDATOR;
14.   private static final SchemaFactory SF;
15.   private static final Schema SCHEMAS;
16.  
17.   static {
18.      try {
19.         // Re-using Schema to parse and validate XML documents
20.         // create a SchemaFactory that conforms to W3C XML Schema
21.         SF = SchemaFactory.newInstance(javax.xml.XMLConstants.W3C_XML_SCHEMA_NS_URI);
22.  
23.         final StreamSource sSoapEnv = new StreamSource(MY_XML_CONSTANTS.XSD_SOAP_ENVELOPE);
24.         final StreamSource sSoapenc = new StreamSource(MY_XML_CONSTANTS.XSD_SOAP_ENCODING);
25.         final StreamSource sMyStuf = new StreamSource(MY_XML_CONSTANTS.XSD_MY_STUF);
26.  
27.         SCHEMAS = SF.newSchema(new Source[] {sSoapEnv, sSoapenc, sMyStuf });
28.         VALIDATOR = SCHEMAS.newValidator();
29.      } catch (Throwable e) {
30.         throw new ExceptionInInitializerError(e);
31.      }
32.   }
33.  
34.   /**
35.    * Validates XML against a XSD.
36.    */
37.   public static void validate(Source docSource) throws CustomXMLException {
38.  
39.      try {
40.         VALIDATOR.validate(docSource, null);
41.      } catch (SAXException e) {
42.         throw new CustomXMLException(CustomErrorMessage.CUST_XML017, e);
43.      } catch (IOException e) {
44.         throw new CustomXMLException(CustomErrorMessage.CUST_XML017, e);
45.      }
46.   }
47. }

As you might known, the class 'Validator.java' that is used here is NOT thread safe. This is told in the Javadoc of the class. So instead of pointing our fingers at the tools we were using we should be looking for the problem in our own code.
So actually there are two lessons here to be learned:
1. If there is found an error, please make sure it isn't in your own code before pointing to others
2. If someone tells you it isn't a fault in their code, don't just take that for granted, but try to proove it with a little testcase.

And for the record here is the modified class that is thread safe:

PLAIN TEXT
JAVA:
1. import java.io.IOException;
2.  
3. import javax.xml.parsers.DocumentBuilderFactory;
4. import javax.xml.parsers.ParserConfigurationException;
5. import javax.xml.transform.Source;
6. import javax.xml.transform.stream.StreamSource;
7. import javax.xml.validation.Schema;
8. import javax.xml.validation.SchemaFactory;
9. import javax.xml.validation.Validator;
10.  
11. public class SchemaUtils {
12.  
13.   private static final SchemaFactory SF;
14.   private static final Schema SCHEMAS;
15.  
16.   static {
17.      try {
18.         // Re-using Schema to parse and validate XML documents
19.         // create a SchemaFactory that conforms to W3C XML Schema
20.         SF = SchemaFactory.newInstance(javax.xml.XMLConstants.W3C_XML_SCHEMA_NS_URI);
21.  
22.         final StreamSource sSoapEnv = new StreamSource(MY_XML_CONSTANTS.XSD_SOAP_ENVELOPE);
23.         final StreamSource sSoapenc = new StreamSource(MY_XML_CONSTANTS.XSD_SOAP_ENCODING);
24.         final StreamSource sMyStuf = new StreamSource(MY_XML_CONSTANTS.XSD_MY_STUF);
25.  
26.         SCHEMAS = SF.newSchema(new Source[] {sSoapEnv, sSoapenc, sMyStuf });
27.      } catch (Throwable e) {
28.         throw new ExceptionInInitializerError(e);
29.      }
30.   }
31.  
32.   /**
33.    * Validates XML against a XSD.
34.    */
35.   public static void validate(Source docSource) throws CustomXMLException {
36.  
37.      try {
38.         SCHEMAS.newValidator().validate(docSource, null);
39.      } catch (SAXException e) {
40.         throw new CustomXMLException(CustomErrorMessage.CUST_XML017, e);
41.      } catch (IOException e) {
42.         throw new CustomXMLException(CustomErrorMessage.CUST_XML017, e);
43.      }
44.   }
45. }
]]> http://blog.redstream.nl/2007/08/14/could-it-be-true-a-bug-in-soap-ui/feed/ 6 http://blog.redstream.nl/2007/07/11/another-common-issue-solved-with-soap-ui/ http://blog.redstream.nl/2007/07/11/another-common-issue-solved-with-soap-ui/#comments Wed, 11 Jul 2007 04:43:00 +0000 Pascal Alma http://www.pascalalma.net/?p=43 Well, I think it is clear now I am a big fan of SoapUI. So here is another post about it. This time I explain how you can use it to perform a load test for your webservice and how to work around a common issue with this test. One of the business rules we have is that a message may only be processed succesfully once. To implement this, a unique referenceNumber is supplied in the body of the SOAP message (I know, it was better to use a policy for that by adding a SOAP header, but this is a piece of legacy I have to deal with). In the webservice (actually in a XFire handler) the referenceNumber is checked against all processed referenceNumbers in a database and if it already exists, a fault message is returned.
To avoid this fault message in our load test we added several steps to our Soap UI testcase that increases this referenceNumber, so it's unique for every message.
Here is an example of how to do this. First I created a webservice that just echoes the inputted string. Here is the WSDL:
PLAIN TEXT
XML:
1. <wsdl:definitions targetNamespace="http://net.pascalalma.services/EchoService">
2. <wsdl:types>
3.   <xsd:schema targetNamespace="http://net.pascalalma.services/EchoService" elementFormDefault="qualified" attributeFormDefault="qualified">
4.     <xsd:element name="s" type="xsd:string"/>
5.     <xsd:element name="echoAnswer" type="xsd:string"/>
6.   </xsd:schema>
7. </wsdl:types>
8. <wsdl:message name="echoRequest">
9.   <wsdl:part element="tns:s" name="s"/>
10. </wsdl:message>
11. <wsdl:message name="echoResponse">
12.   <wsdl:part element="tns:echoAnswer" name="echoAnswer"/>
13. </wsdl:message>
14. <wsdl:portType name="EchoService">
15.   <wsdl:operation name="echo">
16.     <wsdl:input message="tns:echoRequest" name="echoRequest"/>
17.     <wsdl:output message="tns:echoResponse" name="echoResponse"/>
18.   </wsdl:operation>
19. </wsdl:portType>
20. <wsdl:binding name="EchoServiceHttpBinding" type="tns:EchoService">
21.   <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
22.   <wsdl:operation name="echo">
23.     <wsdlsoap:operation soapAction="urn:echo"/>
24.     <wsdl:input name="echoRequest">
25.       <wsdlsoap:body use="literal"/>
26.     </wsdl:input>
27.     <wsdl:output name="echoResponse">
28.       <wsdlsoap:body use="literal"/>
29.     </wsdl:output>
30.   </wsdl:operation>
31. </wsdl:binding>
32. <wsdl:service name="EchoService">
33.   <wsdl:port binding="tns:EchoServiceHttpBinding" name="EchoServiceHttpPort">
34.     <wsdlsoap:address location="http://localhost:8080/XFireTest/services/EchoService"/>
35.   </wsdl:port>
36. </wsdl:service>
37. </wsdl:definitions>

I then created a TestCase based on this WSDL and added four steps:

• A properties step
  In this step a property is defined to be used in this TestCase.
  
• A Groovy Script step
  This step has the logic to increase the property that is defined in the step before.
  
• A Transfer step
  With this step we copy the value of the (modified) property into the SOAP request before we send it to our webservice.
  
• The SOAP request step
  Final step is sending the request with the modified value.
  

Now when all this is in place you can run a simple loadtest like this:


In the server where my webservice is running you will get out put like this:

As you can see each call gets a unique number.

Now we change the LoadTest to have multiple threads accessing the webservice at the same time. When we do that like this:


the output becomes:


Now the generated numbers are no longer unique!

To fix this I have added a property and changed the Groovy Script Step so it adds the thread index to the unique part. The Property Step and the Groovy Step become like:

and


And the output now is:


Now that looks better, doesn't it? All generated ID's are unique again for every message.

]]> http://blog.redstream.nl/2007/07/11/another-common-issue-solved-with-soap-ui/feed/ 15 http://blog.redstream.nl/2007/07/09/managing-the-test-database-with-soap-ui/ http://blog.redstream.nl/2007/07/09/managing-the-test-database-with-soap-ui/#comments Mon, 09 Jul 2007 09:50:37 +0000 Pascal Alma http://www.pascalalma.net/?p=42 As I blogged a few posts ago, we are using the freeedition of soapUI to test our webservice and are very pleased about it.
In this post I will show you one way to solve a common problem when you are testing your software. It is the initial managing the state of the database you are using for your tests. Since you want to run you're tests with a simple push of a button you don't want to have to set the state of your database correctly by hand. So what we did was we created a Java class that calls our sql scripts that sets the initial state of our database. For performing the actual scripts the class uses the SQLExec task of Ant.

Here is the code for the Java class:

PLAIN TEXT
JAVA:
1. package net.pascalalma.test.soapui;
2.  
3. import java.io.File;
4.  
5. import org.apache.tools.ant.Project;
6. import org.apache.tools.ant.taskdefs.SQLExec;
7.  
8. import com.eviware.soapui.SoapUI;
9.  
10. /**
11. * This class is a Helper class for the soapui scripts. Methods in this class are called via the Groovy scripts like
12. * this : net.pascalalma.test.soapui.TestDataBase.cleanByHost(dbHost); (the SQL script are in the
13. * lib dir !!). It contains methods for executing the SQL files (using the ant library) in order
14. * to get a fresh database.
15. *
16. * We use the ant SQLExec task to do the actual sql work for us.
17. */
18. public class TestDatabase {
19.  
20.    /**
21.     * Cleans the database.
22.     *
23.     * @param host the host name
24.     */
25.    public static void cleanByHost(String host) {
26.       clean("org.postgresql.Driver", "jdbc:postgresql://" + host + ":5432/my_db", "my_db", "db_passw", "../lib");
27.    }
28.  
29.   /**
30.     * Cleans the database.
31.     *
32.     * @param driver the JDBC driver classname
33.     * @param dbUrl the database URL
34.     * @param username the username
35.     * @param password the password
36.     * @param path the path where the SQL files are located
37.     */
38.    public static void clean(String driver, String dbUrl, String username, String password, String path) {
39.  
40.       try {
41.          SoapUI.log("Running DB clean on " + dbUrl + " using SQL scripts from " + path);
42.          SQLExec sql = new SQLExec();
43.          sql.setProject(new Project()); // set a dummy project or else log() will fail !
44.          sql.setDriver(driver);
45.          sql.setUrl(dbUrl);
46.          sql.setUserid(username);
47.          sql.setPassword(password);
48.  
49.          // conf/drop_schema.sql
50.          try {
51.             SoapUI.log(" - drop_schema.sql");
52.             sql.setSrc(new File(path + "/drop_schema.sql"));
53.             sql.execute();
54.          } catch (Exception e) {
55.             // continue anyway
56.             SoapUI.log(e.getMessage());
57.             SoapUI.log("continuing anyway");
58.          }
59.  
60.          SoapUI.log(" - install_schema.sql");
61.          sql.setSrc(new File(path + "/install_schema.sql"));
62.          sql.execute();
63.  
64.          SoapUI.log(" - schema_update_1.1.0.sql");
65.          sql.setSrc(new File(path + "/schema_update_1.1.0.sql"));
66.          sql.execute();
67.  
68.          SoapUI.log(" - load_data.sql");
69.          sql.setSrc(new File(path + "/load_data.sql"));
70.          sql.execute();
71.  
72.          SoapUI.log("Ready!");
73.       } catch (Exception e) {
74.          SoapUI.log("Got an exception! ");
75.          SoapUI.log(e.getMessage());
76.       }
77.  
78.    }
79. }

(I am sure you can think of much more/better ways to do this, but I only want to show you how to do this with soapUI)

After compiling this class you can add the TestDatabase.class file to the SOAP UI in the folder '$SOAP_UI_HOME$/bin/ext', together with the necessary jar files, in this case the database driver (postgres-8.1.-404.jdbc3.jar' and the Ant lib (ant-1.6.5.jar). We are using a PostgreSQL database for our application and have putted our sql-scripts in the '$SOAP_UI_HOME$/lib/' folder.

When this is all in place we can add a test step (initialization) to our test run. We insert a Test Step: 'Groovy script' and add the following statement:
nl.pascalalma.test.soapui.TestDatabase.cleanByHost("localhost");

If you now run this step you should see the output of it in the Groovy Test Log window. One thing you have to remind is that you put the correct version of your sql-scripts in the SOAP lib directory!

]]> http://blog.redstream.nl/2007/07/09/managing-the-test-database-with-soap-ui/feed/ 3 http://blog.redstream.nl/2007/05/23/using-soapui-for-testing-your-webservice/ http://blog.redstream.nl/2007/05/23/using-soapui-for-testing-your-webservice/#comments Wed, 23 May 2007 05:20:56 +0000 Pascal Alma http://www.pascalalma.net/?p=37 In my previous post I showed you how you can use Ant and XFire to create a client for your webservice. Another, even nicer and easier way, to test your webservice is to make use of soapUI. This is a free tool (I haven't used the Pro version yet) with which you can easily create a SOAP request and send them to your webservice and see the repsonse that is send back by the webservice. Beside just sending SOAP requests you can also have executed Groovy scripts with which you can prepare the state of your database for instance, so you can create a full and clean test cycle.
I have installed the standalone version of soapUI version 1.7 which can be downloaded here. After installing it, you can start it and create a new WSDL project:


The WSDL I am pointing to, is the WSDL of the service I deployed in this post. Here is the content of the WSDL:

PLAIN TEXT
XML:
1. <?xml version="1.0" encoding="UTF-8"?>
2. <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:ns1="http://model.pascalalma.net" xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope" xmlns:soapenc11="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soapenc12="http://www.w3.org/2003/05/soap-encoding" xmlns:tns="http://net.pascalalma.services/BookService" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://net.pascalalma.services/BookService">
3.   <wsdl:types>
4.     <xsd:schema targetNamespace="http://model.pascalalma.net" elementFormDefault="qualified" attributeFormDefault="qualified">
5.       <xsd:complexType name="ArrayOfBookObject">
6.         <xsd:sequence>
7.           <xsd:element name="BookObject" type="ns1:BookObject" nillable="true" minOccurs="0" maxOccurs="unbounded" />
8.         </xsd:sequence>
9.       </xsd:complexType>
10.       <xsd:complexType name="BookObject">
11.         <xsd:sequence>
12.           <xsd:element name="author" type="xsd:string" minOccurs="0" nillable="true" />
13.           <xsd:element name="isbn" type="xsd:string" minOccurs="0" nillable="true" />
14.           <xsd:element name="title" type="xsd:string" minOccurs="0" nillable="true" />
15.         </xsd:sequence>
16.       </xsd:complexType>
17.     </xsd:schema>
18.     <xsd:schema targetNamespace="http://net.pascalalma.services/BookService" elementFormDefault="qualified" attributeFormDefault="qualified">
19.       <xsd:element name="myAnswer" type="ns1:ArrayOfBookObject" />
20.     </xsd:schema>
21.   </wsdl:types>
22.   <wsdl:message name="getBooksRequest" />
23.   <wsdl:message name="getBooksResponse">
24.     <wsdl:part element="tns:myAnswer" name="myAnswer" />
25.   </wsdl:message>
26.   <wsdl:portType name="BookServiceImpl">
27.     <wsdl:operation name="getBooks">
28.       <wsdl:input message="tns:getBooksRequest" name="getBooksRequest" />
29.       <wsdl:output message="tns:getBooksResponse" name="getBooksResponse" />
30.     </wsdl:operation>
31.   </wsdl:portType>
32.   <wsdl:binding name="BookServiceHttpBinding" type="tns:BookServiceImpl">
33.     <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
34.     <wsdl:operation name="getBooks">
35.       <wsdlsoap:operation soapAction="urn:getBooks" />
36.       <wsdl:input name="getBooksRequest">
37.         <wsdlsoap:body use="literal" />
38.       </wsdl:input>
39.       <wsdl:output name="getBooksResponse">
40.         <wsdlsoap:body use="literal" />
41.       </wsdl:output>
42.     </wsdl:operation>
43.   </wsdl:binding>
44.   <wsdl:service name="BookService">
45.     <wsdl:port binding="tns:BookServiceHttpBinding" name="BookServiceHttpPort">
46.       <wsdlsoap:address location="http://localhost:8080/XFireTest/services/BookService" />
47.     </wsdl:port>
48.   </wsdl:service>
49. </wsdl:definitions>

As you can see it is a simple WSDL:
there are no input parameters for the service and it will return a list (array) of bookObjectTypes. After creation of the soapUI project, you directly create tests for your webservice since the checkbox asking to create a SOAP request for each operation was checked. If you double click the request you can see the content of the SOAP request in the main window:


Since my webservice doesn't have any input parameters, it is very simple request. When we click the green arrow the request is sent and we will see the SOAP response we got back from the server:

PLAIN TEXT
XML:
1. <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
2.    <soap:Body>
3.       <myAnswer xmlns="http://net.pascalalma.services/BookService">
4.          <ns1:BookObject xmlns:ns1="http://model.pascalalma.net">
5.             <author xmlns="http://model.pascalalma.net">Pascal Alma</author>
6.             <isbn xmlns="http://model.pascalalma.net">1313131313</isbn>
7.             <title xmlns="http://model.pascalalma.net">XFire Tutorial</title>
8.          </ns1:BookObject>
9.          <ns1:BookObject xmlns:ns1="http://model.pascalalma.net">
10.             <author xmlns="http://model.pascalalma.net">Pascal Alma</author>
11.             <isbn xmlns="http://model.pascalalma.net">1413135316</isbn>
12.             <title xmlns="http://model.pascalalma.net">XFire Advanced</title>
13.          </ns1:BookObject>
14.       </myAnswer>
15.    </soap:Body>
16. </soap:Envelope>

So now we know the webservice is working. To make it a good test case, we need to create a new testsuite in our project and add testcases to it. With these test cases you can send your custom SOAP requests and check the response with asserts. You can do this by right-clicking the BookServiceHttpBinding and choose 'Generate Testsuite'. You will now get a testsuite with one test case (in my situation). If you expand the Test Steps node and double click at the TestRequestStep getBooks you will see the simple SOAP request again in the main window. But this time you can right-click in the bottom of the window to add assertions:

This way it is not only checking whether the service is reached, but it also checks if the content of the reponse is what you would expect to be returned by the service. This is just a small example of all the things you can do with soapUI but I hope when you play around with it, you will get enthousiastic about the tool as I am.

]]> http://blog.redstream.nl/2007/05/23/using-soapui-for-testing-your-webservice/feed/ 151