In certain scenarios, you might want to override the default values provided in the application.properties file. Using the SEG V2, you can manually override the values in the application.properties file using an external configuration file, instead of modifying the application.properties file.
The following procedure describes the steps to configure the external configurations file.
In addition to the configuration received from the Workspace ONE UEM console, the SEG V2 uses certain values from the local configuration file at SEGDir/config/application.properties. During a SEG V2 upgrade, the values in the older application.properties file are discarded and the external configuration file retains any overridden values when the new version of SEG is installed. In case, any values need to be modified, update the external configuration file. During a SEG upgrade this helps to retain the customer overridden configuration values.
- Create a folder in the server machine where SEG V2 is installed, and create a subdirectory where the override file is located.
For example, create a subdirectory with name config-override under the SEG installation directory C:\AirWatch\SEG\.
- Browse to the newly created folder and create a properties file.
For example, if the file name is seg-application-override.properties, full path of the file might be C:\AirWatch\SEG\config-override\seg-application-override.properties.
- Navigate to .
- Click the Advanced System Settings link on the left-side panel, and then click Environment Variables.
- Create a system variable. Add the additional.spring.config.location value for the Variable name and provide the full path of the file created in Step 2 as Variable value.
- Save the newly created file and click OK. As per the example in Step 2, the value of the system variable is C:\AirWatch\SEG\config-override\seg-application-override.properties.
- Open the properties file created in Step 2 in any text editor, add the property key-value pairs that you want to override and save the file. Any changes to this file take effect only after the SEG service is restarted.
- Restart the SEG service and check if SEG is using the overridden values from the external configuration file.
What to do next
After restarting SEG, the overridden values from the external configuration file is used. Verify that the functional behavior of SEG is as per the overridden values.
SEG provides an API to verify if any invalid keys are configured in the external configuration file. Enter /diagnostic/invalidconfigkeys in the Diagnostics tab of the Admin UI to access the invalid keys.