Type: New Feature
Affects Version/s: 2.2.0
Fix Version/s: 2.2.0
Implement a second, Versioned Portlet Application Manager for clustered environments
We are running into limitations with the NodeManager-based cluster support when deploying to clusters with replicated databases as well as replicated app servers.
The default PAM (Portlet Application Manager) is not-appropriate for many deployments of the portal. I am implementing a second version of the PAM, with no listeners,
and a simpler deployment algorithm based on a version number supplied in the jetspeed-portlet.xml metadata
If this field is not found, or if it is equal to or less than the version in the database, then the PA will not be deployed.
This will allow for dropping in 2..n PAs in a cluster, without re-registering. The problem with re-registering is that the registry algorithm deep deletes the old PA def from the database,
create a new PA, with all new OIDs, invalidating all other PAs and portlets on other nodes in the cluster.