ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

DX APM - Installation of Multiple Instances of the Infrastructure Agent not registering SysEdge as a second service.

book

Article ID: 238069

calendar_today

Updated On:

Products

DX Application Performance Management

Issue/Introduction

Symptoms:

To install the second instance of APMIA on the same server you will follow the steps from DX APM - SaaS:


https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/dx-apm-saas/SaaS/implementing-agents/infrastructure-agent/Install-the-Infrastructure-Agent-on-Windows.html

APMIACtrl.bat install service_name "<service_name>" display_name "<display_name>"

However, using the command above is not honoring the blanks in not registering SysEdge as a second service.

Cause

You don't have to install SysEdge twice.

Environment

Windows Server 2012 & 2019
APM Infrastructure Agent 10.7 - already installed
DX APM Infrastructure Agent 22.1.0.25 downloaded from SaaS installed as a 2nd instance of the APMIA on the same machine

Resolution

Disable SysEdge installation on the second APMIA agent setting the following property to false in IntroscopeAgent.profile as per the screenshot below, reinstall the 2nd agent and it will report to the service of the first agent.

introscope.agent.hostmonitor.sysedge.enabled=false

Additional Information

You can use the following command to uninsntall your 2nd APMIA instance:

APMIACtrl.bat uninstall service_name "<service_name>" display_name "<display_name>"

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/dx-apm-saas/SaaS/implementing-agents/infrastructure-agent/Install-the-Infrastructure-Agent-on-Windows.html

Attachments