Gateway Server - Audit Trail

When I discuss Siebel Audit Trail in my classes, a frequent question is: "Does it work with the server configuration views?".

I answer this question as follows:

You can try to add the (virtual) business components to the Audit Trail Administration but you would be disappointed with the result. But there's some hope: The built-in Audit Trail for the Siebel Gateway Name Server (and it has nothing to do with the "real" Audit Trail).

This feature is officially documented in the Siebel 8.1 bookshelf and really straightforward. So here is an abstract.

In the gateway.cfg file's [InfraNameServer] section, set the EnableAuditTrail parameter to True (should be default anyway).

With this setting, "most (so says bookshelf) logins, modifications, writes and deletions are logged" to a file named nameserver_audit.log which by its nature resides in the log subdirectory of the Siebel Gateway Name Server installation folder.

This means that we are able to capture all login attempts to the Siebel Gateway Name Server. This could be from the srvrmgr command line utility or from the server admin screens in the Siebel client.

In addition, each modification to the enterprise configuration such as changing parameter settings are logged.

Let's have a look at the file:

It's a tab separated text file with the following columns:

• Timestamp for the audit entry
• Record Type such as "Clientconnect" or "WriteRecord"
• Host name
• Process Id
• Client name such as srvrmgr, siebsess or siebmtsh
• User name
• Key name (the entry in siebns.dat which has been modified during a WriteRecord event)
• Value (the new value of the key)

have a nice day

@lex