This topic describes how to install and configure the LEADTOOLS Medical Web Viewer Demo.
The entire medical web viewer’s site folder structure is contained in the <INSTALLDIR>\Examples\DotNet\PACSFramework\MedicalWebViewer\JS\MedicalWebViewerDemo\ folder.
Supported Operating System(s) - Windows 7 and newer - Server 2008 and newer
.NET Framework - The LEADTOOLS services are WCF service classes - Microsoft .NET Framework 3.5 or newer installed
Microsoft Visual C++ Redistributables - Microsoft Visual C++ 2008 SP1 Redistributables are required for .NET 3.5 - Microsoft Visual C++ 2010 SP1 Redistributables are required for .NET 4.0
SQL Server - At least SQL Server Express 2005 or newer is required
By default, the LEADTOOLS configuration demos configure the LEADTOOLS Windows services and web services to run as the LocalSystem (NT Authority\System) identity. This is a special built-in account that has full access to the local system. SQL Server 2008 R2 and earlier included this account as a login with full access to SQL Server. Microsoft considered this a security flaw and the login was removed from the newer versions of SQL Server. For more information about creating a login, refer to the Microsoft topic, SQL Server – "Create a Login", at https://docs.microsoft.com/en-us/sql/relational-databases/security/authentication-access/create-a-login
If enabled in SQL Server, SQL Server authentication may be used. If using SQL authentication, before running the LEADTOOLS Database Configuration demo, the SQL login must already exist. When adding the SQL login, make sure that the option “Must change password” is unchecked. Once the SQL login and user is created, connect to the database engine in Visual Studio or SQL Server Management Studio to test.
If using Windows authentication, create a service user account, a SQL log in, and a user with the appropriate permissions to access the server and databases. Ignore the following dialog when it appears:
Use either Windows or SQL authentication to log into SQL Server. The mapped user must have the correct permissions to perform the functions required by the configuration tools and demos. For development, associating the user with the sysadmin server role and the dbowner role is the quickest but is not recommended for production due to obvious security concerns.
If using Windows authentication, you will need a Windows user account, a SQL login for the Windows user account, and a SQL user account mapped to the SQL login associated with the Windows user account.
Ensure the Windows user account is set up with access to the following items:
For more information, refer to https://marketplace.visualstudio.com/items?itemName=TypeScriptTeam.TypeScript10ToolsforVisualStudio2012
IIS with at least the following features is required (Select ALL options under each section): - Web Management Tools - World Wide Web Services
If Windows 8 or newer is being used, the following features are required: .NET Framework 4.5 Advanced Services - ASP.NET 4.5 - WCF Services
Note: In Windows 8 / Server 2015 and newer, be sure to select both version 3.5 and 4.5.
Open the Windows Start menu and start typing “Turn Windows features on or off” -> open the Windows Features dialog box and make the following selections (both a listing of the selections and screenshots of the selections within the dialog box are provided below):
Perform the following steps to configure the medical web viewer:
The Database Configuration Demo will attempt to enumerate the SQL Servers available on the network. If the demo was unable to enumerate the SQL Servers, it may display a message box similar to the following figure:
A Warning or Connection String Validation message box will be displayed, as shown in the following figure:
Click OK. You may receive a "Named Pipes Provider, error: 40" message box, as shown in the following figure:
If you receive this message, open your SQL Server Configuration Manager and select the drop-down display for the SQL Server Network Configuration. Select Protocols for MSSQLSERVER, which will display 'Named Pipes' on the right. Make sure this is set to 'Enabled', as shown in the following figure:
Now restart your MSSQLSERVER service by going to the Control Panel, choosing Administrative Tools and then Services. Once selected, a window similar to the following one should display. Choose the SQL Server (MSSQLSERVER) by right-clicking it and setting the Server to Stop. After it has stopped, right-click the SQL Server (MSSQLSERVER) and select Start, as shown in the same figure.
Now try to click Validate from the ChooseDefaultSqlServerConfiguration dialog box (the dialog box displayed in Step 5). If validation is successful, the Connection String Validation message box (as shown in the following figure), will appear.
If, instead, a Warning message box appears, click OK and refer to the Troubleshooting the LEADTOOLS Service Host Manager - Remote Server Returns Error 500 section below to correct the warning.
The selected utility loads and is shown in the following figure:
You should now be able to navigate to the link to the demo in the screenshot above. Login using the credentials set in Step 7. At this point the LEADTOOLS Medical Web Viewer demo is fully functional and you can begin your testing. You should see the default login page load. Try logging in, searching for studies and series, and selecting a series to see it loaded into the viewer.
The HTML5 Viewer requires that a LeadtoolsLicense.txt file be placed into a sub-folder in the Members directory. Adding this license file will remove the NAG message seen by the client. This LeadtoolsLicense.txt file is generated separately from the *.LIC and *.LIC.KEY files. Note that the LeadtoolsLicense.txt file cannot be created based on either of those files. This file must be generated by the LEAD Sales department and provided to you. After you receive the file, create a folder called "LEADTOOLS" in the following directory:
Inside the "LEADTOOLS" folder, add the LeadtoolsLicense.txt file. The following file should now exist:
Depending on the order in which the prerequisite steps were completed, it is possible that the handlers for WCF were not installed correctly. To correct this, start an elevated cmd prompt and run the following commands:
%SYSTEMROOT%\Microsoft.NET\Framework\v3.0\”Windows Communication Foundation”\ServiceModelReg –i
%SYSTEMROOT%\Microsoft.NET\Framework64\v3.0\”Windows Communication Foundation”\ServiceModelReg –i
When you have finished trouble-shooting, return to Step 7.