Skip to Content
author's profile photo
Former Member

JDBC connection to MS Access---Urgent

Hi

My problem is not yet solved.

I want to update the MS Access Table through XI

I have given the JDBC Driver as

<b>sun.jdbc.odbc.JdbcOdbcDriver</b>

and connection as

<b>jdbc:odbc:XIDSN</b>

But this give sme an error

<b>Receiver Adapter v1109 for Party '', Service 'TBIT40_MSACCESS_BS':

Configured at 11:59:37 2005-09-30

Processing Error: Accessing database connection 'jdbc:odbc:XIDSN' failed: java.sql.SQLException: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

Addtional information: JDBC driver 'sun.jdbc.odbc.JdbcOdbcDriver' loaded successfully, additional driver information:

Available JDBC drivers:

oracle.jdbc.driver.OracleDriver, 1.0 JDBC compliant

sun.jdbc.odbc.JdbcOdbcDriver, 2.1 JDBC compliant</b>

where XIDSN is my Data Source Name.

How does XI know where XIDSN is?

What should be the Connection that should be specified at the Integartion Directory of XI.

Please respond immediately..

Thanks in Advance

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • author's profile photo
    Former Member
    Sep 30, 2005 at 12:22 PM

    I guess u will have to create the DSN on the XI server to let XI know wheres ur MS-Access database.For JDBC-ODBC connections from Java I guess DSN are mandatory.

    Regards

    Rajeev

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Former Member
    Sep 30, 2005 at 04:52 PM

    Well, I guess you use Message Mapping for it?

    then the problem is the following:

    mapping works within J2EE engine container and it is done on the SERVER SIDE.

    Therefore yor SERVER environment should have ODBC entries for your MS Access database.

    Or you have to provide a host name in your DB URL like

    "jdbc:odbc://hostname/dbname"

    BTW. If your runtime works in linux or AIX environment that's the only chance to connect to ODBC driver as I know because OBDC is a windows protocol.

    Also if you have a cluster and you want to make this connection work on the server side you'll need to configure the same ODBC entries on each cluster node.

    Best regards,

    Dmitry Yankovsky

    Add comment
    10|10000 characters needed characters exceeded