MOM will not load copied Management Module

book

Article ID: 192616

calendar_today

Updated On:

Products

CA Application Performance Management Agent (APM / Wily / Introscope) CA Application Performance Management (APM / Wily / Introscope) INTROSCOPE DX Application Performance Management

Issue/Introduction

An attempt to load a Management Module which contains a Downtime Schedule and which has been copied from a domain of a different name in another MoM and where that domain does not exist in target MoM fails. The MoM log file contains the following message:

6/08/20 12:57:24.044 PM BST [ERROR] [main] [Manager.ManagementModule] Unable to load the AlertDowntimeSchedule named "New Alert Downtime Schedule - Backups" in Management Module "MM1" - 'The command could not be completed because "SuperDomain/DOMAIN1" does not exist.'. 
6/08/20 12:57:24.063 PM BST [WARN] [main] [Manager.Bootstrap] Error in linking Management Module MM1
com.wily.introscope.spec.server.XMLException: 1 error(s) were encountered loading the management modules.

Cause

The AlertDowntimeSchedule element in the ManagementModule.xml file contains a reference to the domain in which it was created. This is not selectable or modifiable in the Management Module Editor

 

<DomainName>SuperDomain/DOMAIN1</DomainName>
                    </Alerts>
                </DowntimePolicy>
                <Schedule>
                    <Type>WEEKLY</Type>
                    <Duration>120</Duration>
                    <Seconds>0</Seconds>
                    <Minutes>0</Minutes>
                    <Hours>3</Hours>
                    <DayOfMonth>?</DayOfMonth>
                    <Month>*</Month>
                    <DayOfWeek>SUN,MON,TUE,WED,THU,FRI,SAT</DayOfWeek>
                </Schedule>
            </AlertDowntimeSchedules>
        </DataGroup>

Environment

Application Performance Management 10.7

Resolution

This is a restriction - when copying management modules with Alert Downtime Schedules the Management Module domain must exist in the target environment. There are no plans to modify this behaviour.

A workaround is to remove Alert Downtime Schedules form the Management Module before copying.