Upgrade

This section describes known upgrade issues and associated solutions.

On some Linux systems, the installer running "Upgrade in place" fails to start upgrade tool after clicking on the "Start Upgrade Wizard" button (6207337)

Description

This problem has been observed on several Linux systems, it is most common on Java Desktop System 2 but has also been observed on Red Hat 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.

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:

   as-install/bin/asupgrade --source as-install/domains --target 
   as-install --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://as-install/docs-ee/about.html

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

Self-signed certificate is not trusted during and after upgrade from 8.0 Platform Edition (PE) to 8.1 Enterprise Edition (EE) UR2 (6296105)

Solution

Remove the following entries from the target domain.xml (after the upgrade) and restart the server:

<jvm-options>-Djavax.net.ssl.keyStore=${com.sun.aas.instanceRoot}
/config/keystore.jks</jvm-options>-
<jvm-options>Djavax.net.ssl.trustStore=${com.sun.aas.instanceRoot}
/config/cacerts.jks</jvm-options>

(sbs-manual, sbs-installer) throws Server Instance server does not have a system connector named null (6545145)

Description

When upgrading from Enterprise Server 8.0PE to v2.1.1, an error is thrown saying the server does not have system connector named null, and invalid user information as seen in sbs-manual. Even after changing the hardcoded values, the same error message is seen.

Solution

You can only encounter this bug while upgrading from a 8.0 PE toEnterprise Server. The workaround is to upgrade to either 8.1, 8.2, or 9.0 and then upgrade to Enterprise Server.

Different domains are lost during upgrade when different build combinations are used (6546130)

Description

When performing an inplace upgrade, in cases where there are multiple domains in the source, the installer invokes upgrade tool even though the process is killed. This happens when it is invoked in GUI mode.

Solution

1. Install inplace in the CLI mode, and exit when the installer prompts you to select the upgrade tool at the end of installation process. This does not delete any of the domains present in the domains directory. Upgrade tool should be manually invoked from the bin directory.

2. When installing inplace in GUI mode, make a backup of the domains present in the domains root to prevent losing any domains in the process. At the end of the installation process, exit when the installer prompts you to invoke the upgrade tool. Copy any backed up domains into the domains directory if they have been lost. Launch upgrade tool manually to do an upgrade.

Solaris: pre-filled Master password in upgrade Tool is from Enterprise Server v2.1.1 and not from AS8.2 (6565825)

Description

When upgrading from AS 8.2, the master password from the 8.2 installation is not inherited in the target installation. This subsequently causes an authentication error at the next admin login.

Solution

The default admin password in Enterprise Server v2.1.1 is changeit. To avoid problems when logging in to the Enterprise Server after upgrading from 8.2, do one of the three following things:

• Change the 8.2 admin password to changeit before performing the upgrade.

• Do not accept the default admin password during the upgrade process, but instead explicitly enter the password you want to use.

• Log in to Enterprise Server v2.1.1 with the default password, and then immediately change it.

Localized Online Help for asupgrade GUI Does Not Exist (6610170)

Description

When running the asupgrade GUI in a language other than English, the online help for the GUI is not localized for the selected non-English language.

Solution

None at the time. Online help is scheduled to be localized in all non-English target languages.

Upgrade Tool deleted nodeagents directory when upgrade (reverse order) with multiple domains (6636871)

Description

After a side-by-side upgrade of a configuration that contains multiple domains, only the node agents of the last processed domain are present. This issue occurs because Upgrade Tool removes and re-creates the nodeagents directory in the target each time Upgrade Tool processes a domain.

Solution: To Preserve All Node Agents in a Side-by-Side Upgrade of Multiple Domains

1. After processing each domain, create a zip file of the nodeagents directory.
2. When all domains have been processed, unzip the files that you created.

   All node agents should now be present.

In-place upgrade does not update the index.html file of existing domain (6831429)

Description

While performing in-place upgrade, the index.html file of a domain that already exists is not replaced. It might still show the old version of the server. This index.html file could be replaced by the index.html file from SGES_BASE.

SGES_BASE/lib/install/templates/ee/index.html DOMAIN_DIR/docroot/index.html