Configuring Client-side Logging

Event logging and tracing on the client computer is handled via a separate properties file. By default, logging and tracing are turned off.

To configure client-side logging
  1. Verify that the file is listed in the client's Java classpath.

    See Enabling Client Access to Run-time Servers for information on editing the client class path.

  2. Open the file, located in the /EAI/Common/Config directory, and change the appropriate logging and tracing values to True.

    For an example, see the sample file below.

  3. To view your event log, open Services, select Events, and choose View Events from the navigation tree. The MCS View Events pane displays. The options you enabled in the file will help filter the list of logged events for easier viewing. See Viewing Events for more information on the MCS event viewer.

Sample file

Using the file you can configure the same settings that are available when configuring the runtime server event logs and traces. Click Help on the Logging/Tracing tab for a description of each option.



This property
Does this
logging and tracing properties Determines the logging and tracing options that will be used on the client computer.

Click Help on the Logging/Tracing page, which is accessed through the management console, Configure page, for information on these properties.

notranslate.truncate Determines how to handle no-translate fields when an input value to the field is longer than the field length.

When set to false (the default), an Exception is thrown and, if previously configured, an event logged.

When set to true, the input value is truncated to the fields length value and, if previously configured, an event logged.

See Properties of Input and Output Fields for more information on Task Builder input and output fields.

Related Topics
Bullet Logging and Tracing
Bullet Configuring Event Logging and Tracing
Bullet Viewing Events
Bullet Properties of Input and Output Fields