XYGATE Merged Audit Reference Manual

XYGATE Merged Audit
®
Reference Manual
Chapter 6. Configuring MOVERs
XYPRO Technology Corporation 134 Proprietary and Confidential
The MOVER Serverclass XAC-NODE1-HIST will process all audit records dated from
January 1, 2007 through March 31, 2007. The MOVER Serverclass XAC NODE1-01
will process all audit records starting with data from April 1, 2007.
Note: When gathering historical data, it is suggested that you set the parameter
BLOCKALERTS to ON. Otherwise, the MOVERs would be generating ALERTS
for ACTIONS that may have taken place months ago. Records that would have
generated an ALERT will be marked with a ‘B’ in the column ALERT in the
AUDIT DETAIL Table.
6.11 Troubleshooting MOVER Problems
If a MOVER abends because the data tables fill up, you must use CLEANUP or
ARCHIVE to remove some of the old data and then do a FUP RELOAD to regain the
space. You should consider increasing the size of the data tables and/or retaining old
records for a shorter time period. Refer to Chapter 8, “Maintaining the XMA Database”
starting on page 145 for more information.
If a MOVER abends because of a TMF error, you must resolve the TMF issue(s) and
then restart the MOVER(s). If a number of MOVERs are involved, it may be easier to
stop and restart the pathway, which will restart all the MOVERs at once.
If a remote MOVER abends because of an EXPAND error, you must resolve the
EXPAND issues and then restart the MOVER. If a number of MOVERs are involved, it
may be easier to stop and restart the pathway, which will restart all the MOVERs at
once.
If you status a MOVER and the status is “Waiting for work”, the MOVER is probably
unable to read its target product’s audit log. Review the security of the product’s audit
logs to be sure the XMA owner has Read access. Refer to section 7.5, “Safeguard
EMS Error Messages” starting on page 143 for more information.