Copyright © Cloud Software Group, Inc. All rights reserved.

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 locations are:

•	Solaris - /var/adm/messages

•	HP-UX - /var/adm/syslog/syslog.log

•	Linux - /var/log/messages

•	AIX - various log files in /var/adm

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. They 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 below it.

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

You could optionally 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. For example:

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

Copyright © Cloud Software Group, Inc. All rights reserved.