Setting up a Test Server

Using a Separate Machine (recommended)

  • Install the latest version of Cascade Server
  • Create a backup of the production database and import it as a new database. Organizations using MySQL should verify that the collation of the new database is configured properly according to step 5 here
  • Configure the test instance to point to the test database created in the previous step
  • Disable publishing to destinations by issuing the following query to the database:
UPDATE cxml_destination SET isEnabled=0;

This will prevent test assets from being published to your production web servers. If you are testing the software using your production database and looking to test publishing, you are encouraged to set up a test Destination that points to a test/staging server.

  • Disable email notifications by issuing the following query to the database:
DELETE FROM cxml_preferences WHERE fieldName LIKE '%smtp%';

This will prevent Workflow emails and LDAP synchronization emails from being sent from the test instance.

  • Disable all 3rd-party Connectors to services like Google Analytics, Wordpress, Facebook, and Twitter:
UPDATE cxml_connector SET isVerified =0;

These can be selectively re-enabled by re-verifying these connectors in the Connectors area of the software.

  • Start Cascade Server
  • Click System Menu -> Preferences -> General and change the System URL field to reflect the URL at which your instance of Cascade Server is hosted. Change the Organization Name to indicate that the instance is a Test or Development instance (so that Users are aware of what instance they are working in).

Using the Production Machine (not recommended)

  • Follow the same steps listed above. Prior to starting Cascade Server, modify the port settings such that they do not interfere with the running Production instance of Cascade Server.