This section provides an overview of upgrading Data Archiving for Adabas.
The Software AG Installer does not support multiple product versions in the same installation directory. If a newer version of Data Archiving for Adabas is to be installed on the same machine as a previous version, a separate installation directory must be used.
As part of the activation process for Data Archiving for Adabas, Adabas System Coordinator (COR) must be configured with a Group Services port number and a Port Range (a range of port numbers from which ports for services such as Data Archiving are allocated). Similarly, the System Management Hub and related components also require port numbers to be assigned during installation.
In order for different versions of Data Archiving for Adabas to co-exist on the same machine, different port numbers must be allocated to the products in each installation directory.
Each new version of Data Archiving for Adabas should be initially installed with a new Repository. The final part of the upgrade process migrates the current Repository content into the new Repository.
The recommended upgrade procedure for Windows and UNIX is in two parts:
In the unlikely event that you need to revert to the previous version, refer to Reverting to the Previous Version.
This section highlights the general installation steps for installing the new version on the target machine and, where applicable, describes upgrade-related tasks to be performed during the installation process.
It refers to sections in, and should be read in conjunction with, the Installation Procedure for Windows and UNIX.
Step | Description | References |
---|---|---|
1 | Using the Software AG Installer, download the latest version of Data Archiving for Adabas and prepare it for installation… | Software AG Installer |
1a | Download the Software AG Installer from the SDC on Empower. | |
1b | Run the Installer on your chosen installation machine. | |
1c | When prompted for the installation location, choose a new or empty directory. | Installation Directory |
1d | On the product selection screen, under the Data Archiving for Adabas node, select the Administration and Archiving Services components. | |
1e | Complete the download process. You will be prompted for the port numbers to use for the System Management Hub and other related components, ensure only dedicated version-specific port numbers are used. | Port Numbers |
2 | Perform the activation… | Activation |
2a | Start the Activation tool in the manner according to your chosen installation machine. | Starting the Activation |
2b | In the COR tab ensure only dedicated version-specific port numbers are used. | Port Numbers |
2c | In the COR tab specify a new Adabas database and file number to be used for the Repository. | Repository |
2d | Complete the activation. | |
3 | Verify the new version installation. | Verifying the Installation |
4 | Check Empower and apply any maintenance to the new version installation. | Applying the Latest Maintenance |
Note:
After successfully installing the new version on the target machine,
the new version and the current version can run concurrently on the same
machine because they are configured to use different Repositories and port
numbers. However, this will not be possible once the final part of the
upgrade Migrating the current Repository
content has been completed.
When you are ready to complete the upgrade, the final stage of the upgrade process is to migrate the content of the current version’s Repository to the new version’s Repository.
Step | Description | References |
---|---|---|
1 | Ensure there are no pending TO-DO lists in the current version’s Repository or alternate Adabas file (if used). | |
2 | Ensure there are no active Actions. | |
3 | Shutdown the current version of Data Archiving for Adabas. | Shutting down the Launch Controller |
4 | Shutdown the new version of Data Archiving for Adabas. | Shutting down the Launch Controller |
5 | Run the Migration Utility to migrate the content
from the current version’s Repository to the new version’s Repository.
Note: |
Migration Utility |
6 | Restart the new version of Data Archiving for Adabas. | Starting the Launch Controller |
7 | Verify that the Repository content has been migrated by using the new version’s browser administration tool. | Web Interface |
8 | The upgrade is now complete. |
Note:
After successfully migrating the current version’s Repository
content, it will no longer be possible to run the new version and the old
version concurrently on the same machine because the new version inherits the
port numbers used by the old version as part of the migration process.
The recommended upgrade procedure for z/OS is in two parts:
In the unlikely event that you need to revert to the previous version, refer to Reverting to the Previous Version.
This section highlights the general installation steps for installing the new version on the target machine and, where applicable, describes upgrade-related tasks to be performed during the installation process.
It refers to sections in, and should be read in conjunction with, the Installation Procedure for z/OS.
Step | Description | References |
---|---|---|
1 | Using the Software AG Installer, download the latest version of Data Archiving for Adabas and prepare it for installation… | Software AG Installer |
1a | Download the Software AG Installer from the SDC on Empower. | |
1b | Run the Installer on your chosen off-host machine which will be used to administer Data Archiving for Adabas. | |
1c | When prompted for the installation location, choose a new or empty directory. | Installation Directory |
1d | On the product selection screen, under the Data Archiving for Adabas node, select the Administration and Archiving Services for z/OS components. | |
1e | Complete the download process. You will be prompted for the port numbers to use for the System Management Hub and other related components, ensure only dedicated version-specific port numbers are used. | Port Numbers |
2 |
Each installation of Data Archiving for Adabas must have its own version specific load library. Create the dataset for the new load library and a site-based ADALNKR routine to reside in it. |
Actions Required Before Starting the Install |
3 | Perform the Archiving Services for z/OS activation… | Activation |
3a | Start the Activation tool in the manner according to your chosen off-host machine. | Starting the Activation |
3b | In the COR tab ensure only dedicated version-specific port numbers are used. | |
3c | In the COR tab specify a new Adabas database and file number to be used for the Repository. | |
3d | In the COR tab specify the newly created load library dataset. | COR tab |
3e | In the FTP Parameters tab specify a new or empty installation directory. | |
3f | Complete the Archiving Services for z/OS activation. | Activate |
4 | Perform the Administration activation on your chosen off-host machine. | Administration |
5 | Verify the new version installation. | Verifying the Installation |
6 | Check Empower and apply any maintenance to the new version installation. | Applying the Latest Maintenance |
Note:
After successfully installing the new version on the target machine,
the new version and the current version can run concurrently on the same
machine because they are configured to use different Repositories and port
numbers. However, this will not be possible once the final part of the upgrade
Migrating the current Repository
content has been completed.
When you are ready to complete the upgrade, the final stage of the upgrade process is to migrate the content of the current version’s Repository to the new version’s Repository.
Step | Description | References |
---|---|---|
1 | Ensure there are no pending TO-DO lists in the current version’s Repository or alternate Adabas file (if used). | |
2 | Ensure there are no active Actions. | |
3 | Shutdown the current version of Data Archiving for Adabas. | Shutting down the Launch Controller |
4 | Shutdown the new version of Data Archiving for Adabas. | Shutting down the Launch Controller |
5 | Run the Migration Utility to migrate the content
from the current version’s Repository to the new version’s Repository.
Note: |
Migration Utility |
6 | Restart the new version of Data Archiving for Adabas. | Starting the Launch Controller |
7 | Verify that the Repository content has been migrated by using the new version’s browser administration tool. | Web Interface |
8 | The upgrade is now complete. |
Note:
After successfully migrating the current version’s Repository
content, it will no longer be possible to run the new version and the old
version concurrently on the same machine because the new version inherits the
port numbers used by the old version as part of the migration process.
In the unlikely event that you need to revert to the previous version, the following table lists the necessary steps:
Step | Description | References |
---|---|---|
1 | Ensure there are no pending TO-DO lists in the new version’s Repository. | |
2 | Ensure there are no active Actions. | |
3 | Shutdown the new version of Data Archiving for Adabas. | Shutting down the Launch Controller |
4 | Restart the previous version of Data Archiving for Adabas. | Starting the Launch Controller |
After successfully reverting to the previous version, any changes that have occurred in the new version’s Repository since migration took place will not be visible in the reverted version’s Repository.
Viewing configuration changes or activity reports in the new version’s Repository will depend on the availability of the new version of the Administration component on a machine which has access to the database containing the new Repository.
New version of Administration component is available on a machine which has access to the Repository
This method is appropriate for Windows or UNIX, where the new version of the Administration component is typically installed on the same machine as the database containing the Repository.
It can also be used for Windows, UNIX or z/OS installations, where the new version of the Administration component is installed on a machine that can access the database containing the Repository via Entire Net-Work.
View the Repository content by performing the following steps in the new version’s Administration component.
Step | Description |
---|---|
1 | Right-click on the Perspectives node within the Data Archiving for Adabas navigation tree, select Add Perspective and then choose the Specific Repository (direct from the UI). |
2 | In the database and file fields, specify the database and file number of the Repository to be viewed. |
3 | After clicking Add and refreshing the tree, the content of the Repository will be displayed. |
Refer to the Adding a Perspective section in the Web Interface documentation for further details.
This method is appropriate for Windows, UNIX and z/OS installations, where the new version of the Administration component is installed on a machine that does not have local or Entire Net-Work access to the database containing the Repository.
It uses an instance of the new version’s Archiving Services components running on a secondary installation (for example a test machine) which does have local or Entire Net-Work access to the database containing the Repository.
View the Repository content by performing the following steps in the new version’s Administration component:
Step | Description |
---|---|
1 | Right-click on the Perspectives node within the Data Archiving for Adabas navigation tree, select Add Perspective and then choose the Specific Repository (using a Daemon as the access point) option. |
2 | In the Hostname and Port fields, specify the hostname of the machine which has an instance of the new version’s Archiving Services components running and enter the port number of its Adabas System Coordinator Daemon. |
3 | In the database and file fields, specify the database and file number of the Repository to be viewed. |
4 | After clicking Add and refreshing the tree, the content of the Repository will be displayed. |
Refer to the Adding a Perspective section in the Web Interface documentation for further details.
The Migration Utility enables the migration of configuration data from a previous version of Data Archiving for Adabas to a newly installed version.
Note:
Refer to Upgrading from Earlier
Versions for a full description regarding the steps necessary
to upgrade Data Archiving for Adabas.
The installation kit for Data Archiving for Adabas includes and
installs Adabas System Coordinator. The Migration Utility is part of Adabas
System Coordinator and it is run using the corlfile
executable
located in the bin
subdirectory underneath the Adabas System
Coordinator installation directory.
For migration, the corlfile
executable is run with the
following parameters:
Parameters | Description | ||
---|---|---|---|
/m |
The |
||
from-file=<db>,<fnr> |
The |
||
to-file=<db>,<fnr> |
The |
||
/o |
By default the migration process will not write to an existing file
unless the file is empty. The optional
|
To use the utility on Windows, start a Command Prompt and change to to
the bin
directory underneath the new Adabas System Coordinator
installation directory:
C:\>cd \SoftwareAG\cor\vvrs\bin C:\SoftwareAG\cor\vvrs\bin>
where vrs is the newly installed Adabas System Coordinator version.
Then run the corlfile
executable with the appropriate
parameters:
C:\SoftwareAG\cor\vvrs\bin>corlfile /m from-file=1,500 to-file=1,501
To use the utility on Linux, UNIX and z/OS (USS), source the Adabas
System Coordinator environment script and then change to the bin
directory underneath the new Adabas System Coordinator installation directory:
ukrdu@dali166 => cd /opt/softwareag ukrdu@dali166 => export ADABAS_ADDONS=yes ukrdu@dali166 => . bin/sagenv.new [Setting environment for Adabas System Coordinator] [Enabling Adabas Add-On products] [done] [Setting environment for Adabas Data Archiving] [done] ukrdu@dali166 => cd $CORDIR/$CORVERS/bin ukrdu@dali166 =>
Then run the corlfile
executable with the appropriate
parameters:
ukrdu@dali166 => corlfile /m from-file=1,500 to-file=1,501
After the utility has successfully completed the migration, Data Archiving for Adabas needs to be reactivated in order to use the new Repository:
Stop all Archiving Services. For more information refer to Shutting down the Launch Controller.
Re-run the Activation process specifying the newly migrated Repository in the COR tab. For more information refer to the Activation section in the Installation procedures for the relevant installation platform.