XYGATE Merged Audit Reference Manual

XYGATE Merged Audit
®
Reference Manual
Chapter 6. Configuring MOVERs
XYPRO Technology Corporation 126 Proprietary and Confidential
/users/hlr/PS4JQ/: ls
dpa_audit_20101106_000018.log dpa_audit_20101108_083715.log
dpa_audit_20101106_000028.log dpa_audit_20101108_100434.log
dpa_audit_20101106_000101.log dpa_audit_20101108_102121.log
dpa_audit_20101106_000111.log dpa_audit_20101108_104304.log
dpa_audit_20101106_000721.log dpa_audit_20101108_112207.log
dpa_audit_20101106_074444.log dpa_audit_20101108_114526.log
dpa_audit_20101106_091009.log dpa_audit_20101108_115921.log
dpa_audit_20101106_092558.log dpa_audit_20101108_123114.log
dpa_audit_20101106_094241.log dpa_audit_20101108_123442.log
dpa_audit_20101106_100023.log dpa_audit_20101108_130417.log
dpa_audit_20101106_104004.log dpa_audit_20101108_134429.log
dpa_audit_20101106_104208.log dpa_audit_20101108_140019.log
In the example above, PS4JQ is the Application Node ID and dpa_audit_* is the file
mask for the DPA audit log files in that directory.
XYGATEMA will validate that files matching the mask contain data in the expected
format; however, the program cannot validate the path or the NODEID so be careful to
enter the path correctly. If you create a MOVER pointing at the wrong directory, you
will have to delete it and add a new MOVER with the correct path and filemask.
Refer to Appendix G6: “HLR Data Mapping” starting on page 254 for information on
HLR data placement within the XYGATEMA database.
6.6.1 Important Notices!
1. Because of the large size of the HLR audit trails, the HLR MOVER will only update
the XMA database with audit records that match an ACTIVE filter. There are
several sample HLR filters in the FILTSAMP file. In order to gather any HLR data,
you must copy any or all of them to the FILTERS file and set the status to ACTIVE
before you start any HLR MOVERs.
2. Adding HLR audit data to XYGATEMA will greatly increase the size of the
database because each HLR event will generate from one to many rows.
Important! Be sure that you place any XMA databases that will include HLR data
on large disks and “size” the XMA tables accordingly.
3. Because of all the parsing, the MOVER will be very busy; therefore, XYPRO
Technology recommends:
• Lowering the priority of the HLR MOVER to perhaps 60 or 70. Set this when
you add the MOVER.
• Changing the default transaction size to perhaps 300 or 500. Set this after you
add the MOVER but before you start it. Within XMA_MANAGER use Movers
Management Menu, option 12: Alter Database params (page 101), and then
select option 1: Transaction size on the submenu that appears.