System requirements

CaseMap Server Web Service requires CaseMap Admin Database residing on SQL Server 2005®, SQL Server 2008® or SQL Server 2012®. Installer will prompt you for SQL Server credentials to create the Admin Database.

CaseMap Server Web Service should only be accessible from within WAN and any access to Web Service from Internet should be blocked.

The CaseMap Server should only be accessible from within the secured network and any access to the CaseMap Server from Internet should be blocked.

CaseMap Server Web Service runs under a Service Account that has the privileges to perform LDAP Queries against Active Directory and has Read/Write/Execute permission on CaseMap Admin database.

CaseMap Server Web Service has two endpoints, one for the CaseMap client application and the other for the CaseMap Admin Console to use.

Admin Console Endpoint Default URL:

 http://[Web_Server_Name]/CMServer/CMServerAdmin.svc

Client Application Endpoint Default URL:

 http://[Web_Server_Name]/CMServer/CMServerClient.svc

CaseMap SQL case databases require SQL Server 2012®, SQL Server 2008® or SQL Server 2005® with SP2 or higher.

Service Broker must be enabled in Microsoft SQL Server for databases that get created when new TextMap SQL cases are created or registered in the CaseMap Admin Console. Enabling Service Broker ensures indexing success when transcripts are imported into a SQL case file. If Service Broker is disabled, indexing and re-indexing will not occur during import or case creation.

When prompted to enter URL for CaseMap Server (optional), please enter an URL ending with CMServerAdmin.svc. CaseMap Server is required to administer TextMap SQL cases and respective users.

Network connection speed, network traffic, database size, and other items may be a factor when evaluating performance. To maximize performance, the user capacity of the CaseMap Server is metered by the hardware. A Pentium CPU will support 25 users. A Xeon or Pentium Hyper Threaded (HT) CPU will support 50 users. Multiple CPU capacity for dual and quad CPU servers. Server capacity is also limited by bandwidth on your LAN and WAN, as well as file server speed.

The CaseMap Server requires a Microsoft Internet Information Server (IIS) v6.0 or v7.0 Web server. If you are installing CaseMap Server on an IIS 6 server, you will need to ensure that aspnet_isapi.dll is allowed.

The application pool identity must be configured for IIS by running the aspnet_regiis utility. You can do this from the command line (running as Administrator).

It must also hold the Log On As Service right in the LSA.

The CaseMap Server should only be accessible inside your protected network and requires installation to a single Windows® Server 2003 or 2008. You should not allow access to the CaseMap Server from the Internet.

If the hosting web site of the CaseMap Server does not have an SSL binding in Microsoft IIS, the SSL endpoints will need to be modified.

To enable support for SSL

To enable support for debugging

Windows Authentication logons can be used by the CaseMap Server, making user administration easy and fully integrated with your existing network policies. CaseMap Server reuses Windows credentials to authenticate a user. Once a user logs on to Windows, CaseMap Server can use that same log on so that a user does not need to re-specify their credentials.

CaseMap Server with Active Directory can be used to verify users' logons and passwords. Logons are checked with Windows Security Controller. Setting this up helps ensure conformation with password policies.

CaseMap Server has two authentication type options:

When using Windows Authentication, you will need to first set up users in the Active Directory and then add the user name to the CaseMap Admin Console. When using Windows authentication, it is important that user names match in both the Active Directory and the CaseMap Admin Console.