1.36 Log Access

This topic describes an overview of the different logs and their access.

Customers can access logs based on the access rights set by the system administrator. They can have limited or full access, and they can view, generate, or purge logs accordingly.

Application Logs

The application log consists of the application or the front-end layer logs.

• Application Log path can be configured in the fcubs.properties (Parameter APPLICATION_WORK_AREA) file, at the time of the property file creation.
• Application logs can be enabled/disabled based on the fcubs.properties (Debug = ‘Y’ or ‘N’) file.
• The storage mainly is in the application server. The data controller controls the access to the storage.

The section of the fcubs.properties is shown below:
Description of the illustration application-logs.png

Back-end Logs

Back end log consists of the back end layer debug logs.

• Database directories are created with the back-end debug path by the data controller. Database directory has to be specified at the time of day 0 setup.
• The data controller can give module-wise access to the back-end logs to the user.

Audit Logs

Audit Logs are used to see the history of all changes that have happened. The user can view the changes made along with the Maker ID and Checker ID as well as time stamp information.

In the Customer Maintenance screen, click Change log to view the modification details as follows:

Figure 1-41 Customer Maintenance - Change Log

Description of "Figure 1-41 Customer Maintenance - Change Log"

Purging Logs

Logs are purged in both Application and DB server by the data controller.