MID Server upgrade to the Istanbul release

The Istanbul release of the MID Server introduces features such as application assignment and changes the way various applications select MID Servers.

When your instance and MID Servers upgrade to the Istanbul (and later) releases, an application (such as Discovery, or Service Analytics) is assigned to the MID Server depending on what plugins you have active and what capabilities are already assigned to the MID Server. This application, along with IP range settings, determine which MID Server is eligible for an application to use. Service Analytics, Service Mapping, and Orchestration no longer use the combination of capabilities and IP ranges to determine which MID Server to use. The upgrade removes certain capabilities such as Analytics and ServiceMapping from MID Servers after assigning correct applications.

Capabilities for Service Analytics and Service Mapping

The upgrade process checks for existing capabilities assigned to MID Servers. If no Service Mapping or Service Analytics capabilities are applied to MID Servers, then the upgrade allows ALL applications to use MID Servers, meaning any application can use the MID Server. If the upgrade detects capabilities, note the following:
  • For the Analytics capability: If the upgrade detects a MID Server with the Analytics capability, the Service Analytics application is assigned to the MID Server. Only the Service Analytics application can use that MID Server.
  • For Service Mapping capabilities: If the upgrade detects that a MID Server has Service Mapping capabilities, then the Service Mapping application is assigned to the MID Server. If the upgrade detects that no MID Servers have Service Mapping capabilities, then any MID Server that does not already have the ServiceAnalytics capability is available for Service Mapping, but the application assignment depends on the other items mentioned in this topic.

Discovery schedules

Any MID Server that is specified in a Discovery schedule is assigned the Discovery application (unless it is already assigned the ALL application.)

The Discovery Schedule form is upgraded to the new version, which specifies the MID Server selection method field. The value for this field is set to:
  • Use Behavior if a behavior was already specified.
  • Auto-Select MID Server if no MID Server is specified.
  • Specific MID Server if a MID server is referenced and is not part of a cluster. The reference to the same MID Server is retained. The Discovery application is also applied to the specified MID Server if the ALL application had not already been applied.
  • Specific MID cluster: if a MID Server is referenced and it is part of a cluster. The specific MID Server reference is not retained. If the MID server belongs to both load balancing and a failover clusters, the failover cluster is used. If no failover cluster is available, a load balance cluster is used.

Orchestration

If a MID Server does not have the Analytics capability, the upgrade assigns the Orchestration application. Any existing Orchestration capabilities are retained. If a MID Server is specified, the upgrade preserves the same MID Server as the default for the Orchestration application.

IP Ranges

The upgrade preserves any IP ranges that are already configured for a MID Server. If no IP ranges are specified, the ALL IP range is assigned. The ALL IP range allows the MID Server to pass the IP range criteria used for selection.

Pre-upgrade testing

Before you upgrade an instance, run these manual tests to ensure that the MID Servers for that instance can upgrade successfully. Testing helps you identify issues that could cause a MID Server outage or require reinstallation.

  1. Log in to each MID Server using the appropriate user account for that MID Server.
  2. Check that there is at least 1GB of free disk space. This is necessary to accommodate the download package required for the upgrade.
  3. From the MID Server host, use a browser to open https://install.service-now.com/test/test.html. You must have access to this server to download the installation package.
  4. Check that the MID Server user account has the correct file permissions on the server.
    • Navigate to the agent folder where the MID Server is installed to ensure access.
    • Create a new text file in the folder and then delete it to ensure the account has rights to manage the temporary folder created during installation.
  5. For Windows MID Servers, verify that the Log on as user for the Windows service is either:
    • Local System (default)
    • A user who is part of the local Administrators group.┬áDomain administrators are part of the local Administrators group by default.