JDBC adapter in BE mode

Hi all,
Scenario: JDBC to RFC synchronous.
Rows are picked from DB and fed as input to RFC. On successful RFC response, one of the DB field(Status) has to be updated to 'P'(processed)
For this i have configured,
JDBC sender adapter in BE mode
RFC receiver adapter
When i execute the scenario,
JDBC sender adapter picks data from the DB,
Mapping to RFC structues happen propely
RFC is executed successfully and RFC response is mapped to JDBC receiver structure (we followed help.sap.com for creating JDBC response structure)
We find that the message has been successfully precessed in Adapter mointor but the status field in DB is not updated. When we see sxmb_moni, we find that the JDBC response structure is getting created as required.
My questions are :
1) <b>Can JDBC adapter be configured in BE mode..?</b>
2) Why is the adapter monitor showing no error when hte record is not being updated in the DB..?

Hi Siva,
This might be because you might have given someother value for the ACTION attribute. As you are trying to update a particlar field, this attribute value has to be set to UPDATE.
Check out the SAP documents on how the value of the ACTION attribute determines what kind of SQL query will be executed.
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
Also, check out these docuements for your receiver and sender JDBC adapters,
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
Hope this helps,
Regards,
Bhavesh

Similar Messages

  • Jdbc adapter error on confirmation message in message monitor (rwb)

    I have the scenario iDoc -> PI 7 - > jdbc (AS400 odbc driver).
    When I do INSERT statements, the data is stored in the Database and the RWB message monitoring shows status Successfull.
    However, for every insert, an other message shows up in the message monitoring with reversed Sender and Receiver (so it looks like a confirmation message is trying to find its way back to XI). This message first is is Status "Waiting", and after some time gets in Status "System Error".
    As I am not expecting any responses in my XI configuration (as I have no place to send them to), I want to stop these messages showing up in the Adapter Engine (as there will be many Error Status messages that are of no interest to me).
    How can I stop these messages, or what should I do in XI to process them (and dump them in my receiver determination). I have NO  BPM involved .

    Hi,
    For each open connection a entry is made j2ee stack.So when the it reaches to max and execption is thrown.
    In Jdbc adapter configuration -> advance mode -> Set -> Disconnect from the database after processing each message.
    Should solve the prob
    <b>Cheers,
    *RAJ*
    *REWARD POINTS IF FOUND USEFULL*</b>

  • Date/Time Format Stored Procedure Calls in ADVANCE MODE in JDBC ADAPTER

    Hi Experts,
    What is significance of Date/Time Format Stored Procedure Calls in ADVANCE MODE in JDBC ADAPTER.
    Thanks,
    ABDUR

    I guess this would be applicable for the folowing formats - DATE, TIME, TIMESTAMP.
    This is the correct link
    http://help.sap.com/saphelp_nw04/helpdata/en/64/ce4e886334ec4ea7c2712e11cc567c/content.htm
    Regards,
    Prateek

  • What are the Batch mode parameters for Receiver JDBC Adapter

    Hi All,
             Could some pls tell me how to set bacth mode in receiver JDBC adapter and what are its parameters and how to configure them. i beleive there is something like max count parameters etc..
    Regards,
    Xier

    Hi,
    Check this for more info
    http://help.sap.com/saphelp_nw04s/helpdata/en/64/ce4e886334ec4ea7c2712e11cc567c/frameset.htm
    Regards
    Seshagiri

  • Jdbc sender adapter in synchronous mode

    Dear Experts,
          I am on PI 7.0 SP 14. I would like to know whether it is possible to use jdbc sender adapter in
    synchrounous mode. The scenario is jdbc to web service . The response from webservice should be inserted into the database.  If we use the insert statement in the response mapping will it work ? 
    Thanks
    Aju

    Hi
    JDBC sync is possible but only at Receiver, look this blog
    SYNCHRONOUS SOAP TO JDBC - END TO END WALKTHROUGH
    JDBC Stored Procedures
    JDBC Receiver Adapter -- Synchronous Select – Step by Step

  • Batch mode on JDBC adapter

    Hello XI Experts
    Could anyone please provide more information about how to use the Batch mode in JDBC adapter.  I would be sending about 200,000 records from abap proxy to oracle. Is it better to adopt the batch mode approach or the splitting of data in chunks approach so as to have a better performance while sending huge volumes of data.

    Hi ,
    Batch mode will be used to execute group of SQL statements at a time and it will improve the performance.
    but in your case sending 2lac records at a time will def create problems,my suggestion is split the data in to small chunks and send to data base,it will not create any problems.
    if you want split the data use java mapping , using that we can easily split the number of records in to small chunks.
    write a log in java mapping split the data in to 10000 records every time, out put stream will return multiple records,suppose you have 200000 records,if you are trying to split the data in to 10000 records,java OUTPUT stream will return 20 messages
    this is my idea,,if you find any other best way to split data,follow that.
    Regards,
    Raj

  • JDBC Adapter in async. scenario

    Hi everybody.
    I have the following scenario:
    R/3  --->  XI ---> Legacy
    In this scenario, there is at the moment a synchronous call from XI -> Legacy using the JDBC receiver adapter. In this call there are various SELECTs and UPDATEs, so I have to use the XML SQL format of the JDBC receiver adapter.
    Unfortunately, the processing of the synchronous call is quite slow, and from time to time there even is a timeout which aborts the whole process. In order to get this process to work I only see two solutions:
    a) increase the timeout values of the synchronous call
    b) switch from synchronous to asynchronous processing
    I don't like solution a) because it could possibly influence others aspects of our XI system as well, so I prefer b).
    However, I do not know how to do it or even if it is possible at all...
    Is it possible to split up the synchronous call in an asynchronous request/response pair and to use correlation in a BPM?
    Is JDBC receiver adapter capable of this usage scenario?
    Regards, Joerg

    Hi everyone!
    Thanks for the valuable input.
    Alas, I still have a problem...
    I did the following: I inserted a dummy SQL statement into my request XML message. This dummy statement simply inserted an ID into the SELECT, and this ID is returned "as is" in the result. I use this ID to create a correlation between an asynchronous SEND step in my BPM and an asynchronous RECEIVE step in the same BPM. Unfortunately it seems to me that the JDBC adapter is not capable of working in an asynchronous mode. I have created a receiver adapter, I send my SQL XML message - and I get <i>no</i> return. It seems to me like the response message (my SQL XML should generate a response) "vanishes" - there is no answer...
    Is there some kind of "trick" I have to apply in order to get the JDBC receiver adapter to work in this scenario?
    Regards, Joerg

  • Strange behavior of JDBC Adapter

    Hello everybody!
    I found a pretty strange behaviour of JDBC Receiver Adapter during problems with network (big thanks to our Basis). According to the status in Adapter Engine, the message wasn't processed. In the database I can see these inserts. However, there are more lines in the XML than lines in the database. So, how it is possible that adapter commits only part of inserts. Logs and settings see below.
    My XML includes a SQL_DML statement and a few INSERT statements, each contains many inserts.
    It looks like that:
    <?xml version="1.0" ?>
    <MyMessage>
        <statement>
            <table1 action="SQL_DML">
                <access>here I delete old values</access>
            </table1>
        </statement>
        <statement>
            <table2 action="INSERT">
                <access>some data</access>
            </table2>
        </statement>
        <statement>
            <table3 action="INSERT">
                <access>some data</access>
            </table3>
        </statement>
    </MyMessage>
    Part of adapter log is here:
    Information
    Message successfully put into the queue
    Information
    The message was successfully retrieved from the receive queue
    Information
    Message status set to DLNG
    Information
    Delivering to channel: Adapter_Name
    Information
    MP: processing local module localejbs/CallSapAdapter
    Information
    Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
    Information
    JDBC Adapter Receiver Channel Adapter_Name: Processing started; party / service BS
    Information
    Database request processed successfully
    Error
    MP: exception caught with message Ack handling failed: creation of messageFactory failed: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Connection JDBC_http://sap.com/xi/XI/System is currently not started.
    Error
    Exception caught by adapter framework: Ack handling failed: creation of messageFactory failed: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Connection JDBC_http://sap.com/xi/XI/System is currently not started.
    Error
    Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.Exception: Ack handling failed: creation of messageFactory failed: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Connection JDBC_http://sap.com/xi/XI/System is currently not started.
    Information
    Message status set to WAIT
    Information
    The asynchronous message was successfully scheduled to be delivered at ...
    Information
    Message status set to TBDL
    Information
    Retrying to deliver message to the application. Retry: 1
    Information
    The message was successfully retrieved from the receive queue
    Information
    Message status set to DLNG
    Information
    Delivering to channel: Adapter_Name
    Information
    MP: processing local module localejbs/CallSapAdapter
    Information
    Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
    Information
    JDBC Adapter Receiver Channel Adapter_Name: Processing started; party / service BS
    Error
    Unable to execute statement for table or stored procedure. 'Table' (Structure 'statement') due to com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'fields'. Cannot insert duplicate key in object 'Table'. The duplicate key value is (field values).
    Error
    JDBC message processing failed; reason Error processing request in sax parser: Error when executing statement for table/stored proc. 'Table' (structure 'statement'): com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'fields'. Cannot insert duplicate key in object 'Table'. The duplicate key value is (field values).
    Error
    MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'Table' (structure 'statement'): com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'fields'. Cannot insert duplicate key in object 'Table'. The duplicate key value is (field values).
    Error
    Exception caught by adapter framework: Error processing request in sax parser: Error when executing statement for table/stored proc. 'Table' (structure 'statement'): com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'fields'. Cannot insert duplicate key in object 'Table'. The duplicate key value is (field values).
    Error
    Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'Table' (structure 'statement'): com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'fields'. Cannot insert duplicate key in object 'Table'. The duplicate key value is (field values).
    Adapter settings:
    Maximum concurrency: 20
    Persistence: Local
    Conflict Resolution: Redo
    Advanced Mode: On
    Number of Retries of Database Transaction on SQL Error: 0
    Transaction Isolation Level: serializable

    Dear All,
    Follow the steps below to resolve the "Connection JDBC_http://sap.com/xi/XI/System is currently not started." issue:
    1. Log in to NWA
    2. Navigate to Operations -> Systems -> Start & Stop
    3. Click on Java Services tab
    4. Search  the service Service "XPI Adapter: JDBC"
    5. Select the service XPI Adapter: JDBC and click on Restart button
    With the restart of JDBC Service in NWA, the channels should start working properly
    Regards,
    Shreyansh

  • Response message timed out - JDBC adapter - PI 7.1

    Hi All,
    I have a synchronous Proxy <-> XI <-> JDBC scenario. The interface works fine in most of the cases, but when my proxy sends data to UPDATE the receiver SQL server 2000 with more than 1000 records, I do not find the response message in SXMB_MONI. But all the records have been successfully updated in SQL database. The response message in my case is the number of records that have been updated.
    Initially I got the message "Synchronous response expired" in RWB, and based on SAP note 791379 and 1078420 , I changed the xiadapter.inbound.timeout.default parameter from 180000 to 600000 and added the parameter 'sqlquerytimeout' in my receiver JDBC adapter configuration with value as 600 seconds.
    I have also enabled batch mode in my receiver adapter.
    Now my problem is I don't see any error message in RWB , but still in SXMB_MONI I am not able the response  message, but can see only the log version of my request message.
    Any idea on what needs to be done in this case ? Any help will be greatly appreciated.
    Regards,
    Sandeep

    Hello,
    Could you pease let us know how thiswas solved ?
    Same problem i am having.
    Thanks in advance

  • JDBC Adapter - transaction handling

    Hi,
    I have a question. I use graphical Message Mapping and standard documents formats for Receiver JDBC Adapter.
    Now I need to push a delete call and insert calls in one message looks like that one f.e.:
      <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:MT_CostcentreUpdate xmlns:ns0="http://rtl.de/xi/TransCostcenter">
    - <StmName>
    - <dbTableName action="DELETE">
      <table>KOSTENSTELLEN</table>
      </dbTableName>
    - <dbTableName action="INSERT">
      <table>KOSTENSTELLEN</table>
    - <access>
      <KOSTL>0000001000</KOSTL>
      <GUELTVON>2005-09-01</GUELTVON>
      <GUELTBIS>9999-12-31</GUELTBIS>
      <ABTEI>Test1</ABTEI>
      <VERAK>Name1</VERAK>
      <KHINR>K1000_1010</KHINR>
      <KTEXT>Test1</KTEXT>
      </access>
    - <access>
      <KOSTL>0000001001</KOSTL>
      <GUELTVON>2005-03-01</GUELTVON>
      <GUELTBIS>9999-12-31</GUELTBIS>
      <ABTEI>Test1</ABTEI>
      <VERAK>Name2</VERAK>
      <KHINR>K1000_1010</KHINR>
      <KTEXT>Test2</KTEXT>
      </access>
    - <access>
      <KOSTL>0000001006</KOSTL>
      <GUELTVON>2006-04-01</GUELTVON>
      <GUELTBIS>9999-12-31</GUELTBIS>
      <ABTEI>Test1</ABTEI>
      <VERAK>Name3</VERAK>
      <KHINR>K1000_1010</KHINR>
      <KTEXT>Test3</KTEXT>
      </access>
      </dbTableName>
    </StmName>
    </ns0:MT_CostcentreUpdate>
    Because I need to do both (delete & insert) in one transaction mode. But i will not work at the moment
    I always get error:
    com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'KOSTENSTELLEN' (structure 'StmName'): java.sql.SQLException: FATAL ERROR document format: invalid level 5' found (structure 'StmName')
    Thanks for any help
    Matt

    Hi Matthias,
    you need to have two statements (StmName), one for delete, one for insert.
    Regards,
    Udo

  • JDBC adapter can't find the jdbc driver class

    Hello, my jdbc driver give an very strange error
    11:46:13 (4207): JDBC adapter terminated
    Mon Aug 02 11:46:13 CEST 2004 *****
    11:46:13 (4210): ERROR: Attempt to load JDBC driver failed ("java.lang.ClassNotFoundException: oracle.jdbc.driver.OracleDriver")
    Attempt to intialize JDBC adapter failed
    11:46:13 (4203): Unable to start JDBC adapter (not initialized)
    I know that the jdbc driver is in the classpath, and to confirm that I have created a java program in the IB (repository) which import the class oracle.jdbc.driver.OracleDriver. I can compile and run that program without problems.
    Here you can see my jdbc adapter configuration file:
    jdbc adapter java class
    classname=com.sap.aii.messaging.adapter.ModuleDB2XMB
    mode=DB2XMB
    Integration Engine address and document settings (example, see docu)
    XMB.TargetURL=http://<host>:<port>/sap/xi/engine?type=entry
    XMB.SenderBusinessSystem=ExtAdapterSender
    XMB.SenderInterfaceNamespace=http://sap.com/xi/xidemo
    XMB.SenderInterfaceName=ExtAdapterSenderIF
    XMB.QualityOfService=EO
    ##DB Adapter specific parameters (example for SQL-Server, see docu)
    db.jdbcDriver=oracle.jdbc.driver.OracleDriver
    db.connectionURL=jdbc:oracle:<user>:<password>/hello@<url>:<port>:<instance>
    db.processDBSQLStatement=Select * emp
    db.pollInterval=600
    xml.recordsetsPerMessage=1

    Hi Ernesto,
    Can you try to the following:
    1. Remove your JDBC driver entries from the CLASSPATH.
    2. Put those jars into your jre/lib/ext directory.
    3. Restart the whole adapter engine, and
    4. Config the driver java class for the adapter. the class name to be used can be found in your JDBC driver document.
    Let me know whether it works.
    Hart

  • Sender JDBC Adapter and Synchronous Interfaces

    Hello
    I have a Oracle/JDBC -> XI -> ECC/RFC scenario. The communication mode is Synchronous.
    In the Oracle database I have a table with a "STATUS" field.  When JDBC Adapter Sends the rows from this table to the Integration Engine, it updates the "STATUS" from "G" (GENERATED) to "R" (READ).
    The response from the RFC contains for each row sent to RFC a "STATUS_from_RFC" field, that I would like to use to update Oracle STATUS field to "S" (SUCCESS) or "E" (ERROR).
    Can the Sender JDBC Adapter use the response from the Synchronous RFC to update Oracle "STATUS" field itself ?
    Or do I need a Receiver JDBC Adapter? In this case, I have to use asynchronous communication and BPM, ok ?
    thanks
    Julio

    Bhavesh,
    <i>>>>But, the online help states it supports QOS of BE and so it does support Synchronous Processing.</i>
    Even File adapter has QOS of BE
    To my understanding response back is possible only if it is PUSH + Sync
    Adapters PUSH + Sync
    HTTP
    SOAP
    RFC
    XI
    etc...
    For the above response is possible
    Adapter PULL + Sync
    File
    JDBC
    etc..
    In general there can be a response if there is a request. In the case of File and JDBC there is no request message coming to the adapter, its the adapter which is actually requesting.
    This is just an idea and my understanding.. might not be true If possible do try it and let everyone know I will also give it a try when time permits
    Thanks,
    Prakash

  • Sender JDBC Adapter hang after network problem ?

    Hi,
    I got problem with Sender JDBC Adapter. in the normal condition it is working fine. no problem at all.
    The problem coming after network connection problem within XI and database for about more than 24 hours. After the connection resume the Sender JDBC Adapter doesn't want to pickup the data.
    Communication Channel Log  Showing  (Without finish Processing).
      6/16/08 5:49:04 PM   Processing started
      6/16/08 5:48:04 PM   Processing started
      6/16/08 5:47:04 PM   Processing started
      6/16/08 5:46:04 PM   Processing started
      6/16/08 5:45:04 PM   Processing started
    In normal Communication Channel Showing :
    6/16/08 5:33:39 PM efcbd379-6b57-4922-364f-9c047e82ac1b Polling interval started. Length: 30.0 seconds
    6/16/08 5:33:39 PM efcbd379-6b57-4922-364f-9c047e82ac1b Processing finished successfully
    6/16/08 5:33:39 PM   Processing started
    6/16/08 5:33:09 PM efcbd379-6b57-4922-364f-9c047e82ac1b Polling interval started. Length: 30.0 seconds
    6/16/08 5:33:09 PM efcbd379-6b57-4922-364f-9c047e82ac1b Processing finished successfully
    6/16/08 5:33:09 PM   Processing started
    The problem resolve after restart the whole XI system. is there any other way to solve the problem without restarting the whole xi server. Because i have tried to stop and start the communication channel but still doesn't work until restart the xi. server.
    Please advise.
    Thank you and Best Regards
    Fernand

    Check JDBC FAQ note 831162
    7. Network-Level Connection Problems
    Q: The TCP/IP connection to my database host is running over an unreliable network connection, i.e. the connection is sometimes interrupted. Consequently, I sporadically receive an SQLException regarding a closed connection in the system trace or audit log or the connection as well as the JDBC Adapter channel are hanging.
    How can I work around this connectivity issue?
    A: Enable the "Advanced Mode" for the respective JDBC Adapter channel and select the option "Disconnect from Database After Processing each Message".
    Note that this might put additional load on your DBMS due to the creation of a new database connection for each message.
    If you are connecting to an Oracle database, also refer to question #10 for an alternative solution.

  • Problem in inbound JDBC Adapter

    My scenario is like sending data from SAP to database through JDBC adapter.
    but when i tried to excute my program it is giving follwing message:
    Error processing request in sax parser: Error when executing statement for table/stored proc.  java.sql.SQLException: ORA-00001: unique constraint (STSC.UDT_PRICELOCZONE_CPK) violated
    i am sure there is no duplicate records.
    can anyone tell me what the problem?

    Hi Suresh,
    that message is defintly from your database. Try to execute your stored procedure in debug mode with just the same parameters as in your XML message.
    Regards,
    Udo

  • XI3 Jdbc Adapter

    Hello,
    we try to get access to a database like hsqlDB.
    If we want to use the Jdbc Adapter we get the folling error message:
    (com.sap.aii.af.ra.ms.api.DeliveryException: java.lang.Exception:
    database connection )
    We configurated the channel prober and deployed at the SDM the hsql driver jar exactly like it is recommended at the Xi3 documentation.
    Our database works fine so it must be a problem with the jdbc deployment.
    Some help would be nice!
    Here is the full Monitoring error::
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!-- Aufruf eines Adapters
    -->
    - <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>SystemError</SAP:MessageClass>
    <SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
    <SAP:MessageId>DAF75920-28E7-11D9-A5A9-000EA6B4552F</SAP:MessageId>
    <SAP:RefToMessageId>8F008041-83D0-D52F-E100-
    0000C0A88572</SAP:RefToMessageId>
    <SAP:TimeSent>2004-10-28T13:47:06Z</SAP:TimeSent>
    - <SAP:Sender>
    <SAP:Service>COM_PLBPRODUCTDB_T</SAP:Service>
    <SAP:Interface namespace="http://plecto.com/com/xibank/plb-
    products_db">insert_inb</SAP:Interface>
    </SAP:Sender>
    - <SAP:Receiver>
    <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty" />
    <SAP:Service>COM_PLBPRODUCTDB_T</SAP:Service>
    <SAP:Interface namespace="http://plecto.com/com/xibank/plb-
    products_db">http_put</SAP:Interface>
    </SAP:Receiver>
    <SAP:Interface namespace="http://plecto.com/com/xibank/plb-
    products_db">insert_inb</SAP:Interface>
    </SAP:Main>
    - <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30"
    xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
    SystemErrorAckRequested="true" SOAP:mustUnderstand="1">
    <SAP:QualityOfService>BestEffort</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>XIAdapterFramework</SAP:Category>
    <SAP:Code area="PARSING">GENERAL</SAP:Code>
    <SAP:P1 />
    <SAP:P2 />
    <SAP:P3 />
    <SAP:P4 />
    <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException:
    java.lang.Exception: database connection missing</SAP:AdditionalText>
    <SAP:ApplicationFaultMessage namespace="" />
    <SAP:Stack />
    <SAP:Retry>M</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="2004-10-28T13:46:58Z" wasRead="false">
    <SAP:Engine type="IS">is.00.sapxi3</SAP:Engine>
    <SAP:Adapter
    namespace="http://sap.com/xi/XI/System">HTTP</SAP:Adapter>
    <SAP:MessageId>8F008041-83D0-D52F-E100-0000C0A88572</SAP:MessageId>
    <SAP:Info>host:192.168.133.114:8000::remote-
    addr:192.168.133.72</SAP:Info>
    </SAP:Hop>
    - <SAP:Hop timeStamp="2004-10-28T13:46:58Z" wasRead="false">
    <SAP:Engine type="IS">is.00.sapxi3</SAP:Engine>
    <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
    <SAP:MessageId>8F008041-83D0-D52F-E100-0000C0A88572</SAP:MessageId>
    <SAP:Info>3.0</SAP:Info>
    </SAP:Hop>
    </SAP:HopList>
    - <SAP:Ack xmlns:SAP="http://sap.com/xi/XI/Message/30"
    xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
    SOAP:mustUnderstand="1">
    <SAP:Status>Error</SAP:Status>
    <SAP:Category>permanent</SAP:Category>
    </SAP:Ack>
    - <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30"
    xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    <SAP:Date>20041028</SAP:Date>
    <SAP:Time>154658</SAP:Time>
    <SAP:Host>sapxi3</SAP:Host>
    <SAP:SystemId>XI3</SAP:SystemId>
    <SAP:SystemNr>00</SAP:SystemNr>
    <SAP:OS>Linux</SAP:OS>
    <SAP:DB>ADABAS D</SAP:DB>
    <SAP:Language />
    <SAP:ProcStatus>000</SAP:ProcStatus>
    <SAP:AdapterStatus>000</SAP:AdapterStatus>
    <SAP:User>WSC</SAP:User>
    <SAP:TraceLevel>3</SAP:TraceLevel>
    <SAP:Logging>1</SAP:Logging>
    <SAP:LogSeqNbr>000</SAP:LogSeqNbr>
    <SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
    <SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
    <SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
    <SAP:PipelineElementId>60C3C53B4BB7B62DE10000000A1148F5</SAP:PipelineEle
    mentId>
    <SAP:PipelineService>PLSRV_CALL_ADAPTER</SAP:PipelineService>
    <SAP:QIdInternal />
    <SAP:CommitActor>A</SAP:CommitActor>
    <SAP:SplitNumber>0</SAP:SplitNumber>
    <SAP:NumberOfRetries>0</SAP:NumberOfRetries>
    <SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
    <SAP:TypeOfEngine client="100">CENTRAL</SAP:TypeOfEngine>
    <SAP:PlsrvExceptionCode />
    <SAP:EOReferenceRuntime type="TID" />
    <SAP:EOReferenceInbound type="TID" />
    <SAP:EOReferenceOutbound type="TID" />
    <SAP:MessageSizePayload>138</SAP:MessageSizePayload>
    <SAP:MessageSizeTotal>0</SAP:MessageSizeTotal>
    <SAP:PayloadSizeRequest>138</SAP:PayloadSizeRequest>
    <SAP:PayloadSizeRequestMap>336</SAP:PayloadSizeRequestMap>
    <SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
    <SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
    <SAP:Reorganization>INI</SAP:Reorganization>
    <SAP:AdapterInbound>PLAINHTTP</SAP:AdapterInbound>
    <SAP:AdapterOutbound>AENGINE</SAP:AdapterOutbound>
    <SAP:RandomNumber>54</SAP:RandomNumber>
    <SAP:AckStatus>000</SAP:AckStatus>
    <SAP:SkipReceiverDetermination />
    </SAP:RunTime>
    - <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:RunTimeItem>
    <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
    <SAP:Timestamp type="begin"
    host="sapxi3">20041028134658.554363</SAP:Timestamp>
    </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
    <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
    <SAP:Timestamp type="end"
    host="sapxi3">20041028134658.574832</SAP:Timestamp>
    </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
    <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
    <SAP:Timestamp type="begin"
    host="sapxi3">20041028134658.658371</SAP:Timestamp>
    </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
    <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
    <SAP:Timestamp type="end"
    host="sapxi3">20041028134658.675398</SAP:Timestamp>
    </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
    <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
    <SAP:Timestamp type="begin"
    host="sapxi3">20041028134658.695891</SAP:Timestamp>
    </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
    <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
    <SAP:Timestamp type="end"
    host="sapxi3">20041028134658.713369</SAP:Timestamp>
    </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
    <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
    <SAP:Timestamp type="begin"
    host="sapxi3">20041028134658.751765</SAP:Timestamp>
    </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
    <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
    <SAP:Timestamp type="end"
    host="sapxi3">20041028134658.7664</SAP:Timestamp>
    </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
    <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
    <SAP:Timestamp type="begin"
    host="sapxi3">20041028134658.788744</SAP:Timestamp>
    </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
    <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
    <SAP:Timestamp type="end"
    host="sapxi3">20041028134704.21443</SAP:Timestamp>
    </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
    <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
    <SAP:Timestamp type="begin"
    host="sapxi3">20041028134704.253736</SAP:Timestamp>
    </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
    <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
    <SAP:Timestamp type="end"
    host="sapxi3">20041028134704.278098</SAP:Timestamp>
    </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
    <SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
    <SAP:Timestamp type="begin"
    host="sapxi3">20041028134704.303583</SAP:Timestamp>
    </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
    <SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
    <SAP:Timestamp type="end"
    host="sapxi3">20041028134706.126445</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>A486A55969723803BA4C52A896A8BF83</SAP:Outbo
    undBindingObjectId>
    <SAP:FromPartyName />
    <SAP:FromServiceName>COM_PLBPRODUCTDB_T</SAP:FromServiceName>
    <SAP:ToPartyName />
    <SAP:ToServiceName>COM_PLBPRODUCTDB_T</SAP:ToServiceName>
    <SAP:ToInterfaceName>insert_inb</SAP:ToInterfaceName>
    <SAP:ToInterfaceNamespace>http://plecto.com/com/xibank/plb-
    products_db</SAP:ToInterfaceNamespace>
    - <SAP:OutboundBindingAttributes>
    <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />
    </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">COM_PLBPRODUCTDB_T</SAP:Serv
    iceName>
    <SAP:ChannelName
    xmlns:SAP="http://sap.com/xi/XI/Message/30">jdbc2</SAP:ChannelName>
    <SAP:AdapterName
    xmlns:SAP="http://sap.com/xi/XI/Message/30">JDBC</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">3B787A8035C111D6BBE0EFE50A11
    45A5</SAP:AdapterSWCV>
    <SAP:AdapterEngineType
    xmlns:SAP="http://sap.com/xi/XI/Message/30">AE</SAP:AdapterEngineType>
    <SAP:AdapterEngineName
    xmlns:SAP="http://sap.com/xi/XI/Message/30">af.xi3.sapxi3</SAP:AdapterEn
    gineName>
    <SAP:MessageProtocol
    xmlns:SAP="http://sap.com/xi/XI/Message/30">XML_SQL</SAP:MessageProtocol
    >
    <SAP:MessageProtocolVersion
    xmlns:SAP="http://sap.com/xi/XI/Message/30">3.0.0527</SAP:MessageProtoco
    lVersion>
    <SAP:TransportProtocol
    xmlns:SAP="http://sap.com/xi/XI/Message/30">JDBC</SAP:TransportProtocol>
    <SAP:TransportProtocolVersion
    xmlns:SAP="http://sap.com/xi/XI/Message/30" />
    <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:ChannelAttributes>
    </SAP:ChannelEntry>
    </SAP:OutboundBindingEntry>
    </SAP:OutboundBinding>
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <Trace level="1" type="B" name="CL_HTTP_PLAIN_INBOUND">
    <Trace level="1" type="T">server-protocol HTTP/1.1</Trace>
    <Trace level="1" type="T">user-agent Java/1.4.2_04</Trace>
    <Trace level="1" type="T">host 192.168.133.114:8000</Trace>
    <Trace level="1" type="T">content-type application/x-www-form-
    urlencoded</Trace>
    <Trace level="1" type="T">content-length 138</Trace>
    <Trace level="1" type="T">remote-addr 192.168.133.72</Trace>
    </Trace>
    <Trace level="1" type="T">COMMIT is expected by application !</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 = XI3</Trace>
    <Trace level="3" type="T">client = 100</Trace>
    <Trace level="3" type="T">language = E</Trace>
    <Trace level="3" type="T">user = WSC</Trace>
    <Trace level="1" type="Timestamp">2004-10-28T13:46:58Z 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 =
    8F00804183D0D52FE1000000C0A88572</Trace>
    <Trace level="1" type="T">PLNAME = CENTRAL</Trace>
    <Trace level="1" type="T">QOS = BE</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="B" name="CL_XMS_MAIN-
    WRITE_MESSAGE_LOG_TO_PERSIST">
    <Trace level="2" type="T">Persisting original message</Trace>
    <Trace level="3" type="T">Message-Version = 000</Trace>
    <Trace level="3" type="T">Message version 000</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2004-10-28T13:46:58Z CET Begin of
    pipeline processing PLSRVID = CENTRAL</Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
    <Trace level="1" type="Timestamp">2004-10-28T13:46:58Z 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>
    <Tracelevel="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: -
    COM_PLBPRODUCTDB_T</Trace>
    <Trace level="2" type="T">Number of Receivers:1</Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2004-10-28T13:46:58Z 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">2004-10-28T13:46:58Z 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 ER 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)
    COM_PLBPRODUCTDB_T insert_inb</Trace>
    <Trace level="2" type="T">...valid InbIf without Condition:
    insert_inb</Trace>
    <Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2004-10-28T13:46:58Z 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">2004-10-28T13:46:58Z 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>
    </Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2004-10-28T13:46:58Z CET End of
    pipeline service processing PLSRVID=
    PLSRV_RECEIVER_MESSAGE_SPLIT</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 = 003</Trace>
    <Trace level="3" type="T">Message version 003</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    </Trace>
    - <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
    <Trace level="1" type="Timestamp">2004-10-28T13:46:58Z 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="1" type="T">Interface Mapping
    http://plecto.com/com/xibank/plb-products_db http_to_productdb</Trace>
    <Trace level="3" type="T">Object ID of Interface Mapping
    F90D4E058EFD371E806F0C9E0307E1CE</Trace>
    <Trace level="3" type="T">Version ID of Interface Mapping
    6E2DC920107611D98FEAE42AC0A88572</Trace>
    <Trace level="3" type="T">Mapping Steps 1 JAVA
    com/sap/xi/tf/_http_to_jdbc_</Trace>
    <Trace level="2" type="T">Mode 0</Trace>
    <Trace level="3" type="T">Creating Java mapping
    com/sap/xi/tf/_http_to_jdbc_.</Trace>
    <Trace level="3" type="T">Load 6e2dc920-1076-11d9-8fea-e42ac0a88572,
    http://plecto.com/com/xibank/plb-products_db, -1,
    com/sap/xi/tf/_http_to_jdbc_.class.</Trace>
    <Trace level="3" type="T">Search com/sap/xi/tf/_http_to_jdbc_.class
    (http://plecto.com/com/xibank/plb-products_db, -1) in swcv 6e2dc920-
    1076-11d9-8fea-e42ac0a88572.</Trace>
    <Trace level="3" type="T">Loaded class
    com.sap.xi.tf._http_to_jdbc_</Trace>
    <Trace level="2" type="T">Call method execute of the application Java
    mapping com.sap.xi.tf._http_to_jdbc_</Trace>
    <Trace level="1" type="T">*** START APPLICATION TRACE ***</Trace>
    <Trace level="3" type="T">Document start</Trace>
    <Trace level="3" type="T">Start tag [ns9:sql_insert]</Trace>
    <Trace level="3" type="T">Add raw attribute [
    xmlns:ns9="http://plecto.com/com/xibank/plb-products_db"]</Trace>
    <Trace level="3" type="T">Start tag [Statement1]</Trace>
    <Trace level="3" type="T">Start tag [PRODUCTTABLE]</Trace>
    <Trace level="3" type="T">Add attribute: [action]=[update]</Trace>
    <Trace level="3" type="T">Start tag [table]</Trace>
    <Trace level="3" type="T">Put value [productdb:PRODUCTTABLE]</Trace>
    <Trace level="3"type="T">Close tag [table]</Trace>
    <Trace level="3" type="T">Start tag [access]</Trace>
    <Trace level="3" type="T">Start tag [productCategoryId]</Trace>
    <Trace level="3" type="T">Put value [4444]</Trace>
    <Trace level="3" type="T">Close tag [productCategoryId]</Trace>
    <Trace level="3" type="T">Close tag [access]</Trace>
    <Trace level="3" type="T">Start tag [key]</Trace>
    <Trace level="3" type="T">Start tag [productid]</Trace>
    <Trace level="3" type="T">Put value [000001]</Trace>
    <Trace level="3" type="T">Close tag [productid]</Trace>
    <Trace level="3" type="T">Close tag [key]</Trace>
    <Trace level="3" type="T">Close tag [PRODUCTTABLE]</Trace>
    <Trace level="3" type="T">Close tag [Statement1]</Trace>
    <Trace level="3" type="T">Close tag [ns9:sql_insert]</Trace>
    <Trace level="3" type="T">Document end</Trace>
    <Trace level="1" type="T">*** END APPLICATION TRACE ***</Trace>
    <Trace level="2" type="T">Java mapping com/sap/xi/tf/_http_to_jdbc_
    completed. (executeStep() of com.sap.xi.tf._http_to_jdbc_</Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2004-10-28T13:47:04Z 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 = 004</Trace>
    <Trace level="3" type="T">Message version 004</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    </Trace>
    - <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
    <Trace level="1" type="Timestamp">2004-10-28T13:47:04Z 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="1" type="T">processing the outbound binding</Trace>
    <Trace level="1" type="T">search outbound bindings</Trace>
    <Trace level="2" type="T">search outbound binding for:</Trace>
    <Trace level="2" type="T">... sender party =</Trace>
    <Trace level="2" type="T">... sender service =
    COM_PLBPRODUCTDB_T</Trace>
    <Trace level="2" type="T">... receiver party =</Trace>
    <Trace level="2" type="T">... receiver service =
    COM_PLBPRODUCTDB_T</Trace>
    <Trace level="2" type="T">... receiver interface namespace =
    http://plecto.com/com/xibank/plb-products_db</Trace>
    <Trace level="2" type="T">... receiver interface name =
    insert_inb</Trace>
    <Trace level="2" type="T">outbound binding found</Trace>
    <Trace level="2" type="T">outbound channel is:</Trace>
    <Trace level="2" type="T">... party =</Trace>
    <Trace level="2" type="T">... service = COM_PLBPRODUCTDB_T</Trace>
    <Trace level="2" type="T">... name = jdbc2</Trace>
    <Trace level="2" type="T">no header mapping defined</Trace>
    <Trace level="1" type="T">outbound bindings found</Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2004-10-28T13:47:04Z CET End of
    pipelineservice 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 = 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_CALL_ADAPTER">
    <Trace level="1" type="Timestamp">2004-10-28T13:47:04Z 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: JDBC</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: JDBC</Trace>
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
    <Trace level="2" type="T">Get logon data for adapter engine
    (SAI_AE_DETAILS_GET): af.xi3.sapxi3</Trace>
    <Trace level="3" type="T">URL =
    http://sapxi3:50000/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">2004-10-28T13:47:06Z 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 = 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="CL_XMS_MAIN-
    WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <!-- ************************************
    -->
    <Trace level="2" type="T">Persisting original message</Trace>
    <Trace level="3" type="T">Message-Version = 000</Trace>
    <Trace level="3" type="T">Message version 000</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    </SAP:Trace>
    </SOAP:Header>
    - <SOAP:Body>
    <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30"
    xmlns:xlink="http://www.w3.org/1999/xlink"
    xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-
    wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-
    5CABE13F5C59AB7FE10000000A1551F7" />
    </SOAP:Body>
    </SOAP:Envelope>

    Hi werner,
        You will have to check the jar file deployment and see if its deployed properly ...By the way which XI document did u refer too..
    -admin

Maybe you are looking for

  • Internal Order Defaults

    Hi, For each company code I have created different Internal Order types. I want to assign default company code in Internal order when it will be created for that particular company code. E.g Three internal order types say ZZ01, ZZ02  and ZZ03 for thr

  • Problem in opening Video Camera

    I'm using Sony Xperia Z1.. When start my video camera in my mobile, it shows an error message: "ERROR! Camera not available". Can any1 of u sugget me how to rectify this prob?

  • Troubles with menu

    Hi all, we are using CRM 2013 (Rus). Current version: 6.1.2.112 (SP1). After update CRM to current version, there is a small issue appeared (Before update, all was fine): In menu, then i choose any "Last Seen" entities, there are Unicode codes instea

  • Link to JRE download page

    Link to JRE download page I maintain a free Java program which can be started from the Web-site. On the Web-site I need to tell how Java is downloaded and installed. What download page should I link to ? I found only http://java.sun.com/javase/downlo

  • CRM Database migration

    Hi,   I am in the process of migrating a WAS 620 based CRM 4.0 system running on DB2 v8 to MSSSQL. It has a JAVA stack also in it (ABAP+JAVA instance).   Does a CRM migration differ from normal R/3 or WAS systems' migrations?   If its different, what