Enterprise tier logs

The following tables list types of enterprise tier logs and where they can be found. Teamcenter business logic server logs Miscellaneous enterprise tier logs PLM XML logs Multi-Site logs Teamcenter business logic server logs Log file Log contents Log file location within BaseLogLocation\Teamcenter\ServerManagers<Cluster><PoolID>\ ServerManager.log Records messages from the server manager application. ServerManager\process ServerManager.log configuration: Increase the information logged to this file by increasing the severity level of the TC_ROOT\pool_manager\confs\configuration-name\log4j2.xml file. tcserverpid.syslog Diagnoses errors. Captures information, errors, and warnings. TcServer\process tcserverpid.syslog configuration: For information on logging levels, see Configuring business logic server logging. tcserverpid.jnl Tracks objects accessed from the database and the activities performed on those objects. This session log also performs a trace through software modules. Each time you invoke or exit a module, the Log Manager posts an entry to this file. Miscellaneous enterprise tier logs Log file Log contents Log file location install.log Tracks Teamcenter installation messages. The date-time stamp represents the date and time Teamcenter Environment Manager was run. For example, install1322241627.log indicates that Teamcenter Environment Manager was run at 4:27 on February 24, 2013. TC_TMP_DIR install.log configuration: Define the TC_TMP_DIR environment variable in the TC_DATA\tc_profilevars.bat file. pomutilities.log Standard output from the POM utilities called by Teamcenter Environment Manager. pomutilities.log configuration: Define the TC_TMP_DIR environment variable in the TC_DATA\tc_profilevars.bat file. audit.log Tracks selected properties for specified actions in the database. These audit logs are created in Audit Manager. TC_LOG The default setting is TC_DATA\log_ORACLE-SERVER_ORACLE-SID where ORACLE-SERVER is the Oracle server network node and ORACLE-SID is the unique name of the Oracle database instance. fscid_startup.log on Linux. fscidstdout.log and fscidstderr.log on Windows. Replace fscid with the FSC ID defined in FSC_HOME\fsc.xml. Captures all FMS server cache (FSC) process output generated from stdout and stderr. This output is useful in diagnosing failure-to-start issues. The file also contains the entries generated to the runtime log. Windows: FSC_HOME Linux: /tmp PLM XML logs Log file Log contents Log file location xml-file-name.log or plmxml_log_timestamp.log Provides complete information regarding the current PLM XML export or import. TC_TMP_DIR For command line export, if TC_TMP_DIR is not set, the log file is generated at the same location as the XML file. For export from the rich client, the log file is generated at the same location as the XML file. xml-file-name.log or plmxml_log_timestamp.log configuration: Specify the logging level with the PLMXML_log_file_content preference. Multi-Site logs Log file Log contents Log file location idsmID.log Tracks actions performed on objects at the session level, such as imported or exported objects. TC_TMP_DIR on the machine hosting the IDSM server. idsmID.syslog Diagnoses errors. Captures information, errors, and warnings. idsmID.jnl Tracks objects accessed from the database and the activities performed on those objects. This session log also performs a trace through software modules. Each time you invoke or exit a module, the Log Manager posts an entry to this file. odsID.log Tracks actions performed on objects at the session level. TC_TMP_DIR on the machine hosting the ODS server. odsID.syslog Diagnoses errors. Captures information, errors, and warnings. odsID.jnl Tracks objects accessed from the database and the activities performed on those objects. This session log also performs a trace through software modules. Each time you invoke or exit a module, the Log Manager posts an entry to this file.