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.
Upgrading RabbitMQ and Erlang
This article provides instructions for upgrading to RabbitMQ 3.8.3 and Erlang OTP 22.
Installing Spok Mobile Services
These instructions describe how to install Spok Mobile services using the Care Connect Suite Installer.
Installing the Spok Mobile Message Monitoring Service
This article describes how to deploy the Spok Mobile Hosted Message Monitoring Service components.
Converting the PFX Certificate to PEM Certificates for the Spok Notification Framework (for CCS 1.9.2.160)
Three PEM certificates are required in order to secure the Spok Notification Framework via TLS. If your customer site will be using the Spok Notification Framework to support non-GCM (Google Cloud Messaging) Android Devices, a Spok PSG professional will perform the conversion process, as described in this article.
Converting the PFX Certificate to PEM Certificates for the Spok Notification Framework (for CCS 1.9.3.x)
This procedure must be completed following the installation of Spok Mobile at customer sites where the Spok Notification Framework will be used to support non-GCM Android devices. This procedure is completed by a Spok PSG professional to convert PFX format certificates to the three PEM format certificates needed to make the framework secure via TLS.
Configuring Spok Mobile Settings and Devices
These pages contain the steps for configuring Spok Mobile 4.6 settings and devices.
Optional Spok Mobile Configurations
This topic describes how to set up optional configurations in addition to the standard, required configurations which must be done for every Spok Mobile implementation.
Post-Implementation Considerations
These articles describe some additional considerations after you have implemented Spok Mobile.
Resetting IIS on the Spok Mobile Server
This topic describes how to reset IIS on the Spok Mobie Server.

 

Spok

Installing the Spok Mobile Message Monitoring Service

This article describes how to deploy the Spok Mobile Hosted Message Monitoring Service components.

For more information about how to install the Spok Mobile Message Monitoring Service on-premises, see Installing the Spok Mobile Message Monitoring Service.

Deploying the Message Monitoring Database

The CareConnectMonitoring database resides on the Spok Hosted server, and contains all data which has been synchronized from clients. To create this database, execute the SQL script Create.sql located in {Hosted Folder}\CareConnect Monitoring\Database\. Execute this script on the Hosted server; if Message Monitoring is deployed to a different location with network access to the Hosted database, execute the script on that server instead.

Configuring the Authentication

The steps below will allow the Web UI to be accessed from outside the server on which it is running.

  1. Open the Hosted.sql script.
  2. Change “APPSERVER_HOSTNAME” to the actual domain name of the Message Monitoring server. If this server is located behind a load balancer for the Web Application, use the load balancer domain name instead.
  3. Run the script.y

Deploying the Message Monitoring Sync Service

The CareConnect.MonitoringSyncService is deployed on the Hosted server and any other server in the Hosted environment. It prompts all of the CareConnect.Monitoring.Api services to synchronize (fetch) data from the client’s Spok Mobile server and Contact Center, and also fetches push notification data from the Spok Mobile Hosted database. It processes the synchronized data in a scheduled job, so that the system does not make calculations such as time between checkpoints at the time it fetches the data for the reporting UI.

To deploy the CareConnect.MonitoringSyncService, do the following on the Hosted server; if the Message Monitoring service is deployed to a separate server, perform these steps on that server instead.

The Message Monitoring Sync Service does not support high availability environments.

  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 the Monitoring SyncService folder and child folders.

  3. Open  a command prompt as an administrator.
  4. Navigate to installutil.exe, usually located in C:\windows\microsoft.net\framework\v4.0.30319\.
  5. Run the following to install CareConnect.Monitoring.SyncService:
    Installutil "D:\Program Files (x86)\Spok\Care Connect\Monitoring SyncService\CareConnect.Monitoring.SyncService.exe"
  6. Open the configuration file CareConnect.Monitoring.SyncService.exe.config and change the following:
    • Change the tags connectionStrings, DataEntities, and DataEntitiesLog to point to the CareConnectMonitoring database.
    • Change Hosted and Hosted_Archive to point to the Hosted server and the AmcomAmcPremiseCore database.
    • Change the Configuration Service url attribute in the cnfgClient tag to point to the Hosted Configuration Service. If the service is behind a load balancer, set the url attribute to the load balancer URL.
    • You can either leave the appSettings tag as it is, or make the following optional changes:
      • Change the synchronization interval to the following:
        <add key="syncCron" value="0 */15 * * * ?" />
        Where “15” means every 15 minutes.
      • Change the processing data interval to the following:
        <add key="processCron" value="0 */15 * * * ?" />
        Where “15” means every 15 minutes.
      • Change the date from which the initial synchronization should be made (for all tenants). This only determines from which prior date the initial synchronization will be made; subequent intervals will use the settings from syncCron.
        <add key="syncLookbackDays" value="40" />
  7. You can now start the Monitoring Service from the Windows Services management screen. You can find it listed as "Spok Monitoring Synchronization Service." It will not do anything until you select tenants from the Web UI (see Installing the Spok Mobile Message Monitoring Service - Spok Mobile Hosted). You can look at the SyncService log file to confirm that the service has been started successfully. The sync-log.txt log file is located in the logs\ directory of the SyncService folder. Because the location of the log is a log4net setting, it can be changed in CareConnect.Monitoring.SyncServicexe.config.

Deploying the Message Monitoring Reporting UI

CareConnect.MonitoringWeb is the reporting user interface, which reports gathered data and allows you to filter and sort it. You can also use the Configuration page of the reporting UI to configure which clients to include in the Message Monitoring service. The reporting UI is an ASP.NET application on the Hosted server (or, if Message Monitoring is deployed on a different server, on that server instead). 

  1. Copy the {Hosted Folder}\CareConnect Monitoring\Monitoring folder to the IIS default folder \wwwroot\
  2. Open the IIS Manager and navigate to the Monitoring folder under Default Web Site.
  3. Select Convert to Application, then click OK.
  4. Open the Web.Config file in the Monitoring 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 Configuration Service; if the service is behind a load balancer, use the load balancer URL instead.

  5. Start the Monitoring application 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.