`

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

阅读更多
一.Tomcat 下部署DB2连接池
将db2安装目录C:\Program Files\IBM\SQLLIB\java下的common.jar,db2java.zip(改名成db2java.jar),db2jcc.jar拷贝到D:\Program Files\Tomcat 5.5\common\lib目录。
修改D:\Program Files\Tomcat 5.5\conf下server.xml
注意两个地方的内容:
	 <Resource name="jdbc/szfood" auth="Container"
              type="javax.sql.DataSource" driverClassName="COM.ibm.db2.jdbc.net.DB2Driver"
              url="jdbc:db2://localhost:6789/SZFOOD"
              username="fuser" password="szfood0755" maxActive="20" maxIdle="10"
              maxWait="-1"/> 

	<Context  docBase="E:\JAVA\WFStudy\szfood\WebRoot"  path=""  reloadable="true" >
           <ResourceLink global="jdbc/szfood" name="jdbc/szfood" type="javax.sql.DataSource"/>
        </Context>

二.Tomcat下部署ORACLE连接池
将oracle安装目录C:\oracle\product\10.2.0\db_1\jdbc\lib\classes12.jar拷贝到D:\Program Files\Tomcat 5.5\common\lib目录。
修改D:\Program Files\Tomcat 5.5\conf下server.xml
注意两个地方的内容:
	 <Resource name="jdbc/oracleds" auth="Container"
              type="javax.sql.DataSource" driverClassName="oracle.jdbc.OracleDriver"
              url="jdbc:oracle:thin:@127.0.0.1:1521:LWF"
              username="scott" password="tiger" maxActive="100" maxIdle="30"
              maxWait="10000"/> 

	<Context  docBase="C:\Documents and Settings\zqwf\workspace\Struts\WebRoot"  path="/Struts"  reloadable="true" >
           <ResourceLink global="jdbc/oracleds" name="jdbc/oracleds" type="javax.sql.DataSource"/>
        </Context>

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

<!-- Example Server Configuration File -->
<!-- Note that component elements are nested corresponding to their
     parent-child relationships with each other -->

<!-- A "Server" is a singleton element that represents the entire JVM,
     which may contain one or more "Service" instances.  The Server
     listens for a shutdown command on the indicated port.

     Note:  A "Server" is not itself a "Container", so you may not
     define subcomponents such as "Valves" or "Loggers" at this level.
 -->

<Server port="8005" shutdown="SHUTDOWN">

  <!-- Comment these entries out to disable JMX MBeans support used for the 
       administration web application -->
  <Listener className="org.apache.catalina.core.AprLifecycleListener" />
  <Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" />
  <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
  <Listener className="org.apache.catalina.storeconfig.StoreConfigLifecycleListener"/>

  <!-- Global JNDI resources -->
  <GlobalNamingResources>

    <!-- Test entry for demonstration purposes -->
    <Environment name="simpleValue" type="java.lang.Integer" value="30"/>

    <!-- Editable user database that can also be used by
         UserDatabaseRealm to authenticate users -->
    <Resource name="UserDatabase" auth="Container"
              type="org.apache.catalina.UserDatabase"
       description="User database that can be updated and saved"
           factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
          pathname="conf/tomcat-users.xml" />
	 <Resource name="jdbc/oracleds" auth="Container"
              type="javax.sql.DataSource" driverClassName="oracle.jdbc.OracleDriver"
              url="jdbc:oracle:thin:@127.0.0.1:1521:LWF"
              username="scott" password="tiger" maxActive="100" maxIdle="30"
              maxWait="10000"/> 
	<Resource name="jdbc/szfood" auth="Container"
              type="javax.sql.DataSource" driverClassName="COM.ibm.db2.jdbc.net.DB2Driver"
              url="jdbc:db2://localhost:6789/SZFOOD"
              username="fuser" password="test" maxActive="20" maxIdle="10"
              maxWait="-1"/> 
  </GlobalNamingResources>

  <!-- A "Service" is a collection of one or more "Connectors" that share
       a single "Container" (and therefore the web applications visible
       within that Container).  Normally, that Container is an "Engine",
       but this is not required.

       Note:  A "Service" is not itself a "Container", so you may not
       define subcomponents such as "Valves" or "Loggers" at this level.
   -->

  <!-- Define the Tomcat Stand-Alone Service -->
  <Service name="Catalina">

    <!-- A "Connector" represents an endpoint by which requests are received
         and responses are returned.  Each Connector passes requests on to the
         associated "Container" (normally an Engine) for processing.

         By default, a non-SSL HTTP/1.1 Connector is established on port 8080.
         You can also enable an SSL HTTP/1.1 Connector on port 8443 by
         following the instructions below and uncommenting the second Connector
         entry.  SSL support requires the following steps (see the SSL Config
         HOWTO in the Tomcat 5 documentation bundle for more detailed
         instructions):
         * If your JDK version 1.3 or prior, download and install JSSE 1.0.2 or
           later, and put the JAR files into "$JAVA_HOME/jre/lib/ext".
         * Execute:
             %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)
             $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA  (Unix)
           with a password value of "changeit" for both the certificate and
           the keystore itself.

         By default, DNS lookups are enabled when a web application calls
         request.getRemoteHost().  This can have an adverse impact on
         performance, so you can disable it by setting the
         "enableLookups" attribute to "false".  When DNS lookups are disabled,
         request.getRemoteHost() will return the String version of the
         IP address of the remote client.
    -->

    <!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->
    <Connector
port="8080"               maxHttpHeaderSize="8192"
               maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
               enableLookups="false" redirectPort="8443" acceptCount="100"
               connectionTimeout="20000" disableUploadTimeout="true"  URIEncoding="UTF-8"/>
    <!-- Note : To disable connection timeouts, set connectionTimeout value
     to 0 -->
	
	<!-- Note : To use gzip compression you could set the following properties :
	
			   compression="on" 
			   compressionMinSize="2048" 
			   noCompressionUserAgents="gozilla, traviata" 
			   compressableMimeType="text/html,text/xml"
	-->

    <!-- Define a SSL HTTP/1.1 Connector on port 8443 -->
    <!--
    <Connector port="8443" maxHttpHeaderSize="8192"
               maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
               enableLookups="false" disableUploadTimeout="true"
               acceptCount="100" scheme="https" secure="true"
               clientAuth="false" sslProtocol="TLS" />
    -->

    <!-- Define an AJP 1.3 Connector on port 8009 -->
    <Connector port="8009" 
               enableLookups="false" redirectPort="8443" protocol="AJP/1.3" />

    <!-- Define a Proxied HTTP/1.1 Connector on port 8082 -->
    <!-- See proxy documentation for more information about using this. -->
    <!--
    <Connector port="8082" 
               maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
               enableLookups="false" acceptCount="100" connectionTimeout="20000"
               proxyPort="80" disableUploadTimeout="true" />
    -->

    <!-- An Engine represents the entry point (within Catalina) that processes
         every request.  The Engine implementation for Tomcat stand alone
         analyzes the HTTP headers included with the request, and passes them
         on to the appropriate Host (virtual host). -->

    <!-- You should set jvmRoute to support load-balancing via AJP ie :
    <Engine name="Standalone" defaultHost="localhost" jvmRoute="jvm1">         
    --> 
         
    <!-- Define the top level container in our container hierarchy -->
    <Engine name="Catalina" defaultHost="localhost">

      <!-- The request dumper valve dumps useful debugging information about
           the request headers and cookies that were received, and the response
           headers and cookies that were sent, for all requests received by
           this instance of Tomcat.  If you care only about requests to a
           particular virtual host, or a particular application, nest this
           element inside the corresponding <Host> or <Context> entry instead.

           For a similar mechanism that is portable to all Servlet 2.4
           containers, check out the "RequestDumperFilter" Filter in the
           example application (the source for this filter may be found in
           "$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters").

           Request dumping is disabled by default.  Uncomment the following
           element to enable it. -->
      <!--
      <Valve className="org.apache.catalina.valves.RequestDumperValve"/>
      -->

      <!-- Because this Realm is here, an instance will be shared globally -->

      <!-- This Realm uses the UserDatabase configured in the global JNDI
           resources under the key "UserDatabase".  Any edits
           that are performed against this UserDatabase are immediately
           available for use by the Realm.  -->
      <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
             resourceName="UserDatabase"/>

      <!-- Comment out the old realm but leave here for now in case we
           need to go back quickly -->
      <!--
      <Realm className="org.apache.catalina.realm.MemoryRealm" />
      -->

      <!-- Replace the above Realm with one of the following to get a Realm
           stored in a database and accessed via JDBC -->

      <!--
      <Realm  className="org.apache.catalina.realm.JDBCRealm"
             driverName="org.gjt.mm.mysql.Driver"
          connectionURL="jdbc:mysql://localhost/authority"
         connectionName="test" connectionPassword="test"
              userTable="users" userNameCol="user_name" userCredCol="user_pass"
          userRoleTable="user_roles" roleNameCol="role_name" />
      -->

      <!--
      <Realm  className="org.apache.catalina.realm.JDBCRealm"
             driverName="oracle.jdbc.driver.OracleDriver"
          connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL"
         connectionName="scott" connectionPassword="tiger"
              userTable="users" userNameCol="user_name" userCredCol="user_pass"
          userRoleTable="user_roles" roleNameCol="role_name" />
      -->

      <!--
      <Realm  className="org.apache.catalina.realm.JDBCRealm"
             driverName="sun.jdbc.odbc.JdbcOdbcDriver"
          connectionURL="jdbc:odbc:CATALINA"
              userTable="users" userNameCol="user_name" userCredCol="user_pass"
          userRoleTable="user_roles" roleNameCol="role_name" />
      -->

      <!-- Define the default virtual host
           Note: XML Schema validation will not work with Xerces 2.2.
       -->
      <Host name="localhost" appBase="webapps"
       unpackWARs="true" autoDeploy="true"
       xmlValidation="false" xmlNamespaceAware="false">

        <!-- Defines a cluster for this node,
             By defining this element, means that every manager will be changed.
             So when running a cluster, only make sure that you have webapps in there
             that need to be clustered and remove the other ones.
             A cluster has the following parameters:

             className = the fully qualified name of the cluster class

             name = a descriptive name for your cluster, can be anything

             mcastAddr = the multicast address, has to be the same for all the nodes

             mcastPort = the multicast port, has to be the same for all the nodes
             
             mcastBindAddr = bind the multicast socket to a specific address
             
             mcastTTL = the multicast TTL if you want to limit your broadcast
             
             mcastSoTimeout = the multicast readtimeout 

             mcastFrequency = the number of milliseconds in between sending a "I'm alive" heartbeat

             mcastDropTime = the number a milliseconds before a node is considered "dead" if no heartbeat is received

             tcpThreadCount = the number of threads to handle incoming replication requests, optimal would be the same amount of threads as nodes 

             tcpListenAddress = the listen address (bind address) for TCP cluster request on this host, 
                                in case of multiple ethernet cards.
                                auto means that address becomes
                                InetAddress.getLocalHost().getHostAddress()

             tcpListenPort = the tcp listen port

             tcpSelectorTimeout = the timeout (ms) for the Selector.select() method in case the OS
                                  has a wakup bug in java.nio. Set to 0 for no timeout

             printToScreen = true means that managers will also print to std.out

             expireSessionsOnShutdown = true means that 

             useDirtyFlag = true means that we only replicate a session after setAttribute,removeAttribute has been called.
                            false means to replicate the session after each request.
                            false means that replication would work for the following piece of code: (only for SimpleTcpReplicationManager)
                            <%
                            HashMap map = (HashMap)session.getAttribute("map");
                            map.put("key","value");
                            %>
             replicationMode = can be either 'pooled', 'synchronous' or 'asynchronous'.
                               * 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.
                               * Synchronous means that the thread that executes the request, is also the
                               thread the replicates the data to the other nodes, and will not return until all
                               nodes have received the information.
                               * Asynchronous means that there is a specific 'sender' thread for each cluster node,
                               so the request thread will queue the replication request into a "smart" queue,
                               and then return to the client.
                               The "smart" queue is a queue where when a session is added to the queue, and the same session
                               already exists in the queue from a previous request, that session will be replaced
                               in the queue instead of replicating two requests. This almost never happens, unless there is a 
                               large network delay.
        -->             
        <!--
            When configuring for clustering, you also add in a valve to catch all the requests
            coming in, at the end of the request, the session may or may not be replicated.
            A session is replicated if and only if all the conditions are met:
            1. useDirtyFlag is true or setAttribute or removeAttribute has been called AND
            2. a session exists (has been created)
            3. the request is not trapped by the "filter" attribute

            The filter attribute is to filter out requests that could not modify the session,
            hence we don't replicate the session after the end of this request.
            The filter is negative, ie, anything you put in the filter, you mean to filter out,
            ie, no replication will be done on requests that match one of the filters.
            The filter attribute is delimited by ;, so you can't escape out ; even if you wanted to.

            filter=".*\.gif;.*\.js;" means that we will not replicate the session after requests with the URI
            ending with .gif and .js are intercepted.
            
            The deployer element can be used to deploy apps cluster wide.
            Currently the deployment only deploys/undeploys to working members in the cluster
            so no WARs are copied upons startup of a broken node.
            The deployer watches a directory (watchDir) for WAR files when watchEnabled="true"
            When a new war file is added the war gets deployed to the local instance,
            and then deployed to the other instances in the cluster.
            When a war file is deleted from the watchDir the war is undeployed locally 
            and cluster wide
        -->
        
        <!--
        <Cluster className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"
                 managerClassName="org.apache.catalina.cluster.session.DeltaManager"
                 expireSessionsOnShutdown="false"
                 useDirtyFlag="true"
                 notifyListenersOnReplication="true">

            <Membership 
                className="org.apache.catalina.cluster.mcast.McastService"
                mcastAddr="228.0.0.4"
                mcastPort="45564"
                mcastFrequency="500"
                mcastDropTime="3000"/>

            <Receiver 
                className="org.apache.catalina.cluster.tcp.ReplicationListener"
                tcpListenAddress="auto"
                tcpListenPort="4001"
                tcpSelectorTimeout="100"
                tcpThreadCount="6"/>

            <Sender
                className="org.apache.catalina.cluster.tcp.ReplicationTransmitter"
                replicationMode="pooled"
                ackTimeout="15000"/>

            <Valve className="org.apache.catalina.cluster.tcp.ReplicationValve"
                   filter=".*\.gif;.*\.js;.*\.jpg;.*\.htm;.*\.html;.*\.txt;"/>
                   
            <Deployer className="org.apache.catalina.cluster.deploy.FarmWarDeployer"
                      tempDir="/tmp/war-temp/"
                      deployDir="/tmp/war-deploy/"
                      watchDir="/tmp/war-listen/"
                      watchEnabled="false"/>
        </Cluster>
        -->        



        <!-- Normally, users must authenticate themselves to each web app
             individually.  Uncomment the following entry if you would like
             a user to be authenticated the first time they encounter a
             resource protected by a security constraint, and then have that
             user identity maintained across *all* web applications contained
             in this virtual host. -->
        <!--
        <Valve className="org.apache.catalina.authenticator.SingleSignOn" />
        -->

        <!-- Access log processes all requests for this virtual host.  By
             default, log files are created in the "logs" directory relative to
             $CATALINA_HOME.  If you wish, you can specify a different
             directory with the "directory" attribute.  Specify either a relative
             (to $CATALINA_HOME) or absolute path to the desired directory.
        -->
        <!--
        <Valve className="org.apache.catalina.valves.AccessLogValve"
                 directory="logs"  prefix="localhost_access_log." suffix=".txt"
                 pattern="common" resolveHosts="false"/>
        -->

        <!-- Access log processes all requests for this virtual host.  By
             default, log files are created in the "logs" directory relative to
             $CATALINA_HOME.  If you wish, you can specify a different
             directory with the "directory" attribute.  Specify either a relative
             (to $CATALINA_HOME) or absolute path to the desired directory.
             This access log implementation is optimized for maximum performance,
             but is hardcoded to support only the "common" and "combined" patterns.
        -->
        <!--
        <Valve className="org.apache.catalina.valves.FastCommonAccessLogValve"
                 directory="logs"  prefix="localhost_access_log." suffix=".txt"
                 pattern="common" resolveHosts="false"/>
     -->
		<Context  docBase="E:\JAVA\WFStudy\szfood\WebRoot"  path=""  reloadable="true" >
           <ResourceLink global="jdbc/szfood" name="jdbc/szfood" type="javax.sql.DataSource"/>
        </Context>
   
		<Context  docBase="C:\Documents and Settings\zqwf\workspace\Struts\WebRoot"  path="/Struts"  reloadable="true" >
           <ResourceLink global="jdbc/oracleds" name="jdbc/oracleds" type="javax.sql.DataSource"/>
        </Context>

      </Host>

    </Engine>

  </Service>

</Server>

 

分享到:
评论

相关推荐

    Tomcat web应用中配置连接池的详细过程

    对于部署在Tomcat服务器上的Java Web应用而言,配置一个合适的连接池显得尤为重要。本文将详细介绍如何在Tomcat环境中配置Oracle数据库连接池,并给出相应的配置示例。 #### 二、配置步骤 ##### 1. 在 `server.xml...

    初学者如何最快用Tomcat配置连接池

    ### 初学者如何快速使用Tomcat配置连接池 #### 一、引言 在Web开发中,数据库连接池是一项非常重要的技术,它能够显著提高应用的性能和响应速度。对于初学者来说,学会如何在Tomcat服务器中配置连接池是非常有帮助...

    各个web服务器安装文档,及连接池的配置

    连接池配置在WebSphere管理控制台中,创建新的数据源,设置连接池大小、超时、验证方式等,确保服务的稳定性和响应速度。 这三款Web服务器在连接池配置上都强调了资源管理,避免空闲连接过多或连接溢出,以提升系统...

    XML解析和数据库连接池

    例如,Apache的DBCP、C3P0、HikariCP和Tomcat的JDBC连接池都是常用的数据库连接池实现。 在Java应用中,配置数据库连接池通常包括以下步骤: 1. 添加对应连接池的依赖库到项目中。 2. 配置连接池的属性,如最大连接...

    jdbc链接池大全

    连接池则是为了提高数据库操作效率而设计的一种机制,它通过预先创建并维护一定数量的数据库连接,避免了每次数据库操作时都创建和销毁连接的开销,从而显著提升了应用性能。 在标签中,“JDBC”、“链接”和...

    springboot + mybatis + pagehelper分页插件 + druid连接池 + generator逆向插件,请阅读README.md

    在本项目中,我们主要探讨的是一个基于Spring Boot框架,结合MyBatis、PageHelper分页插件、Druid连接池以及Generator逆向工程插件的整合应用。这些技术都是现代Java开发中常用且重要的组件,下面将逐一详细介绍它们...

    数据库连接字符串

    tomcat连接池: context.xml配置: &lt;Resource name="jdbc/oracle" auth="Container" type="javax.sql.DataSource" driverClassName="oracle.jdbc.driver.OracleDriver" url=" jdbc:oracle:thin:@host:port:...

    netbeans连接数据库

    **步骤1:创建连接池** 1. 打开NetBeans IDE。 2. 选择“Services”选项卡,在其中找到“Databases”并右键点击“New Connection”。 3. 在弹出的窗口中选择相应的数据库类型(如Oracle、MySQL等)。 4. 输入数据库...

    常用数据库连接方法

    在实际应用中,为了提高代码的可维护性和性能,通常会使用连接池技术来管理数据库连接,如C3P0、HikariCP或Tomcat JNDI等。此外,Spring框架也提供了丰富的数据访问抽象层,可以简化数据库操作,并提供事务管理功能...

    LyBBS『凌云论坛』系统

    采用Struts1.3标准,兼容于Java 2 Standard Edition 1.4和1.5(5.0),兼容Windows/Linux/Unix多种操作系统平台,兼容于Tomcat/Resin/WebLogic/WebSphere等多种JSP服务器容器,兼容于MySQL /DB2/Oracle/MSSQL系列...

    使用JDBC连接数据库的各种jar包

    10. **优化连接池**: 在实际生产环境中,通常会使用连接池(如C3P0、HikariCP、Apache DBCP等)来管理和复用数据库连接,提高性能和资源利用率。 了解以上知识点后,你可以根据具体需求选择对应的JDBC驱动jar包,...

    JNDI数据源配置

    为了简化这一过程并提高应用程序的可移植性和可维护性,Java命名与目录接口(Java Naming and Directory Interface,简称JNDI)提供了一种强大的机制来管理和查找各种资源,包括数据库连接池。本文将详细介绍如何...

    java变态面试题.pdf

    * 数据库连接池:常用的数据库连接池有 Oracle、MySQL、DB2 等,每种数据库连接池都有其优缺点。 * Oracle 数据库:三范式、数据库的存储过程和函数,具体是什么,能干些什么? 六、其他知识点 * Lucene 搜索引擎...

    java部分面试题.pdf

    5. **Tomcat和WebLogic配置连接池**: - 连接池管理数据库连接,提高效率,避免频繁创建和销毁。Tomcat通常使用Apache DBCP或C3P0,WebLogic则有自己的连接池配置。 6. **String和StringBuffer的区别**: - ...

    数据库连接参考配置文件

    这些数据源配置通常用于在应用服务器内部管理数据库连接池,提高性能和资源利用率。 ### 总结 通过上述解析,我们可以看到,不同的数据库系统拥有各自独特的JDBC驱动和URL格式,这是连接数据库时必须准确配置的...

    java连接各种数据库的配置文件写法

    ### Java连接各种数据库的配置文件写法详解 ...此外,对于一些高级功能如连接池等,还需要额外的配置和管理。总之,合理的配置不仅能够简化程序的开发过程,还能够有效提升应用程序的性能和稳定性。

    Informatica-PowerCenter-9-for-Linux64-安装配置.docx

    - **表空间**:为 Informatica 专用表空间预留至少 500MB 空间,对于 DB2 数据库,需要确保缓冲池页大小至少为 32KB。 - **字符集**:确保数据库使用的字符集为中文字符集 GBK。 - **监听器端口**:提供数据库监听器...

    久其移动Framework

    久其移动框架采用了Tomcat 7自带的JDBC连接池。相比之前的Commons DBCP,Tomcat JDBC Pool在性能、易用性和可维护性方面都有显著提升。 **特点:** 1. **兼容性:** Tomcat JDBC Pool与Commons DBCP兼容,使得迁移...

Global site tag (gtag.js) - Google Analytics