Configure Custom MID server Upgrade URL - Support and Troubleshooting

Configure Custom MID server Upgrade URL Description: When the MID Server is being upgraded, upgrade packages are downloaded from https://install.service-now.com . This is a publicly accessible server and some customers' access to https://install.service-now.com may be blocked, which causes the MID Server upgrade to fail.

To avoid this issue, you can customize the https://install.service-now.com URL to your own web server to download the upgrade packages. The OOB system property mid.install_server.base_uri is set to https://install.service-now.com by default and can be modified by a maint user to set a custom web server URL. Then the MID Server upgrade will download packages from the custom web server URL instead.

There are two steps to configure the MID Server URL. These steps must be repeated for every family release.

Download the MID Server packages and upload them your own web server, which can be reached by your MID Servers. Modify the mid.install_server.base_uri property to include your web server base URL.

Download the MID upgrade packages and upload to the your own Web Server which can be reached by MID servers:

1) Run the following script in background script to get the upgrade packages URLs required for MID upgrade.

Note: If the MID Server's OS is Linux, replace Windows with Linux in the following script.

/***********************/

var midBuildStamp = gs.getProperty('mid.buildstamp');

var os = 'windows'; // for linux OS replace windows with linux

var result = {

'result': {

midPackage: []

}

};

var packages = [

new MIDPackage('mid-core', midBuildStamp, 'universal', 'universal'),

new MIDPackage('mid-upgrade', midBuildStamp, 'universal', 'universal'),

new MIDPackage('mid-jre', midBuildStamp, os, 'x86-64')

];

for (var i = 0; i

var pack = packages[i];

var uriFactory = new MIDPackageUriFactory(pack, 'auto_upgrade');

uriFactory.setMidSysId("");

result.result.midPackage.push({

'filename': pack.getLegacyFilename(),

'url': uriFactory.getUris()

});

}

gs.info(result.result.midPackage[0].url.toString());

gs.info(result.result.midPackage[1].url.toString());

gs.info(result.result.midPackage[2].url.toString());

gs.info(result.result.midPackage[1].url.toString().replace('universal.universal', 'preUpgradeCheck'));

/***********************/

Result: The output of the script will result in 4 URLs.

2) Copy paste each URL in a browser and download these 4 files from install-service-now.com .

3) Place these files in your web server where your MID Server can access them.

Example: https://install.service-now.com/glide/distribution/builds/package/mid-core/2023/10/08/mid-core-10-09-2020_10-08-2023_2043.universal.universal.zip file

should be placed in:

https://{yourserverIPorDomain}/glide/distribution/builds/package/mid-core/2023/10/08/mid-core-10-09-2020_10-08-2023_2043.universal.universal.zip

Note: The web server where the upgrade files are placed should be reachable to MID Server. Make sure the upgrade packages are accessible without any credentials.

Modify the mid.install_server.base_uri system property to include the Web Server Base URL:

1) Default is https://install.service-now.com .

2) User must have the maint role to modify this property and set it to a custom Web Server URL, for example: https://{yourserverIPorDomain}

Note: This could be one time change and no need to modify this property for every release, unless Web Server URL changes.

Once these steps are completed, you can trigger the MID Server upgrade to download from the new URL.