The security configuration files, clientConnect.conf and serverConnect.conf, located in the BASEDIR/smarts/conf directory of each VMware Smart Assurance software installation, allow you to set up secure connections between the component applications in a VoIP Availability Manager deployment. By default, the configuration option settings in the clientConnect.conf file and the serverConnect.conf files allow minimally secure connections between the components.

An VoIP Availability Manager deployment employing secure communications has the following environment variables set to the same value in each component application’s BASEDIR/smarts/local/conf/runcmd_env.sh file:

SM_INCOMING_PROTOCOL=[1,0 or 2,0 or 3,0]
SM_OUTGOING_PROTOCOL=[1,0 or 2,0 or 3,0]

For example:

SM_INCOMING_PROTOCOL=2,0
SM_OUTGOING_PROTOCOL=2,0

If you decide to configure client tools, you also need to create a secure connection between the Global Console and the Global Manager. To do so, you need to modify the clientConnect.conf file in the BASEDIR/smarts/conf directory in the Service Assurance Manager installation area for the Global Console. Client tools are described in “Configuring client tools for VoIP Availability Manager” on page 70.

The VMware Smart Assurance System Administration Guide presents detailed information about VMware Smart Assurance secure communications.