The customer's environment has APM Command Center installed on the same server as the EM.
They configured 443 as the port for both to use and saw an immediate conflict with the ports.
They also planned to use a second NIC card to help direct the traffic to the needed application. One for the Command Center and the other for Webview.
Seeing the following errors:
INFO | jvm 1 | 2016/04/19 09:46:26 | 4/19/16 09:46:26.827 AM EDT [WARN] [org.mortbay.log] failed [email protected]:java.net.BindException: Address already in use: JVM_Bind
INFO | jvm 1 | 2016/04/19 09:46:27 | 4/19/16 09:46:27.036 AM EDT [INFO] [org.mortbay.log] Stopped [email protected]:443
INFO | jvm 1 | 2016/04/19 09:46:27 | 4/19/16 09:46:27.037 AM EDT [ERROR] [WebView] WebView was unable to start because it could not bind to port 0. Check for another process running on this port.
APM 10.0 and greater
Even though they have 2 incoming IP addresses, Jetty didn't know which of the 2 IPs to bind to for the 443 port.
Add the following parameter to the webview-jetty-config.xml file will tell Jetty which IP/NIC to listen on.
<Set name="host">###.###.###.###</Set> (add your IP address)