What data requires management?

The Blueworx Voice Response data in /usr/lpp is static, and does not require any management. The Blueworx Voice Response data in /home/dirTalk is dynamic. This is data you generate every time you use Blueworx Voice Response. (As part of the installation process, the directories in /home/dirTalk may have been moved to a different file system. If so, the values of variables in the profile for the Blueworx Voice Response AIX account ID such as $CUR_DIR and $ARC_DIR are set to the new path so that Blueworx Voice Response, and you, can find the data.) Also used to store data is /var/dirTalk—in particular /var/dirTalk/DTBE is used for Java data.

Table 1. Data and how it is managed

Type of Data

Examples

How Created and Managed

Licensed Program Product (LPP) files

AIX, Blueworx Voice Response, Communication Server, and so on

Created by the installation process.

Requires backing up (see Making backup copies of files).

Blueworx Voice Response error logs and trace files

Initialization and termination messages, error messages, and trace entries

Created automatically and managed mostly by Blueworx Voice Response.

Some management of history files can save disk space (see Managing Blueworx Voice Response error logs and trace files).

Blueworx Voice Response configuration data

System parameter values, 3270 sessions, administrator profiles, and so on

Managed by you (see Making a backup copy of system parameter values).

Voice application objects

State tables, prompts, voice segments, 3270 servers, custom servers, application profiles, voice messages, and other voice messaging resources

Created and managed by you (see the Designing and Managing State Table Applications information for background information; see also Removing voice messages from mailboxes).

Blueworx Voice Response and application statistics

Statistics data, reports, logs, and archives

Created automatically and managed by you (see Reports, logs, archives, and statistics).