Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Update 2 Release Notes

- Previous: Security
- Next: Web Container

# Upgrade Utility

This section describes known Upgrade utility issues and associated solutions.

Bug ID | Summary
--- | ---
6165528 | 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.1. 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.
2. 6207337 | On some Linux systems, the installer running "Upgrade in place" fails to start upgrade tool after clicking on the "Start Upgrade Wizard" button. 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. 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. 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
3. adminuser and adminpassword should match the values used for the installation you are upgrading. 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-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.
6296105 | Self-signed certificate is not trusted during and after upgrade from 8.0 Platform Edition (PE) to 8.1 Enterprise Edition (EE) UR2. 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>
6331685 | Document externalizing Domain, Agent directory as workaround for file-based installer full reinstall. For every file-base install patch, it is often necessary to reconfigure and redo or redeploy all applications. This is a time-consuming and error-prone procedure. Solution Externalize the DAS, NodeAgent, HADB, and MQ instance from the subdirectory or path of the AS8.1 installation to avoid having to perform a full reinstall. For example, to externalize the DAS domain to `/work/jnditest`:
    ./asadmin create-domain --domaindir /work \
    --adminport 7878 --adminuser admin --instanceport 7870 jnditest
To externalize the Node Agent to `/work/nagent`:
    ./asadmin create-node-agent --agentdir=/work \
    --port 7878 --host $dashost --user admin nagent
Finally, to start the externalized DAS:
    ./asadmin start-domain --domaindir /work -u admin  jnditest
6436590 | Uninstalling AS7.x that is coexisting with JES causes JES appserver to fail. Uninstalling Application Server 7.`x` causes all components installed with it to be removed. Subsequently upgrading to Application Server 8.`x` causes that installation to fail because some of the components on which it depends are missing. Solution 1 Do not uninstall Application Server 7.`x` before installing 8.`x`. Solution 2 Use pkgrm SUNWas* to manually uninstall packages belonging to Application Server 7.`x`. For example:
    8 - system       SUNWasaco    Sun Java System Application Server Admin Client, unbundled
    10 - system      SUNWascmlo   Sun Java System Application Server Shared Libraries, unbundled
    13 - system      SUNWascmo    Sun Java System Application Server unbundled (common)
    17 - system      SUNWasdmo    Sun Java System Application Server Sample Applications, unbundled
    18 - system      SUNWashaco   Sun Java System Application Server Admin Client Extension,
                                  unbundled
    20 - system      SUNWashdmo   Sun Java System Application Server HA Sample Applications,
                                  unbundled
    21 - system      SUNWashmano  Sun Java System Application Server Extension Manual Pages
    22 - system      SUNWasho     Sun Java System Application Server HA Extension, unbundled
    26 - system      SUNWasmano   Sun Java System Application Server Standard Manual Pages
    27 - system      SUNWaso      Sun Java System Application Server, unbundled (opt)
    28 - system      SUNWasro     Sun Java System Application Server, unbundled (root)
Note that if you use this method, you may need to use `prodreg unregister` to cleanup stale entries in `productregistry`.

- Previous: Security
- Next: Web Container

- © 2010, Oracle Corporation and/or its affiliates