Cascade Server currently supports MySQL 4.1/5.0, Microsoft SQL Server 2005, and Oracle10g.

For instructions on setting up the default database for one of these vendors, click here.

1. Click Global System Menu -> Configuration -> Product License as seen below:

2. Enter the license key code into the Configuration Content field, then click Submit.

Linux/*nix

• Stop Cascade Server
• Edit the file cascade.sh (found in the Cascade root directory)
• Modify the -XX:MaxPermSize parameters on line 2:

For example, the line above sets the MaxPermSize to 192M.  

• Restart Cascade Server 

Windows (command line)

• Stop Cascade Server
• Edit the file cascade.bat (found in the Cascade root directory)
• Modify the -XX:MaxPermSize parameters on line 3:

For example, the line above sets the MaxPermSize to 192M. 

• Restart Cascade Server

Windows (service)

• Navigate to the \tomcat\bin directory and find the file named tomcat5w.exe
• Make a copy of this file and rename it cascadew.exe
• Double-click the file cascadew.exe
  
• In the configuration UI click on the Java tab.
• In the Java Options field, add the following:

In this example, the MaxPermSize is set to 192M.

Linux/*nix

• Stop Cascade Server
• Edit the file cascade.sh (found in the Cascade root directory)
• Add/Modify the -Xmx and -Xms parameters on line 2:

The line above sets the maximum java heap size to 768M.  An -Xms value can also be added to specify an initial heap size.

• Restart Cascade Server 

Windows (command line)

• Stop Cascade Server
• Edit the file cascade.bat (found in the Cascade root directory)
• Add/Modify the -Xmx and -Xms parameters on line 3:

The line above sets the maximum java heap size to 768M.  An -Xms value can also be added to specify an initial heap size.

• Restart Cascade Server

Windows (service)

• Navigate to the \tomcat\bin directory and find the file named tomcat5w.exe
• Make a copy of this file and rename it cascadew.exe
• Double-click the file cascadew.exe
  
• In the configuration UI click on the Java tab.
• Enter a value for the Initial memory pool field
• Enter a value for the Maximum memory pool field
• Click Apply
• Restart the Cascade service

• Shut down Cascade Server
• Create a keystore (from http://tomcat.apache.org/tomcat-5.5-doc/ssl-howto.html):
• Execute the following command:
  

       Windows: %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA
  
       Unix: $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA

  • For the password, enter “changeit”

  (Windows: the .keystore file can typically be found in the Documents and Settings folder under the user's sub folder; eg, C:\Documents and Settings\Administrator)
  (Linux: the .keystore file can typically be found in the home directory of the user who created it; eg, /home/user)

• Edit the file server.xml (found in \tomcat\conf)
  
  - Uncomment the area for SSL/TLS Connector configuration
  
  <!-- 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" />

• Add the keystoreFile and keystorePass attributes to the <Connector> element and specify the location of the keystore along with the password:

• Start Cascade Server – it should now be accessible through https://{host}:8443

NOTE: If both the HTTP/1.1 Connector and the SSL/TLS Connector sections are left uncommented, users will still be able to access the site through port 8080.  This can be changed by:

Commenting out the HTTP/1.1 Connector section in 'server.xml'

            OR

Forcing Tomcat over SSL.  To do this, enter the following code into 'web.xml', just before the closing </web-app> element (web.xml is located in \tomcat\conf):

By default, Cascade Server will attempt to listen on port 8080.  If another application is already listening on this port, administrators may wish to change it so that there are no port conflicts on the system.   To change ports, follow the steps below:

• Shut down Cascade Server
• Navigate to \tomcat\conf
• Edit the file server.xml
• Locate the HTTP/1.1 Connector:
  

• Change the port attribute (default is 8080) and save the file
• Restart Cascade Server  

To configure Cascade's connection to the database, follow the steps below:

• Edit the file tomcat\conf\context.xml
• Locate the Configuration template for the database vendor to which Cascade Server will be connecting
• 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 the format below

MySQL 5.0/5.1 Database URL:

Connect to database named 'cascade' running at hostname 'mysql' over port 3306

SQL Server 2005/2008 Database URL:

Connect to database named 'cascade' running on a server at hostname 'sqlserver' on port 1433

Oracle 9i/10g Database URL:

Connects to an Oracle SID called 'orcl' on a server at 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 uncomment 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's required that the connecting username matches the name of the database schema.

Inbound Connections

Outbound Connections

The table below outlines the default ports that Cascade Server will use for outbound connections:

* Since end users can link to any URL and port, the external link check could require other outbound ports for specific URLs. In general, you should be ok with only allowing port 80 and port 443.

** only necessary if using the Google Analytics Connector, WordPress Connector, or Twitter Connector