Depending on which part of a WebClient is being considered, there are several options available.
Logging for the installation / upgrade of the WebClient run-time
The WebClient run-time is the common installation to WebClient applications on a system, which is used to initialize and execute WebClient programs.
The run-time is installed via InstallShield.
Using the Web-based installation, it is not possible to enable installation logging. However, using the standalone installation (setup.exe) it is possible to enable logging with the following command line:
setup.exe /verbose"C:\IS.log"
Note: there must be no space between the /verbose parameters and the file name.
Logging for the installation / upgrade of a WebClient application
WebClient applications are loaded, installed, initialized and/or upgraded at start up via the programs prowcini and prowc that are part of the run-time.
All the messages that are logged are output to the files named _<AppName>.log and ai.log in the application's installation directory.
Additional client logging can be activated by adding the -clientlog parameter to the startup.pf in the Webclient installation folder, to help debug custom ABL scripts. See Article How to turn on 4GL tracing within WebSpeed, AppServer and the 4GL Client? for more information.
Logging for the execution of a WebClient application
A WebClient application is similar to a regular ABL program. Usual logging options for ABL clients apply. The logging options are set as startup parameters using the WebClient Application Manager.
See Article How to turn on 4GL tracing within WebSpeed, AppServer and the 4GL Client? for more information about ABL client logging.
