Quick Installation Guide for Audit Master

Release Date: 09/12/2018

Introduction
Audit Master is an invaluable tool to diagnose problems with Elliott Business Software -- the types of problems that can happen due to users' mistakes or Elliott software bugs.  While Elliott does provide auditing for the changes of certain tables, Audit Master is a comprehensive tool that can audit all data, if necessary, in Elliott. This tool resolves any mysteries surrounding problems and provides guidance on how to resolve issues.

Installation
Download Audit Master from Actian website:
From the top navigation bar, choose "Products" -> "Pervasive PSQL." This will bring you to the following page:
In this page, find "Audit Master" on the left under "Products." This will bring you to the following page:
In this page, you have the choice to download the following Audit Master versions:
  • Audit Master 13 - Works with PSQL 13
  • Audit Master 12 - Works with PSQL 12
  • Audit Master 8 - Works with PSQL 11
Depending the version of your PSQL, download the corresponding Audit Master.  Once you download the EXE.  Run it on your PSQL server console.  Use the default settings to install.

Create Schema by Importing Elliott DDF
Startup AM Schema Maintenance Wizard. Choose Import Wizard and use the following information:


Enter the following information in the dialog window "Specify the Product Information":


Enter the version that matches your current Elliott version.  Please be aware that there is a bug that exists where if you enter the "Version" field as "V8.2," then the AM advanced search feature won't work. You need to enter the lower case "v8.2" or simply "8.2" to avoid this problem.

Next, you need to identify where the Elliott DDF resides.  Browse to your Elliott folder as follows:
    <ElliottRoot>\Bin\DDF40

Click Next to create the Schema.

Configure Audit Master
After successfully importing Elliott’s schema, start up Audit Master Viewer. Expand the server node, and enter the “Admin” user.  Since this document is intended for admin users only, you need to call Netcellent for the password. Once you've logged in, choose menu item “Admin” -> “Audit Configuration.”  Right click “Elliott Business Software” and choose “New Configuration.”  Then choose the drive where you have Elliott installed, and “8.2” for the version. See sample screen below:


Click "Add Group" and enter the Group Name to match your company folder -- like "DATA," "DATA_02," "Tutorial"...etc.


In the “Available Files” area, browse to your corresponding data folder, select the files you want to monitor, and add to the “Files to Be Monitored” list. See sample screen below:


Since Audit Master creates a lot of auditing data, you don't want to monitor every single table in Elliott. See the following KB articles for a suggested list of files that you should monitor:

Now close it and you will receive the message “Please close AuditMaster and restart all PSQL services for the changes to take effect.”  

But before you do that, you should also make the following changes by going to “Admin” -> “Server Settings.”  Since Audit Master takes a lot of data, we recommend that you to go to “Archives To Keep" and change it from “-1” to “10.” Keep in mind that, by default, Audit Master stores auditing data on your C: drive.  You may change this to a larger number if you have enough disk space.  Also, in the Automated Archiving, change the threshold from 75MB to 1024MB. Then click “OK” and confirm the changes.  This implies that the system can use a maximum of (10 + 1) x 1024 MB, which is 11 GB of disk space for storing Audit Master data.

Stop and Start PSQL Services
Now stop both PSQL Relational and Transaction Engine Services and restart them. This will allow the changes you just did in Audit Master setup to take effect.  Your system is now ready to capture data in Audit Master for future auditing purposes.

Using Audit Master Viewer
For a quick user guide on how to use Audit Master Viewer to explore the captured data, please see the following KB article:


EMK

Pervasive PSQL

  1. Btrieve Error Codes 001 - 199
  2. Btrieve Error Codes 3000 - 3099
  3. Btrieve Error Codes 3100 - 3199
  4. PSQL Version Required by Each Elliott Version
  5. Do I Need to Change PSQL Server Engine Default Parameters After Installing It?
  6. New Elliott PSQL Server Processor and RAM Suggestions
  7. Can I Dynamically Adjust Elliott / PSQL 11 Server Memory?
  8. Received "Your Computer Does Not Have PSQL 10 or 11 Client " Even though PSQL Client Is Just Installed
  9. Btrieve Error 161 on Password File When Starting Up Elliott
  10. Problems with Using Pervasive Rebuild Utility on APOPNFIL and AROPNFIL Tables
  11. Security Issue with Installing PSQL Client Remotely on User's Workstation
  12. PSQL and Distributed File System (DFS)
  13. How Do I Turn on PSQL Relational Engine Security?
  14. An Example of Debugging NOTE_ORD_VIEW PSQL Expression Evaluation Error
  15. Btrieve Error 025 on COP Open Order by Salesman Report
  16. What Is the *.^01 File for My PSQL Btrieve Table?
  17. Suggested Files to be Monitored by Audit Master
  18. Pervasive Backup Agent Is Not Compatible with Creating Work Files
  19. Hardware Recommendations for Your PSQL Database Server
  20. How to Optimize SQL SELECT Statement When Retrieving Data from Invoice History
  21. New User-Defined Functions in Elliott DDF
  22. How to Improve Query Performance When Retrieving Data from Notes & Invoice History
  23. How to Retrieve Tracking Number for an Order from Notes
  24. Actian PSQL Not Started Automatically After Server Reboot
  25. Create a New Database in the PCC for Relational Engine Access
  26. Slow PSQL Relational Engine Performance
  27. IPV6 May Cause Problem for PSQL 11 Relational Query
  28. DDF Files in DATA Folder May Confuse PSQL
  29. What to Do When PSQL 11 License Is Disabled
  30. Quick Installation Guide for Audit Master
  31. Quick User Guide for Audit Master
  32. PSQL 13, Micrsoft SQL Integration Service & Pervasive PSQL OLE DB Provider
  33. Your Firewall Needs to Allow Outbound Traffic to the Netherlands for PSQL Licensing Server Purposes
  34. A Case of Btrieve Error 046 on ARCRCLOG A/R Credit Card Log File
  35. A Support Case of Migrating to Different Version of DDF
  36. How to Clear the Message "Unable to Read your Users record (9/068)"
  37. Setup of the PSQL 13 Report Engine
  38. How to Create CPHSTTRX_VIEW with Left Join to CPINVHDR Due to Invoice Database Archive
  39. How to Access Elliott's Data by Using Query in Microsoft Office Excel 2019
  40. Elliott Database Naming Convention
  41. What Does Btrieve Error 080 Mean?

Feedback and Knowledge Base