Configuring business rule and selector auditing using commands

Use commands to configure business rule and selector auditing when you need to change any of the characteristics while a server is running.

Before you begin

These commands must be run from a command line environment for the server.

Why and when to perform this task

There may be occasions when you need to change how many servers audit business rules and selectors and cannot restart the servers involved. Using the command line, you can automate configuring the servers in a batch mode. The following procedures shows how to use commands to configure one server.
Important: These settings are not saved if you restart the server. To save the configuration after entering these commands, you must use the administration console. (Servers > Applications servers > servername > Business Integration > Business Rules > Business Rules and Selectors Auditing > Runtime or Servers > Applications servers > servername > Business Integration > Selectors > Business Rules and Selector Auditing > Runtime)
Note: The following procedure configures server server1. All of the steps beginning at step 2 could be placed in a jacl script and run that way.

Steps for this task

  1. Enter the administrative environment.

    wsadmind

  2. Decide whether you are configuring audit logging or changing an existing configuration.
    Task Command
    Configuring audit logging set mbean [$AdminControl queryNames *:*,name=CustomizationAuditMBean,process=server1]
    Changing audit logging configuration set auditconfig [$AdminConfig list AuditLog]
  3. Enter the appropriate commands.

Commands to configure or change audit logging

Commands to configure or change audit logging

Important: When entering commands that change an existing configuration, you must save the changes and the changes do not take effect until you restart the server.
The following are the commands you can enter.
$AdminControl invoke $mbean getSeparateAuditLogEnabled
Use to determine whether logging is occurring to a separate audit log.
$AdminControl invoke $mbean setSystemOutAuditLogEnabled {boolean}
Use to enable or disable logging to SystemOut.log file. Boolean can either be true or false.
$AdminControl invoke $mbean getSeparateAuditLogFileName
Use to determine the filename of the separate audit log.
$AdminControl invoke $mbean setSeparateAuditLogFileName {filename}
Use to set the name of the new log file, for example MyAudit.log.
$AdminControl invoke $mbean getSeparateAuditLogFileRolloverSize
Use to determine the size of the audit log.
$AdminControl invoke $mbean setSeparateAuditLogFileRolloverSize integer
Use to set the size of the audit log before the system rolls it over into a history file. The size is in megabytes.
$AdminControl invoke $mbean getSeparateAuditLogFileMaxNumberOfBackupFiles
Use to determine the number of audit log history files.
$AdminControl invoke setSeparateAuditLogFileMaxNumberOfBackupFiles integer
Use to set the number of audit log history files.
$AdminControl invoke $mbean setSeparateAuditLogEnabled {boolean}
Use to start or stop logging to a separate log file. Boolean can either be true or false.
$AdminConfig showall $auditconfig
Use to show the current audit log configuration.
$AdminConfig modify $auditconfig {{separateAuditLogEnabled true}}
Use to enable logging to a separate audit log.
$AdminConfig modify $auditconfig {{systemOutAuditLogEnabled false}}
Use to disable auditing to the system.Out file.
$AdminConfig modify $auditconfig {{customAuditLog {{maxNumberOfBackupFiles 7} {rolloverSize 7}}}}
Use to change the number of audit log history files and the size of the audit log file.
$AdminConfig modify $auditconfig {{customAuditLog {{fileName MyAudit.log}}}}
Use to change the name of the audit log file.
$AdminConfig save
Use to save the configuration.

What to do next

If you want to save these changes, go to the administrative console (Servers > Applications servers > servername > Business Integration > Business Rules > Business Rules and Selectors Auditing > Runtime or Servers > Applications servers > servername > Business Integration > Selectors > Business Rules and Selector Auditing > Runtime) or enter $AdminConfig save.
Related concepts
Installing the business rules dynamic repository for a stand-alone server
Installing the business rules dynamic repository for network deployment
Considerations for modules containing business rules and selectors
Overview of business rules
Business rules manager
Overview of selector components
Related tasks
Configuring the business rule and selector audit log

Last updated: Wed 06 Dec 2006 07:08:08

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