Bryan,
I don’t know about wM 4.6, but in 6.0.1 and above, there’s a service called wm.tn.archive:archive that will not only take care of archiving the ACTIVITYLOG table, but also other TN-related tables, such as BizDoc, BizDocContent, BizDocAttribute, BizDocRelationship, BizDocUniqueKeys, ActivityLog, DeliveryJob, and EDITracking.
Now, the one thing that this service does not account for are ACTIVITYLOG records that do not contain related documents. To account for those records, I created a JDBC adapter service that runs right after wm.tn.archive:archive and executes the following SQL:
DELETE FROM ACTIVITYLOG
WHERE RELATEDDOCID IS NULL
AND ENTRYTIMESTAMP < SYSDATE-?
Where ? is an input to the service representing the number of days to keep.
If you wished, you could change this statement to insert the data into ARCHIVE_ACTIVITYLOG instead of just deleting it.
Thanks,
Percio
#Integration-Server-and-ESB#B2B-Integration#webMethods