Note: My TomCat Datasource will points to this context - the dbadm directory.

I am working on getting the placement of the dbadm.war to the \webapps directory and letting Tomcat extract the contents. It's not behaving right now. Part of the TODO list.

        <Context path="/dbadm" docBase="dbadm" debug="0"
                       reloadable="true" crossContext="true">
                <Logger className="org.apache.catalina.logger.FileLogger"
                           prefix="dbadm_log." suffix=".txt"
                    timestamp="true"/>

                <Environment name="maxExemptions" type="java.lang.Integer"
                            value="15"/>
                <Parameter name="context.param.name" value="context.param.value"
                           override="false"/>

                  <!-- Start DATABASE CONNECTION: DB2 -->
                <Resource name="jdbc/DBADM" auth="SERVLET" type="javax.sql.DataSource"/>
                <ResourceParams name="jdbc/DBADM">
                <!-- Use the apache Database Connection Pool -->
               <parameter>
                     <name>factory</name>
                     <value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
               </parameter>
                <!-- Maximum number of dB connections in pool. Make sure you
                        configure your mysqld max_connections large enough to handle
                        all of your db connections. Set to 0 for no limit.
                        -->
                <parameter>
                  <name>maxActive</name>
                  <value>100</value>
                </parameter>
                <!-- Maximum number of idle dB connections to retain in pool.
                        Set to -1 for no limit.  See also the DBCP documentation on this
                        and the minEvictableIdleTimeMillis configuration parameter.
                        -->
                <parameter>
                  <name>maxIdle</name>
                  <value>30</value>
                </parameter>
                <!-- Maximum time to wait for a dB connection to become available
                        in ms, in this example 10 seconds. An Exception is thrown if
                        this timeout is exceeded.  Set to -1 to wait indefinitely.
                        -->
                <parameter>
                  <name>maxWait</name>
                  <value>10000</value>
                </parameter>
               <!-- To configure a DBCP DataSource so that abandoned dB connections
                  are removed and recycled add the following paramater to the
                  ResourceParams configuration for your DBCP DataSource Resource.
                  When available db connections run low DBCP will recover and recyle
                  any abandoned dB connections it finds. The default is false. -->
               <parameter>
                  <name>removeAbandoned</name>
                  <value>true</value>
               </parameter>
               <!-- Use the removeAbandonedTimeout parameter to set the number of
                   seconds a dB connection has been idle before it is considered abandoned.
                   The default timeout for removing abandoned connections is 300 seconds. -->
                   <parameter>
                    <name>removeAbandonedTimeout</name>
                    <value>60</value>
                  </parameter>
               <!-- The logAbandoned parameter can be set to true if you want DBCP to log a
                     stack trace of the code which abandoned the dB connection resources. -->
                   <parameter>
                    <name>logAbandoned</name>
                    <value>true</value>
                  </parameter>
               <!-- The typical JDBC Connection for DB2. My database was called DBADM -->
                  <parameter>
                     <name>username</name>
                     <value>db2admin</value>
                  </parameter>
                  <parameter>
                     <name>password</name>
                     <value>db2admin</value>
                  </parameter>
                  <parameter><name>driverClassName</name>
                    <value>COM.ibm.db2.jdbc.app.DB2Driver</value>
                  </parameter>
                  <parameter><name>url</name>
                    <value>jdbc:db2:DB2ADM</value>
                  </parameter>
                </ResourceParams>
                  <!-- End DATABASE CONNECTION: DB2 -->


                <Resource name="mail/Session" auth="Container"
                          type="javax.mail.Session"/>
                <ResourceParams name="mail/Session">
                  <parameter>
                    <name>mail.smtp.host</name>
                    <value>localhost</value>
                  </parameter>
                </ResourceParams>
                <ResourceLink name="linkToGlobalResource"
                          global="simpleValue"
                          type="java.lang.Integer"/>
              </Context>

A DB2 schema name called, DBADM, must be created. Remember the to create the table MYEXAMPLE within this schema:

CREATE TABLE DBADM.MYEXAMPLE
(
   RECID INTEGER,
   NAME VARCHAR(32),
   ADDRESS VARCHAR(50),
   PRIMARY CHAR(1)
);

I won't go into the how, but the DB2 environment should look like this.

 

 

 

 

 

 

An ODBC DataSource must also be created:

 

A message should appear indicating that "DataSource name set to: --> jdbc/DBADM"

You may not be able to Login since the Data Access Object (DAO) accessing this process is a flat file: SecureUser.txt. 
The deployed version uses two type of DAOs, flat files and DB2 to access the data.