Data Storage and Management

The first time you run dsClient Desktop the application asks you to designate a directory that it will use as the application library. This library not only houses your test and report configurations, it is also used to store information downloaded from dsTest as well as information that you will import into the library to be used in your tests or credentials used to connect to the dsTest platform. In this topic we'll delve into the application library structure and how the application manages the information it contains.

We strongly recommend that you backup your application data on a regular basis. Backing up the application library and either the directory where you installed dsClient Desktop (standalone application) or the <home directory>\.dsClient directory (web start) will safeguard all of your information.

The cache directory primarily stores files the application downloaded from dsTest, files that you import into the system to augment your test configurations, and supplemental files generated by the application. When dsClient starts it scans all of the servers you registered with the application to learn what version of dsTest is installed and to download their licenses. If an unknown version is encountered dsClient downloads the information noted below from that server. You can initiate a full server scan from the same screen you use to register your servers.

The application is dependent on the names and locations of the directories described in this section and it will (re)create any directories that it cannot locate within your application library. Do not modify the structure or contents of the cache directory unless you are following the instructions of our Support Team.

csv_config - When you provision subscriber data using a CSV file, that file will be imported into this directory. You will also be able to open and edit the file directly from your workspace after importing.

default - This directory contains the schema files for both dsTest and dsClient that were packaged with the application. The dsTest schema files are only used before the application has successfully downloaded a set of schema files from your dsTest server.

dictionaries - Protocol dictionaries that are supported by dsClient are stored in this directory. They provide the usage information displayed in the Schema Help available within dsClient as well as a source for importing structures into Message Templates and custom dictionaries. dsClient refreshes the Diameter dictionary files whenever it recognizes that dsTest's version has changed. The dictionary files for other protocols are packaged with dsClient.

dsTest - dsClient downloads dsTest's schema files when it first scans your dsTest server and after you upgrade dsTest. The files are stored in a sub-directory that identifies the software version they are associated with, enabling one dsClient application to support and interact with multiple versions of dsTest. During its shutdown procedures, dsClient removes any sub-directories that have become obsolete.

images - dsClient generates images of certain configurations to be displayed in the Workspace as visual clues, and it stores those images in this directory.

key_files - If you use key-based authentication to connect to your dsTest platform via SSH, the private key file(s) that you import will be stored in this directory.

licenses - dsTest licenses downloaded by the application are stored in this directory.

templates - You'll find the example templates for HTML Test Results packaged with the application in this directory.

The xmlLibrary directory is your local library and it will store your test and report configurations. The content of this directory is yours to organize as you see fit - you can store everything in the root directory or create sub-directories. dsClient scans the xmlLibrary directory when the application starts to learn your library's structure and contents. See About the XML Library for more information about linking to shared libraries and managing your Local Library.

The examples directory contains example test configurations downloaded from dsTest. See About the XML Library for more information.

Finally, dsClient uses the temp directory to store transitory files that it generates for various purposes. The contents of this directory are deleted during application shutdown procedures.