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

Watch4Net 6.8 | Smarts 9.5 | Notifications are blank (511980)

Last Updated: 5/29/2020Categories: TroubleshootingTotal Views: 17140Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

On a fresh install of Watch4Net 6.8 connecting to smarts 9.5 notifications and topology data are blank.

Cause

This was caused by a mismatch in tomcat port between Watch4net and Smarts. Watch4Net is set up by default to use SSL port 58443. In this instance the customer did not wish to use SSL and had set up 58080 on the smarts side.

Resolution

If the customer does not wish to use SSL they must adjust the server.xml on the watch4net side:

From the Watch4net Front end modify:  /opt/APG/Web-Servers/Tomcat/Default/conf/server.xml file:
a. Locate and remove the entry redirectPort="58443"

Before:

<Connector port="58080" protocol="HTTP/1.1"
connectionTimeout="20000"
compression="2048"/>
redirectPort="58443" URIEncoding="UTF-8" />

After you remove the entry it will look like this:

<Connector port="58080" protocol="HTTP/1.1"
connectionTimeout="20000"
compression="2048"
URIEncoding="UTF-8" />

Then locate the following line and comment it out

Before

<Valve className="com.watch4net.apg.v2.gui.tomcat.ForceSSL" />

after

<!-- <Valve className="com.watch4net.apg.v2.gui.tomcat.ForceSSL" /> -->

Then restart the tomcat service.

This can be done via the GUI in centralized management

or via CLI from the front end server

/opt/APG/bin/mange-modules.sh service restart tomcat Default

Clear the browser cache, and then log in using HTTP.

If the customer wishes to use SSL:

1. Navigate to Centralized Management and expand SolutionPacks>Infrastructure from the left hand tree then Select EMC smarts.
2. Click the pencil icon by the 'Reports SolutionPackBlock'
3. Expand Tomcat Configuration and choose 'Add a new Tomcat configuration' in the drop down box.
4. Click the checkbox for 'HTTPS Enabled for EMC M&R and Smarts'

5.  Ensure the FQDN is specified for the Tomcat server and that it matches the SM_CAS_Server entry on SAM runcmd_env.sh file.
6. Verify that the entry in Smarts EDAA hostname or IP address field matches the SM_TOMCAT_SErver in the Presentation SAM runcmd_env.sh
7. Verify the ports default EMC M&R tomcat port number 58443. Default EDAA port number 8443
8.Verify remaining fields and click 'Reconfigure'

Then continue with SSL certificate generation import and export steps.
The changes will not take effect until the Tomcat servers are restarted in both SAM and EMC M&R.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - Watch4Net/M&R

Take Our Survey

Support Assistant