Settings File (3D Graphic Data Service) - Integration - Ver. 3.7.0.3 - Administration & Configuration - Hexagon

HxGN VDS Install and Setup

Language
English
Product
Integration
Search by Category
Administration & Configuration
VDS Version
3.13

The Diagnostic Utility reads the Himalaya.json settings file from the standard Program Data location in the HxGN 3D Graphic Data Service. While an upgrade to the software does not overwrite the existing settings file, a new copy of the Himalaya.sample.json settings file can be found in the %PROGRAMDATA%\HxGN 3D Graphic Data Service\Settings folder. You can use the generated sample file to update and correct your existing settings file.

The Diagnostic Utility detects the following:

If there is an incomplete or invalid JSON in the settings file, the error message indicates which site node in the data feeds section contains the problem. If any issue is found in the settings file, run the VDS Configuration Utility again, and then click Save & Configure.

  • Service settings file (Himalaya.json) could not be found on this machine

Ensure that the settings file is in the standard Program Data location unless the 3D GDS Service is not going to be running on this system.

  • Error reading settings file (Himalaya.json)

This error indicates a problem in the Himalaya.json settings file. Compare it to the Himalaya.sample.json settings file to help identify the issue.

  • Incomplete "site" settings found in data feed in settings file

Current site settings from the Himalaya.sample.json settings file are shown below. Ensure that the Himalaya.json settings file contains valid entries by comparing entries to those in the sample settings file.

  • Incomplete "smartmq" settings found in data feed in settings file

Current smartmq settings from the Himalaya.sample.json settings file are shown below. Ensure that the Himalaya.json settings file contains valid entries by comparing entries to those in the sample settings file.

  • Incomplete "httpClient" settings found in data feed in settings file

Current httpClient settings from the Himalaya.sample.json settings file are shown below. Ensure that the Himalaya.json file contains valid entries by comparing the entries to those in the sample settings file.

  • Incomplete "oauth" settings found in data feed in settings file

Current oauth settings from the Himalaya.sample.json settings file are shown below. Ensure that the Himalaya.json file contains valid entries by comparing them to entries in the sample settings file.

  • Obsolete "tokenEndpoint" found in data feed in settings file

The settings file contains obsolete tags for authorization. Ensure that the Himalaya.json file is updated with latest settings required for authorization.

  • Incomplete "logging" settings found in data feed in settings file

Current logging settings from the the Himalaya.sample.json settings file are shown below. Ensure that the Himalaya.json settings file contains valid entries by comparing them to entries in the sample settings file.

  • Invalid "plantsURL" settings found in the data feed in the settings file

The plantsURL field in the site settings must contain one of the following:

  • A valid URL containing the list of plants to retrieve.

  • A comma separated list of plants to be used.

If the field is blank, the database name will be used as the plant name.