Testing, debugging, or profiling portlets
You can test, debug or profile a portlet project using the workbench. All three of these tasks involve running a portlet on a server, whether it's in the local test environment, or on the remote server (i.e. server attach).
Debugging allows you to set breakpoints and step through the code to diagnose problems. Profiling provides code analysis tools. To debug or profile on a server, the server must be started in debug or profile mode. The profiling function requires that the Rational Agent Controller be installed and configured on the machine the server is running on. To test, debug or profile a portlet on a local server, install the WebSphere Portal V5.0 test environment from the Rational Application Developer launchpad.
To test, debug or profile a portlet project,...
- Set up the environment for testing, debugging or profiling
- Choose one of these actions:
- Testing portlets locally
- Testing portlets remotely
- Debugging portlets locally
- Debugging portlets remotely
- Profiling portlets (for local test environments)
To run or debug portlet projects which refer to other projects in your workspace, refer to Referring to other projects.
Related concepts
Creating portlets and portlet projects
Related tasks
Defining servers for testing portlets
Configuring Web browsers and device emulators