WhosOn Server

Updating to WhosOn Version 19.1.497

This guide provides step by step directions on updating from any WhosOn 2019 version to build .497.

System Requirements

  • Windows Server 2012/2016/2019 Standard or Core.

  • 1Gb RAM Minimum, 2Gb or higher recommended.

  • .NET Framework 4.6.2 or higher.

  • IIS with ASP.NET.

  • SQL Server 2012 or higher (SQL Server 2017 recommended).

  • Application Request Routing (ARR)

What's New

New: Web Client

The WhosOn 2019 Server now supports client connections via WebSocket. A new 'Web Client' is available that allows operators to use a browser to login and take chat requests. It has a similar look and feel to the modern client. 

Currently the Web Client is in beta and supports Chatting, Transfers, Operator-To-Operator chat, Status setting. More features will be added to the Web Client on an on-going basis.

New: Data Portal

We have introduced a new data portal that uses OData.

Configuring URL Rewrite Rule

Access IIS URL rewrite rule and delete the inbound rule tied to the server farm. Add a new blank routing rule. (The name of this rule is not important) In the Match URL section, set Request URL to "Does Not Matches the Pattern", set Using to "Wildcards" and set the Pattern to */*

Expand Conditions and add four rules, one for each of the WhosOn applications. The rules should be set up as follows:

Input Type Pattern

{REQUEST_URI} Does not Match the Pattern /webclient

{REQUEST_URI} Does not Match the Pattern /whosoncharts

{REQUEST_URI} Does not Match the Pattern /newchat

{REQUEST_URI} Does not Match the Pattern /settings

{REQUEST_URI} Does not Match the Pattern /clientws

{REQUEST_URI} Does not Match the Pattern /data

In the "Action" sections, set the Action type to "Rewrite". Add the following rewrite url: (where "gateway" is the name of the server farm)

If you have altered the application names, then you will need to modify the Pattern to the names you have given the applications within the Site

Backup Data

We always advise backing up before beginning any major software upgrade. Before you start upgrading to WhosOn 2019, we recommend that you take these backup actions:

  1. Backup the following directories:

    • C:\Program Files (x86)\Parker Software\WhosOn Installable\

    • C:\ProgramData\Parker Software\WhosOnV7

  2. Keep these backups in an easy to find directory, such as C:\WhosOn > 2019 Backup\

  3. Backup the SQL Server database to disk in case of any problems

Uninstall WhosOn

After backing up all data, Uninstall the WhosOn application from your system.

Installing and Configuring WhosOn Installable Server

Download the WhosOn Installable Server 2019 from https://www.whoson.com/downloads

Installation of WhosOn requires a SQL database to hold chat and visitor data. If you do not have your own instance of SQL server to use, you will need to install SQL as part of the install process for WhosOn.

Enabling Server Proxy

  1. Open IIS

  2. Select the server level node

  3. Open "Application Request Routing Cache"

  4. Select "Server Proxy Settings" within the Actions pane

  5. Select "Enable proxy"

Configuring WhosOn Web Client

  1. Create the webclient url rewrite rule.

    a. Access Internet Information Services Manager (IIS)

    b. Select URL Rewrite

    c. On the right-hand actions pane, select "Add Rule(s)"

    d. Select "Blank rule" under Inbound rules

    e. Enter a name "WhosOn_Webclient" (name not important)

    f. Set Requested URL to "Matches the Pattern"

    g. Set Using to "Regular Expressions"

    h. Enter "(clientws.*)" as the Pattern

    i. Under Action, set the action type to "Rewrite"

    j. Enter "" as the Rewrite URL

  2. Add Registry Key

    a. Open server registry

    b. Navigate to - HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ParkerSoft\WhosOn\7\Settings

    c. Create a new string value with the name "WebClientSocketURL" and Data "wss://{yourdomain.com}/clientws/"

  3. Access the WhosOn Service Manager

    a. Go to Server Settings

    b. Select Web Client

    c. Enable Client WebSocket Interface

    d. Toggle "Use IIS Proxy" on

    e. Set the External WebSocket Address to "{yourdomain.com}/clientws/"

    f. Toggle "External WebSocket Secure" on