Introduction to Installation

Installing Calmview and building your Calmview website will involve three machines/environments. It is important to understand the purpose of each of these and what your organisation will need to do to install Calmview in the correct way or to prepare for a member of the Axiell staff to carry out this work for you.

They are:

The server that contains your current, live version of Calm (which is linked to your Calm clients). This is the source of data that will appear on your Calmview website.
A development environment. This is where Calmview will initially be installed (by you or Axiell) and where its configuration will take place, via the configuration tool supplied with it and standard web authoring tools.
A live web server, this will be the public-facing front end. This is where your users can search for and view your Calm records, without being able to perform internal operations such as configuring Calmview elements or modifying your working copy of Calm data.

Please note: All these environments must run the same version of Calm and Calmview as each other (Calmview on the development environment and public-facing server only). When you receive software updates from us, your organisation will need to install them on each of the relevant machines.

The first step in installation is to check you have the minimum requirements for Calmview. It is important to check these requirements even if Axiell are carrying out the installation for you. Please be aware that if these requirements are not met prior to the date of the scheduled Calmview installation it may result in the installation not being carried out and your organisation being charged for the site visit.

Your next step will depend on whether your organisation or Axiell are carrying out the installation. It it's Axiell, please read the page to the left entitled 'Axiell Installation'. Otherwise, click on the 'Development Environment' option to the left for instructions on how to set this up.

Why three locations?

You must use separate machines (or virtual machine environments) for the three purposes listed above. Here are some of the reasons:

When the service that Calm uses (called DScribe) is stopped at night to perform a back-up, your Calmview website will continue to be available online.

Records can potentially be locked whilst the public are accessing Calm via Calmview, this will not impact on Archive staff (by making the records unavailable to be updated).
If the Archive staff undertake an intensive update of data, this will not impact on the public viewing your Calmview website.
Only designated personnel in your organisation can configure Calmview, not members of the public or anyone viewing your Calmview website.
Each client connecting to the Calm data on your live server is using one of the user licences from your total purchased amount, but those connecting on your public-facing server via Calmview are not.
If a record containing sensitive data is catalogued incorrectly (not implementing the correct search filters) it will not instantly go on display to the public.
If a member of the public tries to jeopardise your Calmview website, for example with a denial of service attack, the databases on your live server will be unaffected.
When Calm is running on your live server, three TCP (Transmission Control Protocol) ports are opened in your internal firewall to allow the clients to access the data. On the copy of Calm which will be running on your public-facing server you will not need to open these ports on your external firewall (which could compromise security).