Skip Navigation
  1. BlackBerry Docs
  2. BlackBerry Enterprise Mobility Server 3.5
  3. Configuring BlackBerry Mail
  4. BlackBerry Mail (BEMS Push Notifications service)
  5. Steps to configure Push Notifications
  6. Configure the Microsoft SQL Server database for Push Notifications service

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
    Microsoft SQL Server
     host name and instance. This field is prepopulated with the information you provided during the
    BEMS
     installation. The
    Microsoft 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
      Microsoft SQL Server
       database.
  6. If your organization uses AlwaysOn support for
    SQL Server
    , in the
    Additional Properties
     field, type
    MultiSubnetFailover=true
    .
  7. Click
    Test
    .
  8. Click
    Save
    .
  9. Restart the
    Good Technology Common Services
     service in the
    Windows
     Services Manager.