Tomcat SSL Certificate Not Taking Effect After Deployment

Products

• VMware Smart Assurance
• Network Observability

Issue/Introduction

• We have uploaded a new SSL certificate (.p12 format) into the SMARTS Tomcat certificate directory; however, the certificate does not appear to be working after deployment.
• EDAA root not found error in smarts-edaa.log and during querying EDAA API

Environment

All supported release of Smarts

Resolution

1) Ensure the SAM-PRES domain is started with the EDAA mode with the following in the command-line for the service:

'--edaa=sam-presentation/2.0'

2) Edit the msa-sources.xml file located in the SAM installation in <BASEDIR_SAM>/smarts/tomcat/webapps/smarts-edaa/WEB-INF/classes to add entries for your SAM-PRES domain. 

a) Add the entry key information with the corresponding bean id information as follows:

            <entry key="SAM-PRES"
            value-ref="MsaDMTDataSource__SAM-PRES" />

b) Add the corresponding bean id information.

 <bean id="MsaDMTDataSource__SAM-PRES"
          class="com.emc.msa.dmt.dmpool.MSADMTContext">
          <property name="brokerContext" ref="MsaDMTDataSource__Broker" />
          <property name="dmtName" value="SAM-PRES" />
          <property name="dataSourceName" value="SAM-PRES" />
          <property name="modelName" value="sam-presentation" />
          <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="SAMPRES-ExcludeClassesDefault"/>
          <property name="excludeAttributes" ref="SAMPRES-ExcludeAttrsDefault"/>
          <property name="dmtMSAClasses" ref="SAMPRES-MSAClassesDefault"/>
          <property name="maxActiveConnections" value="15" />
    </bean>

 

 

Note: Use the full domain name as it is registered with the Broker. 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. 

 

3) Restart smarts-tomcat service for changes to take affect. 

sm_service stop smarts-tomcat
sm_service start smarts-tomcat