Itemized Upgrade Issues

Localization packages for Access Manager, Application Server, and Message Queue are not upgraded by the installer (6446805)

When upgrade Access Manager, Application Server, or Message Queue, the installer does not upgrade the localization packages even if you choose the "Install multilingual package(s) for all selected components" option.

Solution Remove existing localization packages before upgrading, using the instructions provided in the Sun Java Enterprise System 5 Upgrade Guide for UNIX.

JSP compilation errors in Application Server after other components are upgraded to Java ES 5 (6388329)

After upgrading any Java ES component to Java ES 5 on a system running Release 3 or Release 4 Application Server (version 8.1), Application Server reports errors when you compile JSP pages.

Solution Upgrade Application Server to Java ES 5, or apply the following patch to Application Server 8.1:

• On Solaris: 119166–17

• On Linux: 119168–17

On Linux, applications deployed to Application Server throw Java.security.AccessControlException after other components are upgraded to Java ES 5 (6517722)

After upgrading a Java ES component to Java ES 5 on a Linux system running Application Server, attempts to start some deployed applications throw Java.security.AccessControlException. This problem arises because the location of antchanged in Java ES 5

Solution Upgrade Application Server to Java ES 5, or follow these steps:

1. In Application Server's config/asenv.conf file, change the value of AS_ANT_LIB from "/opt/sun/lib" to "/opt/sun/share/lib".

2. Restart Application Server.

Upgrading Portal Server 7.0 deployed to Web Server follows an unconventional sequence (6507069)

When upgrading Portal Server IFR (Interim Feature Release) 7.0 2005Q4 deployed in Web Server, you must upgrade components in a nonstandard sequence. See the Sun Java Enterprise System 5 Upgrade Guide for UNIX for more information.

Monitoring Framework 1.0 with Instant Messaging needs upgrading if enabled (6515859)

If you enabled the monitoring functionality of Instant Messaging in Java ES 2005Q1 or 2005Q4, you will need to manually upgrade your properties file after you upgrade to Java ES 5.

Solution After you have upgraded your Instant Messaging instance on a given host, edit the new mfwk.properties file to include the configuration parameters you wish to preserve from your old agent.properties file.