JDBC adapter trace logs

We turned on the trace in visual administration tool for JDBC adapter thro' VA>Service>Log configuration>>locations>>com>>sap>>aii>>adapter>>JDBC.
Where should I look in visual adminitration tool for the trace log for JDBC adapter?
We are using Acknowledgment=Transport in Asynchonous "SEND" step of BPM to receive acknowlegement of updating database.
It is updating database but in Tcode-SXMB_MONI, Ack Status = ? "still waiting acknowledgement"
Can someone please help me to figure out where should I look for JDBC logs and why we are not able to receive acknowlegement?
Thanks in advance!
Mrudula

Hi,
- log on to the Visual Administrator
- start service - Log Viewer
- cluster -> server -> logs
- choose defaultTrace.trc
did you set tracing level to debug for JDBC adapter..
Cheers,
Naveen

Similar Messages

  • OS commands from File adapter Trace logs?

    Hi All,
    I am running some UNIX OS commands from File adapter as showing in below Blog.
    Problem is that in SXMB_MONI & in Runtime workbench I can not see any Trace logs written by those UNIX OS commands.
    Even I am writing echo messages.
    Runtime Workbench says only OS command file executed.
    Please guide me where I can see OS trace if some OS command fails?
    Any transaction code even at BASIS level exist?
    Or the only other way round exist is I need to write log into some files.
    /people/daniel.graversen/blog/2008/12/11/sftp-with-pi-the-openssh-way
    I am using PI7.1.
    Regards

    I think no solution, other then writing ABAP code using RFC SXPG_COMMAND_EXECUTE and put log/trace in some table/application.

  • 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.

  • NCHAR issue with oracle database using JDBC adapter

    Hi,
    We have a requirement to develop an XI interface from FTP server(File adapter) to oracle database using JDBC adapter. In the oracle database table few fields are of type NCHAR/NVARCHAR. when we try to insert the character(A,B,c..) values into oracle table fields of type NCHAR/NVARCHAR, we are getting the following error message in the JDBC adapter audit log. IF we pass the numeric value to the same field, then we are able to insert the records successfully.
    Unable to execute statement for table or stored procedure. 'IPCSDD_DOWNLOAD_PROCESS' (Structure 'StatementName1') due to java.sql.SQLException: ORA-00904: "P": invalid identifier
    2010-10-19 22:29:59 Error JDBC message processing failed; reason Error processing request in sax parser: Error when executing statement for table/stored proc. 'IPCSDD_DOWNLOAD_PROCESS' (structure 'StatementName1'): java.sql.SQLException: ORA-00904: "P": invalid identifier
    2010-10-19 22:29:59 Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'IPCSDD_DOWNLOAD_PROCESS' (structure 'StatementName1'): java.sql.SQLException: ORA-00904: "P": invalid identifier
    Please find the system information below.
    Oracle version- 10.2.4
    XI version - 3.0/ service pack 19
    JDBC driver- oracle.jdbc.driver.OracleDriver
    Please suggest.
    Thanks,
    Venkata
    Edited by: Venkata Narayana  Eepuri on Oct 21, 2010 12:10 AM

    Dear Venkata Narayana,
    Concerning the error, kindly go through the following note :
    731 - Collective note: ORA-00904
    follow the recommendations mentioned in that and please check if that helps.
    Best Regards
    Nishwanth

  • System trace for File, JDBC adapter

    In the  JDBC Adapter Help (help.com) I see:
    „The adapter writes the output (STDOUT and STDERR) for the operating system command in the system trace.”
    Which trace is meant here?
    I have the same question regarding File Adapter.
    Thanks, Jozsef

    Hi,
    have a look at my weblog to see how you can check
    the traces:
    /people/michal.krawczyk2/blog/2005/08/17/xi-operation-system-command--error-catching
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • 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.

  • In the rwb adapter monitoring the JDBC Adapter always grey

    Hi all
    I try to use JDBC Adapter in XI 3.0 sp14.
    First I deploy the MS SqlServer JDBC by SDM RemoteGui.I can see the deployed JDBC package in \j2ee\cluster\server0\bin\ext\com.sap.aii.af.jmsproviderlib.
    Then I create a communication Channel using JDBC 2.0 in a Business System and active the configuration.
    But when I monitor JDBC Adapter in the rwb, I find the JDBC Adapter is always grey.In the \server0\log\services\com.sap.aii.adapter.jdbc.svc, no log shows the jdbc adapter is initial.
    So what extended configuration shall i do.
    Thanks in advanced
    Elliott

    hi Alessandro,ravi:
    Thanks for your reply. I will describe detail.
    I use a file adapter as a sender and use a JDBC adapter as a receiver.
    In the sxmb_moni I find the processed message status is successful.
    So I think the integration server works fine.
    In the message monitoring, the message is waiting status.
    If I change the receiver adapter to file adapter.
    It works fine.So I think the process config is fine and the itegration server works fine. the error is in the receiver JDBC adapter side.
    I check the default trace, <b>there is error logs</b>:
    #com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer
    #sap.com/com.sap.aii.af.ms.app
    #com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.invokeHandler(QueueMessage, MessageController, Services)
    #J2EE_GUEST#0#SAP J2EE Engine JTA Transaction :
    [057ffffffb160017c]
    #cgbasis.comgroup.cn_XID_5746950#XIAFUSER#0a056bc0900311daa9ca0013d4b31c7c#SAPEngine_Application_Thread[impl:3]
    _36##0#0#Error##Java###Rolling back transaction for
    message due to: #2#d2fe2281-8fd4-11da-cf7f-
    0013d4b31c7c(INBOUND)#Object not found in lookup of
    SapXIJDBCAdapterService.#
    #com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer#sap
    .com/com.sap.aii.af.ms.app#com.sap.aii.af.ra.ms.impl.core
    .queue.ReceiveConsumer.invokeHandler(QueueMessage, MessageController, Services)
    #J2EE_GUEST#0##cgbasis.comgroup.cn_XID_5746950#XIAFUSER#0
    a056bc0900311daa9ca0013d4b31c7c#SAPEngine_Application_Thread
    [impl:3]_36##0#0#Error##Java###Transaction rolled back
    for meesage due to: #2#d2fe2281-8fd4-11da-cf7f-
    0013d4b31c7c(INBOUND)#Object not found in lookup of
    SapXIJDBCAdapterService.#
    In the adapter monitoring, JDBC Adapter icon is grey. I
    can't click for detail information. I only deploy the
    JDBC drivers by SDM remoteGui. What else shall I do.
    Btw, Can you say sth detail about how to test the
    deployed JDBC adapter on visual administrator?
    Thanks
    Elliott

  • 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

  • JDBC adapter started but no message is created

    I am not able to read data through JDBC adapter.
    When we are starting our inbound JDBC adapter it get started and does not give any error
    but no message is created in XI.When we check status of adapters by clicking main menu it is red.
    Log of adapter shows.
    JDBC adapter initializd succesfully.
    JDBC adapter started.
    Process query select * from ??????.
    JDBC adapter processing complete.Restart for next processing.
    But no message is created in XI.
    Can the no of records be the cause of this problem.
    Any help appericiated

    Hi,
    You can change the logging and tracing level of the JDBC adapter using the trace and log properties.
    Some errors may appear in the adapter_x.log file (see traces from the main menu).
    Goodluck

  • 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

  • Problem in sender JDBC adapter

    hello,
    I am facing one typical problem in sender JDBC adapter.
    Here is the issue,
    JDBC API method getString threw an exception: java.sql.SQLException: Cursor state not valid.
    Can anyone please help me out in solving this problem?
    Actually after a retry of 3 times the message has been successfully sent. Till then i am getting these error
    On 1st attempt ,
    Error during conversion of query result  to XML java.sql.SQLException: Cursor state not valid
    On 2nd attempt,
    Error during conversion of query result  to XML java.sql.SQLException: Internal driver error                                                                               
    (class.java.lang.InterruptedException)
    On 3rd attempt,
    Processing finished successfully.
    This is the scenario that i can see in the audit log.
    Can you please help me out in solving this issue.
    Thanks,
    Soorya

    Hi gaurav,
    It was a good response from your side.
    I have gone through the FAQ but could not able to find anything.
    Can you please help me out in this regard ?
    Also i am using select query of this kind,
    SELECT
    SEFVHRC.VHRBRCD,SEFVHRC.VHRCUCD,SEFVHRC.VHRVIN,SEFVHRC.VHRMOCD,SEFVHRC.VHRCHAS,
    SEFVHRC.VHRSLOR,SEFVHRC.VHRDIVI,SEFVHRC.VHRMGCD,SEFVHRC.VHRMOCH,SEFVHRC.VHRVHTY,
    SEFVHRC.VHRBDTY,SEFVHRC.VHRMFYR,SEFVHRC.VHRMOYR,SEFVHRC.VHRMODS,
    SEFVHRC.VHRMDTL,SEFVHRC.VHRCLBR,SEFVHRC.VHRRCID,SEFVHRC.VHRARDT,
    SEFVHRC.VHRLUTM,SEFVHRC.VHRLUDT,SEFVHRC.VHRKEYN,SEFVHRC.VHRCTORN,
    SEFVHRC.VHRCTIMP,SEFVHRC.VHRPRDT,SEFVHRC.VHRPRDT,SEFVHRC.VHRRCDT,
    SEFVHFT.VHFCLCD,SEFVHFT.VHFCAT,SEFVHFT.VHFCADSC,SEFVHFT.VHFKEY,SEFVHFT.VHFTEXT1,
    SEFVHFT.VHFTEXT2,SEFVHFT.VHFTEXT3,SEFVHFT.VHFTEXT4
    FROM
    SAPTESTLIB.SEFVHRC,SAPTESTLIB.SEFVHFT
    WHERE
    SEFVHRC.VHRVIN = SEFVHFT.VHFVIN AND SEFVHRC.VHRSTTS = ' '
    and update query of this kind,
    Update SEFVHRC SET VHRSTTS = 'R' WHERE VHRSTTS = ' '
    I am using prity big select query. is there any option to optimize it?
    Can you please help me out in solving this problem
    urs,
    Soorya

  • RWB error in Sender JDBC adapter

    Hi All,
    I am using SP at sender communication channel. When I am activating the Sendr CC I am getting the The statement did not return a result set. error.
    But when I lgged to database server and checked the SP it was working fine and giving the values in table. means SP is producing result set.
    what could be the possible resong for the error.
    regards
    rams

    Hi,
    1. turn on the logging in SQL server
    2. start jdbc adapter on XI
    3. check logs on SQL server
    Regards,
    Michal Krawczyk

  • Receiver JDBC Adapter testing?

    Hi
    Can any one tell me ..how do I test specific adapter w'ther it is connected or not?
    I have cross checked using adapter monitor, my jdbc adapter doesn't showing specific error(red) or success(green),in same JDBC monitor remainig channels showing all information..i thought it unable to connect?Am I correct?
    Did i do any specific settings in JDBC receiver communcication channel?
    I left default settings as it is in CC..
    after giving driver details...i left default settings ..
    1. Interpretation of empty string values = Null value
    2. Persistance          = Local
    3. Conflict resolution  = Redo
    and my datatype structure like this:
    <StatementName>
    <table>Payment_ReceiptFromSAP</table>
    <dbTableName action=”INSERT”>
    <access>
    <col1>ComapnyCode</col1>
    <col2>PaidDate</col2>
    <col3>PaidAmount</col3>
    </access>
    </dbTableName> 
    </StatementName>
    mapping is working fine, tested! RFC sender channel working fine, picking the data from SAPR/3.
    SXMB _MONI -- I haven't find any payload ..why? I thought if RFC is picking the daata properly then XI will hold that data into integration server?..how do i find this data?
    It would be appriciated and rewarded , if you make me clear in this situvation..thanks in advance.!
    Regards..rambarki!

    hi,
    >>I have cross checked using adapter monitor, my jdbc >>adapter doesn't showing specific error(red) or >>success(green),in same JDBC monitor remainig channels >>showing all information..i thought it unable to connect?Am >>I correct?
    you will see in adapter monitoring only after the first time the call is made, the bean in generated and you will be able to see in atapter monitoring.
    >>SXMB _MONI -- I haven't find any payload ..why?
    is ur scenaio synchronous?? if so then make sure you have logging set in sxmb_adm
    Configuration -> Integration Engine Configuration -> Change Specific Configuration Data.
    Category : Runtime
    Parameter : LOGGING_SYNC
    value : 1 (activated)
    Cheers,
    Naveen

  • JDBC adapter error

    I am working on proxy to jdbc scenario where iam seeing error log  in jdbc adapter of communication channel monitering  like below:
    Kindly do the needful?
    Could not execute statement for table/stored proc. "ACU_LVL_ADDR_SRC" (structure "Statement_ACU_LVL_ADDR_SRC") due to java.sql.SQLException: ORA-00001: unique constraint (FSSMGR.ACU_LVL_ADDR_SRC_PK) violated
    JDBC Message processing failed, due to Error processing request in sax parser: Error when executing statement for table/stored proc. 'ACU_LVL_ADDR_SRC' (structure 'Statement_ACU_LVL_ADDR_SRC'): java.sql.SQLException: ORA-00001: unique constraint (FSSMGR.ACU_LVL_ADDR_SRC_PK) violated
    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. 'ACU_LVL_ADDR_SRC' (structure 'Statement_ACU_LVL_ADDR_SRC'): java.sql.SQLException: ORA-00001: unique constraint (FSSMGR.ACU_LVL_ADDR_SRC_PK) violated
    Adapter Framework caught exception: null
    Delivering 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. 'ACU_LVL_ADDR_SRC' (structure 'Statement_ACU_LVL_ADDR_SRC'): java.sql.SQLException: ORA-00001: unique constraint (FSSMGR.ACU_LVL_ADDR_SRC_PK) violated

    Use structure like as below .....
    <StatementName1>
    <dbTableName action=u201DUPDATEu201D | u201CUPDATE_INSERTu201D>
        <table>realDbTableName</table>
    <access>
    <col1>val1</col1>
    <col2>val2new</col2>
    </access>
    <key1>
    <col2>val2old</col2>
    <col4>val4</col4>
    </key1>
    <key2>
    <col2>val2old2</col2>
    </key2>
    </dbTableName>
      </StatementName1>

  • JDBC adapter: greek characters

    Hi All,
    We are reading and sending data from a ms sql dbase towards our R/3 system via PI (JDBC adapter).
    I am having some problems related with exotic characters (greek). Reading these characters from the dbase works fine without any additional config, but writing these characters gives problems.
    When I check the message logging inside XI, the characters look fine, but the result in the dbase is not.
    ex:
      XI       = Martine &#913;&#932;&#932;&#921;&#922;&#927; &#920;&#917;&#929;&#913;&#928;&#917;&#933;&#932;&#919;&#929;&#921;&#927;
      dbase = Martine ?????? T???????????
    I already tried changing the charset of the communication channel to "iso-8859-7", but that did not fix the problem.
    Anyone an idea?
    Kindest regards
    Joris

    In note 831162 (FAQ: XI 3.0 / PI 7.0 JDBC Adapter) is mentioned:
    "2. Unicode Handling
    Q: I am inserting Unicode data into a database table or selecting Unicode data from a table. However, the data inserted into or retrieved from the table appears garbled. Why doesn't the JDBC Adapter handle Unicode correctly?
    A: While the JDBC Adapter is Unicode-aware, many JDBC drivers and/or database management systems aren't by default and need a codepage or Unicode-awareness to be configured explicitly. For the respective JDBC drivers, this codepage setting is often configured via the driver URL. For details, refer to the documentation of your JDBC driver or database management system.
    Note: For the Lotus Domino Driver for JDBC, there does not seem to be any documented method to enable support for Unicode strings."
    Does this help you?
    Regards
    Stefan

Maybe you are looking for

  • I can not open my wifi in X201s

    I buy a new hard disc, and re-install the win 7. The drivers and applications are all insalled. The device manager shows all hardware works. However, when I use "Fn+F5" to open the wifi, it always fails. StrangeIy, I can open the WiMAX and bluetooth

  • Project wise vendordetails

    Dear all,   In my client place based on the project requrement we purchase the material from the vendors. I want to take report based on project details vendor report. pl guide me to solve this issue. girija

  • Problems with viQueryf in VISA 2.6

    We've recently installed VISA 2.6 on our systems and have found that our routines making use of viQueryf are no longer working. We've narrowed it down to two main problems: 1. When using "%#t", the size of the array is returned instead of the number

  • AE works fine, connected to internet but AE Utility loses base station

    three computers are connected, one with ethernet cable (1st gen iMac G5) and two wirelessly (1st gen MacBook Pro and 17 in iMac Core Duo 2) All three have connectivity to web but the amber light is flashing and NONE of three computers AE utility can

  • STMS Route configuration in Three system Landscape with DEV,QA and PRD

    Hi We have Three system landscape.i.e DEV,Quality and PRD Before Somebody  configured the STMS by selecting standard two system land scape ( Dev and QAS) We Have Installed Production Server And Added into Existing STMS Configuration Now Three Systems