Add JDBC-Adapter to Monitor?!

Hi,
we configured JDBC-Adapter and are using it. But unfortunately it is not listed in Monitoring of ABAP-Stack, just in CC-Monitoring i can see if messages are processed.
How to add these informations to the ABAP-Part in SXMB_MONI?!
br

If I am not wrong then your question like "NO JDBC adapter status in MONI"???
You cannot chek the trace of JDBC adpater in ABAP stack as it reside in Java Stack. so you have to look it on RWB-Component Monitoring--> Adapter Engine->Communication Channel Monitoring.
Thanks
Farooq.
*Rewards Points if you find it useful*

Similar Messages

JDBC Adapter Message Monitoring

Hi All,
I have configured a sender JDBC adapter. The adapter status is green. The message is Processing finished sucessfully. But I can not find any msg in SXMB_MONI.
I can not see any msg in msg monitoring also.
Any input on this will be highly appreciated.
Regards,
Jai Shankar.

If that does not work , then do this
Can you check the following,
1. Check the SELECT query in your Sender JDBC adapter. Does it actually return any rows?
2. The values enterd for Documentname and DocumentNamespace in your Sender JDBC adapter. You have to enter the name of the Datatype and the namespace in these fields.
3.Have you enterd these details while doing the adapter configuration,
jdbc:oracle:thin:@<IP adress>:<listener port>:<instance name (database name)>
Driver oracle.jdbc.driver.OracleDriver
Another thing that is to be checked is, if the table strucutre has changed in the database, if yes, deactivate and activate the Sender Adapter once again and it should work.

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

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

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

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

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

Scheduling JDBC adapter in PI 7.0 SP09

Hello Experts,
My client is using PI 7.0 sp09. I have a JDBC adapter that needs to execute once every 24 hours but each time the server is restarted the adapter executes and starts the 24 hr cycle again from that time. Is there any way to schedule this so that it only executes at a specific time during the day? I've read the threads about the option of scheduling adapters in sp10 but is there any way to control the execution of JDBC adapters in sp09?
Thanks

Hi
Hope it helps..
Note:You will need to have the authorizations of the user group SAP_XI_ADMINISTRATOR with the role modify.
Go to Runtime Workbench -> Component Monitoring -> Communication Channel Monitoring
Locate the link Availability Time Planning on the top right corner of your Communication Channel Monitoring page.
In your case, the requirement is to schedule the Sender file adapter daily once at 8:00 at morming.
In Availability Time Planning, choose the Availability time as daily and say create.
Provide the details like the time 12:00
Then select the communication channel , goto the Communication Channels tab and filter and add the respective channel (File Sender).
Once all the above has been done 'Save' the changes.
For more
/people/shabarish.vijayakumar/blog/2006/11/26/adapter-scheduling--hail-sp-19-
/people/alexander.bundschuh/blog/2006/01/04/scheduling-messages-in-sap-xi
Thanks

Error when using receiver JDBC adapter

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

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

XI3 Jdbc Adapter

Hello,
we try to get access to a database like hsqlDB.
If we want to use the Jdbc Adapter we get the folling error message:
(com.sap.aii.af.ra.ms.api.DeliveryException: java.lang.Exception:
database connection )
We configurated the channel prober and deployed at the SDM the hsql driver jar exactly like it is recommended at the Xi3 documentation.
Our database works fine so it must be a problem with the jdbc deployment.
Some help would be nice!
Here is the full Monitoring error::
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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 - Are these Properties Correct?

Hi,
I am trying to execute a stored procedure on a Microsoft MSSQL Server via the JDBC Adapter.
The adapter is installed like it is described in the Driver-Manual and I configured the Adapter according to the User-Manual of the driver. But it doens't work.
Are these properties correct?!
http://www.devilstorm.com/downloads/jdbc.jpg
Thank you for your help
Thomas

1. Did you check whether your communication channel is active and in green status in the adapter monitor ?
2. If it is in the error status what is the error ? If it is in green status does it say it last polled at date and time ?
3. it is not call ZZ_COPA_ZCHECK, it should be EXEC ZZ_COPA_CZECH.
One other thing is you do not have a namespace, click on Advanced Mode (Erweiterter Modus) and add
Name = docNamespace
Value = <your namespaece>
regards
SKM

Sapdb (maxdb) and jdbc adapter problem

Hi,
i have installed this jdbc file:
http://sapdb.org/7.4/sap_db_jdbc.htm
like in this how-to:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how to install and configure external drivers for jdbc and jms adapters.pdf
then i set up an jdbc to file szenario to test the adapter.
Driver is: com.sap.dbtech.jdbc.DriverSapDB
connection is: jdbc:sapdb://sapdb-host/XI_DATA
with sapdb-host is the db server and XI_DATA ist the database
user and pw is dba
sql statement is: SELECT * FROM "AAA_XI_DATA" WHERE "number" = 50
with AAA_XI_DATA is the table with test data.
the statment works in the sapdb studio. (No ; in sapdb and the XI)
but when i have a look at the runtime monitor at the af
messages there is no message genereated. where can i
check, if the jdbc driver is working and where do i find
error messages?
Regards
J.
Message was edited by: Jörg Pieper

You can check if there is some kind of error with the JDBC Adapter in the Runtime Workbench. Inside the RWB, open "Component Monitoring", "tree view", "Adapter Monitoring", and in the adapter listing you'll find the "JDBC Adapter". It should have a green light. If not, the error will be displayed.

Stored procedure in Sender JDBC Adapter

Hi All,
My Scenrio goes like this ...
Stored Procedure(SQL Server) --- PI -
File
I need to write the results of stored procedure to File.Here I don't need any mapping.So how many DT , MT and MI need to be created?
The interface need to run by 6AM from Monday to Thrusday, how can i achieve this ?
Stored Procedure has only select statement and no Update statement , but it takes Date as Input parameter , so what i need to provide in sender JDBC adapter.
Thanks,
Monish

Hi Monish,
As per your requirement it is JDBC to File. Please be careful with the structure to be created for sender JDBC. I am unable to understand why you donot require a mapping for this. How XI will send the data to a file then.As per my knowledge if it's file to file and just pick and drop then we can neglect IR and go for ID.But here you are working with JDBC and File so you will be in need of it.
IR:
DT: 2
JDBC_Sender_DT
File_Output_DT(Optional)
You can use the JDBC sender data type structure for File output also.
MT as per your DT
MI:2
Outbound MI: JDBC structure
Inbound MI : File structure
MM: 1
IM: 1
ID as similar to other scenarios.All 1 objects for RD,ID,Sender Agreement and Receiver Agreement.
Sender JDBC channel:
Query: Select * from table where date
But I have a query how are you providing date in input paramerter.It will be dynamically entered into the query right.
You can mention the Avalibility planning for your interface to work in RWB.
Go to RWB>Component Monitoring>Adapter Engine->Communication Channel Monitoring>Avaliablity Planning
Please explain.
Regards,
Nutan

Error in JDBC Adapter Configuration....

Hi,
My scenario is like this FTP->XI->Oracle Database.
The problem is that the files are not getting posted to the database though it is running well.
In XI receiver comm channel in JDBC adapter, I have provided the Connection path as jdbc:oracle:thin:@esealmw275.al.sw.ericsson.se:1521:S14. Whereas in channel monitoring it is taking jdbc:oracle:THIN:@esealmw275.al.sw.ericsson.se:1521:S14. Please note it is taking THIN as in caps.
Can anybody suggest me is this the proposed error for that, if it is so, then pls provide me the suitable solution for that.
BR
Soumya

Hi Soumya,
Have a look at ths blog...
<a href="/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30 to JDBC Adapter using SAP XI 3.0</a> by Anirban Ghatak
Also have a look at this wiki
https://wiki.sdn.sap.com/wiki/display/XI/JDBCTOJDBC
Regards
Santi
<a href="Remember to set the thread to solved when you have received a solution to set the thread to solved when you have received a solution</a>
Where There is a <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/weblogs?blog=/weblogs/topic/16">blog</a> there is a Way.

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 configuration not initialized:null

i
we have a synchronous scenario with the following adapters , RFC <> XI <> JDBC.
1.JDBC Driver installation is done
2.RFC Destination type t is done in sap(sender) system.
3.checking the jdbc in VA is done
while running it is giving the following error.
com.sap.aii.af.ra.ms.api.RecoverableException: JDBC Adapter configuration not initialized: null
where we have to initialize JDBC Adapter configuration
Thanks in advance
Prasad Nemalikanti

hi prasad
There are 2 jar files that may be missing from your SQL JDBC driver --> msbase.jar and msutil.jar, I think once you add these to the driver it might work.
also check the driver string for the SQL driver 2 parameters
i.e 'com.microsoft.jdbc.sqlserver.SQLServerDriver' now becomes
'com.microsoft.sqlserver.jdbc.SQLServerDriver'
This will solve your problem
follow this link
Re: MS SQL Server jdbc Driver installation on XI .
XI JDBC Adapter using stored procedures
thanks
sandeep
Reward points if helpful

JDBC adapter access to iSeries DB files in libraries

Hello,
We try to connect to an AS400 iSeries system via JDBC adapter!!! (not a typical scenario I think!)
The files (so called by IBM but we identify them as tables in our understanding ) are stored in libraries.
The question is how to add this library (like a path?) into JDBC adapter and interface description.
Adapter:
JDBC Driver: <driver name>
Conenction: <physical address of iSeries DB>
LogIn data: xxx
Interface description:
MESSAGE
    STATEMENT   = []
    TABLENAME
            ACTION    = select
            TABLE      = DBNAME.TABLENAME
The interface description is from another successful implementation on an ORACLE DB.
I think the table definition should contaion the library like
<DBNAME>.<LIBRARY>.<TABLENAME>
separated by dots!
I am not sure. So can anyone correct or agree?
Currently we are not ready for a first try because the driver installation is next week.
But it would help to know what we have to do instead of spending possibly a lot of time for trial and error.
Kind Regards
Dirk
Of course, helpful answers are valued by points!

I don't know this mechanism of high availability with 2 IP, but if you really have 2 hostname you should think to a method to switch from a node to the other in easy way, deactivating one and activating the other (for instance with the <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/45/0c86aab4d14dece10000000a11466f/frameset.htm">Controlling a Communication Channel Externally</a>)
I suggest you to verify how it will be in production instance: real cluster ? switch over ? virtual IP ?
Regards,
Sandro

Add JDBC-Adapter to Monitor?!

Similar Messages

Maybe you are looking for