Modifying the Database Configuration


  1. Edit the tomcat/conf/context.xml file.
  2. Locate the Configuration template for the database vendor to which Cascade CMS will be connecting.
  3. In the <Resource> element, update the following attributes:
    • username - the username needed to connect to the database
    • password - the password needed to connect to the database
    • url - the host, port, and database name (following one of the formats below depending on your database vendor)



The connection URL above will attempt to connect to a database named cascade running at hostname mysql over port 3306.

SQL Server

Cascade CMS version 8.17 and earlier:

Cascade CMS version 8.17.1 and later:

Note: The default connection string seen directly above is intended to work for databases using SQL Server authentication. If you are using Windows authentication, you will need to add the following parameters to the connection string (at a minimum):


For more information, see this article on Building the connection url   from Microsoft's documentation.

The connection URLs above will attempt to connect to a database named cascade running on a server with hostname sqlserver on port 1433.


The connection URL above will attempt to connect to an Oracle SID orcl on a server with hostname huxley running on port 1521 using the thin driver. With Oracle, the database schema is specified using the cascadeSchemaName resource.

Ensure that the following line in tomcat/conf/context.xml is uncommented:
<ResourceLink name='schemaName' type='java.lang.String' global='cascadeSchemaName'/>

and then un-comment and update the cascadeSchemaName environment variable to have the value for your database's schema in the tomcat/conf/server.xml file:
<Environment name="cascadeSchemaName" type="java.lang.String" value="my_cascade_db"/>

Important: With Oracle, it is required that the connecting username matches the name of the database schema.