All Examples
This package contains sample applets and standalone applications that illustrate various JDBC programming tasks with WebLogic jDriver for Microsoft SQL Server.
You should test your connection to SQL Server with the dbping utility before you attempt to use the examples.
When executing stored procedures with JDBC, all results sets and update counts must be processed before you can retrieve the values of output parameters. Executing a single CallableStatement can cause multiple result sets and update counts. All of these result sets and update counts must be processed before you can retrieve the value of an output parameter.
This test also serves as a performance test for the JDBC driver, the middle ware used (if any), and the SQL Server itself. If you are performance conscious, compare other JDBC drivers to WebLogic jDriver for Microsoft SQL Server using this test.
The number of threads and connections used can be varied by changing the constant values in the ThreadsTests.java file. If the test fails to open all the connections you may have reached the maximum number of concurrent clients allowed by your SQL Server (this could be limited by your SQL Server license).
Set the CLASSPATH environment variable in that shell to include weblogic\mssqlserver4\classes.
For example (Windows NT):
$ set CLASSPATH=%CLASSPATH%;c:\weblogic\mssqlserver4\classesWhere weblogic is the directory where you installed WebLogic jDriver for Microsoft SQL Server.
$ javac -d c:\weblogic\mssqlserver4\classes *.java
Where c:\weblogic is the path to the directory where you installed WebLogic jDriver for Microsoft SQL Server.
$ java examples.jdbc.mssqlserver4.className
For testing, you can use appletviewer, which is included in the JDK. appletviewer does not have the security restrictions. For example:
appletviewer className.htmlSee Using WebLogic jDriver for Microsoft SQL Server for more information about applets and browser security.