Installing Client Manager for Windows
To install Client Manager:
Step 1 Transfer the appropriate installation files to the target machine (binary mode).
Step 2 Double-click setup.exe. The Security Warning dialog box displays.
Step 3 Click Run. The Internet Explorer-Security Warning dialog box displays.
Step 4 Click Run. The InstallShield Wizard Welcome dialog box displays.
Step 5 Click Next. The Destination Folder panel displays.
Step 6 Select the directory where the TES files will reside.
- Click Change to search for a directory.
-or-
- Accept the default location C:\Program Files\.
Step 7 Click Next. The TES DSP Name and Master IP panel displays.
Step 8 In the TES DSP NAME field, enter the name of your Data Source (TES 6.2) Plug-in.
This value can be anything you want it to be. The default is tes-6.2.
Note Architecturally, the Client Manager is written to be a generic container of plug-ins and is not TES-specific. The TES-specific parts of the UI are in TES plugin.
Step 9 In the Primary Server IP field, enter the host name or IP address for your primary master. The default port is 6215.
Step 10 If using Fault Tolerance, in the Backup Server IP field, enter the IP address for your backup master.
Step 11 Click Next. The Cache Database Server panel displays.
By default, Internal Cache DB server is selected. Alternatively, external DB servers may be provisioned to run Cache Database.
Step 12 Click Next. The Database Server Credentials panel displays if you selected an external database server.
Figure 4-1 Database Server Credentials Panel
Step 13 Enter the credentials for the selected external database, then click Next. The Active Directory/LDAP Authentication panel displays.
Step 14 Select an option, then click Next.
If configuring the Client Manager to use the Active Directory option, the Active Directory Authentication panel displays.
Figure 4-2 Active Directory Authentication Panel
If configuring the Client Manager to use the LDAP option, the LDAP Authentication panel displays.
Figure 4-3 LDAP Authentication Panel
Step 15 For Active Directory, enter the following information:
- Host – Enter the hostname or IP address for the Active Directory server.
- User Search Prefix – Enter the location you want Active Directory to search for users.
- Group Search Prefix – Enter the location you want Active Directory to search for groups.
- Port – Enter the port number for the AD server.
-or-
For LDAP, enter the following information:
- Hostname – Enter the hostname or IP address for the LDAP server.
- Port – Enter the port number for the LDAP server.
- BindDN – Enter the user account to query the LDAP server.
- UserObjectClass – Specify a valid object class for the BindDB user. Only users who posses one or more of these objectClasses will be permitted to authenticate.
- UserBindDN – Enter the user account to query the LDAP server.
- User-role based access for Oracle/Sun Directory Server – Select this option if your TES 6.2 Web Client user authentication is defined to use Oracle/Sun Directory Server with role-based access.
- GroupBindDN – Enter the group account to query the LDAP server.
Example of an AD Setting
Security.Authentication=ActiveDirectory
ActiveDirectory.Host=sjc-ad-1
ActiveDirectory.Port=389
ActiveDirectory.UserSearchPrefix=DC=tidalsoft,DC=local
ActiveDirectory.GroupSearchPrefix=DC=tidalsoft,DC-local
Example of an LDAP Setting
Security.Authentication=LDAP
LDAP.HostName=172.25.6.xxx
LDAP.Port=389
LDAP.BindDN=ou=people,dc=tidalsoft,dc=local
LDAP.UserObjectClass=inetOrgPerson
LDAP.ContextFactory=com.sun.jndi.ldap.LdapCtxFactory
LDAP.AuthenticationMethod=simple
LDAP.UserBindDN=dc=tidalsoft,dc=local
LDAP.GroupBindDN=dc=tidalsoft,dc=local
Note TES 6.2 allows for multiple-domain user authentication for CM. The purpose of this function is to allow users defined in different domains to be authenticated within one CM configuration to avoid installing one CM per domain limitation.
To enable this function:
1. Add the following new property value in clientmgr.props, located under <CM_INSTALL>\config.
Security.Authentication.Ext.File=user-auth.xml
Where user-auth.xml is the file name.
2.Build the user-auth.xml file to include all AD/LDAP servers for TES user authentication.
<ext-user-auth>
<user-auth>
<name>TIDALSOFT</name>
<desc>Configure AD for user user authentication</desc>
<type>ActiveDirectory</type>
<host>hou-ad-1.tidalsoft.local</host>
<port>389</port>
<ad.usersearchprefix>DC=tidalsoft,DC=local</ad.usersearchprefix>
<ad.groupsearchprefix>DC=tidalsoft,DC=local</ad.groupsearchprefix>
</user-auth>
<user-auth>
<name>ITTIDAL</name>
<desc>Configure Open LDAP Server for user authentication</desc>
<type>LDAP</type>
<host>10.88.103.148</host>
<port>5389</port>
<ldap.binddn>ou=People,dc=ittidal,dc=com</ldap.binddn>
<ldap.userobjectclass>account</ldap.userobjectclass>
<ldap.userbinddn>dc=ittidal,dc=com</ldap.userbinddn>
<ldap.groupbinddn>cn=testest,ou=Group,dc=ittidal,dc=com</ldap.groupbinddn>
<ldap.useridentifiertype>uid</ldap.useridentifiertype>
</user-auth>
</ext-user-auth>
In the above example, the authentication process will validate tidalsoft first and then ittidal.
Step 16 Click Next. The Ready to Install the Program panel displays.
Step 17 Click Install. The Installing Tidal Client Manager panel displays.
Step 18 If any information is incorrect, retrace your steps and correct the information by clicking Back until you reach the desired screen.
-or-
If the information is correct, click Install to start the installation of the Client Manager files.
The Installing Tidal Client Manager panel displays. The status of your client installation displays with a progress bar.
Caution
Do not click Cancel once the installation process begins copying files in the Setup Status dialog box. Cancelling the installation at this point corrupts the installation program.You will not be able to install the component without the help of support. If you decide you do not want to install the component, complete the installation and then uninstall.
Step 19 The Setup Completed panel displays.
Step 20 Click Finish.
Note Before starting the Client Manager, be sure to apply the latest hotfix obtained from cisco.com. To ensure compatibility, apply the latest 6.2 hotfix patches to the Master and other components, each time the hotfix patches are applied to the CM. The first time the Client Manager is started, it initializes its data from the master. Depending upon the amount of data, this could take up to 20 minutes.