Transcoding Technology logging and tracing

Portal, Express Beta Version 6.1
Operating systems: i5/OS, Linux,Windows

Transcoding Technology logging and tracing

Transcoding Technology sends events to the message and trace logs. Message logging records informational messages about normal operations as well as warnings and error messages. Tracing provides more detailed information for troubleshooting problems. Messages are translated into the language specified for your machine. Trace records are not translated. By default, message logging is turned on and tracing is turned off. You can turn tracing on and off by selecting the TranscodingTraceLogger component in the Enable Tracing page in the Administration Portal.

To enable tracing, follow these steps:

Download the following files into portal_server_root/IBMTrans/etc/ras:

TranscoderRASTraceLogger.properties 
TranscoderTraceMaskFilter.properties

Restart IBM^® WebSphere^® Portal Express.

Message logging

Message categories

Three categories of messages are written to the message log file:

Information: records normal events. Use these messages to determine whether expected operations occur, for example, to verify that a configuration change takes place as expected.

Warning: indicates a possible problem. Requests might still be handled successfully.

Error: indicates a definite problem requiring administrator attention. Requests will probably not be handled successfully.

Message files

Message files are created in the portal_server_root/IBMTrans/log directory. The first message file created is named TranscoderMessages1.log. When the maximum size is reached, this file will be renamed to TranscoderMessages.log and a new TranscoderMessages1.log file is created for new messages. The default message file size is 512 kilobytes. See the WebSphere Portal Express documentation for information regarding changing the file size. TranscoderMessages1.log is always the newest file.

Viewing messages

Tracing

Tracing records the specific behavior of Transcoding Technology, recording information useful in the diagnosis of problems.

Trace files

Trace files are created in the portal_server_root/IBMTrans/log directory. The first trace file created is named TranscoderTrace1.log. When the maximum size is reached, this file will be renamed to TranscoderTrace2.log and a new TranscoderTrace1.log file created for new messages. The default trace file size is 512 kilobytes. See the WebSphere Portal Express documentation for information regarding changing the file size. TranscoderTrace1.log is always the newest file.

When the maximum number of trace files has been filled, the oldest file will be deleted, the suffix number of each remaining file will be increased by one, and a new TranscoderTrace1.log will be created for new messages. A new file is begun when Transcoding Technology is restarted. The default number of trace files is 3. See the WebSphere Portal Express documentation for information regarding changing the maximum number of trace files.

Enabling Request Viewer for Transcoding Technology

IPX1041 The plugin named com.ibm.wbi.viewer.ViewerServerPlugin could not be initialized. TPX1084E Underlying error detail: com.ibm.wbi.PluginException: RMI is disabled.

Gathering troubleshooting data

If you have a problem while running Transcoding Technology, there is a certain set of information that will be useful in troubleshooting. The RASCollect program will package the necessary files and settings to make it easy to gather diagnostic information. If you need to use this function, execute the following command:

Windows: RASCollect.bat

Linux: ./RASCollect.sh

i5/OS: RASCollect.sh

This will create a RASCollect.zip or RASCollect.tar file that you can send to your service representative. Parent topic: Logging and tracing

Library | Support | Terms of use |