AUDIT LOG FILE IN DATASTAGE

Audit events are recorded in the audit log file on the DataStage Server Services tier. Logging in to or out of any InfoSphere Information Server client application or command-line tool logs events.

Audit events are logged for managing the users, groups, or security roles in the InfoSphere Information Server console, InfoSphere Information Server Web console.

Where audit file will be created?

Audit log file will be created in the logs directory of the InfoSphere Information Server profile in IBM WebSphere Application Server.

The default location is Websphere\AppServer\profiles\InfoSphere\logs with the name ISauditLog_0.log.

For example, if DataStage is installed on unix, audit log file will be created in /opt/IBM/Websphere/AppServer/profiles/InfoSphere/logs directory.

ISauditLog-Path-datastage

If the logs directory does not exist, the audit log file is created in the directory of the application server where InfoSphere Information Server is installed.

Log file sizing:

The log file size and the number of log files to keep are based on the settings in the audit configuration file.

With the default values of audit.file.size=10000000 and audit.file.count=5, when the file grows to approximately 10 million bytes, it is renamed to ISauditLog_1.log.

A new ISauditLog_0.log file is created to hold the most recent audit events. Up to five files can be created, at which time, when the current ISauditLog_0.log file exceeds the size limit of 10 million bytes, the oldest log is deleted, the other files are renamed, and a new file with generation number 0 is created.

The higher the generation number of the file, the older the audit events.

audit-log-files-size-limit

If you see here, DataStage created a new log file whenever log file reached 10 million bytes and 4 log files created so far and 5th audit log file is being written.

Sample Audit Log:

audit-log-sample-datastage

As mentioned earlier, each audit even will be recorded as a line in this file. Above lines are example for login activity and others also will be logged in this way.

Logout and session terminations:

logout-session-audit-log

Session expiry samples:

session-expired-audit-log-sample

We can use this audit log file to capture current users who are all logged into DataStage designer, director and web console components. This can be captured using a shell script and anyone can automate this process to manage the user logins.

 

Comments

comments

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: