Publishing portlets

You can publish your portlets to a WebSphere Portal server either manually or automatically. Publishing automatically is called deploying. Manually publishing consists of exporting a portlet project as a WAR file, then installing it on a WebSphere Portal server using the WebSphere Portal administrative tools.

Exporting a portlet project is recommended for publishing to a staging or production server.

Deploying a portlet project is recommended for publishing to a test, integration or staging server. If there is a firewall between your Rational Application Developer system and your WebSphere Portal server system, which blocks incoming requests, the remote deployment of the portlet will fail, and you will need to use the export method. See Deploying portlet projects for suggestions on configuring your firewall for deployment. Also, if the WebSphere Portal server is on a Linux system, the network settings must be configured so that the real IP address is returned, instead of the local host IP address of 127.0.0.1. This is a common problem with Java networking on Linux systems.

To publish your portlet project, choose one of the following actions:

• To export your portlet project to a WAR file, follow the instructions in Exporting and installing portlet projects.

• To deploy your portlet project,...
  1. Define your target server using the instructions in Defining servers for publishing portlets.

  2. Deploy your portlet project using the instructions in Deploying portlet projects.

 

Related tasks

Defining servers for publishing portlets
Deploying portlet projects
Exporting and installing portlet projects
Publishing portals