Preparing the Demo System for Productive Use

Normally, the requirements regarding network and data security as well as performance are different from running a demo version. For this reason, the following points should be taken into account when switching to productive use of CMS Fiona.

  • Change the password of the root user and other passwords. See Changing Passwords.

  • Replace the supplied SQLite database with a professional database. With respect to performance and data security, SQLite does not meet the requirements of productively used systems and therefore has not been approved for productive use. See Integrating a Different Database.

  • Set-up a backup procedure. Create a dump in regular intervals using a cron job, for example. See Dumping and Restoring Data.

  • For preserving the performance of a Sybase database, the scripts for updating the indexes need to be executed in regular intervals. See Notes on Database / Operating System Combinations.

  • If you imported the demo content, remove it by restoring your own dump or the supplied initialization dump. See Dumping and Restoring Data or Removing the Demo Content, respectively.

  • If you wish to export content incrementally, integrate the Template Engine. See Integrating the Template Engine. How static data can be served using the Trifork application server is described in section Serving Static Data Using the Trifork Server.

  • If dynamic content is to be served, install a web server. For the preview, see Displaying Dynamically Generated Content in the Preview. The information in this section also applies to the live server.

  • Immediately after delivery, the GUI can be operated using SSL. For this, use the port configured in the Trifork server (default: 8443). The port can be changed via the administration console of the Trifork server: http://my.npsserver:8090/console. Use your CMS host name instead of my.npsserver.

    If an official certificate is to be integrated instead of the supplied dummy certificate, place an Apache webserver with active mod_ssl in front of the Trifork server. Alternatively, you can generate a new private key in the JKS Keystore using the key tool and then send the corresponding certification request to the certification authority. Keys or certificates originally intended for use with the Apache webserver cannot be used directly in the Trifork server.

  • If your content does not contain JSPs, you can increase the performance of the Trifork server by removing the -devel option from the TRIFORK_ARGS in the file config/rc.npsd.conf. (The server compiles JSPs dynamically only if the -devel option has been specified.)