Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows
Deploying portlets in multiple clusters
This sections describes how portlet deployment works in a multiple cluster environment
How portlet deployment works
Even though portlets are a type of enterprise application, portlet deployment is typically done through WebSphere Portal Express itself, or if done directly to WebSphere Application Server, WebSphere Portal Express has to be notified separately. This is because WebSphere Portal Express maintains configuration information extracted from the portlet descriptor (portlet.xml) during portlet deployment.
If a portlet is deployed through WebSphere Portal Express, it first takes whatever configuration information it needs from the portlet’s WAR file, and then it generates a unique object ID for this portlet. WebSphere Portal Express then wraps the portlet’s WAR within an EAR definition, giving it a name based on the portlet’s display name, suffixed with the generated object ID. This guarantees that the portlet’s underlying enterprise application name is unique to this portal. In the event that this portal is clustered, the new enterprise application will be common to this cluster, but unique from any other cluster in the cell, because again the object ID is guaranteed to be unique.
If, however, the portlet was already deployed as part of the basic portal configuration during initial installation, then the object ID is likely to be the same as other portal installations based on the same version of WebSphere Portal Express. When multiple clusters are defined in the same cell based on this version, there will likely be many portlets that are common between the clusters, because they share the same object IDs.
The following sections describe how the portal administrator can control the circumstances where a portlet is shared or not between clusters, and when shared, how to control the update and deletion of these portlets.
- Deploying portets unique to a cluster
This section describes two different methods for deploying portlets unique to a cluster - Deploying portlets common to a cluster
This section describes two methods of deploying portlets common across clusters
Parent topic:
Setting up multiple clusters
Previous topic
Application sharing between clusters
Next topic
Updating portlets common across clusters