Http sender adapater

Hi All
when I am trying to send request through url for http sender adapter configuration between CLM(E-sourcing) system and PI, I am getting the following error.
Can any body help me out to resolve this issue.
The scenario is CLM - PI - SRM (HTTP - RFC scenario). CLM is the sender system and SRM is the receiver system.
I have checked each and every parameter in the url.
URL:
http://usaoadbld004:50000/sap/xi/adapter_plain?namespace=http://frictionless.esource.com/v2.0&interface=MI_ESI_OA&service=CLM_BUSINESS_COMPONENT&QOS=BE&sap-user=PIAPPLUSER&sap-password=&sap-client=001&sap-language=EN.
Error:
E-Sourcing was unable to publish Red Book Agreement to SRM. class java.io.IOException Server returned HTTP response code: 500 for URL: 
Thanks & Regards
MGREDDY

Can u check following:-
1. URL used for sending message to PI.
http://help.sap.com/saphelp_nw04/helpdata/en/43/64dbb0af9f30b4e10000000a11466f/frameset.htm
2. check HTTP port from SMICM tcode - Go- Services and use the same one.
chirag

Similar Messages

  • WHEN DOES UPDATE  HAPPEN IN JDBC SENDER Adapater

    Hi folks ,
    I am using jdbc sender adapater to call RFC function and the o/p pf the RFC i am writing to the file
    This is my select query
    SELECT * FROM ULIDTA2.F5631505 WHERE QSINTF='N'
    and mu update query is
    Update ULIDTA2.F5631505 set QSINTF='Y' where QSINTF='N'
    now the slect returns multiple rows and  i  want the rfc to be called depending on the number of rows i get 4m select . but wht is happening is i find that seleect picks the first row calls the rfc writes to the file and updates the query .
    hence other rows are not able to be processed .
    does jdbc sender update as soon as it picks the select query . how do i update one row at a time .
    thks
    amit

    Hi Amit,
    I dont think one row at a time is possible with the SELECT query as the JDBC adapter is going to return all the rows that satisfy your query.
    One work around would be to develop a Stored Procedure in your Datbase, and then use the same Stored Procedure as your select query. Now, tits the task of the stored procedure to make sure only one row is selected at a time.
    Just look at Query SQL Statement part ubnder this link,
    http://help.sap.com/saphelp_nw04/helpdata/en/7e/5df96381ec72468a00815dd80f8b63/content.htm
    Regards,
    Bhavesh

  • File Content Conversion in Sender Adapater

    Hi Folks ,
    I am doing a file 2 file scneario using content conversion at  both end
    My i/p and o/p is file is tab delimited
    My source xml structure is
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:file_sender_mt xmlns:ns0="urn:filetofiledemo">
       <recordset>
          <data1>
             <keyfield/>
             <age1/>
          </data1>
          <data>
             <name/>
             <keyfield/>
             <age/>
             <loc>
                <keyfield/>
             </loc>
          </data>
       </recordset>
    </ns0:file_sender_mt>
    Data and location have the mapping 1.. unbounded
    while data1 has the mapping 1.1
    When I am trying to read it as a tab delimited flat file.
    These are the parameters that i have set
    Document Name  file_sender_mt
    Document Namespace urn:filetofiledemo
    Recordset Name recordset
    Recordset Structure data1,1,data, ,loc,
    Key Field Name keyfield
    data1.fieldNames keyfield,age1
    ignoreRecordsetName true
    recordset.fieldSeparator '0'
    data1.fieldSeparator '0x09'
    data1.keyFieldValue 01
    data1.endSeparator '0'
    data.beginSeparator '0x09'
    data.fieldSeparator '0x09'
    data.fieldNames name,keyfield,age
    data.keyFieldValue 02
    loc.fieldSeparator '0x09'
    loc.beginSeparator '0x09'
    loc.endSeparator '0'
    loc.keyFieldValue 03
    loc.fieldNames keyfield
    My file is getting picked up . I dont see any message in message monitoring and neither anything in moni .
    No error in adapater
    but the file is not getting created .
    if i change the message protocol to file and send t above xml file . the scneario works fine
    any reasons for the above behaviour
    Thanks
    Amit

    I have found you cant use nested element in sender adapater
    so i have chnage my source structure to
    Now if i give my i/p file as
    01 age1
    02 25 03
    file is getting pciked up
    bt if i give it as
    01 age1 02 25 03
    which is the structure i expect my i/p file it is failing  to read with the error
    Error: Conversion of complete file content to XML format failed around position 0: Exception: ERROR converting document line no. 1 according to structure 'data1':java.lang.Exception: ERROR in configuration: more elements in file csv structure than field names specified!
    Does The special character ´0´ is not a separator character.
    not work for sender adapater bcoz in reciever i am able to get o/p in one line and tab delimited
    any idea
    and since i have given my keyfield as the second field in data
    02 would come at the second palce
    Thanks
    Amit

  • OTA-HTTP-SEND-401 Error

    Hi,
    We're getting a 401 error message from a Trading Partner (TP). They say there is no password required to get to their website. From their end, the request doesn't send a certificate with it. The TP certificate has 2048 keysize, while the wallet and our other TPs have 1024 keysize.
    Could the problem be with the transport endpoint or the TP certificate?
    Here is the error from the b2b.log:
    2009.05.05 at 15:06:03:520: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequestPostColab Invoking PackMessage
    2009.05.05 at 15:06:03:520: Thread-15: B2B - (DEBUG) MimePackaging:pack:Enter
    2009.05.05 at 15:06:03:525: Thread-15: B2B - (DEBUG) MimePackaging:createMimeMessage:Enter
    2009.05.05 at 15:06:03:535: Thread-15: B2B - (DEBUG) MimePackaging:createMimeMessage:number of pc components: 1
    2009.05.05 at 15:06:03:535: Thread-15: B2B - (DEBUG) MimePackaging:createMimeBodyPart:Enter
    2009.05.05 at 15:06:03:560: Thread-15: B2B - (DEBUG) MimePackaging:createMimeBodyPart:header name-value: Content-Type-application/EDI-X12; name=004010
    2009.05.05 at 15:06:03:560: Thread-15: B2B - (DEBUG) MimePackaging:createMimeBodyPart:header name-value: Content-Disposition-attachment; filename=004010
    2009.05.05 at 15:06:03:561: Thread-15: B2B - (DEBUG) MimePackaging:createMimeBodyPart:header name-value: Content-Transfer-Encoding-binary
    2009.05.05 at 15:06:03:562: Thread-15: B2B - (DEBUG) MimePackaging:applySecurity:Enter
    2009.05.05 at 15:06:03:562: Thread-15: B2B - (DEBUG) MimePackaging:applySecurity:Exit
    2009.05.05 at 15:06:03:563: Thread-15: B2B - (DEBUG) MimePackaging:createMimeBodyPart:Exit
    2009.05.05 at 15:06:03:690: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setDigestAlgorithm using algorithm name Entering...
    2009.05.05 at 15:06:03:691: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setDigestAlgorithm using algorithm name Leaving...
    2009.05.05 at 15:06:03:785: Thread-15: B2B - (DEBUG) MimePackaging:applySecurity:Enter
    2009.05.05 at 15:06:03:786: Thread-15: B2B - (DEBUG) MimePackaging:createSignedMimeBodyPart:Enter
    2009.05.05 at 15:06:03:787: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setProtocolVersion Entering...
    2009.05.05 at 15:06:03:788: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setProtocolVersion Leaving...
    2009.05.05 at 15:06:03:788: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setSignatureAlgorithm using algorithm name Entering...
    2009.05.05 at 15:06:03:788: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setSignatureAlgorithm using algorithm name Leaving...
    2009.05.05 at 15:06:03:789: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setDigestAlgorithm using algorithm name Entering...
    2009.05.05 at 15:06:03:789: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setDigestAlgorithm using algorithm name Leaving...
    2009.05.05 at 15:06:03:789: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: sign Entering...
    2009.05.05 at 15:06:03:790: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: sign Sign using the configured certificate
    2009.05.05 at 15:06:03:790: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: sign wrl: /hub02/app/oracle/product/64bit/OAS101/Apache/Apache/conf/ssl.wlt/default
    2009.05.05 at 15:06:03:802: Thread-15: B2B - (DEBUG) Utility:getPrivateKey:Enter
    2009.05.05 at 15:06:04:928: Thread-15: B2B - (DEBUG) Utility:getPrivateKey:matching private key found
    2009.05.05 at 15:06:04:931: Thread-15: B2B - (DEBUG) Utility:getPrivateKey:Exit
    2009.05.05 at 15:06:04:964: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.Encoding:Encoding: setEncodingType Entering...
    2009.05.05 at 15:06:04:964: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.Encoding:Encoding: setEncodingType Leaving...
    2009.05.05 at 15:06:04:965: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.Encoding:Encoding: update Entering...
    2009.05.05 at 15:06:04:965: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.Encoding:Encoding: update Leaving...
    2009.05.05 at 15:06:04:965: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.Encoding:Encoding: encode Entering...
    2009.05.05 at 15:06:04:966: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.Encoding:Encoding: encode Leaving...
    2009.05.05 at 15:06:04:967: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: sign Leaving...
    2009.05.05 at 15:06:04:967: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: printErrorInfo Entering...
    2009.05.05 at 15:06:04:968: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: printErrorInfo Leaving...
    2009.05.05 at 15:06:04:982: Thread-15: B2B - (DEBUG) MimePackaging:createSignedMimeBodyPart:Exit
    2009.05.05 at 15:06:04:982: Thread-15: B2B - (DEBUG) MimePackaging:createEncryptedMimeBodyPart:Enter
    2009.05.05 at 15:06:04:985: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setProtocolVersion Entering...
    2009.05.05 at 15:06:04:985: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setProtocolVersion Leaving...
    2009.05.05 at 15:06:04:986: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setEncryptionAlgorithm using algorithm name Entering...
    2009.05.05 at 15:06:04:986: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setEncryptionAlgorithm using algorithm name Leaving...
    2009.05.05 at 15:06:04:987: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setEncryptionCertificate Entering...
    2009.05.05 at 15:06:04:988: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.Encoding:Encoding: setEncodingType Entering...
    2009.05.05 at 15:06:04:988: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.Encoding:Encoding: setEncodingType Leaving...
    2009.05.05 at 15:06:04:989: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.Encoding:Encoding: update Entering...
    2009.05.05 at 15:06:04:989: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.Encoding:Encoding: update Leaving...
    2009.05.05 at 15:06:04:989: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.Encoding:Encoding: decode Entering...
    2009.05.05 at 15:06:04:997: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.Encoding:Encoding: decode Entering...
    2009.05.05 at 15:06:04:997: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: setEncryptionCertificate Leaving...
    2009.05.05 at 15:06:04:997: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: encrypt Entering...
    2009.05.05 at 15:06:05:006: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.packaging.SmimeSecureMessaging:SmimeSecureMessaging: encrypt Leaving...
    2009.05.05 at 15:06:05:007: Thread-15: B2B - (DEBUG) MimePackaging:createEncryptedMimeBodyPart:Exit
    2009.05.05 at 15:06:05:007: Thread-15: B2B - (DEBUG) MimePackaging:applySecurity:Exit
    2009.05.05 at 15:06:05:008: Thread-15: B2B - (DEBUG) MimePackaging:createMimeMessage:Exit
    2009.05.05 at 15:06:05:013: Thread-15: B2B - (DEBUG) MimePackaging:getMimeContent:Enter
    2009.05.05 at 15:06:05:014: Thread-15: B2B - (DEBUG) MimePackaging:getMimeContent:Exit
    2009.05.05 at 15:06:05:014: Thread-15: B2B - (DEBUG) MimePackaging:pack:Exit
    2009.05.05 at 15:06:05:019: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequestPostColab Invoking Pre-Transmit
    2009.05.05 at 15:06:05:019: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:preTransmit Enter
    2009.05.05 at 15:06:05:020: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:preTransmit Log & Update Database Tables
    2009.05.05 at 15:06:05:020: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:preTransmit Update the Message Table Row with message state Wait for Incoming Acknowledgment
    2009.05.05 at 15:06:05:021: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:preTransmit Create a Native Event Table row for outgoing Request Message
    2009.05.05 at 15:06:05:021: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertNativeEvtTblRow(3 params) Enter
    2009.05.05 at 15:06:05:023: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:insertNativeEvtTblRow msgInfo.id = <1396700:0:221@096997515>
    2009.05.05 at 15:06:05:023: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:protocl id set A
    2009.05.05 at 15:06:05:024: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:
    ** DbAccess:insertNativeEvtTblRow protocolCollabId = null
    2009.05.05 at 15:06:05:357: Thread-15: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Runtime
    2009.05.05 at 15:06:05:357: Thread-15: BusinessLogicLayer - (DEBUG) Push Stack: createDataStorage
    2009.05.05 at 15:06:05:366: Thread-15: BusinessLogicLayer - (DEBUG) Pop Stack: createDataStorage
    2009.05.05 at 15:06:05:387: Thread-15: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Runtime
    2009.05.05 at 15:06:05:388: Thread-15: BusinessLogicLayer - (DEBUG) Push Stack: createWireMessage
    2009.05.05 at 15:06:05:408: Thread-15: BusinessLogicLayer - (DEBUG) Pop Stack: createWireMessage
    2009.05.05 at 15:06:05:408: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertNativeEvtTblRow(3 params) Exit
    2009.05.05 at 15:06:05:419: Thread-15: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Runtime
    2009.05.05 at 15:06:05:420: Thread-15: BusinessLogicLayer - (DEBUG) Push Stack: updateBusinessMessage
    2009.05.05 at 15:06:05:431: Thread-15: BusinessLogicLayer - (DEBUG) Pop Stack: updateBusinessMessage
    2009.05.05 at 15:06:05:432: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:preTransmit Create Event Table row for Message Retries
    2009.05.05 at 15:06:05:433: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:preTransmit timeToAck = Wed Dec 31 18:00:00 PST 1969
    2009.05.05 at 15:06:05:437: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertEvtTblRow Enter
    2009.05.05 at 15:06:05:463: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertEvtTblRow Event Type = 2
    2009.05.05 at 15:06:05:463: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertEvtTblRow EventId = 12
    2009.05.05 at 15:06:05:463: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertEvtTblRow Id = 1396700:0:221
    2009.05.05 at 15:06:05:468: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertEvtTblRow Exit
    2009.05.05 at 15:06:05:472: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:preTransmit Current TimeStamp isTue May 05 15:06:05 PDT 2009
    2009.05.05 at 15:06:05:473: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:preTransmit Retry shall happen at Tue May 05 17:06:05 PDT 2009
    2009.05.05 at 15:06:05:473: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:preTransmit business transaction info name null revision null
    2009.05.05 at 15:06:05:474: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:preTransmit Exit
    2009.05.05 at 15:06:05:474: Thread-15: B2B - (DEBUG) DBContext commit: Enter
    2009.05.05 at 15:06:05:482: Thread-15: B2B - (DEBUG) DBContext commit: Transaction.commit()
    2009.05.05 at 15:06:05:483: Thread-15: B2B - (DEBUG) DBContext commit: Leave
    2009.05.05 at 15:06:05:483: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequestPostColab Calling Send to transmit the message
    2009.05.05 at 15:06:05:484: Thread-15: B2B - (DEBUG) Protocol Name: HTTPS
    2009.05.05 at 15:06:05:484: Thread-15: B2B - (DEBUG) Version Name: 1.1
    2009.05.05 at 15:06:05:484: Thread-15: B2B - (DEBUG) Endpoint: https://tp.com:88/invoke/tp.receive/as2
    2009.05.05 at 15:06:05:485: Thread-15: B2B - (DEBUG) using SSL
    2009.05.05 at 15:06:05:486: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.TransportInterface:send URL: HTTPS://TP.COM:88/INVOKE/TP.RECEIVE/AS2
    2009.05.05 at 15:06:05:487: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.TransportInterface:send TO Endpoint: 502 https://tp.com:88/invoke/tp.receive/as2
    2009.05.05 at 15:06:05:487: Thread-15: B2B - (DEBUG)
    Protocol = HTTPS
    Version = 1.1
    Transport Header
    Content-Transfer-Encoding:binary
    Message-ID:<1396700:0:221@096997515>
    MIME-version:1.0
    Receipt-Delivery-Option:https://b2bserver.edu:55/b2b.IP_OUT_QUEUE
    From:096997515
    Disposition-Notification-To:[email protected]
    AS2-To:ZZ043073964T
    User-Agent:AS2 Server
    Date:Tue, 05 May 2009 22:06:01 GMT
    Disposition-Notification-Options:signed-receipt-protocol=required, pkcs7-signature; signed-receipt-micalg=required, sha1
    AS2-From:096997515
    AS2-Version:1.1
    Content-Type:application/pkcs7-mime; smime-type="enveloped-data"
    Connection:close
    Parameters
    -- listing properties --
    http.sender.timeout=0
    2009.05.05 at 15:06:05:847: Thread-15: B2B - (DEBUG) scheme null userName null realm null
    2009.05.05 at 15:06:07:519: Thread-15: B2B - (WARNING)
    Message Transmission Transport Exception
    Transport Error Code is OTA-HTTP-SEND-401
    StackTrace oracle.tip.transport.TransportException: [IPT_HttpSendError] HTTP encounters send error :401
    at oracle.tip.transport.TransportException.create(TransportException.java:91)
    at oracle.tip.transport.basic.HTTPSender.createTransportResponse(HTTPSender.java:748)
    at oracle.tip.transport.basic.HTTPSender.send(HTTPSender.java:560)
    at oracle.tip.transport.b2b.B2BTransport.send(B2BTransport.java:284)
    at oracle.tip.adapter.b2b.transport.TransportInterface.send(TransportInterface.java:837)
    at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1666)
    at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:900)
    at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1082)
    at oracle.tip.adapter.b2b.transport.AppInterfaceListener.onMessage(AppInterfaceListener.java:126)
    at oracle.tip.transport.basic.aq.AQDequeuer.dequeue(AQDequeuer.java:331)
    at oracle.tip.transport.basic.aq.AQDequeuer.run(AQDequeuer.java:206)
    2009.05.05 at 15:06:07:520: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.TransportInterface:send Error in sending message
    2009.05.05 at 15:06:07:520: Thread-15: B2B - (INFORMATION) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequestPostColab Request Message Transmission failed
    2009.05.05 at 15:06:07:521: Thread-15: B2B - (DEBUG) DBContext beginTransaction: Enter
    2009.05.05 at 15:06:07:521: Thread-15: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
    2009.05.05 at 15:06:07:522: Thread-15: B2B - (DEBUG) DBContext beginTransaction: Leave
    2009.05.05 at 15:06:07:523: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequestPostColab [IPT_HttpSendError] HTTP encounters send error :401
    [IPT_HttpSendError] HTTP encounters send error :401
    2009.05.05 at 15:06:07:532: Thread-15: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Runtime
    2009.05.05 at 15:06:07:533: Thread-15: BusinessLogicLayer - (DEBUG) Push Stack: updateBusinessMessage
    2009.05.05 at 15:06:07:540: Thread-15: BusinessLogicLayer - (DEBUG) Pop Stack: updateBusinessMessage
    2009.05.05 at 15:06:07:540: Thread-15: B2B - (DEBUG) DBContext commit: Enter
    2009.05.05 at 15:06:07:543: Thread-15: B2B - (DEBUG) DBContext commit: Transaction.commit()
    2009.05.05 at 15:06:07:544: Thread-15: B2B - (DEBUG) DBContext commit: Leave
    2009.05.05 at 15:06:07:544: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequest Exit
    2009.05.05 at 15:06:07:545: Thread-15: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage:
    ***** REQUEST MESSAGE *****
    Exchange Protocol: AS2 Version 1.1
    Transport Protocol: HTTPS
    Unique Message ID: <1396700:0:221@096997515>
    Trading Partner: ZZ043073964T
    Message Signed: RSA
    Payload encrypted: 3DES
    Attachment: None
    ***** REQUEST MESSAGE *****
    2009.05.05 at 15:06:07:546: Thread-15: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage Exit
    2009.05.05 at 15:06:07:546: Thread-15: B2B - (DEBUG) DBContext commit: Enter
    2009.05.05 at 15:06:07:546: Thread-15: B2B - (DEBUG) DBContext commit: Leave
    2009.05.05 at 15:06:07:548: Thread-15: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.AppInterfaceListener:onMessage processOutgoingMessage was successful, returning transport ACK to the transport layer
    Thankyou,
    Lavar

    When I telnet to the host, I get (Connection to tp.com closed by foreign host.
    I went to the TP URL and save the certificate as Base 64. I then loaded that into my wallet as a Trusted Certificate.
    I see TP.com in the wallet as a Trusted Certificate with an expiration date of July 28, 2010 and Key Size 2048.
    We still get the same 401 error message. The TP is saying that we are not receiving a certificate on their end. I guess that means there is a problem with encoding and encryption.
    I loaded the TP Verisign certificate into my browser as a CA Root.
    Now I get a pop up box, when I go to the website that wants me to choose a digital certificate.
    There are not any digital certificates to choose from, so I can only click OK or Cancel.
    After clicking OK or Cancel, I get prompted for a password.
    There seems to be trust isses between our server and the TP's server. :)
    I asked the trading partner to send me their Root certificate, in case they have a different Verisign certificate.
    Thank you,
    Lavar

  • Passing XML String via HTTP Sender

    Hello everyone,
    currently we try to find a solution on the following requirement - maybe you have useful advice for us:
    8 different business documents can be sent via a web-interface to SAP XI via the http sender adapter. We already have a customized JCo Class that takes only one input parameter (containining the XML string of the business document).
    I think the easiest way would be to receive the XML string from the web-interface and pass it directly on to the JCo-Class in a Java Mapping.
    Is it possible to create a generic message type for all 8 types of XML documents that contains just one element holding the XML as string? By doing so we could use the same URL for all 8 different XML types and pass it directly on as input paramenter to the JCo Class.
    Do you have any idea how to do this?
    Thank you very much.

    Does the HttpURLConnection conn send the string along with the headerYes.

  • How to configure the Http sender adapter

    Now i have look through the sap lib about the http sender adapter
    and i know the url is
    http://hostname:port/path?namespace=<...>
    &interface=<...>&service=<...>&cmd=T&loaderXML=< message object >&end=yes
    My questions are:
    1)the path in the URL is "/sap/xi/adapter_plain", if not, what is it?
    2)the message payload is right?
    any reply is appreciated
    Thank you very much

    Hi Leo,
    For a HHTP Scenario:
    DESIGN:
    1. Create DataTypes for source and Destinations. Create elements for all the text fields of your HTTP Client so that they can all be mapped into the destination file
    2. Create MessageTypes for the two datatypes.
    3. Create Message Interfaces. The One for HTTP is the sender, Asynchronous ( as no response is expected) and one for File is receiver, asynchronous.
    4. Do the mapping. It will be mostly a one to one mapping of the fields.
    5. Create the Interface Mapping.
    Configuration:
    1. Import your Business System under your Configuration Scenario.
    2. Create 2 communication channels. One for Http as a sender and one for your receiver say IDoc.
    Check these links for the configuration part.
    http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/44/79973cc73af456e10000000a114084/content.htm
    3. Do the Receiver Agreement for Idoc. HTTP doesn’t need a sender agreement.
    4. DO the Receiver Determination and Interface Determination.
    Weblog which talk about the same scenario:-
    /people/sriram.vasudevan3/blog/2005/01/11/demonstrating-use-of-synchronous-asynchronous-bridge-to-integrate-synchronous-and-asynchronous-systems-using-ccbpm-in-sap-xi - although this weblog is
    aimed at explaining the sync-async bridge.. Sriram has taken http-to-file scenario as the example
    (use case) and explained it...
    Check this SDN tv demo, it has detail of HTTP adapter setup.
    https://media.sdn.sap.com/SDNTV/main.asp?mediaId=107
    Refer to this link for adapter settings.
    http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm
    You should also have a HTTP client to send message to XI. In the connecting parameters to XI u have to use the URL in the pattern mentioned . U have to give all the configuration details in the URL.
    If you give me your mail id or if you can mail me at [email protected], i can send you a HTTP CLIENT.....In which you need to view the source code and change the username and password to send message to XI.
    Regards,
    Abhy

  • How to use the http sender adapter

    Hi,
    I'm trying to use the http sender adapter but not getting the result.
    1)  I've created the commnunication channel in Integration Directory.
    2)  I have my url:
    http://<server>:56000/sap/xi/adapter_plain?service=BS&namespace=urn%3Acompany%3Apoc&interface=interface
    3)  When i copy that url in a browser i get a login prompt. When i log in i get a message that navigation is cancelled.
    What steps do i need to do to use this url to send my xml message to the adapter engine. Do i need a special system user for this? Any other tools required? (i have httpclient but using that doesnt send messages to the adapter_plain; i think)
    I feel i'm just missing one little thing, but what is it.
    kr
    Robert

    Hello Team,
    I added the user name & pwd to query string & trying to access from IE and still getting blank page.
    Is this what is expected or there is something wrong in URL. I am able to send the XML from HTTP Test tool.
    My URL is :
    http://abc:50000/sap/xi/adapter_plain?namespace=urn:xyz.com:A_To_ERP_Payment_balance_Request&interface=SI_A_CHK_balance_OUT&service=BC_XX_XXX&sap-user=myuser&sap-password=mypassword&sap-client=001&sap-language=EN
    Please advice.

  • HTTP Sender and HTTP Receiver adapter. Pls advice urgent

    Hi All,
    There is one Third Party that wants to send XML data and receive XML data with XI.
    Please let me know can I use HTTP for that.
    How to use HTTP Sender part?
    How to use HTTP Receiver Adapter?
    Pls send blogs/doc for that
    Thanks and Regards

    hi.,
    Check this thread for the code for a HTTP Client,
    /message/266750#266750 [original link is broken]
    Also, check these blogs. They use HTTP adapters for their configuration,
    /people/siva.maranani/blog/2005/05/21/jdbc-stored-procedures
    /people/sriram.vasudevan3/blog/2005/02/14/calling-stored-procs-in-maxdb-using-sap-xi
    http://help.sap.com/saphelp_nw04/helpdata/en/44/79973cc73af456e10000000a114084/content.htm
    Check these links for the configuration part.
    http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/44/79973cc73af456e10000000a114084/content.htm
    Weblog :
    /people/sriram.vasudevan3/blog/2005/01/11/demonstrating-use-of-synchronous-asynchronous-bridge-to-integrate-synchronous-and-asynchronous-systems-using-ccbpm-in-sap-xi - although this weblog is
    aimed at explaining the sync-async bridge.. Sriram has taken http-to-file scenario as the example
    note:reward points if solution found helpfull.....
    regards
    chandrakanth.k

  • URL in HTTP sender adapter

    Hi,
    I have a scenario where I want to configure a HTTP sender adapter.
    I have a HTTP PUT url of a 3rd party application from where the HTTP adapter should poll and pull the files into PI.
    Is this possible? If yes, where and how do I mentioon the URL?
    Please help!
    Thanks,
    Pratibha.

    Hi,
    That means, the sender aplication has to write a http://<hostname:port>/<path>?<query-string> type query?
    Is there no other option?
    Is it not possible with the SOAP sender adapter also?
    Thanks,
    Pratibha.

  • How to Send Idoc Acknowledgements back to Http sender (Http to Idoc)

    Hi
    I have scenario: Http To Idoc
    first requirment:
    i need to map xml file come from HTTP Sender to Idoc (SAP system), and need to send Idoc acknowledgements/status back to Http sender.
    second requirment:
    while mapping COM Xml file come from Http to COMMAT04 idoc into SAP system i need to to check whether corresponding material already exist in R/3 or not, if material is not exist, process should be cancelled and alert should be raised. ( i mean to say before sending COMMAT04 idoc into SAP, corresponding material should be exist already, if not alert should be send to  http sender)
    please thrown some inputs, if sombody has already done with htis....
    Thanks in Advance, and help would be appreciated..
    Thanks and Regards
    Rajesh Babu

    Just providing the specifics that Suhail has intended.
    How to handle IDOC Acknowledgements in XI.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
    RFC Mapping Lookups:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a03e7b02-eea4-2910-089f-8214c6d1b439
    Regards,
    Ravi
    Edited by: Ravi Kanth Talagana on Jul 7, 2008 3:32 PM

  • [HTTP Sender]How to send different XML using static URL

    Hi all,
    I have a problem, my legacy system send XML messages to SAP XI by HTTP, I know that I need to use HTTP Sender adapter, the problem is that legacy system support only a static URL. I have more than one interface, how could I fix this problem?
    Can I send the XML message to SAP XI without define INTERFACE on URL? How can I handle this?
    Thank in advance,
    Daniel Torres

    Hi Srinivas,
    The legacy system is a java application, that send XML messages to SAP XI server using HTTP protocol. So I just ask to legacy system team to change the application to add <b>server</b>, <b>namespace</b> and <b>interface</b> attributes to the URL querystring.
    So for each XML message you should especify mesage interface that it belongs to. You do it by especifying on URL as message atribute for exemple:
    HTTP://[SAPXISERVER]:80[SYSTEM ID]/sap/xi/adapter_plain?service=[BS SERVICE]&namespace=[MESSAGE INTERFACE NAMESPACE]&interface=[MESSAGE INTERFACE]
    So if you have for example information belows:
    <b>MESSAGE INTERFACE</b> = MI_MYMESSAGEINTERFACE_IB
    <b>MESSAGE INTERFACE NAMESPACE</b> = urn:teste:mymessageinterface
    <b>SERVICE</b> = MY_LEGACY
    <b>SYSTEM ID</b> = 10
    <b>SAPXISERVER</b> = MYSAPXI
    Your url should looks like: http://MYSAPXI:8010/sap/xi/apadter_plain?service=MY_LEGACY&namespace=urn:teste:mymessageinterface &interface=MI_MYMESSAGEINTERFACE_IB
    You should have a different message interface for each XML that you send to SAP XI.
    Message was edited by:
            Daniel Torres
    Message was edited by:
            Daniel Torres

  • HTTP Sender - how to read URL Parameter USER id into Mapping

    Hi,
    My scenario is HTTP - XI - ABAP Proxy.
    I wanted to capture USER id of the person who posted(HTTP) into XI(Mapping). How to read/evaluate the value of sap-user from querystring of URL ?
    http://HOST:8008/sap/xi/adapter_plain?namespace=http%3A//abc.com/sales_oa&interface=MI_sales_OA&service=DEV_D&party=&agency=&scheme=&QOS=EO&<b>sap-user=SM9999</b>&sap-password=xxxxx&sap-client=001&sap-language=EN
    please help.

    Mallik,
    Try  URL Parameters in HTTP sender communication channel.
    In the sender communication channel set Adapter Specific Message Attributes. Click on Apply URL Parameters. In Parameter1 put sap-user (U can query any URL parameter by giving its name as in the HTTP URL).
    Now in SXMB_MONI, in inbound payload SOAP Header, under Dynamic configuration u can see the value of the user. Query the same in Mapping using Dynamic Configuration using keyName as UrlParamOne.
    Regards,
    Sudharshan N A
    Message was edited by:
            Sudharshan Aravamudan

  • How to Configure HTTPs sender communication in XI

    Hi,
    I have a request for new interface setup, in which i need to configure HTTPs sender communication from a B2B server to SAP system. Scenario is to receive XML 0rders from HTTPs B2B system and convert to Idoc and post it to SAP.
    Please could some one help on what needs to be done in XI for receiving XML order files from a HTTPs connection and what further needs to be done for processing to Idoc.
    Thanks in advance,

    HI,
    For testing purpose you can use the HTTP client and paste your payload.
    Refer the below pdf for HTTP client what you do is copy and paste the code in note pade and save as .html file.
    This link gives you a sample HTML code to create HTTP Client:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/66dadc6e-0a01-0010-9ea9-bb6d8ca48cc8
    Thnx
    Chirag Gohil

  • HTTP sender adapter and receiver adapter

    Hi guys,
    I have a scenario that I have to communicate with an HTTP server with XML over HTTP.
    When the communication is opened by me I will use an HTTP receiver adapter and give the connection parameters.
    a) Do I have to use a different HTTP receiver communication channel for each different type of XML that I want to send??
    b) When the communication is opened from the HTTP server, they have to type the URL in order to invoke the correct scenario on my side, right? I know that I do not have to use an HTTP sender adapter. They have to call the http URL, followed by the sender business system, sender interface name/namespace etc.
    That means that the URL in the format: http://XIhostname:port/ is not enough right?
    Is there a way to figure out from the type of the XML sent which scenario will be executed in XI?
    Because it is difficult for them to use different URL when they are sending me different type of XML's, i.e. different requests.
    Evaggelos

    >>Do I have to use a different HTTP receiver communication channel for each different type of XML that I want to send??
    Yes,receiver adapter is linked to receiver agreement,if you have different inbound interfaces then it means you need to have diferrent receiver agreement,hence different receiver communication channels.
    >>That means that the URL in the format: http://XIhostname:port/ is not enough right?
    No,its not,there is a test tool on SDN called "HTTP test tool".just search for that and download on your desktop,it will help you generate the correct URL as well as test the scenario by sending sample HTTP request.
    One thing you need to keep in mind is that HTTP scenarios don't require and sender communication channel or sender agreement.they only need configurations on receiver side
    Thanx
    Aamir
    FYI:Here is the test tool
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/66dadc6e-0a01-0010-9ea9-bb6d8ca48cc8
    Edited by: Aamir Suhail on Jul 3, 2008 12:18 PM

  • Http sender adapter: QoS is interpreted as Best Effort by PI 7.11

    Hi
    I have a scenario, where I receive an xml OrderResponse via an http sender adapter and I then map it to an iDoc which is sent to the backend system.
    BUT: for some reason, PI thinks, that the Quality of Service is BE, and I get the error "Only asynchronous processing supported for IDoc adapter outbound processg".
    I have checked both the http sender adapter, the sender agreement, the interface mapping, the service interface and the operation mapping and nowhere can I see, that best effort is selected.
    The OrderResponse is sent from an external partner and is routed through a load balancer and an SAP web dispatcher before arriving to PI.
    Any suggestions would be highly appreciated.
    MIkael Lund

    The external partner is sending the OrderResponse to this URL (external URL):
    https://xxxxxx.xxxxxxxx.dk/sap/xi/adapter_plain?service=LM&namespace=http://xxxxxxxx.dk/XCBL/OrderResponse&interface=xCBLOrderResponse35Out
    this URL is being translated to an internal URL:
    https://yyyyyyy.yyyyyyy.dk/sap/xi/adapter_plain?service=LM&namespace=http://xxxxxxxx.dk/XCBL/OrderResponse&interface=xCBLOrderResponse35Out
    So how should the external and/or internal URL be altered?
    Thanks for a very quick answer by the way
    MIkael

Maybe you are looking for