Limitations in running sm_edit against the various Connect.conf files

Products

• VMware Smart Assurance
• VMware Telco Cloud Service Assurance

Issue/Introduction

Items to keep in mind when modifying encrypted configuration files using sm_edit

Environment

10.x Smart

2.x TCSA

Resolution

All files such as clientConnect.conf and serverConnect.conf have embedded encryption within the file.  The encryption of these files is located at the beginning of the file.  

Modifications of these configuration files must be saved in the following directory:

<Basedir>/smarts/local/conf

"sm_edit" will copy the configuration file from the "<BASEDIR>/conf " to "<BASEDIR>local/conf/" and open it for editing.

"sm_edit" also iterates only 3 levels of the directory for SM_SITEMOD.  If you have set "SM_SITEMOD" to 

/opt/<product directory>/new_local

then the saved directory would look like: 

/opt/<product directory>/new_local/conf