Common Network Viewer Configuration
Flex, OMA, and the Java client use a common map renderer and map configuration mechanism, allowing them to share most map configuration. Flex and Java use the same Common Network Viewer (CNV) configuration files because their users generally need the same map rendering, filtering, and behavior. Client-specific configuration, options, and rendering are still supported; see
Configuring the Java Common Network Viewer for details. To support product-specific adjustments, the products use a base map configuration file and an overrides configuration file. The overrides use the Flex configuration mechanism described in the
NMS Flex Operations Configuration chapter to selectively override the base configuration.
Use the Java/Flex configuration as the master and design it for their shared rendering requirements, which are generally more complex than those of OMA field crews. Use OMA configuration overrides to suppress content that is not needed in OMA.
For Flex, the base configuration and overrides file should be placed at
• $NMS_BASE/flex/config/map/mapConfig.jsonc
• $NMS_BASE/flex/config/map/mapConfigOverrides.jsonc
Note that the product map configuration is split over multiple files where each file contains the configuration for a particular area of the map configuration. This is done via a "flex-include" syntax within the jsonc files, for example
"declutterRules": "flex-include: declutterRules.jsonc",
It is recommended to use the same division of files for your configuration, to make it easier to compare and apply changes from base product map configuration files in future.
It is also recommended to use the WinSCP/VS Code setup used for standard Flex development to edit the configuration files (see
Recommended Tools for more information). In addition is recommended to install and setup Inkscape (or your SVG editor of choice) as the external editor for
.svg files, to allow SVG symbol files to be easily edited.
For OMA, the base configuration and overrides file are built in when the build is performed and exist in the base product source code at:
• src/js/resources/config/mapConfig.jsonc
• src/js/resources/config/mapConfigOverrides.jsonc
You edit these files directly to modify the map configuration.
Note: When developing OMA using the npm run serve command (or by directly running the Oracle JET development server, but it is recommended to use the npm run serve command), any changes made to map configuration or SVG files will automatically reload in the map, making it very quick and easy to test map configuration or SVG files using OMA.