search cancel

AAI Control-M connector log shows: ERROR [ConfigManager] Can not configure scheduler [Data center xxxx not found in Control-M]

book

Article ID: 252587

calendar_today

Updated On:

Products

Automic Automation Intelligence

Issue/Introduction

After installing the Control-M connector, and adding the Control-M Scheduler to the AAI Web UI, the connector logs are showing errors like below stating the Data Center is  not found.

 

ERROR [ConfigManager] Can not configure scheduler [Data center xxxxx not found in Control-M] (will report to AAI server; schedulerId=AYPSVctZd-Q=, transactionId=(none), errorType=GENERAL).
java.lang.IllegalArgumentException: Data center xxxxx not found in Control-M
 at com.broadcom.aai.connector.controlm.service.scheduler.ControlMScheduler.lambda$readDataCenterRecord$0(ControlMScheduler.java:386) ~[classes!/:?]
 at java.util.Optional.orElseThrow(Optional.java:290) ~[?:1.8.0_342]
 at com.broadcom.aai.connector.controlm.service.scheduler.ControlMScheduler.readDataCenterRecord(ControlMScheduler.java:383) ~[classes!/:?]
 at com.broadcom.aai.connector.controlm.service.scheduler.ControlMScheduler.startup(ControlMScheduler.java:345) ~[classes!/:?]
 at com.broadcom.aai.connector.framework.service.config.ConfigManager.configureScheduler(ConfigManager.java:180) ~[connector.framework-6.4.2.jar!/:?]
 at com.broadcom.aai.connector.framework.service.config.ConfigManager.updateScheduler(ConfigManager.java:475) ~[connector.framework-6.4.2.jar!/:?]
 at com.broadcom.aai.connector.framework.service.config.ConfigManager.lambda$updateSchedulers$4(ConfigManager.java:417) ~[connector.framework-6.4.2.jar!/:?]
 at java.util.ArrayList.forEach(ArrayList.java:1259) ~[?:1.8.0_342]
 at com.broadcom.aai.connector.framework.service.config.ConfigManager.updateSchedulers(ConfigManager.java:408) ~[connector.framework-6.4.2.jar!/:?]
 at com.broadcom.aai.connector.framework.service.config.ConfigManager.checkConfigs(ConfigManager.java:380) ~[connector.framework-6.4.2.jar!/:?]
 at com.broadcom.aai.connector.framework.service.config.ConfigManager.verifyAndStartup(ConfigManager.java:346) ~[connector.framework-6.4.2.jar!/:?]
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_342]
 at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_342]
 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_342]
 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_342]
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_342]
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_342]
 at java.lang.Thread.run(Thread.java:750) [?:1.8.0_342]

 

How can I identify the Control-M Data Center.

 

Environment

Release : 6.4.2

Resolution

You can use the query below against the Control-M Enterprise Manager's database to identify the Control-M data_center that should be used in the "Control-M Data Center" field when adding the scheduler through the AAI website.

 

Used the Enterprise Manager's database server for the JDBC string.

Then found the data_center name from the comm table of their Control-M em900 database.

 

em900=> select data_center, platform, control_m_ver, ctm_host_name, gtw_host_name from comm;

 

https://api-broadcom-ca.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=wPDbeqqAHKeAZPZYvyUVFg==

 

Once the correct Data Center is entered you should no longer see the error in the connector.log file.