CORBA 2.6.1 Programmer's Guide for C++

Facility works.
The public section of NSDOM_Trace contains four methods. Three of these methods are used to actually create a trace message, while the
fourth method can be used to create a specific, user-defined trace file (by default, the Trace Facility writes trace messages to the file specified
during system configuration).
//C++ NSDOM_Trace Class
class NSDOM_Trace
{
public:
static void set_trace_file_name(char *pp_trace_fname,
CORBA::Environment &pr_env);
static void open_trace_file (CORBA::Environment &pr_env);
static void close_trace_file (CORBA::Environment &pr_env);
static void log_trace (char *pp_trace_data,
short pv_trace_data_len,
CORBA::Environment &pr_env);
};
Trace Method Descriptions
The NSDOM_Trace::log_trace() method writes a trace message to the trace file. This method will also create and open the trace file if this
operation has not already been performed by a specific call to the
open_trace_file() method (you need not call open_trace_file() before
calling this method).
The NSDOM_Trace::open_trace_file() method provides a means to create and open the trace file before calling the log_trace() method.
NSDOM_Trace::close_trace_file() provides a way to specifically close the opened trace file. NSDOM_Trace does not automatically close the trace
file until the current process exits.
NSDOM_Trace:: set_trace_file_name() provides an option to specify a user-defined trace filename. This method allows you to override the
default trace file specified in the configuration database. To create a user-specified trace file, you must call this method before making any calls
to open_trace_file() or log_trace().
Trace Records
This section describes the trace records for IIOP/SSL. The trace records are emitted by the SSL server. The SSL version is also included in the
trace records.
SSL_accept
The SSL_accept trace record is emitted by a SSL server and is triggered when a hello message is sent from the client to the server. The accept
side of the SSL handshake is traced. The SSL version is included in the trace record.
SSL_accept:before accept initialization
SSL_accept:SSLv3 read client hello A
SSL_accept:SSLv3 write server hello A
SSL_accept:SSLv3 write certificate hello A
SSL_accept:SSLv3 write server done A
SSL_accept:SSLv3 flush data
SSL_accept:SSLv3 failed in SSLv3 read client certificate A
SSL_accept:SSLv3 read client key exchange A
SSL_accept:SSLv3 read finished A
SSL_connect
The SSL_connect trace record is emitted by a SSL client and is triggered when a hello message is sent from the client to the server. The
connect side of the SSL handshake is traced. The SSL version is included in the trace record.
SSL_connect:before connect initialization
SSL_connect:SSLv3 write client hello A
SSL_connect:SSLv3 failed in read sever hello A
SSL_connect:SSLv3 read sever hello A
SSL_connect:SSLv3 read server certificate A
SSL_connect:SSLv3 read server done A
SSL_connect:SSLv3 write client key exchange A
SSL_connect:SSLv3 write change cipher spec A
SSL_connect:SSLv3 write finished A
SSL_connect:SSLv3 flush data
SSL_connect:failed in SSLv3 read finished A
SSL_connect:SSLv3 read finished A
SSL_handshake_done