Upgrade Utility

This section describes known Upgrade utility issues and associated solutions.

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

Description

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)

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 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.

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

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>

Port conflict after upgrading Application Server from JES2 to JES5

Description

When updating from Application Server 7.x to 8.2, you may encounter a port conflict between the old and new installations, most likely with the default ports of 8080 and 8181.

Solution

Change the ports used in Application Server 8.2 to resolve the port conflict.

Derby database used by samples script is created under wrong location. (ID 6377804)

Description

There are two aspects to this bug:

1. When sample application setup scripts that use the Derby database are run, the Derby database gets created under the current directory or under <install_root>/bin.

2. The sample build Ant script creates a password.txt file that stores the admin password file under current directory, which will not be writable in non-root and sparse zones scenarios.

Solution

1. Derby database location – Use the --dbhome option with the start-database command to create the database at the value specified for --dbhome. For example, the following is the asadmin command syntax for start-database.

   start-database [--dbhost 0.0.0.0] [--dbport 1527] [--dbhome db_directory] [--echo=false] [--verbose=false]

2. Location of the password.txt file – By design, the samples directory is expected to be writable since all the build commands include the creation of a password.txt file in that directory. Be sure to install a working copy of the samples in a writable location.

LoginException during upgrade from 8.0UR1PE to 8.2EE; upgrade process aborts (ID 6445419)

Description

This problem occurs when you run the upgrade installation using admin credentials other than the defaults.

Solution

When performing a side-by-side upgrade using the file based installer for 8.xPE to 8.2EE, use the following admin credentials for the new Application Server:

• admin user: admin

• admin password: adminadmin

• master-password: changeit

After performing the upgrade, you can change these passwords as needed.

Upgrade Tool fails to detect existing but invalid directory input for Source Directory field (ID 6460122)

Description

The Upgrade Tool fails to detect an existing but invalid directory input for Source Directory field, and gives the impression that directory configuration is correct.

The expectation is that an “Invalid directory” message should pop up when an incorrect path is entered for the Source Directory. An invalid directory message correctly pops up if /opt/SUNWappserverEE81UR2/ is entered for the Source Directory. However, when /opt/SUNWappserverEE81UR2/domains is entered, the tool continues with the upgrade process without warning, even though the path is invalid. This issue is similar to ID 6440710, except that the behavior differs depending on the input value.

Solution

When upgrading from Application Server 7 or 8.x to Application Server 8.2, the source directory must first be seeded with the value recommended in the documentation: domain root for in-place and domain directory for side-by-side upgrades.

Should invalidate Admin user/password name for semi-column (;) character (ID 6473341)

Description

The Application Server Enterprise Edition 8.2 installation does not allow special characters in the admin user name. Domain creation will fail if any special characters are used. Note, however, that the admin password can have special characters.

Solution

When upgrading from Application Server 7 to Application Server 8.2, verify that the admin user name does not contain any special characters.

Steps are missing for successful side-by-side upgrade. (6898037)

After upgrading from the older version of Application Server, verify the following under the upgraded installation (target-installation) location:

1. Domain directory is in the source directory.

2. Node agent is under node-agent directory as created in the source installation.

   cd target-installation/nodeagents/upgraded-node/agent/config

3. Check the value of the agent.das.port property in the das.properties file before starting the node agent for the first time. Perform this check on the das.properties file on the upgraded installation. The value of the agent.das.port property must reflect the same value as the jmx-connector port defined in the domain.xml file on the source installation from which the domain is upgraded.

4. Check the value of the agent.bind.status property in the nodeagent.properties file before starting the node agent for the first time. Perform this check on the nodeagent.properties file on target-installation. The value of the agent.bind.status property must BOUND. Edit the agent.bind.status property in the nodeagent.properties file on the source installation.

If you are upgrading side-by-side on Windows:

After upgrading the domain, if the upgraded-node has not been created under target-installation/nodeagents directory as in the source installation:

1. Go to the target-installation/bin directory.

2. Manually create the node agent that has the same name as in the source installation with the admin port specified in the create-node-agent command.

3. Perform the additional steps above.

4. Start the node agent.