Testing portlets on remote servers

You can test one or more portlet projects using a remote WebSphere® Portal server. For WebSphere Portal V6.0, or higher projects, you can configure a connection to a WebSphere Portal V6.0, or later server.

To test a portlet project on a remote server:

1. Configure the remote server.

2. From the Project Explorer view, highlight a portlet project and select

   Run | Run on Server.

3. To use an existing server definition, select

   Choose an existing server and choose a Portal server from the list.

   To define a new remote test server, see Defining remote servers for testing portlets.

4. Click

   Finish. After the server starts and the portlet is deployed, the Web browser that you defined opens to the URL of the portlet page on the remote server.

Note: If multiple users are testing portlets on the same server, ensure that the UIDs of the portlets are unique. Otherwise, when the portlet is installed on the server, it may replace the original portlet using that UID. To modify the UID of a portlet:

• For the IBM® portlet API, modify the UID using the portlet deployment descriptor editor. Refer to Customizing IBM API portlets

• For the JSR 168 or JSR 286 portlet API, the UID is constructed using the

  id attribute of the

  portlet-app element. If the

  id attribute is not specified, the UID is generated automatically using the login user ID and project name.

For more information about UIDs, refer to Guidelines for portlet application UIDs in the WebSphere Portal Information Center.

Note: An XML exception occurs and the server attach fails to start if the project name, the filename, the file directory structure, or the User ID for WebSphere Portal login name is excessively long. To correct this, shorten the length of the filename, the file directory structure, or the User ID for WebSphere Portal login on the WebSphere Portal server attach server configuration.

 

Related tasks

Testing and debugging portlets

---