AppManager for BlackBerry Enterprise Server (BES) lets you monitor many aspects of your Research in Motion BlackBerry solution, including log files and services, automatically on a scheduled basis. You can use this module to monitor the operation and performance of the BlackBerry Enterprise Server through the same console you use to monitor your Windows or UNIX environment.
This release improves usability and resolves previous issues. Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure our products meet all your needs. You can post feedback in the AppManager forum on NetIQ Communities, our online community that also includes product information, blogs, and links to helpful resources.
This document outlines why you should install this module, lists installation requirements, and identifies known issues. For more information about installing the module, see the AppManager for BlackBerry Enterprise Server Management Guide, included in the download package.
The documentation for this product is available on the NetIQ Web site in HTML and PDF formats on a page that does not require you to log in. If you have suggestions for documentation improvements, click comment on this topic at the bottom of any page in the HTML version of the documentation posted at the NetIQ Documentation page. To download this product, see the AppManager Module Upgrades & Trials Web site.
This release of AppManager for BlackBerry Enterprise Server provides the following enhancements:
Support for BES 10.0 or later. This release provides support for BlackBerry Enterprise Server version 10.0 and later versions. For more information, see System Requirements.
Support for Microsoft Exchange 2013. This release now supports Microsoft Exchange Server 2013 as the Mail Server. For more information, see the System Requirements.
Support for Windows Server 2012. This release now supports computers running Microsoft Windows Server 2012. For more information, see the System Requirements.
This release of AppManager for BlackBerry Enterprise Server also resolves the following issue:
BES_SRPTest Knowledge Script does not ping the associated SRP host but the default Blackberry router address. This release resolves an issue in which the SRP ping test to the Blackberry Server SRP connection was performed on the SRP URL address. With this release, the SRP ping test is performed on the SRP host correctly. (ENG333714)
This release of AppManager for BlackBerry Enterprise Server replaces all Previous Releases.
For the most recently updated list of supported application versions, see the AppManager Supported Products page. Unless noted otherwise, this module supports all updates, hotfixes, and service packs for the releases listed below.
AppManager for BlackBerry Enterprise Server has the following system requirements:
AppManager version 7.0 or later installed on the AppManager repository (QDB) computer, on the BES servers you want to monitor (agents), and on all console computers
NOTE:Support for Windows Server 2008 requires AppManager Windows Agent hotfix 71704 or later. For more information, see the AppManager Suite Hotfixes page.
One of the following Microsoft operating systems installed on the agent computers:
Windows Server 2012
Windows Server 2008 R2
Windows Server 2008 (32-bit or 64-bit)
One of the following versions of BlackBerry Enterprise Server installed on the agent computers:
Version 10.0 or later
Version 5.0 MR1 or later
Version 4.1 with SP6
One of the following Mail Servers:
Microsoft Exchange Server 2013
Microsoft Exchange Server 2010
Microsoft Exchange Server 2007
Microsoft Exchange Server 2003
AppManager for Microsoft Windows module installed on the AppManager repository (QDB) computer, on the BES computers you want to monitor (agents), and on all console computers
NOTE:Support for Windows Server 2008 R2 requires the AppManager for Windows module, version 7.6.170.0 or later. For more information, see the AppManager Module Upgrades & Trials Web site.
For more information on hardware requirements and supported operating systems and browsers, see the BlackBerry Enterprise Server Management Guide, included in the download package.
AppManager for BES includes a managed object, BBES.dll, and Knowledge Scripts to discover and monitor BES resources. The download package includes this Release Notes, a management guide, Help for Knowledge Scripts, and several files that are used during installation:
AM70-BES-7.5.54.0.msi, the module installer.
AM70-BES-7.5.54.0.ini, a configuration file used with the AppManager setup program.
AM70-BES-7.5.54.0.xml, a configuration file used for deploying the module with Control Center. This is the file you check into the Control Center Web Depot.
AM70-BES-7.5.54.0-RepositoryFiles.exe, a compressed file that contains the QDB and console files. You do not need to run this file during installation.
ckBES.exe, the pre-installation check used with the AppManager setup program.
DefaultRule_BES.xml, a configuration file used for deploying the module with Control Center.
When you download the module, these files are copied by default to the local folder on the download computer. Consider copying these files to the \windows_installation\setup\Setup Files folder on the same distribution computer on which you saved your main AppManager software and documentation. By doing so, you maintain all AppManager software in one location that is easily accessible when you want to add more repositories, management servers, or agents.
Run the module installer to install the module components in the following locations:
On the BES servers you want to monitor (agents) to install the agent components
On all console computers to install the Help and console extensions
Run the module installer only once on each of these computers. You must also install the Knowledge Scripts and, where relevant, the Analysis Center reports. You can install these components into local or remote QDBs.
When installing to each QDB, select the option to install Knowledge Scripts, and then specify the SQL Server name of the server hosting the QDB, as well as the case-sensitive QDB name.
If Analysis Center reports are available for this module, select the option to install Analysis Center reports, and then specify the SQL Server name of the server hosting the Analysis Center Configuration Database.
IMPORTANT:This release provides SQL stored procedures. To ensure module functionality, run the module installer for each QDB attached to Control Center.
Install Knowledge Scripts and Analysis Center reports only once per QDB. The module installer now installs Knowledge Scripts for each module directly into the QDB instead of to the \AppManager\qdb\kp folder as in previous releases.
For more information about installing this module, see the AppManager for BlackBerry Enterprise Server Management Guide, included in the download package.
NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently being researched. If you need further assistance with any issue, please contact Technical Support.
No support for some Knowledge Scripts. Due to architectural changes in BES 10, User Statistics metrics and some SNMP OIDs are not supported in BES 10. Therefore, the following Knowledge Scripts are not supported in BES 10 and later versions:
BES_InactiveUsers
BES_MessageSize
BES_ResponseTime
BES_ServerActivity
BES_UserActivity
BES_UsersWithPendingMessages
BES_BlackBerryAgent Knowledge Script is not supported in BES 10. BlackBerry Agent Service is not supported in BES 10 and therefore, you cannot run BES_BlackBerryAgent script on BES 10 computers.
BES_SRPTest script fails if the BBSRPTest utility does not exist in specified location. In BES 10, the BBSPTRPTest utility is not copied to the BlackBerry default path (BasePath), by default. You should manually copy this utility to the BasePath.
If it is installed in some other location, and while running this script, if the Path and filename for BBSRPTest utility parameter is left blank, an internal failure occurs. The BasePath is similar to the following location:
For BES 5 and earlier versions: C:\Program Files (x86)\Research In Motion\BlackBerry Enterprise server\
For BES 10 and later: C: \Program Files (x86)\Research In Motion\BlackBerry Enterprise Service 10\
BES_OrphanedUsers script fails if MAPI profile is not set up. BES_OrphanedUsers Knowledge Script requires that the Exchange server be associated with a MAPI profile in order to log on and to retrieve information from user mailboxes. To create a MAPI profile, you can run the prof.exe utility from the \AppManager\bin\BES directory. For more information, see AppManager for BlackBerry Enterprise Server Management Guide.
This release of BlackBerry Enterprise Server includes enhancements added in previous releases.
This release of provided the following enhancement:
Support for mirrored databases. This release now supports failover from the primary to the secondary database when Microsoft Exchange Server is running in a mirrored database environment. If you use mirrored databases, you must register the credentials of the secondary database in AppManager Security Manager. If you want to use SQL Authentication, then also provide the login information in the Mirror Database Login parameter of the following Knowledge Scripts: (ENG304912)
BES_InactiveUsers
BES_MDSConnections
BES_MDSFailures
BES_OrphanedUsers
BES_ServerActivity
BES_UserActivity
BES_UsersWithPendingMessages
This release also resolved the following issues:
BES_SRPTest Knowledge Script cannot run in environments where 8.3 file format creation is disabled. This release resolves an issue in which the BES_SRPTest Knowledge Script does not collect data on computers with NTFS that have 8.3 file format creation disabled. With this release, the script successfully gathers data. (ENG300491)
BES_ResponseTime Knowledge Script reports exponential values. This release resolves an issue in which the BES_ResponseTime Knowledge Script cannot always interpret the email timestamp from Blackberry Enterprise Server version 5.0 with SP2, and returns data with incorrect values. With this release, the Knowledge Script can correctly interpret the timestamp format. (ENG304765)
BES_UserCount Knowledge Script does not provide adequate information to determine license problems. This release resolves an issue in which the BES_UserCount Knowledge Script fails with an Internal failures error when the number of licenses used is equivalent to or exceeds the number of licenses available. With this release, the Knowledge Script provides more useful information about the cause of the problem. (ENG305705)
BES_SRPTest Knowledge Script cannot run as a service account. This release resolves an issue in which the BES_SRPTest Knowledge Script does not collect data when you run the Knowledge Script under a service account. With this release, the script successfully gathers data. (ENG307812)
This release resolved the following issue:
The BES_HungThread Knowledge Script raised an error when searching log files. This release resolves an issue in which an error prevented the HungThread script from searching the relevant logs for hung thread information. With this release, the script performs the search successfully, without raising an error. (ENG301784)
This release also included the following enhancement:
Support for Microsoft Exchange 2010. This release now supports Microsoft Exchange Server 2010 as the Mail Server. For more information, see the System Requirements.
This release provided the following enhancements:
Support for Windows Server 2008 R2. With this release, AppManager monitors Blackberry Enterprise Server installed on Microsoft Windows Server 2008 R2. For more information, see the System Requirements.
Support for Blackberry Enterprise Server 5.0 SP1 MR2 and 5.0 SP1 MR3. With this release, AppManager monitors Blackberry Enterprise Server 5.0 SP1 MR2 and 5.0 SP1 MR3 installed on the agent computer. For more information, see the System Requirements.
Support for Blackberry Enterprise Server 5.0 SP2. With this release, AppManager monitors Blackberry Enterprise Server 5.0 SP2 installed on the agent computer. For more information, see the System Requirements.
In addition, this release resolved the following issue:
Job fails with Duplicate dynamic object name error. Before installing this release of the module, some BES_SRPConnectionStatus script jobs incorrectly stop and report the error Duplicate dynamic object name for systems with multiple Blackberry servers. After installing this release of the module, jobs complete as expected. (ENG283232)
This release provided the following enhancement:
Discovery fails after upgrade from previous release of module. Before you install this release, the Discovery_BES Knowledge Script job fails when you run it after you upgraded to release 7.4.50.0 of the AppManager for BES module. After you install this release, a correction in the sequencing of an ObjectType in the module's XML file enables the Discovery_BES Knowledge Script job to complete successfully. Ensure you install this release on at least the AppManager repository (QDB) and agent computers. For more information, see Installing This Module. (ENG279486)
This release provided the following enhancements:
Support for BlackBerry Enterprise Server version 5.0 MR1. AppManager for BES now supports BlackBerry Enterprise Server version 5.0 MR1. For more information, see the System Requirements.
User-specific monitoring for hung threads. The BES_HungThreadsKnowledge Script has been revised so that you can identify user-specific hung threads.
Monitoring of BlackBerry Administration Service and BlackBerry Collaboration Service. The BES_ServiceHealth Knowledge Script alerts you when the BlackBerry Administration Service or the BlackBerry Collaboration Service has failed.
Support for High-Availability/Failover Clusters. The following Knowledge Scripts have been revised to provide support for high-availability BlackBerry Enterprise Server services. They are now "cluster-aware," meaning that jobs will continue to run without interruption of data when failover occurs. These Knowledge Scripts raise an event if the active server fails and the passive server takes over.
BES_HungThreads
BES_InactiveUsers
BES_MDSConnections
BES_MDSFailures
BES_MessageSize
BES_OrphanedUsers
BES_ServerActivity
BES_SRPConnectionStatus
BES_UserActivity
BES_UserCount
BES_UsersWithPendingMessages
In addition, the following issue was resolved:
BES_ResponseTime script stops collecting data when failover occurs. Before installing this version of the module, the BES_ResponseTime script stops collecting data when failover occurs. After installing this version of the module, a new parameter ensures data is collected when the primary BES server is down and the standby BES server takes over. (ENG239754)
This release resolved the following issue:
BES_HungThreads script raises multiple events for unsupported services. Before you install this release, the BES_HungThreads Knowledge Script job raises an event on every iteration to indicate that MDS and Collaboration services are not supported. After you install this release, the BES_HungThreads Knowledge Script job raises an event for this situation only on the first iteration. (ENG262049)
This release resolved the following issues:
ServiceHealth job fails. Before you install this release, the BES_ServiceHealth Knowledge Script job fails with the following error message: An internal failure occurred that prevented the current iteration of the job from completing. A timing error causes the script to look for data too soon. After you install this release, the timing error is resolved. (ENG255099)
SRPTest job does not collect data. Before you install this release, the BES_SRPTest Knowledge Script job does not collect data when there is no SRP connection. A data point with a value of "0" is expected. After you install this release, an increase in the default timeout for data collection allows the job to return data. (ENG260178)
This release provided the following enhancements:
Support for BES 4.1, SP6. This release provides support for BlackBerry Enterprise Server version 4.1 with Service Pack 6. For more information, see System Requirements.
Enhanced monitoring for Mobile Data Service.
The BES_ServiceHealth Knowledge Script now monitors aspects of MDS integration services: services up or down, memory usage, CPU usage.
The Discovery_BES Knowledge Script now discovers MDS integration services.
Increased character limit for DebugLogSearch Knowledge Script. With this release, the Include filter and Exclude filter parameters in the BES_DebugLogSearch Knowledge Script allow 10,000 characters. In previous releases, the parameters allowed only 128 characters.
Support for IPv6. This release adds support for Internet Protocol version 6 (IPv6). AppManager for BES recognizes and displays IPv6 addresses in the Operator Console and Control Center Console.
This release resolved the following issues:
MDSFailures and MDSConnections scripts not collecting data. Before you install this release, a miscalculated start time causes the BES_MDSFailures and BES_MDSConnections Knowledge Scripts to fail to collect data. After you install this release, a recalculated start time enables the MDSFailures and MDSConnections scripts to collect data and generate data streams. (ENG246268)
Discovery_BES jobs fail on BES version 4.1.x. Before you install this release, the BES discovery job fails on BES version numbers that contain an alphabetic character. After you install this release, discovery ignores the alphabetic character and does not fail. (ENG254869)
This release resolved the following issues:
German date/time format not handled properly. Before you install this hotfix, changes to the User Default Format cause Knowledge Scripts to raise events for invalid date/time format. After you install this hotfix, changes to the User Default Format from English to German (or German to English) will not generate an "Invalid format for date/time" message. (ENG244524)
No events raised for hung threads. Before you install this hotfix, the BES_HungThreads Knowledge Script does not raise events when it finds error codes for hung threads in the Control log. After you install this hotfix, you can modify the BESerrorcodes.xml file to include error codes that were unknown at the time the HungThreads script was developed. The HungThreads script then will raise events when the Control log contains any error code included in the XML file. For more information, see the Help for the HungThreads script. (ENG245384)
Memory usage threshold too low for ServiceHealth script. Before you install this hotfix, the BES_ServiceHealth Knowledge Script limits the memory usage threshold to 128 MB. After you install this hotfix, the ServiceHealth script will not limit the value you set for a maximum memory usage threshold. (ENG247998)
This release added support for BlackBerry Enterprise Server version 4.1 with Service Pack 4.
AppManager for BlackBerry Enterprise Server and all updates and modifications thereto (“Software”) is distributed with certain third-party software and open source software (as may be defined in the license agreement provided with the Software).
The following third-party and open source software are included with the Software and are licensed for distribution according to the terms described in this document and any use thereof must be in accordance with such terms, solely in conjunction with your internal use of the Software, and - unless explicitly contradicted below - consistent with the terms and conditions set forth in the applicable license agreement for the software. No further licenses are granted.
Net-SNMP
Part 1: CMU/UCD copyright notice: (BSD like) -----
Copyright 1989, 1991, 1992 by Carnegie Mellon University
Derivative Work - 1996, 1998-2000 Copyright 1996, 1998-2000 The Regents of the University of California
All Rights Reserved
Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of CMU and The Regents of the University of California not be used in advertising or publicity pertaining to distribution of the software without specific written permission.
CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL CMU OR THE REGENTS OF THE UNIVERSITY OF CALIFORNIA BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Part 2: Networks Associates Technology, Inc copyright notice (BSD) -----
Copyright (c) 2001-2003, Networks Associates Technology, Inc All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of the Networks Associates Technology, Inc nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Part 3: Cambridge Broadband Ltd. copyright notice (BSD) -----
Portions of this code are copyright (c) 2001-2003, Cambridge Broadband Ltd. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
The name of Cambridge Broadband Ltd. may not be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you.
For detailed contact information, see the Support Contact Information Web site.
For general corporate and product information, see the NetIQ Corporate Web site.
For interactive conversations with your peers and NetIQ experts, become an active member of our community. The NetIQ online community provides product information, useful links to helpful resources, blogs, and social media channels.
THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT ARE FURNISHED UNDER AND ARE SUBJECT TO THE TERMS OF A LICENSE AGREEMENT OR A NON-DISCLOSURE AGREEMENT. EXCEPT AS EXPRESSLY SET FORTH IN SUCH LICENSE AGREEMENT OR NON-DISCLOSURE AGREEMENT, NETIQ CORPORATION PROVIDES THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME STATES DO NOT ALLOW DISCLAIMERS OF EXPRESS OR IMPLIED WARRANTIES IN CERTAIN TRANSACTIONS; THEREFORE, THIS STATEMENT MAY NOT APPLY TO YOU.
For purposes of clarity, any module, adapter or other similar material (“Module”) is licensed under the terms and conditions of the End User License Agreement for the applicable version of the NetIQ product or software to which it relates or interoperates with, and by accessing, copying or using a Module you agree to be bound by such terms. If you do not agree to the terms of the End User License Agreement you are not authorized to use, access or copy a Module and you must destroy all copies of the Module and contact NetIQ for further instructions.
This document and the software described in this document may not be lent, sold, or given away without the prior written permission of NetIQ Corporation, except as otherwise permitted by law. Except as expressly set forth in such license agreement or non-disclosure agreement, no part of this document or the software described in this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, or otherwise, without the prior written consent of NetIQ Corporation. Some companies, names, and data in this document are used for illustration purposes and may not represent real companies, individuals, or data.
This document could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes may be incorporated in new editions of this document. NetIQ Corporation may make improvements in or changes to the software described in this document at any time.
U.S. Government Restricted Rights: If the software and documentation are being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), in accordance with 48 C.F.R. 227.7202-4 (for Department of Defense (DOD) acquisitions) and 48 C.F.R. 2.101 and 12.212 (for non-DOD acquisitions), the government's rights in the software and documentation, including its rights to use, modify, reproduce, release, perform, display or disclose the software or documentation, will be subject in all respects to the commercial license rights and restrictions provided in the license agreement.
© 2014 NetIQ Corporation and its affiliates. All Rights Reserved.
For information about NetIQ trademarks, see http://www.netiq.com/company/legal/.