Administering HATS rich client applications

For more information about running in different test modes, see Testing modes for rich client projects.

While in the HATS Toolkit, you can edit these files to change settings, for example trace and trace level settings. The files are located in the root of the runtime extension plug-in project. Be aware that any changes made to the runtime.properties file in the HATS Toolkit are retained and become effective when you deploy the HATS application to a runtime environment. In the runtime environment, the runtime.properties file is located in the runtime extension plug-in directory, for example, <eclipse_install_dir>/eclipse/plugins/com.ibm.hats.rcp.runtime.extension_1.0.0. The runtime-debug.properties file is ignored in the runtime environment. For more information about log and trace settings in these files, see Runtime properties files.

For information about how the user can configure log and trace settings and gather problem determination data in the runtime environment, see Preferences.

There is just one runtime extension plug-in project in the workspace, and just one version of the plug-in in the runtime environment. Therefore, in any single HATS rich client runtime environment, log and trace settings are the same for all HATS rich client applications.

License settings are also stored in the runtime.properties file of the runtime extension plug-in (com.ibm.hats.rcp.runtime.extension). Therefore license tracking is performed at the rich client environment level and not at the level of an individual HATS rich client application. Warning messages will appear in the log if the user goes over the number of licenses purchased. For information about specifying license settings, see Enabling HATS runtime and license settings.