Configuring client tools procedure

Configuring client tools involves modifying existing user profiles to use the client tools, copying the client tool scripts to the locations where Global Consoles reside (sometimes a Global Console resides on a remote host), specifying which web browser to use, specifying login credentials, setting up security, and verifying that the client tools launch from the Global Consoles.

Perform these steps to configure VoIP client tools:

Modify existing user profiles to enable client tools.
Import the configureVoipPmTools.xml file into the Global Manager. The configureVoipPmTools.xml file provides default settings for the client tools which appear in the Global Manager Administration Console.

Go to the BASEDIR/smarts/bin directory in the Service Assurance Manager installation area where the Global Manager is running and type this command:
```
t sm_config -s <
               Global Manager name
               > import --force configureVoipPmTools.xml s
```
In the Global Console, select Configure > Global Manager Administration Console to open the Global Manager Administration Console for the attached Global Manager.
In the left panel tree, expand User Profiles and select the user profile to add the client tools to it and click Apply.

The VMware Smart Assurance Service Assurance Manager Configuration Guide provides detailed information about using the Global Manager Administration Console to assign client tools to user profiles and, if necessary, to create new user profiles.

Note:
Changes to a user profile may not be available to console users until they restart the Global Console.
Copy the client tool scripts into the Service Assurance Manager directory where the Global Consoles reside. Client tools must reside on the same hosts with the consoles.

Copy the entire voip subdirectory found in the VoIP Management Suite installation area (BASEDIR/smarts/actions/client/voip) as a subdirectory under the BASEDIR/smarts/actions/client directory in the Service Assurance Manager installation area for the Global Console.
Note:
ts indicates the command must be typed as one line. The copy commands below assume that the VoIP Management Suite and the Service Assurance Manager reside on the same host.

For UNIX, type the following command and press Enter:
```
t cp -r /opt/InCharge/VoIP/smarts/actions/client/voip /opt/InCharge8/SAM/smarts/actions/client/voip s
mkdir C:\InCharge8\SAM\smarts\actions\client\voip 
t copy C:\InCharge\VoIP\smarts\actions\client\voip C:\InCharge8\SAM\smarts\actions\client\voip s
```
If necessary, change the default location and the web browser. The default setting is Netscape Navigator for UNIX.
Go to the BASEDIR/smarts/bin directory in the Service Assurance Manager installation area for the Global Console and use sm_edit to open the config.sh file for UNIX.

For example, type:
```
               sm_edit actions/client/voip/config.sh
            
```

Modify the browser setting in the config file.

For UNIX, replace the default path with the location for your web browser:

BROWSER=/usr/dt/bin/netscape
export BROWSER
/usr/bin/mozilla 
set "BROWSER=C:\Program Files\Internet Explorer\IEXPLORE.EXE"

Save and close the file. The file will be saved to the local directory.
On the VoIP Performance Manager, create a non-administrative user account for client tools.

The non-administrative user account grants non-authenticated users sufficient access to the services offered by VoIP Performance Manager. Users who log in to VoIP Performance Manager through the Java-based GUI, whether authenticated or not, have read-only access.

VMware recommends the use of a non-administrative account for VoIP client tools. The VMware Smart Assurance VoIP Performance Manager System Guide provides instructions for creating accounts for VoIP Performance Manager.

The VoIP Performance Manager attributes for a non-administrative account are User_ID and EncryptedPassword (read-only).

Later for step 5 on page 73 , instead of an administrator account, use the non-administrative account values when you specify login credentials in the Device Access tab for VoIP client tools.
Open Device Access tab in the Global Console and select the setting for the VoIP PM Servers group.

To do so, from the Global Console, select Configure > Domain Manager Administration Console > Polling and Thresholds to open the Polling and Thresholds Console for the attached VoIP Availability Manager. In the Device Access tab, select the setting for the VoIP PM Servers group. “VoIP PM Web Interface setting” on page 164 provides more information about this setting.

For the setting for the VoIP PM Servers group, specify:
- Login credentials (the device user ID and password).
  - If necessary, the IP address for the VoIP Performance Manager’s web server if the web server and the VoIP Performance Manager are installed on different systems.
  - If necessary, a different port for the VoIP Performance Manager’s web server if the default port (80) is reserved or in use.
    
    You must click Apply to save your changes and then click Reconfigure in the Polling and Thresholds Console to make the configuration changes take effect as described in “Creating a credential set” on page 165.
Create a secure connection between the Global Console and the Global Manager.

Modify the clientConnect.conf file in the BASEDIR/smarts/conf directory in the Service Assurance Manager installation area for the Global Console.

The VMware Smart Assurance System Administration Guide describes security and the syntax of the clientConnect.conf file. The VMware Smart Assurance Service Assurance Manager Configuration Guide describes security considerations for tools.
Verify that the client tools launch for the user profiles.
Log in as an operator, for example.
Open a Topology Browser Console attached to the Global Manager (for example, INCHARGE-SA) and right click on a target topology object to verify that the client tools appear in the Client Tools submenu.

Note:
Client tools are invoked under the username of the operator who started the Global Console. If the client tools do not display in the Client Tools submenu, detach and reattach the Global Console to the Global Manager.
Launch some or all of the client tools to confirm that the tool can access the web server running on the VoIP Performance Manager.