How to update Read-only Config Parameters and Wrapper Config Parameters for Containerized MID Servers SummaryImportant Note: Since Washington DC, we added a logic to the init script that is able to detect a change in the environment variables in the YAML file and automatically update the config and wrapper config files. If you are using the new docker recipe in Washington DC, you can ignore the rest of this article. The read-only MID Server config parameters and wrapper config parameters in MID Server profile are not automatically synced to an existing containerized mid server. If you make a deployment request linked to the profile and export it to an YAML file, these parameters are exposed to the container as environment variables. When a new Containerized MID Server is created for the first time using the YAML file, there is an init script that looks at environment variables and updates config.xml and wrapper-override.conf accordingly. After that the MID Server is marked as "initialized" (It created a file named .initialized in the /opt/snc_mid_server/agent folder). This step is done only once. If a MID Server is already initialized, the changes in environment variables do not go to config.xml or wrapper-override.conf. The "Sync to MID Servers" UI button on the MID Server profile form only works for writeable config parameters and MID Server properties on the instance side. These parameters will be synced down to the mid server via the updateConfig system command. In order to update wrapper-override.conf or read-only parameters in config.xml, you have to update the environment variables in the YAML file as shown in the example below (s. the sample YAML files attached to KB1325173 - - How to build and deploy Containerized MID Servers in Kubernetes using StatefulSets# You can put mid config parameter or wrapper config parameters here# Env variable name for MID config parameter starts with MID_CONFIG_ followed by the config parameter name where a dot is replaced by double underscores.# Env variable name for Wrapper config parameter starts with MID_WRAPPER_ followed by the wrapper parameter name where a dot is replaced by double underscores.- name: MID_CONFIG_mid__log__levelvalue: debug- name: MID_WRAPPER_wrapper__java__maxmemoryvalue: '2024'After that you need to re-deploy the mid servers. If you are using StatefulSet, you need to delete the persistent storages before re-deployment.Related LinksThe MID Server config parameters are documented at the link below. Please choose the release version matching to your instance. There is a pending doc task to update the documentation with info about the read-only attribute. If you tried to add/update a read-only parameters to a MID Server record on the instance you will see an error saying that it is not allowed. These parameters must be set directly in config.xml. https://docs.servicenow.com/bundle/utah-servicenow-platform/page/product/mid-server/reference/mid-server-parameters.html