When portlets are published to a server attach server, a Portlet
Preview page is created on the remote server. Each portlet is
placed on its own page under the Portlet Preview page. Each portlet's page
is named user/portletname where user is
the user ID that is defined in the server attach server configuration, and portletname is
the portlet project name.
In the previous versions of WebSphere Studio,
this function was called portlet preview.
To test a portlet project
on a 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 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.