Upgrade

This section describes known issues and associated solutions related to upgrading and using the Upgrade Tool.

Domains created in custom-path other than install_dir/domains directory are not upgraded directly while upgrading from Application Server Platform Edition 8 to Application Server Platform Edition 9. (ID 6165528)

When running the Upgrade Utility and identifying the install_dir as the source installation directory, the upgrade process upgrades only those domains that are created under install_dir/domains directory. Domains created in other locations are not upgraded.

Solution

Before starting the upgrade process, copy all the domain directories from their different locations to the install_dir/domains directory.

The installer running “Upgrade in place” fails to start upgrade tool on some Linux systems after clicking on the “Start Upgrade Wizard” button. (6207337)

This problem has been observed on several Linux systems, it is most common on Java Desktop System 2 but has also been observed on RedHat distributions.

After clicking the Start Upgrade Tool button on the final installer screen, the installer fails to launch the upgrade tool to complete the upgrade process, and hangs indefinitely, not returning the command prompt.

Solution

This issue is not encountered if command line installation mode is used to run upgrade in place.

To use command line installation mode

1. If you ran upgrade in place in GUI mode and encountered this problem, exit the installer by pressing Ctrl+C in the terminal window in which the installer was started.

2. Start upgrade tool from the terminal window, using following command:

   install_dir/bin/asupgrade --source install_dir/domains --target install_dir --adminuser adminuser--adminpassword adminpassword --masterpassword changeit

   adminuser and adminpassword should match the values used for the installation you are upgrading.

3. When the upgrade tool completes the upgrade process you can also start the browser and enter following URL in order to review About page:

   file://install_dir/docs/about.html

   If you also selected the installation option to register the product, follow the link to registration page available on product About page.

Upgrade Tool does not transfer all JVM options (ID 6409650)

The Upgrade Tool does not transfer JVM options, such as those related to stack size and heap size because they should retain the values specified during installation. This is because the values for these options are likely to be set for specific reasons for the current version of the product. The Upgrade Tool will log a message indicating which options have not been transferred.

Copy static documents in docroot directory after upgrade (ID 6409641)

After you upgrade your Application Server installation, copy any static documents in the docroot directory to the new docroot directory. If you did an in-pace upgrade, copy the documents from the backed-up domain directory under the domaindir of the installation.

Must close Application Server files when running Upgrade Tool on Windows

While running Upgrade Tool on Windows, you must close all files in the installation being upgraded. If a file is left open, then the Upgrade Tool has been observed to hang.

Username Token not encrypted if we use XWSClientProvider and XWSServerProvider. (ID 6409652)

To use the XWSCLientProvider and XWSServerProvider in an upgraded Application Server , you must modify the deployment descriptors of the applications that use these providers, to refer to XWSClientProvider and XWSServerProvider.

The deployment decriptors that you must change are sun-web.xml and sun-ejb-jar.xml. The Upgrade Tool logs a message in the upgrade log if it finds ClientProvider and ServerProvider in the sun-web.xml or sun-ejb-jar.xml.