BPEL SE - Persistence schema

Thanks Kiran,

I got that script for Oracle. I did create a schema and changed the persistence property to true. But bpelse throws exception as invalid SQL92 'TIMESTAMPDIFF' on UpdateDanglingInstances.

Another problem: I have created a very simple bpel process using Netbeans 5.5 and deployed the zip file created (in dist folder of jbi module). But when i invoke the process, bpelse throws exception as the porttype and service not available?

I just started GlassFish and openESB few hours ago. Could somebody guide me to the right documentation for openESB, BPELSE documentation, tutorials.

Thank you

Raja

rajaba at 2007-7-9 21:06:45 >

Yes,

I did create a component application and added the Bpel project as JBI Module.

The deployment went well. But when I invoke the process, using JAX-WS web service client (based on the wsdl in the bpel project), throws exception as below.

Here is my configuration:

glassfish V2 - build b36

jbi_components - build 070213_5 (latest promoted build)

Oracle 10g (now persistence set to false to get BPEL working!)

Do I need to do any other configuration to make com.sun.httpsoapbc-1.0-2 discover the BPEL services?

Thank you

Raja

=======================================

[#|2007-02-21T17:07:04.781-0500|SEVERE|sun-appserver9.1|

com.sun.jbi.component.com.sun.httpsoapbc-1.0-2com.sun.jbi.httpsoapbc.InboundMessageProcessor|

_ThreadID=29;_ThreadName=JAXWS-Engine-1;_RequestID=d4567963-49f5-4eda-8ef9-3db1053010f1;|

Failed to send InOut message.

javax.jbi.messaging.MessagingException: Unable to locate activated endpoint for service connection {http://bpel.test/wsdl/TestProcess1}TestProcess1Service TestProcess1Port.

at com.sun.jbi.messaging.MessageService.addressExchange(MessageService.java:485)

at com.sun.jbi.messaging.MessageService.doExchange(MessageService.java:319)

at com.sun.jbi.messaging.DeliveryChannelImpl.send(DeliveryChannelImpl.java:212)

at com.sun.jbi.httpsoapbc.InboundMessageProcessor.sendInOut(InboundMessageProcessor.java:336)

at com.sun.jbi.httpsoapbc.InboundMessageProcessor.execute(InboundMessageProcessor.java:269)

at com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider.invoke(AsyncJBIProvider.java:127)

at com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider.invoke(AsyncJBIProvider.java:88)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:585)

at com.sun.jbi.httpsoapbc.jaxwssupport.InvokerImpl.invoke(InvokerImpl.java:65)

at com.sun.xml.ws.api.server.Invoker.invokeAsyncProvider(Invoker.java:79)

at com.sun.xml.ws.server.InvokerTube$2.invokeAsyncProvider(InvokerTube.java:152)

at com.sun.xml.ws.server.provider.AsyncProviderInvokerTube.processRequest(AsyncProviderInvokerTube.java:45)

at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:559)

at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:518)

at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:503)

at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:400)

at com.sun.xml.ws.api.pipe.helper.AbstractTubeImpl.process(AbstractTubeImpl.java:70)

at com.sun.xml.ws.mex.server.MetadataServerPipe.process(MetadataServerPipe.java:97)

at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:79)

at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:559)

at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:518)

at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:503)

at com.sun.xml.ws.api.pipe.Fiber.run(Fiber.java:352)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)

at java.lang.Thread.run(Thread.java:595)

===================================================

rajaba at 2007-7-9 21:06:45 >

No you don't have to do anything "like discovering services". I think what you did should work. From the exception, it makes me think that the service assembly didn't get deployed properly to the BPEL SE. Deployment seems to have been fine with the httpBC, because it sent a request on the NMR.

I would check if the deployment to the bpelse is fine. Maybe the engine is in the "stop" state? To check if the deployment is fine, go to "runtime" tab, open the servers node, expand jbi node, expand the service assembly node, expand the specific service assembly and you should see two nodes, corresponding to http BC and BPEL SE. If you didn't or if you saw any of the nodes with some funny 'question mark' or 'red icons' your deployment didn't go through fine.

In case you are not able to diagnose, i would uninstall the old glassfish and reinstall it again and this time, try the scenario without having changed any persistence properties.

let us know how you proceed.

kiran.bhumanaa at 2007-7-9 21:06:45 >

Thanks Kiran,

I have Netbeans 5.5 and it is not working with Glassfish (b36). After reading the wiki, i got Netbeans 5.5.1 daily build (070222) and it's always throwing exceptions, and im unable to build one simple bpel process.

Which version of netbeans and glassfish combination you are recommending?

Could you please give me the details to configure bpelse with oracle?

Thank you

Raja

rajaba at 2007-7-9 21:06:45 >