401 Error Proxy to SOAP

Hi,
We have sync interface for Proxy to SOAP. This interface works fine when run once.
When we did volume testing, 10% of the messages ( randomly) failed  with 401 Unauthorized & 503 Service not aviabale.
After researching we found a note 821026 which talks about the issue. We have done changes as per the note & inclease the connection Pool max to 100.
Please advice, if there is anything we can do as it is still failing with 401 & 503 in PI.
Regards

Hi All,
Thanks for reply. We have 3 PI Systems which calls the same Web service via SOAP (  Syn proxy-SOAP.
First we observed this error in one of the system & now it comes in all. The error is
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.SocketTimeoutException: Read timed out
The sequence of event is  Inbound message from ECC looks good, the Mapping is OK. I see in response  the red & the error is in Inbound of Response.
Below is the log in MDT
02.02.2012 18:12:03 Information The message was successfully received by the messaging system. Protocol: XI URL: http://xxxxpd312.r1-core.r1.xxx.net:50000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
02.02.2012 18:12:03 Information Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the request queue.
02.02.2012 18:12:03 Information Message successfully put into the queue.
02.02.2012 18:12:03 Information The message was successfully retrieved from the request queue.
02.02.2012 18:12:03 Information The message status was set to DLNG.
02.02.2012 18:12:03 Information Delivering to channel: CC_SOAP_Rcvr_PaymentVerification
02.02.2012 18:12:03 Information MP: entering1
02.02.2012 18:12:03 Information MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
02.02.2012 18:12:03 Information SOAP: request message entering the adapter with user J2EE_GUEST
02.02.2012 18:12:18 Error SOAP: call failed: java.net.SocketTimeoutException: Read timed out
SOAP: error occured: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.SocketTimeoutException: Read timed out
02.02.2012 18:12:18 Error MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.SocketTimeoutException: Read timed out
02.02.2012 18:12:18 Error Adapter Framework caught exception: java.net.SocketTimeoutException: Read timed out
02.02.2012 18:12:18 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.SocketTimeoutException: Read timed out. Setting message to status failed.
SXMB Log from ECC . This is shown
<!--  Inbound Message
  -->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
  <SAP:Category>XIAdapterFramework</SAP:Category>
  <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
  <SAP:P1 />
  <SAP:P2 />
  <SAP:P3 />
  <SAP:P4 />
  <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.SocketTimeoutException: Read timed out</SAP:AdditionalText>
  <SAP:ApplicationFaultMessage namespace="" />
  <SAP:Stack />
  <SAP:Retry>M</SAP:Retry>
  </SAP:Error>
I am not sure if this is issue in calling adapter engine( while sedning to web service) or When the Data is being send to Proxy this issue comes in.
Ps: We have gone through many notes  & increase the connection pool & max wait time.
Also we have increase the time out in SOAP adapter with no effect. BASIS is looking at SXMB_ADM Http paramterto increase but this was systems were working fine before that.
Now even one message is not flowing.
Thanks & please advice
I

Similar Messages

  • HTTP 401 Unauthorized, error in proxy to SOAP Scenario

    Hi all,
    We got the below error in our proxy to SOAP Scenario.
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized
    We configured User Authentication,Proxy and Proxy User Authentication for the Receiver Communication Channel correctly still we are getting this error.
    So please let me know what could be the possible reasons behind it and how to resolve it.
    Waiting for your valuable response.

    Hi,
    Consider the parameters connection pool size and connection wait time:
    ume.r3.connection.master.poolmaxsize
    ume.r3.connection.master.poolmaxwait
    These parameters are described in the note below:
    #821026 - AdapterEngine messaging URL returns HTTP 401 under high load
    Also, ensure you have maintained the correct password, which MUST be the same, for all the service users
    on XI. You may check all the places it should be maintained, such as Exchange Profile, SU01, SLDAPICUST, etc..
    Please kindly check the note below:
    PI 7.1:
    #999962 - PI 7.10: Change passwords of PI service users
    XI 7.0
    #936093 - XI 7.0: Changing the passwords of XI service users
    XI 3.0
    #721548 - XI 3.0: Changing the passwords of the XI service users
    And ensure that the user has the correct role as per link below:
    http://help.sap.com/saphelp_nwpi71/helpdata/en/9f/d12940cbf2195de10000000a1550b0/frameset.htm
    Regards,
    Caio Cagnani

  • Error while invoking the ABAP Proxy via SOAP Adapter

    Hi,
    My scenario involves SOAP Client invoking a webservice hosted in PI which in turn invokes the ABAP Proxy asyncronously.
    SOAP Client -> PI -> ECC (ABAP Proxy) . This works fine.
    Next , I have exposed the ECC Service Interface as webservice using SOA Manager transaction. Now, once the service is created using SOAManager, i replaced the XI Adapter with SOAP Adapter and provided the target URL as the URL provided by the SOAManager.
    SOAP Client -> PI -> ECC (ABAP Proxy via SOAP Adapter)
    With this approach, i am encountering the below error message
    2009-05-29 12:17:55 Error Adapter Framework caught exception: null
    2009-05-29 12:17:55 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.
    Any ideas on the above errror message? Any pointers or inputs will be appreciated.
    Thanks,
    Vinayak Kamath

    > 2009-05-29 12:17:55 Error Adapter Framework caught exception: null
    > 2009-05-29 12:17:55 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.
    This is a generic error message which does not have any information about the error which has occurred.
    Do you see any error messages in the SOAP client?
    Regards
    Stefan

  • Error in SOAP receiver channel in Synchronous Proxy to SOAP scenario

    Hi all,
    We are experiencing an issue with a synchronous Proxy to SOAP scenario. Getting below error message in the SOAP receiver communication channel for the response message.
    SOAP: Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
    Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error encountered while executing mapping: com.sap.aii.af.service.mapping.MappingException: com.sap.aii.utilxi.misc.api.ResourceException: Could not determine mapping steps for message 1364b76e-ecbf-11e4-85f4-000023acfde6.
    We are running PI 7.4.
    Any help is appreciated.
    Thanks,
    Pushpa

    Hi,
    Seems the Receiver Webservice is not reachable. Did you try to test it using SOAP UI tool.
    1. Test a fresh message from local SOAP UI tool.
    2. Pick 3rd party WSDL file and Import in SOAP UI tool.
    3. Put some dummy data for mandatory fields
    4. Trigger it msg and ckh if you get successful / response msg.
    5. Check if firewall is open and that URL is not blocked.
    Hope it helps
    Regards,
    Azhar

  • PROXY to SOAP ; HTTP403 error in PI 7.1

    Hi team,
    it was proxy to HTTP scenario. Receiver : webportal . We have chnged it to Proxy to SOAP ,due to HTTP does not support multi message generation . I have checked Do NOT USE SOAP Envelope in SOAP rcv channel. Pls find the config details.
    Adapter Type: SOAP
    Trans.protocal: HTTP
    Mess.Protocal: SOAP1.1
    Do not use SOAP envelope : Checked
    Now Im getting error in RWB .
    "Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 403 Access denied"
    I checked with the basis people- they confirmed - some request hitting the site. but unable to read the content . they specified HTTP header should contain the content type : text/xml . If I checked "Do not use SOAP envelope " , I guess the content type is application/xml etc.
    so how can I change the HTTP content type to text/xml. OR any other reason tfor this error.
    thnaks
    Drumi.

    Hello,
    I checked with the basis people- they confirmed - some request hitting the site. but unable to read the content . they specified HTTP header should contain the content type : text/xml . If I checked "Do not use SOAP envelope " , I guess the content type is application/xml etc.
    so how can I change the HTTP content type to text/xml. OR any other reason tfor this error.
    The content type when Do Not Use SOAP Envelope is checked defaults to application/xml. To change it to the correct content type, use the MessageTransformBean for your requirement.
    ProcessingSequence                         ModuleName           Type     ModuleKey
    1          localejbs/AF_Modules/MessageTransformBean            LEB      0
    2          sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean LEB      soap
    Module Configuration
    ModuleKey                ParameterName                ParameterValue
    0                      Transform.ContentType          text/xml
    For more info, see http://help.sap.com/saphelp_nwpi711/helpdata/en/57/0b2c4142aef623e10000000a155106/frameset.htm
    Check also if you are passing credentials in your Receiver.
    Hope this helps
    Mark

  • ABAP-Proxy to SOAP: Error in SOAP Adapter

    Hi!
    I would like to implement ABAP-Proxy to SOAP scenario.
    Unfortunately my SOAP receiver channnel has the following error:
    SOAP: call failed: java.io.IOException: No SOAP Envelope but 1 definitions; HTTP 200 OK
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: No SOAP Envelope but 1 definitions; HTTP 200 OK: java.io.IOException: No SOAP Envelope but 1 definitions; HTTP 200 OK
    Furthermore the call of  /sap/bc/soap/rfc of business system B is erroneous
    http://<server system B>:8000/sap/bc/soap/rfc
    Here I get the error: HTTP 500 Internal Server error
    Can some one help me to solve this problem?
    Thank you very much!
    regards
    Holger

    Hi,
    Are you using the webservice exposed by SAP or it is third party webservice. Can you explain your complete scenario? What is the url you have given in your receiver SOAP Channel? Was that no configured earlier?
    If at all you are using the SAP webservice, the wsdl link should be.
    http://<server>:<http port>/sap/bc/soap/wsdl11?services=BAPI_MATERIAL_EXISTENCECHECK&sap-client=200
    The target url you will be able to see in the wsdl itself also
    amit

  • Error "soap fault: No operation available for request" in proxy to soap Scenario

    Hi Experts,
    Unable to trace the below error when pushing the message from RWB while testing the PROXY to SOAP interface
      Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: No operation available for request {http://schemas.xmlsoap.org/soap/envelope/}Envelope.
    Thank you very much if any one provided the solution
    Regards,
    Yugandhar 

    Hi Yugandhar,
    Check the below thread,
    Connecting from SAP PI To Salesforce
    Regards
    RK N.

  • Error in Proxy to SOAP synchronous scenario

    Hi Gurus,
    Hope you are doing well. I have a Proxy to SOAP synchronous interface interacting with an external system (system outside the firewall/landscape of my company).
    When I am trying to post the request message from XI, I am getting the following error.
    MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: The server was unable to process the request due to an internal error.  For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs
    In the WSDL provided by the external application, i.e. receiver WSDL, there is no attribute/field with the name 'IncludeExceptionDetailInFaults' and there is no fault string defined.
    Where is this error being thrown up? Is it a network/firewall error that XI is unable to determine?
    Please provide an answer as soon as possible.
    regards
    Debansu

    Hi,
    i think it is the problem in the WSDL provider system, because it is throwing the Error with some string".NET",
    do the below steps for investigating the issue
    1)try pinging the URL provided in the WSDL from internet explorer.
    2)if it is successfull, try to push one message from SOAP UI to by importing that WSDL, if you get any error then it is problem in the end system.
    Thank You,
    Madhav

  • Error in synchronous( abap proxy to soap)scenario

    Hi experts,
    My scenario is synchronous abap proxy to sysnchronous soap. for proxy I am using business system name as ERDCLNT220 and soap business system name as BS_HRS_DEV
    configuration steps are
    1. only client proxy to soap scenario I have done.
    communication channels: only receiver soap adapter. no proxy sender communication channel for client proxy.
    Already we have RFC destination connection and connection type H for proxy to xi.
    1.Is it required RFC destination connection for xi to server proxy.
    2.Is it required receiver proxy communication channel for server proxy?.
    i HAVE TESTED THIS INTERFACE. I am able to send the request. But I am not able to receive the response from soap webservice message .
    error is:
    SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson
    exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson
    Error Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson
    Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson. Setting message to status failed.
    Kindly help me.
    advance thanks
    thanks and regards
    elton
    Edited by: eltonsaranya on May 9, 2011 10:27 AM

    Your exception message shows problem at the webservice side.
    Check the following:
    a) you need two mappings one for proxy req to soap request and other soap response to proxy response
    b) You need to create service interfaces both sender and receiver synchronous .
    c) communication channel  QOS is best effort for both sender and receiver
    d) I dont see problem in soap configuration. Bcuz you are able to ping and while getting response from the method getPerson it fails.
    f) See your SOAP response structure matches with WSDL provided.
    g) You can also test outside PI.. I meant testing via soap client tool like SOAPUI  for that web service. So that you know whether problem exists on the target system or not.
    Hope that helps.

  • ABAP Client Proxy error code: 401, error text: Unauthorized

    Hi,
    I have Client proxy in ECC for oubound interface in PI 7.0, when i look into SXMB_MONI of ECC i can see my message with Error "HTTP response contains status code 401 with the description Unauthorized Authorization error while sending by HTTP (error code: 401, error text: Unauthorized)".
    As per few thread i already assign SAP_XI_APPL_SERV_USER role to PIAPPLUSER in ECC, still i am getting same eror.
    I do not understand how this Proxy communication work, which ECC user will be use in communication and how this communcation link to RFC destination "SAP_PROXY_ESR" type G. Even i can not see type H in ECC so i created RFC destination of type G.
    With Regards
    Sunil

    We were able to get it working by making a change in the Integration Engine Configuration (in sxmb_adm).
    Changed "Corresponding Integ. Server" from "http://<server>:<port>/sap/xi/engine?type=entry"
    to "dest://RFCdestinationName"

  • ABAP client proxy   401 error

    Hi i have generated a ABAP client proxy in my ECC system and sending an outbound message to XI.  i get the following error.
    HTTP response contains status code 401 with the description Unauthorized Error while sending by HTTP (error code: 401, error text: Unauthorized)
    I have tested the following.
    1) My sld and ECC system have the integration engine and pipeline  settings for the XI Server: http://server:8000/sap/xi/engine?type=entry
    2) logon to the URL http://server:8000/sap/xi/engine  with user XIAPPLUSER and pwd in the browser because of the error 'Der Aufruf der URL http://server:8000/sap/xi/engine wurde aufgrund fehlerhafter Anmeldedaten abgebrochen'
    any sugestions ?  using a proxy as target works fine

    Hi ,
    You seem to have a problem with the XIAPPLUSER logon. Can you check that the user has the appropriate authorizations? Maybe the user is locked? Maybe the password has been incorrectly entered?
    XIAPPLUSER should have the role SAP_XI_APPL_SERV_USER.
    Also, check that the XI engine service has been activated.
    Transaction SICF. Default_host->sap->xi Activate the entire node with all subtrees.
    Cheers
    Manish

  • Error while testing SOAP scenario

    I have done SOAP(Sender)--SAP-PI- SOAP(RECEIVER) Scenario. It is in synchorous mode..
    It works fine in Altove XML Spy.. and getting the response fron webservice..
    but when i;m testing it PI (RWB->Comp Monit>Integration engine-->Test Messge ) it gives me error
    " Error While Testing: Method Not implemented "
    Can anyone please help me on this.. What acould be the reason.. for this..
    Regards,
    deep

    Sunil, Thanks For your Reply...
    Payload is correct.. and mapping is also fine. I'm getting reponse from Webservices using XML SPY..
    But i have seen one warning about Integation Engine : Is Websecurity Available : Communication error Proxy calls are not permitted on sender or receiver side on the IS (client)  in Component monitoring..
    Does this warning cause this error  anyway.. ?  Because i'm getting error even in XML SPY when i defined business system as Sender and Receiver as Business Service. But if i define both are as Business Serivces.. it works fine.. (in XML SPY)
    But in both cases i'm failing in RWB(INtegration engine-:>Test message)
    Is there any relation to above mentioned warning " Is Websecurity Available : Communication error Proxy calls are not permitted on sender or receiver side on the IS (client)  in Component monitoring.. "
    Regards,
    Deep

  • HTTP 401 error while connecting SAP PI 7.1 with SOAPAdapter

    Hello,
    I am trying to call webservice on R/3 system using SAP PI 7.1 but I am getting HTTP 401 error.
    Following is the error for more detail:
    Message: Server returned error code = 401 for URI : http://sapxx03x:50000/XISOAPAdapter/MessageServlet?channel=:BS_xxxxxxxxxxx_50:CC_xxxxxxxxxxxxx_WSDL_Sender.
    same url when I use with SAP XI 3.0 it works fine. It is only giving problem with PI 7.1
    I know this issue is related to authentication but what problem I am facing is how to pass the credentical with the url to
    resolve this authentication issue? Are there any settings I am missing? or Any other way of doing it?
    I have already tried following things to resolve this issue:
    1. tried giving user id & password in URL but still having same error HTTP 401.
    2. tried one of the SAP note (891877) regarding Netweaver Administration to change ROLE settings but problme still persist.
    3. Checked SAP Help settings
    4. Did changes to web.xml file to comment the security part and restarted the system
    But, Problem still exist.
    Please let me know what will be the solution for this issue.
    Thanks,
    Anand

    Hello Abhishek,
    Fine I will try using new URL but user id  & password are working fine with PI 7.1.
    I tried running URL directly and it is working fine and giving following message:
    Message Servlet is in Status OK
    Status information:
    Servlet com.sap.aii.adapter.soap.web.MessageServlet (Version $Id: //tc/xpi.adapters/NWxx_xx_xxx/src/_soap_application_web_module/webm/api/com/sap/aii/adapter/soap/web/MessageServlet.java#1 $) bound to /MessageServlet
    Classname ModuleProcessor: null
    Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
    Lookupname for remoteModuleProcessorLookupName: null
    ModuleProcessorClass not instantiated
    ModuleProcessorLocal is Instance of $Proxy45_10002
    ModuleProcessorRemote not instantiated
    Any other pointers,
    Thanks,
    Anand

  • Abap proxy 2 soap

    Hi,
    this scenario is abap proxy 2 soap ,, , source system send some data to target webservice and target webservice return approval number.
    I checked target url and soap action in receiver soap adapter, and those value is correct.
    on sxmb_moni
    i got NO_MAPPINGPROGRAM_FOUND
    http://test.test.com/pt/ses001/approvalprocess SES001_IM does not exist in runtime cache</SAP:Stack>
    and Applicatoin Error
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>application fault</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    here is Sent message log on MDT.
    2006-08-29 13:25:37 Error SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
    2006-08-29 13:25:37 Success SOAP: response message leaving the adapter
    2006-08-29 13:25:37 Success Application attempting to send an XI message asynchronously using connection AFW.
    2006-08-29 13:25:37 Success Trying to put the message into the send queue.
    2006-08-29 13:25:37 Success The response message for message 44f23177-e6ed-0270-0000-000046028211(INBOUND) was successfully transmitted to the calling application.
    2006-08-29 13:25:37 Success The message status set to DLVD.
    2006-08-29 13:25:37 Success The application sent the message asynchronously using connection AFW. Returning to application.
    here is Receive message log on MDT.
    2006-08-29 13:25:37 Success The message was successfully received by the messaging system. Profile: XI URL: http://xi0034:50000/MessagingSystem/receive/AFW/XI
    2006-08-29 13:25:37 Success Using connection AFW. Trying to put the message into the request queue.
    2006-08-29 13:25:37 Success Message successfully put into the queue.
    2006-08-29 13:25:37 Success The message was successfully retrieved from the request queue.
    2006-08-29 13:25:37 Success The message status set to DLNG.
    2006-08-29 13:25:37 Success Delivering to channel: R_TEST_SOAP_SSS001
    2006-08-29 13:25:37 Success SOAP: request message entering the adapter
    2006-08-29 13:25:37 Success SOAP: completed the processing
    2006-08-29 13:25:37 Success SOAP: response message received 6bc3e4d0-3716-11db-a265-00145e483080
    2006-08-29 13:25:37 Error SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
    i can see source data on sxmb_moni.
    <?xml version="1.0" encoding="utf-8" ?>
    - <nr1:APPROVALREQ_SES_MT xmlns:nr1="http://test.test.com/pt/ses001/approvalprocess">
      <TITLE>46</TITLE>
      <GUBUN />
      <REQUESTOR>46</REQUESTOR>
      <TEXTLINE>SAFSAFSAFDSAF</TEXTLINE>
      </nr1:APPROVALREQ_SES_MT>
    request message mapping of request
      <?xml version="1.0" encoding="UTF-8" ?>
    - <ns1:ApprovalRequest xmlns:ns1="http://70.2.207.241:8080/axis/ApprovalService.jws">
      <args1>46</args1>
      <args2>46</args2>
      </ns1:ApprovalRequest>
    I can not see any return value comming from target webservice on sxmb_moni.
    request message mapping error on response
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>application fault</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    payload of request message mapping of response
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
      <ns2:hostname xmlns:ns2="http://xml.apache.org/axis/">ibmr52</ns2:hostname>
    please check what was my fault.
    thanks
    venjamin

    Hi Bhavesh.
    thanks for the note.,,
    please look at the bottom of this content.
    i can not see  "Method=Approval" between jws and args1 even though i set SOAP Action = Approval on Receiver SOAP Adapter.
    is this happening something wrong? or is it normal log?
    <?xml version="1.0" encoding="UTF-8"?>
    <ns1:ApprovalRequest xmlns:ns1="http://70.2.207.241:8080/axis/ApprovalService.jws"><args1>333</args1><args2>333</args2></ns1:ApprovalRequest>
    SAP_512dbe91-372d-11db-b291-00145e483080_END
    here is detail message log on MDT.
    --SAP_512dbe91-372d-11db-b291-00145e483080_END
    Content-ID: <[email protected]>
    Content-Disposition: attachment;filename="[email protected]"
    Content-Type: text/xml; charset=utf-8
    Content-Description: SOAP
    <SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header>
    <sap:Main xmlns:sap='http://sap.com/xi/XI/Message/30' versionMajor='3' versionMinor='0' SOAP:mustUnderstand='1' xmlns:wsu='http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' wsu:Id='wsuid-main-92ABE13F5C59AB7FE10000000A1551F7'>
    <sap:MessageClass>ApplicationMessage</sap:MessageClass>
    <sap:ProcessingMode>synchronous</sap:ProcessingMode>
    <sap:MessageId>44f23fa9-e6ed-0270-0000-000046028211</sap:MessageId>
    <sap:TimeSent>2006-08-29T07:10:08Z</sap:TimeSent><sap:Sender><sap:Party agency='' scheme=''></sap:Party>
    <sap:Service>BS_SAPR3_SSS0017</sap:Service></sap:Sender><sap:Receiver>
    <sap:Party agency='' scheme=''></sap:Party><sap:Service>BS_MMM_D</sap:Service></sap:Receiver>
    <sap:Interface namespace='http://sds.samsung.co.kr/pt/sessingle001/approvalprocess'>APPROVALREQ_MMM_IB</sap:Interface>
    </sap:Main><sap:ReliableMessaging xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'>
    <sap:QualityOfService>BestEffort</sap:QualityOfService></sap:ReliableMessaging>
    <sap:Diagnostic xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'>
    <sap:TraceLevel>Information</sap:TraceLevel><sap:Logging>Off</sap:Logging></sap:Diagnostic><sap:HopList xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'>
    <sap:Hop timeStamp='2006-08-29T07:10:08Z' wasRead='false'><sap:Engine type='BS'>BS_SAPR3_SSS0017</sap:Engine>
    <sap:Adapter namespace='http://sap.com/xi/XI/System'>XI</sap:Adapter><sap:MessageId>44f23fa9-e6ed-0270-0000-000046028211</sap:MessageId><sap:Info>3.0</sap:Info></sap:Hop>
    <sap:Hop timeStamp='2006-08-29T07:09:06Z' wasRead='false'>
    <sap:Engine type='IS'>is.00.xi0034</sap:Engine>
    <sap:Adapter namespace='http://sap.com/xi/XI/System'>XI</sap:Adapter>
    <sap:MessageId>44f23fa9-e6ed-0270-0000-000046028211</sap:MessageId><sap:Info>3.0</sap:Info></sap:Hop><sap:Hop timeStamp='2006-08-29T07:09:08Z' wasRead='false'>
    <sap:Engine type='AE'>af.sxd.xi0034</sap:Engine><sap:Adapter namespace='http://sap.com/xi/XI/System'>XIRA</sap:Adapter>
    <sap:MessageId>44f23fa9-e6ed-0270-0000-000046028211</sap:MessageId></sap:Hop></sap:HopList></SOAP:Header><SOAP:Body>
    <sap:Manifest xmlns:sap='http://sap.com/xi/XI/Message/30' xmlns:xlink='http://www.w3.org/1999/xlink' xmlns:wsu='http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' wsu:Id='wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7'/></SOAP:Body></SOAP:Envelope>
    --SAP_512dbe91-372d-11db-b291-00145e483080_END
    content-id: [email protected]
    content-type: application/xml
    <?xml version="1.0" encoding="UTF-8"?>
    <ns1:ApprovalRequest xmlns:ns1="http://70.2.207.241:8080/axis/ApprovalService.jws"><args1>333</args1><args2>333</args2></ns1:ApprovalRequest>
    SAP_512dbe91-372d-11db-b291-00145e483080_END
    thanks
    venjamin
    Message was edited by: venjamin

  • Problem Proxy to SOAP Synchronous

    Hi Experts, I was looking for a solution to this problem, but I could not find the solution, I hope you can help me.
    I have the scenario PROXY ==> PI ==> SOAP (Synchronus).
    When the Web Service is ok, I have no problems, my problem is with the Fault Exception, because I tested it in SoapUI, and I'm getting this message.
    <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
       <S:Body>
          <S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope">
             <faultcode>S:Server</faultcode>
             <faultstring>Error al insertar Domicilio en servicio Empleado</faultstring>
             <detail>
                <FaultException:FaultException xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.interacciones.com.mx/ServicioEmpleado/" xmlns:FaultException="http://www.interacciones.com.mx/ServicioEmpleado/"/>
                <ns2:exception class="mx.com.interacciones.servicioEmpleado.FaultException_Exception" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false" xmlns:ns2="http://jax-ws.dev.java.net/">
                   <message>Error al insertar Domicilio en servicio Empleado</message>
                   <ns2:stackTrace>
                      <ns2:frame class="mx.com.interacciones.servicioEmpleado.ServicioEmpleadoImpl" file="ServicioEmpleadoImpl.java" line="87" method="agregarEmpleado"/>
                      <ns2:frame class="sun.reflect.GeneratedMethodAccessor267" line="unknown" method="invoke"/>
                      <ns2:frame class="sun.reflect.DelegatingMethodAccessorImpl" file="DelegatingMethodAccessorImpl.java" line="25" method="invoke"/>
                      <ns2:frame class="java.lang.reflect.Method" file="Method.java" line="597" method="invoke"/>
                      <ns2:frame class="weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker" file="WLSInstanceResolver.java" line="101" method="invoke"/>
                      <ns2:frame class="weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker" file="WLSInstanceResolver.java" line="83" method="invoke"/>
                      <ns2:frame class="com.sun.xml.ws.server.InvokerTube$2" file="InvokerTube.java" line="152" method="invoke"/>
                      <ns2:frame class="com.sun.xml.ws.server.sei.EndpointMethodHandler" file="EndpointMethodHandler.java" line="264" method="invoke"/>
                      <ns2:frame class="com.sun.xml.ws.server.sei.SEIInvokerTube" file="SEIInvokerTube.java" line="93" method="processRequest"/>
                      <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="604" method="__doRun"/>
                      <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="563" method="_doRun"/>
                      <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="548" method="doRun"/>
                      <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="445" method="runSync"/>
                      <ns2:frame class="com.sun.xml.ws.server.WSEndpointImpl$2" file="WSEndpointImpl.java" line="275" method="process"/>
                      <ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit" file="HttpAdapter.java" line="454" method="handle"/>
                      <ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter" file="HttpAdapter.java" line="250" method="handle"/>
                      <ns2:frame class="com.sun.xml.ws.transport.http.servlet.ServletAdapter" file="ServletAdapter.java" line="140" method="handle"/>
                      <ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke" file="HttpServletAdapter.java" line="319" method="run"/>
                      <ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter" file="HttpServletAdapter.java" line="232" method="post"/>
                      <ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="310" method="doPost"/>
                      <ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="727" method="service"/>
                      <ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="87" method="service"/>
                      <ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="820" method="service"/>
                      <ns2:frame class="weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction" file="StubSecurityHelper.java" line="227" method="run"/>
                      <ns2:frame class="weblogic.servlet.internal.StubSecurityHelper" file="StubSecurityHelper.java" line="125" method="invokeServlet"/>
                      <ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="292" method="execute"/>
                      <ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="175" method="execute"/>
                      <ns2:frame class="weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction" file="WebAppServletContext.java" line="3594" method="run"/>
                      <ns2:frame class="weblogic.security.acl.internal.AuthenticatedSubject" file="AuthenticatedSubject.java" line="321" method="doAs"/>
                      <ns2:frame class="weblogic.security.service.SecurityManager" file="SecurityManager.java" line="121" method="runAs"/>
                      <ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2202" method="securedExecute"/>
                      <ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2108" method="execute"/>
                      <ns2:frame class="weblogic.servlet.internal.ServletRequestImpl" file="ServletRequestImpl.java" line="1432" method="run"/>
                      <ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="201" method="execute"/>
                      <ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="173" method="run"/>
                   </ns2:stackTrace>
                </ns2:exception>
             </detail>
          </S:Fault>
       </S:Body>
    </S:Envelope>
    So, I was reading a lot of threads, those said to copy the structure, but it doest not work.
    I tried to check the "Do Not Use SOAP Envolve", but when I did that I got this error.
    Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 415 Unsupported Media Type
    When I unchecked I got this error.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
      <SAP:P1>com/sap/xi/tf/_MM_RecursosHumanos_ServicioEmplead~</SAP:P1>
      <SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
      <SAP:P3>on: Cannot create target element /ns0:Fault. Value</SAP:P3>
      <SAP:P4>s missing in queue context. Target XSD requires a~</SAP:P4>
      <SAP:AdditionalText />
      <SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_RecursosHumanos_ServicioEmplead~; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:Fault. Values missing in queue context. Target XSD requires a~</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    I could never see the Fault Structure in PI and neither in Web Service Navigator.
    Please, I need some help.
    Thank you very much.
    Regards

    If I test it in Soap UI I get the Fault, and in WsNavigator I can see the FaultCode and FaultString as a message on the top of the page.
    I do not know what more to do.
    <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
       <S:Body>
          <S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope">
             <faultcode>S:Server</faultcode>
             <faultstring>Error al insertar Domicilio en servicio Empleado</faultstring>
             <detail>
                <FaultException:FaultException xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.interacciones.com.mx/ServicioEmpleado/" xmlns:FaultException="http://www.interacciones.com.mx/ServicioEmpleado/"/>
                <ns2:exception class="mx.com.interacciones.servicioEmpleado.FaultException_Exception" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false" xmlns:ns2="http://jax-ws.dev.java.net/">
                   <message>Error al insertar Domicilio en servicio Empleado</message>
                   <ns2:stackTrace>
                      <ns2:frame class="mx.com.interacciones.servicioEmpleado.ServicioEmpleadoImpl" file="ServicioEmpleadoImpl.java" line="87" method="agregarEmpleado"/>
                      <ns2:frame class="sun.reflect.NativeMethodAccessorImpl" file="NativeMethodAccessorImpl.java" line="native" method="invoke0"/>
                      <ns2:frame class="sun.reflect.NativeMethodAccessorImpl" file="NativeMethodAccessorImpl.java" line="39" method="invoke"/>
                      <ns2:frame class="sun.reflect.DelegatingMethodAccessorImpl" file="DelegatingMethodAccessorImpl.java" line="25" method="invoke"/>
                      <ns2:frame class="java.lang.reflect.Method" file="Method.java" line="597" method="invoke"/>
                      <ns2:frame class="weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker" file="WLSInstanceResolver.java" line="101" method="invoke"/>
                      <ns2:frame class="weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker" file="WLSInstanceResolver.java" line="83" method="invoke"/>
                      <ns2:frame class="com.sun.xml.ws.server.InvokerTube$2" file="InvokerTube.java" line="152" method="invoke"/>
                      <ns2:frame class="com.sun.xml.ws.server.sei.EndpointMethodHandler" file="EndpointMethodHandler.java" line="264" method="invoke"/>
                      <ns2:frame class="com.sun.xml.ws.server.sei.SEIInvokerTube" file="SEIInvokerTube.java" line="93" method="processRequest"/>
                      <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="604" method="__doRun"/>
                      <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="563" method="_doRun"/>
                      <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="548" method="doRun"/>
                      <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="445" method="runSync"/>
                      <ns2:frame class="com.sun.xml.ws.server.WSEndpointImpl$2" file="WSEndpointImpl.java" line="275" method="process"/>
                      <ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit" file="HttpAdapter.java" line="454" method="handle"/>
                      <ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter" file="HttpAdapter.java" line="250" method="handle"/>
                      <ns2:frame class="com.sun.xml.ws.transport.http.servlet.ServletAdapter" file="ServletAdapter.java" line="140" method="handle"/>
                      <ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke" file="HttpServletAdapter.java" line="319" method="run"/>
                      <ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter" file="HttpServletAdapter.java" line="232" method="post"/>
                      <ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="310" method="doPost"/>
                      <ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="727" method="service"/>
                      <ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="87" method="service"/>
                      <ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="820" method="service"/>
                      <ns2:frame class="weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction" file="StubSecurityHelper.java" line="227" method="run"/>
                      <ns2:frame class="weblogic.servlet.internal.StubSecurityHelper" file="StubSecurityHelper.java" line="125" method="invokeServlet"/>
                      <ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="292" method="execute"/>
                      <ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="175" method="execute"/>
                      <ns2:frame class="weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction" file="WebAppServletContext.java" line="3594" method="run"/>
                      <ns2:frame class="weblogic.security.acl.internal.AuthenticatedSubject" file="AuthenticatedSubject.java" line="321" method="doAs"/>
                      <ns2:frame class="weblogic.security.service.SecurityManager" file="SecurityManager.java" line="121" method="runAs"/>
                      <ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2202" method="securedExecute"/>
                      <ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2108" method="execute"/>
                      <ns2:frame class="weblogic.servlet.internal.ServletRequestImpl" file="ServletRequestImpl.java" line="1432" method="run"/>
                      <ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="201" method="execute"/>
                      <ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="173" method="run"/>
                   </ns2:stackTrace>
                </ns2:exception>
             </detail>
          </S:Fault>
       </S:Body>
    </S:Envelope>

Maybe you are looking for

  • Doubt on server proxy and file to idoc scenario

    Hi,      I could able to solve most of my doubts from this forum, many regards to all who assisted me.Here are some simple doubts plz help me in solving them.           1.In FILE to PROXY scenario is it necessary to create rfc destination on IS and r

  • Help required on Datetime string conversion

    Hello Experts, I have a string with value '2010-07-16T07:30:00+03:00' which came from a webservice string data.Please advice how to declare variable in abap to get the correct date and time from this string? From my previous exp, if I had the xml str

  • BPC 4.2 Optimization error (object variable or with block variable not set)

    Hi All, I am getting the following error when I try to optimize application from the front end: Run-time error '91': Object variable or With block variable not set From the back end the optimization works just fine. This is the new application I crea

  • Excel Question

    Hello, Is it possible to do the following using the below table as an example. The first column is data that relates to a name in the 2nd column. If I paste a value into column 3 I would like a formula in column 4 that looks at the value in each cell

  • Deploying EJB with RAD

    Hello, I have an EJB application which uses several external JARs. I added them as a library to the project so that the bean will be able to pass the compilation. However, when I start the server (WebSphere 5.1 Test Environment), I get the exception: