This is a guide for customers self hosting Case Manager which would like to implement the web and mobile app infrastructure.
Prerequisites
? To access the App, you will need the web version of Case Manager installed on your own server. Following is a list of requirements to install the web version of Case Manager on your own server. It’s rather technical, so we suggest you consult your IT company:
? If IIS is already installed, please ensure the required options outlined in the IIS server installation section below is installed.
? A web server running IIS with Dot Net 4.8 installed.
? Windows Active Directory used to manage permissions to the database and the Case Manager document share. We normally recommend a user named ‘CaseManagerWeb’. This user will be set as the identity for the application pool that hosts the web site.
? A domain name for the site. It’s suggested you use a subdomain of your public domain (e.g.
‘casemanager.yourdomain.com.au’) which can be created by adding an A record to your existing domain record.
? A firewall rule to forward ports 80 and 443 for the IP address associated with the domain name. Port 80 is not mandatory, and we only use it to redirect to secure port 443, but without it users will have to prefix the URL with “https://”.
? An SSL certificate with TLS1.2 enable and issued after March 2018 to secure the site and enable Apple mobile devices to access the app. If using a subdomain it’s recommended that you purchase a wildcard certificate (‘*.yourdomain.com.au’) so that it can be used for other purposes. Free Self generated certificates will not work.
Install IIS Server on your web server
? Connect to the web server using RDP or console.
? Click the Server Manager icon in the Windows taskbar:
? Click the Add roles and features link:
? Select the Role-base or feature-based installation option:
? Select the current machine for the Server Pool list:
? Select the Web Server (IIS) role:
? Allow the addition of features that are required for the Web Server (IIS) role:
? Skip over the Features page (do not add any additional features).
? On the Web Server (IIS) / Role Serves page, enable only the following options (disable all others):
? Web Server
? Common HTTP Features
? Default Document
? HTTP Errors
? Static Content
? Health and Diagnostics
? HTTP Logging
? Performance
? Static Content Compression
? Dynamic Content Compression
? Security
? Request Filtering
? Application Development
? .NET Extensibility 4.5
? ASP.NET 4.5
? ISAPI Extensions
? ISAPI Filters
? Websockets Protocol
? Management Tools
? IIS Management Console
? Management Service
Configure Internet Information Server (IIS)
Preparation
? Open the Internet Information Server (IIS) Manager console.
Application Pool Defaults
? Select “Application Pools” on the left, and then “Set Application Pool Defaults” on the right.
? Change “Enable 32-Bit Applications” to True.
? Under CPU, change “Limit (percent)” to 80 and and “Limit Action” to ThrottleUnderLoad.
? Change “Load User Profile” to True.
? Click OK to save changes.
Install yourcompanyname.com SSL Certificate
? Go to Server Manager > Roles > Web Server (IIS) > IIS Manager > Server name
? Double-click the the Server Certificates icon:
? Import the yourcompanyname.com certificate into the Personal certificate store, allowing the certificate to be exported (example below shows the casemanager.biz certificate):
Configure Web Management Service
? Double-click the Management Service icon:
? Enable remote connections using the yourcompanyname.com SSL certificate, then start the service:
Deploying the sites and creating app pools.
Copy files to the file system
? Request Case Manager to send you the installation files.
? You will only need the mobileapi and wwwroot folders within the zip file
? Extract files to a local folder on the web server. Ensure that the file is “unblocked” by going to file properties of the .zip folder before extracting. If a D: drive is present this should be the \CaseManagerData\Web folder (may need to be created), otherwise use C:\inetpub\casemanager (creation of “casemanager” subfolder may be required).
? Extract wwwroot as is to this CaseManager folder.
? Extract mobileapi as is to this CaseManager folder.
Set the security permissions on the files.
? Find out the exact users ID for IIS users, go to the properties of C:\inetpub\wwwroot and look for the username that has IIS.
? Add and apply the following permissions to both folders extracted:
? read/execute permission to:
? CaseManagerApp group (assuming this was created when Case Manager application was installed), IIS_IUSRS, Users, CaseManager web account (as mentioned in the body of the email that accompanied this document, if this account needs to be created it only needs to be a member of the CaseManagerApp group).
? Ensure full control is assigned to
? System
? Admin login used at the time of deployment
? Local Administrator
? Remove all other inherited permissions and apply permissions to all child objects.
? Modify permissions for the CaseManagerWeb account on tmpupload for both web folders ( mobile and web) – add “users” and if page does not load properly later add the same “users” with read and execute access to the “web” folder
? Set database connection string in web.config in the wwwroot or web folder. Please note the mobileapi application inherits the web.config connection string settings from the parent web wwwroot folder. This .config file can be modified with notepad.
? Below is a sample of the connection string, the sections highlighted in red will need to be updated.
<connectionStrings>
<add name=”CaseManager” connectionString=”data source=SQLServerName\Instance;Initial Catalog=CaseManagerDatabaseName;integrated security=True;MultipleActiveResultSets=True” providerName=”System.Data.SqlClient” />
</connectionStrings>
? Create an app pool called “Case Manager” and navigate to the identity section in advance setting. Enter the CaseManager web account username and password (as mentioned in the body of the email that accompanied this document, if this account needs to be created it only needs to be a member of the CaseManagerApp group). Ensure
Create the websites.
? From the IIS console create the main website:
? Enter the casemanager.yourcompanyname.com in the “Site Name” field.
? Select the “Case Manager” app pool that was created in the previous steps.
? Browse to the physical path of the Case Manager web folder named wwwroot which was previously extracted.
? Set https binding (do not specify an IP) with the SSL certificate, then right click the site and go to edit bindings to add the http binding.
? Start the website.
Add the mobile application
? Add an application to the main website called “mobileapi” (right click casemanager site -> Add application).
? Select the “Case Manager” app pool.
? Configure the physical path to point to the mobileapi folder within the Case Manager web folder.
Test Case Manager Interface
? Using the web URL defined, use Google Chrome browser to launch and login to Case Manager.
? Once logged in, browse cases and add a test document to confirm the document store is configured correctly
? Test the mobile app after installing it on your smart device. Details on installation at the link below:
? http://learning.casemanager.biz/App/InstallApp.htm
Troubleshooting
Errors when loading the page. Example:
If you get the message agave, this means that the IIS server and the website is online but it is having an issue loading the page. Common causes are:
? Connection strings are not set correctly
? The server has ran out of memory
? If this occurs after an upgrade from a previous version of Case Manager web, the old devexpress files were not removed before copying the new files over.
To identify the issue, you can turn “Custom Errors” off to obtain more details. To do this:
1. Open the “Web.Config” file and look for the “Custom Errors” line.
2. Change the <customErrors mode=”On” /> to <customErrors mode=”Off” />
3. Save the file, refresh the site and it will give you more detailed errors. Example below:
10
Loading...