Define servers for testing portlets
To test, debug or profile a portlet project, define a local or a remote server. Local servers are called Test Environments within the workbench. Remote servers (called server attach) are external to the workbench, either on the same system or another system .
You can define a server for your project within the Run (Test), Debug, or Profile on Server wizards; or you can define it using the New Servers wizard. In either case, you select a local or a remote server and configure it appropriately.
Note: To use a local WebSphere Portal v5.1 server, install the WebSphere Portal v5.1 Test Environment using the WebSphere Portal 5.1 CD-ROM provided with Rational Developer. Before using the server, configure Rational Developer to use the WebSphere Portal v5.1 Test Environment. See Configuring the WebSphere Portal 5.1 Test Environment.
- To define a server for your portlet project within the Run, Debug or Profile on Server wizards:
- From the Project Explorer view, highlight a portlet project. Select one of the following options:
- Run > Run on Server to test the project.
- Debug > Debug on Server to debug the project.
- Profile > Profile on Server to profile the project.
The Server Selection dialog box opens.
- To use an existing server, select Choose an existing server and highlight a server from the list. Click Finish.
- To define a new server, select Manually define a server and choose one of the following:
- To define a local Test Environment server, follow the steps in Configuring local servers for testing portlets.
- To define a remote Server Attach server, follow the steps in Configuring remote servers for testing portlets.
- To define a server using the New Servers wizard:
- From the Servers view, right-click and select New > Server.
- To define a new server, choose one of the following:
- To define a local Test Environment server, follow the steps in Configuring local servers for testing portlets.
- To define a remote Server Attach server, follow the steps in Configuring remote servers for testing portlets.
- Select the projects that are associated with the server using the instructions in Associating servers with projects
- An EAR project named wps is created when a test environment configuration is saved and a portlet project exists in workspace. If you plan to test, debug, or profile your portlet project locally, do not modify the wps project once it is created. When creating a project, do not name it wps.
Configuring local servers for testing portlets
Configuring the WebSphere Portal 5.1 Test Environment
Configuring remote servers for testing portlets
Preparing WebSphere Portal for remote testing and debugging
Associating servers with projects