Windchill System Administrator's Guide

Log Files
Database Components
specifications that are executed by a background processing manager. The
specifications are essentially method names and serialized arguments (stored as
BLOBs) that are stored in the database for reliability.
A transaction that triggers background processing includes updating a background
method queue as part of the overall transaction. Once committed, the background
manager is notified, and it proceeds to execute the methods asynchronously.
Removal of queue entries is performed within the transaction that carries out the
method, thus guaranteeing that entries are processed to completion only once,
while still ensuring that incomplete transactions are restarted after system failures.
Upon failure, entries are marked as requiring administrator intervention and
ignored.
Examples of the background processing mechanism include life cycle processing,
workflow automation, and full text retrieval (FTR) index maintenance.
For information about background queue configuration and maintenance, see
Configuring and Administering Background Queues.
Log files are used to capture exception/error tracebacks and debug tracing
messages. In the first case, log entries are generally infrequent, marking
exceptional events. However, you can enable more verbose logging levels for
troubleshooting purposes. (Full tracebacks may not be available when you run
some JIT compiler implementations.)
Many packages support the printing of messages during execution to assist you in
debugging. This option is typically controlled by property settings in the
wt.properties file. Using these properties, you can enable or disable writing to log
files. Additionally, log files can be appended or overwritten at each execution.
Output can be sent to both the console and log file, or just the log file.
Logging does have a performance impact, so the verbose mode should be turned
off if you are not debugging.
Each server application (server manager, method server, and HTTP gateway) has
a separate log. For the HTTP gateway, CGI and Servlet share the same log file. In
addition, code generation tools also have log files.
Object Relational Database Management System (ORDBMS)
The Windchill system uses an ORDBMS to store structured and unstructured
business data. The database manager is typically run on the same host as the
Windchill servers, but at larger sites it may run on a dedicated host and be
accessed remotely from one or more Windchill server hosts. Oracle, with support
for very large objects and object tables, is the reference feature set for which
Windchill is designed.
Windchill Runtime Environment A-17