Error in Interface Sync RFC-XI-SOAP

Hi,
I have an interface RFC - XI - SOAP Sync.
The error appears only in PRD environment and is intermittent error.
Follow the message error in sxmb_moni:
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Security.SecurityException: The event source ExceptionManagerInternalException does not exist and cannot be created with the current permissions. ---> System.Security.SecurityException: Requested registry access is not allowed. at Microsoft.Win32.RegistryKey.OpenSubKey(String name, Boolean writable) at System.Diagnostics.EventLog.CreateEventSource(String source, String logName, String machineName, Boolean useMutex) at System.Diagnostics.EventLog.CreateEventSource(String source, String logName, String machineName) at System.Diagnostics.EventLog.CreateEventSource(String source, String logName) at Microsoft.ApplicationBlocks.ExceptionManagement.DefaultPublisher.VerifyValidSource() --- End of inner exception stack trace --- at Microsoft.ApplicationBlocks.ExceptionManagement.DefaultPublisher.VerifyValidSource() at Microsoft.ApplicationBlocks.ExceptionManagement.DefaultPublisher.Publish(Exception exception, NameValueCollection additionalInfo, NameValueCollection configSettings) at Microsoft.ApplicationBlocks.ExceptionManagement.ExceptionManager.PublishInternalException(Exception exception, NameValueCollection additionalInfo) at Microsoft.ApplicationBlocks.ExceptionManagement.ExceptionManager.Publish(Exception exception, NameValueCollection additionalInfo) at Microsoft.ApplicationBlocks.ExceptionManagement.ExceptionManager.Publish(Exception exception) at mServices.WebServices.mServices.CancelServiceOrderList(OrderTypeCancelTO[] orders) --- End of inner exception stack trace ---</SAP:AdditionalText>
Could you help me?
Thank a lot.
Maicon.

> {quote:title=Rosa Maicon wrote:}
> Hi,
> I have an interface RFC - XI - SOAP Sync.
> The error appears only in PRD environment and is intermittent error.
> The event source ExceptionManagerInternalException does not exist and cannot be created with the current permissions.
This looks like a permission error for the user role provided in production. try sending soap request from web client tool and see whether you get the same error.
Check whether you have all the permissions required and also check whether there is WS security in the production environment.
Regards,
Pavan

Similar Messages

  • Error in SAOP adapter : RFC to SOAP Synch Scenario

    Hi Experts,
    Scenario is "RFC to SOAP Synch".
    For creating this following this link : **************** - Scenario on RFC to SOAP
    Trying to send XML to SOAP receiver.
    Using Below details for SOAP:
    Website : http://www.webservicex.net/WS/WSDetails.aspx?WSID=59&CATID=4
    Target URL : http://www.webservicex.net/SendSMS.asmx?WSDL
    SOAP Action: http://www.webserviceX.NET/SendSMSToIndia
    But when I try to send showing this error:
    "Error in processing caused by: com.sap.aii.af.lib.mp.module.ModuleException: call to messaging system failed: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIAdapterFramework:GENERAL:com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: unable to create a socket".
    Any one please suggest how resolve this issue?
    Is there any setup necessary in PI server to send message through SOAP?
    Thanks,
    Arthita

    Is there any setup necessary in PI server to send message through SOAP?
    No
    Solution
    Check if there are any firewall rules in place which are restricitng the PI system to connect with the URL
    : http://www.webservicex.net/SendSMS.asmx?WSDL
    Suggestion
    Copy paste this URL in browser and verify if it is accessible
    Sourabh

  • Error handling with Sync RFC

    Hi @ all,
    I have following scenario: a BPM doing some stuff on DB and map this values to a RFC request (sync) to a SAP R/3 system. Within this RFC I define 2 exceptions.
    I did map the RFC exception in interface mapping to a fault message.
    In BPM I put my RFC call into a Block with an Exception "RfcError" and insert a Exceptionbranch - which should send a email.
    Put anyhow it doesn't work - every RFC exception ends as an error in SMBX_MONI...
    Anyone a idea how to solve it??
    Regards Matt

    Hi Bhavesh,
    thanks for your tip, I see an error within my block their. But I don't know what it means to me
    Während des Anwendungs-Mappings com/sap/xi/tf/_MM_ Rfc_Error_to_Mail_ wurde eine com.sap.aii.util Work item 000000120730: Object CL_SWF_XI_MSG_BROKER method SEND_SYNCHRON cannot be executed
    No exception defined for system errors
    Error handling for work item 000000120729
    Runtime handle of object type  could not be created
    Runtime handle of object type  could not be created
    No exception defined for system errors
    Regards
    Matt

  • Get the Error-Message-Number from RFC to SOAP

    Hi All,
    we have implemented a synchronous SOAP-Call to RFC over XI. How can I get the message-number from the raised exception in the RFC-function Module to the SOAP-Caller?
    Thanks a lot
    Matthias

    Matthias,
    For you to have an exception structure when an rfc is imported into Xi, the rfc should have an exception defined. Usually we define an ApplicationError as one of the exceptions.
    The idea is that if there was an exception which you didnt handle in your rfc (BAPI return will be emplty), the exception will be returned to XI and shown in SXMB_Moni as hard error(of course there should be a message mapping avaliable in XI )
    In all the other cases, since you are populating BAPIReturn which is tables parameter, you should be able see the filled structure in your response message from RFC.
    Regards,
    naveen

  • RFC - XI - SOAP ERROR.

    I get a difficult error now, following is the error.
    my scerio is rfc -> xi -> soap.
    http://90.3.9.11:7001/axis/DocumentService.jws?wsdl
      <?xml version="1.0" encoding="UTF-8" ?>
    - <wsdl:definitions targetNamespace="http://90.3.9.11:7001/axis/DocumentService.jws" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://90.3.9.11:7001/axis/DocumentService.jws" xmlns:intf="http://90.3.9.11:7001/axis/DocumentService.jws" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    - <!--
    WSDL created by Apache Axis version: 1.4
    Built on Apr 22, 2006 (06:55:48 PDT)
      -->
    - <wsdl:message name="exportFileBySapIDRequest">
      <wsdl:part name="userID" type="xsd:string" />
      <wsdl:part name="mySingleID" type="xsd:string" />
      <wsdl:part name="sapID" type="xsd:string" />
      </wsdl:message>
    - <wsdl:message name="exportFileBySapIDResponse">
      <wsdl:part name="exportFileBySapIDReturn" type="xsd:string" />
      </wsdl:message>
    - <wsdl:portType name="DocumentService">
    - <wsdl:operation name="exportFileBySapID" parameterOrder="userID mySingleID sapID">
      <wsdl:input message="impl:exportFileBySapIDRequest" name="exportFileBySapIDRequest" />
      <wsdl:output message="impl:exportFileBySapIDResponse" name="exportFileBySapIDResponse" />
      </wsdl:operation>
      </wsdl:portType>
    - <wsdl:binding name="DocumentServiceSoapBinding" type="impl:DocumentService">
      <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
    - <wsdl:operation name="exportFileBySapID">
      <wsdlsoap:operation soapAction="" />
    - <wsdl:input name="exportFileBySapIDRequest">
      <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://DefaultNamespace" use="encoded" />
      </wsdl:input>
    + <wsdl:output name="exportFileBySapIDResponse">
      <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://90.3.9.11:7001/axis/DocumentService.jws" use="encoded" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:service name="DocumentServiceService">
    - <wsdl:port binding="impl:DocumentServiceSoapBinding" name="DocumentService">
      <wsdlsoap:address location="http://90.3.9.11:7001/axis/DocumentService.jws" />
      </wsdl:port>
      </wsdl:service>
      </wsdl:definitions>
    Design **************************************
    DT_exportFileBySapIDRequest
    --> exportFileBySapIDRequest
         -> userId
         -> mysingleId
         -> sapId
    DT_exportFileBySapIDResponse
    --> exportFileBySapIDResponse
         -> exportFileBySapIDReturn
    exportFileBySapIDRequest(Message Types)
    exportFileBySapIDResponse(Message Types)
    MI_RFC_TO_Webservice (Synchronous Inbound)
    exportFileBySapIDRequest
    exportFileBySapIDResponse
    MM_RFC_TO_Webservice_Req
    Z_XI_FI_MAILTEST  <----> exportFileBySapIDRequest
    MM_RFC_TO_Webservice_Resp
    exportFileBySapIDResponse <-----> Z_XI_FI_MAILTEST.response
    IM_RFC_TO_Webservice
    Z_XI_FI_MAILTEST     MI_RFC_TO_Webservice
    Configuration ************************************
    Communication Channel
    sender  : SAP_Sender_RFC_SEP
    receiver : RFC_TO_Webservice
                  target url : http://90.3.9.11:7001/axis/DocumentService.jws
    sxmb_moni Trace ************************************
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Response
      -->
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="T">Party normalization: sender</Trace>
      <Trace level="1" type="T">Sender scheme external = XIParty</Trace>
      <Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
      <Trace level="1" type="T">Sender party external =</Trace>
      <Trace level="1" type="T">Sender party normalized =</Trace>
      <Trace level="1" type="T">Party normalization: receiver</Trace>
      <Trace level="1" type="T">Receiver scheme external =</Trace>
      <Trace level="1" type="T">Receiver agency external =</Trace>
      <Trace level="1" type="T">Receiver party external =</Trace>
      <Trace level="1" type="T">Receiver party normalized =</Trace>
      <Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
      <Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.1</Trace>
      <Trace level="2" type="T">Host = sscxidev:8001</Trace>
      <Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
      <Trace level="2" type="T">Remote address = 90.3.9.13</Trace>
      <Trace level="1" type="T">COMMIT is done by XMB !</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
      <Trace level="3" type="T">Getting type of XMB...</Trace>
      <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
      <Trace level="2" type="T">XMB kind = CENTRAL</Trace>
      <Trace level="3" type="T">Start pipeline found</Trace>
      <Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
      <Trace level="3" type="T">No triggers found. OK.</Trace>
      </Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">XMB entry processing</Trace>
      <Trace level="3" type="T">system-ID = SXD</Trace>
      <Trace level="3" type="T">client = 001</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2006-12-14T11:36:36Z UTC+9</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Message-GUID = 5B0889208B6711DBC8380018717400ED</Trace>
      <Trace level="1" type="T">PLNAME = CENTRAL</Trace>
      <Trace level="1" type="T">QOS = EO</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">QOS = EO</Trace>
      <Trace level="3" type="T">Message-GUID = 5B0889208B6711DBC8380018717400ED</Trace>
      <Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
      <Trace level="3" type="T">External PLID = CENTRAL</Trace>
      <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
      <Trace level="3" type="T">Generate prefixed queue name</Trace>
      <Trace level="1" type="T">Queue name : XBTI0004</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTI0004</Trace>
      <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
      <Trace level="3" type="T">Setup qRFC Scheduler</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="3" type="T">Call qRFC .... MsgGuid = 5B0889208B6711DBC8380018717400ED</Trace>
      <Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
      <Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
      <Trace level="3" type="T">OK.</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Going to persist message</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="3" type="T">Version number = 000</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Persisting message Status = 001</Trace>
      <Trace level="3" type="T">Message version 000</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
      <Trace level="3" type="T">Trace object available again now. OK.</Trace>
      <Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
      <Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
      <Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
      <Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
      </Trace>
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">message version successfully read from persist version= 000</Trace>
      <Trace level="2" type="T">Increment log sequence to 001</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="3" type="T">system-ID = SXD</Trace>
      <Trace level="3" type="T">client = 001</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2006-12-14T11:36:36Z UTC+9</Trace>
      <Trace level="1" type="T">----
    </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">
      <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
      <Trace level="3" type="T">External PLID = CENTRAL</Trace>
      <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline attributes</Trace>
      <Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
      <Trace level="3" type="T">ENABLE = 1</Trace>
      <Trace level="3" type="T">TRACELEVEL = 0</Trace>
      <Trace level="3" type="T">EXEMODE = A</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline elements</Trace>
      <Trace level="3" type="T">ELEMPOS = 0001</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0002</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0003</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0004</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0007</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0008</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0009</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T" />
      <Trace level="1" type="Timestamp">2006-12-14T11:36:36Z UTC+9 Begin of pipeline processing PLSRVID = CENTRAL</Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
      <Trace level="1" type="Timestamp">2006-12-14T11:36:36Z UTC+9 Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      <Trace level="2" type="T">Start without given receiver</Trace>
      <Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
      <Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
      <Trace level="2" type="T">...valid Receiver w/o Condition: - MYS</Trace>
      <Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
      <Trace level="2" type="T">Number of Receivers:1</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2006-12-14T11:36:36Z UTC+9 End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 001</Trace>
      <Trace level="3" type="T">Message version 001</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
    - <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
      <Trace level="1" type="Timestamp">2006-12-14T11:36:36Z UTC+9 Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      <Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) MYS MI_MYS_Resp_IN_Async</Trace>
      <Trace level="2" type="T">...valid InbIf without Condition: MI_MYS_Resp_IN_Async</Trace>
      <Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2006-12-14T11:36:37Z UTC+9 End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 002</Trace>
      <Trace level="3" type="T">Message version 002</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
    - <!--  ************************************
      -->
      <Trace level="1" type="Timestamp">2006-12-14T11:36:37Z UTC+9 Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_RECEIVER_SPLIT</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
      <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="2" type="T">got property produced by receiver determination</Trace>
      <Trace level="1" type="T">number of receivers: 1</Trace>
      <Trace level="1" type="T">Single-receiver split case</Trace>
      <Trace level="1" type="T">Post-split internal queue name = XBTO6___0000</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Persisting single message for post-split handling</Trace>
      <Trace level="1" type="T" />
      <Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Persisting message Status = 012</Trace>
      <Trace level="3" type="T">Message version 003</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
      <Trace level="3" type="T">Trace object available again now. OK.</Trace>
      <Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
      <Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
      <Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
      <Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
      </Trace>
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">message version successfully read from persist version= 004</Trace>
      <Trace level="2" type="T">Increment log sequence to 005</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="3" type="T">system-ID = SXD</Trace>
      <Trace level="3" type="T">client = 001</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2006-12-14T11:36:37Z UTC+9</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
      <Trace level="3" type="T">External PLID = CENTRAL</Trace>
      <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline attributes</Trace>
      <Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
      <Trace level="3" type="T">ENABLE = 1</Trace>
      <Trace level="3" type="T">TRACELEVEL = 0</Trace>
      <Trace level="3" type="T">EXEMODE = A</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline elements</Trace>
      <Trace level="3" type="T">ELEMPOS = 0001</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0002</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0003</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0004</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0007</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0008</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0009</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T" />
      <Trace level="1" type="Timestamp">2006-12-14T11:36:37Z UTC+9 Begin of pipeline processing PLSRVID = CENTRAL</Trace>
      <Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
    - <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
      <Trace level="1" type="Timestamp">2006-12-14T11:36:37Z UTC+9 Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
      <Trace level="2" type="T">......attachment XI_Context not found</Trace>
      <Trace level="3" type="T">Mapping already defined in interface determination</Trace>
      <Trace level="3" type="T">Object ID of Interface Mapping BA9D2B14DB953699A6F72BB0C992416E</Trace>
      <Trace level="3" type="T">Version ID of Interface Mapping CAB00A010BF111DBCC73F1B85A1E0C79</Trace>
      <Trace level="1" type="T">Interface Mapping http://xi.mySingle.draft.send IM_MYS</Trace>
      <Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_MM_MYS_</Trace>
      <Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
      <Trace level="2" type="T">Mode 0</Trace>
      <Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_MM_MYS_.</Trace>
      <Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_MYS_</Trace>
      <Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_MYS_ completed. (executeStep() of com.sap.xi.tf._MM_MYS_</Trace>
      <Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2006-12-14T11:36:37Z UTC+9 End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 005</Trace>
      <Trace level="3" type="T">Message version 005</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
    - <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
      <Trace level="1" type="Timestamp">2006-12-14T11:36:38Z UTC+9 Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_OUTBINDING</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
      <Trace level="2" type="T">O U T B O U N D - B I N D I N G</Trace>
      <Trace level="2" type="T">Cache Content is up to date</Trace>
      <Trace level="2" type="T">determine OUTBOUND BINDING for:</Trace>
      <Trace level="2" type="T">-MYS</Trace>
      <Trace level="2" type="T">-MYS</Trace>
      <Trace level="2" type="T">http://xi.mySingle.draft.send.MI_MYS_Resp_IN_Async</Trace>
      <Trace level="2" type="T">Channel found: - MYS - FS_MysEmpty</Trace>
      <Trace level="2" type="T">no header mapping defined</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2006-12-14T11:36:38Z UTC+9 End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 006</Trace>
      <Trace level="3" type="T">Message version 006</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
    - <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">
      <Trace level="1" type="Timestamp">2006-12-14T11:36:38Z UTC+9 Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
      <Trace level="3" type="T">ADRESSMOD = SD</Trace>
      <Trace level="3" type="T">P_CLASS =</Trace>
      <Trace level="3" type="T">P_IFNAME =</Trace>
      <Trace level="3" type="T">P_METHOD =</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Unknown channel type: File</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = AENGINE</Trace>
      <Trace level="3" type="T">ADRESSMOD = SD</Trace>
      <Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_IE_ADAPTER</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
      <Trace level="3" type="T">Channel for adapter engine: File</Trace>
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
      <Trace level="2" type="T">return fresh values from cache</Trace>
      <Trace level="2" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET):</Trace>
      <Trace level="3" type="T">URL = http://sscxidev:50100/MessagingSystem/receive/AFW/XI</Trace>
      <Trace level="3" type="T">User = PIISUSER</Trace>
      <Trace level="3" type="T">Cached = X</Trace>
      <Trace level="3" type="T">Creating HTTP-client</Trace>
      <Trace level="3" type="T">HTTP-client: creation finished</Trace>
      <Trace level="3" type="T">Security: Basic authentication</Trace>
      <Trace level="3" type="T">Serializing message object...</Trace>
      <Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
      <Trace level="3" type="T">HTTP-client: request sent</Trace>
      <Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
      <Trace level="3" type="T">HTTP-client: response received</Trace>
      <Trace level="3" type="T">HTTP-client: checking status code...</Trace>
      <Trace level="3" type="T">HTTP-client: status code = 200</Trace>
      <Trace level="3" type="T">Deserializing message object...</Trace>
      <Trace level="3" type="T">HTTP-client: closing...</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2006-12-14T11:36:38Z UTC+9 End of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 007</Trace>
      <Trace level="3" type="T">Message version 007</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
      <Trace level="3" type="T">Async processing: skip mapping of response</Trace>
      </Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Async processing completed OK.</Trace>
      <Trace level="3" type="T">system-ID = SXD</Trace>
      <Trace level="3" type="T">client = 001</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2006-12-14T11:36:38Z UTC+9</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Persisting message Status = 003</Trace>
      <Trace level="3" type="T">Message version 008</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </SAP:Trace>
    Thanks.

    Have you cheked this blogs?
    If you havenot,
    /people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
    /people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2

  • Error RFC to SOAP Scenario

    Hi Experts,
    I am getting an error while dealing with RFC to SOAP scenario::
    soap fault: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: . at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest() at System.Web.Services.Protocols.SoapServerProtocol.Initialize() at System.Web.Services.Protocols.ServerProtocol.SetContext(Type type, HttpContext context, HttpRequest request, HttpResponse response) at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
    IS it problem from the webserver in sending the response?
    Please suggest.
    Thanks & Regards,
    Sushama

    Hi Suraj,
    Thanks for the imputs.
    We are given with the webservice by separate team, also I am accessing the application via Citrix. I cant test the WS outside the client network and in client desktop they haven't installed Altova Xml Spy
    Request and response both are generated in Moni. It seems problem in receiving response only ?? WS url is also correct.
    Regarding Receiver Soap parameters:
    I have checked adapter specific identifiers and Variable transport binding.
    Please suggest, if this is problem with the WS, I need to check with the team.
    Thanks & Regards,
    Sushama

  • ASync RFC -- Sync RFC -- SOAP scenario: do I need BPM?

    Hi,
    I have this scenario. ASync RFC --> PI --> Sync RFC --> PI  --> SOAP scenario.
    Here are the details.
    1. users run async RFC and it will pass data to PI.
    2. PI will call Sync RFC with received data and get the data.
    3. PI now calls web service with received data from #2.
    Do I need BPM to implement this scenario.
    Thank you.
    -Won

    I'm still wondering if it's possible to perform my scenario without using RFC lookup or BPM.
    Yes, it is possible.
    I want to see if PI supports sequence of calling RFC, JDBC, web service, etc and pass data to
    the next call in sequence... without BPM...
    Yes, PI supports that. Please make a search on SDN, there are numerous blogs / posts which talks about A/S bridge without BPM.

  • RFC to SOAP sync error

    Hi All,
    I am doing the RFC to SOAP sync scenario. request R3 data is coming to XI and its triggering to SOAP receiver.
    Information SOAP: continuing to response message e9598290-a14f-11df-969a-00145e474044
    Error SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
    i have tried to test the File to SOAP sync scenario to test the SOAP and its working fine. from file request to soap request and soap response to file response.
    the same way i have done the RFC request to soap request and soap response to rfc response.
    in sxmi_moni i can see the request from RFC but i did't find the request mapping to SOAP.
    I have tested the test mapping and its working fine.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  XML Validation Outbound Channel Response
      -->
    - <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://www.webMethods.com/2001/10/soap/encoding">exception</SAP:ApplicationFaultMessage>
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    the r3 request stacture is:
    <filed1>
    <filed2>
    <filed3>
    <ITEM>
    <ITEM1>
    <ITEM22>
    </ITEM>
    the soap request stacture is:
    <filed1>
    <filed2>
       <Header>
        <filed1>
        <filed2>
        <filed3>
       </header>
       <Item>
        <item1
        <item2>
        <item3>
       </Item>
    </field2>
    </field1>   
    is there any issue with mapping?
    RFC sender CC error is Error in processing caused by: com.sap.aii.adapter.rfc.core.server.RfcServerException: got unexpected document type:DOC_TYPE_UNKNOWN
    Can you pls let me know the some inputs to reslove this issue
    Thanks,
    Venkat

    have tried to test the File to SOAP sync scenario to test the SOAP and its working fine. from file request to soap request
    and soap response to file response. the same way i have done the RFC request to soap request and soap response to rfc
    response.
    FILE to SOAP Sync scenario....did you use RequestResponseBean and are you using the same to process RFC to SOAP Sync scenario? If yes, then you dont need the RequestResponseBean for RFC <--> SOAP.
    in sxmi_moni i can see the request from RFC but i did't find the request mapping to SOAP. I have tested the test mapping
    and its working fine. - - Application APPLICATION_ERROR application fault exception M the r3 request stacture is: the soap
    request stacture is: is there any issue with mapping?
    I hope you have included a mapping program for Request Mapping and also for Response Mapping in the Interface/ Operation Mapping and included the same in Interface Determination!
    Regards,
    Abhishek.

  • PI 7.11 sp6 - SOAP error on INBOUND SYNC (BE) interface - No handler ...

    Experts,
    We're running a AIX 6.1 unix based PI 7.11 system patched to Stack SP6.  We've got one instance...no web dispatcher or load balancing of any kind.
    Our proxy system (sender) is an ECC6.0 EHP4 system.  Our 3rd party system (receiver) system is non-sap.
    In about a 2 hour timespan, we processed 9700 XML messages all in the SOAP adapter.  almost all our traffic is BE (sync).  Of those messages, we got 11 errors.  And here is what we see in XSMB_MONI and in the java default trace:
    #2.0^H#2011 08 29 15:40:08:183#0-500#Error#com.sap.aii.adapter.xi.ms.XIEventHandler#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#327C4279AB0F2E5C000000010019C0BE#3930552000000004#sap.com/com.sap.aii.af.ms.app#com.sap.aii.adapter.xi.ms.XIEventHandler.onRequest(Services, TransportMessage)#PIISUSER#8
    546##875E5AD3D27311E0C8580000003BF9B8#875e5ad3d27311e0c8580000003bf9b8#875e5ad3d27311e0c8580000003bf9b8#0#Thread[HTTP Worker [@2008983637],5,Dedicated_Application_Thread]#Plain##
    Message 4e5b07b7-8180-00ab-e100-80000ae201a4(INBOUND): was not delivered due to com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PA
    RSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> No handler is registered for this service.#
    #2.0^H#2011 08 29 15:40:08:081#0-500#Error#com.sap.engine.messaging.impl.spi.ServicesImpl#
    #BC-XI-CON-MSG#com.sap.aii.af.ms.svc#327C4279AB0F2E98000000000019C0BE#3930552000000004##com.sap.engine.messaging.impl.spi.ServicesImpl.deliver(Message)#J2EE_GUEST#0##875E5AD3D27311E0C8580000003BF9B8#875e
    5ad3d27311e0c8580000003bf9b8#875e5ad3d27311e0c8580000003bf9b8#0#MS Queue Worker [SOAP_http://sap.com/xi/XI/SystemRqst]#Plain##
    Caught exception com.sap.engine.interfaces.messaging.api.exception.MessagingException from application code with msgKey: 4e5b07b7-8180-00ab-e100-80000ae201a4(INBOUND)#
    So I've looked all over the marketplace and SDN/google.  I could not find anyone else getting this type of error.
    We have WILY introscope and all the diag tools.  I am not seeing any bottlenecks on the threads for http or inbound/outbound queues.
    I was hoping someone could point me in the right direction.  I was thinking about bumping up all the default queue threads for the com.sap.aii.af.ms.svc service.  It has the default "10" for all those. 
    We have done MAJOR tuning already on this instance.  I think I've read all the notes/guides/HOW-TO...etc that there is for PI 7.11.  So we are making progress.
    Thanks,
    NICK

    Hi Nick,
    From error message i could feel that, there is no problem from PI side and error is at the receiver system side where PI is posting the message. Why i am telling it's not PI issue and it's receiver's issue is that, error message you got is SOAP fault message. Fault message are raised by receiver system if any error occurs. If messgae is processed successfully then receiver system would send proper SOAP response message not a SOAP fault.
    soap fault: Server was unable to process request. ---> No handler is registered for this service.#
    So, in my view you better check at your receiver system (in your case it's no-sap sytem) why it's giving problem as 'No handler is register for the service'.
    Rgards,
    RK

  • Error PI 7.31 RFC-SOAP Certificate Rejected

    Hi Experts,
    I'm facing an error last days.
    The scenario is, an interface was working fine in DEV, but in QAS stopped.
    DEV and QAS has the same configuration, same endpoint, user, etc....
    In QAS the error in PI 7.31 was:
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: iaik.security.ssl.SSLCertificateException: Peer certificate rejected by ChainVerifier
    So, I saw the certificate and it was expired. The server updated the certified.
    And now DEV and QAS stopped working, and both return the message above in PI.
    The certificate is a auto-signed, and according to the documentation there was no certificate installation in development.
    The communication is an RFC to SOAP synchronous.
    Using Proxy, and authentication.
    The communication channel was not changed, and they don't have certificate authentication.
    I requested de basis team to install the certificate in NWA, but the view does not appeard in the configuration in PI.
    So... any idea what's my problem?
    Thanks.

    Hi,
    Thanks all for the answers.
    I already requested the installation of certificate, but they don't appear in configuration of channel communication on PI:
    the certificate installed:
    Any Ideia?

  • RFC to Soap Sync with attachment

    I have an interface RFC u2013 SOAP Sync, PI 7.1 and SAP is R/3, without proxy connection.
    The SOAP message returned the value in this format: <return href=u201Dcid:XXXXXXXXXXXu201D >. I think this is an attachment.
    Anybody knows how can I read this attachment and return the values back to RFC?
    I found some threads here, but sincerely, none helped me. If necessary custom adapter Module, what will be necessary to put in this module? Is there an example?
    Best Regards,
    Maicon

    Hi,
    RFC Adapter does not support attachments.
    However you may try this link for soap adapter:
    [http://help.sap.com/saphelp_nwpi711/helpdata/en/cd/5af7c0c994e24fb0d0088443513de2/frameset.htm]
    Regards,
    Beena.

  • RFC error while running sync job in AC 10

    I have done all the configuration to add new SAP system via SPRO in GRC 10. Now I am trying to run the sync job for the first time, I am getting the below mssage. I checked the RFC desitinations, it looks fine.
    Error in RFC; 'Function module "/GRCPI/GRIA_ROLE_GET_RANGES" not'
    Error in RFC; 'Function module "/GRCPI/GRIA_ROLE_GET_RANGES" not'
    Role sync failed with errors
    Program for Repository User Synchronization
    Error in RFC; 'Function module "/GRCPI/GRIA_USR_GET_RANGES" not f'
    User sync failed with errors
    Repository Object sync job failed with errors
    Please check SLG1 for further details
    I checked in SLG1 also, its displaying the same errors as listed above.  I have some systems added earlier which are correctly configured and working fine. I tried to match the configuration with the new systems, and everything looks fine. Not sure why this error is coming.
    Please someone can help.

    Hello,
    It seems to be a problem with the add-on in the back-en system, and a function module couldn't be found. Check the RFC connection (refer here for example GRC AC10 sync job error ) and make sure the add-on is properly installed.A simple check could be go to the back-end system, tx SE37 and check if the function modules exist.
    Cheers,
    Diego.

  • RFC to SOAP Interface - Problem in Request Message Mapping

    Dear All,
    We are working on RFC to SOAP Scenario i.e. pulling out data from an WebService from SAP via PI.
    In Request Message Mapping, when the wsdl file is uploaded as Target Message, the wsdl request shows the nested elements like below.
    <Request>
       <Request_New>
          <PAR1>xyz</PAR1>
          <PAR2>123</PAR2>
       </Request_New>
    </Request>
    But the desired Request should go like below.
    <Request>
       <PAR1>xyz</PAR1>
       <PAR2>123</PAR2>
    </Request>
    Hence it gives an error saying that the tag Request_New does not exist.

    Dear All,
    Our target webservice cotains multiple methods.
    The every method contains its corresponding request, response and SQL ecxeption as messages.
    In case of request structures, every method (except crmPaymentReceived) contains more than 1 root element.
    So while calling those methods having more than 1 root element, the additional header tag will always appear(not avoidable) in the request coming from SAP PI.
    For Example,
    Request Structure for method u2018isLoginIdExistu2019 (having more than 1 root element)
    <?xml version="1.0" encoding="UTF-8"?>
    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <soap:Body>
    <ns1:isLoginIdExistRequest xmlns:ns1="http://netpricing">      -
    >>>>>  u201CThis Header tag will always appear u201D
    <isLoginIdExistin0>asp</isLoginIdExistin0>
    <isLoginIdExistin1>1</isLoginIdExistin1>
    </ns1:isLoginIdExistRequest>
    </soap:Body>
    </soap:Envelope>
    For this method, we get the error(saying that ns1:isLoginIdExistRequest xmlns:ns1="http://netpricing" does not exists).
    Request Structure for method u2018crmPaymentReceivedu2019 (having only 1 root element)
    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd=http://www.w3.org/2001/XMLSchema-instance xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <soap:Body>
    <ns1:crmPaymentReceivedin0 xmlns:ns1="http://netpricing">false</ns1:crmPaymentReceivedin0>
    </soap:Body>
    </soap:Envelope>
    For this method, we get the success response.
    I tested their wsdl URL in XMLspy and wizdal(a wsdl testing tool), it shows request in the format having only root elements and not the header tags.
    But header tags will always appear when header tag contains more than 1 root element.
    Can anybody suggest me how do I tackle this?
    Thanks in Advance.

  • RFC to SOAP Scenario error

    Hello ALL
    I am trying to working in RFC to SOAP scenario in sap pi 7.31 single stack system.with help of blog **************** - Scenario on RFC to SOAP
    i am trying to pass input values from ECC through RFC  to web service .
    while sending data using  function module from ECC system i got following error
    thnx in advance

    Hi Ganesh,
    are you getting any error is SM58? Please check the below blog for configuration
    Michal's PI tips: How do you activate ABAP Proxies with AEX - simplified version
    IDOC_AAE To File with all Configurations
    the below discussion will be useful
    RFC to FILE(7.3) single stack

  • RFC to SOAP Scenarion : Error while communication

    Hi Experts,
    We are trying RFC to SOAP Scenario. When we trigger the message from RFC we get error as Communication error . when we re-activate the Sender communication channel in PI , the program-ID gets registered and we can trigger the message. This problem we are facing regularly and we have to re-activate the Sender RFC communication channel everytime.
    How can we solve this problem.
    Regards,
    Syed

    Have you tried increasing the parameter "Maximum Connections"? Is it possible that the same program ID is used for more than one scenarios?
    Regards,
    Prateek

Maybe you are looking for

  • How can I add a new field for Belgium in T588M?

    Hi experts, I am trying to change the infotype 0002 screen for BElgium. This is how I am doing T588M > new entry > MP000200 > alt. screen 2012 > var. key 12 >  feature p0002 >. I also maintained 12 as the var. key for the countr yBE in P0002 feature.

  • SSL error occurred, secure connextion cannot be made

    Hello everyone, I was trying to put a picture online on my blogger-blog with MarsEdit when I got this weird error: An SSL error has occurred and a secure connection to the server cannot be made. When I checked MarsEdit net-log, there was an URL: http

  • Return data on fillable pdf

    Sending out a fillable pdf, but when page comes back (even using the distribute option) the data is apparently in xml form.  It is not in the filled out page form.  How do I change the default on my pdf form to make it come back as a filled form?

  • Mstsc.exe keeps crashing trying to connect

    Everytime I try to connect to my server, My RDP connection crashes every time. Ive tried all I can and some days it works and some days it doesnt. Problem signature:   Problem Event Name:    APPCRASH   Application Name:    mstsc.exe   Application Ver

  • HOW can I call EJB with JSP?

    Hi, I'm working with JSP and want to include some EJB. I dont know how can I access EJB through JSP. I dont know if I use the right code in JSP for calling EJB. Did someone know how to use that? Can someone tell me if is the right code in JSP in my e