Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

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

Last Updated: 9/19/2022Categories: How toTotal Views: 887Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

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)

Purpose

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

Resolution

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:

'--edaa=ip/2.0'

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

SM_TOMCAT_SERVER=http://<tomcat_FQDN_or_ipadress>:<port>

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"
value-ref="MsaDMTDataSource__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"/>
</bean>

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>GA.*</value>
<!--<value>MR_MetaObject</value> -->
<value>ICIM_Test</value>
<value>NasManager</value>
<value>Topo.*</value>
<value>Hierarchical.*</value>
<value>VOIP.*</value>
</util:list>

Use sm_edit to open the <SAM-BASEDIR>/smarts/conf/edaaClientConnect.conf file.

a. Add an entry for the IP Manager using the format

#*:<DOMAINNAME>:admin:changeme.
*:Insert APM Domain name Here:admin:changeme
::_edaa: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

Related Information

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

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
Workspace ONE Intelligence 2020/06/17 リリースのお知らせ (79631)

KB
•
VMware AirWatch MDM Agent 6.5.11 for Windows Mobile/CE リリースのお知らせ (79610)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - SMARTS

Take Our Survey

Support Assistant