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.

No. Even though the 8.1.x JDBC drivers are backward compatible to 8.0.x databases, they require an 8.1.x database to support SQL object features. In a configuration using an 8.1.x driver and 8.0.x database, you might be able to compile a SQLJ application that uses SQL objects, but it will not work at runtime.

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.

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

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

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

Java database programming requires some relatively complicated classpath and database-specific configuration and class loading which are explained elsewhere. This example focuses on creating and executing an SQL insert statement using a PreparedStatement, with values taken from command line parameters. It uses a fixed database driver class name, database URL, user name and password for simplicity.

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

Please visit the Connection Wizard section in the Load JDBC Driver and Get Connected document. 4.4 "No suitable driver" error message The "No suitable driver" status may appear in the Connection Message in the Connection tab: No suitable driver. This message indicates that none of the currently loaded driver can setup the connection based on the specified Database URL. The reason is either that the needed driver is not loaded or that the Database URL is invalid in its syntax.

The "No suitable driver" status may appear in the Connection Message in the Connection tab: No suitable driver. There is no driver that can handle a connection for the specified URL. The most common reason is that the driver is not loaded in the Driver Manager. Also make sure the URL is correct spelled. This message indicates that none of the currently loaded driver can setup the connection based on the specified Database URL.

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.

The standard import statement makes a class available to the importing class to use its public variables and method calls. It is certainly possible to import specific JDBC driver implementations and use them in the same way, provided they are available on the application's classpath. However, the Java SQL package and JDBC scheme has been designed to deal with database interfaces in a generic way that is not tied to any single driver implementation.

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 simplest solution is to use the JDBCâ?¢ subprotocol "inetpool". You need to change the subprotocol in your source code (sample PooledDriver.java), only. You can create a DataSource and call a pool manager. You can use the pool manager i-net Plexaâ?¢ (sample WithPoolManager.java) You can request a DataSource from a directory and call a pool manager (sample WithJndiAndPoolManager.java)

Yes, you do. JMS is also a XAResource that participates in the distributed transaction. Therefore, there are two resources participating in the distributed transaction, and a 2PC license is needed.

If your JDBC driver is not included in the list of drivers in the question about JDBC databases supported by WebLogic JMS, then the tables required by JMS must be created manually. Note: WebLogic Server only guarantees support for the JDBC drivers included in the previous list. Support for any other JDBC driver is not guaranteed. The .ddl files located in the weblogic/jms/ddl directory of the weblogic.jar file may be used as templates.

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.

Generally, it is recommended that Oracle Connection Manager be used to proxy your connections through the firewall. You open up a port designated to be used by the Oracle Connection Manager, and let it handle the rest. You should not directly open up any port that the database listener is using, like port 1521. Please refer to the Oracle Net Services Administrator's Guide for how to configure Oracle Connection Manager.

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.

The JDBC Driver interface provides vendor-specific implementations of the abstract classes provided by the JDBC API. Each vendors driver must provide implementations of the java.sql.Connection,Statement,PreparedStatement, CallableStatement, ResultSet and Driver.

The procedures for removing and regenerating the JDBC store tables or creating the database tables manually are described in detail in JDBC Database Utility in Programming WebLogic JMS.

The thin JDBC Driver has been tested with Netscape Navigator 4.06 and 4.5. It has also been tested with Internet Explorer 3.0. However, in order to use the thin JDBC Driver with Netscape Navigator 3.0, the web server and the database server need to be located on the same machine. This is because of security considerations associated with JDK 1.0.2 signed applets. The communication between an applet that uses the Thin JDBC driver and the Oracle database happens over Java TCP/IP sockets.

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.