From Versions Earlier than 7.0

ServicePlanner is a completely redeveloped product from that which was released prior to 7.0. Whereas ServicePlanner was a stand-alone product prior to 7.0, from 7.0 onwards it is a module of ServiceManager. Therefore versions of ServicePlanner prior to 7.0 should be removed, along with any geographic data, prior to installing the upgraded ServicePlanner.

From Version 7.0

The ServicePlanner that came with version 7.0 created its maps through a separate MapXtreme servlet. This was deployed with a mapxtreme.war file. This servlet is no longer used and so the WAR file is no longer distributed. Any remaining mapxtreme.war files and their related deployments should be removed.

Upgrading ServiceManager

When there is a new release of ServicePlanner, the ServicePlanner module will need to be uninstalled and then re-installed. This can be safely done without affecting the ServiceManager installation, although in practice ServicePlanner will mostly get updated along with ServiceManager.

Windows MSI Installer

If using the Windows MSI installer, then the installer is set-up so that ServiceManager can be uninstalled and reinstalled without interfering with any of its installed modules. As such, ServiceManager can be freely uninstalled and reinstalled without needing to re-run the ServicePlanner installer. The exception is if there is a need to move ServiceManager's modules directory then ServicePlanner will need to be reinstalled to the new location.
In order for the new files to be properly detected by ServiceManager the application will need to be redeployed and restarted twice, see section 5.3 of [6].

ZIP Release Bundle

Reinstallation of ServiceManager can be made without requiring reinstallation of ServicePlanner, but care needs to be taken. If the modules directory is under ServiceManager's installation directory then it will get deleted when ServiceManager gets deleted. In this case the modules directory will need to be moved to outside ServiceManager's installation directory before reinstallation of ServiceManager and moved back afterwards. The same goes for ServicePlanner's geographic data.
In order for the new files to be properly detected by ServiceManager the application will need to be redeployed and restarted twice, see section 5.3 of [6].