The CreatorCon Call for Content is officially open! Get started here.

Mid.version property in changing frequently

amanseth31
Tera Contributor

Hello, 

 

My instance version is - vancouver-07-06-2023__patch6-01-11-2024_01-22-2024_2201 while the property mid.version is changed to vancouver-07-06-2023__patch5-12-01-2023_12-11-2023_2006.

 

The property is changing frequently. When upgraded it was set correctly..after a week it went back to vancouver-07-06-2023__patch5-12-01-2023_12-11-2023_2006 and from then changing frequently between patch 5 and 6. 

 

Any thoughts. What could be the reason ?

2 REPLIES 2

Sumanth16
Kilo Patron

Hi @amanseth31 ,

 

It is possible to stop MID server from auto-updating by setting mid.version.override property in the system property table (sys_properties) or by configuration parameter mid.pinned.version.

The configuration may be set in the config.xml file of the MID server or in a property setting.

In addition to mid.version.override, the MID Server version can also be controlled with the configuration parameter mid.pinned.version which pins the MID Server to a specific version.To pin a MID Servers, set the mid.pinned.version parameter with the name of that version in the config.xml file of each MID Server. Use the format <version>-mm-dd-yyyy. This setting overrides the property setting for the pinned MID Server version. For instructions, see Add a MID Server parameter. The value set in this parameter is not affected by an upgrade.

Warning:Using mid.version.override and mid.pinned.version is not recommended. The different versions on the MID Server and instance can cause outage issues on the MID Server.

https://docs.servicenow.com/bundle/sandiego-servicenow-platform/page/product/mid-server/concept/c_Up...

If the reason to stop auto-upgrade is because MID server do not have Internet access, it's better to re-think the system architecture. It is recommended to place a MID server in the DMZ to allow Internet access.

Some of the MID server feature may not work properly if the version of the MID server and ServiceNow instance differs too much.

If the reason to not update the MID server is to continue using older features that are depreciated in the new version, it is probably better to switch over to the new feature because support of older feature may end.

For example, TLS1.1/1.0 will end. It is better to switch over to TLS1.2 rather than keep using TLS1.1/1.0 because TLS1.1/1.0 have security risks.

 

If I could help you with your Query then, please hit the Thumb Icon and mark it as Correct !!

 

Thanks & Regards,

Sumanth Meda

amanseth31
Tera Contributor

@Sumanth16 Thank you for the response. We wanted to keep the auto upgrade...and need to track the cause of change in value for mid.version property. 

Ideally property should remain same as of instance version.