Deploy portlet projects

 

+

Search Tips   |   Advanced Search

 

These instructions apply only when you are deploying to a WebSphere Portal server.

When you deploy a portlet project, the portlet is installed on the target WebSphere Portal server, but not placed on a page. You can use the Administrative functions of the target WebSphere Portal server to manage the placement of the portlets.

For limitations regarding firewalls and Linux, refer to Network considerations.

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

1. To open the Deploy Portlet Wizard, from the project explorer view, right-click the portlet project and select Deploy Portlet.

2. Select an existing server from the list or create a new one.

   Click Next.

3. On the Portlets page, define the Portlet Overwriting options:

   • If you do not want to be prompted, select Automatically overwrite portlets.

   • Select the option that you want to use for overwriting portlets:

     • Use the

       Update option to install the portlet, but preserve any customization data from the configure or edit modes.

     • Use the Remove & Deploy option to remove and reinstall the portlet. The removal process removes both the customization data and the portals from their pages. 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 if your portlet is not compatible with the old version.

4. Click Finish. Do not interrupt the deployment process.

   If you get an error about LTPA authentication, verify that the WAS and portal passwords are set in...

   wp_profile/ConfigEngine/properties/wkplc.properties

5. Once the portlet is successfully installed on the portal server, add the portlet to a portal page following these steps:

   1. Open a Web browser to the Administration page of the remote WebSphere Portal server.

   2. Click

      Portal User Interface | Manage Pages

   3. Select the page where you will add the portlet. Click on the Edit Page Layout button.

   4. Use the Add portlets buttons to add the portlet to the page, then click Done to save the changes.

If the project name, the filename, the file directory structure or the User ID for WebSphere Portal login name are too long there will be a XML Exception and the server attach will fail. You can ensure this does not happen by shortening the length of the filename, the fie directory structure or the User ID for WebSphere Portal login at the WebSphere Portal Server Attach server configuration.

When portlets contain references to other J2EE modules, such as enterprise beans or utility JAR files, there are special considerations for testing and deploying the portlets to remote WebSphere Portal servers.

 

Related concepts

Testing and deploying portlets that reference J2EE modules

 

Related tasks

Defining servers for publishing portlets

 

Related information

Publishing portlets

Network considerations

---