This topic describes how to use the servers.json
file to define the default connection behavior in OmniSci Immerse. It describes how to enable default behavior using servers.json
, provides basic syntax, and includes examples. You can define the OmniSci database to connect to, as well as the username and password. You can also configure Immerse to use additional tile sources for geo charts.
To enable default behavior through a servers.json
file, you must first edit omnisci.conf
to include servers.json
information:
In your OMNISCI_STORAGE directory, open omnisci.conf
. For information about omnisci.conf
and available options, see Configuration Parameters.
In the [web]
section of omnisci.conf
, reference servers.json
by adding the following line:
servers-json = "/servers.json"
Replace with the full path to servers.json
.
Save omnisci.conf
.
Property | Description |
| The name of the database that Immerse connects to by default. |
| Name of the database host. |
| ID number of the Immerse dashboard to load on login. |
| Dropdown menu of databases to select at login. Note: If you also provide the |
| Immerse user password. |
| Port used for connecting to the database host. |
| Connection protocol to use: |
| Universal resource locator. Defines the path to the source database. Can be used as an alternative to identifying host and protocol. |
| Name of the Immerse user. |
| Set to |
| Set to |
| Enable SAML in Immerse. The URL value is Identify Provider Single Sign-On URL. For more information about configuring SAML, see Connecting to OmniSci Using SAML. |
| Productize Immerse by customizing colors, login text, logo, and other UI elements. For more information, see Enable Custom Styles. |
| Specify and use basemap styles other than those provided with Immerse. For more information, see Enable Custom Basemap Styles for Geo Charts. |
You can create a servers.json
file to control the default configuration when you log in to OmniSci Immerse. The information in servers.json
can identify the database you connect to and credentials to use during automatic login.
If servers.json
does not exist yet, create a file by that name in the OMNISCI_STORAGE directory.
In servers.json
, specify the database to connect to, as well as username and password information. You can use host, port, and protocol to specify the path to the data:
[{"database": "<database_name>","port": "<port_number>","host": "<hostname>","protocol": "<protocol>","username": "<username>","password": "<password>"}]
Alternatively, you can define the data source using a URL:
[{"database": "<database_name>","url": "<URL>","username": "<username>","password": "<password>"}]
Save servers.json
.
If you leave the option values blank, the Immerse login form loads with blank fields.
The contents of servers.json
must be formatted as an array.
The feature_flags
section lets you set global default settings for the Immerse user interface.
Element | Description |
| Set to |
| Set to determine whether the filter panel is open by default ( |
| Determine if the filter panel opens in Simple mode ( |
| Set the default Immerse theme for all users. If a user has defined their own theme, that theme is used for that user's instance. If a user has not specified a theme, but the default theme is set in If no default theme is set, the system default is |
| Set to |
| Control whether the Data Catalog is enabled in Immerse. The value is |
| Linked zoom is disabled by default ( |
| Set to |
| Controls whether the New Combo chart is available in Chart Editor, and also controls whether Duplicate as New Combo is available. |
| By default ( |
| Sets the limit for rows exported in map charts. Default: 100,000. |
| Adds additional restrictions to the VIEW-only experience. If set to |
| Set to |
| Controls visibility of the UI Settings panel for non-superusers. Panel is available by default ( |
| Controls visibility of Label defaults in the UI Settings panel for non-superusers. Label defaults is available by default ( |
| Enable ability of non-superusers to configure chart margins. Set to |
| Controls visibility of the Color palette in the UI Settings panel for non-superusers. The Color palette is available by default ( |
| Controls whether the filter panel opens in expanded view or in Simple View. |
To productize OmniSci Immerse, you can add the customStyles
JSON object to servers.json
. Use the customStyles
elements to:
Customize colors
Customize the text displayed in the browser tab
Add your own logo
Customize the login text
Disable the Help menu dropdown on the navigation bar
Element | Description |
| Button color when inactive |
| Button color when hovering. |
| Hexadecimal color definitions used in charts. |
| Custom colors, requires 11 or more colors. These are the options available in the Color by Dimension pop-up. |
| URL to your dark mode logo. You can set different logos for light and dark mode. If no dark mode logo is configured, the logo defined in Must be a browser-accessible http(s) URL, not a file system path. |
| Set to |
​ | ​ |
| Specify custom text for the Immerse login page. |
| URL to your logo. You can set different logos for light and dark mode. If a dark mode logo is configured in Must be a browser-accessible http(s) URL, not a file system path. |
| 4 scales, 1 or more colors each scale. Defines a range of colors that measures iterate through repeatedly. The size of the range can vary. |
| 4 scales, 1 or more colors each scale. Quantitative measures produce smooth, continuous gradients between each "stopping point" defined in the list of colors, in order. |
| Button color when pressed. |
| Solid colors, requires 8 or more colors. All measures are assigned one color. The array of colors you provide defines which colors are available. |
| Text displayed in the browser tab. |
You can also set fonts and colors in the Immerse UI Settings panel. For more information, see Configuring the Dashboard User Interface.
There are no visual design guarantees when using a large number of colors. For example, visual elements might bleed beyond borders or have an unexpected layout.
Custom styles do not affect the settings for charts or dashboards saved before the custom styles are defined. However, you can edit existing charts and replace the colors in use to colors in your custom palette.
The following example shows a complete servers.json
file that includes customization. When you want to change any of the settings in servers.json
, you must replace all settings in servers.json
, even if you duplicate the default values.
[{"database": "omnisci","url": "localhost","port": "6273","username": "admin","password": "HyperInteractive","feature_flags": {"ui/default_theme": "light"},"customStyles": {"logoURL": "http://www.omnisci.com/docs/latest/images/3_panda.png","loginText": "Log in to Panda Bear Wear Ware","title": "Where Panda Bear Wear Ware Wearers Dare Care","buttonPrimaryColor": "#888888","buttonSecondaryColor": "#444444","buttonSecondaryHighlightColor": "#000000","colors": {"solid": ["#333333","#555555","#777777","#999999","#aaaaaa","#cccccc","#eeeeee","#ffffff"],"custom": ["#000000","#eeeeee","#222222","#cccccc","#444444","#bbbbbb","#666666","#aaaaaa","#333333","#dddddd","#111111"],"ordinal": [["#111111","#cccccc"],["#111111","#777777","#cccccc"],["#111111","#555555","#999999","#bbbbbb","#eeeeee"],["#111111","#333333","#555555","#777777","#999999","#bbbbbb","#dddddd","#eeeeee"]],"quantitative": [["#555555","#cccccc"],[ "#111111","#eeeeee"]]}}}]
This example is for the totally-not-made-up company Panda Bear Wear Ware, where you can find all of your Panda Bear Wear Ware in one lair with time to spare. There is an understandable predilection toward black, white and everything in between on their color palette.
The first section contains branding information for their OmniSci Immerse instance.
"logoURL": "http://www.omnisci.com/docs/latest/images/3_panda.png","loginText": "Log in to Panda Bear Wear Ware","title": "Where Panda Bear Wear Ware Wearers Dare Care","buttonPrimaryColor": "#888888","buttonSecondaryColor": "#444444","buttonSecondaryHighlightColor": "#000000",
The logo, labeling, and button colors are visible at the dashboard level.
The Solid palette colors all items in Line, Pie, Bar, and other charts with one color. You can define the array of available colors.
"colors": {"solid": ["#333333","#555555","#777777","#999999","#aaaaaa","#cccccc","#eeeeee","#ffffff"],
The Ordinal palette defines a range of colors that are iterated repeatedly in a chart with many values. You can define multiple ranges from which to select.
" ordinal": [["#111111","#cccccc"],["#111111","#777777","#cccccc"],["#111111","#555555","#999999","#bbbbbb","#eeeeee"],["#111111","#333333","#555555","#777777","#999999","#bbbbbb","#dddddd","#eeeeee"]],
For example, a Pie chart can cycle through colors on the Ordinal palette to color each segment.
The Custom palette populates the Custom and Color By Dimension pop-ups, allowing you to assign specific colors to one or more values.
"custom": ["#000000","#eeeeee","#222222","#cccccc","#444444","#bbbbbb","#666666","#aaaaaa","#333333","#dddddd","#111111"],
The Quantitative palette gives a range of two or more colors. Values are expressed as a gradient on a continuum between the colors you define. You can create multiple value sets.
"quantitative": [["#555555","#cccccc"],[ "#111111","#eeeeee"]]
If you work extensively with geospatial data, you might need to use basemap styles that are different than those provided by Immerse. By modifying servers.json
, you can use custom map styles created with Mapbox Studio, as well as third-party OGC-compliant raster tile sources.
To use different basemap styles, add the mapboxCustomStyles
property, and then define the source.
Note: Entering a source incorrectly can result in unexpected behavior in the geo charts, or cause Immerse to not load. Make sure that mapboxCustomStyles
is an array, and that the objects in the array have label
and value
properties. To avoid errors, consider using a JSON validator like JSON Lint to make sure the code is correctly formatted before starting Immerse.
The following example syntax shows how to add custom base maps using the mapboxCustomStyles
property, in the following order:
A custom map style created in Mapbox Studio and hosted on mapbox.com.
A basemap style hosted on a Mapbox Atlas Server.
A third-party OGC-compliant raster tiles source not affiliated with Mapbox. This source must adhere to the Mapbox Style Specification.
[{"database": "<database>","password": "<password>","url": "<omnisciserver>","port": "<port_number>","username": "<username>","mapboxCustomStyles": [{"label": "custom-mapbox-studio-source","value": "mapbox://styles/omnisci/<mapbox-studio-style-id>"},{"label": "mapbox-atlas-source","value": "http://<domain>:<port>/pages/<style_name>/<style_name>.json"},{"label": "3rd-party-raster-source","value": {"version": 8,"sources": {"openstreetmap": {"type": "raster","tiles": ["http://a.tile.openstreetmap.org/{z}/{x}/{y}.png","http://b.tile.openstreetmap.org/{z}/{x}/{y}.png"],"tileSize": 256}},"layers": [{"id": "openstreetmap","type": "raster","source": "openstreetmap","minzoom": 0,"maxzoom": 22}]}}]}]