This log file contains the server version, build number, listener addresses, Java VM version and type, trace and debug messages, all other messages logged by the server, and component output.
Use any of these techniques to output messages to the EAServer log file from an EAServer component or application:
Enable debug, trace, or other properties as outlined in “EAServer traces”.
Call System.out.print from a Java component.
Call jaguar.server.Jaguar.writeLog method in a Java component. See the EAServer API Reference Manual for information.
Call JagServer::WriteLog from an ActiveX component. See the EAServer API Reference Manual for an example.
Call JagLog from a C or C++ component. See “Handle errors in your C component” in Appendix C, “Creating C Components,” in the EAServer Programmer’s Guide for information.
Utilize the ErrorLogging object for a PowerBuilder component. See “Error logging service” in the PowerBuilder Application Techniques manual for usage information.
The preconfigured server writes messages to the Jaguar.log file. Change the log file name for each new server that you create.
If you have changed the default configuration, or run user-defined servers, the log file may not be Jaguar.log. To change or verify the log file name:
In EAServer Manager, highlight the server, right-click and select Server Properties.
On the Log/Trace tab, enter the Log File Name and click OK.
The server may exit immediately without logging errors if there are errors in the server configuration; in this case, the server prints error messages to the shell window (console) where it was started.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
