Open topic with navigation

TIBCO iProcess® Engine 11.10.0

# Using the UNIX System Log

The UNIX system log (also known as `syslog`) is a general-purpose logging facility available when you are running TIBCO iProcess® Objects Server on a UNIX system.

Messages that are written to the audit log (see Audit Log) are always written to the UNIX system log. You can also optionally specify that messages that are written to the TIBCO iProcess® Objects Server log (other than Debug messages) be written to the UNIX system log.

To specify that you want TIBCO iProcess® Objects Server log messages written to the UNIX system log, locate the `UseSysLog` parameter (see UseSysLog (UNIX Only)) in the TIBCO iProcess® Objects Server configuration file (`$`SWDIR`/seo/data/swentobjsv.cfg)` and set it to “1” (the default is “0” — information is not written to the UNIX system log).

The location of the UNIX system log can be configured on each UNIX system, but the usual location is:

| • | Linux - `/var/log/messages`

All syslog messages are categorized by the type of “subsystem” or “facility” that originated the message, and by the “priority” given the message. The “subsystems” are areas such as “kernel” (message generated by the kernel, i.e., UNIX itself), “user” (messages from various user programs), “mail,” “daemon,” “auth,” and “lpr.” There are also “local” subsystems (local0 through local7) that are reserved for local program use. The TIBCO iProcess® Objects Server uses one of these — local0.

Within each subsystem, there are various priority levels. In the TIBCO iProcess® Objects Server, the priorities that are used, correspond to the TIBCO iProcess® Objects Server log levels/types. The following log levels or types are:

| • | local0.info - includes “info,” “notice,” “warn,” and “err”

| • | local0.notice - includes “notice,” “warn,” and “err”

| • | local0.warn - includes “warn,” and “err”

| • | local0.err - includes “err” only

Notice that each priority also includes the levels it.

The UNIX system log file is controlled by the configuration file `/etc/syslog.conf`.

You can also choose to send all TIBCO iProcess Objects Server messages to a different file by adding a line similar to the following to the `syslog.conf` file:

    local0.info /var/adm/spo_messages_only

Note that whenever the `syslog.conf` file is changed, the syslogd daemon must be sent a SIGHUP signal.

Example:

    kill -HUP ‘cat /etc/syslog.pid’

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-2025. Cloud Software Group, Inc. All Rights Reserved.