Archiving or Deleting Audit Data Using the Monitor User Interface

Option	Description
Number of days to retain (ending with today)	Monitor keeps data for the number of days (including the current date) that you specify. For example, if you specify 15, Monitor keeps data that is 15 or fewer days old and archives/deletes data that is 16 or more days old.
Retention period start date (ending with today)	Date of the oldest data to keep. The period ends with and includes the current date. For example, if you specify 6/3/2012, Monitor keeps data from 6/3/2012 through the current date and archives/deletes any data logged before 6/3/2012. Use the calendar picker and hour and minute fields to set the date.

Note:

Processes and services have a start timestamp and an end timestamp; Monitor archives or deletes process based on the end timestamp. Documents and server data have a single timestamp, and Monitor archives or deletes them based on that timestamp.

Select...

To archive...

Processes

For the process model or models selected, Monitor archives or deletes:

Process log entries, input pipelines, error data, and run-time values for user-specified input and output document fields.

Referenced processes, process-related service data (services, service error data, and user-defined messages).

Process control data (resubmit, suspend, and resume actions).

Services

Service log entries, input pipelines, error data, user-defined messages, and service control data (resubmit actions).

Note:

Monitor can archive user-defined messages for a service only if customized logging is set up for the service. That is, if service logging is globally enabled in Integration Server, but customized logging is not set up for the service in Designer, then Monitor cannot archive user-defined messages written by the service.

Documents

Logged documents for all webMethods Broker clients and document control data (resubmit actions). If selected, Monitor archives or deletes all logged documents.

Server Data

Integration Server session and guaranteed delivery log entries, and error log entries that are not associated with logged processes, services, or documents (for example, errors that occur during startup or during the run of unlogged processes, services, activations, and documents). If selected, Monitor archives or deletes all server data.

Note:

You can only archive by process model name when Monitor uses stored procedures to perform archiving. When Monitor is configured to use JDBC pools, all process models are archived.

Option	Archives or deletes...
Completed	Audit data for processes or services with a Completed status.
Completed-Failed	For services. Data with the status, Completed, Failed, Failed (Escalated), and Resubmitted. For processes. Data with the status, Completed, Failed, Stopped, and Resubmitted.

Note:

You can only choose the status when archiving or deleting processes and services. Documents and Integration Server data do not have statuses and therefore cannot be archived selectively.

4. In the Archiving Batch Size field, indicate the number of primary items and accompanying items to archive or delete at a time. For example, to archive or delete 100 processes and accompanying services, activity logs, and errors at a time, choose a number that takes the size of each record and other performance factors into consideration. If the record size is large, consider reducing the batch size; if the record size is small, increasing the batch size might increase the speed of the archive or delete.