Open topic with navigation

TIBCO iProcess® Engine 11.9.1

# LOG_FILE_MAX_ARCHIVES

This specifies the number of archive log files that are saved when the log rolls over as a result of reaching the maximum size limit (LOG_FILE_MAX_SIZE). This can be useful if you want to collect many MB of debug logs, but do not want to include a very large log file by setting LOG_FILE_MAX_SIZE to a large value.

## Windows Systems

The “non-archived” TIBCO iProcess® Objects Server log file is named `SWEntObjSv` `XX``.log` (see Name and Location of the TIBCO iProcess® Objects Server Log). If the LOG_FILE_MAX_ARCHIVES parameter is set to a value greater than 0, and the “non-archived” TIBCO iProcess® Objects Server log file reaches the maximum size set by the LOG_FILE_MAX_SIZE parameter, the log rolls over and “archived” log files are saved. The archived log files are named `SWEntObjSv` `XX``_``timestamp``_archive_``xxx``.log`, where xxx is a counter that is incremented each time the log rolls over (starting at 1). For example, if this parameter is set to 2, the first time the log rolls over, it will be saved as `SWEntObjSv` `XX``_``timestamp``_archive_1.log`. The next time it rolls over, it will be saved as `SWEntObjSv` `XX``_``timestamp``_archive_2.log`. If it rolls over again, it will be saved as `SWEntObjSv` `XX``_``timestamp``_archive_3.log`, but `SWEntObjSv` `XX``_``timestamp``_archive_1.log` will be deleted because it is only saving two archives.

## UNIX Systems

The “non-archived” TIBCO iProcess® Objects Server log file is named `swentobjsv` `XX``.log` (see Name and Location of the TIBCO iProcess® Objects Server Log). If the LOG_FILE_MAX_ARCHIVES parameter is set to a value greater than 0, and the “non-archived” TIBCO iProcess® Objects Server log file reaches the maximum size set by the LOG_FILE_MAX_SIZE parameter, the log rolls over and “archived” log files are saved. The archived log files are named `swentobjsv` `XX``_``timestamp``_archive_``xxx``.log`, where `xxx` is a counter that is incremented each time the log rolls over (starting at 1). For example, if this parameter is set to 2, the first time the log rolls over, it is saved as `swentobjsv` `XX``_``timestamp``_archive_1.log`. The next time it rolls over, it is saved as `swentobjsv` `XX``_``timestamp``_archive_2.log`. If it rolls over again, it is saved as `swentobjsv` `XX``_``timestamp``_archive_3.log`, but `swentobjsv` `XX``_``timestamp``_archive_1.log` will be deleted because it is only saving two archives.

Whenever the TIBCO iProcess® Objects Server is restarted, the archive log file name starts back at `swentobjsvb` `XX``_``timestamp``_archive_1.log`. Therefore, if the system is set up for three archive log files, and the log rolls over eight times, the archive log files will be ..._6.log, ..._7.log, and ..._8.log. However, if the server is now shut down and restarted, the next three archive log files will be ..._1.log, ..._2.log, and ..._3.log (the ..._6.log, ..._7.log, and ..._8.log files will still exist).

Lower Bound: 0 (do not archive log files)
Upper Bound: none
Default: 0

Process Attribute | Description
`LOG_FILE_MAX_ARCHIVES` Type : Integer Range : 0 to 99999 MB Default : 0 | Maximum number of archived log files created if the log rolls over. A value of 0 means do not archive logs. This process attribute can be changed while the TIBCO iProcess Objects Server is running.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO iProcess® Engine

Copyright © 1994-2024. Cloud Software Group, Inc. All Rights Reserved.