Skip to main content
Older versions of Internet Explorer will not support certain site features. Chrome, Safari, Firefox, and Edge will provide the best experience.
Resources
Spok

Installing the Spok Mobile Message Monitoring Service - Spok Mobile Hosted

The page provides Spok IT administrators with procedures to deploy the Hosted Spok Mobile Message Monitoring Service components.

For the procedure to install the Spok Mobile Message Monitoring Service on-premise, see Installing the Spok Mobile Message Monitoring Service.

Deploying the Message Monitoring Database

What: CareConnectMonitoring database - The database is called "CareConnectMonitoring" and resides on the Hosted and this is where we have all the data synchronized (gathered) from the clients and then processed.

Where: On the Hosted database server, or if the Message Monitoring is deployed to a separate server (which has network access to the Hosted database), then on its own MSSQL server, execute the SQL script for creating the CareConnectMonitoring database, which is located in this path: {Hosted Folder}\CareConnect Monitoring\Database\Create.sql.

Configuring the Authentication

What: Hosted.sql - this script must be edited and run so that the Web UI can be accessed from outside of the server it is running on.

Where: on the Hosted Database Server

  1. Open the Hosted.sql script.
  2. Change the “APPSERVER_HOSTNAME” to actual domain name of Message Monitoring server (if behind load balancer for the Web Application, use the LB domain name).
  3. Run the script.

Deploying the Message Monitoring Synch Service

What: CareConnect.Monitoring.SyncService – this is a Windows service deployed on Hosted server (or any other server in the Hosted environment). It calls all the CareConnect.Monitoring.Api services to synchronize (fetch) data from the client’s Premise and Contact Center, and also fetches Notification data (push notifications) from Hosted database. It also processes the synchronized data in a different scheduled job, so that we do not make calculations such as time delta between checkpoints at the time we fetch the data for the reporting UI.

Where: Install this on the Hosted server, or if MessageMonitoring is deployed to a separate server – then on that server.

Current implementation of Message Monitoring Sync Service does not support working in High Availability environment. This means that we need to have only one instance running at the same time.

  1. Copy the {Hosted Folder}\CareConnect Monitoring\Monitoring SyncService folder to the Hosted server folder “D:\Program Files (x86)\Spok\Care Connect\”
  2. Right click on the Monitoring SyncService folder and give all permissions to “NETWORK SERVICE” and “LOCAL SERVICE” users to Monitoring SyncService folder and child folders.

  3. Open Command Prompt as Administrator.
  4. Navigate to the installutil.exe (usually in c:\windows\microsoft.net\framework\v4.0.30319\installutil.exe) folder in Command Prompt, and then write the following command:
    Installutil "D:\Program Files (x86)\Spok\Care Connect\Monitoring SyncService\CareConnect.Monitoring.SyncService.exe"
    • This should install the CareConnect.Monitoring.SyncService windows service.
  5. Open the configuration file CareConnect.Monitoring.SyncService.exe.config and change the following:
    • The “connectionStrings” tag the “DataEntities” and “DataEntitiesLog” should point to the CareConnectMonitoring database.
    • The “Hosted” and “Hosted_Archive” should point to Hosted server and AmcomAmcPremiseCore database (Hosted).
    • Change the Config Service “url” attribute in “cnfgClient”  tag to point to the Hosted Config Service (if behind load balancer, use the load balancer url).
    • In the “appSettings” tag, you can leave all as it is, or if you can change the:
      • Synchronization interval:
        <add key="syncCron" value="0 */15 * * * ?" />
        Where “15” means every 15 minutes.
      • Processing data interval:
        <add key="processCron" value="0 */15 * * * ?" />
        Where “15” means every 15 minutes.
      • Days in the past to make the synchronization from (for all tenants). This is only the initial synchronization. The next intervals will be the one you setup in “syncCron”:
        <add key="syncLookbackDays" value="40" />
  6. You can now start the CareConnect.Monitoring.SyncService from Window’s Services management screen under the name "Spok Monitoring Synchronization Service." It will not do anything until you select Tenants from the Web UI, which is the next step. You can look at the SyncService log file to confirm that the service has been started successfully. The log is located in “logs\sync-log.txt” of the SyncService folder. The location of the log could be changed from CareConnect.Monitoring.SyncServicexe.config as this is log4net setting.

Deploying the Message Monitoring Reporting UI

What: CareConnect.Monitoring.Web – the reporting UI which is again deployed on Hosted and represents reporting of the gathered data, with filtering and sorting. We also configure which clients to include in the Message Monitoring in the Configuration page of this UI.

Where: Once again, you need to deploy this ASP.NET application on the Hosted server, or if Message Monitoring is deployed to a separate server – then on that server.

  1. Copy the “{Hosted Folder}\CareConnect Monitoring\Monitoring” folder to the IIS default folder “wwwroot\”
  2. Open the IIS Manager, find the Monitoring folder under Default Web Site and select Convert to Application, then OK.
  3. Open the Web.Config file in that folder and change DataEntities in the “connectionStrings” tag to point to the CareConnetMonitoring database. In the “cnfgClient” tag change the "url" to point to the Hosted Config Service (if behind load balancer, use the load balancer url).

  4. Start the Monitoring application (you will need to log in), and navigate to Configuration page. You should see all of the tenants there.

For more information about the Spok Mobile Message Monitoring interface, see Spok Mobile Message Monitoring.