ImageServer 2.0 Installation > Performing A New ImageServer Install

Prepare the FileSystem

Before you run the ImageServer installer, you must prepare the FileSystem(s) used for the storage of DICOM studies. This is usually not an issue if you are using one of the computer's local disks, but if you are using network storage or other external disks, you must ensure that the FileSystem is accessible prior to running the installer or it will not be able to complete successfully.

Installing ImageServer 2.0

1. Select Components

Launch the ImageServer installer. After the License Agreement, the installer will provide a list of components to install. This guide will provide instructions for a simple configuration where all components are installed to the same computer. Accept the default configuration (all components).

The default configuration installs all components to the same computer.

2. Specify SQL Server

On the Database connection page enter the sa logon and password you created during the SQL Server install. You may use another SQL account here as long as it has sufficient permissions. In the DB Server field, enter the SQL server IP address and instance name if applicable, just as you did when verifying the connection using SQL Server Management Studio. You cannot use the IP address in place of the hostname unless you explicitly set up your SQL server to accept connections over TCP/IP protocol.

Enter the sa logon, password, and server name as when logging into Management Studio.

3. Specify Database File Directories

On the Database installation page, specify the location of the database files. Check that the default path exists before continuing. If you choose to change the path, you must ensure that SQL Server has write permissions on the new path or else the database will fail to be created. If you change the path and the database could not be created, you should check the install log for error details.

Default paths must exist in order for the database to be created.

A note about using a dedicated SQL Server: if you are running separate application and database servers, you have the option of running the installer on the application server to install both the application and web components locally and the database on a remote server in one go. You can also run the installer separately on the application and database servers and select the discrete components for each server.

If you wish to install the database to a remote server, the installer can pass the paths specified to the remote SQL server and instruct it to create the database files to its own local disk according to the paths specified. To do this, you must place a check mark in the box labeled Check if database is being created on a remote server.

4. Setup Filesystem

On the Filesystem setup page, specify a description for your filesystem and enter the path to it. If this path is to a remote or extenal disk, the credentials to access the disk must already be supplied in your Windows session and the disk must be accessible or the installer will fail.

Filesystem Path must be accessible.

5. Setup Partition

A Partition in ImageServer is essentially a Virtual PACS Server. You can create multiple Virtual Servers, each with its own AE Title, however, they are not limited to listening on different ports. All Partitions in ImageServer can be configured to listen on different ports or on the same port. All Partitions use the same physical Filesystem(s) for storage, but each Partition stores its own set of studies which are not visible to other Partitions as if they are separate PACS servers.

On the Partition setup page, configure the DICOM parameters for your first Partition. Specify the DICOM AE Title you wish to assign to this Partition, a description for it, the name of the directory as it will appear on your filesystem, and finally, the port this DICOM device will listen on. The AE Title you choose must be unique on our network. If you wish to use the default port 104 you must ensure that the same port is not already in use by another application on the same machine and is not blocked by your firewall. If you have already installed Workstation on this computer and it is using the default port 104 you must specify another port to be used by ImageServer.

Assign an AE Title to This Partition that is unique to your network.

6. Create Web UI Admin User

Lastly, on the Web UI Admin User creation page, specify the username and password that will be used to log into the Web Interface. ImageServer provides only one account for administering the PACS unless integrated with the Enterprise Server. Intended for large enterprises, the soon-to-be-released Enterprise Server will allow for Single Point Sign-On User Management across all three ClearCanvas RIS/PACS components.

Create your Web UI Admin User account.

7. Start the ImageServer Shredhost Service

Once the installer has completed, you will be given an option to start the Shredhost service upon closing the wizard. Whether you start the service now or manually at a later time, the service is still configured for automatic startup when Windows starts. You are given the option to prevent start up now in order to facilitate ImageServer cluster installs where you may want to finish installing other components first before starting the service.

Start the ClearCanvas ImageServer Shredhost Service manually.

Logging in to ImageServer

Once the installer has completed, you may open Internet Explorer and browse to http://<hostname>/imageserver where <hostname> is the hostname of the ImageServer computer. Log in using the username and password of the Web UI Admin User you just created.

Congratulations! You have successfully completed a new ImageServer install. Please read the ImageServer User's Guide for more details on how to use the software.