Testing, debugging, or profiling portals

You can test, debug or profile a portal project using the workbench. All three of these tasks involve running a portal on a server, either on the test environment within the workbench (local), or on separate server (remote, or 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 portal on a local server, install the WebSphere Portal V5.0 test environment from the Rational Application Developer launchpad.

To test, debug or profile a portal project,...

1. Set up the environment for testing, debugging or profiling following the instructions in Configuring test and debug environments for portal projects.

2. Choose one of these actions:
   • Testing portals locally

   • Testing portals remotely

   • Debugging portals locally

   • Debugging portals remotely

   • Profiling portals

 

Related concepts

Portal projects

 

Related tasks

Customizing portal sites
Defining servers for testing portals
Configuring Web browsers and device emulators
Publishing portals