What you do:
This message indicates that there were changes made in your environment that need to be committed in the database before new products can be added into the database. So go to System Preferences and apply ConfigDB for changes to be committed. Also you can discard changes to proceed with the upgrade.
We all know that enabling cache methodology saves a lot of bandwidth when there are very fw changes on the webpages. Maximo among large organizations is also among the cases where we can enable the caching mechanism to make the experience faster and smoother. With this, the locations which have lower connectivity speed will also see improved performance.
Starting Maximo 6 version, cache feature is present in the tool. The Client browser is made to store the static content and a variable MAXAGE helps to renew it. After MAXAGE variable value, the server renews the cache data.
The MAXAGE variable is present at location : (maximo_home)/applications/maximo/maximouiweb/webmodule/WEB-INF/web.xml
the default is set to 1 hour(3600 seconds) however you can change this value according to your requirement. There are instances where people have used 12 hours and 24 hours also as the cache expiry time.
So if your Maximo environment is stable and no changes are planned to be moved, then enabling cache would help to improve the response time in high latency environments.