cancel
Showing results for 
Search instead for 
Did you mean: 

JDBC Receiver Adapter Communication channel

Former Member
0 Kudos

HI,

i am using these parameters for jdbc receiver could you tell me is it correct

JDBC DRIVER: com.microsoft.jdbc.sqlserver.SQLServerDriver

Connection: 172.16.7.218\SQLDES; DatabaseName=SAPCOBAN

when i execute it there are not errors.

i can see a message processed successfully bu ti doesnt update in database.

could you tell me what is the issue.

Jeff

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Jeff -

First, please confirm that you have deployed the necessary MS SQL Server drivers to XI's j2ee engine. If not, follow the following guide: <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bf4b1055-0d01-0010-32a3-b3848d77a6b9">How to Install and Configure External Drivers for JDBC & JMS Adapters</a>.

Otherwise, your JDBC DRIVER looks good. For Connection, try the following:

jdbc:microsoft:sqlserver://172.16.7.218:1433;databaseName=SAPCOBAN

Assumes port is using 1433 default.

Regards,

Jin

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

Here two situations may be happened ,

-empty values are inserted check

- commit is not going check.

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

Regards

Chilla

Former Member
0 Kudos

I'm not sure exactly what the connection information for the MS SQL is, but I know that when I have done JDBC reciever adapters the communication channel would give me an error (in Communication Channel Monitoring - runtime workbench) instead of saying the message was successful.

I would try copying the SQL command that XI is generating and running in manually to test if it's actually working. If it's not working it's possible there is an error with your mapping or the structure of your receiving message type.

If you haven't already, try turning on the SQL command logging:

<i>Use the parameter

logSQLStatement true

in your receiver JDBC comm channel. Click on Advanced properties and enter this parameter with value true.</i>

That way you can figure out if the command is actually working, so you can determine whether or not the error exists in the driver parameters.