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.  EDIINT:receive - Invalid input - stream

    Posted Sun May 05, 2013 11:27 PM

    Hi,

    I’m trying to submit EDI document using “wm.EDIINT:receive” service as below:

    • pub.string:stringToBytes
    • pub.io:bytesToStream
    • wm.EDIINT:receive

    Inputs as below:
    protocol :: http
    message-ID :: 19153097.5.1366816884863.JavaMail.sam@fra12684
    contentType :: application/edi-X12
    AS2-From :: ABC
    AS2-To :: DEF
    stream :: stream which I formed as above

    But, I’m getting this error

    Invalid input - stream [EDIINT.000001.000003]

    Your views please.

    Regards,
    Sam
    Invalid input - stream [EDIINT.000001.000003]


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


  • 2.  RE: EDIINT:receive - Invalid input - stream

    Posted Mon May 06, 2013 11:44 AM

    What are you trying to do?

    Are you trying to send it to TN from another IS/TN?

    If you are sending it to some external partner routing via TN you should use
    wm.EDIINT:send and input mapping is stream (*ffdata)

    HTH,
    RMG


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


  • 3.  RE: EDIINT:receive - Invalid input - stream

    Posted Tue May 07, 2013 12:10 AM

    Hi RMG,

    I’m submitting from the same IS. I was submitting the data using wm.EDIINT:send, after converting the EDI data to Stream. During which I can see the transaction in TN.

    In RECEIVER DeliveryMethod tab, I’m invoking the wm.EDIINT:receive service Where I’m seeing the error in IS Admin page error log.

    So I tried executing the service “wm.EDIINT:receive” service directly, in both the way’s I’m getting the same error. Not sure where I’m doing the mistake…

    Regards,
    Sam.


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


  • 4.  RE: EDIINT:receive - Invalid input - stream

    Posted Tue May 07, 2013 12:24 AM

    Are you using certs in your testing and what encryption level are you sending to the Receiver?

    Try the testing with text/plain and see how the send/receive goes…Mimic the testing to send it to differrent IS/TN server receiving partner.

    EDIINT testing is not straight forward and some communication hiccups will be there. :frowning:

    HTH,
    RMG


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


  • 5.  RE: EDIINT:receive - Invalid input - stream

    Posted Tue May 07, 2013 12:41 AM

    :slight_smile: Yes I was doing the very plain vennila testing. Below are the inputs used for send.

    Type=plain
    compressed=false
    deliveryMethod=PrimaryHTTP
    data/contentType=application/edi-X12
    stream=input EDI data after convertion to stream
    requestMDN=false
    requestSignedReceipt=false
    senderID/id=**
    senderID/idTypeDesc=EDIINT AS2
    receiverID/id=**
    receiverID/idTypeDesc=EDIINT AS2
    TNFlags/prtIgnoreDocument=false

    Regards,
    Sam


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


  • 6.  RE: EDIINT:receive - Invalid input - stream

    Posted Tue May 07, 2013 01:12 PM

    Change this also to text/plain:

    data/contentType=application/edi-X12

    Also can you simulated it to send it to different IS that has EDIINT module installed (for receiving) etc…

    HTH,
    RMG


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


  • 7.  RE: EDIINT:receive - Invalid input - stream

    Posted Thu May 09, 2013 05:26 PM

    Hi RMG,

    During EDIINT:send service, for ‘Type’ field, I’m giving the value as “plain” which I selected from the drop down.

    We can’t give it as text/plain.

    Regards,
    Sam


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


  • 8.  RE: EDIINT:receive - Invalid input - stream

    Posted Fri May 10, 2013 12:13 PM

    What I mean was set contentType :text/plain just to make sure connectivity works fine:

    HTH,
    RMG


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