Systems no longer shown on MTC-A webpage after CA OPS/MVS maintenance.

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

After applying the following CA OPS/MVS maintenance (CARS2011 2012 2101 2102 2103), existing MTC A instance could stop showing the systems 

OPSMTCA sysout will show error messages like below. 

2021-05-08 13:39:31.209 .https-jsse-nio-8443-exec-4. ERROR c.c.m.s.RulesService - RulesService.getFilterSystems: Unable to find discovered system (SYSTEM_A) in ESM topology map.        
2021-05-08 13:39:31.209 .https-jsse-nio-8443-exec-4. ERROR c.c.m.s.RulesService - RulesService.getFilterSystems: Unable to find discovered system (SYSTEM_B) in ESM topology map.                      
2021-05-08 13:39:31.209 .https-jsse-nio-8443-exec-4. ERROR c.c.m.s.RulesService - RulesService.getFilterSystems: Unable to find discovered system (SYSTEM_C) in ESM topology map.

After the backout of the deploy using ZFS without the maintenance, MTC-A works properly again.

Environment

Release: 14.0
Component: MAINFRAME TEAM CENTER AUTOMATION

Cause

Missing TOPOLOGY configuration in ESMENV member. These requirements were added by the Federated Security feature (SO15067 and SO15068). 

Resolution

Add the missing TOPOLOGY definitions to the ESMENV member. See detailed information on how to define the Topology configuration in the link below:

ESM Microservice Topology Configuration Reference