VMware Smart Assurance SMARTS: How to Configure EDAA for Smarts IP domains (Smarts 9.3 and above)
search cancel

VMware Smart Assurance SMARTS: How to Configure EDAA for Smarts IP domains (Smarts 9.3 and above)


Article ID: 323802


Updated On:




There are two variants of the Smarts EDAA, the Smarts 9.2.x EDAA and the Smarts 9.3 EDAA.  One big difference between the Smarts 9.2.x EDAA and the Smarts 9.3 EDAA is how they are delivered.  

The Smarts 9.2.x EDAA is delivered with the Smarts 9.2.x Console software while the Smarts 9.3 EDAA is delivered with the Smarts 9.3 Service Assurance Manager.  

Please make sure you are using the correctly KB article for the deployment you have.  This article is for the Smarts 9.3.x EDAA and above

To query the APM domain via EDAA requires INCHARGE-AM-PM to be enabled with EDAA mode and then configure it to be able to successfully communicate with the EDAA hosted on the SAM server (remote or local)


VMware Smart Assurance - SMARTS


Please follow the steps to setup the INCHARGE-AM-PM domain and use the existing SAM EDAA as follows:

  • Ensure the APM domain is started with the EDAA mode with the following in the command-line for the service:
  • On the AMPM installation, please make an entry to the SAM-Tomcat as follows 
<IP-BASEDIR>/smarts/bin/sm_edit local/conf/runcmd_env.sh
  • Restart the APM services for the change to take effect.
  • Edit the msa-sources.xml file located in the SAM installation in /smarts/tomcat/webapps/smarts-edaa/WEB-INF/classes to add entries for your IP Managers. 
a) Add the entry key information with the corresponding bean id information as follows:
            <entry key="AMPM-01"
AMPM-01" />

b) Add the corresponding bean id information.
            <bean id="MsaDMTDataSource__AMPM-01" class="com.emc.msa.dmt.dmpool.MSADMTContext">
              <property name="brokerContext" ref="MsaDMTDataSource__Broker" />
              <property name="dmtName" value="
AMPM-01" />
              <property name="dataSourceName" value="
AMPM-01" />
              <property name="modelName" value="ip" />
              <property name="modelVersion" value="2.0" />
              <property name="useTLS" value="true" />
              <property name="disableKeepalives" value="true" />
              <property name="lockBoxSupport" value="false" />
              <property name="excludeClasses" ref="IP-ExcludeClassesDefault"/>
              <property name="excludeAttributes" ref="IP-ExcludeAttrsDefault"/>
Use the full domain name as it is registered with the Broker (for example, INCHARGE-AM-PM  and not APM). The entry key parameter value should match the datasource name (the domain name with which the IP Manager is started). 

The value of the bean id parameter must match the value-ref parameter value. 
The dmtName property value and the dataSourceName property value must match the entry key value. 
  • Open the msa-model-defaults.xml file in the /smarts/tomcat/webapps/smarts-edaa/WEB-INF/classes/ directory. If not commented, comment the MR_MetaObject value in the xml node with id="IPExcludeClassesDefault". 
For example: 
<!-- Start of Default Values for Provider Entries -->
<util:list id="IP-ExcludeClassesDefault">
<!--<value>MR_MetaObject</value> -->
  • Use sm_edit to open the <SAM-BASEDIR>/smarts/conf/edaaClientConnect.conf file.
a. Add an entry for the IP Manager using the format
*:Insert APM Domain name Here:admin:changeme
The account _edaa is used to log in to IP Managers 9.3 and higher.
b. Save the file.
  • Stop and start the smarts-tomcat, smarts-rabbit-mq, and smarts-elasticsearch services

Additional Information

For NPM Domains, please review KB: https://kb.vmware.com/s/article/89538?lang=en_US