홈
제품
Red Hat Process Automation Manager
7.10
Developing process services in Red Hat Process Automation Manager
Chapter 13. Managing log files

이 콘텐츠는 선택한 언어로 제공되지 않습니다.

Chapter 13. Managing log files

Red Hat Process Automation Manager manages the required maintenance, runtime data that is removed, including:

Process instance data, which is removed upon process instance completion.
Work item data, which is removed upon work item completion.
Task instance data, which is removed upon completion of a process to which the given task belongs.

Runtime data, which is not cleaned automatically includes session information data that is based on the selected runtime strategy.

Singleton strategy ensures that runtime data of session information is not automatically removed.
Per request strategy allows automatic removal when a request is terminated.
Per process instances are automatically removed when a process instance is mapped to a session that is completed or aborted.

In order to keep the track of process instances, Red Hat Process Automation Manager provides audit data tables. There are two ways to manage and maintain the audit data tables, including cleaning up the jobs automatically and manually.

13.1. Setting up automatic cleanup job
링크 복사

You can set up an automatic cleanup job in Business Central.

Procedure

In Business Central, go to Manage > Jobs.
Click New Job.
Enter values for Business Key, Due On, and Retries fields.
Enter the following command into the Type field.
```
org.jbpm.executor.commands.LogCleanupCommand
```
To use the parameters, complete the following steps:
For full parameters list, see Section 13.3, “Removing logs from the database”.
1. Open the Advanced tab.
2. Click Add Parameter.
3. Enter a parameter in the Key column and enter a parameter value in the Value column.
Click Create.

The automatic cleanup job is created.

13.2. Manual cleanup
링크 복사

To perform manual cleanup, you can use the audit API. The audit API is divided into the following areas:

Expand

Table 13.1. Audit API areas
Name	Description
Process audit	It is used to clean up process, node and variable logs that are accessible in the `jbpm-audit` module. For example, you can access the module as follows: `org.jbpm.process.audit.JPAAuditLogService`
Task audit	It is used to clean up tasks and events that are accessible in the `jbpm-human-task-audit` module. For example, you can access the module as follows: `org.jbpm.services.task.audit.service.TaskJPAAuditService`
Executor jobs	It is used to clean up executor jobs and errors that are accessible in the `jbpm-executor` module. For example, you can access the module as follows: `org.jbpm.executor.impl.jpa.ExecutorJPAAuditService`

13.3. Removing logs from the database
링크 복사

Use LogCleanupCommand executor command to clean up the data, which is using the database space. The LogCleanupCommand consists of logic to automatically clean up all or selected data.

There are several configuration options that you can use with the LogCleanupCommand:

Expand

Table 13.2. LogCleanupCommand parameters table
Name	Description	Is Exclusive
`SkipProcessLog`	Indicates whether process and node instances, and process variables log cleanup is skipped when the command runs. The default value is `false`.	No, it is used with other parameters.
`SkipTaskLog`	Indicates if the task audit and event log cleanup are skipped. The default value is `false`.	No, it is used with other parameters.
`SkipExecutorLog`	Indicates if Red Hat Process Automation Manager executor entries cleanup is skipped. The default value is `false`.	No, it is used with other parameters.
`SingleRun`	Indicates if a job routine runs only once. The default value is `false`.	No, it is used with other parameters.
`NextRun`	Schedules the next job execution. The default value is `24h`. For example, set to `12h` for jobs to be executed every 12 hours. The schedule is ignored if you set SingleRun to `true`, unless you set both SingleRun and NextRun. If both are set, the NextRun schedule takes priority. The ISO format can be used to set the precise date.	No, it is used with other parameters.
`OlderThan`	Logs that are older than the specified date are removed. The date format is `YYYY-MM-DD`. Usually, this parameter is used for single run jobs.	Yes, it is not used with `OlderThanPeriod` parameter.
`OlderThanPeriod`	Logs that are older than the specified timer expression are removed. For example, set `30d` to remove logs, which are older than 30 days.	Yes, it is not used with `OlderThan` parameter.
`ForProcess`	Specifies process definition ID for logs that are removed.	No, it is used with other parameters.
`ForDeployment`	Specifies deployment ID of the logs that are removed.	No, it is used with other parameters.
`EmfName`	Persistence unit name that is used to perform delete operation.	Not applicable

Note

LogCleanupCommand does not remove any active instances, such as running process instances, task instances, or executor jobs.

이 콘텐츠는 선택한 언어로 제공되지 않습니다.

Chapter 13. Managing log files

13.1. Setting up automatic cleanup job
링크 복사

13.2. Manual cleanup
링크 복사

13.3. Removing logs from the database
링크 복사

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat 소개

Theme

Red Hat legal and privacy links

Red Hat legal and privacy links

이 콘텐츠는 선택한 언어로 제공되지 않습니다.

Chapter 13. Managing log files

13.1. Setting up automatic cleanup job링크 복사링크가 클립보드에 복사되었습니다!

13.2. Manual cleanup링크 복사링크가 클립보드에 복사되었습니다!

13.3. Removing logs from the database링크 복사링크가 클립보드에 복사되었습니다!

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat 소개

Theme

Red Hat legal and privacy links

Red Hat legal and privacy links

13.1. Setting up automatic cleanup job
링크 복사

13.2. Manual cleanup
링크 복사

13.3. Removing logs from the database
링크 복사