This section explains the application process operation log.
Log name | Description |
---|---|
ibpm_audit.log | The log for the application process operation is output. |
To obtain the process instance operation log for the application process, execute the get process instance audit information command.
[Windows Manager]
Installation_folder\RCXCTMG\MyPortal\bin\ibpm_audit
[Linux Manager]
/opt/FJSVctmyp/bin/ibpm_audit
The process instance audit information that can be obtained will be the process instance information that was complete after the command was executed the previous time.
[Windows Manager]
Administrator privileges are required. If the operating system is Windows Server 2008 or later, execute as the administrator.
This command can be executed on the admin server.
[Linux Manager]
System administrator (superuser) privileges are required.
This command can be executed on the admin server.
The log output destinations are shown below:
Log name | Output destination folder | Output destination files |
---|---|---|
ibpm_audit.log | [Windows Manager] Installation_folder\RCXCTMG\MyPortal\log [Linux Manager] /var/opt/FJSVctmyp/log | ibpm_audit[n].log (*) |
*Note: n indicates the number of generations.
The log file size and number of generations are as follow.
Log name | File size | Number of generations (*1)(*2) |
---|---|---|
ibpm_audit.log | 10MB | 10 |
*1: If this number is exceeded, old generations will be deleted, starting with the oldest generation.
*2: If the file size does not reach 10 MB, the log continues to be output to the same file even if the ibpm_audit command is executed multiple times.
Approximately 300 bytes are used for recording each operation for subscription, reconfiguration, or application cancellation of an L-Platform. If necessary, back up the logs at appropriate intervals according to the usage frequency.
Example
When backing up log files for three generations, the names of the files to be backed up are as follows:
ibpm_audit1.log
ibpm_audit2.log
ibpm_audit3.log
Logs are CSV files where the following items are output in the following order.
One item of process instance information is displayed as one record.
"Process instance start time","Process instance starter","Process instance name","Process instance state","Process instance end time","Activity name","Task execution date/time","Person responsible","Status","Task process",...,"Result of application"
Item | Description |
---|---|
Process instance start time | Time when the application was executed |
Process instance starter | User ID of applicant |
Process instance name | Process instance name L-PlatformSubscription_xxx,L-PlatformChange_xxx,L-PlatformUnsubscription_xxx |
State of process instance | State of process instance closed: Closed |
Process instance end time | Time that the process instance ended yyyy-mm-dd hh:mm:ss.sss |
Activity name | Activity name |
Task execution date/time | The date/time the task was executed |
Person responsible | User ID of the user that executed the task |
Status | Shows the state of task COMPLETED: Completed |
Task process | Button name executed by the activity: Application: Apply
|
Result of application | Result of application:
|
The example below shows the output of the audit information for the process instance with the name "L-Platform usage application_100".
"2012-04-11 17:03:53.580","tenant_user001","L-PlatformSubscription_100","closed","2012-04-11 17:04:25.471","Application","2012-04-11 17:03:56.111","tenant_user001","COMPLETED","Apply","Approve","2012-04-11 17:04:15.908","tenant_admin001","COMPLETED","0:Approve","Assess","2012-04-11 17:04:21.346","infra_admin001","COMPLETED","0:Accept","Accepted"
Point
Using an operating system feature such as Task Scheduler (Windows Manager) or cron (Linux Manager), configure the settings so that the get process instance audit information command is executed at fixed intervals so that an operation log of process instances can be obtained between command executions.