LSN JDBC connection fails on LSF9

 6 Replies
 0 Subscribed to this topic
 14 Subscribed to this forum
Sort:
Author
Messages
Joe O'Toole
Veteran Member Send Private Message
Posts: 314
Veteran Member

We migrated our Smart Notification from our Env 8.03 server to LSF9 but the connection tests for the JDBC data souce fail on the new box (DME connections test ok). We think all the SQL and JDBC settings are correct but the LSN install validator still reports Tomcat for the connection. Aside from moving from LSN 3.X to 9.X the only other fundemental difference is that LSN 9 is being serviced by Websphere while LSN 3 was using Tomcat. Has anyone else run into this or know how to point LSN at Websphere?

John Henley
Send Private Message
Posts: 3351
<!-- Converted from text/plain format -->

What database are you using? I remember running into a similar situation with MSSQL and had to devise a workaround...

Thanks for using the LawsonGuru.com forums!
John
Joe O'Toole
Veteran Member Send Private Message
Posts: 314
Veteran Member

MS SQL 2000

Joe O'Toole
Veteran Member Send Private Message
Posts: 314
Veteran Member

After looking at this again, step 6 (JDBC driver location) in the LSN validator say's "Tomcat only test - not performed". I may have misinterpreted this message. At any rate, the connection test fails.

John Henley
Send Private Message
Posts: 3351
<!-- Converted from text/plain format -->

You're probably hitting the same error I ran into, as it sounds like the same error.  I will look for my workaround and post it.

Thanks for using the LawsonGuru.com forums!
John
John Henley
Send Private Message
Posts: 3351

The problem I ran into was after LSN/LBI was installed, when I tried to create a datasource/infoset using JNDI, which didn't work using the MSSQL provider built into Websphere.

BTW, I'm moving this thread to the SmartNotification forum..

Thanks for using the LawsonGuru.com forums!
John
Joe O'Toole
Veteran Member Send Private Message
Posts: 314
Veteran Member
John,
We found that many of the JDBC settings are stored within Websphere so you can create a JNDI connection in LSN that is much simpler. Once we defined the JNDI datasource, our connection test worked. Now all we need to do is verify that the SQL code used in our SN's still work with the new connection type.
Joe