9.11 Upgrading Application Server or Application Server for Developers

To upgrade Application Server or Application Server for Developers, perform an upgrade operation and apply the domain of the older version to the newer version. To do this, create a backup file of the domain of the older version by using the backup-domain subcommand of the asadmin utility command, install the newer version, and then restore the domain to the new environment by using the restore-domain subcommand of the asadmin utility command. To upgrade the configuration of the domain administration server, execute the start-domain subcommand of the asadmin utility command on the restored domain.

Prerequisites

The domain of the older version exists.

Intended users

System engineers or system operators

Procedure

Back up the environment of the older version.
1. Stop all the servers and all the domain administration servers that are running in the environment of the older version.
2. To back up the environment information of the older version , run the backup-domain subcommand of the asadmin utility command.
```
asadmin backup-domain 
--backupdir path_of_the_directory_where_the_backup_files_are_saved domain_name
```
  When this command is run, the result is displayed as follows:
```
Command  backup-domain executed successfully.
```
3. Confirm that the following backup file has been output:
```
path_of_the_directory_where_the_backup_files_are_saved/domain_name/domain_name_YYYY_MM_DD_vserial_number.zip
```
  The serial number is a number starting from 00001.
Install a newer version.
1. Stop all the servers and all the domain administration servers that are running in the environment of the older version.
2. Install a newer version.
  
  You can use the following types of installation:
  
  New installation: Install a new version on a machine other than the machine on which an old version is installed
  
  Multiple installations: Install a new version in another directory on the machine on which an old version is installed
  
  Overwrite installation: Install a new version in the same directory on the machine on which an old version is installed
  
  If you want to build a cluster configuration in which multiple Java EE servers are placed, perform the installation on each remote host.
3. If the domain administration server will start after a reboot of the machine after the installation, stop the domain administration server.
Migrate the environment definitions that were backed up in the old version to the new version.

This process is not required for overwrite installations.
1. Set the environment variables that were added to the environment variable definition file (asenv.bat) of the Java EE Server in the old version to the same file in the new version.
  
  Environment variable definition file of the Java EE Server
  
  installation_directory/javaee/glassfish/config/asenv.bat
  
  For installation_directory, specify the installation directory for Application Server or Application Server for Developers.
2. In the environment of the new version, run the restore-domain subcommand of the asadmin utility command to restore the environment information of the old version that was backed up to the new version.
```
asadmin restore-domain 
--backupdir path_of_the_directory_where_the_backup_files_are_saved domain_name_whose_environment_information_will_be_restored
```
3. Check the domain directory of the restored domain to make sure that the environment information was restored.
Upgrade the domain.
1. To upgrade the domain, run the start-domain subcommand of the asadmin utility command in the environment of the new version, with the --upgrade option specified.
```
asadmin start-domain --upgrade domain_name
```
  When this command is run, the result is displayed as follows:
```
Command start-domain executed successfully.
The DAS was stopped.
```
  At this time, check the console to make sure that no message in the SEVERE, ALERT, or EMERGENCY level is output.
2. In the environment of the new version, delete the directory with the name osgi-cache-number that is output under the domain directory.
  
  When you upgrade the domain, the OSGi cache directory under the domain directory is renamed to osgi-cache-number. Delete this directory because it will not be used after the upgrade.
3. To start the domain administration server, run the start-domain subcommand of the asadmin utility command.
```
asadmin start-domain domain_name
```
  When this command is run, the result is displayed as follows:
```
Command start-domain executed successfully.
```
4. To change the installation directory of each node to the installation directory of the newer version, run the update-node-config subcommand or the update-node-dcom subcommand of the asadmin utility command.
  If the node is the local host:
```
asadmin update-node-config --installdir installation_directory_for_new_version/javaee_absolute_path --nodedir node_directory node_name
```
  If the node is a DCOM connection node:
```
asadmin update-node-dcom --installdir installation_directory_for_new_version/javaee_absolute_path --nodedir node_directory node_name
```
  If the node directory was changed from the default in the environment for the old version, specify the --nodedir option to also change the node directory.
  
  If necessary, change the node directory as well.
  When this command is run, the result is displayed as follows:
  
  If the node is the local host:
```
Command update-node-config executed successfully.
```
  If the node is a DCOM connection node:
```
Command update-node-dcom executed successfully.
```
Test the server and the applications.
1. Start the server on the domain and test the server and the applications.
2. If the test finishes successfully, start using the newer version as the production environment.
If necessary, delete the environment of the older version.

This step is not necessary if an overwrite installation was performed.

If the environment of the older version was in a cluster configuration in which multiple Java EE servers were placed, perform this step for each of the remote hosts.

To Page Top