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" ?>
- 
- <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

Similar Messages

JDBC Adapter Invalid level 4' found

Hi all,
I have the following XML messages send to a JDBC adapter and I get an Invalid Level 4' found:
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:ATL_JDBC_SQL_MAT_BOM_IN_MT xmlns:ns0="http://atlantis.com/material.bom">
- <Statement1>
- <dbTableName action="UPDATE_INSERT">
<table>SAP_MATERIAL_BOM</table>
- <access>
<IDOC hasQuot="YES">0000000000003670</IDOC>
<CODE hasQuot="YES">0183654</CODE>
<ROWMATCODE hasQuot="YES">0183685</ROWMATCODE>
<ROWMATQTY hasQuot="YES">8.000</ROWMATQTY>
<CH_OK hasQuot="YES">0</CH_OK>
</access>
</dbTableName>
- <key>
<CODE hasQuot="YES">0183654</CODE>
</key>
</Statement1>
</ns0:ATL_JDBC_SQL_MAT_BOM_IN_MT>
Does anybody have an idea what might by wrong? Thanks.
....Socrates>>

We are using XI3.0 sp18. The communication channel (JDBC RECEIVER) has the following error when receive the above XML message:
11/9/06 3:21:49 PM 4c54613a06b71c409b86d27d7df80ce3 Error while parsing or executing XML-SQL document: Error processing request in sax parser: Error when executing statement for table/stored proc. 'SAP_MATERIAL_BOM' (structure 'Statement1'): java.sql.SQLException: FATAL ERROR document format: invalid level 4' found (structure 'Statement1')
11/9/06 3:21:49 PM 4c54613a06b71c409b86d27d7df80ce3 Processing started
That's all the Info I have...

Sender JDBC Adapter in a synchronous szenario

Hi,
i am trying to set up following szenario:
A JDBC Sender Adapter is polling data from a database, this data is beeing mapped to a synchronous RFC-Call to the R/3 backend. The result from the RFC-Call contains an order-number, which should be stored in the database.
The query of the DB and the rfc-call works fine. The query is also doing the UPDATE statement to the DB, marking this line of data as beeing processed.
The QOS in the sender-jdbc-adapter is set to "Best Effort", which should allow a synchronous communication.
I am mapping the response of the rfc-call to a jdbc-receiver-like structure, in the monitoring i can see the rfc-result and also the message to update the databae. There are no errors in the adapter-monitoring and everything looks fine, except that the database is not beeing updated.
Is there another messageformat for the synchronous answer to a sender-jdbc-adapter? Or is it possible, that the commit for the answer is not beeing sent?
We have an XI3.0 with SP16 installed.
Thanks for your help.
Ingo

hi,
you cannot use the Sender JDBC adapter to Upate.
Create a receibver JDBC adapter with the format as mentioned and use it to update the DB.
the steps in BPM wil be ,
1. Receive -- for Sender JDBC adapter
2- Send Synchronous -- RFC call synchrnous
3 - Send -- using Receievr JDBC adapter to Insert / Update the DB.
Do let me know if u need further info,
regards,
Bhavesh

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.

DB Insert failed through JDBC Adapter

Hi all,
My system is on the latest patches of XI3.0 SP9. I am trying to insert some records into a database through JDBC adapter. The XML arriving at JDBC adapter is:
<?xml version="1.0" encoding="UTF-8" ?>
<ns:MaterialDataUpdate_Msg xmlns:ns="http://acsis.com/ManufacturingManagement">
<MaterialData>
<TMP_MAT_SERIAL action="INSERT">
<table>TMP_MAT_SERIAL</table>
<access>
<MATNO>0000000012</MATNO>
<BATCH>32151</BATCH>
<ITM_SERIAL>453176587769</ITM_SERIAL>
<WEIGHT>12.34</WEIGHT>
<T_TIME>2005-01-21 13:21:34.432</T_TIME>
</access>
</TMP_MAT_SERIAL>
</MaterialData>
</ns:MaterialDataUpdate_Msg>
The connection to the database looks ok. My JDBC adapter config is pointing to "jdbc:microsoft:sqlserver://sapsrv03:1433;databaseName=JDE".
In rwb, I got the following error:
Unable to execute statement for table or stored procedure. "TMP_MAT_SERIAL" due to java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Invalid object name 'TMP_MAT_SERIAL'.
I have checked the database "JDE", and the table 'TMP_MAT_SERIAL' does exist.
Does anyone have any idea about this error?
Thanks a lot for helping!
Hart

Hi Hart Liu,
My system is on the latest patches of XI3.0 SP9. I am trying to insert some records into a database through JDBC adapter.
We have been facing with problem XSD structure in the jdbc side. We r manually created XSD structure. In the adapter engine we dont have any action item. In u r mail
U r structure contains action attribute.
Can u plz help me out to generate the right XSD structure?
We have one more doubt, is there any automatically structure-generated option? plz let us know.......
We r waiting for u r reply....
Plz help me!!!!!!!!
Regards,
Anil

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

Reg: How to Stop Polling of JDBC Adapter without Scheduling the adapter

Dear Gurus,
Here I am having one requirement. My clients wants to send data from JDBC adapter (ORcale System table) to R3 system via RFC.
His Requirement::
1. He is not telling the time of data flow from Oracle server so that based on that we can schedule the adapter in the Communication Channel monitoring (Availablitiy Time Planning) or Else we can Schedule by deciding the setting of the polling interval time.
2. He is telling that When ever he waants to send the data he will place one dummy file in the File Adapter FTP location so that it will became an Indication for u to poll the jdbc adapter and to transfer the data to R3.
3. Untill he keeps the file or gives indication he doesn;t want to communicate with Oracle server due to some security and it s a most important data base he doesn't want to disturb that Oracle Server as so many business are running on that.....
We Proposed::
1. Atleast you need to tell the scheduling time or poll interval time so that we can schedule our adapter.
but he s not accepting for this
2. Atleast U need to give access for Data base to enter one more extra field like STATUS CODE so that we will add one number and we keep on Update in the Update table and based on that Update table statement it will poll.
but he s not even accepting for this
3. Finally we prposed that to create another table in the Oracle SYstem as Dulplicate Table which is similar to Standard Orginal table when ever he wants to pick the data please keep that data in this Duplicate TABle so that JDBC adapter will pick the data from thsi TABLE instead of picking the data from that standard table so that it will not effect any standard table data in the table.
but he s not even accepting for this
We have done some R & D:::
1. WE approached even through BPM and via switch conditions is one scenario
   FILE RECEIVE >SWITCH CONDITION> RECEIVE AND SEND or else EXIT
2. Using correlation in anotehr scenario means correlating File adapter and JDBC and based on one dynamica value it will goes to SEND STEP ( RECE IVE --> RECEIVE --> SEND STEPS )
Even though we know this...concept that...we jsut tried::
In BPM we can control the flow in XI 3.0 but we cannot Stop the Polling of JDBC adapter at backend because one the data comes from FILE adapter it will keep on HOLD untill it receives the JDBC from Oracle then based on the condition or Correlation it will goes futher SEND step means after that file adapter is picking file or not ...what ever it may be JDBC will polls at backend and brings that data to BPM"
Hence sugest me How to Stop Polling of JDBC Adapter without Scheduling the adapter or else using STATUS CODE Update statements in JDBC Tables
Regards:
Amar Srinivas Eli

Hi! All,
Finally I decided to do the scenario in two steps:
1: FILE REQ --> JDBC REQ -->JDBC RES --> FILE RECV
2: FILE RECV --> RFC
But I am getting issue while doing first scenario
Desgn :
I have created 2 Synchronous interfaces :
1) FILE 2 JDBC REQ
In this a) out put message is FILE Req
          b) Input msage:; FILE RES
2} JDBC2FILE RECV
        a) Output mesage;; JDBC REQ
        b) Input Msge :: JDBC Response
Mappings:
1) File REQ-->JDBC REQ
2) JDBC RES-->FILE RES
Interface mappings:
1: FILE 2 JDBC REQ--> JDBC 2 FLE RECV
CONFIGURATION ::
1: One Seder File CC
2: Two reciever CC's one is for JDBC RECEIVER and other s FILE RECEIVER
3; One Sender Agreement
4: 2 Recver agreements
5: One Interface Determination and
6: One RECCV Determination
My Question;;
1. First let confirm whether my development steps are right or not ?
2: Another thing s I am not sure reg Configuration Steps means
whetehr one interface determination and one Receiver Determinations are required or not as these are synchronous Interfaces
3: main Issue is::::
If my scenario s FILE2RFC2FILE then I will get RFC response automatically but here issue is this is JDBC
My reqquirement is By sending one Field from fILE to JDBC REQ it needs to send entire TAbLE records as a Response to file as XML
without having Sender JDBC how can I send the JDBC Res to FILE and If that is the case then again JDBC adapter is polling which is contradict to the client requuirement which i explained above.
pleas suggest me the Detailed steps mainly Colloboration agreements and logical routings and
also explain in detail if i can go for BPM
Also give cleear blogs but before giving make sure that it contains detailed screen shots because aIready gone thorugh
Scenario File-JDBC-RFC
File<-->JDBC Sync coomunication.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/file-rfc-file(Without+BPM)
/people/luis.melgar/blog/2008/05/13/synchronous-soap-to-jdbc--end-to-end-walkthrough
Regards::
Amar Srinivas Eli

How to insert a NULL value in SQL using JDBC Adapter

Hi All,
I have a File -> JDBC scenario.
In the File and in the SQL table I have a column called "MR_DATE" that needs to be mapped
I have to do the following:
If MR_DATE is NOT equal to "00000000"
then pass MR_DATE to SQL table
else
set the MR_DATE column in the table as NULL.
Please suggest
regards,
Piyush

Hi Piyush,
In the receiver JDBC adapter select the option Interpretation of Empty String Values as NULL.
Pass date as empty, it will be interpreted as NULL by adapter and inserted in database.
Regards,
Gautam Purohit

Error while executing the stored procedure through sender JDBC adapter

Hi All,
I am getting below error while executing the stored procedure through sender JDBC adapter.
Database-level error reported by JDBC driver while executing statement 'exec SapgetNextEntity 'SalesOrder''. The JDBC driver returned the following error message: 'com.microsoft.sqlserver.jdbc.SQLServerException: The statement did not return a result set.'. For details, contact your database server vendor.
what is the problem? any idea to anyone...
regards
Ramesh

hi Dharamveer,
I am not getting below statement for your reply
Try to use Refrence Cursor it will return u reference of resultset.
I mention SP like this
exec SapgetNextEntity 'SalesOrder'
SapgetNextEntity -
> SP Name
SalesOrder----
> Parameter I am passing...
regards
Ramesh

Error while retrieving data from sql using jdbc adapter

hi all,
i m working on one scenario where i m sending data using HTTP and receiver is jdbc adapter which is retrieving me data from sql server.
i have checked the structure both for req and res.
i m getting this error
<SAP:Error>
<SAP:Category>Application</SAP:Category>
<SAP:Code>MAPPING.EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_INF57285_DB_HR_RES_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
<SAP:Stack>During the application mapping com/sap/xi/tf/_INF57285_DB_HR_RES_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
</SAP:Error>
can somebody help me with this.
Thanks & Regards
Aruna

thnks bhavesh i think i made it that way
JDBC REQ
<ns:INF57285_DB_Request xmlns:ns="http://www.infosys.com/xi/training/hyd/57285">
<Employee>
    <EmpDetails action="SELECT">
      <table>EmpDetails</table>
      <access>
        <Name />
        <EmpId />
        <Band />
        <Salary />
      </access>
      <Key>
        <EmpId>57285</EmpId>
      </Key>
    </EmpDetails>
</Employee>
</ns:INF57285_DB_Request>
JDBC RES
<ns:INF57285_DB_Request_response xmlns:ns="http://www.infosys.com/xi/training/hyd/57285">
<Employee_response>
    <row>
      <Name>aruna</Name>
      <EmpId>57285</EmpId>
      <Band>A</Band>
      <Salary>4675776</Salary>
    </row>
</Employee_response>
</ns:INF57285_DB_Request_response>
my hr req is which i mapped with DB req
<ns:INF57285_HR_Req xmlns:ns="http://www.infosys.com/xi/training/hyd/57285">
<REQUEST>
    <EmpNo>57285</EmpNo>
</REQUEST>
</ns:INF57285_HR_Req>
my hr res is which i mapped with DB res
<ns:INF57285_HR_Res xmlns:ns="http://www.infosys.com/xi/training/hyd/57285">
<response>
    <row>
      <Name>aruna</Name>
      <Empld>57285</Empld>
      <Salary>4675776</Salary>
    </row>
</response>
</ns:INF57285_HR_Res>
and interestingly i am not getting any error in sxmb_moni
it's not showing any error
plz suggest me something wht to do ....
thnks & regards
Aruna

Need to connect to Oracle 11g using PI 7.1 JDBC adapter

Hi All,
I am trying to configure a JDBC adapter to connect Oracle 11g. For this I need to know the driver,jar and connection URL details.
Can anyone please provide the above information?
Please correct me if my details are wrong :
JDBC Driver : oracle.jdbc.driver.OracleDriver
JAR : ojdbc5.jar
URL : jdbc:oracle:thin:@localhost:1521:ora11i
Regards,
Prakash.

Yes i knew how to deploy the jars using SDA.
I will try to deploy the above jar (ojdbc5.jar ) and try to connect to Oracle 11g with URL & Driver classname.
If I face any problem then i will get back to you.

How to call Packaged Stored Procedure in JDBC Adapter?

hello frnds,
I m working on a SAP R/3 -> XI -> Oracle scenario. Here on receiver side i m using JDBC Adapter in which i m using a stored procedure.
I have my stored procedure in a Package. Example : package "PKG_SPARES_VOR_UPLOAD" and in that stored procedure "pr_spares_vor_po_hdr_upload".
i have checked that if i write this stored procedure outside the package then it works fine... but if i put it into the package then it is giving me error that ....
" Receiver Adapter v2112 for Party '', Service 'BS_ORADEV':
Configured at 2006-08-16 10:12:14 GMT+05:30
History:
- 2006-08-16 11:02:04 GMT+05:30: Error: TransformException error in xml processor class: Error processing request in sax parser: Error when executing statement for table/stored proc. 'PR_SPARES_VOR_PO_HDR_UPLOAD' (structure 'statement'): java.sql.SQLException: ORA-06550: line 1, column 7:
PLS-00201: identifier 'PR_SPARES_VOR_PO_HDR_UPLOAD' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored ".
please help me out with this problem.
Thankx,
Regards,
Audumbar

Hi,
I have the same problem to call a stored Procedure in a Package.
If my procedure is not in a package, everything is right.
And I musn't indicate all the name, because I musn't put '.' in the name (of the procedure), in my DT on XI.
It would be so nice to have an answer.
Rémi

Table name in Receiver JDBC Adapter

Hi All,
I am using receiver JDBC adapter.
But table name consist of " like BPC."#II" .
After mapping table name becomes BPC."#II" .
I am getting error while pulling data from DB.
Is the table name creating a problem.
Please remedy of this if you have come across such scenario.
Regards
Piyush

Hi Piyush,
All that i could get from the SAP Help regarding JDBC Adapters are these links where i never found anything much regarding the table name.anyways just go through these links and see if you find anything useful.
http://help.sap.com/bp_bpmv130/Documentation/Planning/XIUnicodeGuide030411.pdf
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/b0/676b3c255b1475e10000000a114084/content.htm">Configuring the Receiver JDBC Adapter</a>
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/cf/406642ea59c753e10000000a1550b0/content.htm">Mapping Lookups</a>
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/22/b4d13b633f7748b4d34f3191529946/content.htm">JDBC Adapter</a>
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/64/ce4e886334ec4ea7c2712e11cc567c/content.htm">Configuring the Receiver JDBC Adapter - part 2</a>
This is all i got from the help files, anyways you can also go through those links and see if you find anything else useful.
- Escape Symbol for Apostrophe
The apostrophe character () is a reserved character in SQL syntax and is therefore replaced by an escape character if it occurs within value strings. This replacement character can be database-specific. Typical replacement characters are \ or (default value). If a character occurs that is invalid for the database being used, the adapter triggers an error message (an SQL exception) concerning the SQL syntax that is generated by the database.
- Column Name Delimiter
Depending on the database being used, column names can be enclosed by a special delimiter character, for example, if the names can contain special characters (such as ). This character can be specified at this point. The default setting is no delimiter character. If a character occurs that i
Also check if there are notes in the service market place related to the same.
Regards,
abhy
Message was edited by: Abhy Thomas

XI3 Jdbc Adapter

Similar Messages

Maybe you are looking for