All posts in cmWatcher @en

cmWatcher User Manual

Kategorien: Allgemein @en, cmWatcher @en, knowledge base @en
Comments Off on cmWatcher User Manual

Intro

You want to install and configure cmWatcher. Therefore you want to have the latest User Manual available.

Solution

This note contains the latest User Manual. Please use the following link to download ist:

“connmove_cmWatcher_UserManual_EN”.


How to install cmWatcher in a cluster

Kategorien: Allgemein @en, cmWatcher @en, knowledge base @en
Comments Off on How to install cmWatcher in a cluster

Intro

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.

Solution

Architecture:

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:

IP Adresss:
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.

Prequesites:

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 FilesConnmove GmbHcmWatcher” and copy the “cmWatcherSettings” file to the other nodes.

Creating cluster service:

Open the Failover Cluster Manager and click on “Create Empty Role”.

FailoverClusterManager

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.

FailoverClusterManager_RoleProperties

Right click on the role and select “Add Resource/Generic Service”.

FailoverClusterManager_RoleAddRessource

 

The “New Resource Wizard” window opens. Choose the cmWorker service from the list and click next until the wizard finishes.

FailoverClusterManager_RoleSelectService

FailoverClusterManager_RolePropertiesConfirmation

FailoverClusterManager_RolePropertiesSummary

Right click on the role entry and choose “Start Role”.

FailoverClusterManager_StartRole

The cmWorker service will now start on one of the specified cluster nodes.

FailoverClusterManager_RunningRole

You now succesfully completed the cmWatcher cluster installation.

 


Configuration MAI on non Windows servers

Kategorien: cmWatcher @en, knowledge base @en
Comments Off on Configuration MAI on non Windows servers

Intro

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.

Solution

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:

#!/usr/bin/sh
 filename=$1
 shift
 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.

MAI_NonWin_CreateExternalCommand

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:

Configuration ID Extra key combination
MAI_OS_CMD_CONFIG CONFIG_TYPE = PARAMETERS ; FILTER_VALUE = OS_CMD_REACT
MAI_OS_CMD_CONFIG CONFIG_TYPE = PARAMETERS ; FILTER_VALUE = OS_CMD_REACT_CLOSE

Download the file CmWatcherMAIConfig_NonWin.xml from this post, open it and scroll down to the bottom. You will find an entry similar to:

<AGS_SISE_GS_S_KEY_VALUE>
  <NAME>01;$$</NAME>
     <VALUE>[MAI:ALERT:ID][MAI:ALERT:DATE][MAI:ALERT:TIME][MAI:ALERT:REASON_FOR_CLOSURE].txt
     [MAI:ALERT:MO_NAME]|[MAI:ALERT:MO_TYPE]|[MAI:ALERT:ID]|[MAI:ALERT:DATE]|[MAI:ALERT:TIME]|
     [MAI:ALERT:NAME]|[MAI:ALERT:TECHNICAL_NAME]|[MAI:ALERT:DESCRIPTION]|[MAI:ALERT:CATEGORY]|
     [MAI:ALERT:RATING]|[MAI:ALERT:SEVERITY]|[MAI:ALERT:STATUS]|[MAI:ALERT:REASON_FOR_CLOSURE]|SID</VALUE>
  <IS_SECURE />
</AGS_SISE_GS_S_KEY_VALUE>

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:

Configuration ID Extra key combination
MAI_OS_CMD_CONFIG CONFIG_TYPE = PARAMETERS ; FILTER_VALUE = OS_CMD_REACT

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 ID Extra key combination
MAI_OS_CMD_CONFIG CONFIG_TYPE = PARAMETERS ; FILTER_VALUE = OS_CMD_REACT_CLOSE

MAI_NonWin_OSCommandConfiguration

 

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.

MAI_NonWin_SAPSystemSettings

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:

  • Open the Windows Task Scheduler and create a new task.
  • Enter a name for the task. If you selected Windows Authentication for the cmWatcher database connection, the user account with which the task will be executed must have privileges for the database.
    MAI_NonWin_TaskScheduler
  • Change to tab Triggers and create a new one. Set the options similarly tot he picture:
    MAI_NonWin_TSNewTrigger
  • Change tot ab Actions and click on New. Set the Action field to Start a program. For Program/script browse the cmWatcher program directory and choose cmWatcherMAI2SCOM.exe. In the field Add arguments set PATH <Path to alerts folder>. For Example: PATH \cmWatcherSharealerts
    MAI_NonWin_TSNewAction

 

The configuration is now complete.


Note: Update cmWatcher to Version 3.14

Kategorien: cmWatcher @en, knowledge base @en
Comments Off on Note: Update cmWatcher to Version 3.14

Intro

connmove released a new Version of cmWatcher which supports the SAP Solution Manager Monitor and Alering Infrastructure (MAI) for SCOM.

Problem

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.

Solution

Steps for updating cmWatcher:

  • Uninstall cmWatcher.
  • Download the latest version of cmWatcher from http://connmove.eu/software/downloads/.
  • Unzip the downloaded file and install cmWatcher.
  • Update cmWatcher database:
    • Open the file CmWatcherDBUpdate.sql which is contained in the program directory of cmWatcher.
    • You will find the line USE [cmWatcher]. If you have named your database other than cmWatcher, edit the line.
    • Execute the script.
  • Open the cmWatcher GUI, go to the tab SCOM, select the respective entry and choose Install Management Pack.

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:

  • Uninstall cmWatcher.
  • Remove cmWatcher Management Pack from SCOM.
  • Delete database of cmWatcher.
  • Download the latest version of cmWatcher from http://connmove.eu/software/downloads/.
  • Unzip the downloaded file and install cmWatcher.
  • Install/Configure cmWatcher as described in the manual (you can find it in the cmWatcherSetup.zip file).

Note: cmWatcher Changelog

Kategorien: cmWatcher @en
Comments Off on Note: cmWatcher Changelog

Intro

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.

Solution

cmWatcher 3.14.0.0 (GA 21. October 2013)

-MAI interface supported.
-Management Pack and cmWatcher database updated.

Please read this Note for Update hints.

cmWatcher 3.13.0.0

-Fixed GUI bug: Changing the order of the SCOM connectors didn’t worked.

cmWatcher 3.12.0.0

-Fixed bugs:
– 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.

cmWatcher 3.0.0.0

-ManagementPack / cmWatcher GUI redesigned

cmWatcher < 3.0

cmWatcher 2.8.4.0 ***************** -Position of used Alert-Customfields can be changed. -Alert-Description can be customized. -ManagementPack updated.

cmWatcher 2.8.3.0 ***************** 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 2.8.1.0 ***************** 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’

ManagementPack updated


cmWatcher 3.0 is now available

Kategorien: cmWatcher @en, knowledge base @en
Comments Off on cmWatcher 3.0 is now available

cmWatcher 3.0 is now available. You can download it from our download section: http://connmove.eu/software/downloads/

cmWatcher_GUI

Changes:

  • cmWatcher GUI redesigned
  • LogonTest: cmWatcher creates for each SAPConnector a performance counter named ‚LogonTest‘. This counter shows the connection time to the sap system.
  • ManagementPack:
    • redesigned class model
    • cmWatcher creates a relationship between the connmove.cmWatcher.Instance class and the System.Computer class. Thereby the health status of the instance is forwarded to the computer object.
    • Views:
      • Status view for each class
      • Alert view
      • Event view
      • Performance view
      • Diagram view

Management Pack classes:

MP_Classes

 

Screenshots:

DiagramView:

Diagramm

 

HealtExplorer of a Windows.Computer object:

wincomputers_HealthExplrer

DashboardView (not included in cmWatcher ManagementPack):

dashboard

 

 

 

 

 

 

 


cmWatcher 2.8.3 is now available

Kategorien: cmWatcher @en, knowledge base @en
Comments Off on cmWatcher 2.8.3 is now available

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.

 

Changes:

 

cmWatcher 2.8.3.0
*****************

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 2.8.1.0
*****************

cmWatcher GUI:
– function ‘Delete Alert Cache’
– function ‘Map System to SCOM’ only creates the Instance. To create the Healthexplorer, you have to call ‘Install / Update ManagementPack’

Management Pack:

ManagementPack has been updated


cmWatcher and latest SAP Kernel (720)

Kategorien: cmWatcher @en, knowledge base @en
Comments Off on cmWatcher and latest SAP Kernel (720)

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.


cmWatcher librfc32 download

Kategorien: cmWatcher @en, knowledge base @en
Comments Off on cmWatcher librfc32 download

If you still need the librfc32.dll file, you can download it also from:

 

http://my.theobald-software.com/index.php?/Knowledgebase/Article/View/71/0/theobald–products-in-a-64-bit-environment

 


CCMS Monitor Template

Kategorien: cmWatcher @en, knowledge base @en
Comments Off on CCMS Monitor Template

You want to use cmWatcher and CCMS – but don’t have CCMS configured? Then use our CCMS Starter Template. This templates monitors most import system components.

 

Part of the content:

MTE Description
ABAP Shortdumps Errors during the execution of ABAP programs are displayed here in the status attribute Shortdumps. The system has created a dump and reported this to the monitoring architecture. Transaction ST22 (ABAP Runtime Errors) is set as the analysis method.
Aborted Batch Jobs Individual aborted jobs on an application server; a separate red alert is generated for each of these jobs
Update Errors Error in Updates
Update Service Status of Updates Services

 

This template monitors all known SAP systems in your environment by dynamic Monitor definitions.

Installing the template:

1. Download template: connmove_example_Monitor_Set

2. Create new Monitor / Monitor set

3. Enter the new Monitor in Maintenance Mode

4. Import Monitor Template

Further Information:

SAP Help Portal – Transport CCMS Monitors