To install the web application, you must determine where to store the web site on your web server.  By convention, web sites are usually installed in the C:\Inetpub directory on the web server itself.  In our example, we create a new folder named iService at this location.

Create website folder

Once this folder has been created, copy all of the files within the Website directory of our release package into this new folder, shown here:

Copy contents of website

The website folder only includes the iService web pages. The web.config files is located in the For New Installation folder of the archive and must be copied into the root of the iService website folder you just created.

Edit the web.config to specify your connection details.

appSettings - Update the config file with your connection details for your server and database.

 <appSettings>

         <add key="databaseServerName" value="servername or IP" />

         <add key="databaseDatabaseName" value="masterDBname" />

         <add key="databaseUserName" value="username" />

         <add key="databasePassword" value="userpassword" />

         <add key="asmxUrl" value="https://machine.domain.com/iService.asmx" />

         <add key="aspnet:UseTaskFriendlySynchronizationContext" value="true" />

</appSettings>

Server Name - This is the name or IP address of the SQL Server.

Database Name - This is the master database name entered when you created the initial database in the management console.

User Name - This is the SQL user name you specified when creating the initial database.

Password - This is the SQL user password you specified when creating the initial database.

ASMX URL - This is the path to your iservice.asmx file. It was entered when you created your initial tenant, but any valid path to the asmx file will work.

Special Setting for Vue application

The iService user interface was replaced in v9 with a Vue.js application. You can toggle your website between the v8 interface and the Vue.js interface using this update to web.config. Since there are configurations that are only available in v9, it is recommended that you install v9 in a mode that still delivers the v8 (AngularJS) interface to agents. Once you have completed your configuration, and can update web.config to load the Vue.js site for all agents.

To load AngularJS (v8) as the default:

<configuration>
  <appSettings>
    <add key="indexUrl" value="/default"/>
  </appSettings>
</configuration>

To load Vue.js (v9) as the default:

<configuration>
  <appSettings>
    <add key="indexUrl" value="/app"/>
  </appSettings>
</configuration>

In the above examples, only the highlighted text is added to web.config as the other values should already be present in the file. The default behavior is to load Vue,js (/app) for all agents unless the /default setting is in place.

The iService mailpopper service also requires a configuration file. The iServicemailpopper.config file is located in the For New Installation folder of the archive and must be copied into the folder that contains the Windows Service (same as the management console).

Edit the iServicemailpopper.config  file to specify your connection details.

  <databases>

         <database server="servername or IP" name="masterDBname" userID="username" password="userpassword" />

  </databases>

The values should be the same as the web.config.

Open the Internet Information Services (IIS) Manager.  This can be found in the Administrative tools folder usually located in the Control Panel or All Applications links in the Start Menu.

Once IIS is open, right click on the Sites folder and select Add Web Site … from the popup menu.

Add website to IIS

Fill in the Site Name with the friendly name you’d like it to appear as in IIS.  The physical path should match the location that you just placed the iService web site files (in our example, c:\inetpub\iService).  Depending on your desired configuration the Bindings section can be modified to your requirements, but the most straightforward setup is to have a normal http connection on port 80 bind to a host name across all unassigned IP addresses for the server (this is shown in the example screenshot).

Webiste settings

The recommended configuration is to use HTTPS for all connections, and redirect any HTTP requests to use a secure connection. You will configure bindings for port 80 and 443. After the website is added, click on Bindings.

Open Bindings

Then click Add.

Add a binding

Configure port 443 by setting Type = https, Port = 443, and Host Name = your path to the website. Then select the SSL certificate from your server. You will need to import your SSL certificate to the server before it can be selected here.

Configure HTTPS

Click OK.

Next click on the Application Pool option on the left side of IIS:

Application Pool

You should see a new application with the friendly name you gave the web site in the previous step.  Right click this and choose Basic Settings.

Basic Settings

iService uses .NET 4.x, so change the Framework version to the 4.x version, and click OK.

.NET Framework v4.x

Now we need to be sure that the new Application Pool has the proper permissions to access the folder you made in the earlier step.  Right click on the web site in IIS and choose Edit Permissions.

Edit Permissions

Choose the Security tab, and press the Edit.. button. In the new window click Add.

Permissions for iService

In the text area, type IIS AppPool\<appname> where <appname> is the friendly name you gave the website in the earlier step.  In our example, it would be IIS AppPool\iServiceAssistant Web Site.

Select Users or Groups

Press OK.  

Give the app pool Full Control permissions of the folder and Press OK through both windows.

Folder permissions for the iService website