This section provides an overview of upgrading Adabas Fastpath and is applicable to version 8.2 SP2 and above.
The new version of Adabas Fastpath is fully compatible with your current configuration file. No migration of the configuration file is required.
This compatibility enables the same configuration file to be shared between the new version and your current version.
The new version of the Adabas Fastpath online services can be used to administer and monitor both new and current versions (although fix AW822077 needs to be applied in an AFP822 environment). Of course, any newly implemented configuration capability will only take effect when the appropriate new version component is running.
Likewise, your current version of the Adabas Fastpath online services can be used to administer and monitor both new and current versions. Of course, any newly implemented configuration and monitoring capability will not be available for use.
The following table shows the supported runtime version compatibility between the new and your current Adabas Fastpath components:
| Client Component Version | Daemon Component Version | Database Component Version |
|---|---|---|
| Current | Current | Current |
| Current | Current | New |
| Current | New | New |
| New | New | New |
Where:
The client component consists of the AFP load library made available to the client.
The daemon component consists of the AFP load library made available to the daemon.
The database component consists of the AFP load library made available to the database
Note
If a particular version combination is not specified in the above table, then it is
not supported.
In a multi-system environment, the Upgrade Procedure for upgrading Adabas Fastpath database components and daemon components must be extended across all systems as follows:
Adabas Fastpath database components across all systems must be upgraded before any single daemon component or client component is upgraded.
Adabas Fastpath components in Adabas System Coordinator daemons across all systems must be upgraded before any single client component is upgraded.
If you currently use Adabas Fastpath load libraries that are shared across client, daemon, and database components, you must ensure that the library changes described in each step of the Upgrade Procedure affect only the component relevant to that step.
This may require discontinuing the use of shared libraries until after the upgrade process has completed.
Refer to Software GmbH’s Empower website for the latest available maintenance for this version of Adabas Fastpath.
If maintenance is available, we strongly recommend that it be applied before proceeding with the upgrade.
Note
If you wish to use this new version of SYSAFP online services to administer your
existing AFP 8.2 SP2 environment, then fix AW822077 should be applied to your existing
environment first.
This section describes the required steps to upgrade Adabas Fastpath.
For reference, the table in the Runtime Component Version Compatibility section tabulates the upgrade steps of the Adabas Fastpath components.
In addition to the information provided here, please also refer to the Adabas Fastpath Installation documentation for further information.
Upgrade Adabas Fastpath database components by replacing the current version of the Adabas Fastpath database load library with the new version.
The new version of the Adabas Fastpath database component is fully backward compatible with your current version of Adabas Fastpath client and daemon components.
Note
In a multi-system environment, Adabas Fastpath database components - across all
systems - must be upgraded before any single daemon or client component is
upgraded.
Upgrade the Adabas Fastpath component in Adabas System Coordinator daemons by replacing the current version of the Adabas Fastpath load library in the Adabas System Coordinator daemon with the new version.
Daemons within a group can be upgraded individually or all together at the same time.
The new version of Adabas Fastpath in the Adabas System Coordinator daemon is fully backward compatible with your current version of Adabas Fastpath client components and peer daemons (daemons within the same group) but is not backward compatible with earlier versions of database components (which is why databases must first be upgraded as described in Step 1).
Note
In a multi-system environment, Adabas Fastpath components in Adabas System
Coordinator daemons - across all systems - must be upgraded before a single client
component is upgraded.
Upgrade Adabas Fastpath client components by:
Replacing the current version of the Adabas Fastpath client load library with the new version.
The new version of the Adabas Fastpath client component is not backward compatible with earlier versions of database or daemon components (which is why Adabas Fastpath database and daemon components must first be upgraded as described in Steps 1 and 2).