Synchronous JDBC scenario

Hi All,
The scenario is
SAP Portal will send data to XI using web service(SOAP Adapter) and then XI will post data in Database using JDBC adapter.
When above scenario executes it is automatically creating response (Synchronous) once it post data in Database (New message in SXI_MONITOR). I have checked message interface both inbound and outbound are asynchronous. When I ran the same scenario using file adapter instead of SAP portal it is not creating new message.
Please guide how to avoid creating new message in case of SAP Portal .

Hi,
The jdbc response is generated in synchronous cases.
Make sure the webservice call that you are making is asynchronous.
In case of file adapter the call you made was asynchronous, hence no response was generated.
Check this blog for configuration for Capturing response message.
/people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
- Deepak

Similar Messages

Synchronous Proxy to Synchronous JDBC scenario

Hi,
I have a scenario for a synchronous PROXY to a synchronous JDBC scenario. I have set 4 message types .
MT_PROXYOUT u2013 o/b synch with a response MT_PROXYIN
MT_JDBC - i/b synch with a response MT_JDBC_RESPONSE
I then set up an interface mapping for both the request and response message interfaces. The design looks good but I got stuck in the configuration part.
Since itu2019s a proxy sender, the sender agreement is not needed(Correct me if I am wrong). In the interface determination, there is provision for only the inbound interface which in case would be the JDBC (request/response) back to the proxy and the interface mapping is applied.
So do I need just one interface determination from the proxy as sender and jdbc as receiver and also one receiver determination again with the proxy as sender and the jdbc as receiver. I am confused here because when I try to create a receiver determination for the response back from JDBC to proxy receiver , the interface mapping comes blank. Is it taken in account by the single receiver determination in synchronous to synchronous scenarios??
Teresa

Hi Teressa,
Java Proxy to Synchronous JDBC scenario and SAP XI:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a068cf2f-0401-0010-2aa9-f5ae4b2096f9
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f272165e-0401-0010-b4a1-e7eb8903501d
ABAP proxies-
Client proxy:
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
Server Proxies
/people/siva.maranani/blog/2005/04/03/abap-server-proxies
Cheers
Sunil

Sender side Synchoronous jdbc scenario

Hii experts,
Can we do Sender side synchronous jdbc scenario?? if yes give me an example how the scenario will look like??
and what are the steps has to be done?
Regards,
Balaji

Hi,
Can you pls clear your requirement?
In your case, do sender JDBC will fetch the data and give it to the target, and again target will give some resonse and that
response you have to insert into the database at sender side?
If this is the case for you, then it can be achieved.
Pls exactly tell what you are looking for.
-Tanaya.

Two Receiver DB in Synchronous Proxy to JDBC Scenario?

Hey,
Is it possible to develop a synchronous proxy to JDBC Scenario that have two different DBs as Receiver?
The response Datas are insert_count and update_count.
Thank.

Park,
You can't have more than one receivers in Sychronous case. If you designed the scenario , then u will get the error as "TOO_MANY_RECEIVER CASE_BE".
-raj.

SOAP TO JDBC scenario: calling stored procedure which will return the value

Hi
I have Soap To Jdbc scenario in which I am going to call the Stored Procedure at target side which will be executed and it is going to return the result set .
Result contains following values.
return code as ( 0 Or 1) and also specific exception message if its return code as 1.
Could you suggest me the way by which I can handled this return code and send it back to the Sap PI system then the same thing is directed the to SMTP server for sending mail to consern person.
Regards
Kumar

The OUT parameters of stored procedure will be returned as response. Where exactly are you facing the proble? Here is a complete walkthourgh
/people/luis.melgar/blog/2008/05/13/synchronous-soap-to-jdbc--end-to-end-walkthrough
In your case, you don't want response at sender. Instead you want to mail it. For this you may use BPM to design your scenario with following steps
Receive (to receive data from sender)
Send Sync (to stored procedure and get response)
Send Async (to mail receiver)
Regards,
Prateek

Reg http to jdbc Scenario

Hi all,
I am trying to execute a synchronous Http to Jdbc Scenario using MS Access table as my back end.
In design part ,I have followed the steps like
1. Created a http req ,jdbc req, jdbc response ,and then http response in Data types and the in Message types.
2.Created Outbound MI with http req and http response as input and output messages respectively,then Inbound message interface with jdbc req and jdbc response as input and output messages respectively.
3.In Message mapping with Http req and jdbc req as request mappings and jdbc response and http response as Response mappings following the Action and access Steps.
Thats Fine with design part
IN Configuration Part, Since it is a Http Sender ,i didnt create any sender agreement and sender communicatin channel.
Then Configured Jdbc adapter properly and i am able to access my table with that.
While Executing ,I can find that my message is sent in Runtime workbench and can find that Jdbc adapter is Running by showing green flag.
I was trying to send an empid of a table as key and expecting to retrieve the complete row of the corresponding key.
But I could not find the response even though everything is fine with XI.
Where Could be the problem ,where can I see the response from jdbc adapter .
Please help me out in solving this .
Thanks and Regards,
Kalpana

Hi Kalpana,
Can you check this weblog
/people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
This should help you...
Check the Response Mapping,also you have one IM with Reqest and Response mapping...
Also if you have SP16 then you can have sender CC for HTTP also ...
Regards,
sridhar

** RFC to JDBC scenario - Need not source code - Correct ?

Hi Friends,
I am doing RFC to JDBC scenario. It is a synchronous scenario. I think it is need not required to write any code in the source code tab of RFC. Is it correct ...? (Only Import and Export parameters are enough.)
Kindly reply, friends.
Kind Regards,
Jeg P.

Hi,
RFC needs only configuration and we will call remote method in R/3. Actual logic present in R/3.
Thanks,
RamuV

Need information regarding IDOC to JDBC Scenarios.

Hi,
Kindly help me with the pre-requisites inorder to start with a scenario of IDOC to JDBC and also the scenario of JDBC to IDOC.
Regards,
Sreedhar, Av

Hello Sreedhar,
While we working in JDBC or JMS Adapters we should deploy the Drivers..
Go through this links,
/people/varadharajan.krishnasamy/blog/2007/02/27/configuring-jdbc-connector-service-to-perform-database-lookups
http://searchsap.techtarget.com/tip/0,289483,sid21_gci1246926,00.html
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
Please check the driver path as mentioned below.
JDBC Driver : sun.jdbc.odbc.JdbcOdbcDriver
Connection:jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=//location of DB table.mdb;
No JDBC driver required.
Receiver JDBC scenario MS access - /people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
follow this thread
Re: Problem when connecting to MS Access through JDBC Adapter.
SAP Note 850116 has details
2) While we working in IDOC Adapters we should do ALE Config of IDOC Settings .
Do these configurations in R/3 and in XI...
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
Here in IDOC to JDBC interface we need not to config sender Adapter..
1) The main usage of a sender adapter is to convert the input format into the XI supported XML format.
Once the conversion is completed the sender agreement appends the header with the sender details.
In case of these adapters we wont require sender agreement and sender communicationchannel for the
following reasons.
Sender agreement is associated with a namespace when we shoot an idoc frm r/3 if already contains its standard sap namespace. so those is need of sender agreement
The sender communication channel use is to identify the sending system and adapter, as the idoc header contains the details there is no need to sender.
These adapters resides on ABAP stack here the integration server takes care of IDOC/HTTP to XML conversion without requirement of adapter.
The business system that is sending the adapter has already been assigned to a techinical system which normally acts as an integration server...
IDOC to xi links
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
Hope this explanation is useful to u..
Thanks,
Satya Kumar
Edited by: SATYA KUMAR AKKARABOYANA on Jun 3, 2008 9:57 AM

Need help in webservice to JDBC scenario

Hi All,
My scenario is a synchronous webservice to JDBC scenario. The SOAP request contains two fields one is ID & the other field is Date which is an optional field. I need to perform a SELECT statement on JDBC based on ID & Date. SOAP request will always contain ID field & Date may or maynot be there in the request. If Date present then search should be based on ID & Date , if Date not present search should be based on ID only. How to achieve this with the help of standard JDBC reciever structure or is there any other way to achieve this?
Thanks
Navin

You can create your target structure as shown below and check the existence of DATE field in the source(using standard function "Exists" ) and then only create the target DATE node.
<StatementName>
          <dbTableName action=u201DSELECTu201D>
              <table>realDbTableName</table>
              <access>
                  <col1/>
                 <col2/>
                 <col3/>
              </access>
              <key1>
                 <DATE/>
                 <ID/>
              </key1>
          </dbTableName>
   </StatementName>
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=%28J2EE3417700%29ID0591392850DB01436613452367233705End?blog=/pub/wlg/3928
Pooja

Two way Asynchronous business process for Webservice to JDBC scenario

Hi Experts,
For the webservice to JDBC scenario, I have to use two way Asynchronous business process. Is it possible?
Scenario : Webservice to JDBC -> Async Call
JDBC to Webservice -> Async Call
I have already done with two way Synchronous. Here I would like to know about only Async call. Please provide your suggestions.
Is it recommended to use Async call when we have Synchronous option?
For the above requirement I have to create two separate services and in BPM, I have to call one by one..Is it correct?
Regards
Sara
Edited by: Sara D on Dec 18, 2007 8:05 AM

hi sara,
yes it is possible.
In receiver channel JDBC we have a special parameter "Exactly Once Handling " which is to assure async incoming data to be written only once to avoid redundancy.
Although Synchronous is "Best Effort" but it is considered to be "Worst Case". We can use Sync but try to use Async as much as possible to ensure system performance.
Ques : For the above requirement I have to create two separate services and in BPM, I have to call one by one..Is it correct?
yup you have to create two services and you are following right path but this scenario should be in two steps seperately.
Rergards,
Mandeep Virk

The Resource Pool has already been destroyed - File to JDBC Scenario

Hi,
Error : "Error when attempting to get processing resources: com.sap.aii.af.service.util.concurrent.ResourcePoolException: The resource pool has already been destroyed"
Scenario : This error is occurring for the File to JDBC Scenario .
Could you please let me know why am getting this error and solution to resolve this error..
Thanks in Advance!!
Regards,
Sekhar

Hi ,
Thanks for the replies..
Just to add to have more clarity on the error for the scenario
Scenario : This error is occurring for the File to JDBC Scenario
The Scenario has a BPM involved.The synchronous send step within the BPMsends the data to the JDBC receiver adapter.The response from the JDBC
adapter is throwing the below error.
Thanks,
Sekhar

XI idoc-jdbc scenario in details

Hi Experts,
Please provide me this scenario pn detail.
Cheers
Aman

Hi,
For IDOC to JDBC scenario:
Refer the below weblog for help:
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30 --> for jdbc receiver: file -JDBC
1) First you need to install the JDBC drivers on XI server refer the below link for installation process.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-9644e49f1a10
2) You need to do the IDOC configuration at R3 as well as at Xi end:
Refer the below configuration steps:
ALE configuration for pushing idocs from SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
IDOC testing using WE19
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
Pre-requisites for Outbound IDoc from R/3 to PI:
Configurations required in R/3:
Maintain Logical System (SALE)
Define RFC Destination (SM59) which points to PI system
Maintain Port (WE21)
Maintain partner profile. (WE20):
Maintain Distribution Model (BD64):
Configuration required at Xi side:
Go to IDX2: load the DOC metadata.
3) For updating the table you need to write the stored procedure:
Refer the below link for stored prcedure.
JDBC:
Receiver JDBC scenario MS access - /people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
Stored Procedures-
/people/siva.maranani/blog/2005/05/21/jdbc-stored-procedures
http://www.ics.com/support/docs/dx/1.5/tut6.html
/people/sriram.vasudevan3/blog/2005/02/14/calling-stored-procs-in-maxdb-using-sap-xi
http://www.ics.com/support/docs/dx/1.5/tut6.html
http://java.sun.com/docs/books/tutorial/jdbc/basics/sql.html
http://www.sqlteam.com/article/stored-procedures-an-overview
Thnx
Chirag
Reward points if it helps and close the threads.

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

Problem in JDBC to JDBC scenario

Hello all,
I am working on a JDBC 2 JDBC Scenario.
Everything gone fine, data is picked from source, but it is not updated in the destination.
I could not see any message related to this in SXMB_MONI it shows only messages related to IDOC, on search I fould, we need to add trace level,etc in SXMB_ADM but still couldnot found any message (I restarted the system, cleared cache also).
In RWB(communication channel monitoring) I could find that sender is sucessful, but no message for receiver.
In RWB (message monitoring) I checked my business system, i could see sender entries but no receiver entries, there is only one error message as :
<b> transmitting the message to endpoint http://xisystem:50100/sap/xi/engine?type=entry using connectio</b>
For which I found we need to change XI businesssystem's pipeline port no from some 54+++ to 4+++ (but I could see only 50100 in the pipeline so i did'nt)
we are using R/3, was7.0 sp11,XI3.0,
Can any body help me in this regard
Thanks,
Sai.k.k

Hi,
Error in SXMB_MONI :
com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_JDBC2JDBC_MM_: RuntimeException in Message-Mapping transformatio~
Error in Integration repository when I test with the payload :
<pre>
13:01:52 Start of test
Document start
Start tag [ns0:Receiver_JDBC_MT]
Add raw attribute [ xmlns:ns0="http://xyz.com/JDBC2JDBC_NMSP"]
Start tag [Statement]
Start tag [dbTable]
Add attribute: [action]=[INSERT]
Start tag [table]
Put value [Example]
Close tag [table]
Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)com.sap.aii.utilxi.misc.api.
BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException:XML Declaration not allowed here.(:main:, row:1, col:8)
at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157)
at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73)
at java.lang.Thread.run(Thread.java:534) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException:Fatal
Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)(:main:, row=1, col=8) ->
com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2126)
at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2774)
at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155)
at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73)
at java.lang.Thread.run(Thread.java:534) -
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155)
at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73)
at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2126)
at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2774)
at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 4 more Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
13:01:52 End of test
</pre>
Query : Select * from Employee fetches all the fields
Payload :
<pre> <?xml version="1.0" encoding="utf-8" ?>
- <resultset>
- <row>
<PerNer>t</PerNer>
<Initials>t</Initials>
<Name>t</Name>
<DOB>t</DOB>
<State>t</State>
<Country>t</Country>
</row>
</resultset>
</pre>
Regards,
Sai.k.k

Error"SYSTEM Failure" while testing the RFC in SE37 : RFC to JDBC Scenario

Hi All,
I am doing RFC to JDBC scenario. When I am testing the RFC in SE37 using the RFC destination created in SM59, I get an error "SYSTEM FAILURE".
Please suggest.
Thanks,
Shyam
Edited by: Shyam Sreepada on Dec 18, 2007 5:46 PM

Hi,
You must run RFC with RFC destination in background mode, I suggest to read following post in order to understand it better.
Syntax would be:
CALL FUNCTION func IN BACKGROUND TASK
[DESTINATION <your RFC destination>]
parameter list
http://help.sap.com/saphelp_nw04/helpdata/en/8f/53b67ad30be445b0ccc968d69bc6ff/frameset.htm
If you read it you will find that you can't test it directly from SE37, for this either you need to create dummy ABAP program or another RFC where you will call this RFC with background syntax.
Regards,
Gourav
Reward points if it helps you
Edited by: Gourav Khare on Dec 18, 2007 6:07 PM

Synchronous JDBC scenario

Similar Messages

Maybe you are looking for