Tomcat下连接池的创建及部署For DB2 ,ORACLE

1.一.Tomcat 下部署DB2连接池  
2.将db2安装目录C:\Program Files\IBM\SQLLIB\java下的common.jar,db2java.zip(改名成db2java.jar),db2jcc.jar拷贝到D:\Program Files\Tomcat 5.5\common\lib目录。  
3.修改D:\Program Files\Tomcat 5.5\conf下server.xml  
4.注意两个地方的内容:  
5.     <Resource name="jdbc/szfood" auth="Container"  
6.              type="javax.sql.DataSource" driverClassName="COM.ibm.db2.jdbc.net.DB2Driver"  
7.              url="jdbc:db2://localhost:6789/SZFOOD"  
8.              username="fuser" password="szfood0755" maxActive="20" maxIdle="10"  
9.              maxWait="-1"/>   
10.  
11.    <Context  docBase="E:\JAVA\WFStudy\szfood\WebRoot"  path=""  reloadable="true" >  
12.           <ResourceLink global="jdbc/szfood" name="jdbc/szfood" type="javax.sql.DataSource"/>  
13.        </Context>  
14.  
15.二.Tomcat下部署ORACLE连接池  
16.将oracle安装目录C:\oracle\product\10.2.0\db_1\jdbc\lib\classes12.jar拷贝到D:\Program Files\Tomcat 5.5\common\lib目录。  
17.修改D:\Program Files\Tomcat 5.5\conf下server.xml  
18.注意两个地方的内容:  
19.     <Resource name="jdbc/oracleds" auth="Container"  
20.              type="javax.sql.DataSource" driverClassName="oracle.jdbc.OracleDriver"  
21.              url="jdbc:oracle:thin:@127.0.0.1:1521:LWF"  
22.              username="scott" password="tiger" maxActive="100" maxIdle="30"  
23.              maxWait="10000"/>   
24.  
25.    <Context  docBase="C:\Documents and Settings\zqwf\workspace\Struts\WebRoot"  path="/Struts"  reloadable="true" >  
26.           <ResourceLink global="jdbc/oracleds" name="jdbc/oracleds" type="javax.sql.DataSource"/>  
27.        </Context>  

以下是示例server.xml文件内容：

1.<!-- Example Server Configuration File -->  
2.<!-- Note that component elements are nested corresponding to their  
3.     parent-child relationships with each other -->  
4.  
5.<!-- A "Server" is a singleton element that represents the entire JVM,  
6.     which may contain one or more "Service" instances.  The Server  
7.     listens for a shutdown command on the indicated port.  
8.  
9.     Note:  A "Server" is not itself a "Container", so you may not  
10.     define subcomponents such as "Valves" or "Loggers" at this level.  
11. -->  
12.  
13.<Server port="8005" shutdown="SHUTDOWN">  
14.  
15.  <!-- Comment these entries out to disable JMX MBeans support used for the   
16.       administration web application -->  
17.  <Listener className="org.apache.catalina.core.AprLifecycleListener" />  
18.  <Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" />  
19.  <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />  
20.  <Listener className="org.apache.catalina.storeconfig.StoreConfigLifecycleListener"/>  
21.  
22.  <!-- Global JNDI resources -->  
23.  <GlobalNamingResources>  
24.  
25.    <!-- Test entry for demonstration purposes -->  
26.    <Environment name="simpleValue" type="java.lang.Integer" value="30"/>  
27.  
28.    <!-- Editable user database that can also be used by  
29.         UserDatabaseRealm to authenticate users -->  
30.    <Resource name="UserDatabase" auth="Container"  
31.              type="org.apache.catalina.UserDatabase"  
32.       description="User database that can be updated and saved"  
33.           factory="org.apache.catalina.users.MemoryUserDatabaseFactory"  
34.          pathname="conf/tomcat-users.xml" />  
35.     <Resource name="jdbc/oracleds" auth="Container"  
36.              type="javax.sql.DataSource" driverClassName="oracle.jdbc.OracleDriver"  
37.              url="jdbc:oracle:thin:@127.0.0.1:1521:LWF"  
38.              username="scott" password="tiger" maxActive="100" maxIdle="30"  
39.              maxWait="10000"/>   
40.    <Resource name="jdbc/szfood" auth="Container"  
41.              type="javax.sql.DataSource" driverClassName="COM.ibm.db2.jdbc.net.DB2Driver"  
42.              url="jdbc:db2://localhost:6789/SZFOOD"  
43.              username="fuser" password="test" maxActive="20" maxIdle="10"  
44.              maxWait="-1"/>   
45.  </GlobalNamingResources>  
46.  
47.  <!-- A "Service" is a collection of one or more "Connectors" that share  
48.       a single "Container" (and therefore the web applications visible  
49.       within that Container).  Normally, that Container is an "Engine",  
50.       but this is not required.  
51.  
52.       Note:  A "Service" is not itself a "Container", so you may not  
53.       define subcomponents such as "Valves" or "Loggers" at this level.  
54.   -->  
55.  
56.  <!-- Define the Tomcat Stand-Alone Service -->  
57.  <Service name="Catalina">  
58.  
59.    <!-- A "Connector" represents an endpoint by which requests are received  
60.         and responses are returned.  Each Connector passes requests on to the  
61.         associated "Container" (normally an Engine) for processing.  
62.  
63.         By default, a non-SSL HTTP/1.1 Connector is established on port 8080.  
64.         You can also enable an SSL HTTP/1.1 Connector on port 8443 by  
65.         following the instructions below and uncommenting the second Connector  
66.         entry.  SSL support requires the following steps (see the SSL Config  
67.         HOWTO in the Tomcat 5 documentation bundle for more detailed  
68.         instructions):  
69.         * If your JDK version 1.3 or prior, download and install JSSE 1.0.2 or  
70.           later, and put the JAR files into "$JAVA_HOME/jre/lib/ext".  
71.         * Execute:  
72.             %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)  
73.             $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA  (Unix)  
74.           with a password value of "changeit" for both the certificate and  
75.           the keystore itself.  
76.  
77.         By default, DNS lookups are enabled when a web application calls  
78.         request.getRemoteHost().  This can have an adverse impact on  
79.         performance, so you can disable it by setting the  
80.         "enableLookups" attribute to "false".  When DNS lookups are disabled,  
81.         request.getRemoteHost() will return the String version of the  
82.         IP address of the remote client.  
83.    -->  
84.  
85.    <!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->  
86.    <Connector  
87.port="8080"               maxHttpHeaderSize="8192"  
88.               maxThreads="150" minSpareThreads="25" maxSpareThreads="75"  
89.               enableLookups="false" redirectPort="8443" acceptCount="100"  
90.               connectionTimeout="20000" disableUploadTimeout="true"  URIEncoding="UTF-8"/>  
91.    <!-- Note : To disable connection timeouts, set connectionTimeout value  
92.     to 0 -->  
93.      
94.    <!-- Note : To use gzip compression you could set the following properties :  
95.      
96.               compression="on"   
97.               compressionMinSize="2048"   
98.               noCompressionUserAgents="gozilla, traviata"   
99.               compressableMimeType="text/html,text/xml"  
100.    -->  
101.  
102.    <!-- Define a SSL HTTP/1.1 Connector on port 8443 -->  
103.    <!--  
104.    <Connector port="8443" maxHttpHeaderSize="8192"  
105.               maxThreads="150" minSpareThreads="25" maxSpareThreads="75"  
106.               enableLookups="false" disableUploadTimeout="true"  
107.               acceptCount="100" scheme="https" secure="true"  
108.               clientAuth="false" sslProtocol="TLS" />  
109.    -->  
110.  
111.    <!-- Define an AJP 1.3 Connector on port 8009 -->  
112.    <Connector port="8009"   
113.               enableLookups="false" redirectPort="8443" protocol="AJP/1.3" />  
114.  
115.    <!-- Define a Proxied HTTP/1.1 Connector on port 8082 -->  
116.    <!-- See proxy documentation for more information about using this. -->  
117.    <!--  
118.    <Connector port="8082"   
119.               maxThreads="150" minSpareThreads="25" maxSpareThreads="75"  
120.               enableLookups="false" acceptCount="100" connectionTimeout="20000"  
121.               proxyPort="80" disableUploadTimeout="true" />  
122.    -->  
123.  
124.    <!-- An Engine represents the entry point (within Catalina) that processes  
125.         every request.  The Engine implementation for Tomcat stand alone  
126.         analyzes the HTTP headers included with the request, and passes them  
127.         on to the appropriate Host (virtual host). -->  
128.  
129.    <!-- You should set jvmRoute to support load-balancing via AJP ie :  
130.    <Engine name="Standalone" defaultHost="localhost" jvmRoute="jvm1">           
131.    -->   
132.           
133.    <!-- Define the top level container in our container hierarchy -->  
134.    <Engine name="Catalina" defaultHost="localhost">  
135.  
136.      <!-- The request dumper valve dumps useful debugging information about  
137.           the request headers and cookies that were received, and the response  
138.           headers and cookies that were sent, for all requests received by  
139.           this instance of Tomcat.  If you care only about requests to a  
140.           particular virtual host, or a particular application, nest this  
141.           element inside the corresponding <Host> or <Context> entry instead.  
142.  
143.           For a similar mechanism that is portable to all Servlet 2.4  
144.           containers, check out the "RequestDumperFilter" Filter in the  
145.           example application (the source for this filter may be found in  
146.           "$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters").  
147.  
148.           Request dumping is disabled by default.  Uncomment the following  
149.           element to enable it. -->  
150.      <!--  
151.      <Valve className="org.apache.catalina.valves.RequestDumperValve"/>  
152.      -->  
153.  
154.      <!-- Because this Realm is here, an instance will be shared globally -->  
155.  
156.      <!-- This Realm uses the UserDatabase configured in the global JNDI  
157.           resources under the key "UserDatabase".  Any edits  
158.           that are performed against this UserDatabase are immediately  
159.           available for use by the Realm.  -->  
160.      <Realm className="org.apache.catalina.realm.UserDatabaseRealm"  
161.             resourceName="UserDatabase"/>  
162.  
163.      <!-- Comment out the old realm but leave here for now in case we  
164.           need to go back quickly -->  
165.      <!--  
166.      <Realm className="org.apache.catalina.realm.MemoryRealm" />  
167.      -->  
168.  
169.      <!-- Replace the above Realm with one of the following to get a Realm  
170.           stored in a database and accessed via JDBC -->  
171.  
172.      <!--  
173.      <Realm  className="org.apache.catalina.realm.JDBCRealm"  
174.             driverName="org.gjt.mm.mysql.Driver"  
175.          connectionURL="jdbc:mysql://localhost/authority"  
176.         connectionName="test" connectionPassword="test"  
177.              userTable="users" userNameCol="user_name" userCredCol="user_pass"  
178.          userRoleTable="user_roles" roleNameCol="role_name" />  
179.      -->  
180.  
181.      <!--  
182.      <Realm  className="org.apache.catalina.realm.JDBCRealm"  
183.             driverName="oracle.jdbc.driver.OracleDriver"  
184.          connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL"  
185.         connectionName="scott" connectionPassword="tiger"  
186.              userTable="users" userNameCol="user_name" userCredCol="user_pass"  
187.          userRoleTable="user_roles" roleNameCol="role_name" />  
188.      -->  
189.  
190.      <!--  
191.      <Realm  className="org.apache.catalina.realm.JDBCRealm"  
192.             driverName="sun.jdbc.odbc.JdbcOdbcDriver"  
193.          connectionURL="jdbc:odbc:CATALINA"  
194.              userTable="users" userNameCol="user_name" userCredCol="user_pass"  
195.          userRoleTable="user_roles" roleNameCol="role_name" />  
196.      -->  
197.  
198.      <!-- Define the default virtual host  
199.           Note: XML Schema validation will not work with Xerces 2.2.  
200.       -->  
201.      <Host name="localhost" appBase="webapps"  
202.       unpackWARs="true" autoDeploy="true"  
203.       xmlValidation="false" xmlNamespaceAware="false">  
204.  
205.        <!-- Defines a cluster for this node,  
206.             By defining this element, means that every manager will be changed.  
207.             So when running a cluster, only make sure that you have webapps in there  
208.             that need to be clustered and remove the other ones.  
209.             A cluster has the following parameters:  
210.  
211.             className = the fully qualified name of the cluster class  
212.  
213.             name = a descriptive name for your cluster, can be anything  
214.  
215.             mcastAddr = the multicast address, has to be the same for all the nodes  
216.  
217.             mcastPort = the multicast port, has to be the same for all the nodes  
218.               
219.             mcastBindAddr = bind the multicast socket to a specific address  
220.               
221.             mcastTTL = the multicast TTL if you want to limit your broadcast  
222.               
223.             mcastSoTimeout = the multicast readtimeout   
224.  
225.             mcastFrequency = the number of milliseconds in between sending a "I'm alive" heartbeat  
226.  
227.             mcastDropTime = the number a milliseconds before a node is considered "dead" if no heartbeat is received  
228.  
229.             tcpThreadCount = the number of threads to handle incoming replication requests, optimal would be the same amount of threads as nodes   
230.  
231.             tcpListenAddress = the listen address (bind address) for TCP cluster request on this host,   
232.                                in case of multiple ethernet cards.  
233.                                auto means that address becomes  
234.                                InetAddress.getLocalHost().getHostAddress()  
235.  
236.             tcpListenPort = the tcp listen port  
237.  
238.             tcpSelectorTimeout = the timeout (ms) for the Selector.select() method in case the OS  
239.                                  has a wakup bug in java.nio. Set to 0 for no timeout  
240.  
241.             printToScreen = true means that managers will also print to std.out  
242.  
243.             expireSessionsOnShutdown = true means that   
244.  
245.             useDirtyFlag = true means that we only replicate a session after setAttribute,removeAttribute has been called.  
246.                            false means to replicate the session after each request.  
247.                            false means that replication would work for the following piece of code: (only for SimpleTcpReplicationManager)  
248.                            <%  
249.                            HashMap map = (HashMap)session.getAttribute("map");  
250.                            map.put("key","value");  
251.                            %>  
252.             replicationMode = can be either 'pooled', 'synchronous' or 'asynchronous'.  
253.                               * Pooled means that the replication happens using several sockets in a synchronous way. Ie, the data gets replicated, then the request return. This is the same as the 'synchronous' setting except it uses a pool of sockets, hence it is multithreaded. This is the fastest and safest configuration. To use this, also increase the nr of tcp threads that you have dealing with replication.  
254.                               * Synchronous means that the thread that executes the request, is also the  
255.                               thread the replicates the data to the other nodes, and will not return until all  
256.                               nodes have received the information.  
257.                               * Asynchronous means that there is a specific 'sender' thread for each cluster node,  
258.                               so the request thread will queue the replication request into a "smart" queue,  
259.                               and then return to the client.  
260.                               The "smart" queue is a queue where when a session is added to the queue, and the same session  
261.                               already exists in the queue from a previous request, that session will be replaced  
262.                               in the queue instead of replicating two requests. This almost never happens, unless there is a   
263.                               large network delay.  
264.        -->               
265.        <!--  
266.            When configuring for clustering, you also add in a valve to catch all the requests  
267.            coming in, at the end of the request, the session may or may not be replicated.  
268.            A session is replicated if and only if all the conditions are met:  
269.            1. useDirtyFlag is true or setAttribute or removeAttribute has been called AND  
270.            2. a session exists (has been created)  
271.            3. the request is not trapped by the "filter" attribute  
272.  
273.            The filter attribute is to filter out requests that could not modify the session,  
274.            hence we don't replicate the session after the end of this request.  
275.            The filter is negative, ie, anything you put in the filter, you mean to filter out,  
276.            ie, no replication will be done on requests that match one of the filters.  
277.            The filter attribute is delimited by ;, so you can't escape out ; even if you wanted to.  
278.  
279.            filter=".*\.gif;.*\.js;" means that we will not replicate the session after requests with the URI  
280.            ending with .gif and .js are intercepted.  
281.              
282.            The deployer element can be used to deploy apps cluster wide.  
283.            Currently the deployment only deploys/undeploys to working members in the cluster  
284.            so no WARs are copied upons startup of a broken node.  
285.            The deployer watches a directory (watchDir) for WAR files when watchEnabled="true"  
286.            When a new war file is added the war gets deployed to the local instance,  
287.            and then deployed to the other instances in the cluster.  
288.            When a war file is deleted from the watchDir the war is undeployed locally   
289.            and cluster wide  
290.        -->  
291.          
292.        <!--  
293.        <Cluster className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"  
294.                 managerClassName="org.apache.catalina.cluster.session.DeltaManager"  
295.                 expireSessionsOnShutdown="false"  
296.                 useDirtyFlag="true"  
297.                 notifyListenersOnReplication="true">  
298.  
299.            <Membership   
300.                className="org.apache.catalina.cluster.mcast.McastService"  
301.                mcastAddr="228.0.0.4"  
302.                mcastPort="45564"  
303.                mcastFrequency="500"  
304.                mcastDropTime="3000"/>  
305.  
306.            <Receiver   
307.                className="org.apache.catalina.cluster.tcp.ReplicationListener"  
308.                tcpListenAddress="auto"  
309.                tcpListenPort="4001"  
310.                tcpSelectorTimeout="100"  
311.                tcpThreadCount="6"/>  
312.  
313.            <Sender  
314.                className="org.apache.catalina.cluster.tcp.ReplicationTransmitter"  
315.                replicationMode="pooled"  
316.                ackTimeout="15000"/>  
317.  
318.            <Valve className="org.apache.catalina.cluster.tcp.ReplicationValve"  
319.                   filter=".*\.gif;.*\.js;.*\.jpg;.*\.htm;.*\.html;.*\.txt;"/>  
320.                     
321.            <Deployer className="org.apache.catalina.cluster.deploy.FarmWarDeployer"  
322.                      tempDir="/tmp/war-temp/"  
323.                      deployDir="/tmp/war-deploy/"  
324.                      watchDir="/tmp/war-listen/"  
325.                      watchEnabled="false"/>  
326.        </Cluster>  
327.        -->          
328.  
329.  
330.  
331.        <!-- Normally, users must authenticate themselves to each web app  
332.             individually.  Uncomment the following entry if you would like  
333.             a user to be authenticated the first time they encounter a  
334.             resource protected by a security constraint, and then have that  
335.             user identity maintained across *all* web applications contained  
336.             in this virtual host. -->  
337.        <!--  
338.        <Valve className="org.apache.catalina.authenticator.SingleSignOn" />  
339.        -->  
340.  
341.        <!-- Access log processes all requests for this virtual host.  By  
342.             default, log files are created in the "logs" directory relative to  
343.             $CATALINA_HOME.  If you wish, you can specify a different  
344.             directory with the "directory" attribute.  Specify either a relative  
345.             (to $CATALINA_HOME) or absolute path to the desired directory.  
346.        -->  
347.        <!--  
348.        <Valve className="org.apache.catalina.valves.AccessLogValve"  
349.                 directory="logs"  prefix="localhost_access_log." suffix=".txt"  
350.                 pattern="common" resolveHosts="false"/>  
351.        -->  
352.  
353.        <!-- Access log processes all requests for this virtual host.  By  
354.             default, log files are created in the "logs" directory relative to  
355.             $CATALINA_HOME.  If you wish, you can specify a different  
356.             directory with the "directory" attribute.  Specify either a relative  
357.             (to $CATALINA_HOME) or absolute path to the desired directory.  
358.             This access log implementation is optimized for maximum performance,  
359.             but is hardcoded to support only the "common" and "combined" patterns.  
360.        -->  
361.        <!--  
362.        <Valve className="org.apache.catalina.valves.FastCommonAccessLogValve"  
363.                 directory="logs"  prefix="localhost_access_log." suffix=".txt"  
364.                 pattern="common" resolveHosts="false"/>  
365.     -->  
366.        <Context  docBase="E:\JAVA\WFStudy\szfood\WebRoot"  path=""  reloadable="true" >  
367.           <ResourceLink global="jdbc/szfood" name="jdbc/szfood" type="javax.sql.DataSource"/>  
368.        </Context>  
369.     
370.        <Context  docBase="C:\Documents and Settings\zqwf\workspace\Struts\WebRoot"  path="/Struts"  reloadable="true" >  
371.           <ResourceLink global="jdbc/oracleds" name="jdbc/oracleds" type="javax.sql.DataSource"/>  
372.        </Context>  
373.  
374.      </Host>  
375.  
376.    </Engine>  
377.  
378.  </Service>  
379.  
380.</Server

eg：Eclipse + Tomcat + sql server2005 配置数据连接池
1.Eclipse升级j2ee ,D:\j2ee\Tomcat 5.5\common\lib 中加入数据据包：sqljdbc.jar

2.建一Hello工程，lk加入sqljdbc.jar的包，运行run on server

3.编写

DBPool.java

package com.zd.test;


import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.sql.DataSource;

public class DBPool {
      private static DataSource pool;
      static {
           Context env = null;
            try {
                env = (Context) new InitialContext().lookup("java:comp/env");
                pool = (DataSource)env.lookup("jdbc/tkbTestDB");
                if(pool==null)
                    System.err.println("'DBPool' is an unknown DataSource");
                 } catch(NamingException ne) {
                    ne.printStackTrace();
            }
        }
      public static DataSource getPool() {
          return pool;
      }
}

4.eclipse / servers / tomcat/ server.xml 的</host>加入：

  

<Context docBase="Hello" path="/Hello" reloadable="true" source="org.eclipse.jst.j2ee.server:Hello">
      <Resource driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver" maxActive="100" maxIdle="10" maxWait="3000" name="jdbc/TestDB" scope="Shareable" type="javax.sql.DataSource" url="jdbc:sqlserver://192.168.1.27:1433;DatabaseName=xxx;user=sa;password=sa123"/>

5. Hello项目中的web.xml 的</web-app>前加入

<resource-ref>
    <description>JNDI JDBC DataSource</description>
    <res-ref-name>jdbc/tkbTestDB</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
</resource-ref>

6.测试xx.jsp文件。
 

<%@ page contentType="text/html; charset=big5" %>
<%@ page import="com.zd.test.DBPool"%>

<%
java.sql.Connection Conn;
java.sql.Statement Stmt;
java.sql.ResultSet rs=null;

Conn =DBPool.getPool().getConnection();
Stmt=Conn.createStatement();
rs=Stmt.executeQuery("select * from userprofile");

while(rs.next()){
    out.println(rs.getString("Name")+"<br>");
}
Conn.close();

%>
OK

7. 停止Eclipse中的tomcat服务，在D:\j2ee\Tomcat 5.5\conf/server.xml,加入：
<Context
            docBase="D:/workspace/Hello/WebContent"
            path="/Hello"
            reloadable="true">
          <Resource
            name="jdbc/TestDB"
            type="javax.sql.DataSource"
            maxActive="100"
            maxIdle="10"
            maxWait="3000"
            driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver"
            url="jdbc:sqlserver://192.168.1.27:1433;DatabaseName=xxx;user=sa;password=sa123"/>
        </Context>

这样，在tomcat外面启动，就可以访问数据库了。