12.4 The Server Logger
Generally, you need take no additional steps to prepare for server-side logging. All HydraExpress services in a given Agent share the same logger, and by following the procedures outlined in Section 12.3, log messages are written to the default log file, webservices.log, as described in that section.
The server's <serviceName>handlers.xml file cannot be used to configure logging as can the client's, though you can explicitly change to a non-default logger programmatically in your code. Note, however, that this is only recommended for debugging and troubleshooting since any change you make to logging will affect all other active services in the container.
For example, perhaps you wish to set the log level to Info in order to trace through some code containing Info level log messages, which are ignored when the log level is set to the default value of Error.
rwsf::DefaultLogger* myLogger = new rwsf::DefaultLogger; //1 myLogger->setLogLevel(rwsf::CallInfo::Info); //2 rwsf::HandlerManager::setLogger(myLogger); //3
| //1 | Create a new default logger. |
| //2 | Set the log level on the new logger to Info. |
| //3 | Set the handler manager to use the new logger. The rwsf::HandlerManager class takes ownership of the logger along with responsibility for deleting it. |
Note that setting the filename is optional. If it is not set explicitly, log messages continue to be written to the default log file, webservices.log. If you wish to change the filename, the code shown in Section 12.3 includes an example.
Be aware that setting the logger via rwsf::HandlerManager sets the same logger for all Web services hosted in the Agent.
©2004-2007 Copyright Quovadx, Inc. All Rights Reserved.
Quovadx and Rogue Wave are registered trademarks of Quovadx, Inc. in the United States and other countries. All other trademarks are the property of their respective owners.
Contact Rogue Wave about documentation or support issues.