From the Blogosphere
Setting the Driver Straight
I've been working on setting up a new environment for SAP IDM 7.1 SP5
Sep. 12, 2011 11:45 AM
I've been working on setting up a new environment for SAP IDM 7.1 SP5 (yes I know 6 is available). This installation is notable for me since I am configuring it around:
So it's my first pure 64-bit system. I'm pretty excited. I got the OS installed no problem. I got SQL installed. (I have to say, 2008R2 is probably the smoothest SQL install I've done since SQL Server 7. Very much a fan.) I got the IDM DesignTime and Runtime installs completed with no problems. I installed Java 1.6 and installed the 3.0 SQL Server drivers. Then the skies began to darken...
I kept getting driver not found errors when I went to test the dispatcher. Very frustrating! I tried regenerating the dispatcher scripts, tweaking the Java configuration from MMC, and even took a look a look at the dispatcher's .prop file and jdbcdefs.xml. Tweaking some of these shed some light on the issue, but did not bring complete success. That's when I started rethinking things and went back to basics.
First I hit up Google and did some searching on SQL Server 2008, JDBC drivers and related topics. Based on this I decided to roll back to the 2.0 SQL Server drivers and re-create the JDBC connection string. This time I installed the SQL Server 2005 option instead and I got a little closer. It seems that when one is using Java 1.6, the level 4 driver (sqljdbc4.jar) is required rather than the level 3 driver (sqljdbc.jar).
What kept throwing me off in this is that I was reading the options, and I read them too literally. What the SQL Server 2005 option should read is SQL Server 2005 and later... The connection string syntax and the driver name that is called see different starting with 2005.
I was able to confirm the level 3/4 driver issue when troubleshooting between the configuration on my various sandbox systems. My latest one is running 1.6 with sqljdbc4.jar and one of my older systems is using Java 1.5.
So to wrap it up, what I've found is this:
That's about it for the moment. I still need to install a trial version of NetWeaver to get the sandbox up and running.
Latest Cloud Developer Stories
Subscribe to the World's Most Powerful Newsletters
Subscribe to Our Rss Feeds & Get Your SYS-CON News Live!
SYS-CON Featured Whitepapers
Most Read This Week