IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Back to discussions
Expand all | Collapse all

Can't invoke wm.ip.rn:receive

  • 1.  Can't invoke wm.ip.rn:receive

    Posted Mon August 14, 2006 11:08 PM

    Hi,

    When I try to invoke wm.ip.rn:receive at browser, I always get a 403 code. The IS also show below log. Pls advise how to solve the problem. Thanks!!

     com.wm.lang.flow.FlowException: ip.rn.receive(): Error trapped in 
service: wm.ip.rn:receive Error: 
com.wm.app.b2b.server.Service.getParentServiceName()Ljava/lang/String; 
Occured at: 2006/08/15 05:12:08.486 Service Call 
Stack:wm.ip.rn:receiveat 
com.wm.lang.flow.FlowExit.getFailure(FlowExit.java:250)at 
com.wm.lang.flow.FlowState.willExit(FlowState.java:268)at 
com.wm.lang.flow.FlowSequence.invoke(FlowSequence.java:196)at 
com.wm.lang.flow.FlowRoot.invoke(FlowRoot.java:258)at 
com.wm.lang.flow.FlowState.invokeNode(FlowState.java:580)at 
com.wm.lang.flow.FlowState.step(FlowState.java:438)at 
com.wm.lang.flow.FlowState.invoke(FlowState.java:403)at 
com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1749)at
com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554)at 
com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44)at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221)at 
com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49)at 
com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194)at 
com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39)at 
com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384)at
com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486)at 
com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359)at 
com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246)at
com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:128)at
com.wm.app.b2b.server.HTTPInvokeHandler._process(HTTPInvokeHandler.java:138)at 
com.wm.app.b2b.server.InvokeHandler.process(InvokeHandler.java:113)at 
com.wm.app.b2b.server.Dispatch.run(Dispatch.java:298)at 
com.wm.util.pool.PooledThread.run(PooledThread.java:105)at 
java.lang.Thread.run(Thread.java:534)
     
java.lang.reflect.InvocationTargetException: 
com.wm.app.b2b.server.Service.getParentServiceName()Ljava/lang/String;at
com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:340)at 
com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554)at 
com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44)at 
com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221)at 
com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49)at 
com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194)at 
com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39)at 
com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384)at
com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486)at 
com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359)at 
com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246)at
com.wm.app.b2b.server.BaseService.invoke(BaseService.java:155)at 
com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:324)at 
com.wm.lang.flow.FlowState.invokeNode(FlowState.java:580)at 
com.wm.lang.flow.FlowState.step(FlowState.java:438)at 
com.wm.lang.flow.FlowState.invoke(FlowState.java:403)at 
com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1749)at
com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554)at 
com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44)at 
com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221)at 
com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49)at 
com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194)at 
com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39)at 
com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384)at com.wm.app.b2b.server.invoke.InvokeManager.invoke

    #B2B-Integration
    #Integration-Server-and-ESB
    #webMethods


  • 2.  RE: Can't invoke wm.ip.rn:receive

    Posted Tue August 15, 2006 02:03 AM

    whats the reason of invoking RNO gateway service from browser?You should set it up in TN Delivery URL or invoke thru http/s post to receive PIP’s. What you are trying to do??
    Are you stimulating as if your partner is sending RN PIP to your IS??

    HTH,
    RMG


    #webMethods
    #B2B-Integration
    #Integration-Server-and-ESB


  • 3.  RE: Can't invoke wm.ip.rn:receive

    Posted Wed August 30, 2006 05:41 AM

    To put it simply, wm.ip.rn:receive is not designed to be invoked by a browser. It requires that the client is a RosettaNet compliant end-point (i.e. at least RNIF1.1 or RNIF2.0), and that a RNO or RBM is submitted. A browser is neither.


    #Integration-Server-and-ESB
    #B2B-Integration
    #webMethods


Related Content