Users Guide

Appendix A: JSON configuration file

EVO:RAIL relies on a JSON-formatted file to initially populate fields in the user interface. The end user is

presented with this data during initial appliance configuration (both for Customize and Just Go

workflows). The initial configuration file is found on the EVO:RAIL service datastore at: /usr/lib/

vmware-marvin/marvind/webapps/ROOT/WEB-INF/classes/default-config-static.json

Before configuring EVO:RAIL, customers must read through the Network configuration section in this

document and fill out the EVO:RAIL Network Configuration Table. Sample JSON configuration files that

correspond to the default values listed in this table are found in VMware KB articles for each EVO:RAIL

release.

A similarly formatted JSON file could be used with Upload Configuration File, which is available after you

select Customize. This feature allows you to use a modified configuration file on-site, after shipment

from Dell. The primary use case for this feature is a ROBO environment, where EVO:RAIL appliances are

distributed with a similar configuration file for multiple locations.

NOTE:

• The JSON file format may change throughout EVO:RAIL releases. Get the sample JSON file that

corresponds to the software release that your appliance was built with at the Dell factory and

then edit the sample file for your configuration.

• EVO:RAIL expects the data in the configuration file in a specific format. Any changes to the

JSON format results in unexpected results and/or stops responding.

• There is no built-in capability to generate and export an updated copy of an EVO:RAIL JSON

configuration file from the GUI.

Upload configuration file

Prepopulate a custom configuration file for use in the Customize workflow with the following steps:

1. Obtain a copy of the default-config-static.json file for the EVO:RAIL release that you are configuring

from VMware Knowledge Base 2106961.

2. Edit your new configuration file to insert the values from the EVO:RAIL Network Configuration Table.

3. Ensure that the filename has a .jsonextension.

4. Ensure that the file is in valid JSON format because EVO:RAIL are not validate the syntax (for

example, a missing comma causes the configuration file to fail). EVO:RAIL validates the content of a

correctly formatted JSON file in the same manner that it validates manual entries, verifying data entry

and performing deep validation prior to building the appliance.

5. Make this file accessible from the EVO:RAIL Configuration and Management workstation or laptop.