Cisco Cisco Workload Automation 6.3 User Guide

Troubleshooting

Troubleshooting the Client Manager

How to Clear the Cache When Needed 

Clearing the cache involves truncating all tables in the schema except the table CACHEPROPERTY. CACHEPROPERTY 
holds the value of Cache.Version.  Optionally, dropping all tables in the schema can also clear the cache. A SQL script 
will be provided to the customer for clearing cache via table drops.

To clear the cache:

Locate the clearcache.sql script.

Execute script as the user for the cache database. 

Verifying the Version of the Client Manager

When consulting with the Cisco Technical Assistance Center about a problem with the Client Manager, one of the most 
basic pieces of information they need is which version of the Client Manager is being used.

To verify the version of the Client Manager:

In the Client Manager log folder, open any log file. Verify at the top of the file the four digit version number. For example, 
6.0.0.1192.

You can also check the clientmgr.out file located in the same folder.

Diagnostic Logging for the Client Manager

clientmgr.props file contains several logging categories. The following two are the main logging categories that apply to 
the Client Manger:



DspLog – For items related to the DSP module.



CommonsLog – For items related to core component logging, such as the Jetty embedded Web server.

The following is an example clientmgr.props file:

PrimaryServer=tcp://server:6215

Security.Authentication=ActiveDirectory

ActiveDirectory.Host=adhost

ActiveDirectory.Port=389

ActiveDirectory.UserSearchPrefix=DC=testdomain,DC=local

ActiveDirectory.GroupSearchPrefix=DC=testdomain,DC=local

JAVA_HOME=C:\Program Files\Java\jre6

JVMARGS=-Xms8192m -Xmx8192m -XX:PermSize=128m -XX:MaxPermSize=128m

MaxLogFiles=1000

JmxRmiPort=1100

JmxOn=Y

<DSP>.dsp contains the following properties for the DSP:



CacheLog – Applies to writing to the cache during synchronization.