Sun Microsystems Logo
Products and Services
 
Support and Training
 
 

A  B  C  D  E  F  G  H  I  J  K  L  M  N  O  P  Q  R  S  T  U  V  W  X  Y  Z  
 
Application Server Utilityasupgrade(1m)


NAME

 asupgrade - migrates the configuration of a previously installed Sun Java System Application Server

SYNOPSIS

 asupgrade [ -c | --console ] [ -V --version ] [ -h | --help ]-s | -source applicationserver7.x_installation -t --target applicationserver8.x_installation [ -d | --domain domain_name -n | --nsspwdfile NSS_password_filepath -j | --jkspwdfile JKS_password_filepath -p | --capwdfile CA_password_filepath ]

DESCRIPTION

 

Use the asupgrade utility to migrate the server configration and its persisted state, J2EE services, and deployed J2EE applications. The configuration of an installed Sun Java System Application Server 7 is migrated to the Sun Java System Application Server 8 Application Server 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.

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 beyond the scope of the asupgrade command.

Only those instances that do not use the Sun Java System Web Server specific features will be upgraded seamlessly. Configration 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 checkbox in the Application Server installer. After completion of the upgrade, use the Application Server 7 Uninstaller to remove the previous version of the Application Server.

Application archives (.ear) and component archives (.jar, .war, .rar) that are deployed in the Application Server 7 environment do not require any modification to run on Application Server 8. However applications and components deployed in the source server are repackaged into new J2EE archives in the target server's autodeploy directory and are deployed upon server startup. Applications that do not deploy successfully, must use Migrationtool (asmigrate) on the application and then manually redeploy the application.

You must specify the source and target directories for the upgrade. If the upgrade includes certificates, you must also 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 (JSSE), the migration keys and certificates are converted to the new format. Upon successful upgrade, an upgrate report is generated listing successfully migrated items along with a list of the items that could not be migrated.


OPTIONS

 
-c --console
launches the upgrade command line utility.
-V--version
displays the version of the UpgradeTool.
-h--help
displays the arguments for launching the UpgradeTool.
-s--source
identifies the installation directory for Sun Java System Application Server 7.
-t--target
identifies the installation directory for Sun Java System Application Server 8.
-d--domain
identifies the destination domain name for the migrated certificates.
-n--nsspwdfile
identifies the path to the NSS password file.
-j--jkspwdfile
identifies the path to the JKS password file.
-p--capwdfile
identifies the path to the CA certificate password file.

EXAMPLES

 Example 1. Using asupgrade
 
 
example% upgrade -s /home/sunas7 -t /home/sunas8

SEE ALSO

 

asmigrate(1M)



Sun Java System Application ServerGo To TopLast Changed March 2004