Missing WS_HEADER protocol in client proxy

Hi!
I generated a client proxy to consume services from 3rd party application, wanted to use standard SAP WS security with user and timestamp, logical port with security profile didn't work, used proxy's header protocol to create my own security header and it worked fine.
Then I generated the new proxy with different set of services from the same application and wanted to do the same thing. To my surprise, there was no header protocol. I debugged the GET_PROTOCOL method and saw that the proxy's attribute table PROTOCOLS does not contain the WS_HEADER protocol (class CL_WSPROTOCOL_WS_HEADER), but instead of it XI_HEADER (CL_WSPROTOCOL_XI_HEADER). I can't use XI protocol (or at least don't know how) - it's completely different and has no SET_REQUEST_HEADER method.
Why in the world would 3rd party application use XI? Can I find this somewhere in WSDL? I have no idea - please give me some hints.
Thanks in advance!
Igor

Hi Igor,
Can you tell me how do you have called your external WebService that uses standard WS Security with user and password, using the proxy's header protocol?
I'm trying to do it but I keep getting the following error: "SoapFaultCode:1  WSDoAllReceiver: Request does not contain required Security header".
Can you give me a example how did I do it?
I've tried also with the logical port's security profile but with no success.
Thanks in advance!
Alexandre

Similar Messages

  • Error generating Client Proxy - object  missing in WSDL

    Hello,
    I have error while generating Client Proxy.
    I have WSDL and XSD in files. I get error message:
    object <message name="requestUPOMessage"> missing in WSDL
    Diagnosis
    In the WSDL document, the object
       "<portType name="GateServicePortType"> <operatio..."
    from the namespace
      "https://bramka.edeklaracje. mf.gov.pl/"
    links to the object
       "<message name="requestUPOMessage">"
    from the namespace
       "https://bramka.e-deklaracje.mf.gov.pl/"
    However, this last object does not exist in the WSDL document.
    WSDL FILE and XSD FILE: http://www.sendspace.com/filegroup/N8kSxPp5bhY2nVfcNBbAXg
    WSDL:
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
    xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
    xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:ns="https://bramka.edeklaracje.
    mf.gov.pl/xsd" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:gate="https://bramka.e-deklaracje.mf.gov.pl/"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="https://bramka.edeklaracje.
    mf.gov.pl/">
    <wsdl:types>
    <xs:schema attributeFormDefault="qualified" elementFormDefault="qualified"
    targetNamespace="https://bramka.e-deklaracje.mf.gov.pl/xsd"
    xmlns:xs="http://www.w3.org/2001/XMLSchema">
    <xs:include schemaLocation="GateService.xsd"/>
    </xs:schema>
    </wsdl:types>
    <wsdl:message name="sendDocumentWithAttachmentResponseMessage">
    <wsdl:part name="part1" element="ns:sendDocumentWithAttachmentResponse">
    </wsdl:part>
    </wsdl:message>
    <wsdl:message name="sendUnsignDocumentResponseMessage">
    <wsdl:part name="part1" element="ns:sendUnsignDocumentResponse">
    </wsdl:part>
    </wsdl:message>
    <wsdl:message name="requestUPOResponseMessage">
    <wsdl:part name="part1" element="ns:requestUPOResponse">
    </wsdl:part>
    </wsdl:message>
    <wsdl:message name="sendDocumentResponseMessage">
    <wsdl:part name="part1" element="ns:sendDocumentResponse">
    </wsdl:part>
    </wsdl:message>
    <wsdl:message name="sendUnsignDocumentMessage">
    <wsdl:part name="part1" element="ns:sendUnsignDocument">
    </wsdl:part>
    </wsdl:message>
    <wsdl:message name="sendDocumentMessage">
    <wsdl:part name="part1" element="ns:sendDocument">
    </wsdl:part>
    </wsdl:message>
    <wsdl:message name="requestUPOMessage">
    <wsdl:part name="part1" element="ns:requestUPO">
    </wsdl:part>
    </wsdl:message>
    <wsdl:message name="sendDocumentWithAttachmentMessage">
    <wsdl:part name="part1" element="ns:sendDocumentWithAttachment">
    </wsdl:part>
    </wsdl:message>
    <wsdl:portType name="GateServicePortType">
    <wsdl:operation name="sendDocument">
    <wsdl:input message="gate:sendDocumentMessage">
    </wsdl:input>
    <wsdl:output message="gate:sendDocumentResponseMessage">
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="sendUnsignDocument">
    <wsdl:input message="gate:sendUnsignDocumentMessage">
    </wsdl:input>
    <wsdl:output message="gate:sendUnsignDocumentResponseMessage">
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="sendDocumentWithAttachment">
    <wsdl:input message="gate:sendDocumentWithAttachmentMessage">
    </wsdl:input>
    <wsdl:output message="gate:sendDocumentWithAttachmentResponseMessage">
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="requestUPO">
    <wsdl:input message="gate:requestUPOMessage">
    </wsdl:input>
    <wsdl:output message="gate:requestUPOResponseMessage">
    </wsdl:output>
    </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="GateServiceSOAP12Binding" type="gate:GateServicePortType">
    <soap12:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsdl:operation name="sendDocument">
    <soap12:operation soapAction="urn:sendDocument" style="document"/>
    <wsdl:input>
    <soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:input>
    <wsdl:output>
    <soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="sendUnsignDocument">
    <soap12:operation soapAction="urn:sendUnsignDocument" style="document"/>
    <wsdl:input>
    <soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:input>
    <wsdl:output>
    <soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="sendDocumentWithAttachment">
    <soap12:operation soapAction="urn:sendDocumentWithAttachment" style="document"/>
    <wsdl:input>
    <soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:input>
    <wsdl:output>
    <soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="requestUPO">
    <soap12:operation soapAction="urn:requestUPO" style="document"/>
    <wsdl:input>
    <soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:input>
    <wsdl:output>
    <soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:binding name="GateServiceSOAP11Binding" type="gate:GateServicePortType">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsdl:operation name="sendDocument">
    <soap:operation soapAction="urn:sendDocument" style="document"/>
    <wsdl:input>
    <soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="sendUnsignDocument">
    <soap:operation soapAction="urn:sendUnsignDocument" style="document"/>
    <wsdl:input>
    <soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="sendDocumentWithAttachment">
    <soap:operation soapAction="urn:sendDocumentWithAttachment" style="document"/>
    <wsdl:input>
    <soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="requestUPO">
    <soap:operation soapAction="urn:requestUPO" style="document"/>
    <wsdl:input>
    <soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="GateService">
    <wsdl:port name="GateServiceSOAP12port" binding="gate:GateServiceSOAP12Binding">
    <soap12:address location="https://test-bramka.edeklaracje.gov.pl/uslugi/dokumenty/"/>
    </wsdl:port>
    <wsdl:port name="GateServiceSOAP11port" binding="gate:GateServiceSOAP11Binding">
    <soap:address location="https://test-bramka.edeklaracje.gov.pl/uslugi/dokumenty/"/>
    </wsdl:port>
    </wsdl:service>
    </wsdl:definitions>
    XSD
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="https://bramka.edeklaracje.
    mf.gov.pl/xsd" targetNamespace="https://bramka.e-deklaracje.mf.gov.pl/xsd"
    elementFormDefault="qualified" attributeFormDefault="qualified">
    <xs:element name="sendDocument">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="document" type="xs:base64Binary"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="sendDocumentResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="refId" type="xs:string" minOccurs="0"/>
    <xs:element name="status" type="xs:int"/>
    <xs:element name="statusOpis" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="sendUnsignDocument">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="document" type="xs:base64Binary"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="sendUnsignDocumentResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="refId" type="xs:string" minOccurs="0"/>
    <xs:element name="status" type="xs:int"/>
    <xs:element name="statusOpis" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="sendDocumentWithAttachment">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="attachment" type="xs:base64Binary" minOccurs="0"/>
    <xs:element name="document" type="xs:base64Binary"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="sendDocumentWithAttachmentResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="refId" type="xs:string" minOccurs="0"/>
    <xs:element name="status" type="xs:int"/>
    <xs:element name="statusOpis" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="requestUPO">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="refId" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="requestUPOResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="upo" type="xs:string" minOccurs="0"/>
    <xs:element name="status" type="xs:int"/>
    <xs:element name="statusOpis" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    </xs:schema>
    Maybe someone know what is wrong in wsdl file and how to correct this?

    Hi Marcus,
    Did you fix the problem?
    I'm asking because I'm dealing with the same problem! I tried to generate a Proxy object from a WSDL document and I can't... I always receive the error "Cannot generate proxy (object  missing in WSDL, see long text)". I have checked on the service.sap.com and I found a xls document with all unsupported WSDL elements and one of them is the "part name=" and I have it in my WSDL! I don't know how to workaround this issue, can you help me please?
    Thanks in advance,
    Ricardo.

  • Async Client proxy -PI - File scenario- Pipeline steps missing in SXMB_MONI

    Hi
    I made a scenario where an ABAP client proxy(in a BW system) pulls data from a BW table and push it to PI.
    In PI a Mapping is done to write an XML file and sump it to a desired location.
    It is working fine in the development environment(request send to PI and mapped into an xml file)..so i migrated it to the quality/test environment where it started failing(It is only visible till SXMB_MONI of Client system and not reaching PI in case of quality/test environment).
    I checked SLDCHECK in the Client environments (say DWC for development and DWA for quality) and it looks fine.
    All I could see is:
    In SXMB_MONI of development system DWC--> Steps that are followed are
    Inbound Message
    Call Integration Server
    Response
    In SXMB_MONI of quality/test system DWA-->The only step is
    Inbound Message
    Could this be an Integration Server issue ??
    Please advise !!
    Regards,
    Naina

    check and compare the the parameter are set in SXMB_ADM of Dev system with Quality system.
    u can refer this blog for steps.
    /people/michal.krawczyk2/blog/2005/05/10/xi-i-cannot-see-some-of-my-messages-in-the-sxmbmoni
    chirag

  • Client Proxy Question

    Hi all,
    Initially, when we have created a client proxy in ECC 5.0 with Oracle on Windows,
    we have chosen Local File as the WSDL source. We had the WSDL saved locally.
    This way we have generated a Client Proxy in SE80.
    Then we created a logical port using LPCONFIG.
    Since this the default logical port, we just saved it with all the settings imported
    from the WSDL definition.
    This way the Client proxy was working fine.
    The doubt that I have is, later on, if we want to just change the URL under
    call paramters in LPCONFIG to the URL of the WSDL residing on some
    other server(Non SAP), will the client proxy work?
    Regards,
    Vishnu

    Hi Gaurav,
    Looking at the error below, the binding is happening.
    However, there is a return code 503. And SAP is not able to access the
    Webservice located at the other server(Non-SAP).
    INFO 01:44:43: SOAP SESSION Protocol CL_SOAP_SESSION_PROTOCOL
    ->IF_SOAP_PROTOCOL~PRE_PROCESS() SOAP Session Protocol
    preprocessed
    INFO 01:44:43: SOAP Transport Binding CL_SOAP_HTTP_TPBND_ROOT
    ->IF_SOAP_TRANSPORT_BINDING~SEND() Try to send message ( DEST =
    ,PATH = ,URL = http://server name:portno/ ,SOAP Action = "ROI_R3
    _DF.roiSAPCreateOrder" )
    INFO 01:44:43: SOAP Transport Binding CL_SOAP_HTTP_TPBND_ROOT
    ->IF_SOAP_TRANSPORT_BINDING~SEND() Message sent
    INFO 01:44:43: SOAP Transport binding CL_SOAP_HTTP_TPBND_ROOT
    ->IF_SOAP_TRANSPORT_BINDING~RECEIVE() Try to receive message
    INFO 01:44:52: SOAP HTTP Binding CL_SOAP_HTTP_TPBND_ROOT->HANDLE
    _STATUS_CODE() Received return code 503 ( not available )
    ERROR 01:44:52: SOAP Message CL_SOAP_MESSAGE->IF_SOAP_MESSAGE
    _PART~INIT_FOR_DESERIALIZE() A SOAP Runtime Core Exception
    occurred in method XP_READ_TAG of class CL_SOAP_XP at position id
    1 with internal error id 112 and error text no extended error
    message (SOAP_ESERVER) (fault location is 1 ).
    Regards,
    Vishnu

  • Error in CRM box after executing client proxy

    Hi ,
    I am executing client proxy program from CRM box.
    It is getting the following error in CRM sxmb_moni
    I checked the sm59 in CRM box. the  RFC connection ( type 3) is configured for XI box (XI1CLNT100_RFC).
    In SXMB_ADM of CRM box the correspoinding integration server is 'dest://XI1CLNT100_RFC'.
    I am not able to debug this.. any help please..
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">DESTINATION_NOT_FOUND</SAP:Code>
      <SAP:P1>XI1CLNT100_RFC</SAP:P1>
      <SAP:P2>CR1</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>HTTP destination XI1CLNT100_RFC missing (system , transaction SM59)</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>

    Hi Ashok,
    > I checked the sm59 in CRM box. the  RFC connection ( type 3) is configured for XI box (XI1CLNT100_RFC).
    > In SXMB_ADM of CRM box the correspoinding integration server is 'dest://XI1CLNT100_RFC'.
    XI adapter uses HTTP connection.So create RFC destination with Connection type H and following parameters
    1 Connection Type: H
    2 Target Host: System name
    3 Service Number: HTTP Port name
    4 Path Prefix: /sap/XI/engine/?type=entry
    On the Logon/Security tab page, enter the following logon data:
    1 User: XIAPPLUSER (for example); this user should represent the sending business system (see also the SAP XI Security Guide under Service Users for Message Exchange).
    2 Password: the password you have specified for this user
    3 Client: SAP XI Integration server
    4 Language: Language required
    and use this HTTP destination in TA - SXMB_ADM configuration.
    Cheers,
    Jag

  • Advice on client proxy generation (ABAP and SAP PI)

    Hi,
    I've set up an ABAP client proxy using the wizard in transaction SE80 in the backend system, released it using transaction SOAMANAGER and tested that it works.
    I now want to compare this technical approach against the same scenario using a proxy generated from a SAP PI outbound synchronous message interface.
    I have hit the following issues:
    1) When I upload the WSDL file (saved from the test web service I exposed from one of our SAP systems) into the Integration Repository, I receive the following error:
    "Check Result for Object GetDOB_WSDL Document check found errors  Cause: Unable to recognize the loaded document as valid WSDL  Tag Policy is not permitted at position portType".
    I can remove this error by deleting the tag policy but don't have an answer why this is not supported and whether this is the right approach - this error occurs regardless of which option I choose when saving the WSDL (i.e. portType or binding) or which upload option I select.
    2) When I create the proxy in the backend system based on the message interface the objects are all created successfully and generate/activate correctly.  As I don't need the PI runtime (no mapping, queuing etc) I go to create the logical port in transaction SOAMANAGER and I receive the error:
    SRT Framework exception: The WSDL document is not compatible with proxy class "ZPROXCO_ZFUNC_UPDATE_ADDRESSHI": "Operation(s) Missing ZFuncUpdateAddresshistory"
    even though the external operation does exist and is called ZFuncUpdateAddresshistory.
    I have no clues as to why this doesn't work other than the generated WSDL file in the ABAP client proxy has the same name for the portType and operation (ZFuncUpdateAddresshistory).
    3) Can someone please explain the value at design time over creating the client proxy in SAP PI versus using simply the wizard in the backend ABAP system - is it simply that the interfaces can be held centrally in the IR if desired or the WSDL might already be there and could be used to quickly generate a message interface?
    Thanks,
    Alan

    Hi,
      As far as I know, we follow the top down approach in proxy scenarios.
    meaning, we first create the interfaces in XI IR and then go to the back end to implement them.
    So, you should create a message interface (Probably Manually rather than importing the wsdl from R/3)
    in IR and then go to the ERP backend to implement the proxy using the SPROXY transaction.
    Coming to your 3rd question, In PI 7.1 you might be knowung that we have something called ESR(Enterprise Service Repository), which has all the services in a single place.This gives us an option of collating all the different enterprise services scattered all over different systems to be in a common repository.
    Regards,
    Ravi Kanth Talagana

  • PI 7.1 - Configuring a client proxy - not working.

    I am trying to send a Client proxy from ECC to XI.
    This is a new PI 7.1 install so I am trying to test a quick and easy client proxy from ECC to XI and cant even  get a message sent to XI.
    On ECC, I am getting a weird message in SXI_MONITOR
    I get a gray colored flag and when I hover over it, give me the following info:
    "Message recorded (Commit Missing)". 
    Has anyone encounter this type of status.
    Basically the message never send out to XI.  Also, the message does not let me restart or even cancel the message. 
    Overall, all the config looks good on ECC
    SLDCHECK looks good.
    In ECC, I configured the Integration engine config as an Application Server and pointed it to RFC destination that points to the XI server.
    -steve

    Hi,
    1) Queues are clean
    2) I have checked the RFC Destination for the HTTP connection.  It brings back a 500 empty response which is good.
    I did a check on the Integration Engine Config and it brings back a yellow status that "Corresponding Integration Server not Maintined" 
    I wasnt sure if this was an info message that really wasnt an error.....any thoughts?

  • How to find the error when client proxy is not successfully triggered?

    Hi all,
    I want to consume a .NET service in SAP.
    But when I want to test the client proxy the following error occur:
    GENERAL_ERROR Error duing proxy processing (PART
    UNKNOWN (NULL) )
    Transaction ST11:
    TRACE SOAP RUNTIME - trace records                                                                               
    E CONTEXT 20090518061404.5255720 : CL_SOAP_CONTEXT ->SET_FAULT   
    SOAP runtime fault handling                                                                               
    E SOAP_RUNTIME 20090518061404.5256990 : CL_SOAP_RUNTIME_CLIENT   
    ->EXEC_PROCESSING Exception handling in SOAP runtime                                                                               
    E CONTEXT 20090518061404.5255620 : CL_SOAP_CONTEXT ->SET_FAULT set
    fault loop detected                                                                               
    E SOAP_RUNTIME 20090518061404.5256920 : CL_SOAP_RUNTIME_CLIENT                                   
    .NullPointerException:                                           
    Transaction SM21:
    SOAP Runtime Protocol: SOAP Fault exception occurred in program CL_SOAP_RUNTIME_ROOT==========CP in include CL_SOAP_RU NTIME_ROOT==========CM004 at position 80
    SOAP Runtime Protocol: Exception message: Severe processing error; SOAP fault handling required
    How can I find what's wrong????
    This error logging is not really helpful to me...
    Any ideas?
    regards

    Hello Mr. Bauer,
    Will you please elaborate on your solution to fix this issue?
    We are facing this issue too.
    Thanks in advance.
    Regards,
    Victor

  • Client proxy message not reaching to XI system

    Hi
    I have done one scenario from CRM to FILE. When i am executing the client proxy through my zprogram its executing without any errors. I have checked in SXMB_MONI of CRD system i can see the messages but they are not with successful flag or not with error flag. But in XI system (SXMB_MONI) i didnt find any messages. Could you please tell me what's the problem is?
    Regards
    Sowmya

    Sowmya,
    As you are not getting any message in SXMB_MONI, there can be following possibilities:
    1. There can be some problem in proxy configuration on your CRM system. Please check with your BASIS team that steps give in this blog are properly followed:
    How do you activate ABAP Proxies? 
    2. Make sure that in
    SXMB_ADM     --->integration engine config -
    >change specific attributes....
    The RUNTIME parameter is defined LOGGING and TRACE_LEVEL and the value is 1.
    3. Make sure the queues are registered in Tx: SMQR.
    Further, I do not think that COMMIT statement or anything like that is missing as in that case you should have got a message in SXMB_MONI with a green flag stating that "Commit statement is missing".

  • ABAP Client Proxy to File (File is not getting generated)

    Hi All,
    I'm trying out a scenario ABAP proxy --> XI  --> FILE.
    I have followed the given blog to create ABAP client proxy.
    /people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
    While executing the ABAP client proxy, the values are properly sent to XI and in the SXMB_MONI the message shows as successful. But the correspoding file is not created.
    It seems everything is fine in the receiver adpater(Monitoring) and in the SXMB_MONI also the msg shows successful(receiver side).
    The directory path and the corresping file creation parameters also looks fine.
    Couldn't figure out what went wrong. Please help me on this.
    Thanks,
    Ajay.

    Hi Smitha,
        Please find below the Call Adapter trace
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <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 =</Trace>
      <Trace level="1" type="T">Sender agency external =</Trace>
      <Trace level="1" type="T">Sender party external =</Trace>
      <Trace level="1" type="T">Sender 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.0</Trace>
      <Trace level="2" type="T">Host = iscsapapp4w:8010</Trace>
      <Trace level="2" type="T">Server protocol = HTTP/1.0</Trace>
      <Trace level="2" type="T">Remote address = 10.191.117.166</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 = NW2</Trace>
      <Trace level="3" type="T">client = 100</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = XIAPPLUSER</Trace>
      <Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET</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 = B2DD6D78BBF141458DDC0DDE39782DE3</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 = B2DD6D78BBF141458DDC0DDE39782DE3</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 : XBTI0000</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTI0000</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 = B2DD6D78BBF141458DDC0DDE39782DE3</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 = NW2</Trace>
      <Trace level="3" type="T">client = 100</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = XIAPPLUSER</Trace>
      <Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET</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-04-03T10:24:14Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
      <Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET 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">Check conditions for rule line no. 1</Trace>
      <Trace level="2" type="T">...valid Receiver w/o Condition: - ACN_LEGACY2_04_BS</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-04-03T10:24:14Z CET 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-04-03T10:24:14Z CET 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) ACN_LEGACY2_04_BS MI_Client_Proxy_Inbound</Trace>
      <Trace level="2" type="T">...valid InbIf without Condition: MI_Client_Proxy_Inbound</Trace>
      <Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET 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-04-03T10:24:14Z CET 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 = XBTOM2__0001</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 = NW2</Trace>
      <Trace level="3" type="T">client = 100</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = XIAPPLUSER</Trace>
      <Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET</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-04-03T10:24:14Z CET 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-04-03T10:24:14Z CET 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 is already determined in the interface determination</Trace>
      <Trace level="3" type="T">Object ID of Interface Mapping 791955998E03380CA938A0130A348AFB</Trace>
      <Trace level="3" type="T">Version ID of Interface Mapping 3475AE80930811DAA18DC14C0ABF75A6</Trace>
      <Trace level="1" type="T">Interface Mapping http://accenture.com/xi101/ABAPclientProxy IM_Valuemapping</Trace>
      <Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_MM_Valuemapping_</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_Valuemapping_.</Trace>
      <Trace level="3" type="T">Load 3475ae80-9308-11da-a18d-c14c0abf75a6, http://accenture.com/xi101/ABAPclientProxy, -1, com/sap/xi/tf/_MM_Valuemapping_.class.</Trace>
      <Trace level="3" type="T">Search com/sap/xi/tf/_MM_Valuemapping_.class (http://accenture.com/xi101/ABAPclientProxy, -1) in swcv 3475ae80-9308-11da-a18d-c14c0abf75a6.</Trace>
      <Trace level="3" type="T">Loaded class com.sap.xi.tf._MM_Valuemapping_</Trace>
      <Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_Valuemapping_</Trace>
      <Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_Valuemapping_ completed. (executeStep() of com.sap.xi.tf._MM_Valuemapping_</Trace>
      <Trace level="3" type="T">Dynamic configuration is empty</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2006-04-03T10:24:15Z CET 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-04-03T10:24:15Z CET 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">-ACN_Sender_BS_XI</Trace>
      <Trace level="2" type="T">-ACN_LEGACY2_04_BS</Trace>
      <Trace level="2" type="T">http://accenture.com/xi101/ABAPclientProxy.MI_Client_Proxy_Inbound</Trace>
      <Trace level="2" type="T">Channel found: - ACN_LEGACY2_04_BS - ValueMap_Repl_Receiver1</Trace>
      <Trace level="2" type="T">no header mapping defined</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2006-04-03T10:24:15Z CET 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-04-03T10:24:15Z CET 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): af.nw2.iscsapapp4w</Trace>
      <Trace level="3" type="T">URL = http://iscsapapp4w.idcsap.com:51000/MessagingSystem/receive/AFW/XI</Trace>
      <Trace level="3" type="T">User = XIISUSER</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-04-03T10:24:19Z CET 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>
      </SAP:Trace>
    Thanks,
    Jothivel.

  • Scenario:client proxy

    Dear experts,
    -here my scenario is client proxy(file to file)
    -Error is internal error
               http_resp_status_code_not_ok
    -when we check it in sxmb_moni sysyem cannot identify the receiver business system and receiver message ineterface
    -how to solve this problem.
    plz help me
    regards
    somesh

    Hi,
    1.Go to SM59 -
    > INTEGARTION_DIRECTORY_HMI -
    > Connection Test.
    You should not get any error! If you get an error the consult with your basis team.
    2.The server encountered an unexpected condition which prevented it from fulfilling the request.
    Check whether you have given the right credentialsand also check the conditions which you have given whether any condition is false... If you are very sure that you have given right credentials then your problem will be solved by restarting J2EE engine
    steps to restart J2EE engine
    1) run transaction SMICM
    2) then in the tab administration => J2EE instance(local) =>send soft shutdown with restart
    by this java engine will restart and will be up in 5-10 minutes and your problem will be solved
    for more details on error code follow the link
    http://www.web-cache.com/Writings/http-status-codes.html
    http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
    http://www.helpwithpcs.com/courses/html/html_http_status_codes.htm
    3) Check Pipeline URL-
    should be
    http://<hostname>:<port>/sap/xi/engine?type=entry
    and not type=execute.
    Need to check this value in your SLD> Business system> <yourIntegrationServer> --> Pipeline URL
    4) Go to SM59 and check the Http destination -test connection-
    Also check this blog-
    /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
    For timeout check this-
    /people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
    Please reward points if it helps
    Thanks
    Vikranth

  • Client proxy Http connection

    Hi experts,
    When doing abap client proxy.. in receiver channel i speficied XI adapter.. its asking the Http destination... so i went sm59 tcode and trying to create Http connection.. what are the parameter i should give...
    Connection type is "H"
    in the host name what should i give host name of PI or R3.. and what is the service number how to find out the service no? what should be the prefix string. what is need of this? .. in logon & security tab.. In user name and password , do we give the values of R3 system or PI system...
    Actually i gave the values like
    , in Host ---> i gave the Hostname of PI system and service no as 8000
    in prefix string --- > i gave '/sap/xi/engine?type=entry'
    (but i got the error like 'Query string not allowed')
    Please guide me
    Regards,
    Balaji

    Hi abhishek,
    There is no destination for r3 in type "H".
    i want to create the HTTP connection to r3. so i gave the hostname of R3 system.. the system instance is '00'' so i gave the service name as 8000... i gave the user name , password of r3.
    other setting are
    Logon procedure---> SAP standard
    status secure protocol-----> 
                  SSL--> Active
    SSL client certificate---> Default SSL client (standard)
    I dint give the single course  i gave /sap/xi/engine?type=entry only. But still he saying "Query string is not allowed".
    Regards,
    Balaji
    Edited by: Balaji Pichaimuthu on Aug 1, 2009 12:24 PM

  • Client Proxy Error in UAT System

    Hi,
    I am having a Client Proxy - PI - File Scenario.
    The Client proxy is working perfect in Development and Test system, but its raising exception "CX_AI_SYSTEM_FAULT" in UAT system.
    Please advice. Is there any setting/configuration missing.
    Thanks,
    Navneeth K.

    Please refer this wiki
    http://wiki.sdn.sap.com/wiki/display/Snippets/HowtohandleCX_AI_SYSTEM_FAULTin+RFC

  • Web service - Client Proxy - SOAP error

    Hi All,
    I created a custom web service/port and Client proxy.
    While I test the Client proxy with Logical port via SE80, I am getting error message related to SOAP.
    Error text:
    SOAP:14 Unexpected element -el=definitions ns=http://schemas.xmlsoap.org/wsdl/
    Error when processing Web service call
    Error when calling SOAP Runtime functions: Unexpected element -el=definitions ns=http://schemas.xmlsoap.org/wsdl/
    Am I missing any configuration?
    THanks,
    Chirag

    Hi,
    I got the same error with using the configuration tool LPCONFIG after implementing -> with SOAMANAGER everything worked allright directly just create a port with that tool.
    Maybe tha will help you also - for your problem.
    Regards,
    Jeroen Cosijnse

  • Testing a Client Proxy - mustUnderstand=1, is not recognized

    Hello,
    I developed an Application Service in NWDS and tested it in the WebService Navigator.
    It worked fine u2026
    Now I want to call this WebService in ABAP. So I created a Client Proxy (SE80) with the corresponding WSDL and set up a logical port (with the same WSDL).
    While testing this Client Proxy an error occurred:
    SoapFaultCode: 1
    Through the transaction se11 I got the following infos:
    E SOAP_RUNTIME 20100914152300.8430000 : CL_SOAP_RUNTIME_CLIENT
    ->EXEC_PROCESSING Ausnahmebehandlung innerhalb der SOAP Laufzeit
    E HTTP_TRANSPORT_BINDING 20100914152300.7340000 : CL_SOAP_HTTP
    _TPBND_ROOT ->HANDLE_STATUS_CODE Received return code 500 (
    Internal Server Error )
    E SOAP_RUNTIME 20100914152300.8430000 : CL_SOAP_RUNTIME_CLIENT
    ->EXEC_PROCESSING SOAP Fault Exception caught: : Header element
    [http://schemas.xmlsoap.org/ws/2004/08/addressing]To, marked with
    mustUnderstand=1, is not recognized.
    Can anybody give me a hint how to solve this problem?
    Best regards
    Tim

    Can you goto Logical port and suppress message Id transfer.
    You can find it under tab "Messaging"->"Message Id Protocol" = suppress id transfer and then test.
    For troubleshooting please test RFC destination in SM59, you can find name of HTTP destination in "Additional Settings" tab if it is working.
    Regards,
    Gourav

Maybe you are looking for

  • Disk utility won't MOUNT .iso images to disk?

    For some reason Disk Utility started only showing a "to erase a rewritable cd or dvd so you can write it again" screen when i click on my dvd drive. I am trying to Mount a .iso file to a disk, It will let me "burn" the files to a disk, but that does

  • Using Profile to limit resource access

    Hello, I'm trying to use the profile feature to limit access for specific users the featue I want to limit is: CPU_PER_CALL defined as follow: Limits the amount of CPU time that can be consumed by any single database call in any session established b

  • Exchange Server 2010 Public Folder Error!

    I found that no one can sent email to our mail-enable public folder. there's a warning like below Delivery has failed to these recipients or groups: ([email protected]) <[email protected]> There's a problem with the recipient's mailbox. Please try re

  • Is there a Pages template for a family tree

    Trying to find a way to present an eight generation family tree.  Any ideas?

  • HT4972 How to back up ipad

    I have an ipad2 and don't know how to access the cloud nor update my operating system. There is no software update in my general settings. how do I back up my iPad ?