JDBC ADAPTER  logSQLstatement=true

Hi Experts,
         I would like to know  which other SQL statements can be used in JDBC reciever adapter like
logSQLstatement = true
Thannks in Advance

Hi,
JDBC Adapter: Additional Parameters
Please have look into the note:  801367
Regards,
Rajesh

Similar Messages

  • Sql Server logSQLStatement - JDBC Adapter

    Hi
    I try to show sql statements in RWB using additional parameter logSQLStatement = true in JDBC Adapter.
    It works fine in Oracle database, but i try in SQL Server 2005 and not show in RWB.
    any help ?
    tks
    Marco

    Maybe you need to setup something on  sqlserver 2005.

  • Inserting Multiple Rows into Database Table using JDBC Adapter - Efficiency

    I need to insert multiple rows into a database table using the JDBC adapter (receiver).
    I understand the traditional way of repeating the statement multiple times, each having its <access> element. However, I am just wondering whether this might be performance-inefficient, as it might insert records one by one.
    Is there a way to ensure that the records are inserted into the table as a block, rather than record-by-record?

    Hi Bhavesh/Kanwaljit,
    If we have multiple ACCESS tags then what happens is that the connection to the database is made only once. But the data is inserted row by row.
    Why i am saying this?
    If we add the following in JDBC Adapter..logSQLStatement = true. Then incase of multiple inserts we can see that there are multiple
    <i>Insert into tablename(EMP_NAME,EMP_ID) VALUES('J','1000')
    Insert into tablename(EMP_NAME,EMP_ID) VALUES('J','2000')</i>
    Doesnt this mean that rows are inserted one by one?
    Correct me if i am wrong.
    This does not mean that the transaction is not guaranted. Either all the rows will be inserted or rolled back.
    Regards,
    Sumit

  • JDBC Adapter-XML Document Name

    I am working on XI 2.0 and need to change the XML document name I am receiving from an inbound JDBC adapter.  The document I am receiving is:
    <resultset>
      <row>
        <col1>ABC</col1>
        <col2>123</col2>
      </row>
    </resultset>
    I want to receive:
    <MyDocumentName>
      <row>
        <col1>ABC</col1>
        <col2>123</col2>
      </row>
    </MyDocumentName>
    Does anyone know how to override the default "resultset" name from the JDBC adapter???  The reason I need to do this is because my message mapping does not work properly unless I have the Message type of the message from my JDBC adapter as "resultset". 
    Thanks for your help!
    Dan Pettingill

    (Note: I work with Dan Pettingill, the starter of this thread)
    I decompiled the class Renato suggested, but I don't
    think that's going to be the solution.  The DB2XMBProcesser is dependent on XI properly setting the properties values for the jdbc adapter.  DB2XMBProcesser will use a property named "db.documentname" to set the name of the root node of the DB2 results. If no such property is defined, the default value of resultSet is used.
    [documentName = getParaWithDefault("db.documentName", "resultset");]
    Our problem seems to be that XI is not passing along the parameters we define in the adapter configuration.  We've tried numerous combinations and names, but they never take. 
    The only way we can get XI to recognize that we are sending in a documentName parm is to call it "docName".  Any other name is essentially ignored (including db.documentname, documentname, XMB.docName, and a lot of other permutations as well).
    But here is the log from that adapter when we do so.  Not that it sees the value we're setting, but it won't set the documentname parm going to the jdbc.
    2004-08-31 17:33:45 : jdbcListener
    Raw configuration data ***
    Transport protocol: JDBC, version
    Message protocol: JDBC, version
    pollInterval|301
    additionalParameters|true
    jdbcDriver|com.ibm.db2.jcc.DB2Driver
    retryInterval|null
    dbpassword|***
    queryStatement|SELECT * FROM RBPRDB.T1256;
    queueName|null
    autoCommit|false
    updateStatement|Delete from RBPRDB.T1256 Where GUID Is Not Null;
    dbdisconnect|false
    dbuser|r50445
    adapterStatus|active
    isolationLevel|2
    addParameterParams|*** TABLE , 2 ROWS DEFINED ***
    addParameterParams|addParameterParams$0$addParameterParamName$docNamespace
    addParameterParams|addParameterParams$0$addParameterParamValue$urn:freescale.com
    /xi/db2-ims/wms
    addParameterParams|addParameterParams$1$addParameterParamName$docName
    addParameterParams|addParameterParams$1$addParameterParamValue$SelectAckQueue
    pollIntervalMsecs|null
    execute|null
    connectionURL|jdbc:db2://WACCTSO.sps.mot.com:9003/WACCDB2T
    qualityOfService|EO
    Used configuration data ***
    'MessageProtocol': 'JDBC'
    'adapterStatus': 'active'
    'addParameterParams.dbEncoding': ''
    'addParameterParams.docName': 'SelectAckQueue'
    'addParameterParams.docNamespace': 'urn:freescale.com/xi/db2-ims/wms'
    'addParameterParams.docNamespaceScope': 'root'
    'additionalParameters': 'true'
    'autoCommit': 'false'
    'connectionURL': 'jdbc:db2://WACCTSO.sps.mot.com:9003/WACCDB2T'
    'dbdisconnect': 'false'
    'dbencoding': ''
    'dbpassword': '***'
    'dbuser': 'r50445'
    'documentname': 'resultset'
    'documentnamespace': ''
    'execute': ''
    'isolationLevel': '2'
    'jdbcDriver': 'com.ibm.db2.jcc.DB2Driver'
    'pollInterval': '301'
    'pollIntervalMsecs': '0'
    'qualityOfService': 'EO'
    'queryStatement': 'SELECT * FROM RBPRDB.T1256;'
    'retryInterval': '301'
    'updateStatement': 'Delete from RBPRDB.T1256 Where GUID Is Not Null;'
    OK - initialized

  • Two queries on same table in sender JDBC adapter

    Hi all..
    My requirement is as follows....
    query a table and fetch rows where column Error="true"
    If there are no records in the table satisfying the above condition ,i want to send a mail stating  that there are not records with error flag set to "true"
    But the problem is i wont get a message to PI if there are no records.
    If i write a query to get the count of records where column Error="true",Obviously the count would be zero. Using this message from database i can send a mail.
    Now please let me know if i can write both the queries in query SQL statement? if so howshould be the source structure?
    Thanks
    Ram..

    Hello ram,
                     As far as i know it is not possible to use two different SQL statements in the sender adapter, though you can try with the join statement.
    For further information refer this discussion
    [Multiple Select Possible?|How to call multiple SQL using the JDBC adapter;
    Regards,
    Prasanna

  • 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

  • Error when using receiver JDBC adapter

    i am using JDBC adapter as receiver(for oracle 10g) now, however i got ORA-00984 error. So i enable logSQLStatement.
    then got the following SQL statement from communication channel monitoring:
    INSERT INTO BASEINFO(APPNO, BUSSINAME, APPPERSON) VALUES (3, Steven, Lee)
    I realize the statement is incorrect, which should be:
    INSERT INTO BASEINFO(APPNO, BUSSINAME, APPPERSON) VALUES ('3', 'Steven', 'Lee')
    So how can i correct the SQL statement? is there any setting i miss out in configuration?
    Thanks

    You may try this. For each field in datatype, add an attribute hasQuot. Map it to "no" in mapping. Then add single quotes to all the values by simply concatinating it on both sides of value.
    Regards,
    Prateek

  • 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

  • XI JDBC Adapter using stored procedures

    Hi
    I am using the JDBC adpapter to call a stored procedure on a SQL database.
    In the adapter configuration I am using 'com.microsoft.jdbc.sqlserver.SQLServerDriver' as the JDBC Driver parameter and 'jdbc:microsoft:sqlserver://LIBOEE01:1433;DatabaseName=DEV_OEE;SelectMethod=cursor;' as the connection string.
    My payload is as follows:
      <?xml version="1.0" encoding="UTF-8" ?>
      <root>
        <Statement>
        <PL101_SAPR3_SKU_OBJ action="EXECUTE">
         <p_verb isInput="true" type="varchar">CREATE</p_verb>
         <p_site_id isInput="true" type="varchar">GPK</p_site_id>
         <p_sap_line_id isInput="true" type="varchar">LN005</p_sap_line_id>
         <p_sku_id isInput="true" type="varchar">4014847</p_sku_id>
         <p_sku_desc isInput="true" type="varchar">Klipdrift Exp -  12x750ml</p_sku_desc>
         <p_bottles_in_sku isInput="true" type="float">12</p_bottles_in_sku>
         <p_bps_sap isInput="true" type="float">2.083</p_bps_sap>
         </PL101_SAPR3_SKU_OBJ>
        </Statement>
       </root>
    However, when I cal lthe interface I receive the follwoing error in the adapter:
    2007-07-18 11:25:03 Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: JDBC Adapter configuration not initialized: null
    2007-07-18 11:25:03 Error Exception caught by adapter framework: JDBC Adapter configuration not initialized: null
    2007-07-18 11:25:03 Error Delivery of the message to the application using connection failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: JDBC Adapter configuration not initialized: null.
    Is this possibly casued by the driver being the incorrect version?
    Regards
    Michael

    Hi Kanth,
    Thanks for your response, but the blog by Siva Maranani is actually where I got my code from. Upon further research I think have found the problem as experienced in this blog --> Re: MS SQL Server jdbc Driver installation on XI . There are 2 jar files missing from our SQL JDBC driver --> msbase.jar and msutil.jar, I think once I have added these to the driver it might work. Strange that when you download the driver from microsoft's website that these 2 files are only available in the UNIX download though!
    Regards
    Michael

  • JDBC Adapter debugging parameter

    Dear gurus,
    We wanna activate the debugging parameter for the JDBC adapter to generate logs in XI 3.0.
    Please comment !!!!
    Regards,

    I cannot find how to set the parameter for activating the trace for JDBC adapter.
    The exact path is given in the question here in this thread
    JDBC adapter trace logs
    help me in activating the parameter logSQLStatement
    As already been suggested refer note:801367
    I think this parameter is available in XI3.0 also.Just go to the advanced mode of the JDBC channel and select it.

  • JDBC adapter Commit/Rollback

    Hi Guys, I got a question regarding JDBC adapter auto commit. Hopefully you guys can help me :). Until now, when my XI calling a storedprocedure in ORACLE using JDBC adapter, it will automatically commit the calling. When i see my configuration for the JDBC adapter receiver, the checkbox for Enable Autocommit is thicked. My question is, is there anyway that we handle the commit or rollback ourself. How we can handle that? Is it from the BPM or just from the Configuration.
    Thank you very much in advance for all replies, advices and answer. Cheers guys..

    Hi
    Try this out
    You can programmatically set auto commit to true as in follows
    // Load the Oracle JDBC driver
    DriverManager.registerDriver(new oracle.jdbc.OracleDriver());
    // Connect to the database
    // You can put a database hostname after the @ sign in the connection URL.
    Connection conn =
          DriverManager.getConnection ("jdbc:oracle:oci:@", "scott", "tiger");
    // It's faster when auto commit is off
    <b>conn.setAutoCommit (true); </b>
    // Create a Statement
    Statement stmt = conn.createStatement ();
    regards
    krishna

  • Where to see generated SQL statement from jdbc adapter?

    Hi everybody,
    where can I see the generated SQL statement from JDBC adapter?
    Regards Mario

    Yes and True lterally means the same, but alas XI does not understand literature..
    Just checked the note as well, as you are correct!
    Regards
    Bhavesh

  • Pass system ack of JDBC adapter to ERP in IDoc - XI - JDBC scenario

    Dear all,
    i have an IDoc -> XI -> JDBC scenario (without using ccBPM). In the standard way the ERP system, sending the IDoc waits for an application acknowledgement. However the JDBC adapter is only capeable to send system acknowledgements.
    Is there a way to pass these acknowledgements to the IDoc status record?
    In help.sap.com (http://help.sap.com/saphelp_nwpi71/helpdata/en/ab/bdb13b00ae793be10000000a11402f/frameset.htm) under "IDoc Processing with the IDoc Adapter " there is a table that maps XI system/applic acknowledgement to IDoc status. So in my opinion the status record of my IDoc should at least chenge to the corresponding status for the system ack.
    Can anyone tell, if this is really working? What if I deactivate the acknowledgement request in the NOALE programm?
    In any case, can I achieve to transfer the system ack to the IDoc status without using a ccBPM?
    Many thanks and best regards
    Florian

    Is there a way to pass these acknowledgements to the IDoc status record?
    Without BPM, No.
    So in my opinion the status record of my IDoc should at least chenge to the corresponding status for the system ack.
    The ack referred here is related to idoc status whether it is properly reached till XI or not and not related to the JDBC ack.
    What if I deactivate the acknowledgement request in the NOALE programm?
    Then u won't have any ALEAUD message at sender R3.
    In any case, can I achieve to transfer the system ack to the IDoc status without using a ccBPM?
    No
    Regards,
    Prateek

  • JDBC Adapter - Established database connection failed

    Hi Guys,
    we have installed the JDBC Adapter based on the How To Guide and we checked after the installation the  Libaries :Cluster --> Server --> Libraries --> com.sap.aii.af.jmsproviderlib and the box Box "JARs Contained" was filled.
    So in my point of view we have done everything right during the installation.
    Now the developer tested theJDBC Adapter and he comes back with following Error:
    Attempt to establish database connection failed with SQL error com.sap.aii.adapter.jdbc.sql.DriverManagementException: Cannot establish connection to URL "jdbc:microsoft:sqlserver://xxx.x.xx.xxx:1433; databaseName=CZZ03;":ClassNot FoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver
    Do you have any ideas?
    Regards
    Markus

    Hello Markus,
    To install JDBC driver follow the how to guide.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how%20to%20install%20and%20configure%20external%20drivers%20for%20jdbc%20and%20jms%20adapters.pdf
    Configuration of JDBC Adapter for SQL Server
    JDBC Driver = com.microsoft.jdbc.sqlserver.SQLServerDriver
    Connection = jdbc:microsoft:sqlserver://hostname:<port>;DatabaseName=<DBName>
    UserID and Password.
    If the connection is not working find the correct port number.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40b92770-db81-2a10-8e91-f747188d8033
    JDBC- X I -  R/3 Scenario
    /people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
    /people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
    Thanks,
    Satya Kumar
    Reward Points If it is Useful..

  • CLOB Datatype with JDBC Adapter

    Hi,
    we try to fill a Clob Datatype to JDBC Database.
    We try 2 ways with the JDBC Adapter:
    action="SQL_DML" with an SQL Statment and $placeholders$
    But how can i say the key element that it is a CLOB type?
    He used this a VARCHAR and there a not more than 4k Chars allowed.
    second way is action="EXECUTE" to call a Stored Procedure, but there we got the error that CLOB type is an Unsupported feature.
    Any Idea?
    Regards,
    Robin
    Message was edited by: Robin Schroeder

    Ok i will check this...
    But i'm right when i say that the only way to fill CLOB Type is to use a Stored Procedure ?
    or is there any possibility to do this with action="SQL_DML" ?
    Regards,
    Robin

Maybe you are looking for

  • Using a MacBook and saving my neck at the same time

    I recently bought a MacBook Air with a 13" screen. It is my primary computer. I write a lot as part of my job, and I do a lot of this writing at home. This new MacBook is great, but it is destroying my neck. To get my head level with the screen, I sl

  • Printer Control App for iPad

    I use the above app mainly for scanning straight to my iPad and it is very good at that. I have one niggle in that I have to set the page size for each page I scan. Being a UK user A4 is the main paper size in use rather than US size. If we could set

  • POV in Hyperion Financial Reporting Studio and Workspace

    Hi! I have the following problem. I create a report in Hyperion FinReporting Studio, choose required members in POV. Save report. Then I open it in Workspace and sometimes my chosen POV crushed: sometimes there are no chosen members, sometimes there

  • Ren Server Issue

    Hi All, I am configuring Renserver. I am facing error HTTP 403. i have performed following steps. 1. configured application server and set psrensrv option, gave auth domain. 2. restarted domain. did not change any thing in webserver. 3. i have full p

  • My airport express doesn't seem to have extended the wifi range

    I have recently bought an Airport Extreme which connects to my modem (broadband) via ethernet. This wifi signal does not reach the kitchen and we need internet access there, so I have bought an Airport Express, hoping it would extend the signal and g