Installation

Web Server or Application Server fails to start after Java ES 5 Update 1 installation because of AMLController filter. (# 6604128)

Solution:

Set the container JVM Class path.

1. Edit the following file:

   On Application Server: Application-Server-domian-instance-dir/config/server.xml

   On Web Server: Web-Server-domian-instance-dir/config/domain.xml

2. Search for java-config classpath-suffix= ".

3. Change the following line: /wireless_rendering.jar:/wireless_rendering_util.jar:/ obile_services.jar:/ ccpp-1_0.jar:/ccpp-ri-1_0.jar:/jena-1.4.0.jar:/rdffilter.jar:/locale to:

   /opt/SUNWma/lib/wireless_rendering.jar: /opt/SUNWma/lib/wireless_rendering_util.jar :/opt/SUNWma/lib/mobile_services.jar: /opt/SUNWma/lib/ccpp-1_0.jar:/opt/SUNWma/lib/ ccpp-ri-1_0.jar:/opt/SUNWma/lib/jena-1.4.0.jar: /opt/SUNWma/lib/rdffilter.jar:/opt/ SUNWma/lib/locale

Patch needs to be applied as a root user. (#5080029)

Solution:

If you have followed any post-installation configuration to run Portal Server as a non-root user, you need to remove these changes, and run Portal Server as root before applying the patch.

After successfully applying the patch, follow the post-installation procedure to run Portal Server as a non-root user .

If Portal Server and Access Manger are installed on two different machines, creation of discussions and searching fail. (#6534761, 6534777)

Solution:

After upgrading Portal Server 7.1 to Portal Server 7.1 Update 2, restart the common agent container.

On the Solaris platform:

/usr/lib/cacao/lib/cacaoadm stop /usr/lib/cacao/lib/cacaoadm start

On the Linux platform:

/opt/sun/cacao/bin/cacaoadm stop

/opt/sun/cacao/bin/cacaoadm start

Restarting of the common agent container is required after creating a new portal. (#6521384)

Example:

In the Linux platform, if you use Application Server 8.2 as the web container for Portal Server, after creating a new portal, restart the common agent container.

/opt/sun/cacao/bin/cacaoadm stop /opt/sun/cacao/bin/cacaoadm start

If Portal Server is installed on an Application Server cluster, to uninstall Portal Server, you need to delete the Portal Server instance on every node. (#6494878)

Solution:

Do the following:

1. Start DAS on each secondary node.

2. Delete Portal Server instances on each secondary node by running the psadmin delete-instance command.

3. Delete Portal Server instance on the primary node.

4. Run the uninstall command to uninstall Portal Server.