BlackBerry Management Pack Custom connection string to BES database

BlackBerry Management Pack Custom connection string to BES database

 

In most cases the BlackBerry Management Pack is able to construct the connection string in order to connect to the BlackBerry Enterprise server database. In special cases where SQL standby servers are used or other forms of SQL redundancy, the connection string might not reflect the correct configuration. An example is that the BlackBerry management pack cannot construct a connection string that reflects a standby server. In order to allow the BlackBerry Management Pack to connect to SQL back-ends with varying configurations, the option is given to create a custom connection string by overriding the default configuration. In order to override the default connection string follow the steps below.

 

  1. The default connection string outomatically generated by the BlackBerry Management Pack has the following form: Provider=SQLOLEDB;Database=BESMgmt;Server=olxsql01;Trusted_Connection=Yes;IntegratedSecurity=SSPI
  2. The management pack cannot automatically build connection strings for failover or standby databases, so you will need to override the default connection string to the following format (You will need to determine the exact format of the connection string for your environment):Provider=SQLOLEDB;Database=BESMgmt;Server=olxsql01;Failover Partner=olxsql02;Initial Catalog=myDataBase;Trusted_Connection=Yes;IntegratedSecurity=SSPI.
  3. Once you have determined the correct connection string, in the SCOM console browse to the authoring section and set the scope as shown in the screenshot:
  4. Then select: Authoring -> Management Pack Objects -> Object Discoveries and double click BlackBerry 5.0.x Enterprise Server Discovery
  5. Select the Overrides tab and select For all objects of class: BlackBerry 5.0.x servers.
  6. In the Overrides Properties window check the checkbox next to ConnectionString and enter the new connection string into the Override Value field. Save the override in an appropriate management pack and save the changes.

Using the BlackBerry Log File Alert Template in the BlackBerry 5.0.x Management Pack

Using the BlackBerry Log File Alert Template in the BlackBerry 5.0.x Management Pack

The BlackBerry Management Pack for BES 5.0.x contains a number of rules that check the log files for particular events which could have an impact on your BlackBerry environment. The standard rules in the BlackBerry management pack should be sufficient to monitor your BlackBerry logs, but in certain cases you might want to monitor additional entries. To accommodate for this, the BlackBerry Management Pack contains templates for creating custom rules in the Authoring section of the Operations Manager Console.

The following example will show you how to create a custom Log File Alert Rule for checking the state of a ‘BlackBerry Messaging Agent’ by using the available template in the BlackBerry Management Pack.

In the Operations Manager Console navigate to the Authoring section of the Operations Manager Console and select the BlackBerry Log File Alert Template.

 

Right click the BlackBerry Log File Alert Template and select Add Monitoring Wizard

 

Select the BlackBerry Log File Alert Template in the Select Monitoring Type wizard page and click Next.

 

On the Name and Description page enter a logical name (Messaging Agent Not Started in this example) and description and select a management pack in which you would like to store the custom rule. Click Next.

 

In this example we are looking for the phrase “not started in the MAGT logs.

 

On the Alert Configuration page select the BlackBerry Mailbox/Messaging Agent (MAGT) from the Log File dropdown box. In the Query pattern box enter the string to search for in the log file. You can use either Simple Expressions or Regular Expressions. In this example we look for the Simple Expression not started. We can set the Severity of the alert to Critical or Warning in the Severity dropdown box, in this example we set the severity to Warning.

 

Click Create to finish creating the custom rule. The custom rule is now visible in the BlackBerry Log File Alert Template view.

 

BlackBerry components that need licensing when using the OpsLogix BlackBerry Management Pack

BlackBerry components that need licensing when using the OpsLogix BlackBerry Management Pack

As enterprise grade software, the BlackBerry Enterprise Server software can be installed on a single server, or the BlackBerry Enterprise Server roles/components can be installed on multiple separate servers. When monitoring the BlackBerry roles/components with the OpsLogix Management Pack for BES, the Management Pack is licensed per BlackBerry server. The overview below shows if/when a license is needed for the BES Management Pack, when the BlackBerry Enterprise Server roles/components are installed over multiple servers.

List of possible services (BlackBerry components) that need to be licensed when installed on a BlackBerry server:

  • Attachment Service
  • Enterprise Server (service)
  • MDS Service
  • Router Service

If one of the above services is installed on a BlackBerry server, the BlackBerry server with the service installed always needs to be licensed. If multiple services are combined on one server only one license is needed for that particular server.

List of possible services (BlackBerry components) that DO NOT need to be licensed:

  • Administration Service
  • Collaboration Service
  • BAS (BlackBerry Administration Service)
  • BMS (BlackBerry Monitoring Service)

If one or more of the above services that do not need licensing is installed on a BlackBerry server (and none of the services are installed on the same server that do need licensing), no license is required for the BlackBerry server.

 

Blackberry 10.2.0.x Management Pack Guide for Operations Manager 2012

Blackberry 10.2.0.x Management Pack Guide for Operations Manager 2012

Blackberry 10.2.0.x Management Pack

Guide for Operations Manager 2012

Published: Feb 2014

Copyright

The information contained in this document represents the current view of OpsLogix on the issues discussed as of the date of publication and is subject to change at any time without notice to you. This document and its contents are provided AS IS without warranty of any kind, and should not be interpreted as an offer or commitment on the part of OpsLogix, and OpsLogix cannot guarantee the accuracy of any information presented. OPSLOGIX MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.

The descriptions of other companies’ products in this document, if any, are provided only as a
convenience to you. Any such references should not be considered an endorsement or support by
OpsLogix. OpsLogix cannot guarantee their accuracy, and the products may change over time. Also,
the descriptions are intended as brief highlights to aid understanding, rather than as thorough
coverage. For authoritative descriptions of these products, please consult their respective
manufacturers.

This deliverable is provided AS IS without warranty of any kind and OPSLOGIX MAKES NO WARRANTIES, EXPRESS OR IMPLIED, OR OTHERWISE.

All trademarks are the property of their respective companies. © 2009 OpsLogix BV. All rights reserved.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

  1. Table of Contents

2. Copyright 2

3. Table of Contents 3

4. BlackBerry MP Installation Guide 4

5. Document Version 5

6. Prerequisites 6

7. Configuring Prerequisites 7

8. Importing the License Management Pack 8

9. Importing the BlackBerry Management Pack 9

10. Configuring the BlackBerry Management Pack 10

11. Licensing the BlackBerry Management Pack 13

  1. BlackBerry MP Installation Guide

OpsLogix intelligent management pack for BlackBerry 10.2.0.x, checks the status of your BlackBerry service as a whole, checking both BDS (BlackBerry Device Service) and UDS (Universal Device Service) components. Using System Center Operations Manager’s built-in Live Views, it provides the BES administrator insight in the root-cause of the problem. OpsLogix intelligent management pack for BlackBerry provides comprehensive state views and performance views on your BlackBerry infrastructure.

  1. Document Version

This guide was written based on version 10.2.0.501 of the OpsLogix BlackBerry Management Pack.

Release Date Changes
Feb 2, 2014 First draft
  1. Prerequisites

  • The OpsLogix BlackBerry Management Pack requires Microsoft System Center Operations Manager 2012.
  • The OpsLogix BlackBerry Management Pack makes use of Microsoft .NET Framework 3.5.Microsoft .NET Framework 3.5 must be install on all BlackBerry Enterprise Servers 10.x in order to monitor some of the critical BlackBerry components.
  • Agent Proxy must be enabled on all Operations Manager agents installed on BlackBerry servers.
  • A Microsoft Windows Domain account must be present which has local administrator rights on the BlackBerry servers and also has read permissions on the BlackBerry (BESMgmt) database.
  1. Configuring Prerequisites

Enabling Agent Proxy

The BlackBerry Management pack makes use of the Agent Proxy functionality in Operations

Manager 2012. Please make sure you enabled Agent Proxy for all the BlackBerry servers in your environment. To enable agent proxy, in the Operation Manager console, go to the
Administration pane. In the Administration pane select Agent Managed, then from the list right click on you BlackBerry server and select Properties. On the Agent Properties dialog select the Security tab and check the Allow this agent to act as a proxy and discover managed objects on other computers checkbox. Repeat this step for all your BlackBerry servers.

  1. Importing the License Management Pack

If this is the first time you are importing an OpsLogix Management Pack, you need to import the Licensing Management pack. If you have already installed OpsLogix Management Packs in your current SCOM environment previously, please make sure that the version is 2.3.2.7 or later.

In the Administration section of the Operations Manager 2012 Console complete the following steps:

1. Right click Management Packs -> Import Management Packs… -> Add -> Add from Disk

2. Browse to the location where you unpacked the OpsLogix BlackBerry Management Pack.

3. Import the following files:

a. OpsLogix.BaseLibrary.mp

e. OpsLogix IMP – Licensing Dashboard v2.3.2.7.mpb

4. Click Open -> Import

The OpsLogix Licensing Dashboard is now visible in the Monitoring section of the Operations Console under the following node:

Monitoring -> OpsLogix -> OpsLogix Licensing Dashboard

  1. Importing the BlackBerry Management Pack

In the Administration section of the Operations Manager 2012 Console complete the following steps:

1. Right click Management Packs -> Import Management Packs… -> Add -> Add from Disk

2. Browse to the location where you unpacked the OpsLogix BlackBerry Management Pack.

3. Import the following files OpsLogix IMP – BlackBerry 10 Management Pack (v10.2.0.501).mpb

4. Click Open -> Import

  1. Configuring the BlackBerry Management Pack

In order for the BlackBerry Management Pack to correctly monitor you BlackBerry environment, the Management Pack needs to be configured. To configure the BlackBerry Management pack the following steps need to be completed:

Configuring the RunAs Accounts

In the Administration section of the Operations Manager 2012 Console complete the following steps:

BlackBerry database Run As Account

  1. Navigate to Run As Configuration -> Accounts in the Administration view and right click Accounts -> Create RunAs Account.
  2. On the Introduction Page click Next.
  3. On the General page in the RunAs Account type dropdown box select Windows and enter BlackBerry Database Account in the Display name text box. Optionally add a description in the Description text box.
  4. On the Windows RunAs Account page, enter the name of the Windows Account that has access to the BlackBerry database and local administrator rights on all BlackBerry Servers which are to be monitored. Enter the password for the account in the Password and Confirm password text boxes. Select the appropriate domain in the Domain text box.
  5. On the Distribution Security page select the security level that is appropriate for your organization. If you chose the More secure option, make sure you include all your BlackBerry servers.
  6. Click Create.
  7. Click Close.

Configuring the RunAs Profiles

In the Administration section of the Operations Manager 2012 Console complete the following steps:

BlackBerry Enterprise Server Database RunAs profile

  1. Navigate to Run As Configuration -> Profiles in the administration view.
  2. In the right pane right click BlackBerry 10.x Database Run As Profile and select
    Properties.
  3. On the Introduction page click Next.
  4. On the General Properties page click Next.
  5. On the Run As Accounts page click Add.
  6. In the Add a Run As Account dialog box, select BlackBerry Database Account from the
    Run As Account dropdown box.
  7. In the Add a Run As Account dialog box, select the A selected class, group, or object radio button and click the Select… button and from the dropdown select Group…
  8. In the Group Search popup dialog search for BlackBerry 10.x Run As Instances (enter BlackBerry 10.x Run As Instances in the Filter by field and click search). From the Available Groups list select BlackBerry 510.x Run As Instances and click OK twice.
  9. Click OK.
    The result should look as in the screenshot:

 

  • Click Save.
  • On the Completion page you can choose to make use of more-secure/less-secure Run As
    account distribution. If you make use of the more-secure distribution, make sure that you
    select all Blackberry servers for account distribution.
  • Click Close.

 

  1. Licensing the BlackBerry Management Pack

In order to import a license you should have received a valid license key from OpsLogix. If you did not receive a valid license key please contact support@opslogix.com or sales@opslogix.com to obtain a license key.

In the OpsLogix License Manager in the Monitoring section of the Operations Console click the Add License button.


In the Add License popup box paste the license key you received (taking care that there are no trailing spaces, empty lines, or carriage returns) and click the Import License(s) button.


The License is now imported. Because of the license model later – after importing and configuring the BlackBerry Management Pack – you will need to return to the licensing console to enable the license for each BlackBerry server you would like to monitor.

To assign a license to a BlackBerry server, navigate to the OpsLogix License Manager in the Monitoring section of the Operations Console and select the Assign tab.


From the Dropdown list box select the OpsLogix.IMP.BlackBerry.5.0 license (Note that the same license is used for the BlackBerry 5.0 Management Pack as the BlackBerry 10 Management Pack). Check all the BlackBerry servers that you wish to license and click the Update button.

BlackBerry Management Pack – Configuring Run As Profiles for the OpsLogix IMP BlackBerry Management Pack 5.0.2.x

BlackBerry Management Pack – Configuring Run As Profiles for the OpsLogix IMP BlackBerry Management Pack 5.0.2.x

General

Depending on the configuration of your BlackBerry environment, it is important to have your Run As profiles configured correctly.

 

Configuring the BlackBerry 5.0.x Database Run As Profile

There are five possible scenarios for which you can configure the BlackBerry Management Pack BlackBerry 5.0.x Database Run As Profile. The following article details three of the five scenarios which are:

1. Single BlackBerry server with the BlackBerry database installed locally on the BlackBerry server

2. Single BlackBerry server with Blackberry database installed on a separate server

3. Multiple BlackBerry servers which share a database on a separate server

Scenario 1: Single BlackBerry server with the BlackBerry database installed locally on the BlackBerry server

Depending on the configuration of Operations Manager usually you don’t need to specify a Run As account in the BlackBerry 5.0.x Database Run As Profile for this profile because the Operations Manager agent uses the local system account which has access to the local BlackBerry database. If your default Action Account runs under a low permissions Windows Domain account then you might need to create a separate Run As account and specify it in the BlackBerry 5.0.x Database Run As Profile. In order to do this, please follow the chapters: Creating a Run As account for the BlackBerry 5.0.x Database Run As Profile and Linking the Run As account to the BlackBerry 5.0.x Database Run As Profile by Class.

Scenario 2: Single BlackBerry server with Blackberry database installed on a separate server

If your default Action Account runs under a low permissions Windows Domain account then you might need to create a separate Run As account and specify it in the BlackBerry 5.0.x Database Run As Profile. In order to do this, please follow the chapters: Creating a Run As account for the BlackBerry 5.0.x Database Run As Profile and Linking the Run As account to the BlackBerry 5.0.x Database Run As Profile by Class.

Scenario 3: Multiple BlackBerry servers which share a database on a separate server

If your default Action Account runs under a low permissions Windows Domain account then you might need to create a separate Run As account and specify it in the BlackBerry 5.0.x Database Run As Profile. In order to do this, please follow the chapters: Creating a Run As account for the BlackBerry 5.0.x Database Run As Profile and Linking the Run As account to the BlackBerry 5.0.x Database Run As Profile by Class.

 

Creating a Run As account for the the BlackBerry 5.0.x Database Run As Profile

1. In the Administration section of the Operations Manager console Create a Windows Run As account for connecting to the BlackBerry database. The Windows Domain account used for this Run As account will need the following permissions:

a. Data Reader role on the BlackBerry (BESMgmt) database

b. Local administrator permissions on the BlackBerry Server(s)


2. Complete the steps in the Create Run As Account Wizard as shown in the screenshots:

a.) Click Next In the Introduction page of the Wizard.


b.) On the General Properties page select Windows for the Run As Account Type, and choose a logical name for the Display name of the Run As Account; for example: BlackBerry DataBase Run As Account. Optionally enter a Description for the Run As Account. Click Next.


c.) On the Credentials page enter the Windows domain account user name, password and domain. Click Next.


d.) On the Distribution Security page select the Less secure radio button if you want the account to be distributed to all servers Managed by Operations Manager. If you only want to distribute the Run As account to your BlackBerry servers select the More secure radio button. Click Create.


e.) Complete the Wizard by Clicking Close.

3. If you selected the Less secure radio button in the Create Run As Account Wizard, you can skip this step (step 3). If you selected the More secure radio button in the Create Run As Account Wizard, then you need to configure the BlackBerry servers to which you want to distribute the Run As account. You can configure the distribution by following these steps:


a.) In the Administration section of the Operations Manager console, select the Run As profile you just created (BlackBerry DataBase Run As Account in the example) and open its properties.


b.) On the Run As Account Properties page select the Distribution tab and click Add.


c.) On the Computer Search dialog box enter the name of the computer to which you wish to distribute the Run As account to. Click Search and select the appropriate computer(s) in the Available items list, then click Add. Repeat this steps for all computers to which you wish to distribute the Run As account. Click OK.


d.) Review the computers you added and click OK.

Linking the Run As account to the BlackBerry 5.0.x Database Run As Profile by Class

1. After creating the Run As Account you need to link it to the BlackBerry 5.0.x Database Run As Profile. In order to link the Run As account to the Run As profile, browse to the Administration view in the Operations Manager console.

2. If you use a single Run As account to connect to your BlackBerry database(s) please follow the steps below. If you have multiple BlackBerry databases in your environment and use different credentials to connect to these databases, please skip to step 6.

 


 

a.) In the Administration section select Profiles and open the properties of the BlackBerry 5.0.x Database Run As Profile.


b.) Click Next on the Introduction page of the Run As Profile Wizard.


c.) Click Next on the General Properties page.


d.) On the Add Run As accounts page click Add.

If you are using the BlackBerry Management Pack version 5.0.3.25 or higher please skip to i.) and follow the steps from there.


e.) On the Add a Run As Account dialog box select the Run As account you created in the previous steps. Select the A selected class, group, or object radio button, click Select and click Class from the dropdown menu.

 


f.) On the Class Search dialog type blackberry in the Filtered by: (optional) field and click Search. In the Available items list select BlackBerry 5.0.x servers and click OK. Click OK again to close the Add a Run As Account dialog.

 


g.) Repeat steps b.) through f.) for the following classed (as shown in the screenshot):

i.: BlackBerry Enterprise Server Resource

ii.: Database Connection

iii.: Handheld Devices

h.) Click Save and Close to complete the Run As Profile Wizard.

i.) Setting up the BlackBerry 5.0.x Database Run As Profile for BlackBerry Management Pack version 5.0.3.25 and higher

 

  • Navigate to the Administration section of the Operations Console
  • Select the Administration -> Run As Configuration -> Profiles Node
  • Select the Properties of the BlackBerry 5.0.x Database Run As Profile

     


     

  • Click Next on the Introduction Page
  • Click Next on the General Properties page
  • On the Add Run As accounts page click the Add button

     


     

  • In the Add Run As accounts dialog select the Run As database account you created for the BlackBerry management pack in the Run As account drop down box
  • Under This Run As Account will be used to manage the following objects select the radio button A selected class, group, or object
  • Click the Select button and click Group…

     


     

  • In the Group Search dialog type BlackBerry in the Filtered by field and click Search
  • Select the BlackBerry 5.0.x Run As Instances group and click OK.


    Click OK and then Save to complete the configuration.

    After you have completed the above steps, restart or refresh the Operations Console.