Set Trace Options

Using the Trace Settings panel, you can select one or more of the following types of trace options:

Enable Runtime Tracing: Enables tracing in ZIETrans runtime for connections in your project. To trace these runtime connections at a different level, see Runtime properties files for information about the trace settings.
Enable Widget Tracing: Enables tracing in ZIETrans runtime for widgets in your project. To trace widgets at a different level, see Runtime properties files for information about the trace settings.
Enable Action Tracing: Enables tracing in ZIETrans runtime for event actions in your project. To trace events at a different level, see Runtime properties files for information about the trace settings.
Enable Component Tracing: Enables tracing in ZIETrans runtime for components in your project. To trace components at a different level, see Runtime properties files for information about the trace settings.
Enable Util Tracing: Enables tracing in ZIETrans runtime for runtime utilities in your project. To trace these runtime utilities at a different level, see Runtime properties files for information about the trace settings.
Integration Object Tracing: Enables tracing in specific Integration Objects in your project. Use the Class Name specification field to specify which Integration Objects to trace, using one or more patterns. Each pattern can contain one or more wildcard (*) character. For example, IntegrationObject.Callup* specifies that tracing is enabled for all Integration Objects that start with the letters Callup. To trace all Integration Objects, specify IntegrationObject.*. If multiple patterns are specified, they should be delimited with commas. ZIETrans administrative console sets the Integration Object setting to the maximum trace level. To trace Integration Objects at a different level, see Runtime properties files for information about the trace settings.
Applet Tracing: Enables tracing of the applet. The higher level of trace will produce more tracing information. When applet tracing is turned on, it will output server side messages for troubleshooting. For more information about applet trace settings, see Runtime properties files.
User Macro Tracing: Traces the playing of macros. Because it affects system performance, we recommend that you use this trace only for debugging macros.
Display Terminal: Enables you to view the host terminal screen of any connection as it runs in real time on the server. After you enable the display terminal, the terminal settings are shown only for newly created connections. For more information about the Display Terminal, see Using display terminal for testing and debugging.
Note: You can decide whether ZIETrans should display a dialog asking you if you want to turn on the display terminal when you Run on Server. For more information, see Using ZIETrans preferences.
Record Host Simulation Trace: Select the Enable Host Simulation Recording box to enable host simulation recording during runtime. Recording starts the next time a host session starts and ends when the host session is closed, for example when the user clicks the disconnect button on the application keypad. If the user closes the Web browser while tracing is active, the trace will continue until the HTTP session times out. The trace file is saved in the host simulations folder on the server, for example, <WebSphere® install root>\AppServer\profiles\AppSrv01\installedApps\<Node ID>\<ear file name>\<ApplicationName>.war\WEB-INF\profiles\hostsimulations. Trace files are named using the following template, ApplicationName_ConnectionName_Date(yyyymmdd)_Time(hhmmss)_Number, for example, MyApplication_main_20060101_134543_1.
In order to trace multiple host sessions concurrently, host simulation uses multiple TCP/IP ports. Use the TCP/IP Port Range for Recording fields to set the range of port numbers for server runtime usage. The default starting port in the range is 7021, and the default ending port is 7050.
Trace Output: Enables you to control whether trace information is written to the trace file, and define the file to which the log events are written. See Log and trace file names for information about how trace files are named. If the file already exists, new trace information is appended to it. You can also define how many trace files to keep and the maximum size of each trace file.