Audit logging for business rules and selectors

You can set up WebSphere Process Server to automatically log any changes made to business rules and selectors.

With WebSphere® Process Server version 6.0.2, you can configure your server to automatically detect when changes are made to business rules and selectors, and create an entry in a log file detailing the changes. You can choose to have the log entries written to either the standard JVM SystemOut.log file, or to a custom audit log file of your choice. Depending on how the changes are made, the process server where each business rule or selector change is made will log the:
The business rule and selector objects are the complete business rule set, decision table, business rule group, or selector for both the business rule or selector that is replaced and the new version which replaced it. You will have to examine the logs (the audit output cannot be directed to the Common Event Infrastructure database) to determine the changes that were made, by comparing the old and new business rules or selectors. The following scenarios describe the circumstance when logging occurs, if it has been configured, and the contents of the log entry:
Scenario Result Log entry contents
Publish business rules using the Business Rule Manager Request User ID, Server name (including Cell and Node, if applicable), old business rule ruleset, new ruleset.
Failure User ID, Server name (including Cell and Node, if applicable), old business rule ruleset, new ruleset.
Repository database update and commit (from attempt to publish using the Business Rule Manager) Success User ID, old ruleset, new ruleset.
Failure User ID, new ruleset.
Exporting a selector or business rule group Request User ID, selector or business rule group name.
Success User ID, Server name (including Cell and Node, if applicable), copy of exported selector or business rule group
Failure User ID, Server name (including Cell and Node, if applicable), selector or business rule group name.
Importing a selector or business rule group Request User ID, copy of new selector or business rule group.
Success User ID, Server name (including Cell and Node, if applicable), copy of imported selector or business rule group, copy of selector or business rule group that was replaced by the imported version.
Failure User ID, Server name (including Cell and Node, if applicable), copy of selector or business rule group that was to be imported.
Application install Success User ID, Server name (including Cell and Node, if applicable), selector or business rule group name.
Failure User ID, Server name (including Cell and Node, if applicable), selector or business rule group name.
Application update (through the administrative console or wsadmin command) Success User ID, Server name (including Cell and Node, if applicable), copy of new selector or business rule group, copy of old selector or business rule group.
Failure User ID, Server name (including Cell and Node, if applicable), copy of new selector or business rule group
Previously deployed application with existing business rules, selectors or both is started Success Server name (including Cell and Node, if applicable), copy of selector or business rule group.
Failure Server name (including Cell and Node, if applicable), copy of selector or business rule group.
Related concepts
Viewing and interpreting service component event log files
Related information
Business rules manager
Overview of business rules and selectors
Configuring the business rule and selector audit log

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)