Deploying portlet projects

The capability described in this topic is available only when you are deploying to a WebSphere Portal v5.0 server. To deploy portlets to a WebSphere Portal v5.1 server, export portlet projects to WAR files, and then install them to WebSphere Portal v5.1 using the WebSphere Portal administration interface.

To deploy a portlet project to a WebSphere Portal server, follow the steps below.

  1. From the Project Explorer view, right-click the portlet project and select Deploy Portlet. The Deploy Portlet wizard opens.

  2. Select an existing server from the list or create a new one. Follow the instructions in Defining servers for publishing portlets.

  3. Press Next, or press Finish if you do not need to change the defaults in the Portlet Overwriting section, which are to prompt before overwriting portlets, and to overwrite portlets using the update method.

  4. On the Portlets page, define these options for Portlet Overwriting:

    1. Select Automatically overwrite portlets to replace existing portlets without warning.

    2. Select the Update or the Remove & Deploy option.

      • Use the Update option to install the portlet, but preserve any customization data that was added in the configure or edit modes.

      • Use the Remove & Deploy option to remove and reinstall the portlet. During the removal process, all customization data is also removed, and portlets are removed from any pages where they were already placed. The install process only installs portlets, but does not restore customization data nor place portlets on pages. Use this option if you want to clean up portlet settings, or your portlet is not compatible with the old version.

  5. Press Finish. Do not interrupt the deployment process.

For limitations regarding firewalls and Linux, refer to Configuring networks for deployment.

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 at the WebSphere Portal Server Attach server configuration.

 

Related tasks

Defining servers for publishing portlets