3.7.1 What to check before upgrading
Before upgrading, perform the following tasks:
-
To prevent script errors during login after the upgrade, clear the web browser's cache.
The cache needs to be cleared on all web browsers that will be used to access Navigation Platform after the upgrade.
-
If you are using JP1/Base for user authentication, upgrade JP1/Base before upgrading Navigation Platform.
Next, in order to upgrade, the following requirements must be satisfied:
-
Navigation Platform must be running, stopped, or not yet set up.
-
All steps in the upgrade procedure must be performed in the same machine environment.
-
The command must be executed by the user who installed Navigation Platform.
-
The server must have enough free disk space.
Note that the data shown in the table below is outside the scope of an upgrade. If you have such data, take the actions shown in the table before upgrading.
No. |
Type of data |
Data |
Action |
---|---|---|---|
1 |
Navigation Platform settings |
Configuration software log size |
No action necessary. |
2 |
Collection target path setting for the troubleshooting data collection command |
No action necessary. |
|
3 |
Collection target path setting for the IT Report Utility (systoru command) |
No action necessary. |
|
4 |
Data created by developers |
WTP (Eclipse Web Tools Platform) data |
Use the version of Eclipse that is included with the post-upgrade Navigation Platform. |
5 |
I/O Plugin created using a uCosminexus Navigation Developer version earlier than 09-50 |
Delete the data from the Operational Content beforehand so it does not cause errors when imported. |
|
6 |
Menu areas customized by HTML or JSP |
No action necessary. |
|
7 |
Application server settings |
Cosminexus Management Server settings |
Reconfigure the settings based on the description about changing the J2EE server settings in the Hitachi Navigation Platform Development Guide. |