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
  • 1.  FTP to EDI VAN - issue

    Posted Tue September 20, 2011 02:48 AM

    Hi
    We are using webMethods 8.0 IS and MWS 8.0.3.0.97. The EDI messages are posted to the VAN using a service which posts the message to the EDI VAN using pub.client.ftp service. The service receives an FTP 350 return code but the files are finally delivered to the VAN, so MWS gives a wrong status as DONE W/ERRORS. Is there any way to track the correct status from VAN ftp and update MWS or is this a bug in MWS ?


    #edi
    #webMethods
    #Integration-Server-and-ESB


  • 2.  RE: FTP to EDI VAN - issue

    Posted Tue September 20, 2011 05:12 PM

    FTP 350 is not the right status code…

    Also you can try VAN connectivity services instead of client:ftp I know its the same service used internally by VAN connectivity services…

    You should get 226 successful transfer status back while ftp put:

    HTH,
    RMG


    #webMethods
    #edi
    #Integration-Server-and-ESB


  • 3.  RE: FTP to EDI VAN - issue

    Posted Tue September 20, 2011 09:02 PM

    Hi rmg, that is where this is intriguing because the ftp put results in return code 350 but the file is indeed delivered to the VAN. Following is the error message that we are getting:

    82511: com.wm.app.b2b.server.ServiceException: 350-Requested file action pending further information.
    Mailboxing SNRF: 82511.
    TIP status: Pending-awaiting confirmation of file status from remote EDI service.(0016)
    350
    at com.wm.app.b2b.server.Service.throwError(Service.java:484)
    at pub.client.ftp.put_append(ftp.java:913)
    at pub.client.ftp.put(ftp.java:833)
    at sun.reflect.GeneratedMethodAccessor247.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:635)
    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:238)
    at com.wm.app.b2b.

    Will try the VAN connectivity service i.e VAN.ftp:put.


    #Integration-Server-and-ESB
    #edi
    #webMethods


  • 4.  RE: FTP to EDI VAN - issue

    Posted Tue September 20, 2011 09:20 PM

    Search the web for “ftp 350” and you’ll see information regarding this return code.


    #webMethods
    #edi
    #Integration-Server-and-ESB


  • 5.  RE: FTP to EDI VAN - issue

    Posted Tue September 20, 2011 09:35 PM

    ftp 350 statuts indicates:

    350
    Requested file action pending further information.


    #webMethods
    #Integration-Server-and-ESB
    #edi