IBM DataPower Operations Dashboard v1.0.16.0
A newer version of this product documentation is available.
You are viewing an older version. View latest at IBM DPOD Documentation.
Upgrade to 1.0.16.0 - Special Steps
Create a Missing Directory
The following steps apply only to the DPOD cell members.
Before applying the upgrade to 1.0.16.0, please execute the following command to create the directory in case it is missing:
mkdir -p /data/es-raw-trans
Remove non-DPOD Directories with a Prefix of /data
The following steps apply to all DPOD installations (All-in-One, cell manager and cell members).
Before applying the upgrade to 1.0.16.0, please make sure there are no non-DPOD directories that start with /data
, such as /data-old
, /datapower
, /data_backup
, etc. If such directories exist, please delete or rename them.
Valid DPOD data directories start with /data
and are optionally followed by a number, such as /data
, /data2
, /data33
, etc.
Non-DPOD directories that start with /data
will cause the upgrade to 1.0.16.0 to fail.
You may restore the directories you deleted or renamed after applying the fix.
Remove Unused Properties from the Retention Configuration File
The following steps apply to all DPOD installations (All-in-One, cell manager and cell members).
Some installations might have unused properties in the retention configuration file, which may cause the upgrade to 1.0.16.0 to fail with the following error:
File /app/hk_retention/MonTier-HK-ESRetention/conf/MonTierHousekeeping.conf contains placeholders
Before applying the upgrade to 1.0.16.0, please execute the following commands:
sed -i '/elasticsearch\.index\_set\.logical\-tran\-full\.max\_size\=.*/d' /app/hk_retention/MonTier-HK-ESRetention/conf/MonTierHousekeeping.conf sed -i '/elasticsearch\.index\_set\.iib\-log\-tran\.max\_size=.*/d' /app/hk_retention/MonTier-HK-ESRetention/conf/MonTierHousekeeping.conf sed -i '/elasticsearch\.index\_set\.iib\-stats\-tran\.max\_size=.*/d' /app/hk_retention/MonTier-HK-ESRetention/conf/MonTierHousekeeping.conf
Internal Alerts May Appear About the Reindex Manager
After the upgrade to 1.0.16.0 completes successfully, the following internal alert may appear once or twice:
This is expected and does not indicate an issue with the upgrade.
However, if the internal alert is triggered continuously, please open a support case.