You want to install and configure cmWatcher. Therefore you want to have the latest User Manual available.
This note contains the latest User Manual. Please use the following link to download ist:
Your monitoring concept requests a high available monitoring solution for Microsoft System Center Operation Manager (SCOM) and SAP components. Therefore also connmove cmWatcher shoud be high avilable.
connmove cmWatcher supports a configuration in a Microsoft Failover Cluster environment. With this configuration, cmWatcher is protected against single Hardware outages and single Operating systems outages.
This article describes how to install and configure cmWatcher in a Microsoft Failover Cluster. It describes how to configure a generic service within the microsoft failover cluster role.
cmWatcher Failover Cluster configuration is supported in a two node configuration. Alike other cluster configuration, cmWatcher with its specific functionality has special demands on the cluster configuration:
The cluster Service does not need a specific IP adress, because cmWatcher connects to the systems and database. No connections goes to the cmWatcher installation directly
Cluster shared Storage
cmWatcher is normaly installed in c:\program files. Of couse you can install it directly on a cluster shared disk. But while cmWatcher stores configuration and status items in the database, there is not really a need to do so. It’s suitable to install cmWatcher on both Cluster nodes on local disks.
Disadvantage off this local configuration: Patches of cmWatcher must be done on both nodes.
cmWatcher runs in a Microsoft Failover Cluster. connmove recomment the cluster configuration itself along to current Microsoft Failover Cluster configuration guidelines. connmove support this kind of configuration in Microsoft Failover Cluster with Windows Server version 2008 R2 and above, x64 bit only.
Installation of cmWatcher:
Install cmWatcher (for additional information, see the cmWatcher manual) on the respective nodes of the cluster. Note: The cmWorker service has to be stopped. After the installation of the cmWatcher instances the database connection of one cmWatcher instance has to be configured. Then change to the directory of the cmWatcher „C:\Program Files\Connmove GmbH\cmWatcher“ and copy the „cmWatcherSettings“ file to the other nodes.
Creating cluster service:
Open the Failover Cluster Manager and click on „Create Empty Role“.
The new role will appear in the Roles list. Double clicking the role opens the properties window. Specify the name for the role and select the cluster nodes on which you have installed cmWatcher. Apply changes and close the window.
Right click on the role and select „Add Resource/Generic Service“.
The „New Resource Wizard“ window opens. Choose the cmWorker service from the list and click next until the wizard finishes.
Right click on the role entry and choose „Start Role“.
The cmWorker service will now start on one of the specified cluster nodes.
You now succesfully completed the cmWatcher cluster installation.
If your SAP Solution Manager does not runs on a Windows server, the configuration for cmWatcher is a little bit other as described in the cmWatcher manual.
Because it is not possible to pass the alerts directly from the SAP system to the cmWatcherMAI2SCOM tool, the alerts must be stored in a shared folder which is accessible from the SAP Solution Manager server and the server where the cmWatcher is installed. Then, the SAP system can save the alerts in the folder and the cmWatcher can take them from there.
Create a new shared folder and mount it to your SAP Solution Manager server.
In our example, we call the folder cmWatcherShare. The folder contains a subfolder called alerts and a file maiscript.sh with the following content:
echo $@ >> /cmWatcherShare/alerts/$filename
The script has the following function: It takes two parameters. The first is the file name and the second is the content of the file. The script creates in the folder alerts a file with the given file name and the content.
If you have not yet configured the connection to the database for the cmWatcher open its programs folder and execute cmWatcherMAI2SCOM.exe.
The form for providing the database settings will appear. Fill out the form and click Connect.
Log on to Solution Manager using SAPGui, open transaction SM49 (External Operating System Commands) and create a new entry. Set the command name and the path to the maiscript.sh. Option Additional Parameters Allowed must be checked.
Configure your SAP system as described in guide HOW-TO GUIDE OS Command Adapter.pdf. In section 3.1.1 of this guide set the external command which we have just created.
Section 3.1.2 (OS Command Parameters) describes how to configure the parameters for:
Download the file CmWatcherMAIConfig_NonWin.xml from this post, open it and scroll down to the bottom. You will find an entry similar to:
Replace SID with the system ID of your SAP system and save the changes.
Now return to the browser as described in section 3.1.2 and select configuration option:
Under Configuration details click View as XML to open the upload dialog. Click Browse, select the CmWatcherMAIConfig_1.xml file and click Perform upload. Repeat these steps for configuration option:
Configuration of cmWatcher
Open the cmWatcher GUI, go to tab SAP, select the respective entry and choose Modify Entry to open the SAP System Settings dialog. Go to tab SAP MAI and select option Enable MAI.
Save the changes.
Create a scheduled Task for CmWatcherMAI2SCOM.exe:
Once we the Solution Manager creates the alert-files in the shared folder, we have to configure the CmWatcherMAI2SCOM tool to collect and store them into the database. For that we create a scheduled Task which executes our tool each x minutes.
Steps to create the scheduled task:
The configuration is now complete.
connmove released a new Version of cmWatcher which supports the SAP Solution Manager Monitor and Alering Infrastructure (MAI) for SCOM.
You already use cmWatcher and want do update to this new version. If your current version is higher than 3.11. this note explain the upgrade path.
If you use cmWatcher Version < 3.11, please follow section „Steps if you have an older version“ in this note.
Steps for updating cmWatcher:
For further informations on how to configure cmWatcher see the manual (you can find it in the cmWatcherSetup.zip file).
Steps if you have an older version:
connmove improves cmWatcher with every new release. This note explains which Version is the latest one and also shows changes and new features.
The latest version is always available at http://connmove.eu/software/downloads/. With the download you also get the latest cmWatcher Manual and Management Packs.
-MAI interface supported.
-Management Pack and cmWatcher database updated.
Please read this Note for Update hints.
-Fixed GUI bug: Changing the order of the SCOM connectors didn’t worked.
– creating discovery objects with empty names. Alerts and performance nodes will be skipped if the relevant fields are empty.
– stopping cmWorker service itself if an error occurs during the verification of the database version.
– if alerts can not be loaded from SAP system, cmWatcher closes the alerts from SCOM and transfers them another time again.
-ManagementPack / cmWatcher GUI redesigned
cmWatcher 126.96.36.199 ***************** -Position of used Alert-Customfields can be changed. -Alert-Description can be customized. -ManagementPack updated.
cmWatcher 188.8.131.52 ***************** cmWatcher GUI: – PerformanceView: Fix a bug while loading selected monitors which have the same name on the same tree level. – PerformanceView: For a better differentiation the System name was added on monitor nodes. – Forms can be confirmed by pressing ‚Enter‘. – New Connector form added. Connector can be selcted/deleted from a list.
cmWatcher 184.108.40.206 ***************** cmWatcher GUI: – New function ‚Delete Alert Cache‘ – New function ‚Map System to SCOM‘ only creates the Instance. To create the Healthexplorer, you have to call ‚Install / Update ManagementPack‘
To get the alerts from the SAP system we call the following BAPIs:
The result of the error is an empty alert list.
Because no alerts were loaded, the cmWorker service falsely assumes that the alerts were closed from the SAP system. The service closes the alerts then also from SCOM.
When the next loading of alerts is successful, the alerts will be again transferred to SCOM.
Hotfix is avaialble for customer. Please contact connmove Support.
cmWatcher 3.0 is now available. You can download it from our download section: http://connmove.eu/software/downloads/
Management Pack classes:
HealtExplorer of a Windows.Computer object:
DashboardView (not included in cmWatcher ManagementPack):
As cmWatcher uses SAP CCMS Interfaces to get data of SAP systems for SCOM, you must use also CCMS for monitoring of J2EE Engines. The best way to connect J2EE Enginges to SAP CCMS are CCMS Agents. SAP Help provide some good artices around this theme.
Monitoring Status of J2EE with CCMS
Overview on CCMS Agents
CCMS Agent for J2EE
Upcoming version of cmWatcher will also support the latest MAI Interface ofSAP Solution Manager.
cmWatcher 2.8.3 is now available on http://www.connmove.com/index.php/en/downloads
Important notice: If you have already an older cmWatcher version installed, read the readme file for installation instructions.
– PerformanceView: Fix a bug while loading selected monitors which have the same name on the same tree level.
– PerformanceView: For a better differentiation the System name was added on monitor nodes.
– Forms can be confirmed by pressing ‚Enter‘.
– New Connector form added. Connector can be selcted/deleted from a list.
– function ‚Delete Alert Cache‘
– function ‚Map System to SCOM‘ only creates the Instance. To create the Healthexplorer, you have to call ‚Install / Update ManagementPack‘
ManagementPack has been updated
SAP delivers a new downward compatible Kernel (720) to customer. With this Kernel a few changes in CCMS at least for Dual Stack systems are coming up. They are explained in SAP note 1667336.
With SAP Kernel 720 SAP CCMS agent are no longer used. Every system connects to SAPSTARTSRV (local service) and this service delivers any monitor functionality. Please follow the note and deregister the SAP CCMS agents so CCMS can connect to each system using SAPSTARTSRV.
For cmWatcher this change in SAP Kernel has no effect.