Apart from the debugging technique available in developer studio outlined here. You can enable java logging by using the webclientlog logging handler found at [IFS_HOME]\instance\[INSTANCE_NAME]\conf\j2ee-logging.properties
Errors in the client that points out an included JS file are hard to debug. For this reason, there is a flag in webclientconfig.xml 'AUDIT/__DEBUG/SEND_JS' that controls whether the IFS Web Client generates <script> tags that just points to the included files, or if the include script files should be sent in the page to the browser.
The IFS Web Client makes sure that it's not possible to reuse expired pages. When the back button is pressed in the browser, the page will be reloaded. During the development process there are situations when you wish to see older requests. This is possible by using the flag AUDIT/__DEBUG/CONFIRM_ON_RELOAD in webclientconfig.xml If the function is turned on you'll get a dialog box asking you whether you wish to reload the page or not.
The IFS Web Client uses cookies for several of reasons, such as global variables, information that tells us if the page has expired, information about 'redirect' and user management etc. You can analyze these cookies by using functionality controlled by the parameter AUDIT/__DEBUG/SHOW_COOKIES in the webclientconfig.xml . This parameter can display two extra buttons at the bottom of every page, and by pressing them you'll be presented with the content of the cookies, in encoded our decoded form respectively.
To study error messages and expired pages you need to know the unique identifier (page id) that every page (request) receives. You can display this identifier with the parameter AUDIT/__DEBUG/SHOW_PAGE_ID in webclientconfig.xml .
Further debugging possibilities are available with separately delivered tool called debug.exe that currently only run under Microsoft Windows operating system.
Sometimes it is useful to be able to debug JavaScript code. Given below are the necessary steps to enable debugging for JavaScript in IE browsers.