(4756/4809) Portal Server 7.1u2 cohabitation issue on single node

Description

After migrating from Access Manager 7.1.1 to OpenSSO 8.0, Portal Server 7.1u2 works properly when deployed on a separate node, but does not work if Portal Server and Access Manager are deployed on the same node. Portal Server fails to properly initialize, and the following error is shown in the server log:

[#|2009-03-23T19:06:37.004+0100|SEVERE|sun-appserver2.1|javax.enterprise.system.
container.web|_ThreadID=10;_ThreadName=main;_RequestID=00e6500a-e66c-42f4-9f06-6
afdace1a2d8;|WebModule[/surveys]PWC1275: Exception sending context initialized e
vent to listener instance of class com.sun.faces.config.ConfigureListener
java.lang.NoClassDefFoundError: com/iplanet/sso/SSOException

The problem is that OpenSSO Enterprise and the AM SDK component of Access Manager cannot coexist in the same web container (Application Server/GlassFish), and Portal Server requires the AM SDK component.

See the following URLs for more information about this bug:

4756
4809

Solution

OpenSSO does not support the package-based AM SDK. There is not a direct upgrade path for AM SDK-based installations. The recommended workaround is as follows:
1. Leave Portal Server/AM SDK running on Application Server 8.2
2. Install new GlassFish Enterprise Server v2.1 and deploy OpenSSO with /amserver to this GlassFish instance pointing to same Directory Server Enterprise Edition as Access Manager 7.1.
3. Reconfigure Portal Server/AM SDK to point to OpenSSO on a different port.