Help topic contents |
After you complete the installation process
described in Configuring the Archive Utility, you are ready to
use the Archive Utility. This help topic explains the following aspects of using the
Archive Utility:
|
||||||||||
Configuration options |
Before you can archive data, you must configure the Archive Utility with the appropriate information. The following information must be specified: | ||||||||||
Tivoli Problem Management configuration |
To properly archive data, the Archive Utility
must access the correct Tivoli Problem Management database tables. You should verify that the Tivoli Problem Management version and database information displayed in the Tivoli Problem Management Archive Utility window are correct. If the Tivoli data source that is listed is not the Tivoli Problem Management production data source, then:
|
||||||||||
Where data is to be archived |
Before you can archive data, you must specify a
destination for the archived items. You can choose from the following three options:
If you choose to archive data to a flat file, each line in the file represents one record from a table. To archive to a flat file, you must specify the file in which to archive data. Refer to APIs Used With the Archive Utility for more information about flat files. If you choose to archive to a database, archived data is stored in archive tables in the default database. The default database is identified as the Tivoli Data Source in the Tivoli Problem Management Archive Utility window. To archive to a database, the destination database tables must already exist. Refer to Creating destination database tables for more information on creating archive tables. If you choose to delete data, all archived items are deleted. They are not copied to a flat file or to an archive database table. Caution: If you choose this option, you cannot retrieve the deleted data for any purpose! |
||||||||||
Dates of data to be archived |
An archived item can be any problem or
information call with a "closed" status. The closed status of these problems and
calls is assigned on a particular date. To indicate which data items are to be archived,
you specify the range of dates during which the items to be archived were designated as
closed. Note that the dates you specify are inclusive. That is, the problems that are archived include those that were designated as closed on the starting and ending dates. |
||||||||||
Items to be archived |
In order to perform an archiving procedure, you
must specify the number of items to be archived. Items can consist of multiple records in multiple tables. For example, an information call consists of one CALL and one or more SESION records. If you first specify the archiving dates, you can use the Estimate function to determine how many items exist to be archived within the given range. Estimate calculates the number of items to be archived, and displays the result in the Total Items to Archive box. This is a useful function when you are unsure of the number of data items to be archived, or when you need to limit the number of items to be archived. If the number calculated by Estimate is too high, you can narrow the range of dates or specify a lower number of items. If you are running the Archive Utility for the first time, it may be useful to use different number values to determine the amount of time required to archive data at your site. You can use different values in both the Commit Size and Total Number of Items text boxes to test performance at your site. |
||||||||||
Commit size |
You must specify the commit size for the
archiving procedure. Commit size refers to the number of items to be archived before a database "commit" is executed. This number should be considerably less than the value of the rollback segment because an item consists of multiple CALL, SESION, WORK_HISTORY, PROBLEM_HISTORY, and PROBLEM records. By default, the commit size is 50 items. Commit size and rollback segments should be configured for high volume data transfer. Refer to the database documentation for your site to confirm the commit size and rollback segments that your database uses. This value should only be modified if authorized by a database administrator. |
||||||||||
Compatibility with Tivoli Problem Management |
Because the Archive Utility works with Tivoli
Problem Management data, modifications or customizations to Tivoli Problem Management may
affect the Archive Utility. When you modify Tivoli Problem Management, you must ensure
that the Archive Utility is compatible with those modifications. The following Tivoli Problem Management modifications require you to alter the Archive Utility for use with Tivoli Problem Management data:
The following sections describe the steps to take to maintain Tivoli Problem Management compatibility after each of these modifications. |
||||||||||
Tivoli Problem Management customizations |
If you archive to a database and you have
customized any of the following tables in the Tivoli Problem Management database, you must
customize the Archive Utility to reflect those changes:
Customizing the archive tables involves two separate steps:
Before installation, the simplest way to customize the archive database tables is to modify the scripts that build the tables. After installation, however, re-running build scripts destroys all data in the tables. Instead, you should make the necessary customizations directly to the archive database tables themselves. Refer to the documentation for your DBMS for more information on customizing database tables. |
||||||||||
When to modify eaacust.kb |
Each of the Tivoli Problem Management tables
used by the Archive Utility corresponds to a procedure in the eaacust.kb file. The
procedure names are listed below. The name of each procedure includes the name of the
table to which it corresponds.
If you have customized any of these tables in Tivoli Problem Management, you must modify the corresponding procedure entry in the eaacust.kb file. |
||||||||||
String or integer data |
Depending on the type of data you added to the
Tivoli Problem Management table, you need to use a different procedure to define the new
field in the eaacust.kb procedure.
The AddStr and AddNonStr procedures take the same parameters: ( VAL Wrap : STRING, VAL Delmtr : STRING, REF str : STRING, VAL newstr : STRING) Descriptions of the parameters follow:
Refer to APIs Used With the Archive Utility for a description of each of the file export characters to use as arguments for these parameters. For example, if you added a column to an Tivoli Problem Management table, you must add a new line to the procedure in eaacust.kb which corresponds to the additional column. Suppose you added a Problem_Code field to the PROBLEM_HISTORY table in Tivoli Problem Management in order to track the changes to problem codes. You must then add a new line to the EAProblem_History procedure in eaacust.kb which corresponds to the Problem_Code field. Because problem codes are strings, the line you add to define the new Problem_Code field in the EAProblem_History procedure looks like this: AddStr( STD, DELM, str, ph.problem_code); |
Configuring and running the Archive Utility |
The following steps provide a guideline for
using the Archive Utility.
|
||||||||||||
Running the Archive Utility on multiple machines |
It may be advisable to run the Archive Utility
on more than one machine at various times. Choosing to use more than one machine may be a
function of:
To run the Archive Utility on multiple machines simultaneously, you need to:
|
||||||||||||
Dropping tables after the Archive Utility runs |
You may want to consider dropping the tables
used for the Archive Utility after the utility runs. Dropping tables saves considerable
space on the data source. Caution: If the data in dropped tables is required for future use, back up the archive tables before you drop them. To drop the tables created for use with the Archive Utility, choose the script that corresponds to your database server and run it with TSD Build.
Refer to the Tivoli Service Desk Installation Guide for more information on using TSD Build. |
||||||||||||
Modifying archive tables for use with DDM |
If you archive to a database, and you install
DDM for use with Tivoli Problem Management, you must ensure that the archive tables are
compatible with DDM. If you install DDM after the Archive Utility is installed and the archive tables are created, you can alter the tables for use with DDM by running an .alt script file which corresponds to your DBMS. You must not run any build scripts (.tab scripts) for this purpose. Doing so destroys any data currently present in the archive tables. Follow these steps to modify the archive tables for use with DDM:
|
||||||||||||
Editing eaacust.kb |
The following procedure describes how to edit
eaacust.kb:
|