By configuring JP1/Software Distribution for automated storage, you can ensure that the latest operation information is available any time a problem occurs. This setup is also useful in that it allows you to perform regular monitoring of the latest operation information. Even though automatically stored operation information is removed from the database after a specified retention period has elapsed, you can still execute a command to re-store the lost information for viewing.

The following explains the settings and user actions during JP1/Software Distribution operation in order to use automated storage.

Settings

Make the following settings on the Operation Monitoring page during setup.

• Select the Save the operation monitoring history check box.
• Select the Store the operation monitoring history in the JP1/SD database check box.
• Select the Enable automatic storage check box.

For details about setup, see 4.2.14 Operation Monitoring page in the Setup Guide.

During operation

Operation information is automatically stored and deleted, so no user action is required during JP1/Software Distribution operation. If necessary, however, you can use the dcmmonrst command to store or delete operation information to or from the database.

For details about the dcmmonrst command, see 4.13 dcmmonrst.exe (storing operating information in a database) in the manual Administrator's Guide Volume 2.

Even if the monitoring timing and period have not been predetermined, you can still monitor operation information as needed over a desired period of time by means of command execution.

The following explains the settings and user actions during JP1/Software Distribution operation in order to use non-automated storage.

Settings

Make the following settings on the Operation Monitoring page in the setup.

• Select the Save the operation monitoring history check box.
• Select the Store the operation monitoring history in the JP1/SD database check box.
• Select the Compress and move the operation history to the storage directory radio button.
• Clear the Enable automatic storage check box.

For details about setup, see 4.2.14 Operation Monitoring page in the Setup Guide.

During operation

You can use the dcmmonrst command to store or delete operation information to or from the database.

In the Embedded RDB environment, you must use the netmdb_reclaim.bat command to release the area after you delete operation information.

For details about the dcmmonrst command, see 4.13 dcmmonrst.exe (storing operating information in a database) in the manual Administrator's Guide Volume 2.

When you want to manually store operation information, you can use data partitioning, which is a facility of Microsoft SQL Server 2012, Microsoft SQL Server 2008 or Microsoft SQL Server 2005, to store operation monitoring history.

Large users

If the number of operation information items generated per day exceeds 10 million, we recommend that you create a data partition for each day to store the information.

Mid-size users

If the number of operation information items generated per month exceeds 10 million, we recommend that you create a data partition for each month to store the information.

Small users

Data partitions are not required in the following cases:

• The types of operation logs to be collected from the user are limited, and the number of operation logs to be managed is around several million.
• The number of users to be managed is small, and the number of operation logs to be managed is around several million per month.
• For users whose operation logs do not need to be managed, no data partitions are required.

Dividing a partition and locating the resulting partitions on multiple disks provides the following benefits:

• File input/output can be distributed.
• Index maintenance, database backup, and database restoration can be performed by partition.

Note that you need an operating procedure to reconfigure the partition to enable new data to be stored by stopping the system on a regular basis.

When you need to search for information in the operation monitoring history

Dividing a partition might weaken the search performance. Several cases are described below, using a search from the Operation Log List window as an example: one case in which search performance improves, and two cases in which search performance may deteriorate.

Case in which search performance improves

Search performance improves if a range within which the partition was divided (a range within a day if the partition was divided by day, or within a month if the partition was divided by month) is specified for the search period in the Operation Log List window.

Cases in which search performance may deteriorate

• When no search period is specified
• When the jamTakeOperationLog.bat command is executed to output all search results

When you need to delete unnecessary operation monitoring history

Using the dcmmonrst command for deletion purposes might take a long time. In this case, you can quickly delete data by converting all unnecessary monitoring history into tables to be deleted at once, and deleting those tables.