Chapter 1 Upgrading a Communications Server Installation

You can upgrade an earlier installation of Communications Server to Communications Server 2.0 and replicate the configuration of a previously installed server in the target installation. Communications Server provides assistance in upgrading the configuration, applications, and certificate data .

This chapter discusses the following topics:

• Supported Upgrade Paths

• Upgrade Scenarios

• Upgrading Communications Server Runtime Binaries

• Upgrading Configuration and Deployed Applications

Supported Upgrade Paths

The following table shows supported Communications Server upgrade paths for file-based installations.

Upgrade Scenarios

The upgrade scenarios are as follows:

• Side-by-Side Upgrade

• In-Place Upgrade

Side-by-Side Upgrade

The source server and the target server are installed in different install locations. You can choose to perform this type of upgrade if you wish to have the configuration corresponding to these installations on the same machine in different locations.

A side-by-side upgrade involves the following sequence of tasks

1. Upgrading Communications Server Runtime Binaries

2. Upgrading Configuration and Deployed Applications.

In-Place Upgrade

The target server is installed in the same installation location as the source server. You can choose to perform this type of upgrade if you wish to install the configuration (that is, the domains) in the same location as before. In this scenario, you install the binaries in the same location as the existing binaries using the installer.

An in-place upgrade involves the following sequence of tasks:

1. Upgrading Communications Server Runtime Binaries

2. Upgrading Configuration and Deployed Applications.

Upgrading Communications Server Runtime Binaries

Use the Communications Server file-based installer to install the target server binaries. You can install in-place (in the same location as your earlier installation) or side-by-side (in a different location). For instructions on how to use the file-based installer, see Sun GlassFish Communications Server 2.0 Installation Guide.

Upgrading Configuration and Deployed Applications

You cannot perform an upgrade if the source and target server file systems, specifically the domain root file system, are not accessible from the same machine. To perform the upgrade, the user who runs the upgrade needs to have Read permissions for the source and target directories and Write permission for the target directory.

The upgrade process will merge the source domain configuration and the new target domain configuration. The upgrade process is started when you invoke the asadmin start-domain command after upgrading the binaries.

To Upgrade Communications Server 1.5 Configuration and Deployed Applications

This procedure assumes that Communications Server 1.5 is installed in source-install-dir. The default domain, domain1 is running. Deployed applications, clusters, and node agents are also running. The following procedure enables you to upgrade the configuration of the default domain.

1. Install Communications Server 2.0 in target-install-dir. This installation should have the same profile has the Communications Server 1.5 installation in source-install-dir.

2. Navigate to the config directory of the Communications Server 2.0 installation.

   cd target-install-dir/config

3. Open the asenv.conf file. Point the AS_ACC_CONFIG and AS_DEF_DOMAINS_PATH variables to corresponding Communications Server 1.5 locations as follows:

   AS_ACC_CONFIG=source-install-dir/domains/domain1/config/sun-acc.xml

   AS_DEF_DOMAINS_PATH=source-install-dir/domains

4. Stop the Communications Server 1.5 node agents and domain.

5. Start the Communications Server 2.0 domain.

   The command to start the default domain is as follows:

   • cd target-install-dir/bin

   • target-install-dir/bin>asadmin start-domain domain1

6. Start the Communications Server 1.5 node agent from the Communications Server 2.0 installation.

   target-install-dir/bin>asadmin start-node-agent -syncinstances=true --agentdir source-install-dir/nodeagents/ node-agent-name

   Repeat this step for all node agents on the domain.

7. Launch the deployed applications.

   There is no need to stop and restart the clusters, instances, and databases.