For further details on Rich UI, see "Rich UI debugging."
To set general preferences for the EGL debugger:
These files are the result of an intermediate step in the build process. If EGL does not find the IR files, a warning window opens that states that the source files for the program could not be found. To suppress this message, clear the Prompt when a called program's source cannot be found preference, which is selected by default. In the warning window, there is a Do not display this message in the future check box. If you select this option, EGL automatically clears the Prompt when a called program's source cannot be found preference.
The user ID and password that are used for remote calls while debugging are separate from the user ID and password that are used to access a SQL database.
The class path additions might not be visible to the application server test environment, but you can add to the classpath of that environment by working on the Environment tab of the server configuration.
Use the buttons to the right of the Class Path Order section.
The user ID and password that are used to access an SQL database are separate from the user ID and password that are used to make remote calls while debugging. To set the user ID and password for remote calls while debugging, see the instructions in this topic for setting preferences in the debugger.
The EGL debugger uses a port to establish communication with the Eclipse workbench. The default port number is 8345. If another application is using that port or if that port is blocked by a firewall, set a different value, as described in the instructions in this topic for setting preferences in the EGL debugger.
When you debug a program that calls another program or a service, the debugger can execute either the EGL source code or the generated code for the called program or service. By default, the debugger uses the EGL source code. To use the generated code, add an entry to the Debug behavior mapping table.