Copyright © Cloud Software Group, Inc. All Rights Reserved

Upgrading to Release 2.1.1

Upgrade Procedures

Two upgrade methods are available for TIBCO ActiveSpaces:

•	Rolling Upgrade  You can use this method when upgrading from a minor release to a major release. With a rolling upgrade, you bring one node down and upgrade it, restart it, and then upgrade additional nodes, one node at a time.

 

The rolling upgrade feature is available only for upgrade between minor releases; for example, upgrading from one service pack to another service pack release.

 

You cannot use the rolling upgrade method for nodes that are running through as-agent processes. For these nodes, you must use the offline upgrade method.

•	Offline Upgrade  You perform an offline upgrade by shutting down each instance of ActiveSpaces, upgrading the node to ActiveSpaces 2.1.1, and then restarting the node. You can use this method for any of the upgrade paths to ActiveSpaces 2.1.1.

If you are upgrading from TIBCO ActiveSpaces Release 2.0.0 to Release 2.0.x or from release 2.0.1 to release 2.0.2, and you have implemented shared-nothing persistence, then after upgrading to the new release version, you must convert any shared-nothing persistence data files from your 2.0.0 release to the newer format that is used with Release 2.0.2.

An off-line conversion utility, as-convert, is provided to perform this data conversion. The utility automatically detects the release that created the data files and converts them to the release 2.1.1 format.

For information on the as-convert utility, see Running the as-convert Utility.

Upgrade Paths

The following upgrade paths are available for ActiveSpaces 2.1.1:

•	Release 2.0 to 2.1.1  Requires an offline upgrade. Convert any shared-nothing persistence data files to the ActiveSpaces 2.1.1 format by running the as-convert utility.

•	Release 2.0.1 to Release 2.1.1  Requires an offline upgrade. Convert any shared-nothing persistence data files to the ActiveSpaces 2.1.1 format by running the as-convert utility.

•	Release 2.0.1 to 2.0.2  Requires an offline upgrade. Convert any shared-nothing persistence data files to the ActiveSpaces 2.1.1 format by running the as-convert utility.

•	Release 2.0.2 to Release 2.1.1  Requires an offline upgrade. You do not need to convert shared-nothing persistence data files for this upgrade.

•	Release 2.1.1 to Future 2.1.x Releases  Depending on your situation, you can use the rolling upgrade method or the offline upgrade method.

Performing a Rolling Upgrade

To perform a rolling upgrade:

1.	Run the TIBCO Universal Installer and install the new version of ActiveSpaces into a new TIBCO_HOME directory.

If there is no previous installation on this machine, you do not need to use a different TIBCO_HOME directory.

2.	Start one instance (for example, an as-agent) from the new TIBCO_HOME directory, and wait for redistribution to complete.

3.	Then, bring down gracefully (using the metaspace.closeAll method) a node that was started from the old TIBCO_HOME directory or kill the node (using CTRL-c or kill -9), and wait for redistribution to complete.

4.	Repeat steps 2-3 until all nodes from the old TIBCO_HOME are removed from the cluster.

5.	Repeat steps 1-4 on all hosts.

 

Review the Release Notes the new TIBCO ActiveSpaces version for changes to the API that might affect your applications. You will need to upgrade your applications to use the new API calls.

Performing an Offline Upgrade

On each AS node:

1.	Stop all ActiveSpaces processes.

2.	If you have implemented shared-nothing persistence, run the as-convert utility to convert shared-nothing persistence data files to the release 2.1.1 format.

See Running the as-convert Utility.

3.	Run the TIBCO Universal Installer and install AS 2.1.1.

See Installing ActiveSpaces.

4.	Restart the ActiveSpaces processes.

 

Review the Release Notes for the new TIBCO ActiveSpaces version for changes to the API that might affect your applications. You will need to upgrade your applications to use the new API calls.

Running the as-convert Utility

The as-convert.exe file is located in the following directory:

AS_HOME/bin

 

Before you run as-convert, stop all as-agents and seeders. The as-convert utility must be run off-line.

Command Syntax

as-convert -data_store <directory_path> -metaspace <metaspace_name> -space <space_name> -name <membername> -file <file_name> -compact -dry_run -verbose -log <log_file> -debug <log_level>

Table 4 describes the parameters for as-convert.

 

Table 4 Parameters for as-convert

Parameter	Usage
-data_store	directory_path specifies the path to the data store to convert.
-metaspace	To specify conversion of the data files for all of the spaces defined for a metaspace, specify a metaspace name.
-space	To specify conversion of the data files for a specific space within the metaspace, specify the space name with the -space parameter and the metaspace name with the -metaspace parameter.
-name	To specify conversion of the data files for a specific space member, specify the member name with the -name parameter, the space name with the -space parameter, and the metaspace name with the -metaspace parameter.
-file	To specify conversion of a specific file, specify the filename with the -file parameter, the data store path with the -data_store parameter, and the metaspace name with the -metaspace parameter.
-compact	Deletes any white spaces in converted file. White spaces can be added to the data file as a result of processing Takes, which delete data.
-dry_run	To run the utility without actually converting the data store and output informational messages, include the -dry_run parameter
-help	Outputs a summary of the command syntax for as-convert.
-verbose	Causes output of more information.
-log	Specifies the name of a log file to which to write log information
-debug	Specifies the log level for messages output by the utility.

Usage Notes

The as-convert utility converts ActiveSpaces shared-nothing files from one format (or one version) to another (usually higher). The utility does the following:

•	If a file name is provided, processes that file and prints out the result.

•	If a space name is provided along with the member name and metaspace name, converts all files that belong to that space.

•	If a member name is provided along with the space name, converts files for that member only.

•	If a metaspace name is provided, the utility does the above for each space that is part of the metaspace.

•	If no argument is provided, processes the entire data store — reads each subdirectory and converts all files.

•	the dry_run option will just touch the files and identify which are older than current version. This option is good for estimating how many files need conversion.

Copyright © Cloud Software Group, Inc. All Rights Reserved