iProcess Engine Log Files

The iProcess Engine node automatically produces the following log files in the SWDIR\logs directory.

iProcess Engine Log Files

Log File

Description

sw_error.log

This file is created if a serious error occurs that needs to be investigated immediately, and the error occurs at a different date than the date the last error is logged. In the meantime, the previous log file will be archived as sw_errortimestamp.log, where the timestamp variable is the date when that log is generated.

See TIBCO iProcess Engine System Messages Guide for detailed information about the system errors and warning messages that can be returned by iProcess Engine.

sw_errortimestamp.log

This file is the archived sw_error.log, where the timestamp variable is the date when the log is generated.

sw_warn.log

This file is created if an error occurs that needs to be dealt with, but is not serious enough to prevent iProcess from being used, and the error occurs at a different date than the date the last error is logged. In the meantime, the previous log file will be archived as sw_warntimestamp.log, where the timestamp variable is the date when that log is generated.

See TIBCO iProcess Engine System Messages Guide for detailed information about the system error and warning messages that can be returned by iProcess Engine.

sw_warntimestamp.log

This file is the archived sw_warn.log, where the timestamp variable is the date when the log is generated.

iapjms_java.log

This file is created by the IAPJMS process (if enabled). By default, any warning or error messages produced by the IAPJMS process are written to this file.

userinfo.log

An entry is added to this file whenever user information is updated on the system. For example:

staffusr updated by swadmin - Tue Dec 7 17:27:15 2001

roleinfo.log

An entry is added to this file whenever role information is updated on the system. For example:

staffrol updated by swadmin - Tue Dec 7 17:27:36 2001

swjmx_java.log

This file is created by the JMX engine (which is part of the RPC_TCP_LI process). By default, any warning or error message produced by the JMX engine is written to this file.

wiswarn.log

An entry is added to this file whenever the server shuts down. For example:

2001/12/ 7 17:58 wisrpc : normal shutdown

wqswarn.log

An entry is added to this file whenever the server shuts down. For example:

2001/12/ 7 17:54 wqsrpc: normal shutdown

rpcport.log

This text file is only used when the port and/or RPC number ranging is enabled (see Administering Firewall Port Ranges). The file contains entries that show the resource allocation for the ports and RPC numbers used. It records the following events:

Startup of the port/RPC resource allocation service
Shutdown of the port/RPC resource allocation service
Allocation of a port/RPC number
Release of a port/RPC number
Failure to re-bind a released port
Successful re-binding of a previously failed port
Errors in the allocation/release of a port/RPC number