File -- XI -- Abap proxy Que lock

Hi all,
My scenario is file --> XI --> Abap proxy, for some strange reason the message always gets locked on R3 side. So, in the monitor of XI the message is processed succesful BUT in the monitor of R3 we always have to unlock (que) the message manually before he executes the proxy. Isn't there a way that we don't have to unlock the message manually before executing the proxy?
TIA

Have you registered and activated the queues?
Transaction sxmb_adm -> Integration Engine-> Administration -> Manage Queues.
Cheers
Manish

Similar Messages

  • File to ABAP Proxy (problem with inbound queues in R3)

    Hi,
    In File-XI-ABAP proxy scenario, XI is successfully picking up file and sending it to R3.
    But in R3, an inbound queue is created in SMQ2 transaction code and I solved the same to automatically process the Queue by registering that in SMQR transaction code. But even though the inbound queue doesn't appear in SMQ2 (which means that it is processed successfully) it doesn't call the method EXECUTE_ASYNCHRONOUS. Can anyone help me whether I need to do any settings to run that method?
    Also can anyone help me, after the inbound queue is successfully processed in SMQ2 transaction, what would be the next step to watch what exactly that queue has done?

    Hi,
    Please check the program code for Server ABAP proxy.
    This will show you the trigerring of Proxy on inbound side.
    ABAP Proxy inbound program - sales order creation - Community Profiles - Wiki
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/abap%2bproxy%2binbound%2bprogram%2b-%2bsales%2border%2bcreation
    For Queues, you can go to SMQR and check for the register queue. Select and double click on it. If anything is stuck up then you can see in it. Even same with SMQ2
    Thanks
    swarup

  • File to ABAP Proxy(ProductActivityNotification_In)

    Hi All
    I have to develop one scenario for Flat File to ABAP Proxy (ProductActivityNotification_In).
    I am going to use Receiver File Adapter(to receive file in PI) and Reiver XI adapter(to send file to SNC proxy ProductActivityNotification_In)
    I am new to XI please let me know how to approach to this solution.
    What could be the design steps I need to consider?
    Do I Need to use content conversion?
    Can I use graphical mapping?
    Thanks for your inputs.
    Regards
    Amol.

    Hey,
    You need to import the SNC standard content in XI.
    This will provide you with the Proxy interface.
    Then you need to do certain settings on the SNC server.
    R3 side
    SLDCHECK
      Use this transaction to access the SLD of XI.
    SLDAPICUST
      Create an entry for respective XI server
      requires hostname, port username and ip.
      Can have multiple enteries for different servers.
      But you can check only one entry.
      based on the entry that is checked, respective SLD API will be triggered from
      SLDCHECK.
    SM59 (T type connections).
      To connect to the SLD you need 2 types of TCP/IP connections.
      1)LCRSAPRFC:-
          In this you require the gateway host(ip address) and gatewayservice(sapgw[system no.])
          YOu also need to give Program ID.
          Entry of corresponding Program ID must be maintained in SMGW.
          IN SMGW Click GoTo->logged on Clients.
          If entry is not there for corresponding XI.
          Create a communication channel in XI, pointing to R3 and give a Program ID
          in the channel. Once the channel is activated, corresponding Program ID wil
          appear in SMGW.
      2)SAPSLDAPI:-
         In this case follow the same porcedure as for LCRSAPRFC.
       As far as the Program ID is concerned te procedure mentioned above is for
       Customized RFC's
       The RFC destinations mentioned here are both standard RFC's
       Hence for these two RFC's no need to Create Program ID's. you just need to
       change the System ID of the Program ID.
       Both these RFC's are maintained in the J2ee server of XI.
    SPROXY.
       In this transcation you can check the Proxies.
       If the proxies are not activated (i.e. if the message interfaces are not active)
       then you need to maintain one G type RFC destination pointing the resepctive XI server.
       In the G tpye RFC destination give the Ip adress of the XI server in the target
       host and set the path prefix as /rep.
       Goto SPROXY->Goto->connection test-> click on the table SPROXSET.
       In this table maintain enteries for ADDRESS_ONLY_FROM_SPROXSET and IFR_HTTP_DEST
       The values corresponding to these enteries will be the G tpye RFC destination.
    In order to connect R3 to the Integaration server you need to maintain H type
    The default RFC is XI_INTEGRATIONSERVER. In you need to give the Target host entry as the
    Ip address and Path Prefic as.../sap/XI/engine/?type=entry (this you can get from SXMB_ADM of XI)
    You can also create the H type RFc of your own.
    goto SXMB_ADM(r3) and open Integration engine configuration.
    Goto edit->change global configuration and give the RFC dest name like this:-
    Corresponding Integration server:- dest://{h-type rfc destination}
    If you do not want to create RFC destination you can directly give
    the Integration server address(that you can obtain from SXMB_ADM of XI) in the
    Corresponding Integration server field.
    This is to activate the communication between SNC and PI.
    now you need to create the file structure in XI.
    the next step is to do the mapping between the file structure and the appropriate interface
    As yours is a flat file you need to do a file content conversion
    In Integration directory you need to configure two channels one for File and the other one for Proxy.
    regards,
      Milan

  • File to ABAP proxy with EOIO

    Hi Experts,
    I am working on File to ABAP proxy scenario. The requirement is to have EOIO from end to end.
    Which means the files have to be sent to target system (R/3) in the same order as they are placed in the file location. I have two questions regarding this.
    1. Do I have to create 2 queues, one in PI and one in R/3 to acheive this? In File Sender CC we have option of specifying queue name but in XI Receiver CC, I do not see such option. How to handle this?
    2.For picking the files from folder if I use NFS, then I have option of specifying 'Processing Sequence' as 'By Date' to pick the files based on timestamp. But if I am using FTP, how can I make sure that the files are sent to Integration engine based on timestamp?
    Please provide your valuable inputs.
    Thanks and regards,
    Prasad

    Hi,
    1. Do I have to create 2 queues, one in PI and one in R/3 to acheive this? In File Sender CC we have option of specifying queue name but in XI Receiver CC, I do not see such option. How to handle this?
    1 queue is okay. Just specify it in the Sender File CC.
    2.For picking the files from folder if I use NFS, then I have option of specifying 'Processing Sequence' as 'By Date' to pick the files based on timestamp. But if I am using FTP, how can I make sure that the files are sent to Integration engine based on timestamp?
    Processing Sequence is not supported for FTP and is only for NFS.
    If you have to use processing sequence, then do an FTP, bring the files to an NFS directory and then use the processing sequence accordingly.
    Hope this helps.
    Regards,
    Neetesh

  • File to ABAP proxy via AAE

    Hi All
    Am doing a file to ABAP proxy scenario and using SOAP adapter(XI protocol 3.0) at target side in order to make use of AAE.
    But while testing am getting the following error at both the channels(file and soap) :
    Error Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection timed out.
    SOAP channel configuration :
    Target URL : http://X.X.X.X:8001/sap/xi/engine?type=entry
    Logon language : en
    X.X.X.X  being the IP address of the target system which is BW.
    Appreciate any help.
    Regards
    Soumen

    Re-Iterating my 1st post : Am using SOAP( Message Protocol : XI 3.0 ) as I want to make use of the AAE. XI adapter is not supported by AAE.
    Followed this : http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70066f78-7794-2c10-2e8c-cb967cef407b?quicklink=index&overridelayout=true
    Anyways, found out I was having some error in teh IP I was using ...corrected it and now my error is changed to :
    Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 403 Forbidden
    Now since my source is File which goes through mapping, what do I need to do for this error?

  • File to ABAP Proxy Scenario

    Hi All,
    I am  doing File-to-ABAP Proxy Scenario, in the sender side side it is picking the file, but in sxmb_moni it is giving the error:
      *<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>*
    *- <!--  Call Adapter*
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIProtocol</SAP:Category>
      <SAP:Code area="MESSAGE">DUPLICATE_DETECTED</SAP:Code>
      <SAP:P1>4CFF4691EEE211DC85E30019D1522982</SAP:P1>
      <SAP:P2>CENTRAL</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Message ID 4CFF4691EEE211DC85E30019D1522982 already exists in called system (pipeline CENTRAL)</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    Can u plz tell me why this error is occurring and how we can resolve this error.
    Thanks & Regards,
    Vikas

    Hi Vikas
    make a dummy change and activate your object then make a full refresh
    you can make it through in 3 ways
    1) tcode SXI_CACHE
    2) go to ID -> environment and make a full cache refresh
    3) http://<host>:5<sys#>00/CPACache/refresh?mode=full     Full CPA cache refresh
    when you do the developement then these are stored in ABAP data dictionary table which can be refreshed by delta cache
    while full cache will delete this temporary object and make this cahe into runtime
    hope this will help you
    thanks
    sandeep
    if helpful reward points

  • SAP XI- File to ABAP Proxy scenario

    Hi SDN,
    I have a FILE to ABAP proxy scenarioin SAP+XI can you guide me how to procede in that, what should be my ESR and ID objects and how to use the sproxy transaction.
    Regards,
    Aniruddha Bhattacharya

    Hi,
    please check out the search option on SDN forum first - there are tons of blogs with step by step on the same
    come back with more detailed questions ok ?
    thank you,
    Regards,
    Michal Krawczyk

  • BPM file to ABAP proxy

    HI all
    I´m developing a BPM, this has the following steps:
    1º
    Reciver Step: this is to read a file , comunication channel type file.
    2º transformation Step: maps the MT of the file to a new MT
    3º Send step: send syncronously the result of the the map.Using an ABAP proxy. XI adapter.
    4ºSwitch step: compares de the value of the result of the syncronous call, with a constant.First branch Send Step to write a file
    Second branch nothing.
    My question is? Do i have to insert something before the switch. Because i cannot activate the BPM, In the SXI_CACHE i can see and error that says that the value that i´m using to compare the value it is not an object of the payload.
    Any idea?
    Many thanks
    Noelia

    Hi,
    Last try...
    salida_proxy./p1:MT_salidaproxy/row/valor = 0
    In the condition editor:
    When you do a f4 for the left operanfd text box:
    The expression editor opens:
    You need to click on the "Interface Variable" radio button and select your container salida_proxy and prove the correct xpath.
    Make sure that the Type specified next to the xpath in the expression editor is String.
    A f4 in the right operand text box opens a expression ediote, where:
    You need to click on the constant radio button, and provide the constant 0.
    Again make sure that the xsd trype is String.
    In case all this has been done perfectly, then try deleting the switch and recreating it again. You never know, this might do the trick!
    Regards,
    Smitha.
    Message was edited by:
            Smitha Rao

  • File to Abap Proxy Scenario : No message log in SXMB_MONI

    I have a PI Scenario in which a FTP server is polled every 5 minutes, and when it receives any file,  file is archieved and abap proxy is called. Few days back it was running perfectly fine. But For last couple of days I am facing strange error.
    My File is archived but abap proxy isnot called, neither I get any message in SXMB_MONI.
    any guesses what should I do?
    Jawed Ali

    Hi Jawed,
    HOLD means you have given QoS as EOIO in sender channel and the first message got failed and hence all messages are waiting..
    Check this thread
    Re: PI 7.1 Messages stuck into the Queue of the Adapter Engine
    Try resending the messages through runtime workbench->message monitoring->adapter engine
    Regards
    Suraj

  • File to ABAP proxy as attachment

    Hello PI expert,
    I have requirement to FTP file from FTP server to ECC server.  But because of some security, we can not get FTP permission on ECC server.
    What i want to do is, get the file from FTP server as it is, and send it using abap proxy as attachment. I don't want to do any content conversion or xml conversion because I want to transfer file as it is.
    Any suggestion.
    Thanks,

    Hi,
    if your PI version is at least "SAP NetWeaver PI 7.1 SP3"
    create sample Data type structure with one node and one field, and use this for both proxy and file service/message interfaces.
    Pick the file from FTP. No graphical mapping. Use Java Mapping. Read the input stream and create an attachement from this and attach it to the message. pass some static values for the output (proxy) structure using output stream. Thats all.
    http://help.sap.com/javadocs/pi/SP3/xpi/index.html
    Methods:-
    com.sap.aii.mapping.api --> OutputAttachments --> create(String contentId, byte[] content) / create(String contentId, String contentType, byte[] content)

  • Performance problem in File to ABAP Proxy scenario

    Hi gurus,
        I have a scenario where the sender is sending a file and the receiver is ABAP Proxy.The file is a simple DAT file containing banking data.The file sample is as belo
    00000MM21901 PYM0901021531     
    704401020100005510000040000D0002
    704401020127147391000033500D0003
    704401020127147391000045000D0004
    704401020109341157000038800D0005
    70420!!!!10200000182174D
    704401021100006040000015158D0001
    704401021100006040000005034D0002
    7042010210000020192D
    The above file need to be split and mapped to the fields of the ABAP Proxy after doing some validations.
    Is Receiver Determination using mapping required? What is the most efficient way of splitting the file?
    Please give your replies keeping better performance of the interface in mind.What is the best way of doing the validations?
    regards
    Debansu

    Hi Satish,
        As you can see in my question above,the sender side contains a flat file(the file format is given in the question),I need to split the file into strings which can then be mapped to specific fields of the ABAP Proxy.A sample output of the xml file that is passed on to the ABAP proxy after mapping transformations is given below:
    <BATCH_TOTAL_RECORD_420>
      <BATCH_REPORT_DISTRICT>70</BATCH_REPORT_DISTRICT>
      <KEY_VALUE>420</KEY_VALUE>
      <BATCH_NUMBER>1021</BATCH_NUMBER>
      <BATCH_TOTAL>0000020192</BATCH_TOTAL>
      <FILLER_BATCH_TOTAL_SIGN>D</FILLER_BATCH_TOTAL_SIGN>
      <FILLER />
      </BATCH_TOTAL_RECORD_420>
    - <BATCH_TOTAL_RECORD_420>
      <BATCH_REPORT_DISTRICT>70</BATCH_REPORT_DISTRICT>
      <KEY_VALUE>420</KEY_VALUE>
      <BATCH_NUMBER>9999</BATCH_NUMBER>
      <BATCH_TOTAL>0000202366</BATCH_TOTAL>
      <FILLER_BATCH_TOTAL_SIGN>D</FILLER_BATCH_TOTAL_SIGN>
      <FILLER />
      </BATCH_TOTAL_RECORD_420>
    I hope now you can provide me some answers.
    Regards
    Debansu

  • File to custom IDOC  or File to abap proxy

    Hi there,
    I would like to know best approach for the following scenario.
    1) i have file coming from legacy system
    2) On target side SAP , I have BAPI's available  (Create, Save, Commit )(No standard IDOC available)
    I can create Custom IDOC and call those BAPI's in Custom Function Module
    or
    I can use ABAP proxy and call BAPI's
    What is the best way of doing this? and Is there any other way?
    Thanks
    Kumar

    hi,
    Abap Proxy is better than RFC in terms of performance.
    proxy is that it always by passes the Adapter Engine and will directly interact with the application system and Integration engine - so it will and should give us a better performance.
    In your case , if there want to crate idoc from scratch level then we go for proxy  and proxy support large volume of data (more than 5 mb).
    One more  reason is RFC , the data is converted between RFC and XML in RFC adapter. In proxy XI communicates with the R/3 in native XI language (SOAP XML).

  • FILE TO ABAP PROXY

    Please help me. 
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Adapter Call (Integration Engine, Idoc, RFC)
      -->
    - <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SOAP:Header>
    - <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
      <SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
      <SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
      <SAP:MessageId>BDC54350-4589-11DC-C86A-00145ED17196</SAP:MessageId>
      <SAP:TimeSent>2007-08-08T08:31:21Z</SAP:TimeSent>
    - <SAP:Sender>
      <SAP:Service>DCM</SAP:Service>
      <SAP:Interface namespace="http://northstar.co.kr/filetoproxy">MI_file2proxy</SAP:Interface>
      </SAP:Sender>
    - <SAP:Receiver>
      <SAP:Party agency="" scheme="" />
      <SAP:Service>DWP300</SAP:Service>
      <SAP:Interface namespace="http://northstar.co.kr/filetoproxy">MI_file2proxy_receiver</SAP:Interface>
    - <SAP:Mapping notRequired="M">
      <SAP:ObjectId>EvqSYdM2Oj+vPpOBdlZyow==</SAP:ObjectId>
      <SAP:SWCV>j7PEAD8NEdyWPv/FCgEUJA==</SAP:SWCV>
      <SAP:SP>-1</SAP:SP>
      </SAP:Mapping>
      </SAP:Receiver>
      <SAP:Interface namespace="http://northstar.co.kr/filetoproxy">MI_file2proxy_receiver</SAP:Interface>
      </SAP:Main>
    - <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
      </SAP:ReliableMessaging>
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIProtocol</SAP:Category>
      <SAP:Code area="MESSAGE">DUPLICATE_DETECTED</SAP:Code>
      <SAP:P1>BDC54350458911DCC86A00145ED17196</SAP:P1>
      <SAP:P2>CENTRAL</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Message-Id BDC54350458911DCC86A00145ED17196 ist im gerufenen System bereits vorhanden (Pipeline CENTRAL)</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    - <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
    - <SAP:Hop timeStamp="2007-08-08T08:31:21Z" wasRead="false">
      <SAP:Engine type="BB" />
      <SAP:Adapter namespace="" />
      <SAP:MessageId>BDC54350-4589-11DC-C86A-00145ED17196</SAP:MessageId>
      <SAP:Info />
      </SAP:Hop>
      </SAP:HopList>
    - <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Date>20070808</SAP:Date>
      <SAP:Time>173121</SAP:Time>
      <SAP:Host>dwxidev</SAP:Host>
      <SAP:SystemId>DXD</SAP:SystemId>
      <SAP:SystemNr>01</SAP:SystemNr>
      <SAP:OS>AIX</SAP:OS>
      <SAP:DB>ORACLE</SAP:DB>
      <SAP:Language />
      <SAP:ProcStatus>020</SAP:ProcStatus>
      <SAP:AdapterStatus>000</SAP:AdapterStatus>
      <SAP:User>PIAFUSER</SAP:User>
      <SAP:TraceLevel>3</SAP:TraceLevel>
      <SAP:Logging>1</SAP:Logging>
      <SAP:LogSeqNbr>008</SAP:LogSeqNbr>
      <SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
      <SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
      <SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
      <SAP:PipelineElementId>60C3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
      <SAP:PipelineStartElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineStartElementId>
      <SAP:PipelineService>PLSRV_CALL_ADAPTER</SAP:PipelineService>
      <SAP:QIdInternal>XBTO2___0002</SAP:QIdInternal>
      <SAP:CommitActor>X</SAP:CommitActor>
      <SAP:SplitNumber>0</SAP:SplitNumber>
      <SAP:NumberOfRetries>0</SAP:NumberOfRetries>
      <SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
      <SAP:TypeOfEngine client="500">CENTRAL</SAP:TypeOfEngine>
      <SAP:PlsrvExceptionCode />
      <SAP:EOReferenceRuntime type="TID">0A011424404546B97F590F81</SAP:EOReferenceRuntime>
      <SAP:EOReferenceInbound type="TID" />
      <SAP:EOReferenceOutbound type="TID" />
      <SAP:MessageSizePayload>158</SAP:MessageSizePayload>
      <SAP:MessageSizeTotal>2601</SAP:MessageSizeTotal>
      <SAP:PayloadSizeRequest>158</SAP:PayloadSizeRequest>
      <SAP:PayloadSizeRequestMap>148</SAP:PayloadSizeRequestMap>
      <SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
      <SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
      <SAP:Reorganization>INI</SAP:Reorganization>
      <SAP:AdapterInbound>AENGINE</SAP:AdapterInbound>
      <SAP:AdapterOutbound>IENGINE</SAP:AdapterOutbound>
      <SAP:InterfaceAction>DEL</SAP:InterfaceAction>
      <SAP:RandomNumber>38</SAP:RandomNumber>
      <SAP:AckStatus>000</SAP:AckStatus>
      <SAP:SkipReceiverDetermination />
      <SAP:Sender_Agreement_GUID>4C52CAEEFC3A3C7196F446FBC0A1DF56</SAP:Sender_Agreement_GUID>
      <SAP:Receiver_Agreement_GUID>4B83BC0307A03704BDFB279AA19216EA</SAP:Receiver_Agreement_GUID>
      <SAP:Serialize_Children>X</SAP:Serialize_Children>
      </SAP:RunTime>
    - <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:RunTimeItem>
      <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
      <SAP:Timestamp type="begin" host="dwxidev">20070808083121.426832</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
      <SAP:Timestamp type="end" host="dwxidev">20070808083121.438161</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="begin" host="dwxidev">20070808083121.438517</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="end" host="dwxidev">20070808083121.444991</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
      <SAP:Timestamp type="begin" host="dwxidev">20070808083121.445001</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
      <SAP:Timestamp type="end" host="dwxidev">20070808083121.628032</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="dwxidev">20070808083121.63016</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="dwxidev">20070808083121.633311</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="dwxidev">20070808083121.639573</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="dwxidev">20070808083121.641732</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="begin" host="dwxidev">20070808083121.647566</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="end" host="dwxidev">20070808083121.707874</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
      <SAP:Timestamp type="begin" host="dwxidev">20070808083121.707885</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
      <SAP:Timestamp type="end" host="dwxidev">20070808083121.865461</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
      <SAP:Timestamp type="begin" host="dwxidev">20070808083121.867649</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
      <SAP:Timestamp type="end" host="dwxidev">20070808083121.919723</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
      <SAP:Timestamp type="begin" host="dwxidev">20070808083121.926969</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
      <SAP:Timestamp type="end" host="dwxidev">20070808083121.930027</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
      <SAP:Timestamp type="begin" host="dwxidev">20070808083121.937628</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">HTTP_SEND</SAP:Name>
      <SAP:Timestamp type="begin" host="dwxidev">20070808083121.944421</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">HTTP_SEND</SAP:Name>
      <SAP:Timestamp type="end" host="dwxidev">20070808083122.025902</SAP:Timestamp>
      </SAP:RunTimeItem>
      </SAP:PerformanceHeader>
    - <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:TraceLevel>Information</SAP:TraceLevel>
      <SAP:Logging>Off</SAP:Logging>
      </SAP:Diagnostic>
    - <SAP:OutboundBinding xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    - <SAP:OutboundBindingEntry version="30">
      <SAP:OutboundBindingObjectId>4B83BC0307A03704BDFB279AA19216EA</SAP:OutboundBindingObjectId>
      <SAP:FromPartyName />
      <SAP:FromServiceName>DCM</SAP:FromServiceName>
      <SAP:ToPartyName />
      <SAP:ToServiceName>DWP300</SAP:ToServiceName>
      <SAP:ToInterfaceName>MI_file2proxy_receiver</SAP:ToInterfaceName>
      <SAP:ToInterfaceNamespace>http://northstar.co.kr/filetoproxy</SAP:ToInterfaceNamespace>
    - <SAP:OutboundBindingAttributes>
    - <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:Attribute>
      <SAP:Name>applyEncryptionAlias</SAP:Name>
      <SAP:Value />
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>applyEncryptionKeyStore</SAP:Name>
      <SAP:Value />
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>applyEncryptionSignatureAlias</SAP:Name>
      <SAP:Value />
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>applyEncryptionSignatureKeyStore</SAP:Name>
      <SAP:Value />
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>applySignatureAlias</SAP:Name>
      <SAP:Value />
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>applySignatureEncryptionAlias</SAP:Name>
      <SAP:Value />
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>applySignatureEncryptionKeyStore</SAP:Name>
      <SAP:Value />
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>applySignatureKeyStore</SAP:Name>
      <SAP:Value />
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>propagatePrincipal</SAP:Name>
      <SAP:Value>0</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>securityProfileSignAndEncrypt</SAP:Name>
      <SAP:Value>applySignatureHeaderAndManifestWithSameKey</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>wsse.namespace</SAP:Name>
      <SAP:Value>http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd</SAP:Value>
      </SAP:Attribute>
      </SAP:AdapterTypeData>
      </SAP:OutboundBindingAttributes>
    - <SAP:HeaderMapping>
      <SAP:FieldMapping xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      </SAP:HeaderMapping>
    - <SAP:ChannelEntry version="30">
      <SAP:PartyName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:ServiceName xmlns:SAP="http://sap.com/xi/XI/Message/30">DWP300</SAP:ServiceName>
      <SAP:ChannelName xmlns:SAP="http://sap.com/xi/XI/Message/30">DWP300_XI_Receiver</SAP:ChannelName>
      <SAP:AdapterName xmlns:SAP="http://sap.com/xi/XI/Message/30">XI</SAP:AdapterName>
      <SAP:AdapterNamespace xmlns:SAP="http://sap.com/xi/XI/Message/30">http://sap.com/xi/XI/System</SAP:AdapterNamespace>
      <SAP:AdapterSWCV xmlns:SAP="http://sap.com/xi/XI/Message/30">B38BCD00E47111D7AFACDE420A1145A5</SAP:AdapterSWCV>
      <SAP:AdapterEngineType xmlns:SAP="http://sap.com/xi/XI/Message/30">IS</SAP:AdapterEngineType>
      <SAP:AdapterEngineName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:MessageProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">XI</SAP:MessageProtocol>
      <SAP:MessageProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30">3.0</SAP:MessageProtocolVersion>
      <SAP:TransportProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">HTTP</SAP:TransportProtocol>
      <SAP:TransportProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30">1.0</SAP:TransportProtocolVersion>
      <SAP:ChannelDirection xmlns:SAP="http://sap.com/xi/XI/Message/30">O</SAP:ChannelDirection>
      <SAP:FromPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:FromPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:ToPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:ToPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
    - <SAP:ChannelAttributes xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:Attribute>
      <SAP:Name>SecurityProfile</SAP:Name>
      <SAP:Value>securityProfileWSSE</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>addressingMode</SAP:Name>
      <SAP:Value>url</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>authenticationModeBasicAnon</SAP:Name>
      <SAP:Value>basicSAP</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>host</SAP:Name>
      <SAP:Value>dwxidev.daewoong.co.kr</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>httpDestination</SAP:Name>
      <SAP:Value />
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>isMessageSecurity</SAP:Name>
      <SAP:Value>0</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>logonClient</SAP:Name>
      <SAP:Value>500</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>logonLanguage</SAP:Name>
      <SAP:Value>KO</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>logonPassword</SAP:Name>
      <SAP:Value isPassword="true" />
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>logonUser</SAP:Name>
      <SAP:Value>pisuper</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>passHopList</SAP:Name>
      <SAP:Value>0</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>path</SAP:Name>
      <SAP:Value>/sap/xi/engine?type=entry</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>port</SAP:Name>
      <SAP:Value>8001</SAP:Value>
      </SAP:Attribute>
      </SAP:AdapterTypeData>
      </SAP:ChannelAttributes>
      </SAP:ChannelEntry>
      </SAP:OutboundBindingEntry>
      </SAP:OutboundBinding>
    - <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 = dwxidev:8001</Trace>
      <Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
      <Trace level="2" type="T">Remote address = 10.1.20.36</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 = DXD</Trace>
      <Trace level="3" type="T">client = 500</Trace>
      <Trace level="3" type="T">language = 3</Trace>
      <Trace level="3" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2007-08-08T08:31:21Z 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 = BDC54350458911DCC86A00145ED17196</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 = BDC54350458911DCC86A00145ED17196</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 = BDC54350458911DCC86A00145ED17196</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="T">--start sender interface action determination</Trace>
      <Trace level="1" type="T">select interface MI_file2proxy*</Trace>
      <Trace level="1" type="T">select interface namespace http://northstar.co.kr/filetoproxy</Trace>
      <Trace level="1" type="T">no interface found</Trace>
      <Trace level="1" type="T">--start receiver interface action determination</Trace>
      <Trace level="1" type="T">Loop 0000000001</Trace>
      <Trace level="1" type="T">select interface *</Trace>
      <Trace level="1" type="T">select interface namespace</Trace>
      <Trace level="1" type="T">no interface found</Trace>
      <Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
      <Trace level="1" type="T">Hence set action to DEL</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 = DXD</Trace>
      <Trace level="3" type="T">client = 500</Trace>
      <Trace level="3" type="T">language = 3</Trace>
      <Trace level="3" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2007-08-08T08:31:21Z 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">2007-08-08T08:31:21Z UTC+9 Begin of pipeline processing PLSRVID = CENTRAL</Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
      <Trace level="1" type="Timestamp">2007-08-08T08:31:21Z 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: - DWP300</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">2007-08-08T08:31:21Z 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">2007-08-08T08:31:21Z 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) DWP300 MI_file2proxy_receiver</Trace>
      <Trace level="2" type="T">...valid InbIf without Condition: MI_file2proxy_receiver</Trace>
      <Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2007-08-08T08:31:21Z 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">2007-08-08T08:31:21Z 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 = XBTO2___0002</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 = DXD</Trace>
      <Trace level="3" type="T">client = 500</Trace>
      <Trace level="3" type="T">language = 3</Trace>
      <Trace level="3" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2007-08-08T08:31:21Z 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">2007-08-08T08:31:21Z 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">2007-08-08T08:31:21Z 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 12FA9261D3363A3FAF3E9381765672A3</Trace>
      <Trace level="3" type="T">Version ID of Interface Mapping 8FB3C4003F0D11DC963EFFC50A011424</Trace>
      <Trace level="1" type="T">Interface Mapping http://northstar.co.kr/filetoproxy IM_file2proxy</Trace>
      <Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_MM_file2proxy_</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_file2proxy_.</Trace>
      <Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_file2proxy_</Trace>
      <Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_file2proxy_ completed. (executeStep() of com.sap.xi.tf._MM_file2proxy_</Trace>
      <Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2007-08-08T08:31:21Z 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">2007-08-08T08:31:21Z 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">-DCM</Trace>
      <Trace level="2" type="T">-DWP300</Trace>
      <Trace level="2" type="T">http://northstar.co.kr/filetoproxy.MI_file2proxy_receiver</Trace>
      <Trace level="2" type="T">Channel found: - DWP300 - DWP300_XI_Receiver</Trace>
      <Trace level="2" type="T">no header mapping defined</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2007-08-08T08:31:21Z 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">2007-08-08T08:31:21Z 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">Channel for Integration Engine: XI</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 = IENGINE</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 Integration Engine: XI</Trace>
      <Trace level="1" type="T">Sender: Header mapped to</Trace>
      <Trace level="1" type="T">Party =</Trace>
      <Trace level="1" type="T">Agency =</Trace>
      <Trace level="1" type="T">Scheme =</Trace>
      <Trace level="1" type="T">Service = DCM</Trace>
      <Trace level="1" type="T">Receiver: Header mapped to</Trace>
      <Trace level="1" type="T">Party =</Trace>
      <Trace level="1" type="T">Agency =</Trace>
      <Trace level="1" type="T">Scheme =</Trace>
      <Trace level="1" type="T">Service = DWP300</Trace>
      <Trace level="1" type="T">Party denormalization: sender</Trace>
      <Trace level="1" type="T">Sender target scheme =</Trace>
      <Trace level="1" type="T">Sender target agency =</Trace>
      <Trace level="1" type="T">Sender party normalized =</Trace>
      <Trace level="1" type="T">Sender party external =</Trace>
      <Trace level="1" type="T">Party denormalization: receiver</Trace>
      <Trace level="1" type="T">Receiver target scheme =</Trace>
      <Trace level="1" type="T">Receiver target agency =</Trace>
      <Trace level="1" type="T">Receiver party normalized =</Trace>
      <Trace level="1" type="T">Receiver party external =</Trace>
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
      <Trace level="2" type="T">Addressing mode: url</Trace>
      <Trace level="3" type="T">Host = dwxidev.daewoong.co.kr</Trace>
      <Trace level="3" type="T">Port = 8001</Trace>
      <Trace level="3" type="T">Transport protocol = HTTP 1.0</Trace>
      <Trace level="3" type="T">Message protocol =</Trace>
      <Trace level="3" type="T">Path = /sap/xi/engine?type=entry</Trace>
      <Trace level="2" type="T">Auth mode: basicSAP</Trace>
      <Trace level="3" type="T">Conversion of language from char2 to char1 KO</Trace>
      <Trace level="3" type=

    Thanks. Yaghya Nana.
    I was try to access the following URL:
    http://dwxidev.daewoong.co.kr:8001/sap/xi/engine?type=entry
    I could see an xml page with messgae:
    EMPTY_HTTP_REQUEST_RECEIVED

  • XML File Sender to ABAP Proxy

    Hi Experts,
                    I have a scenario like File to ABAP Proxy. Input file is huge like 60 MB and it's a XML file. Currently, it's consuming large resources in both XI & R/3 system.
                     I would like to use the option of Recordsets per message using the File Content Conversion. As the Input file being the XML, how the parameters under the  File Content Conversion can be handled? Can you please throw some input on this?
    Thanks,
    Kumar.

    Hi Kumar,
         I guess u cannot use File Content Conversion for an input file which is in XML format. But if ur concern is to handle the large file then, u can go thru the following link which talks abt handling large files...
    <a href="/people/alessandro.guarneri/blog/2007/02/21/sap-xi-acting-as-a-huge-file-mover:///people/alessandro.guarneri/blog/2007/02/21/sap-xi-acting-as-a-huge-file-mover
    Regards,
    Akshay

  • Error Handling in Inbound ABAP Proxy with EOIO

    Hi,
    The scenario
    I have a File to ABAP Proxy scenario and since the requirement is that the messages have to be processed in a single queue in the SAP system (i.e. EOIO), the sender file channel was configured to be EOIO. This ensures that all messages that enters the SAP system are put in a single queue and then processed one after the other.
    The Issue
    Now if one of the messages that enter SAP system fails during the processing in the ABAP program, the queue gets stuck and all messages after that go into a scheduled state. And one has to manually clear the errored message in order to continue processing the other waiting messages.
    The Question
    I know this is a default behavior in an EOIO scenario, however is there any way in which if a message fails in the ABAP program then one can automatically push it out of the queue and keep processing the other messages after it ?
    Thanks
    Bharath

    As a general rule I only use EOIO when there is a possibility of dependancy between messages (message 1 must be first and finsihed before message 2 starts). Assuming your just moving the errored message asside, I would assume that EOIO should be just EO.
    Alternatively, change the ABAP proxy to handle the error and return a clean status. Exception handling (try/catch) should be used were ever dangerous code is being used.
    If alerting in the proxy end point is to much trouble - change your proxy to a sync scenario return the error to PI and fire alerts from there <- I think this should be avoided but it will work.
    The main point is the exception handling so that the proxy fails "gracefully".

Maybe you are looking for

  • Can you choose unlimited messaging package anymore for new contracts?

    hi, my verizon contract is up next month so i was planning which phone i want next... i was wondering if it's possible to do this though. right now i'm just on an unlimited text plan, no minutes. is there an option to do that still? i tried picking o

  • Can't play out to DV/tape

    Hi, recently splashed out on FCP and a new MacBook Pro after a year or so of FCE on an identically spec'd MacBook Pro. However, I'm having a problem when I try to save my work down to tape using FCP. I have a Sony DV machine as my output (recording t

  • The question about using LSMW to input data to IT2001.

    Dear all, My client have a system where employee make eform to absence so I have shcedule is uploading these absence data on IT2001. I have been created an LSMW for uploading absence data, I check all step these haven't any error but on the finish st

  • Finding files by searching folder location.

    Can I find photos by searching folder location, using Photoshop Elements 10?  I used to use that method frequently inversion 5, but don't see how to do it in version 10.  I am using Windows 7.

  • Installing Oracle 10g and error with DISPLAY value

    Hello, I am instaling Oracle 10g and when I run: . /runInstaller this error apear: Can't connect to X11 window server using :0.0 as the value of DISPLAY variable. how must I set de DISPLAY variable if I have instaling in a local system? Thanks