|
WebLogic Server 6.0 Code Examples, BEA Systems, Inc. |
See:
Description
Class Summary | |
complexproc | This example shows the correct method of retrieving rows, update counts, procedure status, and/or output parameters from complex stored procedures that may have multiples of them. |
exsql | This simple example shows how JDBC Extended SQL can be embedded in standard SQL sent to the DBMS. |
LargeTableTests | This example creates a large table, retrieves its contents, and then deletes the table. |
login | This simple example shows the alternatives for making a JDBC connection to a MSSQLServer instance. |
ProcedureTests | This example shows how to create, call and remove a stored procedure from a Microsoft SQL Server. |
ReadingThread | The threads created by ThreadTests execute this class. |
records | This simple example shows how JDBC can be used to execute DDL and DML. |
simpleselect | This simple example shows how data and result set metadata are selected with JDBC. |
simplesql | This simple example shows how to execute DDL and DML using JDBC. |
storedprocs | This simple example shows how to create and execute stored procedures, and get the results. |
ThreadsTests | This example creates n database connections and runs n threads on each. |
Timer | Timer objects track elapsed time. |
This package contains standalone applications that illustrate various JDBC programming tasks with WebLogic jDriver for Microsoft SQL Server.
We recommend that you test the connection to SQL Server with the dbping utility before you attempt to use the examples.
This package contains the following 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).
To build and run this package follow the instructions provided with each example.
|
Documentation is available at http://e-docs.bea.com/wls/docs60 |