Logging

To facilitate the troubleshooting of runtime issues, you can review logs from both EAServer and Service Container in different ways.

By default, Service Container information automatically gets logged to the EAServer as well. Depending on whether or not you want to view your Service Container details in context with EAServer log information, you can choose which log is most appropriate for your troubleshooting analysis. Remember, you can review Service Container information in the EAServer logs only after you deploy the service.

Additionally, to analyze information at the logic level of a business process, consider enabling enhanced logging to complement line-by-line troubleshooting at the package level. Because of the additional overhead required to process and capture this information, only temporarily enable enhanced logging to review the logic and performance of these processes. Once you have accomplished this task, disable enhanced logging to avoid degrading the performance of Service Container.

Note: If you enable enhanced logging, use a text editor to open the log file rather than from a console or log viewer. Text editors render the XML elements more clearly.

Setting Service Container Log Properties
Adjust the log properties for viewing service container runtime information that gets recorded to the <installation directory>\log\SC55.X.log file.
Opening EAServer Log Files
To troubleshoot problems with services, EJB components, EAServer runtime, HTTP requests, servlet engine, or the EAServer Web console, review the EAServer log files.
Viewing EAServer Log Files with the Log Viewer
Troubleshoot problems with services, EJB components, EAServer runtime, HTTP requests, servlet engine, or the EAServer Web console by reviewing the EAServer log files.
Opening Service Container Log Files
To troubleshoot problems with service invocation, service deployment, business process engine variable assigns, final business process output messages, intermediate steps in the execution of business processes, or to debug, review the service container log files.
Viewing the Service Container Log File with the Log Viewer
To troubleshoot problems with service invocation, service deployment, business process engine variable assigns, final business process output messages, intermediate steps in the execution of business processes, or to debug, review the service container log files.
Disabling Service Container Logging to EAServer Log Files
Console logging for Service Container is enabled, which ensures that runtime errors and "unable to load class" errors are always captured in both Service Container and EAServer logs by default. In certain situations, you might need to temporarily disable console logging for Service Container so that you only get EAServer log information in the EAServer console logs.
Enhanced Logging XML Reference
Enhanced logging captures the step-by-step logic of a business process rather than at the package level (that is, captured by the log level you choose in the <installation directory>\EAServer\bin\logging.properties ).