WebLogic 8.1 The following database connection pool configuration and Tomcat, Resin, etc. have a relatively large difference, it seems that BEA is getting more and more M $, likes to standard. No way, who makes him a boss of Java App Server. hate.....
Take MS SQLServer 2K as an example. Open Console: http: // localhost: 7001 / console /, log in, select the Connection Pool below the JDBC. Then configure a new JDBC Connection Pool ...
The driver can select the type 4 of M $, which is the driver of M $ 4 JDBC usually used, so that the program makes it easier to transplant. Suppose is named Webcp, the database to access is WebcP:
Screen.width / 2) this.width = Screen.width / 2 "vSpace = 2 border = 0>
After the test connection is not a problem, you can deploy it to the server, usually deployed to myserver.
Then enter the Data Sources below JDBC, configure a new jdbc data source, where jndi name is the JNDI name you use when you query the pool, and set it to WebCP:
Screen.width / 2) this.width = Screen.width / 2 "vSpace = 2 border = 0>
Then select the connection pool you want to use in the next page, which is the WebCP we just configured. Then deploy it to myServer.掂. Try: context ctx = new initialContext (); object obj = ctx.lookup ("webcp"); DataSource DS = (Datasource) Obj; connection conn = ds.getConnection ();
One thing to note, the default access to SA defaults in SQL Server 2K is MATERS, which may cause problems. This is well resolved, you can modify the configuration of the connection pool, or you can also create a new database account.
Below is the configuration code in config.xml:
