x

1. From the Workspace menu, select Configuration/Monitor.
2. Open the Logs and Traces folder on the navigation pane, right-click Traces, and select Configure.

   The Traces Configuration page opens.

   

3. Optionally, set the trace size limit to a specific number of lines. After the limit is reached, trace data is dumped to an alternate file with the extension TRB. Logging continues into the trace file with extension TRC. For related information, see Limiting the Size of a Trace File.

   A blank entry indicates no trace size limit.

4. Select an option from the Choose the trace components to activate drop-down menu. The selections you make here are written into a file called ibitrace.fex. The settings take effect on the next server start/restart.

   Note that Customer Support Services may request that you change from the default trace setting to a custom setting to facilitate their research.

   Default Components

   • R1H
   • QOPSYS
   • PRH
   • NWH
   • NLS

   All Components

   • All traceable server components.

   Typical Components

   • CEH
   • NWH2
   • PRH
   • SQLAGGR
   • STMTRACE

   Custom Components

   This option allows you to select the specific components to activate.

   The components are categorized as follows (each category has a list of trace options within it):

   • COMMAND PROCESSING
   • COMMUNICATIONS and SYSTEMS
   • COMMON ADAPTER LAYERS AND SERVICES
   • SQL TRANSLATOR
   • SQL DATA ADAPTERS
   • OLAP DATA ADAPTERS
   • NON-SQL DATA ADAPTERS
   • LEGACY DATA ADAPTERS
   • REPORT SERVICES
   • NLS SERVICES
   • ODIN INFORMATION
   • SMART MODE
   • MAINTAIN PROGRAMMER TRACES
   • MAINTAIN INTERNAL SERVICES
   • MISCELLANEOUS SERVICES
   • TRANSACTION COORDINATOR
   • XFOCUS
   • USE-WHERE
5. Click the Save or Save and Restart Server.

Tip: If you wish to restore default settings or choose typical settings, select these options, then click Save Settings. The selected group will be checked when you reopen the Custom Components list.

x

You can use set the size limit of the trace files. The trace size limit specifies the maximum number of lines in the trace files. The value is written into the IBITRACE.FEX file as SET TRACESIZE = value and requires a server restart to activate. After the size limit is reached for a particular trace, the trace data is redirected to an alternate file with an extension of .TRB. When the size limit is reached in the .TRB version of the file, then writing resumes with the .TRC version of the file. A trace cycles between the two matched sets of files to alleviate maxing out a disk drive with large individual traces. Each cycle starts a fresh file (versus an append). If there are intermediate traces that need to be saved, it is up to the site to monitor and implement specific methods to save traces based on their needs and capabilities. For example, copying to an archive disk or secondary machine and possibly using compression.

x

1. From the Workspace menu, select Configuration/Monitor.
2. Open the Logs and Traces folder on the navigation pane, right-click Traces, and select Filter.

   The Traces Filter page opens.

3. Select an option from the Trace components to filter drop-down menu:
   • No Filtering (the default) displays all trace information.
   • Errors displays only errors, crashes, errno, abort or fail conditions.
   • Typical Components displays trace information from typical components.
   • Custom Components displays trace information from components which you select.

   

4. Click Set Filter. The filters take affect when you enable and run traces.

x

Capturing traces in a script file enables you to isolate server problems. Specifically, you can enable this type of custom trace, then reproduce the problem and capture the input commands issued from a front-end tool (such as WebFOCUS Developer Studio) to the server. Customer Support Services can then isolate debugging for the server only, instead of having to recreate a whole complex environment.

1. From the Workspace menu, select Configuration/Monitor.
2. Open the Logs and Traces folder on the navigation pane, right-click Traces, and select Configure.
3. Select Custom Components from the Trace components to filter drop-down menu.
4. Click the Unselect All button.
5. Choose AJ - NWHSIM/1 under Communications and Systems.
6. Click Set Filter.

The trace setting will be active the next time the server is started.

x

By default, the Session Log holds 500 lines. You can increase or decrease the number of lines.

x

1. From the Workspace menu, select Configuration/Monitor.
2. In the navigation pane, right-click Miscellaneous Settings, and click Configure.
3. On the Miscellaneous Settings page, locate the seslog_max_lines field, and type the number of lines to assign to the buffer for the Session Log.

   In the following image, the value for seslog_max_lines is set to 750.

   

4. Click Save. You do not need to restart the server for the new setting to take effect.

x

1. On the Web Console menu bar, click the Show Session Log Window icon, as shown in the following image.

   

   Tip: After you open the Session Log, the Show Session Log Window icon disappears from the menu bar. When you hide the Session Log, as described in step 6, the icon reappears.

   A small pane opens near the bottom of the window, similar to the one shown in the following image.

   

2. Click the Maximize button at the upper-right of the pane to enlarge it.
3. Click the Refresh button on the left of the Session Log menu bar to display the current contents of the log.
4. Optionally, click the Filter drop-down list to select only those commands or data that you want to include in the Session Log. You can select:
   • Focus, to display WebFOCUS commands sent to the server for execution.
   • Sql/mdx, to display SQL or MDX code that is generated by an adapter and sent to a relational database or OLAP database, respectively.
   • Transform, to display the result of transforming the user-supplied code in a procedure, into WebFOCUS code that is supported on the server. This option is useful for DataMigrator jobs that require transformation.
   • Errors, to display error messages returned from the server.
   • Messages, to display informational messages returned from the server, for example, NUMBER OF RECORDS IN TABLE, SVG FILE SAVED, and others.
   • Timestamp, to display the date and time at which a command or message was exchanged. For example, if you select Errors and Timestamp, the Session Log displays the time at which an error message was returned from the server.
   • No Delay, to display the Session Log while a request is still running, not after it has finished running. This option is recommended for long-running requests.

   In the following image, the check boxes for Focus, Messages, and Timestamp are selected to include the display of WebFOCUS commands and messages, and to include the date and time of each entry in the log.

   

   When you filter the Session Log, its contents automatically refresh to reflect the last criterion that you specified.

5. Optionally, you can do one of the following:
   • Click the Clear Messages button on the left of the Session Log menu bar to remove the current contents of the log.
   • Click the Refresh button on the left of the Session Log menu bar to update the log.
   • Use standard editing functions, such as:

     Ctrl+A, Ctrl+C, and Ctrl+V to select all the contents of the log, copy it, and paste it into another file.

     Ctrl-click to highlight a line.

     Shift at the beginning of a block of lines, and Shift-click at the end of the block of lines, to highlight the lines.

6. When you have finished reviewing the messages in the Session Log and want to close it, click Hide on the right of the Session Log menu bar.

x

You can display a log of the activity that takes place in an individual Web Session.

1. From the Workspace menu, select Configuration/Monitor.
2. In the navigation pane, expand the Special Services and Listeners folder.
3. Right-click HTTP, and from the menu, click Web Sessions.

   The Performance Report for all Web Sessions is displayed.

4. On the report, right-click a row for an individual Web Session, and from the menu, click View Session Log.

   The log for the selected Web Session opens, as shown in the following image.