JDBC Receiver Adapter Communication channel

[Former Member]

HI,

I have a scenarion where JDBC is receiver. i would appreciate if someone can provide me required information.

Connection?

Driver?

where do we mentoin database name.

and table name.

how to we avoid duplicate entries.

Jeff

[Former Member]

Hi Jeff,

The parameters that you mention in your JDBC adapter depends on which Database you are trying to connect to and also you have to install the appropriate driver on your XI server for that database. Are you done with this step??

This PDF can help you on the steps involved to install the JDBC driver.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-964...

Regards,

Abhy Thomas

[prateek]

Hi Jeff,

The connection and driver settings

http://help.sap.com/saphelp_nw04s/helpdata/en/b0/676b3c255b1475e10000000a114084/content.htm

Database name is part of the connection string and driver detail

e.g. for SQL server,u have to deploy the drivers (msbase.jar, mssqlserver.jar, msutil.jar).

U have to specify the table name in the message structure defined in the following manner

http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm

Have a look at this also

/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30

Regards,

Prateek

[Former Member]

Hi,

Could you tell me the significance of Statement, Table, Access

Regards,

Jeff

[MichalKrawczyk]

Hi,

>>>>Statement, Table, Access

<b>Statement</b> - jdbc call - meaning one SQL statement

<b>Table</b> - table on which you execute your command (insert, select update)

<b>Action</b> - SQL command - insert, update

for more:

http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm

Regards,

michal

-

---

<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

[Former Member]

Hi,

Statement : sql statement which will be understand by JDBC,

table : this is optional , you can stright away use the table name as xml node.

or you would have to assign the table name to thi table xml element

Access : here we need to mension the structure of table

and key also

see below links

http://help.sap.com/saphelp_nw2004s/helpdata/en/64/ce4e886334ec4ea7c2712e11cc567c/content.htm

/people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn

/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30 - File to JDBC

/people/siva.maranani/blog/2005/09/16/xi-how-to-on-jdbc-receiver-response - XI: How-to on JDBC receiver response

Regards

Chilla

[Former Member]

Hi,

I am a bit confused at statement.

while defininig data type for element statement, do we need to pass sql query to statement.

or at mapping stage we need to pass any value.

Regards,

Jeff

[bhavesh_kantilal]

Jeff,

The input to the JDBC adapter is XML? Now how does the JDBC adapter insert the data into the database.

The JDBC adapter expects the data in a particular format ( the links pointed above show the formats for each type of action ) . it then converts this data into a SQL query that is used to trigger the call to the database.

The output of the mapping should confirm to the datatype given in the links above depending on what the action is.

You do not give the query directly, but give the parameters and thsi is converteed to a Query by the JDBC adapter

Regards

Bhavesh

[prateek]

Hi Jeff,

It is the task of JDBC adapter to generate the SQL statement. For this, the adapter requires the input data in the specified format (as i had provided earlier also) in the link.

http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm

<i>while defininig data type for element statement, do we need to pass sql query to statement.</i>

No, u need to pass just the input to JDBC adapter in the format specified above

<i>or at mapping stage we need to pass any value</i>

Yes, the values will b passed at mapping time

Regards,

Prateek