test

Sun GlassFish Communications Server 2.0 Upgrade 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.

ProcedureTo 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.