This site requires JavaScript to be enabled
IE BUMPER

Product
Version
IncidentLookup using list
Language
How can we help?

Solution Suggestions

Please enter your question to get suggestions.
  Help
IE BUMPER
Categories
Boolean Operators
OR or vertical bar symbol (|)
Finds a match if either the terms exist in a document (a union using sets).
AND
Finds a match if both terms exist in a document (an intersection of sets).
NOT, minus (-), or exclamation point (!)
Excludes documents that contain the term after NOT (a difference of sets).
Wildcards
Asterisk (*)
The asterisk symbol performs a multi character wildcard search.
Percent sign (%)
The percent sign performs a single character wildcard search.
Phrases
Quotation marks (")
Use quotation marks to search for an exact phrase with multiple terms.
For examples and more information look at our Knowledge Base: Advanced Search On The Support Portal

Logging options in TOSCA

The following articles will give you an overview over the different kinds of logging in TOSCA.


Situation

For a further analysis of issues it is sometimes required to provide more information about the affected components.
There are several logging options which can be activated to retrieve this information.


Table of contents

General

TBox & license

Classic Engines


General

Workspace logging

Workspace logs are created by default. Default log level is 4.
To create a log with log level 12, Tosca Commander must be started via Windows command line with the following command.

  • Tosca 12.2+
    "%COMMANDER_HOME%\ToscaCommander.exe" -loglevel 12
  • Tosca 10.0 to 12.1
    "%TRICENTIS_HOME%\ToscaCommander.exe" -loglevel 12

Log directory: workspace folder

 

SupportInfo

  1. In Commander, go to Project tab
  2. Select About Tosca
  3. Select Supportinfo

Log directory: %TRICENTIS_ALLUSERS_APPDATA%\Support

 

Migration log

During manual migration of the common repository there is a temporary log file created.

Log directory: %APPDATA%\TRICENTIS\TOSCA TestSuite\7.0.0\Temp\TCTempLog

 

TBox & License

TBox & license logging

  • Tosca 12.2+​​​​​
    1. Start the file %TBOX_HOME%\Tricentis.Common.LogServer.exe
    2. Select OFF->All from the menu
    3. Reproduce the issue (execution, scan, license issue, ...)
  • Tosca 10.2 to 12.1
    1. Start the file %TRICENTIS_HOME%\Tricentis.Common.LogServer.exe
    2. Select OFF->All from the menu
    3. Reproduce the issue (execution, scan, license issue, ...)

Log directory: %TRICENTIS_ALLUSERS_APPDATA%\logs\Automation

 

Flexera License Server

Tosca 10.2+

Log directory: C:\Windows\ServiceProfiles\NetworkService\flexnetls\<producer_name>\logs

(see also the relevant section in the FNE_LicenseServerAdminGuide_2016R2-SP1.pdf that is part of the license server setup)

 

Sentinel License Server

until Tosca 10.1

Default log directory: <OSdrive>:\WINDOWS\system32\lservsta

The directory is set manually in the environment variables:

  • LSERVSTA
  • LSERVLOG (contains the name of the error-logfiles)

 

Classic engines

Classic Base Engine

Logging can be enabled via settings:

  • Engine.Logging Options.EventLog Level change to Errors, Warnings and Informations
  • Engine.Logging Options.Log Level change to Class Events

Log directory: see setting Engine.Logging Options.Path to Logfile Directory

 

Delphi Engine

Logging can be enabled via setting Special Engines.DelphiEngine.Trace.EnableTrace

Log directory: see setting Special Engines.DelphiEngine.Trace.TracePath

 

DotNet Engine

Logging can be enabled via setting Special Engines.DotNetEngine.Trace.EnableTrace

Log directory: see setting Special Engines.DotNetEngine.Trace.TracePath

 

Gupta Engine

Logging can be enabled via setting Special Engines.GuptaEngine.Trace.Enable Trace

Log directory: see setting Special Engines.GuptaEngine.Trace.Directory of the trace files

 

Java Engine

Logging can be enabled via setting Special Engines.JavaEngine.Logging.Logger Type

Log directory: see setting Special Engines.JavaEngine.Logging.Log-Directory

 

Visual Basic Engine

Logging can be enabled via setting Special Engines.VBEngine.Trace.EnableTrace

Log directory: see setting Special Engines.VBEngine.Trace.TracePath

 

Powerbuilder Engine

Logging can be enabled via the file: %TRICENTIS_HOME%/dll/PBEngine/log4net.xml

In this file, the following value has to be adapted.
From:
level value="WARN"
To:
level value="DEBUG"

Log directory: %APPDATA%\Tricentis\TOSCA Testsuite\7.0.0\logs\pbengine
 

0 3

Jay Reyes

Created: 2018-05-17 18:49:28 , Updates: 1, Last Update: 2018-05-18 16:43:34

Great read!

0 3

Jay Reyes

Created: 2018-06-08 17:43:54 , Updates: 1, Last Update: 2018-06-15 23:51:19

:)