You are here:

Public-facing Server

Please note: Setting up and troubleshooting Microsoft IIS and Microsoft .net 4.0 framework are not supported by Axiell, any advice required will need to be obtained from your server support team.

Perform the following steps to set up the public-facing server:

Setting up the environment

Check the minimum requirements list for the public-facing server and install or upgrade any missing software.

Please note: If you are using IIS version 7 or above, you will need to install the IIS Console and other components to allow CalmView to be installed.

Please note: If you are running a 64bit version of Windows Server 2008, you will need to install the 32bit IIS environment alongside the 64bit one. Windows Server 2008 is able to run both environments together. This is not necessary for Windows Server 2012 or above.

If IIS was installed after the .net framework, ensure that the .net framework is registered with IIS (see your server support team for instructions).
Within IIS, allow ASP and .net applications to run.
In IIS, create a second website called CalmViewBE (stands for 'Back End') and allocate a TCP port that doesn't conflict with any other applications on this server.

Please note: It is advisable to have this port blocked from external access on your firewall.

For this CalmViewBE website, set the home directory to the inetpub\wwwroot sub-folder on this machine. (This is the same as the default website).

Installing the Calm software and databases

Install the Server version of Calm from your installation CD. Please note: This must be the same version as Calm running on your current live server and as Calm running on your development environment.
Ensure the DScribe Server/2 service is loaded and started.
Install the Client version of Calm from your installation CD.

Please note: Prior to copying files from the development environment to the public-facing server, it is important to ensure that any records you do not wish the public to view meet your filtering criteria. To do this perform relevant searches on the development environment and check the results.

Follow the instructions for copying your live Calm databases from your Calm server to this machine. This is the responsibility of your organisation.
Run the Calm client and enter the license key. Check that your Calm records have been copied successfully.

Installing CalmView

Start to install CalmView from your installation CD.
Enter the language you wish to install CalmView in.
Enter the password (contact the Calm Helpdesk for this).
When you are asked which CalmView features you wish to install, remove the tick from 'CalmView Configurator' but leave the other defaults selected i.e. CalmView, Brokers, CalmBroker, Discovery (and Core, which is greyed out).
It is very important that you do not install the CalmView Configurator onto this live public-facing server.
On the pages that follow, leave the default settings for the CalmView component, i.e. install it into the default website and the inetpub\wwwroot subfolder on this machine.
On the pages after that, where you install the other components (CalmBroker and CalmViewStats), choose the CalmViewBE website and leave the folder as the default setting i.e. the inetpub\wwwroot subfolder on this machine

By splitting the CalmView install in this way (using the default website and the CalmViewBE website) you are protecting your back-end CalmView components from unwanted public access.

Once the files have been installed, the Calm API Configuration window will pop up. Enter the version of Calm you are using, but do not change any of the other settings.

Moving CalmView from development

Use the following procedure to copy CalmView files from your development environment to your public-facing server. You will need a medium that will allow you to copy these files.

Locate the CalmView folder (usually inetpub\wwwroot\CalmView) on your development environment.
Copy this folder to your chosen portable medium.
Locate the CalmView folder (usually inetpub\wwwroot\CalmView) on your public-facing server.
Open this CalmView folder and delete all the files and folders located here. This is a very important step so that you don't have old files remaining.
Go back to the root of the wwwroot folder here on the public-facing server.
Copy the CalmView folder from your portable medium to the root of the wwwroot folder overwriting the CalmView folder.
Open this CalmView folder (on the public-facing server) and locate a file called web.config.
Open web.config in a text editor such as Notepad or Textpad.
Within web.config, locate the line that reads;
<search broker="http://localhost/CalmBroker/DiscoveryBroker2.asmx">
Carefully change the URL in this line to the URL of this file on your public-facing server. Based on the port you chose to run the CalmViewBE website on, the URL will look something like this:

Still within web.config, next locate the line that reads;

Ensure this path states the correct location for the General\dscovery.log file. If not, correct it. If you are unsure of what the path should be, please contact the Calm Helpdesk.
Next locate the line that reads;
<file value="c:\inetpub\wwwroot\CalmViewStats\logs\Error\dscovery.log" />
Ensure this path states the correct location for the Error\dscovery.log file. If not, correct it. If you are unsure of what the path should be, please contact the Calm Helpdesk.
Finally, locate the line that reads;

Ensure this path states the location for the CRecords\dscovery.log file. If not, correct it. If you are unsure of what the path should be, please contact the Calm Helpdesk.
Once you are happy that the URL and the 3 file paths all point to the correct locations, save the web.config file.

You are now ready to run your live CalmView website using the following URLs:

http://localhost/CalmView on this server
http://ServerName/CalmView from another location on your network
http://www.domainname/CalmView over the internet

➤