Correcting Potential Upgrade Problems

This section addresses issues that could occur during an upgrade to Application Server 9 and explains how you can correct them.

To Transfer JVM Options

When you upgrade from a previous version of the application server, transfer of the previous configuration is required. Since the target configuration files may have new parameters and new preconfigured features, copying the old configuration files to the new server installation is not possible. The values of the old configurations must be transferred to the Application Server 9 configuration format.

The following JVM options are not transferred from the source to the target installation:

• Dorg.xml.sax.driver

• Dcom.sun.jdo.api.persistence.model.multipleClassLoaders

• Djava.util.logging.manager

• Dcom.sun.aas.imqLib

• Dcom.sun.aas.imqBin

• Dcom.sun.aas.webServicesLib

• Dcom.sun.aas.configRoot 8. Xmx<...>m

The options that are not transferred are listed down in the upgrade log. The user can manually change such attributes, in the configuration file, if needed.

To Upgrade Additional HTTP Listeners Defined on the Source Server to the Target PE Server

If additional HTTP listeners have been defined in the PE source server, those listeners need to be added to the PE target server after the upgrade:

1. Start the Admin Console.

2. Expand Configuration.

3. Expand HTTP Service.

4. Expand Virtual Servers.

5. Select <server>.

6. In the right hand pane, add the additional HTTP listener name to the HTTP Listeners field.

7. Click Save when done.