Smarts SAM: EMC Data Access API (EDAA) service not starting; Ports 8080, 8005 and 8009 already in use by Business Dashboard; How to change EDAA ports?
search cancel

Smarts SAM: EMC Data Access API (EDAA) service not starting; Ports 8080, 8005 and 8009 already in use by Business Dashboard; How to change EDAA ports?

book

Article ID: 331721

calendar_today

Updated On:

Products

VMware Smart Assurance

Issue/Introduction

Symptoms:


Default ports when configuring tomcat are 8080, 8005 and 8009

However, if Businesss Dashboard is running tomcat on these ports as per default installation, trying to set up a service like EDAA on same server causes port conflict as default ports for this version of tomcat are also 8080, 8005 and 8009. 

Note : When Business Dashboard and EDAA are running on same server, they require 2 versions of tomcat to run - one is installed with the Console for the Dashboard service and the other for the SAM server services that require it such as EDAA. 




Default ports when configuring tomcat are 8080, 8005 and 8009

However, if Businesss Dashboard is running tomcat on these ports as per default installation, trying to set up a service like EDAA on same server causes port conflict as default ports for this version of tomcat are also 8080, 8005 and 8009. 

Note : When Business Dashboard and EDAA are running on same server, they require 2 versions of tomcat to run - one is installed with the Console for the Dashboard service and the other for the SAM server services that require it such as EDAA.

Therefore need to change default ports for SAM server tomcat

Environment

VMware Smart Assurance - SMARTS

Cause

When Business Dashboard and EDAA are running on same server, they require 2 versions of tomcat to run - one is installed with the Console for the Dashboard service and the other for the SAM server services that require it such as EDAA.

Resolution

1.  Find a list of ports that are not being used on the server :

Windows: Run command:

netstat -anb -p TCP

Linux: Run command:
 
netstat -anpt 
 
2.  On the server where EDAA is installed, go to the tomcat directory of the SAM installation

./SAM/smarts/tomcat/conf  and save a copy of server.xml to server.xml.orig

3.  Edit the server.xml file 


Change the ports 8080, 8005 and 8009 to ports that are not being used (in this example 8015, 8181 and 8019):

<Server port="8015" shutdown="SHUTDOWN">
  <!-- Security listener. Documentation at /docs/config/listeners.html
  <Listener className="org.apache.catalina.security.SecurityListener" />
  -->
  <!--APR library loader. Documentation at /docs/apr.html -->
  <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" />
  <!--Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html -->
  <Listener className="org.apache.catalina.core.JasperListener" />
  <!-- Prevent memory leaks due to use of particular java/javax APIs-->
  <Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener" />
  <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
  <Listener className="org.apache.catalina.core.ThreadLocalLeakPreventionListener" />
 
  <!-- Global JNDI resources
       Documentation at /docs/jndi-resources-howto.html
  -->
  <GlobalNamingResources>
    <!-- Editable user database that can also be used by
         UserDatabaseRealm to authenticate users
    -->
    <Resource name="UserDatabase" auth="Container"
              type="org.apache.catalina.UserDatabase"
              description="User database that can be updated and saved"
              factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
              pathname="conf/tomcat-users.xml" />
  </GlobalNamingResources>
 
  <Service name="Catalina">
 
    <!--The connectors can use a shared executor, you can define one or more named thread pools-->
    <!--
    <Executor name="tomcatThreadPool" namePrefix="catalina-exec-"
        maxThreads="150" minSpareThreads="4"/>
    -->
 
    <Connector port="8181" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" />
 
    <!-- Define an AJP 1.3 Connector on port 8009 -->
    <Connector port="8019" protocol="AJP/1.3" redirectPort="8443" />


4. Set  the SM_TOMCAT_SERVER to the replacement port for 8080 (line with: protocol="HTTP/1.1") in the runcmd_env.sh file:

From:

SM_TOMCAT_SERVER=http://<public_hostname>:<public_port>

To (e.g., in this instance):

SM_TOMCAT_SERVER=http://<public_hostname>:8181

5. Restart the tomcat service

The method used to restart Tomcat depends on how it was started and which OS is in use.
 
Linux service:
 

sm_service stop smarts-tomcat
sm_service show
sm_service start smarts-tomcat
 
Linux interactive command line terminal:
 

Ctrl+C from the window it was started in
Use sm_tomcat to restart it.
This process needs to be changed in the normal ways if started in a console and then sent to background
 
Windows service:
 

Use the Service control panel to stop the service named "EMC Smarts Data Web Applications (Tomcat)"
Use the Service control panel to start the service named "EMC Smarts Data Web Applications (Tomcat)"
 
Windows console terminal:
 

Ctrl+C from the window it was started in, or close the window it is running in.
Use sm_tomcat to restart it