Use the asupgrade utility to upgrade the server configuration and its persisted state, J2EE services, and deployed J2EE applications. The configuration of your earlier version of Application Server is migrated to the Sun Java System Application Server 8.1 installation. If the domain contains information about a deployed application and the installed application components do not agree with the configuration information, the configuration is migrated as is without any attempt to reconfigure the incorrect configurations.
You can use the tool through the command-line interface (CLI) or the GUI. To use the Upgrade tool in GUI mode, issue the asupgrade command with no options. To run the Upgrade tool in CLI mode, invoke the asupgrade command with the -––c/––console option. You can run the upgrade CLI in the interactive or non-interactive mode. If you supply all required arguments when invoking asupgrade on the console, the upgrade is performed in non-interactive mode and no further input is required.
asupgrade migrates the configuration and deployed applications of a previous version of the Application Server. However, the runtime binaries of the server are not updated. Database migrations or conversions are also beyond the scope of the asupgrade command.
Only those instances that do not use Sun Java System Web Server-specific features will be upgraded seamlessly. Configuration files related to HTTP path, CGI bin, SHTML, and NSAPI plugins will not be upgraded.
The upgrade process can also be initiated automatically at installation time using the Upgrade check box in the Application Server installer. After completion of the upgrade, use the uninstaller to remove the previous version of the application server.
Application archives (EAR files) and component archives (JAR, WAR, and RAR files) that are deployed in the Application Server 7.x/8.x environment do not require any modification to run on Application Server 8.2 EE. Applications and components that are deployed in the source server are deployed on the target server during the upgrade. Applications that do not deploy successfully on the target server must be migrated using the Migration Tool or asmigrate command, then redeployed manually.
If the upgrade includes certificates, provide the passwords for the source PKCS12 file and the target JKS keyfile for each domain that contains certificates to be migrated. Since Application Server 7 uses a different certificate store format (NSS) than Application Server 8 PE (JSSE), the migration keys and certificates are converted to the new format. Only one certificate database password per domain is supported. If multiple certificate database passwords are used in a single domain, all of the passwords must be made the same before starting the upgrade. The passwords can be reset after the upgrade has been completed.
If the upgrade includes clusters, specify one or more cluster files. Upon successful upgrade, an upgrade report is generated listing successfully migrated items along with a list of the items that could not be migrated.
If you issue the asupgrade command with no options, the Upgrade Tool GUI will be displayed. If the asupgrade command is used in command-line mode and all of the required information is not supplied, an interviewer will request information for any required options that were omitted.
Launches the upgrade command line utility.
The version of the Upgrade Tool.
Displays the arguments for launching the UpgradeTool.
The installation directory for Sun Java System Application Server 7.x/8.x installation that will be upgraded.
The installation directory for Sun Java System Application Server 8.1.
The username of the administrator.
The password for the adminuser. Although this option can be used, the recommended way to transmit passwords is by using the ––passwordfile option.
The master password that is created during installation. The default value is changeit. Although this option can be used, the recommended way to transmit passwords is by using the ––passwordfile option.
The path to the file that contains the adminpassword and masterpassword. Content of this file should be in the following format: AS_ADMIN_ADMINPASSWORD=adminpassword AS_ADMIN_MASTERPASSWORD=masterpassword
The domain name for the migrated certificates.
The path to the NSS password file.
The path to the target NSS password file.
The path to the JKS password file.
The path to the CA certificate password file.
The path to the cluster file. The default filename is $AS_INSTALL/conf/clinstance.conf .
This example shows how to upgrade (side-by-side) a Sun Java System Application Server 7 installation to Sun Java System Application Server 8.2 Enterprise Edition. You will be prompted to migrate certificates. If you reply no, then no certificates will be migrated.
example% asupgrade --adminuser admin --passwordfile password.txt --source /home/sunas7 --target /home/sjsas8.2/domains
For information of the upgrade scenarios (side-by-side, in-place) see Chapter 2 in the Sun Java System Enterprise Edition 8.2 Upgrade and Migration guide.
This example shows how to upgrade (side-by-side) a Sun Java System Application Server 7.1 EE installation with a cluster to Sun Java System Application Server 8.2 EE. NSS certificates will be migrated, as will the clinstance.conf cluster file.
example% asupgrade --adminuser admin --passwordfile password.txt --source /home/sjsas7.1 --target /home/sjsas8.2/domains --domain domain1 --nsspwdfile /home/sjsas7.1/nsspassword.txt --targetnsspwdfile /home/sjsas8.2/nsspassword.txt --clinstancefiles /home/sjsas7.1/config/clinstance.conf
After the upgrade, node agents for all remote instances must be created and started on their respective host systems.
This example shows how to upgrade (in-place) a Sun Java System Application Server 8.1 EE installation to Sun Java System Application Server 8.1 PE. JKS and CA certificates will be migrated.
example% asupgrade --adminuser admin --passwordfile password.txt --source /home/sjsas8.1/domains --target /home/sjsas8.2/domains --domain domain1 --nsspwdfile /home/sjsas8.1/nsspassword.txt --targetnsspwdfile /home/sjsas8.2/nsspassword.txt --clinstancefiles /home/sjsas8.1/config/clinstance.conf