To enable logging, the Orbix simple_persistent demo can be taken as an example: The server from the demo is run on windows with the following command:
"java -classpath .\\java\\classes;%CLASSPATH% simple_persistent.Server -ORBname simple_orb [-file <objref-filename>] "

So the orbname used is simple_orb. Therefore, the following configuration scope needs to be added to the configuration file:

simple_orb
{
    event_log:filters = ["*=*"];
    plugins:local_log_stream:filename = "C:\\Orbix6.3.3\\asp\\6.3\\demos\\corba\\standard\\simple_persistent\\simple_persistent.log";
};

The logging level is specified by the event_log:filters variable. In the above example its set to the maximum level. This may not be suitable for a production system as the log files may be too large. The plugins:local_log_stream:filename configuration variable then specifies the location where the logging is been output. 
Additional logging can be output to the command prompt using the line: "-ORBevent_log:filters *=*". So in the above example, the command to run the server would now be: "C:\\Iona\\Orbix6.3.3\\asp\\6.3\\demos\\corba\\standard\\simple_persistent>java -classpath .\\java\\classes;%CLASSPATH% simple_persistent.Server -ORBevent_log:filters *=* -ORBname simple_orb -file test.ior". The configuration scope simple_orb in the Orbix domain configuration would have to be commented out for this to work correctly.