Creating a component trace

Last update: 8 March 2018

Microsoft Windows

This article describes the steps neccessary to trace activities of Fabasoft Folio components.
This includes for instance tracing versions of libraries as fscvapp.dll, fscvport.dll or simply activating certain settings in a running kernel instance.

Fabasoft Tracer

In order to capture the trace messages from the Kernel the Fabasoft Tracer "tracer.exe" has to be started, for more information about the usage please see Fabasoft Tracer.

Creating the Trace

If the instructions from the Service Desk Ticket include a trace version of a certain library, please make sure to follow any additional steps for replacing the library, as provided by the support engineer.

To create the trace the following steps have to be performed:

  1. Open the properties of the software component, or components, that should be traced.
  2. In the software component activate the settings "Trace Calls", "Trace Errors" and "Trace Expressions" at the bottom of the first page, and commit these changes.
    Example image
  3. Prepare the steps necessary to reproduce the problem.
  4. Start the Fabasoft Tracer.
  5. Try to reproduce the problem.
  6. When the problem occurs, save the tracer output to a file using the menu "File->Save".
  7. Deactivate the settings "Trace Calls", "Trace Errors" and "Trace Expressions" inside the component.
  8. Upload the trace file to the Fabasoft Support Service Desk.

Please ensure that only trace message information from process, thread and module are recorded, this can be achived by using the Fabasoft Tracer menu "Settings->Output->Default".

Please only start the Fabasoft Tracer when you are ready to reproduce the problem. This ensures that only trace messages that are related to the problem are recorded and helps in the analysis of the trace.

Removing the Trace Version

To remove the trace verions of any provided library, stop the services on the server, delete the trace version of the files from their respective directories and execute the command "cooprep -complete".

Linux

This article describes the steps neccessary to trace activities of Fabasoft Folio components.
This includes for instance tracing versions of libraries as libfscvapp.so, libfscvport.so or simply activating certain settings in a running kernel instance.

Trace Message Logging

Prior to Fabasoft Folio 2015 trace messages in Linux were written in the log file of the appropriate instance:

  • Webservices:
    Webservices write trace messages into "/var/opt/fabasoft/log/web/WebService_.error.log".
  • AT-Services:
    AT-Services write into "/var/opt/fabasoft/instances/COOATService_/log/main/current".
  • FSCEval:
    FSCEval outputs the trace messages to the current console, in order to record this trace messages the console output has to be redirected.
    fsceval -file > /tmp/tracefile.trc

Newer versions use the tool "tracer" to log these messages, for more information about the usage please see Fabasoft Tracer.

Creating the Trace

If the instructions from the Service Desk Ticket include a trace version of a certain library, please make sure to follow any additional steps for replacing the library, as provided by the support engineer.

To create the trace the following steps have to be performed:

  1. Open the properties of the software component, or components, that should be traced.
  2. In the software component activate the settings "Trace Calls", "Trace Errors" and "Trace Expressions" at the bottom of the first page, and commit these changes.
    Example image
  3. Start a terminal.
  4. Login to the Fabasoft Folio service user.
    su - fscsrv
  5. Prepare the steps necessary to reproduce the problem.
  6. Start the Fabasoft Tracer and redirect, or tee, the ouput to a file or flush the log file if you are using a version prior to Fabasoft Folio 2015
    cat /dev/null > /var/opt/fabasoft/
  7. Try to reproduce the problem.
  8. When the problem occurs, close Fabasoft Tracer or if you are using a version prior to Fabasoft Folio 2015 copy the log file using the following command:
    cp /var/opt/fabasoft/ /tmp/tracefile.trc
  9. Deactivate the settings "Trace Calls", "Trace Errors" and "Trace Expressions" inside the component.
  10. Upload the trace file to the Fabasoft Support Service Desk.

Removing the Trace Version

To remove the trace verions of any provided library, stop the services on the server, delete the trace version of the files from their respective directories and execute the command "cooprep -complete".