During our installshield program, we are getting information from the user such as hostname, database name, etc. When next is pressed, we catalog the remote tcpip node and the database. We then attempt to validate the connection with a java class. The problem is this:
If we pass the java class a good hostname(node) it finds it fine and connects...if you pass it a bad hostname, we don't connect, send them back to the previous panel and uncatalog the db and node. We then recatalog the correct node and db and the connection fails. We suspect this is some kind of JDBC problem...has anyone ever run into this problem before? Is there some way to refresh the drivermanager (deregister driver did not work and db2 terminate did not help either) or the connection? Any and all help is appreciated.
If we pass the java class a good hostname(node) it finds it fine and connects...if you pass it a bad hostname, we don't connect, send them back to the previous panel and uncatalog the db and node. We then recatalog the correct node and db and the connection fails. We suspect this is some kind of JDBC problem...has anyone ever run into this problem before? Is there some way to refresh the drivermanager (deregister driver did not work and db2 terminate did not help either) or the connection? Any and all help is appreciated.