IBM InfoSphere Master Data Management, Version 11.3Use your log files to record specific events for troubleshooting and system analysis.
Log files generally record InfoSphere® MDM Collaboration Server runtime events, including exception traces and error messages and can help you resolve issues. For troubleshooting and analysis of your log files, you can use the Log and Trace Analyzer (LTA).
The InfoSphere MDM Collaboration Server log files under the <install dir>/logs directory provides helpful debugging information.
Each product service includes several different runtime-generated log files that record certain events within each of the services. The svc.out log file is a runtime log file that each service creates, and it should be one of the first log files that you analyze when troubleshooting a problem. After starting a service, view the svc.out file for errors or exceptions to ensure that the service started correctly.
For the appsvr, the most common startup problem is database related. The appsvr does not start if it cannot connect to the database. The db.log file in the appsvr log directory indicates if a connection can be made.
The default log file format is the log4j PatternLayout format. To provide you with some control over the legibility of your PatternLayout log files, you can modify how the messages are formatted within the log file. The log.xml file is located in $TOP/etc/default/ directory.
For the log file, you can choose to use one of two formats: log4j PatternLayout format and Common Base Event (CBE) CBELayout format. You specify which format that you want to use in the common.properties file. The CBE format is generally used only while troubleshooting a problem under instruction by IBM® Software Support.
On UNIX, the console output from a service is redirected to daemon.out and daemon.err in each log directory.
You can run the —verbose option with almost any script to print debugging information. For InfoSphere MDM Collaboration Server services, you can use the svc_control.sh script to display information about the configuration of a service. To display the configuration information including classpath and JVM system properties that start a service, you can run the script <install dir>/bin/go/svc_control.sh –action=show_config –svc_name=<svc full name>. The start_cmd and start_cmd_args settings show the exact string used to start a service.