Originally posted by sharaf navas:
well MS Access is our client's datasource..and we cannot force them to go for even a lighter version's of DB's like mySQL etc. now we have decided to go with jdbc odbc thruogh websphere but still its a problem in configuring the JNDI for Webspere.. any suggestions for it ?
Configuring JDBC-ODBC in WebSphere; what have you tried? Or are you stuck where to begin?
I would add that Scott is right, that is quite an architectural mismatch, its going to hinder the operation of WebSphere a good bit I'd imagine. Why are they spending all that money on the most complex and configurable applciation server out there and spending next to nothing on the database behind it? If they are an MS house, SQL Server would seem to be a far better option.
JDBC-ODBC is not designed to be used in production. If your client is adamant, then I would consider convincing them of the need to pay for a better JDBC driver for Access (there are no free ones, but I understand there are better implemnetations than the one Sun provides).