Page Comparison

...

1. Create a database for TermWeb to store data in (e.g. termweb). 
   
   • Open pgAdmin and right click on Databases and select New Database
     Name: termweb
     Encoding: UTF8
     Template: template0
     Collation: C
     Character Type: C
     
     
2. Create a database login role (user) which TermWeb will connect as (e.g. termwebuser), with permissions for the database.
   • Create a new login role (right click on Login Roles and select New Login Role) and name it termwebuser. Select password: termwebpwd.
   • Set login role as database owner (right click on termweb database and select Properties). Select termwebuser as owner.
     
     
3. Execute the grant_privileges_postgresql.sql file from the installation package to grant the necessary privileges to termwebuser.
   
   
4. Connect as the new user before creating TermWeb tables. This is important, in order for the new user to also be owner of every table.
   • Right click on PostgreSQL server and select Disconnect server
   • Right click on PostgreSQL server and select Properties
   • Write termwebuser as username
   • Doubleclick on PostgreSQL server to connect (might need to do it twice, due to wrong password)
   • Write the password termwebpwd in order to connect with the new user
     
     
5. Execute the termweb_postgresql.sql file from the installation package to create the database tables.
   • Select termweb database and click on SQL icon to open an SQL execution window.
   • Copy paste termweb_postgresql.sql content and execute query.

After successfully creating the TermWeb schema on a PostgreSQL database, you need to pass the credentials of your database in the context of Tomcat by following steps 2 and 3.
However, if you are planning to deploy TermWeb on a Heroku container, the following steps are not needed. Instead you can directly follow this tutorial on how to deploy on Heroku.
The reason for this is that a Heroku container has an embedded Tomcat server, which does not use context properties. That is why we don't configure the data source in Tomcat.
TermWeb is configured to use Heroku's standard way of reading the data source, i.e. to get the database credentials from the container's environmental variables.

2. Copy the PostgreSQL JDBC Driver to Tomcat

(if the application is about to be deployed on Heroku, this step is not needed)

1. Download the PostgreSQL driver (v9.4) from PostgreSQL official site.
2. Add the PostgreSQL driver jar (postgresql-9.4.1208.jre6.jar) to <tomcat-install>/lib/ directory.
   Make sure to download the correct version that is compatible with your Java version (e.g. jre7 for Java 1.7)
   If you are using Tomcat 8, there are cases where you can totally skip this step.

3. Configure a DataSource for TermWeb in Tomcat

(if the application is about to be deployed on Heroku, this step is not needed)

1. Edit <tomcat-install>/conf/context.xml. 

2. Within the Context tags, insert the DataSource Resource tag:

    

   Code Block
   language xml
   <Resource name="jdbc/TermWebDS" auth="Container" type="javax.sql.DataSource" username="termwebuser" password="termwebpwd" driverClassName="org.postgresql.Driver" url="jdbc:postgresql://localhost/termweb" maxActive="20" maxIdle="10" validationQuery="Select 1"/>

   1. • If PostgreSQL does not run on the same server as Tomcat, replace localhost in url with the name of the database server
      • If you named the database something else than termwebdb, replace termwebdb in url with your database name 
      • Replace termwebuser and termwebpwd in url with your database user and password.

   The configuration properties for Tomcat's standard data source resource factory (org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory) are as follows:

   • • driverClassName – Fully qualified Java class name of the JDBC driver to be used.
     • maxActive – The maximum number of active instances that can be allocated from this pool at the same time.
     • maxIdle – The maximum number of connections that can sit idle in this pool at the same time.
     • maxWait – The maximum number of milliseconds that the pool will wait (when there are no available connections) for a connection to be returned before throwing an exception.
     • password – Database password to be passed to our JDBC driver.
     • url – Connection URL to be passed to our JDBC driver. (For backwards compatibility, the property driverName is also recognized.)
     • user – Database username to be passed to our JDBC driver.
     • validationQuery – SQL query that can be used by the pool to validate connections before they are returned to the application. If specified, this query must be an SQL SELECT statement that returns at least one row.

...