Hi All,
I need help from you guys.
Current version we are using is SAG 8.2.2 version.
We are trying to create connectivity between Tibco (version BW 5.7) and webMethods using web services.
We got some wsdl’s from Tibco Team and we created consumers at wM end. However, wM is not able to communicate with Tibco wsdls.
Here is the error we are getting, wsdl is created using RPC Iiteral style.

Find WSDL in attachment

Thanks in advance!!

Error:
com.wm.app.b2b.server.ServiceException: org.apache.axis2.AxisFault: An HTTP transport error occured. Error Code: 404, Error Message: No such object: WMService
at pub.clientimpl.wssClient(clientimpl.java:2957)
at pub.clientimpl.soapClient(clientimpl.java:1308)
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:597)
at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:439)
at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:643)
at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:46)
at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44)
at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:243)
at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:51)
at com.wm.app.b2b.server.invoke.PipelineProcessor.process(PipelineProcessor.java:171)
at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:276)
at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:30)
at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:363)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:547)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:386)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:234)
at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:194)
at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:324)
at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:584)
at com.wm.lang.flow.FlowState.stepIncremental(FlowState.java:494)
at com.wm.lang.flow.FlowState.invoke(FlowState.java:382)
at wm.server.flowdebugger.stepFlow(flowdebugger.java:935)
at wm.server.flowdebugger.execute(flowdebugger.java:465)
at sun.reflect.GeneratedMethodAccessor127.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:449)
at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:643)
at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:46)
at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44)
at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:243)
at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:51)
at com.wm.app.b2b.server.invoke.PipelineProcessor.process(PipelineProcessor.java:171)
at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:276)
at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:30)
at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:363)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:547)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:386)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:234)
at com.wm.app.b2b.server.comm.DefaultServerRequestHandler.handleMessage(DefaultServerRequestHandler.java:119)
at com.wm.app.b2b.server.HTTPMessageHandler.process(HTTPMessageHandler.java:160)
at com.wm.app.b2b.server.HTTPDispatch.handleRequest(HTTPDispatch.java:181)
at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:355)
at com.wm.util.pool.PooledThread.run(PooledThread.java:131)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.axis2.AxisFault: An HTTP transport error occured. Error Code: 404, Error Message: No such object: WMService
at com.wm.app.b2b.server.wss.HTTPTransportSender.makeFault(HTTPTransportSender.java:1060)
at com.wm.app.b2b.server.wss.HTTPTransportSender.handleResponse(HTTPTransportSender.java:708)
at com.wm.app.b2b.server.wss.HTTPTransportSender.writeMessageWithWebM(HTTPTransportSender.java:520)
at com.wm.app.b2b.server.wss.HTTPTransportSender.invoke(HTTPTransportSender.java:192)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:449)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:402)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at com.softwareag.wsstack.client.impl.WSOperationClientImpl.execute(WSOperationClientImpl.java:65)
at com.wm.app.b2b.server.wss.wssClientImpl.invokeWebService(wssClientImpl.java:282)
at pub.clientimpl.wssClient(clientimpl.java:2816)

wsdl with RPC.wsdl (1.46 KB)

Hello Mohamad, if you have access to empower - suggest to read KB article 1741954.

If it does not help - suggest open a Global Support ticket

Shmuel

Shmuel ,

I didnt find the KB article 1741954 in EMPOWER.

And am facing same above issue while calling java webServices to.

Please help me with more infomation here.

Any data will be kindful here.

Thanks
Shafi

Hi Shafi, I admit the article I mentioned does not exist.

If there is a proxy between IS consumer WSD and target Tibco web service - perhaps you need to configure in IS a proxy alias.

It is hard for me to understand why not open a Global Support ticket, stay well

Shmuel

Hi Shmuel,

Thanks for your information.

We are able to sort the issue. The problem was proxy setups in intranet.

We are able to call the TIBCO services with help of http alias proxy setups.

Thanks
Shafi

I am facing same issue can you please inform as to how this was resolved

Did you check the proxy setups (DMZ) as mentioned above if there is or firewall blocking etc…connecting to TIBCO site?

HTH,
RMG

client has confirmed that web service request is received by tibco server yet client responds with http 404 error

Please google on the 404 status error and you will get the hits of results.

one of the result:

So can you check with your network team regarding if any internal firewall is blocking the traffic from tibco’s request/response (2-way comm to wM server/endpoint) and troubleshoot behind the scenes?

HTH,
RMG

Hi BSR,
Please check with your networking team if firewall is open for incoming request from client.

Yes this would be first thing to check with internal network folks and make sure its not the bottle neck for your WS communication (endpoints).

Recommend you get a hold of SoapSonar Personal Edition and SoapUI and Fiddler.
Make sure those tools are able to read the wsdl, negotiate the authentication, deal with any ws-addressing, ws*, ssl issues.

Once you tests then have your functional tests then I would get latest fixes for designer,mediator,centrasite and try to get the wsdl into centrasite, then from centrasite into designer. Next steps would be to virtualize the service and deploy it to mediator.

Then i would use the tools again to do some testing against the virtual services.

Are you advising or is it another issue you are troubleshooting?