The portaldb.json file captures all configuration settings specified when a DivePort portal is constructed. It contains details about the environments, pages, portlets, groups, and users.
Multiple DivePorts can be run on the same portaldb.json file. This is how DivePort supports clustering. When one portal changes the portaldb file, the others are aware of the timestamp change within a few seconds and reload the file.
The portaldb.json file is stored in the DI\Solution\webdata\<diveport>\database folder.
CAUTION: If administrators attempt to change the file in two portals at the same time, changes from only one of the portals are committed, and the administrator on the other portal receives an error saying that their change was lost. To avoid this conflict scenario, DI recommends that in a cluster, all administration changes are made from a single portal.
Version compatibility
You cannot import a DivePort 7.1 portaldb.json file to an earlier version of DivePort.
After an upgrade, in order for DivePort to be able to replace the map_data.dat file in the webdata directory, which is a local cache of map data downloaded from DiveLine, Tomcat must have permission to delete that file.
NOTE: DivePort 6.4 and earlier use a portaldb.xml file. When you upgrade to DivePort 7.x, if DivePort detects a portaldb.xml file, it uses the contents to create a portaldb.json file. It leaves the xml file in place which permits older DivePort versions to continue to use the same dataroot.