Tab navigation
- Overview
- Getting started
- Documentation
- Support- selected tab,
Web services server administration
Any administration problems, such as Web Admin GUI for IBM i problems or Web service deployment problems, should be logged in the Web administration server logs.
For V5R4, the log files are in directory /qibm/userdata/os/osgi/lwisysinst/admin2/lwi/logs. For V6R1 and subsequent releases, the log files are in directory /qibm/userdata/os/osgi/lwisysinst/admin/lwi/logs.
The following files should be examined:
- lwistderr.txt: This file contains the output from stderr when the Web administration server is running. This file is cleared each time the LWI server is started so it only contains information about the last time the server was run.
- lwistdout.txt: This file contains the output from stdout when the Web administration server is running. This file often contains debug information. This file is cleared each time the LWI server is started so it only contains information about the last time the server was run.
Web service runtime
View the logs for the server to determine if there is any information that may help in debugging any problems you may encounter in a deployed Web service or within the server itself. You can view the server logs by clicking on the View Logs link from the administrative panel when administrating the Web services server.
If there is a problem with a deployed Web service when it is invoked, you can turn on Java toolbox tracing. This can be done by using the Web Administration GUI and selecting the Server Tracing link for the Web services server in which the Web service is deployed. See the article IBM Systems Magazine: Power Under the Hood (link resides outside of ibm.com) for more information.
One thing to note about Java toolbox tracing and that is the tracing properties affect all applications or services running in the server. That is, tracing will be done for all services and log data will be written to one log file. So when debugging a service using Java toolbox trace, it is best to isolate the service in its own server or ensure that the other services are not invoked by any client.
