Where is the SSL debug trace saved in TIBCO Data Virtualization 8.5 and in TIBCO Business Directory 8.5?

Where is the SSL debug trace saved in TIBCO Data Virtualization 8.5 and TIBCO Business Directory 8.5?

If SSL debug tracing has been turned in TDV (TIBCO Data Virtualization) 8.5 or in BD (Business Directory) 8.5, the location in which the SSL debug trace may be found depends on whether the server was:

• started without the monitor
• started with the monitor

1.   TDV server or BD server started without the monitor

TDV may be started without the monitor by running the following command from the [Install dir]\bin folder.
            composite_server.bat run         (on Windows)
            composite_server.sh run          (on Unix)
BD may be started without the monitor by running the following command from the [Install dir]\bin folder:
              bd_server.bat run                      (on Windows)
              bd_server.sh run                       (on Unix)

If started without the monitor, the SSL debug trace may be found as follows.

Windows: 

• For both TDV and BD, the SSL debug trace is not saved to a file.
• Instead, the trace appears in the console window in which the command was run.

Example:  TDV running on Windows without the monitor



Example: BD running on Windows without the monitor



Unix:

When the monitor is not running, the SSL debug trace is saved to the following file:

•  cs_server.out                (for TDV)
•  cs_bd_server.out          (for BD)

Example: TDV running on Unix without the monitor



Example: BD running on Unix without the monitor

2.  TDV server or BD server started with the monitor

TDV may be started with the monitor by running the following command from the [Install dir]\bin folder.
            composite.bat monitor start         (on Windows)
            composite.sh  monitor start          (on Unix)
BD may be started with the monitor from the [Install dir]\bin folder by running the following command:
             bd.bat monitor start                   (on Windows)
             bd.sh monitor run                      (on Unix)

If started with the monitor, the SSL debug trace is written to the following log:

• commons-daemon.out  for both TDV and BD                            (on Windows)
• cs_bd_monitor.out for BD and cs_monitor.out  for TDV          (on Unix)

Example: BD running on Windows with the monitor



Example:  BD running on Unix with the monitor


Example: TDV running on Windows with the monitor



Example: TDV running on Unix with the monitor