Navigation:  »No topics above this level«

Installation

 Previous pageReturn to chapter overviewNext page

Once the installer has been downloaded, you'll need to unzip and run it. In the likely case that you don't have the .NET Framework 3.0 installed, the installer will download it from Microsoft and install it. This can take some time, so be patient and don't interrupt it.

The installer has three basic options when installing. A full installation can be done with all components, an install can be done with just the ImageServer database, or an install can be done with just the Windows service and Web components. If desired, the ImageServer database can be installed on a dedicated system, with the Windows service and Web components installed on another system to improve performance.

When the database is being installed, the user is queried for several initial settings for the ImageServer. The initial Server Partition with DICOM Application Entity Title and listen port is setup at this time, and an initial filesystem is configured for storing DICOM files. Note that in a configuration where the database and services are being installed on separate systems, care must be taken to ensure the filesystem is accessible to the ImageServer Windows service.

Technical Notes

•There is one executable for the ImageServer: ClearCanvas.ImageServer.ShredHostExe.exe. This executable is a Windows Service that runs in the background that will send and receive DICOM images, respond to DICOM queries and delete image files when the used disk space exceeds a specified watermark. If you want to start or stop that service, you must do so from Control Panel | Administrative Tools | Services.
•The log file for the Windows service is in INSTALLDIR\logs. When reporting a bug, it's recommended that you include the log file in your report.
•The files for the web site are contained in INSTALLDIR\web. A virtual directory is created within IIS to point to this folder.
•The log file for the Web application is in INSTALLDIR\web\logs. When reporting a bug with the Web application, it's recommended that you include the log file in your report.