Multiple cluster portlet deployment

Although portlets are a type of enterprise application, portlet deployment is typically done through HCL WebSphere Portal. If done directly to WebSphere Application Server, HCL WebSphere Portal must be notified. HCL WebSphere Portal maintains configuration information that is extracted from the portlet descriptor (portlet.xml) during portlet deployment.

If a portlet is deployed through HCL WebSphere Portal, it first takes whatever configuration information it needs from the portlet's WAR file. Then, it generates a unique object ID for this portlet. HCL WebSphere Portal then wraps the portlet's WAR within an EAR definition, giving it a name that is based on the display name, suffixed with the generated object ID. It guarantees that the underlying enterprise application name is unique to this portal. If this portal is clustered, the new enterprise application is common to this cluster, but unique from any other cluster in the cell. The object ID is guaranteed to be unique.

If the portlet was deployed during initial installation, then the object ID might be the same as other portal installations based on the same version of HCL WebSphere Portal. When multiple clusters are defined in the same cell that is based on this version, many portlets are common between the clusters. These portlets share object IDs.

Note: When we deploy and activate portlets, while we are logged in to HCL WebSphere Portal, we must log out and log back in to see the updated status for the portlets.

Parent topic: Manage portlets in the cluster