Back to series

This video will show you the new enhanced debug options in RightFax 16.4

In RightFax 16.4, RightFax services can be run in debug mode with custom options for real-time monitoring, logging, and troubleshooting.

Today, I’ll be giving you a brief demonstration on how to use the new debug options.

On your RightFax Server, open Enterprise Fax Manager and then, click on services. I’m going to be running DocTransport in debug mode, but there are several services that have this option available. Before running any debug, I want to change the logging level for the service.

To change the logging level, right-click on the RightFax DocTransport Module and select “configure service”. From here, make sure that “Global DocTransport Settings” is selected on the left and then click in the drop-down for “Event Log Level” and change it to “Verbose”. Click “OK” at the bottom of the window to save the change.

Now we’re ready to begin our debug. Keep in mind that running a service in debug mode requires the service to be stopped first before we can start the debug. Just something to consider if you are doing this in a production environment. Right-click once more on RightFax DocTransport Module and select “Debug with Options”. A dialog box will open asking us which options, also referred to as “switches”, we want to use. The option “Run in console” is automatically selected for me and cannot be changed. The remaining options are up to us. I’m going to leave the “Show diagnostic input” option selected and will also place a check next to “Output to log file” which will create a text file containing our debug. Notice that the -o switch was added to the window at the bottom. Now I’ll click “OK” to begin the debug. We are now presented with a window asking us to confirm that we want to stop the service, which again will interrupt any active faxing. I’m going to click “Yes” to begin my debug.

At this point, a command prompt window opens which shows us our debug is running. Let this continue to run for as long as necessary to capture the information we need. When you’re ready to end the debug, simply click the “x” in the top right corner of the command prompt window. Before we start our service back up again, remember to go back into configuration and change the Event Log Level back to what it was before we changed it earlier. After changing it back and clicking “ok”, right-click on your stopped service and start it up again.

To locate the logfile that our debug created, navigate to your RightFax install directory, and then the subdirectory for the service you ran the debug. Since I just ran a debug on DocTransport, I’ll go into that directory. Notice the “Logs” folder here. This is where our debugs are stored. If we go into this directory, we see our debug file which is automatically named with the name of the service, our RightFax server’s name, and a date/time stamp. This will make it easier to identify if you’ve run multiple debugs and need to find a specific one later. If we open the debug file, you’ll see there’s a column on the left that shows minutes, seconds and milliseconds. It doesn’t show us the hour, but that’s located here in the filename for our debug logfile.

For a complete list of RightFax services that can be run in debug, please refer to the OpenText RightFax 16 EP4 Administrator Guide.

That’s it for enhanced debug options in RightFax 16.4

This is Michael with RightFax University saying thank you for watching and please visit us again. The RightFax University is a work under continual progress and we update often.