Configuring Predix Edge Technician Console
If you do not want to use the default settings for Predix Edge Technician Console, you can configure certain settings by creating and deploying your own settings.json file.
About this task
When Predix Edge Technician Console starts, it checks for a settings.json file. If one exists, Predix Edge Technician Console parses the file and overwrites the default configuration parameters. If the file does not exist, Predix Edge Technician Console uses its default configuration parameters.
Note: If you deploy a settings.json file, Predix Edge Technician Console continues to use the values set in that file until a new settings.json file is deployed, even if the default configuration values for Predix Edge Technician Console change on the backend.
Procedure
- Create a file and name it settings.json.
- Configure the parameters in JSON format, and save the file. The following is an example settings.json file:
{ "maxOSUpdateFileSizeMB": 500, "maxStagingAggregateSizeMB": 1000, "sessionTimeoutSeconds": 600 }
The following table contains information about the configurable parameters.Parameter Description Default Value sessionTimeoutSeconds
Maximum time Predix Edge Technician Console can be idle before the user is logged out. - Default value is 900 seconds (15 minutes)
- Minimum value is 300 seconds (5 minutes)
- Maximum value is 3600 seconds (one hour)
900 maxStagingAggregateSizeMB
Maximum allocation, in megabytes, that can be used for all staged config packages, prior to applying them to applications. 1000 maxOSUpdateFileSizeMB
Maximum file size of the OS update image that you can upload to Predix Edge Technician Console. 500 - Deploy the configuration package.You can deploy the configuration using Predix Edge Technician Console or Edge Manager.Note: When you apply a new configuration, Predix Edge Technician Console restarts and you are signed out. You will need to sign into Predix Edge Technician Console again.