Smarts: Limitations in running sm_edit against the various Connect.conf files
Article ID: 332208
Updated On:
Products
VMware Smart Assurance
Environment
VMware Smart Assurance - SMARTS
Resolution
For all the files which have encryption embedded in it (such as clienctConnect.conf, serverConnect.conf), we require it to be copied into their respective "local/conf" folder. These folders are not created by default by Smarts.
For example, if the SM_SITEMOD has the value of /opt/InCharge9/SAM/smarts/new-local" , then there must be a local directory created underneath it called local/conf. Then the entire path would be "/opt/InCharge9/SAM/smarts/new-local/local/conf".
Now when you run "./sm_edit conf/clientConnect.conf" it will copy the "clientConnect.conf" from the "BASEDIR/conf " to "/opt/InCharge9/SAM/smarts/new-local/local/conf/" and open it for editing.
sm_edit also iterates only 3 levels of the directory for SM_SITEMOD. Thus having a directory structure like:
/opt/InCharge9/local-now/conf
This means you set the SITEMOD to:
SM_SITEMOD=/opt/InCharge9/new-local/
For example, if the SM_SITEMOD has the value of /opt/InCharge9/SAM/smarts/new-local" , then there must be a local directory created underneath it called local/conf. Then the entire path would be "/opt/InCharge9/SAM/smarts/new-local/local/conf".
Now when you run "./sm_edit conf/clientConnect.conf" it will copy the "clientConnect.conf" from the "BASEDIR/conf " to "/opt/InCharge9/SAM/smarts/new-local/local/conf/" and open it for editing.
sm_edit also iterates only 3 levels of the directory for SM_SITEMOD. Thus having a directory structure like:
/opt/InCharge9/local-now/conf
This means you set the SITEMOD to:
SM_SITEMOD=/opt/InCharge9/new-local/
Feedback
Yes
No
Powered by
