Configure a default MID Server for each application

You can configure a default MID Server on the application or MID Server record for all applications except Event Management.

Before you begin

Role required: agent_admin or admin

About this task

Applications are only available when their respective plugins are activated.
The default MID Server is used when applications fail to find a suitable MID Server that matches configured criteria during auto-select. The default MID Server for the ALL application is used if the default MID Server for the specific application is not available. Some applications also offer a property to set the default MID Server.
Important: If you configure a MID Server for ALL IP ranges (type Include) and also create an IP range of type: Exclude for the same MID Server, the system will ignore the excluded IP range for that MID Server.
The default MID Server does not need to meet any criteria (application, IP range, behavior, or capability) to be used. Specifying a default MID Server is optional, and you can use a MID Server as the default for more than one application.
Application Additional notes
Discovery Discovery attempts to use the default MID Server when the discovery schedule specifies Auto-Select MID Server and Discovery cannot find any MID Servers with the correct application and IP range.
Orchestration Orchestration attempts to use the default MID Server when it cannot find any MID Servers with the capabilities that you define in the Orchestration activity.

You can also specify a default MID Server. The value in that property automatically synchronizes with the default MID Server you select in the Orchestration application.

Service Analytics Not applicable. The MID Server is selected if it has the RCA capability. Route to right MID by domain.
Service Mapping Starting with the Istanbul release, fresh Istanbul installs use the default MID Server for the Service Mapping application. Upgrades to Istanbul still use the MID Server .
Event Management You can specify a default MID Server for Event Management using the mid.server.connector_default system property. Event Management does not use the default MID Server in the application record.
Cloud Management N/A

Procedure

  1. Configure the default MID Server for an application in the MID Server record.
    1. Navigate to MID Server > Servers and open a record.
    2. In the Supported Applications related list, click Edit.
    3. In the left column of the slushbucket, click the applications that can use this MID Server and move them to the right column.
      You can define which applications are included in the ALL option.
    4. Click Save.
  2. Configure the default MID Server for an application in the application record.
    1. Navigate to MID Server > Applications.
      The list of installed applications that can use MID Servers appears.
    2. Click the name of an installed application.
    3. On the MID Server Application form, select the MID Server in the Default MID Server field.
    4. To select additional MID Servers for this application, click Edit in the MID Servers related list and select alternate MID Servers that this application is allowed to use.
    5. Click Update.