Archiving Data
On the Data management page, you can archive obsolete audit data for a specified Retention time period. You must carefully choose the Retention time period, as archiving too much data at once might have negative effects on the database, such as an increased time of the archive operation, locking issues, a large increase of the database size, an increase of the transaction log, and an increase of the temp table size. To avoid these negative effects, for each archive operation, choose the largest retention period possible.
Service Monitoring can archive user-defined messages for a service only if customized logging is set up for the service. If service logging is globally enabled in Integration Server, but customized logging is not set up for the service in Designer, then Service Monitoring cannot archive user-defined messages written by the service.
To archive audit data
1. In the Retention time period area of the screen, specify how long you want to keep the data in the IS Core Audit Log tables. Service Monitoring archives data that is older than the retention period you specify.
The following table describes the data retention options.
Option | Description |
Number of days to retain (including today) | Number of days for which you want Service Monitoring to keep archive data. For example, if you specify 15, Service Monitoring will archive data that is 16 days old or older. |
Retention period start date (including today) | Date of the oldest data to keep. Click the calendar icon and select the date and time. For example, if you specify 6/3/2020 0:00:00, Service Monitoring will keep data from 6/3/2020 until the current date, and will archive data logged before 6/3/2020. |
Note:
Service Monitoring archives services based on their end timestamp, and documents and server data based on the timestamp.
2. Select Data types to archive.
a. Select the check boxes corresponding to the types of data to archive.
The following table describes the types of data.
Select | To archive |
Services | Service log entries, input pipelines, error data, user-defined messages, and service control data (resubmit actions). |
Documents | Logged documents for all webMethods Broker (deprecated) clients and document control data (resubmit actions). If selected, Service Monitoring archives 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 services, activations, and documents). If selected, Service Monitoring archives all server data. |
b. If you want to archive services, select which status to archive.
The following table lists the status options.
Option | Archives or deletes |
Completed | Audit data for services with status Completed. |
Completed-Failed | Data for services with status Completed, Failed, Failed (Escalated), and Resubmitted. |
3. In the Archiving batch size field, indicate the number of primary items and accompanying items to archive at a time.
For example, to archive 100 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 archiving speed.
4. Click Archive and delete.