Install Studio

The following guide explains how to install a Crafter Studio instance in a QA or production Unix-based server.

Before You Start

Crafter Studio relies on two underlying stores: a repository and a RDBMS Database. The content itself, the versions and other core metadata are stored in the repository. Operational data concerning dependencies, workflow and deployment are stored in the RDBMS database.

When you install Crafter CMS via the zip file and start up Crafter Studio it starts up with an in-memory database. This is meant to facilitate local developer environments and evaluation. For production, you will want to use an external database. Crafter supports a number of popular RDBMS databases.

The steps below assume you have setup and configured an external database, created a schema and provisioned a user for that schema.

Installation Steps

  1. Download the This file contains already Tomcat 7 with the Studio, Search and Preview Engine WARs, the Crafter Deployer and the necessary configuration files.

  2. Download the database JDBC driver.

  3. Unzip the to any folder (from now on this folder will be referred as INSTALL_DIR). The recommended INSTALL_DIR is /opt/crafter/bin/authoring.

  4. Copy the JDBC driver jar to INSTALL_DIR/apache-tomcat/lib.

  5. Add the JAVA_HOME variable to INSTALL_DIR/apache-tomcat/bin/

  6. Add the JAVA_OPTS variable to INSTALL_DIR/apache-tomcat/bin/ (e.g. JAVA_OPTS="$JAVA_OPTS -server -Xms2G -Xmx8G -XX:MaxPermSize=512M").

  7. Remove the JAVA_OPTS variable from INSTALL_DIR/bin/

  8. Change the Studio configuration to connect to the database and to specify the environment:

    1. Go to INSTALL_DIR/apache-tomcat/shared/classes/crafter/cstudio/extension/

    2. Add the database connection properties, depending of your database engine (remember to replace the {} with the actual values, except for ${}):

      • MYSQL Properties

      • Oracle Properties

      • Postgres Properties

      • MS SQL Server Properties

    3. Add the following properties to specify the environment (the string value of this properties can be anything, just make sure that when site administrators specify environment overrides in the site configuration, they do it under a folder with the same name):

  9. Change the path where the preview content will be stored. A good path for this directory is /opt/crafter/data/preview-content.

    1. In INSTALL_DIR/crafter-deployer/conf/preview-target-context.xml, under the PreviewTarget bean configuration, change <value>target/preview</value> to the new preview content dir.
    2. In INSTALL_DIR/apache-tomcat/shared/classes/crafter/engine/extension/, update the value of the property, e.g. file:/opt/crafter/data/preview-content/{siteName}/{siteName}/work-area (don’t replace {siteName}).
  10. Change the path where the preview Solr search indexes will be stored, e.g. /opt/crafter/data/preview-indexes:

    1. In INSTALL_DIR/apache-tomcat/solr-crafter/conf/solrconfig.xml, update the value of <dataDir> to the preview indexes folder path (e.g. <dataDir>/opt/crafter/data/preview-indexes</dataDir>).
  11. Change the path where the Tomcat and deployer logs will be stored. A good path is /opt/crafter/logs:

    1. In INSTALL_DIR/apache-tomcat/conf/, change the values of,, and to the logs folder path.
    2. In INSTALL_DIR/crafter-deployer/log4j.xml, change the value of File param of the file appender to include the logs folder path (e.g. /opt/crafter/logs/deployment.log).