Installing iService

You must have administrator access to the servers on which you will be installing iService. You will also need the SQL user that has the create database permission to create the iService database. For security purposes, it is best to have a new SQL account created by your DBA for this purpose rather than use the default SA user account shipped with SQL Server.

This installation guide assumes you have already installed MS SQL Server on your database server, and MS IIS on your web server.

 

hmtoggle_plus1Preliminary Considerations

tipsThe iService Web Application must be installed on a Windows 2008 R2 or newer web server running IIS 7.5 or newer.  We recommend running IIS 8.0 or higher with the Web Sockets feature installed. See https://www.iis.net/configreference/system.webserver/websocket. The web server must have the .NET 4.6.1 or higher run-time package installed (If it is not preset during installation, iService will automatically download and install it during the setup process). The iService Mail Popper Service should be installed on a Windows 2008 R2 or newer Windows Server, and also requires that the .NET 4.6.1 or higher run-time package be installed.  The Master and Tenant databases require a SQL Server 2008 R2 or newer database server.  

Installation requirements for SQL Server are outside the scope of this document.  Note that it is required that the server be configured to allow Windows and SQL Server Authentication. This is because you will create a SQL Server User that the iService web services and mail popper will use to access the iService database.  In addition, it is recommended that you install the SQL Server Reporting Services (SSRS) when you setup your SQL server as this is the engine that iService Reporting will utilize when the reports are formally released. For best security practices, it is recommended to run SSRS on a separate server from your actual database.

When determining what servers to use for the installation of each component, keep in mind the following requirements:

•The Web Server must be able to be reached by your agents and must be able to open a network connection to your SQL server.  This server must also be able to access the outgoing mail server via SMTP for delivery of agent responses.  If you plan on utilizing Secure Messaging to your customers or the Find Answers Knowledge Base, your customers will also need to be able see web pages served by this server.

•The iService Mail Popper Service must be able to access the mail server where incoming messages may be retrieved via POP3, SSL-POP3, or IMAP. This server must also be able to access the outgoing mail server via SMTP for delivery of agent and alert notifications.  These services must also be able to open a network connection to your SQL server.

•The SQL server must be reachable by both the Web server and the Mail Popper Service.

 
hmtoggle_plus1Web Server Prerequisites

As indicated above, .NET 4.6.1 or higher is required for the web application to function.  Installation of .NET is beyond the scope of this document, but it can generally be added as a feature during the Windows Server setup.  Otherwise, the iService installer will detect that it is not present, and will prompt to automatically download the pre-requisite .NET libraries.

The Web Application pool used by iService needs to be set to use .NET CLR 4.0.

 

 

 

 

 

© 2019 One-to-One Service.com, Inc.