Configure the Microsoft SQL Server database for Push Notifications service

If the Mail service is installed on separate computers, but uses the same database name, this task needs to be completed only once.
  1. In the BlackBerry Enterprise Mobility Server Dashboard, under BlackBerry Services Configuration, click Mail.
  2. Click Database.
  3. In the Server field, verify the SQL Server host name and instance. This field is prepopulated with the information you provided during the BEMS installation. The SQL Server must be in the following format: <SQLServer_hostname>\<instance_name>.
    If you configured the database for an AlwaysOn Availability Group, set the server to the AlwaysOn Listener FQDN. Do not use the cluster name or host name of the server in the cluster.
  4. In the Database field, verify the database name. For example, BEMS-Core.
    If you configured the database for an AlwaysOn Availability Group, set the database to the name of the database added to the AlwaysOn Availability Group.
  5. In the Authentication Type drop-down list, complete one of the following tasks:
    • If you select Windows Authentication, the Push Notifications service uses the Windows credentials to access the Microsoft SQL Server database.
    • If you select SQL Server Login, type the username and password used to access the SQL Server database.
  6. By default, the "encrypt=false" property is prepopulated in the Additional properties field, so data between the BEMS and the SQL Server is not encrypted. Existing properties that you have configured are retained. If your environment requires data to be encrypted, and requires verification of the TLS certificate, complete the following:
    Note: If you enable encryption for all data that is sent between BEMS and the SQL Server, it may cause higher than normal CPU usage.
    1. Import the CA certificate that is signing your SQL Server certificate into the Java certificate store. For more information, see Import the CA certificate into the Java certificate store.
    2. Change the encrypt property to true and add trustServerCertificate=false separated by a semicolon (no space before or after the semicolon).

    If your organization uses AlwaysOn support for SQL Server, type MultiSubnetFailover=true.

  7. Click Test.
  8. Click Save.
  9. Restart the Good Technology Common Services service in the Windows Services Manager.