ESB Link

Hi!
We're using the BAM together with ESB.
I want to link from a window displaying errors direct into the correct instance in the ESB console.
Do anyone have a correct URL? besides the hostname of course.
There's documentation for doing the same thing but into the BPEL console, but doesn't really help...
See Below
Regards Eskil
URL1 (dynamic)
To Active BPEL Process Instance on BPEL Console (to verify the process details)
http://localhost:8888/BPELConsole/default/displayInstance.jsp?referenceId=bpel://localh
ost/default/OrderBooking~1.0/xxxx
where xxxx – the process instance id, which is dynamically supplied by BAM console

I dont think that will make any fault, but you have to update the references of WSDLExt2 with the new operation.
Otherwise i dont see any issue, you can use existing message or new messages no problem with those.
Thanks,
Vijay

Similar Messages

Ant extractESBDeploymentPlan Issue with linked ESB Artifacts

Hi
I seem to have found a problem with the ExtractESBDeploymentPlan script.
I've created a number of ESB artifacts that are common to a number of other ESB processes. I link them together by calling an existing ESB Routing Service from an ESB, which then adds the .esbsvc descriptors to my process (I assume just to enable them to be seen in the diagram). Doing this does not import the wsdl's etc which is good.
However, if I then try to extract these ESB projects, I get the following error:
internal.ExtractESBDeploymentPlan:
[echo] -- EXTRACTING ESBCRMCitizen --
[delete] Deleting: M:\code\solihull\jdev\ESBCRMCitizen\deployment\devDeploymentPlan.xml
[extractESBDeploymentPlan] java.lang.Exception: Programming Error : Adapter Service <PostCitizen> does not have an assoc
iated WSDL artifact
[extractESBDeploymentPlan] at oracle.tip.esb.jdev.artifacts.model.ESBAdapterServiceArtifactContent.getDeploymentPro
perties(ESBAdapterServiceArtifactContent.java:154)
[extractESBDeploymentPlan] at oracle.tip.esb.client.anttasks.ExtractESBDeploymentPlanTask.hydrateServiceDeploymentP
lans(ExtractESBDeploymentPlanTask.java:372)
[extractESBDeploymentPlan] at oracle.tip.esb.client.anttasks.ExtractESBDeploymentPlanTask.constructDeploymentPlan(E
xtractESBDeploymentPlanTask.java:477)
[extractESBDeploymentPlan] at oracle.tip.esb.client.anttasks.ExtractESBDeploymentPlanTask.execute(ExtractESBDeploym
entPlanTask.java:543)
[extractESBDeploymentPlan] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
[extractESBDeploymentPlan] at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)
[extractESBDeploymentPlan] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[extractESBDeploymentPlan] at java.lang.reflect.Method.invoke(Method.java:585)
[extractESBDeploymentPlan] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
[extractESBDeploymentPlan] at org.apache.tools.ant.Task.perform(Task.java:348)
[extractESBDeploymentPlan] at org.apache.tools.ant.Target.execute(Target.java:357)
[extractESBDeploymentPlan] at org.apache.tools.ant.Target.performTasks(Target.java:385)
[extractESBDeploymentPlan] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
[extractESBDeploymentPlan] at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.ja
va:38)
[extractESBDeploymentPlan] at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
[extractESBDeploymentPlan] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:416)
[extractESBDeploymentPlan] at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105)
[extractESBDeploymentPlan] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
[extractESBDeploymentPlan] at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)
[extractESBDeploymentPlan] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[extractESBDeploymentPlan] at java.lang.reflect.Method.invoke(Method.java:585)
[extractESBDeploymentPlan] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
[extractESBDeploymentPlan] at org.apache.tools.ant.Task.perform(Task.java:348)
[extractESBDeploymentPlan] at org.apache.tools.ant.Target.execute(Target.java:357)
[extractESBDeploymentPlan] at org.apache.tools.ant.Target.performTasks(Target.java:385)
[extractESBDeploymentPlan] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
[extractESBDeploymentPlan] at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
[extractESBDeploymentPlan] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
[extractESBDeploymentPlan] at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
[extractESBDeploymentPlan] at org.apache.tools.ant.Main.runBuild(Main.java:698)
[extractESBDeploymentPlan] at org.apache.tools.ant.Main.startAnt(Main.java:199)
[extractESBDeploymentPlan] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
[extractESBDeploymentPlan] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
BUILD FAILED
M:\code\solihull\jdev\Resources\deploy\build.xml:185: The following error occurred while executing this line:
M:\code\solihull\jdev\Resources\deploy\lib\cb-ant-oracle.xml:159: java.lang.Exception: Programming Error : Adapter Servi
ce <PostCitizen> does not have an associated WSDL artifact
This is valid, as the .esbsvc does not have a .wsdl.
Now, is this my fault for doing something not in best practice, or an issue with JDeveloper, or the extract script?
Any thoughts?
Chris

Hi Chris
I have the exact same problem as you. I have a .esbsvc file in my project that does not have a corresponding local .wsdl file. (In the .esbsvc file I link to the WSDL with a HTTP-address).
Did you come up with a solution?
Thanks
//Kalle Viklund

How to link ODI with ESB???

Hi,
I need to know how to link ODI with ESB(Enterprise Service Bus)....
should i expose ODI as a web service or is there any other way to link these two...
please reply me asap its very urgent...
Regards,

I'm also interested on this.
I don't know very much about ODI, but could point the following:
1 - Your datasource could be exposed as a web service, as you suggested, and be exposed for ESB to consume.
2 - ESB can connect to your data source (not ODI, but the datasource the ODI act on) using a DBAdapter.
3 - ESB can send a JMS message that can be consumed by an ODI JMS based datasource (I'm not sure)
4 - ODI can have a Web Service based datasource that points to a web service exposed by ESB.
When I see ODI Topology Manager, I can identify these options.
Denis

Dynamic Partner links in BPEL (or ESB

Can we dynamically define Partner links at runtime and at runtime decide to call these services? If yes, can we also dynamically map the schemas?
BPEL cook book provides an example to for creating Dynamic Partner but this requires redeploying the WSDL?
This is not acceptable because redeploying the WSDLwill effect other processes running.

Just for your information it is recommended when dealing with Batch type processing that the you do not use BPEL variables larger than 5MB.
Therefore is this is the case it might be worth considering a mechanism (as described above) to de batch the process to provide a flow of data rather than a big hit of data.
Hope that Helps
Dave

Error while invoking BPEL from ESB

Hi All,
I am try'n to invoke BPEL process from ESB services ,where my BPEL process contains a webservice which has an input parameter of type ,a customized bean.
I am hitting with the below error
<env:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>env:Server</faultcode>
<faultstring>oracle.tip.esb.server.common.exceptions.BusinessEventRetriableException: An unhandled exception has been thrown in the ESB system. The exception reported is: "oracle.tip.esb.server.common.exceptions.BusinessEventRetriableException: An unhandled exception has been thrown in the ESB system. The exception reported is: "org.collaxa.thirdparty.apache.wsif.WSIFException: exception on JaxRpc invoke: serialization error: java.lang.IllegalArgumentException: getSerializer requires a Java type and/or an XML type at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeOperation(WSIFOperation_JaxRpc.java:1714) at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeRequestResponseOperation(WSIFOperation_JaxRpc.java:1460) at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.executeRequestResponseOperation(WSIFOperation_JaxRpc.java:1182) at oracle.tip.esb.server.common.wsif.WSIFInvoker.executeOperation(Unknown Source) at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(Unknown Source) at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(Unknown Source) at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.nextService(Unknown Source) at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.processBusinessEvent(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(Unknown Source) at oracle.tip.esb.server.dispatch.BusinessEvent.raise(Unknown Source) at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(Unknown Source) at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(Unknown Source) at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(Unknown Source) at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(Unknown Source) at oracle.tip.esb.server.dispatch.BusinessEvent.raise(Unknown Source) at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.raiseEvent(Unknown Source) at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.processMessage(Unknown Source) at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:869) at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349) at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:460) at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114) at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96) at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177) 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:298) at java.lang.Thread.run(Thread.java:595) ". at oracle.tip.esb.server.common.wsif.WSIFInvoker.executeOperation(Unknown Source) at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(Unknown Source) at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(Unknown Source) at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.nextService(Unknown Source) at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.processBusinessEvent(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(Unknown Source) at oracle.tip.esb.server.dispatch.BusinessEvent.raise(Unknown Source) at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(Unknown Source) at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(Unknown Source) at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(Unknown Source) at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(Unknown Source) at oracle.tip.esb.server.dispatch.BusinessEvent.raise(Unknown Source) at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.raiseEvent(Unknown Source) at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.processMessage(Unknown Source) at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:869) at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349) at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:460) at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114) at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96) at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177) 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:298) at java.lang.Thread.run(Thread.java:595) Caused by: org.collaxa.thirdparty.apache.wsif.WSIFException: exception on JaxRpc invoke: serialization error: java.lang.IllegalArgumentException: getSerializer requires a Java type and/or an XML type at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeOperation(WSIFOperation_JaxRpc.java:1714) at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeRequestResponseOperation(WSIFOperation_JaxRpc.java:1460) at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.executeRequestResponseOperation(WSIFOperation_JaxRpc.java:1182) ... 39 more ". </faultstring>
<faultactor/>
</env:Fault>
</env:Body>
</env:Envelope>
Help me out form this issue...
& pls let me know if iam not clear.
Regards,
Kalyan patti.
Message was edited by: kalyan
patti

Hi,
Refer below thread and links for more information. Hope this should help you guys.
ESB Not allowing to call Secured Service
Regards

Error while invoking ESB process from a BPEL process

Hi all
We have a requirement to call an ESB process from a BPEL process. We are using an adapter wth the ESB's WSDL url. After deploying the BPEL process, the registered ESB is getting called for most values while suddenly some values return the followign error
*"exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Connection reset"*
The catch here is, if we re-run the process with the same values again, the ESB is called successfully! How is it possible for a process to error out and run normally for the same inputs ?
What could be the possible fix for this? I am thankful for any inputs on this.
Vijay

Hi Vijay,
This is a bug and you can refer the metalink note:
"Applying Patch 7445876 Results in Error "java.lang.NullPointerException". [ID 942575.1]" for reference.
Also you can refer the following link:
"http://puchaanirudh.blogspot.com/2008/12/exception-on-jaxrpc-invoke-http.html" also.
Thanks,
Vishwanath.

Unable execute a BPEL process calling esb db outbound service

getting the following error while invoking an esb db service from a synchronous bpel process
<Faulthttp://schemas.xmlsoap.org/soap/envelope/>
<faultcode>env:Server</faultcode>
<faultstring>com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is 3f3d2d8955322f32:-40315b29:10d588f5253:-7fd3. Please check the process instance for detail.</faultstring>
</Fault>
Please help.
Thanx
AJ

thanx for your reply Dave,
When I get this error, nothing shows up in the instance screen.
Also, I had to configure the partner link using the wsdl provided in definitions tab in the esb console (since the service explorer in jdev throws an exception: service not found". So, i did cut and paste only and it parsed perfectly. i am using the concrete url available in the definitions tab in esb console.
And what wud u mean by esb rt endpoint?
Where can I find the wsil browser in bpel
I am still tryig to figure out the cause of the problem here.
I tried the following today:
- created a new esb project
- created a new esb system
- created a db adaptor service with a simple select from a db table (The db table has only one record and one column)
- created a routing service for the same, with no routing rules or transformations
- registered the same with the esb server
- created a new synchronous bpel process
- created a partner link (using concrete wsdl available in the definitions tab in esb control)
- assigned the input and output variable to the partner link.
- deployed the bpel process
- initiated a new instance of the same from the bpel console
- received the following error "<Faulthttp://schemas.xmlsoap.org/soap/envelope/>
<faultcode>env:Server</faultcode>
<faultstring>com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is 3f3d2d8955322f32:3ac11df3:10d5df12505:-7fb6. Please check the process instance for detail.</faultstring>
</Fault>"
- in the bpel console flow of the instance found the following error stack
"<bindingFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>exception on JaxRpc invoke:
start fault message:
oracle.tip.esb.server.common.exceptions.BusinessEventRetriableException: An unhandled exception has been thrown in the ESB system. The exception reported is: "oracle.tip.esb.server.common.exceptions.BusinessEventRetriableException: An unhandled exception has been thrown in the ESB system. The exception reported is: "java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0
     at java.util.Vector.get(Vector.java:710)
     at oracle.tip.esb.server.common.wsif.WSIFInvoker.readResponseHeader(Unknown Source)
     at oracle.tip.esb.server.common.wsif.WSIFInvoker.executeOperation(Unknown Source)
     at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(Unknown Source)
     at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.nextService(Unknown Source)
     at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.processBusinessEvent(Unknown Source)
     at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(Unknown Source)
     at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(Unknown Source)
     at oracle.tip.esb.server.dispatch.BusinessEvent.raise(Unknown Source)
     at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(Unknown Source)
     at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(Unknown Source)
     at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(Unknown Source)
     at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(Unknown Source)
     at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(Unknown Source)
     at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(Unknown Source)
     at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(Unknown Source)
     at oracle.tip.esb.server.dispatch.BusinessEvent.raise(Unknown Source)
     at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.raiseEvent(Unknown Source)
     at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.processMessage(Unknown Source)
     at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:869)
     at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
     at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:460)
     at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
     at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96)
     at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177)
     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.AJPRequestHandler.run(AJPRequestHandler.java:302)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)
     at oracle.tip.esb.server.common.wsif.WSIFInvoker.executeOperation(Unknown Source)
     at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(Unknown Source)
     at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.nextService(Unknown Source)
     at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.processBusinessEvent(Unknown Source)
     at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(Unknown Source)
     at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(Unknown Source)
     at oracle.tip.esb.server.dispatch.BusinessEvent.raise(Unknown Source)
     at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(Unknown Source)
     at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(Unknown Source)
     at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(Unknown Source)
     at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(Unknown Source)
     at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(Unknown Source)
     at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(Unknown Source)
     at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(Unknown Source)
     at oracle.tip.esb.server.dispatch.BusinessEvent.raise(Unknown Source)
     at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.raiseEvent(Unknown Source)
     at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.processMessage(Unknown Source)
     at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:869)
     at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
     at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:460)
     at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
     at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96)
     at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177)
     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.AJPRequestHandler.run(AJPRequestHandler.java:302)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0
     at java.util.Vector.get(Vector.java:710)
     at oracle.tip.esb.server.common.wsif.WSIFInvoker.readResponseHeader(Unknown Source)
     ... 34 more
:end fault message</summary>
</part></bindingFault>"
- the instance was visible in esb console too and the following error message was present
"An unhandled exception has been thrown in the ESB system. The exception reported is: "java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0 at java.util.Vector.get(Vector.java:710) at oracle.tip.esb.server.common.wsif.WSIFInvoker.readResponseHeader(Unknown Source) at oracle.tip.esb.server.common.wsif.WSIFInvoker.executeOperation(Unknown Source) at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(Unknown Source) at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.nextService(Unknown Source) at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.processBusinessEvent(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(Unknown Source) at oracle.tip.esb.server.dispatch.BusinessEvent.raise(Unknown Source) at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(Unknown Source) at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(Unknown Source) at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(Unknown Source) at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(Unknown Source) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(Unknown Source) at oracle.tip.esb.server.dispatch.BusinessEvent.raise(Unknown Source) at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.raiseEvent(Unknown Source) at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.processMessage(Unknown Source) at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:869) at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349) at oracle"
apologies for the long msg, but i just wanted you to give the whole picture in one shot. I am really struggling to figure this out.
thanx
AJ
Message was edited by:
jashutosh
Message was edited by:
jashutosh

PI 7.11 ESB hangs on startup

Hi Gurus
Would love your help with this one!
We have a PI 7.11 SP4 landscape and a particular user cannot launch the QA server's Enterprise Services Builder. She used to be able to, but now when she clicks on the link, she gets the login prompt, enters her details and then an "ESB process" appears on the Windows taskbar. This process can't be maximized or right-clicked on to do anything useful.
The weird thing is, if she tries to launch the Integration Builder from the same server, it works. If I try to launch the ESB, logging in as me or XISUPER, on her PC, it also works. If she tries to launch the ESB from any other server than the QA server, it also works! Nobody else has a problem, so I assume the server is correct and, since she can use ESB elsewhere, that the Java installation on her PC is fine.
I guess there's a cache or lock somewhere that I need to clear out, but where? I've bounced the server, refreshed all the caches I can think of and deleted the adapter engine cache, but no luck.
The PC's we're using are Vista ones and the backend PI server is RHEL Linux if that matters. Java runtime on Vista is 1.6 but there is also 1.4 installed.
Thanks for any help!
Chris

Doh.
It was a windows problem. The ESR was launching but I needed to do the "alt-SPACEBAR-X" trick in order to see the window.
No idea what happened there, but it's fixed now.

Error calling BPEL from ESB Multi-part simple type

I am trying to define a soap service in ESB which is refering a BPEL service. I get the error
The selected porttype is using a message that is invalid for ESB because it is multi-part or has a simple type.The message RuntimeFaultMessage in operation process of port type exportCaCustomers is invalid. Please select another portype.
Here is the wsdl for the BPEL service. exportCaCustomers.wsdl
<definitions
name="exportCaCustomers"
targetNamespace="http://xmlns.oracle.com/exportCaCustomers"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:ns1="http://www.globalcompany.com/ns/order"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:ns3="http://usconcrete.com/v1/interfaces/common/InputMessage.xsd"
xmlns:ns2="http://schemas.oracle.com/bpel/extension"
xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
xmlns:client="http://xmlns.oracle.com/exportCaCustomers"
xmlns:ns10="http://usconcrete.com/v1/interfaces/common/InputMessage.xsd"
>
<import namespace="http://schemas.oracle.com/bpel/extension" location="RuntimeFault.wsdl"/>
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:ns1="http://www.globalcompany.com/ns/order"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:client="http://xmlns.oracle.com/exportCaCustomers">
<import namespace="http://xmlns.oracle.com/exportCaCustomers" schemaLocation="exportCaCustomers.xsd"/>
</schema>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns1="http://www.globalcompany.com/ns/order"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:client="http://xmlns.oracle.com/exportCaCustomers">
<xsd:import namespace="http://www.globalcompany.com/ns/order" schemaLocation="sampleTax.xsd"/>
</xsd:schema>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://usconcrete.com/v1/interfaces/common/InputMessage.xsd" schemaLocation="InputMessage.xsd"/>
</xsd:schema>
</types>
<message name="exportCaCustomersRequestMessage">
<part name="payload" element="ns10:CVInputMessage"/>
</message>
<message name="exportCaCustomersResponseMessage">
<part name="payload" element="client:exportCaCustomersProcessResponse"/>
</message>
<portType name="exportCaCustomers">
<operation name="process">
<input message="client:exportCaCustomersRequestMessage"/>
<output message="client:exportCaCustomersResponseMessage"/>
<fault name="bindingFault" message="ns2:RuntimeFaultMessage"/>
</operation>
</portType>
<plnk:partnerLinkType name="exportCaCustomers">
<plnk:role name="exportCaCustomersProvider">
<plnk:portType name="client:exportCaCustomers"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>
These are the contents of RuntimeFault.wsdl
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="RuntimeFault"
targetNamespace="http://schemas.oracle.com/bpel/extension"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<message name="RuntimeFaultMessage">
<part name="code" type="xsd:string"/>
<part name="summary" type="xsd:string"/>
<part name="detail" type="xsd:string"/>
</message>
</definitions>
This looks like a very basic thing to do. My BPEL process is working fine. I just want to access it from ESB. Any ESB gurus there. Please respond.

<fault name="bindingFault" message="ns2:RuntimeFaultMessage"/>Don't think this is the way to define the RuntimeFaults.
the fault-element you use to 'throw' you own business faults.
RunTimeFaults are handled by the bpel framework itself and aren't throwable like this.
See :
http://www.oracle.com/technology/products/ias/bpel/htdocs/orabpel_technotes.tn007.html
""Business faults are application specific faults and occur when an explicit <throw> activity is executed or an <invoke> activity gets a fault as response. The fault name of a business fault is specified by the BPEL process and the messageType, if one exists, is defined in the WSDL.
Runtime faults are not user defined and will not appear in the WSDL for a process or service.""

Error while invoking ESB which contains Adapters

Hi All,
In the BPEL process we are getting below error while invoking ESB’s which contains Adapters :
Exception not handled by the Collaxa Cube system.
An unhandled exception has been thrown in the Collaxa Cube system. The exception reported is: "java.rmi.RemoteException: Cannot resolve Uddi Location on domain
     at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:356)
     at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:285)
     at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:829)
     at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:412)
     at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:199)
     at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3714)
     at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1657)
     at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:220)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:317)
     at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5787)
     at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1089)
     at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:589)
     at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:421)
     at sun.reflect.GeneratedMethodAccessor87.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
     at com.evermind.server.ThreadState.runAs(ThreadState.java:693)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
     at CubeDeliveryBean_LocalProxy_4bin6i8.handleInvoke(Unknown Source)
     at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:37)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:141)
     at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:58)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
     at java.lang.Thread.run(Thread.java:619)
Exception: java.rmi.RemoteException: Cannot resolve Uddi Location on domain
Handled As: com.collaxa.cube.CubeException
If anyone has faced similar issue or is familiar with the error, please let us know what could be the possible cause and what is the resolution.
Thanks & Regards,
Vivek Vishal

Hi Vijay,
This is a bug and you can refer the metalink note:
"Applying Patch 7445876 Results in Error "java.lang.NullPointerException". [ID 942575.1]" for reference.
Also you can refer the following link:
"http://puchaanirudh.blogspot.com/2008/12/exception-on-jaxrpc-invoke-http.html" also.
Thanks,
Vishwanath.

What's the meaning of a yellow DB-Adapter service in an ESB Instance?

Hi Forum,
I have implemented a really small ESB routing application, taking 3 Values, which will be written to a database using a routing service and a DB-Adapter. When calling this service via URI of the local endpoint (at the definition tab of ESB Control) everything works fine so far.
Next I tried to invoke this service from a BPEL process. But all I got was a yellow marked DB-Adapter in the ESB instance. This is accompanied by a R tag on the adapter. The details tab states that a rollback has been done because of an error "undefined" on a non transactional endpoint.
By the way, there is no error tab displayed in ESB Control and moreover no BPEL instance is logged. I asume that is a result of the rollback. So there is pretty few information on what has happened.
Unfortunately I couldn't find anything of value on the web dealing with non transactional endpoints.
Has anyone got a clue, what the reason for this strange behavior could be?
TIA,
Marco

Hi James,
thanks a lot for your answer. You've been totally right, it was a error in payload. Actually, after fiddling about with no success to get it right, I ended up with no ESB instance trace at all :-(
So I decided to restart the server and guess what, everything looked nice. The instance came up with tracking information and error log showing that the payload was incomplete.
And even the main problem of being unable to deploy a BPEL-Process because of an undefined partner link type (which I couldn't follow as the PLT was enclosed in the wsdl of the ESB service and that led me to designing a small repro case) vanished into thin air.
This SOA-Suite seems to be a sort of weird. At the moment I can't figure out how to successfully run a real-life project using this technology :-(
Working on a research project now, I hope to be getting more experienced before it gets down to business.
Cheers
Marco

Response not coming back to ESB when calling BPEL process

Hi,
I am doing some demo,
the actual process is, in ESB, I am reading a file and passing thsoe fiel contents to BPEL as SOAP service. In BPEL proecess, I processed the message and sending the response back to the ESB. When I deployed and check the process flow in the BPEL console, everything looks fine, I mena, it sending the response back to the ESB, where as in ESB process, I am not able to see the response.
Is there any thing that I am missing?
Thanks.

Is the BPEL process a synchronous process?
Also for performance reasons it it best to call BPEL process via the direct jca connector not SOAP.
You do this by just selecting the BPEL process in the routing service going through the wizard. There is no need to creat a SOAP service. The good this about this is that in the ESB process it provides a link to the BPEL process.
cheers
James

Problem when used ESB put file to AS400

Hello All,
I create ESB for put files from Win2003 to AS400 by outbound FTP Adapter Service.
I never used AS400 before.I test esb with windows environment it work but when move to as400 that error.
I test with FTP command i can put file like below.
F:\ProductionProject\ESBdeployLib>ftp 172.16.8.59
Connected to 172.16.8.59.
220-QTCP at AS400DEV.
User (172.16.8.59:(none)): HATCYRD
331 Enter password.
Password:
230 HATCYRD logged on.
ftp> put deploy.bat
200 PORT subcommand request successful.
150 Sending file to member BAT in file DEPLOY in library YRDDTALIB.
226 File transfer completed successfully.
ftp: 50 bytes sent in 0.00Seconds 50000.00Kbytes/sec.
I want to put file at root directory of ftp.
What value that I should set directory specific to logical Name with end point properties parameter name "outgoingFilePath".
and error that not display.
this is error when I set outgoingFilePath with value 'YRDDTALIB'.
An unhandled exception has been thrown in the ESB system. The exception reported is: "org.collaxa.thirdparty.apache.wsif.WSIFException:
esb:///ESB_Projects/temp_ESB_YBRTServiceProject_localhost/putLOG_DOMESTICCARLOCATION.wsdl [ Put_ptt::Put(Root-Element) ] - WSIF JCA Execute of operation 'Put' failed due to: Wrong logical to physical
output directory mapping. No mapping found for logical output directory to physical output directory. ; nested exception is: ORABPEL-11047 Wrong logical to physical output directory mapping. No mapping found for
logical output directory to physical output directory. For the value specified in the (Physical/Logical)Directory parameter, ensure that the mapping from logical name<->physical directory is correctly specified in the
deployment descriptor. at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:623) at
this is error when I set outgoingFilePath with empty value '' or '.'.
[ Put_ptt::Put(Root-Element) ] - WSIF JCA Execute of operation 'Put' failed due to: Error sending file to FTP Server. Unable to send file to server. ; nested exception is: ORABPEL-11429 Error sending file to FTP Server. Unable to send file to server. Please ensure 1. Specified remote output Dir has write permission 2. Output filename has not exceeded the max chararters allowed by the OS and 3. Remote File System has
Regards,
Weerawat

Hi James
from link:[http://www.mcpressonline.com/networking/general/the-one-as/400-ftp-command-you-must-understand.html]
I found FTP by ESB not support AS400 .I think because ESB work on mode "NAMEFMT 1"
but normal it must be "NAMEFMT 0" .
if NAMEFMT 0 it view mode library and can't see "/" root path.
I develop java program for FTP to AS400 that work correctly but esb can't.So I think ESB work on "NAMEFMT 1".
this is result of ftp command
Connected to 172.16.8.59.
220-QTCP at AS400DEV.
220 Connection will close if idle more than 5 minutes.
User (172.16.8.59:(none)): HATCYRD
331 Enter password.
Password:
230 HATCYRD logged on.
ftp> ls
200 PORT subcommand request successful.
125 List started.
TEST_23.TOP
YBRT.YBRT
YDLV.YDLV
YEQM.YEQM
YGPX.YGPX
YISU.YISU
YSTS.YSTS
250 List completed.
ftp: 96 bytes received in 0.16Seconds 0.62Kbytes/sec.
ftp> pwd
257 "YRDDTALIB" is current library.
ftp> quote site name 1
250 Now using naming format "1".
ftp> pwd
257 "/QSYS.LIB/YRDDTALIB.LIB" is current library.
ftp> ls
200 PORT subcommand request successful.
125 List started.
TEST_23.FILE/TOP.MBR
YBRT.FILE/YBRT.MBR
YDLV.FILE/YDLV.MBR
YEQM.FILE/YEQM.MBR
YGPX.FILE/YGPX.MBR
YISU.FILE/YISU.MBR
YSTS.FILE/YSTS.MBR
250 List completed.
ftp: 168 bytes received in 0.31Seconds 0.54Kbytes/sec.
ftp>
ftp> cd /
250-NAMEFMT set to 1.
250 "/" is current directory.
ftp> open 172.16.8.59
Connected to 172.16.8.59.
220-QTCP at AS400DEV.
220 Connection will close if idle more than 5 minutes.
User (172.16.8.59:(none)): HATCYRD
331 Enter password.
Password:
230 HATCYRD logged on.
ftp> put TEST /QSYS.LIB/YRDDTALIB.LIB/TEST_01.FILE
200 PORT subcommand request successful.
150 Sending file to member TEST_01 in file TEST_01 in library YRDDTALIB.
226 File transfer completed successfully.
ftp: 6 bytes sent in 0.00Seconds 6000.00Kbytes/sec.
ftp> pwd
257 "/QSYS.LIB/YRDDTALIB.LIB" is current library.
ftp> ls
200 PORT subcommand request successful.
125 List started.
TEST_01.FILE/TEST_01.MBR
TEST_23.FILE/TOP.MBR
YBRT.FILE/YBRT.MBR
YDLV.FILE/YDLV.MBR
YEQM.FILE/YEQM.MBR
YGPX.FILE/YGPX.MBR
YISU.FILE/YISU.MBR
YSTS.FILE/YSTS.MBR
250 List completed.
ftp: 168 bytes received in 0.13Seconds 1.34Kbytes/sec.
ftp>
I want to put file by FTP on my login library name "YRDDTALIB".
Normally if mode NAMEFMT 1 in ftp command must used "put TEST /QSYS.LIB/YRDDTALIB.LIB/TEST_01.FILE ".
Can ESB to do this ?
If FTPadapter support NAMEFMT 0 how i set to NAMEFMT 0 ?
this is my oc4j-ra.xml
<connector-factory location="eis/Ftp/FtpAdapter" connector-name="Ftp Adapter">
          <config-property name="host" value="172.16.8.59"/>
          <config-property name="port" value="21"/>
          <config-property name="username" value="HATCYRD"/>
          <config-property name="password" value="PASSWORD"/>
          <config-property name="ftpAbsolutePathBegin" value="/"/>
          <config-property name="ftpPathSeparator" value="/"/>
          <config-property name="keepConnections" value="true"/>
          <config-property name="serverType" value="unix"/>
          <config-property name="serverLocaleLanguage" value=""/>
          <config-property name="serverLocaleCountry" value=""/>
          <config-property name="serverLocaleVariant" value=""/>
          <config-property name="serverEncoding" value=""/>
          <config-property name="useFtps" value="false"/>
          <config-property name="useImplicitSSL" value="false"/>
          <config-property name="walletLocation" value="C:\wallet\ewallet.p12"/>
          <config-property name="walletPassword" value="welcome1"/>
          <config-property name="channelMask" value="both"/>
          <config-property name="securePort" value="990"/>
          <config-property name="keyStoreProviderName" value=""/>
          <config-property name="keystoreType" value=""/>
          <config-property name="keystoreAlgorithm" value=""/>
          <config-property name="enableCipherSuits" value=""/>
          <config-property name="proxyHost" value=""/>
          <config-property name="proxyPort" value=""/>
          <config-property name="proxyUsername" value=""/>
          <config-property name="proxyPassword" value=""/>
          <config-property name="proxyType" value=""/>
          <config-property name="proxyDefinitionFile" value=""/>
          <config-property name="useProxy" value="false"/>
          <config-property name="useSftp" value="false"/>
          <config-property name="authenticationType" value="password"/>
          <config-property name="preferredKeyExchangeAlgorithm" value="diffie-hellman-group1-sha1"/>
          <config-property name="preferredCompressionAlgorithm" value="none"/>
          <config-property name="preferredDataIntegrityAlgorithm" value="hmac-md5"/>
          <config-property name="preferredPKIAlgorithm" value="ssh-rsa"/>
          <config-property name="privateKeyFile" value=""/>
          <config-property name="preferredCipherSuite" value="blowfish-cbc"/>
          <config-property name="transportProvider" value="socket"/>
          <connection-pooling use="none">
          </connection-pooling>
          <security-config use="none">
          </security-config>
     </connector-factory>
Thank
Weerawat
Edited by: user1442964 on May 6, 2009 12:54 AM
Edited by: user1442964 on May 6, 2009 3:14 AM
Edited by: user1442964 on May 6, 2009 3:15 AM

Error Handling in BPEL & ESB - Rejection Handlers

Hi guys
I have been trying to evaluate various ways for handling errors/exceptions in BPEL and ESB in Oracle SOA Suite 10.1.3.4 (Basic installation).
What i have found is that in ESB, errors can be handled at two levels: ESB routing service errors using ERROR_TOPIC and Adapter errors using RejectionHandlers. AND
in BPEL errors can be handled using in built try/catch (calling error hospital from the catch) and adapter erros using RejectionHandlers.
I tried using Rejection handlers (bpel, wsif, file) in BPEL and ESB. In BPEL they all are working fine when registered in bpel.xml.
But in ESB only the file handler is working. What i did in ESB is:
I set up an ESB which is polling a file adapter and simply putting the data into a table in database.
Then i created a BPEL (or a Webservice) which is based on http://localhost:8888/orabpel/xmllib/jca/RejectionMessage.wsdl file, taking
{http://xmlns.oracle.com/pcbpel/errorHandling}RejectedMessage as input.
Then I registered Rejection Handler in ESB's file adapter's .esbsvc (or Enpoint property- rejectedMessageHandlers):
"wsif://http//localhost8888/Error_Service/RejectionHandlerPort?wsdl|handleRejection|message"OR "bpel://default:welcome1|BPEL_Error_Handler|handleRejection|message"
I generated error in ESB by changing a column name of the table
For bpel rejection handler:
i was getting error: "<ERROR> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Rejection handler failed
Error while trying to hand off bad message to Rejection handler bpel://default|BPELProcess2|handleRejection|message due to: java.lang.Exception: Failed to create "ejb/collaxa/system/DeliveryBean" bean; exception reported is: "javax.naming.NameNotFoundException: ejb/collaxa/system/DeliveryBean not found
at com.evermind.server.rmi.RMIServerContext.lookup(RMIServerContext.java:207)
at com.evermind.server.ApplicationContext.unprivileged_lookup(ApplicationContext.java:256)
at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:196)
at javax.naming.InitialContext.lookup(InitialContext.java:351)"
It was solved by adding in server.xml - <application-server ... global-jndi-lookup-enabled="true">. But now i am getting
"Error while trying to hand off bad message to Rejection handler bpel://default:welcome1|BPEL_Error_Handler|handleRejection|message due to: java.lang.LinkageError: duplicate class definition: com/oracle/bpel/client/ejb/interfaces/IDeliveryBeanHome. Please address the underlying issue or correct/redeploy the process."
*For wsif rejection handler*:
getting error: "Error while trying to hand off bad message to Rejection handler wsif://http//localhost8888/Error_webservices/RejectionHandlerPort?WSDL|handleRejection|message due to: exception on JaxRpc invoke: serialization error: java.lang.IllegalArgumentException: getSerializer requires a Java type and/or an XML type
Please address the underlying issue or correct/redeploy the process."
I followed: Link:[http://www.oracle.com/technology/products/integration/adapters/pdf/Adapter_TN_004_Adapter_ErrorManagement.pdf]
Same bpel/wsif handlers pointing to same BPEL/J2EE services, if configured for BPEL adapters, works absolutly fine and gives proble in ESB.
Am i missing something in ESB or is there any patch need to be applied? Please help me there.
Thanks in advance.
Inder

Hi
I even installed SOA Suite 10.1.3.4 MLR#5 Advanced installation with Oracle Express dehyderation store.
I was able to use WSIF rejection handler with this upgrade... but bpel rejection handler was still a failure.
So basically i re-visited ESB documentation. it says that ESB will not support bpel rejection handler.
At least not upto now.
So Summary:
For BPEL we can use - file, wsif, bpel & aq rejection and fatal message handler.
For ESB we can use file, WSIF (10.1.3.4 with MLR#5) & aq rejection and fatal message handler.
Thanks
Inder
Keep going...

Exception in ESB Header Functions (ehdr:getRequestHeader)

Hi,
I was working on the context based routing in the ESB.
My scenario is a simple File to File scenario where I want to make some changes
in the Filter Expressions in the Routing service part.
I want to include the Header functions in order to route the file adapters.
If I Input some two text files of different name in Input File what file name I have
specified in the Header must only written in the Output File.
For this I am trying it in RS Filter Expression part and when I drop the Header
function ehdr:getRequestHeader function some exception is shown like
Funtion of name "ehdr:getRequestHeader" not Found .
I was also using the sample Headersupport demo working component which they
have specified in the following link.
http://www.oracle.com/technology/products/integration/esb/files/esb-presentation-headers.pdf
Anyone have Idea on this.

See the samples on the new ESB OTN page. http://www.oracle.com/technology/products/integration/esb/index.html
There isn't much GUI support but look at the JMS sample jdev project and study the filters for routing and xsl for setting headers. The hardest part is setting the namespaces correctly.

ESB Link

Similar Messages

Maybe you are looking for