Deleting audit log entries, using administrative commands

Use the administrative commands to delete some or all audit log entries.

Before you begin

Before you begin this procedure, the following conditions must be met:
  • The user ID that you are using must have administrative rights.
  • The application server through which audit log entries are to be deleted must be running. That is, the -conntype none option of wsadmin cannot be used, because a server connection is required.
  • When security is enabled, you must have operator authority.

Why and when to perform this task

You can use the deleteAuditLog.jacl script to delete audit log entries from the database.

Steps for this task

  1. Change to the Business Process Choreographer utilities directory where the scripts are located.
    On Windows® systems, enter:
    cd install_root\ProcessChoreographer\util
    On UNIX® and Linux® systems, enter:
    cd install_root/ProcessChoreographer/util
  2. Delete the entries in the audit log table.
    On Windows systems, enter one or more of the following commands. The differences between the commands are emphasized:
    install_root\bin\wsadmin -f deleteAuditLog.jacl 
                             -server serverName
                             [-profileName profileName]
                             [options]
    
    install_root\bin\wsadmin -f deleteAuditLog.jacl 
                             -node nodeName
                             -server serverName
                             [-profileName profileName]
                             [options]
    
    install_root\bin\wsadmin -f deleteAuditLog.jacl 
                             -cluster clusterName
                             [-profileName profileName]
                             [options]
    On UNIX and Linux systems, enter one or more of the following commands. The differences between the commands are emphasized:
    install_root/bin/wsadmin.sh -f deleteAuditLog.jacl 
                             -server serverName
                             [-profileName profileName]
                             [options]
    
    install_root/bin/wsadmin.sh -f deleteAuditLog.jacl 
                             -node nodeName
                             -server serverName
                             [-profileName profileName]
                             [options]
    
    install_root/bin/wsadmin.sh -f deleteAuditLog.jacl 
                             -cluster clusterName
                             [-profileName profileName]
                             [options]

    Where:

    cluster clusterName
    The name of the cluster. Required if the business process container is configured for a WebSphere® cluster.
    node nodeName
    Optional when specifying the server name. This name identifies the node. The default is the local node.
    server serverName
    The name of the server. Required if the cluster name is not specified.
    profileName profileName
    The name of a user-defined profile. Specify this option if you are not working with the default profile.

    The available options are:

    -all
    Deletes all the audit log entries in the database. The deletion is done in multiple transactions. Each transaction deletes the number of entries specified in the slice parameter, or the default number.
    -time timestamp
    Deletes all the audit log entries that are older than the time you specify for timestamp. The time used is coordinated universal time (UTC). Its format must be: YYYY-MM-DD['T'HH:MM:SS]. If you specify only the year, month, and day, the hour, minutes, and seconds are set to 00:00:00.

    The -time and -processtime options are mutually exclusive.

    -processtime timestamp
    Deletes all the audit log entries that belong to a process that finished before the time you specify for timestamp. Use the same time format as for the -time parameter.

    The -time and -processtime options are mutually exclusive.

    -slice size
    Used with the -all parameter,size specifies the number of entries included in each transaction. The optimum value depends on the available log size for your database system. Higher values require fewer transactions but you might exceed the database log space. Lower values might cause the script to take longer to complete the deletion. The default size for the slice parameter is 250.

Terms of use | | Broken links

Last updated: Tue Dec 06 04:14:42 2005

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