Monitor 10.11 | pub.monitor.archive Folder | pub.monitor.archive:serviceArchive
 
pub.monitor.archive:serviceArchive
Archives or deletes service log entries, input pipelines, error data, and user-defined messages from the PRA_ERROR table in the IS Core Audit Log database component and service control data (such as resubmit actions) from the PRA_PROCESS_ACTION table in the Process Audit Log database component.
Note:Monitor can archive user-defined messages for a service only if customized logging is set up for the service in Designer. That is, if service logging is globally enabled in Integration Server but customized logging is not set up for the service in Designer, Monitor cannot archive used-defined messages that a service writes.
Input Parameters
The following table lists the input parameters.
todate
String Optional. Start date for the period to keep the data in the IS Core Audit Log and Process Audit Log database components. The period ends with and includes the current date. Use the format yyyy--mm-dd hh:mm:ss.
Supply either todate or days. Do not supply both.
days
String Optional. Number of days to keep the data in the IS Core Audit Log and Process Audit Log database components, ending with and including the current date.
Supply either todate or days. Do not supply both.
archiveAction
String Indicates whether to archive or delete the data.
*ARCHIVE Default. Copy the data from the IS Core Audit Log and Process Audit Log database components to the Archive database component and delete the data from the and Process Audit Log database components.
*DELETE Delete the data from the IS Core Audit Log and Process Audit Log database components without archiving it first.
status
String Indicates the status for which to archive or delete the data.
*COMPLETED Default. Archive or delete data for services with a status of Completed. Data for services with other statuses is retained in the database.
*COMPLETED-FAILED Archive or delete data for services with a status of Completed, Failed, or Resubmitted. Data for services with a status of other than those specified is retained in the database.
*ALL Archive or delete data for services with any status.
batchSize
String Optional. Number of services to archive or delete at a time.
Output Parameters
The following table lists the output parameters.
message
String Message that indicates the success of the archive or delete action.
errorMessage
String Errors that occurred during the archive or delete action.
Usage Notes
You can use this service with Integration Server Administrator to archive or delete data automatically, at specific times or intervals. To do so, build a wrapper service that calls the archive or delete service and sets its input parameters; then run the wrapper service as a scheduled task from Integration Server Administrator. For instructions on scheduling services to run at specific times, see webMethods Integration Server Administrator’s Guide.
Examples
*todate parameter: Suppose the current date is September 30 and you want to archive or delete data for 4.x activations that finished running more than 15 days ago (that is, before September 15). You would specify this parameter as 2003-10-15 00:00:00.
*days parameter: Suppose the current date is September 30 and you want to archive or delete data for 4.x activations that finished running more than 15 days ago (that is, before September 15). You would specify this parameter as 15.