Installation guide

CHAPTER 5 New features in EAServer 5.0
What’s New 31
Logging APIs
Regardless of the logging system you use, you can write messages to the log
using all of the methods supported in earlier versions of EAServer, such as:
•
System.out.println or Jaguar.writeLog from Java code running in the server
•
ErrorLogging.log from PowerBuilder® NVO components
•
JagLog from C or C++ components
•
IJagServer.writeLog from ActiveX components
In addition, if you use Log4j or the Java Logging system, you can log messages
from in-server Java code by calling the logging API directly.
Managing log profiles
“Configuring log profiles” in the EAServer System Administration Guide
describes how to manage log profiles.
Runtime monitoring enhancements
EAServer 5.0 includes these new runtime monitoring features:
• You can trace the SQL commands sent through connection caches. For
more information, see “SQL tracing properties” in Chapter 4, “Database
Access,” in the EAServer System Administration Guide.
• In EAServer Manager, HTTP and IIOP network monitoring shows thread
usage, and IIOP network monitoring shows the host and thread
information for current clients. For information on runtime monitoring
with EAServer Manager, see Chapter 11, “Runtime Monitoring,” in the
EAServer System Administration Guide.
• The monitoring APIs have been enhanced as follows:
•
Jaguar::Monitoring supports new keys to retrieve the configured values
for maximum HTTP threads and the maximum number of
simultaneous client threads, as well as the existing keys for current
thread usage.
•
Jaguar::Monitoring includes a new method, getConnectedUsers, that
returns information on IIOP clients.