The JDBC adaptor was designed to allow use with any JDBC driver (hence any database that has a JDBC driver). However, the adaptor has to be certified with the JDBC driver as there can be some minor differences between drivers especially when it comes to the SQL they support and the metadata information they provide. We have certified the adaptor for Oracle, Sybase, JDataStore, MS SQLServer, Interbase and DB2 UDB.

Before making access to Db2 via JDBC, you MUST register the database using Client Configuration Assitant. The <database_name> should be the alias you specify when you register with Client Configuration Assitant. Since the database has been registered, you don't have to specify host name and port number for the vbroker.naming.url.

The following settings in the configuration file should be modifed as follows (we assume you use jdbc driver from weblogic):

You should start InterServer before accessing InterBase via JDBC. If the InterBase server resides on the local host, specify server as localhost; otherwise specify it as the host name. If the InterBase database resides on NT, specify the full_db_path as Driver:\\dir1\dir2\\db.gdb (the first backslash '\' is to escape the second baskslash '\'). If the InterBase database resides on Unix, specify the full_db_path as \dir1\dir2\db.gdb. You can get more information from www.interbase.com

If the JDataStore database resides on NT, the <full path of the JDataStore database> should be Driver:\\dir1\\dir2\\db.jds (the first backslash '\' is to escape the second backslash '\'). If the JDataStore database resides on UNIX, the <full path of the JDataStore database> should be /dir1/dir2/db.jds

Connection con = DriverManager.getConnection("jdbc:oracle:thin:@oracle.students.itee.uq.edu.au:1521:iteeo", "login", "password");

Provided the JAR file containing the driver is properly configured, just place the JAR file in the classpath. That's it. No need to manually load the class... For loading and registering a driver you should use Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"), but I have used JdbcOdbcDriver j=new JdbcOdbcDriver() and I still get a connection. Why is this so?... Using Class.forName will create and initialize an instance of the class you pass in as a paramter. So using Class.

Author: Lennart Jorelid (http://www.jguru.com/guru/viewbio.jsp?EID=15) Question originally posed by John Zukowski PREMIUM (http://www.jguru.com/guru/viewbio.jsp?EID=7 Longer answer: You may create a digitally signed applet using a Certicate to circumvent the security sandbox of the browser. See the Certificate jFAQ.

Author: John Zukowski (http://www.jguru.com/guru/viewbio.jsp?EID=7) Oracle basically has two JDBC drivers: an OCI driver which includes native code and a Thin driver which is 100% Pure Java. Since the OCI driver includes native code, it cannot be used in applets. You must use thin driver. You can get all Oracle JDBC drivers from http://technet.oracle.com/software/tech/java/sqlj_jdbc/software_index.htm.

The InMemory adaptor is very much faster than the JDBC adaptor. How much faster it is, depends on the underlying DataBase and JDBC driver used, and the operation being performed. For example, resolve operations using the JDBC adaptor with Sybase takes twice the time as that using the InMemory adaptor, while the JDBC adaptor with Oracle takes four times the time.

You should be able to improve performance by turning on the Caching facility and make it closer to the speeds achieved using the InMemory adaptor. However, care must be taken to ensure that it is the only Naming Server accessing the underlying data in the database. Inconsistency may result if this is not case. Though the performance of the optimised JDBC adaptor is much better than the JDBC adaptor, it is not always better to use the optimised JDBC adaptor.

No, the JDBC drivers are not included with VisiBroker. You will need to get your JDBC drivers from your database vendor. To get you started quickly, the Visibroker CD includes a development license for JDataStore.

Method 1: Set the Java property sql.drivers using the Java -D option. The sql.drivers property is defined as a colon-separated list of driver class names. For example: intersolv.jdbc.sequelink.SequeLinkDriver: The sql.drivers property can be set like other Java properties, using the -D option. For example: java -Dsql.drivers=intersolv.jdbc.sequelink. Method 2: Set the Java property sql.drivers from within your Java application or applet.

Rajkumar Seth offers the following: static void ftdsjdbc () { try { // use your hostname and port number here String url = "jdbc:freetds:sqlserver://nt1:1433/master"; String login = "sa"; // use your login here String password = "secret"; // use your password here if (false) { //Sybase url = "jdbc:freetds:sybase://unix1:4100/master"; login = "sa"; // use your login here password = "secret"; // use your password here } Class.forName("com.internetcds.jdbc.tds.

All databases supported by SequeLink 4.0, or higher, can be accessed through the SequeLink JDBC Driver. These include: The SequeLink JDBC Driver and SSL classes are packaged in the JAR files slje.jar and crysec.jar, which are located in the directory <installdir>/driver/classes. Copy these JAR files to your Web server and make sure that the JAR files are specified correctly in your HTML code using the codebase and archive tags in the applet tag.

No. DataDirect XQuery™ 3.0 provides an XQuery engine as well as XQJ API implementation. DataDirect XQuery™ 3.0 embeds the DataDirect JDBC drivers as part of the product for relational access.

JDataStore is a Pure Java ORDBMS and includes JDBC Type 4 Local and Remote Drivers. A development license for JDataStore is provided on the VisiBroker CD. The installation is fairly easy. You can look at the online guides that come with it. Please note that when you create a JDataStore database, you need to set/associate a transaction manager (TxManager) with it.

You will need to get your Sybase jConnect driver from www.sybase.com. (For our testing, we used Sybase ??? and Sybase jConnect 4.1/5.0. One important thing to note is that you need to run a script at the Sybase Database Server, to setup stored procedures which are required by the JDBC Driver when the DatabaseMetaData class is used. This class is used by the Naming Service at startup and if the Database Server is not set up properly, you will face problems.

We are using the type 4 JDBC driver from Oracle. You can download this driver from the Oracle website at technet.oracle.com or get it from the Oracle installation CD. Follow the instructions that come with the JDBC driver. It is fairly straight forward. We assume that the Oracle Host Server is 7.3.2 and above.