IBM DataPower Operations Dashboard v1.0.17.0
A newer version of this product documentation is available.
You are viewing an older version. View latest at IBM DPOD Documentation.
Upgrade
- shachar greenberg (Unlicensed)
- Amit Munwes
- Shachar Greenberg
DPOD software upgrades are available from time to time and include enhancements, security updates, component upgrade, bug fixes, etc.
The following sections describe the process of upgrading an existing installation.
Upgrade Paths
The following table describes the upgrade paths between versions:
From | 1.0.10.x | 1.0.11.0 | 1.0.12.0 | 1.0.13.0 | 1.0.14.0 | 1.0.15.x | 1.0.16.0 |
|---|---|---|---|---|---|---|---|
1.0.11.0 | 1.0.10.x → 1.0.11.0 |
|
|
|
|
|
|
1.0.12.0 1 | 1.0.10.x → 1.0.12.0 | 1.0.11.0 → 1.0.12.0 |
|
|
|
|
|
1.0.13.0 | 1.0.10.x → 1.0.13.0 | 1.0.11.0 → 1.0.13.0 | 1.0.12.0 → 1.0.13.0 |
|
|
|
|
1.0.14.0 2 | 1.0.10.x → 1.0.13.0 | 1.0.11.0 → 1.0.13.0 | 1.0.12.0 → 1.0.13.0 | 1.0.13.0 → 1.0.14.0 |
|
|
|
1.0.15.x 3 | 1.0.10.x → 1.0.13.0 | 1.0.11.0 → 1.0.13.0 | 1.0.12.0 → 1.0.13.0 | 1.0.13.0 → 1.0.14.0 | 1.0.14.0 → 1.0.15.x |
|
|
1.0.16.0 | 1.0.10.x → 1.0.13.0 | 1.0.11.0 → 1.0.13.0 | 1.0.12.0 → 1.0.13.0 | 1.0.13.0 → 1.0.14.0 | 1.0.14.0 → 1.0.16.0 | 1.0.15.x → 1.0.16.0 |
|
1.0.17.0 | 1.0.10.x → 1.0.13.0 | 1.0.11.0 → 1.0.13.0 | 1.0.12.0 → 1.0.13.0 | 1.0.13.0 → 1.0.14.0 | 1.0.14.0 → 1.0.17.0 | 1.0.15.x → 1.0.17.0 | 1.0.16.0 → 1.0.17.0 |
1 Version 1.0.12.0+ requires at least 1.0.10.x because of Store engine upgrade and data upgrade issues.
2 Version 1.0.14.0+ requires at least 1.0.13.0 because of an architecture change of the Store engine.
3 Version 1.0.15.0+ requires at least 1.0.14.0 because of an architecture change of the Store engine.
Backup the Servers
It is highly recommended to perform a full backup (including the operating system) of all DPOD servers prior to upgrading, so the system can be restored in case of a failed upgrade.
In virtual environments, it is highly recommended to create snapshots of the virtual machines, which can be removed later once the upgrade is completed successfully.
Make Sure the System is Healthy and Ready for the Upgrade
Upgrade is possible only if the current installation is healthy.
For an all-in-one installation, make sure the DPOD server is up and running, and that the Store status is green (under DPOD Health → Store).
For a cell environment, make sure all the servers in the cell are up and running, and that the Store status is green (under DPOD Health → Store).
Navigate to the Upgrade Assistant page and inspect the system status. In case this update includes a major version upgrade of the Store engine of DPOD, your system must first be ready for the upgrade as indicated in this page. If your system is still not ready for the upgrade, you may change the reindex options to accelerate the reindexing activity and get the system ready faster.
Upgrading a Cell Environment
To upgrade a cell environment:
Upgrade the cell manager (see “Upgrading a Single DPOD Server” below).
When the cell manager upgrade is complete, only the following services should be up and running -MonTier-Derby,MonTier-es-raw-trans-Node-1/2/3/4(the Web Console will be unavailable).
Do not start the other services manually on the cell manager unless requested explicitly.Upgrade all cell members (see “Upgrading a Single DPOD Server” below).
The upgrade of all cell members can be done in parallel.When the cell members upgrade is complete, start the cell manager services using the
app-util.sh("Start All").
Upgrading a Single DPOD Server
Copy the Software Update Files
DPOD software updates are available through IBM Fix Central. The download consists of two files:
The update file:
DPOD-fixpack-<version number>.sfsThe md5 checksum of the update file:
DPOD-fixpack-<version number>.md5Verify the integrity of the downloaded update file by calculating its md5 checksum and comparing it to the downloaded md5 checksum file.
Create necessary directories:
mkdir -p /installs/update/fix/TODO /installs/update/fix/logsCopy the downloaded files to the following directory on DPOD server:
/installs/update/fix/TODO
Make Sure there is Enough Free Disk Space
Inspect the free space of each mount point. You may use the following command:
df -hThe following table lists the required available space:
Mount Point | Required Available Space |
|---|---|
/ | 100 MB |
/installs | 4 GB + internal configuration database size |
If there is not enough free space on the /installs mount point, you may free some from the following directories:
Directory | Description |
|---|---|
/installs/update/fix/TODO | Remove old DPOD update files (.sfs). |
/installs/backups | Move old DPOD backup directories to a different server. It is recommended not to delete the backups until you are absolutely sure you don’t need them anymore. |
/installs/APPL-setup | Remove the directories. |
Follow Special Steps
Some versions require special steps. Make sure to follow them:
Install the Software Update
Execute the following commands as root (using sudo is not supported):
cd /installs/update/fix/TODO
MonTierUpdateInstaller.sh -u DPOD-fixpack-<version number>.sfs -s DPOD-fixpack-<version number>.md5
For example:
MonTierUpdateInstaller.sh -u DPOD-fixpack-1_0_16_0.sfs -s DPOD-fixpack-1_0_16_0.md5Do not interrupt the software update process after it has started.
Please review the upgrade log file if the console displays any error messages.
If SSH connection is lost during upgrade, the upgrade will still continue. Reconnect to the server and check the log files for the process status and outcome.
Manual Steps during the Software Update
Rerunning the Installer after an Operating System Update
Some versions upgrade the operating system (CentOS) when DPOD is installed in Appliance Mode.
In that case, the installer should be rerun manually after the OS upgrade is complete and the server is restarted.
Rerunning the Installer after an Installer Update
Some versions make changes to the installer file itself (MonTierUpdateInstaller.sh). In that case, the following message will be displayed, and the installer should be rerun manually: