TIM is not working and is unable to synch all the monitors.

book

Article ID: 8411

calendar_today

Updated On:

Products

APP PERF MANAGEMENT CA Application Performance Management Agent (APM / Wily / Introscope) CUSTOMER EXPERIENCE MANAGER INTROSCOPE

Issue/Introduction

  Customer is not able to synchronize the monitors in their APM CE (CEM)/TIM installation.  In the logs are these messages:

hub: ConfigFile: reading configuration file /opt/CA/APM/tim/config/domainconfig.xml 

**ERROR: hub: ConfigFile: data error in /opt/CA/APM/tim/config/domainconfig.xml: invalid value "1" for attribute "name_type" in <ParameterDef> 

**ERROR: hub: ConfigFile: Data error: invalid value "1" for attribute "name_type" in <ParameterDef> 

hub: WebServer: cmd=POST url=/tess/setdomainconfig status=500 message=Error 

 

Cause

 The customer had made changes to a Business Transaction and had set name_type=3 and OP =1.  These parameters should not mix/match regular expressions and wildcard matching values. They should have the same values for regular expressions/wildcard matching. Here are the possible values for these two fields:

name_type attribute: Optional, default is 0 (literal value); possible values:

  0: name attribute is a literal value

  1: name attribute may contain a single "*" character, which matches any

     substring.

  3: name attribute is a regular expression

OP Attribute

1: (MATCH_SIMPLE_PATTERN) The value attribute represents a

      pattern which must match the observed data.  The pattern may

      contain a single "*" character, which matches any substring.

  2: (DOES_NOT_EXIST) The observed data must not contain a

     parameter named by the name attribute.  In this case the value

     attribute must not be supplied.

  3: (MATCH_REGULAR_EXPRESSION) The value attribute represents a

      Perl-compatible regular expression which must match the observed data.

 

      See http://www.pcre.org/ for details of the regular expression syntax.

 

 

 

Environment

Found in TIM and APM running 10.5. But this may occur in any supported APM release.

Resolution

  In this case, the customer backed out the changes in the Business Transaction. This corrected the problem.