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: How to change Watch4net portal URL (304758)

Last Updated: 5/29/2020Categories: How toTotal Views: 2271Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Resolution

How to change port number that the Watch4net portal listens on from the default 58080 to a different port such as 80

How to change the Watch4net portal URL from http://apgportal.customer.net:58080 to http://apgportal.customer.net

To change port number W4N is listening on from 58080 to different port such as 80, do the following:

In an XML editor, open the Watch4net server.xml file in the following directory:

<APG>/ Web-Servers/Tomcat/Default/conf

Find the main Connector element in the server.xml file, and change the Connector port attribute from 58080 to the desired port number (see following "Port change considerations" section). The following shows the main Connector element section:

<Connector port="58080" protocol="HTTP/1.1"

connectionTimeout="20000"
compression="off" compressableMimeType="text/"
redirectPort="58443" URIEncoding="UTF-8" />

Restart Tomcat service.

Port change considerations
In Linux, ports below 1024 are reserved for privileged users like root. To have the Watch4net Tomcat service running by the Watch4net apg user on a port lower than 1024 such as port 80, you must set Tomcat as root user by adding apg.user=root  to unix-service.properties file in the in "Main Service Properties" section. The unix-service.properties file is found in the following Watch4net directory:

<APG>/ Web-Servers/Tomcat/Default/conf

Alternatively, you can use the iptables command in Linux and a technique known as port relaying or net filtering to "relay" Port 80 tcp connections to port 58080. The syntax for this command is as follows:

iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 58080

(replace eth0 with your actual interface name if it is different)

To add a redirect message:

1. Create ROOT folder

mkdir /opt/APG/Web-Servers/Tomcat/Default/webapps/ROOT

2. Create index.html

vi /opt/APG/Web-Servers/Tomcat/Default/webapps/ROOT/index.html

3. Paste the following content (sample message in body):

<html>
<head>
<title>Redirect</title>
<META http-equiv="refresh" content="0;URL=/APG/">
</head>
<body>Please wait while redirecting...
</body>
</html>

4. Change permissions, owner & group to ROOT folder:

chmod 755 /opt/APG/Web-Servers/Tomcat/Default/webapps/ROOT/

chown R apg:apg /opt/APG/Web-Servers/Tomcat/Default/webapps/ROOT/

5. Restart tomcat

/opt/APG/bin/./manage-modules.sh service restart tomcat

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