SOA Governance and API Management : Administering Integration Server : Setting Up the Server Log : Overview of the Server Log
Overview of the Server Log
The Integration Server server log contains information about operations and errors that occur on Integration Server, such as the starting of Integration Server subsystems and the loading of packages belonging to Integration Server or other webMethods products. Entries are written to the server log by Integration Server's major subsystems, called facilities. For example, the Integration Server package facility writes server log entries when it loads and unloads packages, the Integration Server flow manager facility writes server log entries when it processes a flow service, and Integration Server's HTTP ports write server log entries when they receive requests. Entries are also written to the server log by facilities for individual products that are installed on Integration Server, such as Trading Networks Server or adapters. Below is an excerpt from a sample server log.
2009-04-22 17:20:45 EDT [ISS.0028.0012I] WmRoot: Startup service
(wm.server.soap:init)
2009-04-22 17:20:46 EDT [ISS.0028.0012I] WmRoot: Startup service
(wm.server.dbalias:initRepoAlias)
2009-04-22 17:20:46 EDT [ISS.0028.0012I] WmRoot: Startup service
(wm.server.tspace:init)
2009-04-22 17:20:46 EDT [ISS.0028.0012I] WmRoot: Startup service
(wm.server.ws:init)
2009-04-22 17:20:46 EDT [ISS.0028.0012I] WmPublic: Startup service
(pub.ldap:init)
2009-04-22 17:20:46 EDT [ISS.0028.0012I] WmPublic: Startup service
(pub.storage:startup)
2009-04-22 17:20:46 EDT [WmSharedCacheSC.config.0595I] Reading cache
configuration: distributedCache
2009-04-22 17:20:50 EDT [ISS.0028.0012I] WmVCS: Startup service
(wm.server.vcsadmin:startup)
2009-04-22 17:20:50 EDT [VCS.0132.0050I] VCS package initializing
2009-04-22 17:20:50 EDT [ISS.0028.0012I] WmVCS: Startup service
(wm.server.vcsui:addSolutions)
2009-04-22 17:20:50 EDT [ISS.0028.0012I] WmART: Startup service
(wm.art.admin:startup)
2009-04-22 17:20:50 EDT [ISS.0028.0012I] WmXSLT: Startup service
(wm.xslt.Admin:startup)
2009-04-22 17:20:50 EDT [ISS.0028.0012I] WmAssetPublisher: Startup service
(wm.server.metadata.admin:startup)
2009-04-22 17:20:50 EDT [ISS.0138.0052I] Asset Publisher package initializing
2009-04-22 17:20:50 EDT [ISS.0028.0012I] WmISExtDC: Startup service
(com.wm.isextdc.PkgInit:init)
2009-04-22 17:20:50 EDT [ISS.0028.0012I] WmARTExtDC: Startup service
(com.wm.artextdc.pkginit:init)
2009-04-22 17:20:50 EDT [ISP.0046.0012I] Enabling HTTP Listener on port 9999
2009-04-22 17:20:50 EDT [ISP.0046.0012I] Enabling HTTP Listener on port 5555
2009-04-22 17:20:50 EDT [ISP.0046.0012I] Enabling HTTP Listener on port 6666
2009-04-22 17:20:50 EDT [ISS.0098.0021I] Persistent Trigger Output Dispatcher
started
2009-04-22 17:20:50 EDT [ISS.0098.0021I] Volatile Trigger Output Dispatcher
started
2009-04-22 17:20:50 EDT [ISS.0098.0027I] PersistenceManager started all Stores
2009-04-22 17:20:50 EDT [ISS.0025.0036I] Dispatcher started
2009-04-22 17:20:50 EDT [ISS.0025.0005I] Port Manager started
2009-04-22 17:20:50 EDT [ISS.0025.0013I] Cache Sweeper started
2009-04-22 17:20:50 EDT [ISS.0014.0002C] Initialization completed in 21 seconds.
2009-04-22 17:20:51 EDT [ISS.0025.0016I] Config File Directory Saved
For a list of available facilities in Integration Server, see Server Log Facilities.
By default, all facilities write to the server log, and the facilities write log entries about critical, error, warning, informational, and debug-related situations. You can have only selected facilities write to the log, and you can increase or decrease the amount of data the facilities provide. This flexibility is useful for troubleshooting. For example, you might temporarily increase the level of detail written to the server log to help uncover the cause of an Integration Server error or performance problem, and return to a lower level once the problem is resolved. You can also override the amount of information to include in the server log for a particular Integration Server session.
By default, Integration Server queues log entries written by its facilities in memory, then uses a background thread to write them to the server log. You can change that property so that facilities write directly to the server log. Using a background thread improves Integration Server performance, but writing directly causes the entries to appear in the server log more quickly.
Integration Server always writes server log entries to flat files; you cannot store the server log in a database. By default, Integration Server writes server log entries for the current day (defined as midnight to midnight) to the server.log file. However, you can configure Integration Server to rotate the srever.log file by size instead of by day. For more information, see Configuring the Server Log to Rotate Based on Size.
When rotating the server log file, either by day or by size, Integration Server renames the current server.log file to have the archive file name and starts a new server.log file. The archive file names include the date (yyyymmdd) on which the log entries were originally written.
By default, all log and archive files are stored in the Integration Server_directory \instances\instance_name\logs directory. For information about changing the location of the server.log file, see Changing the Default Server Log Location
You can override the location of the server log files for a particular session.. For more information about overriding the location of the server log file or the logging levels for a session, see Overriding Logging Level and Server Log Location for a Session.
Copyright © 2015- 2016 Software AG, Darmstadt, Germany.
Product LogoContact Support   |   Community   |   Feedback