Strange problem with connection to Integrator Server

Question

Hi,
I have a strange problem with making a connection to my Integrator Server.
I have one workspace folder that I share between Integrator version 2.4 and 3.0 (I have several versions installed for testing purposes)
When I try to create a new Integrator Server Project in Integrator Designer I get this nice 'Connect to CloverETL Server' panel.
By default: the connection URL is http://localhost:8080/clover. So by default Integrator Designer wants to connect to my 2.4 Integrator Server.
When I change this to http://localhost:8301/clover by using the drop-down box and fill in my credentials everything is looking fine. I click Next.
The problem now is that every time I switch to the next or previous configuration windows the connection is reset to the default http://localhost:8080/clover.
So it seems like Integrator Designer resets the CloverETL Server URL each time I switch to a different configuration window by using NEXT or BACK.
The problem occurs in both versions of Integrator Designer.
Does anybody know that the problem is? Can I change the default URL to my 3.0 Integrator Server?
Greetings,
Marcow
Edited by: Marco Snels (AortaBI)(NL) on 31-mei-2013 4:59

Answer 1

I'm using iPlanet App server as well and experiencing similar problem. I load my SQL Server driver by Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver"), then use DriverManager.getDriver() to obtain the Driver.
However, the Driver returned is not the SQLServerDriver as expected. The Driver returned is com.netscape.server.jdbc.Driver! And then when I do Driver.getConnection("jdbc:microsoft:sqlserver://MyServer"), it throws an SQLException saying that it doesn't accept a jdbc:microsoft:sqlserver subprotocol. Well, of course it doesn't, it's not a microsoft Driver at all.
I suspect the problem is that the netscape Driver's acceptsURL() method ALWAYS returns true in iPlanet app server, thus when you getDriver(), the netscape Driver is always returned (and always returned as the first one since it's default?). Thus even though the same piece of code works fine as a standalone application, it just doesn't work on iPlanet app server.
My work around is:
Class.forName("my.Driver");
Enumeration enu = DriverManager.getDrivers();
Driver useThis = null;
while (enu.hasMoreElements()) {
Driver d = (Driver)enu.nextElement();
if (d.getClass().toString().indexOf("my.Driver") > -1) {
useThis = d;
Mind that my above code does not have an performance issue. If you look into the source code of how DriverManager get a Driver for a particular URL, it also loads the whole set of available Drivers, then call acceptsURL() method on each of them to find the first "suitable" one. Thus time complexity is the same.
I know this is not a very elegant solution and it defeats the purpose of having a DriverManager. Does any one else has a better way to solve this problem, like a way to specify the priority of each Driver so that SQLServerDriver is returned before the netscape Driver?
Thanks a lot.