Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.

MID Server properties

Log in to subscribe to topics and get notified when content changes.

MID Server properties

Properties control the behavior of all MID Servers or a particular MID Server.

Links to each of the MID Server sectionsEnsure that the MID Server can connect to elements inside and outside your networkDownload and install the MID Server on a Linux or Windows hostConfigure your MID ServerConfigure MID Server securityEnsure that the MID Server can connect to elements inside and outside your networkDownload and install the MID Server on a Linux or Windows hostConfigure your MID ServerConfigure MID Server security

The MID Server properties are in the MID Server Property [ecc_agent_property] table and can be accessed by navigating to MID Server > Properties. To set these properties, you must add them, if they are not already present.

MID Server properties

alias_filtering_behavior
Sets the behavior of Discovery aliases. Behaviors define how strictly the system enforces the use of credential aliases in Discovery schedules.
The choices for behaviors are:
  • strict: Aliases defined for the credential must match the aliases configured for the probe.
  • loose: The probe's credential is used if it contains all the aliases specified in the schedule.
  • Type: string
  • Default value: loose
com.glide.closure_max_rows_per_table
Sets the maximum number of rows allowed in a table. This property is not visible by default and must be added.
  • Type: integer
  • Default value: 200000
concurrent.dist.download
Sets the number of concurrent MID Server auto-upgrades permitted by the instance. The default value of this property is 2, which allows the MID Server to use 2 of the 4 semaphores available on the instance for upgrading. If your instance has more than 4 INT semaphores, you can increase the value in this property to allow more concurrent upgrades.
  • Type: integer
  • Default value: 2
glide.stored_proc.data_type.validation
Stops validation of data types in stored procedure parameters. Use this property if you use Orchestration to run a stored procedure on MySQL, Oracle DB, and MS-SQL databases and you want to avoid performing data type validation. Restart the MID Server service after you change the value of this property.
  • Type: true | false
  • Default value: false
mid.aws.sts.assume_role.disable_credential_caching
Set this property to true to prevent the caching of temporary AWS credentials for Cloud Discovery.
  • Type: true | false
  • Default: false
mid.aws.sts.assume_role.credential_ttl_minutes
Set the number of minutes you want to cache temporary AWS credentials for Cloud Discovery.
  • Type: integer
  • Default: 60
mid.discovery.max_pattern_payload_size
Defines the maximum overall payload size for the payload of results that come from patterns.
  • Type: integer (bytes)
  • Default value: 300000

You can also configure this as a configuration parameter on a individual MID Server.

mid.discovery.max_payload_size
Specifies the maximum string length of Discovery results that the MID Server sends to the instance. If the Discovery probe results exceed the limit, the MID Server discards them and returns a warning message.

For probes, this applies only to those probes where the Used by Discovery field is true. For patterns, this applies to the Horizontal Pattern probe.

Set the value to any negative number to disable the payload limit and allow payloads of any size to be sent to the instance. For example, -1.

  • Type: integer (bytes)
  • Default value: 5000000

You can also configure this as a configuration parameter on a individual MID Server.

mid.discovery.multiprobe.skip_others_on_error
Prevents probes in a multi-probe from iterating through available credentials when another member probe has already failed or timed out. If this property is set to false, each probe in the multi-probe attempts to connect to the target with the same invalid credentials. This condition results in longer probe execution times on the MID Server.

This property is not visible by default and must be added to the sys_properties table to change the value.

  • Type: true | false
  • Default value: true
mid.eccq.max_payload_size
Specifies the maximum string length of a payload that the MID Server sends to the instance. The MID Server verifies the size of the payload before sending it to the instance. If the payload size exceeds the limit, the MID Server discards it and returns an error message in the payload.
  • Type: integer (bytes)
  • Default value: 20000000

You can also configure this as a configuration parameter on a individual MID Server.

mid.max_ci_count_per_page
Defines the size of each chunk in a payload of results that come from patterns. The chunk can be greater than this value, depending on the relationships of the CIs.
  • Type: integer (bytes)
  • Default value: 300000

You can also configure this as a configuration parameter on a individual MID Server.

mid.powershell.target_base_dir
Specifies the location of the target base folder used for Discovery using WMI. If another network share is mounted on each Window's target, the folder may be changed by updating this property.
  • Type: string
  • Default value: $admin share
mid.probe.use_legacy_forward_dns
Enables the legacy DNSNameResolver probe and disables the default DNSNameResolver probe. See Probes used by Orchestration for more information.
  • Type: true | false
  • Default value: false
mid.probe.use_legacy_reverse_dns
Enables the legacy DNS probe and disables the default DNS probe. If you experience problems with the features of the default DNS probe, use this property to disable those features. The default DNS probe's features include being lightweight and faster due to executing in parallel, while the legacy probe is throttled by the MID Server because it executes in serial. The default probe utilizes DNS lookup by the MID Server host OS to make use of the OS maintained DNS cache, while the legacy probe does not. Consequently, after a DNS lookup by the default probe fails in Windows systems, the OS also tries looking up by NETBIOS name.
  • Type: true | false
  • Default value: false
mid.process_flow.log_listener.max_size
Sets the maximum size in bytes of memory available to save log messages for Flow Designer actions running on a MID Server. The MID Server stores up to the limit in memory and discards additional log messages, then sends the messages back to the instance along with the execution plan.
  • Type: integer (bytes)
  • Default value: 10485760
mid.property.jdbc_operations
Tells the JDBCOrchestrationProbe what JDBC operations it is allowed to execute. Edit this property value to allow JDBC Orchestration activities to perform more operations. All operations are comma separated. Select a MID Server in the MID server field to define specific operations for that MID Server, or leave the field empty to apply the list of operations to all MID Servers. This property requires the Orchestration plugin.
  • Type: string
  • Default value: select,update,insert,delete,show,create,describe,begin,if,end,not,exists
mid.property.jms.command.allowed_factory_names
Comma delimited list of Java Messaging Service (JMS) connection factories that the MID Server requires for a custom JMS activity or action. This property requires the Orchestration plugin.
  • Type: string
  • Default value: connectionFactory, queueConnectionFactory, topicConnectionFactory
mid.property.ssh.use_snc
Enables the use of the SNCSSH client for Discovery and Orchestration. Change this property to false to use J2SSH. This property applies to all MID Servers connected to the instance.
  • Type: true | false
  • Default value: true
mid.servicewatch.max_concurrent_connections
Defines the maximum number of concurrent tasks sent to an individual host by a single MID Server.
  • Type: integer
  • Default value: 7
mid.sa.prefer_powershell
Enables MID Server to use PowerShell Remoting.
  • Type: True | False
  • Default value: false
mid.shazzam.regulator.interval_ms
Sets the interval, in milliseconds, in which Shazzam can launch packets.
  • Type: integer
  • Default value: 1
mid.shazzam.regulator.packets_per_interval
Sets the number of packets that Shazzam can launch in the time interval specified by the mid.shazzam.regulator.interval_ms property.
  • Type: integer
  • Default value: 1
mid.sm.discolog.max_log_size
Limits the length of the log statements in the Horizontal Discovery Log. If the results are truncated, the Command results reports, "Result is larger than [value] characters and was truncated by the logger."
  • Type: integer (characters)
  • Default value: 1000
mid.sm.discolog.max_object_size
Limits the length of the object in the Horizontal Discovery Log. Objects in the log statement are truncated to the number of characters set by this property's value. This property only affects the object character size in the Horizontal Discovery Log. The following message appears if an object is limited by this property "The max object size reached the maximum limit of [value]. To adjust this use the mid property mid.sm.discolog.max_object_size."
  • Type: integer (characters)
  • Default value: 1000
mid.snmp.use_getbulk
Specifies whether to use GETBULK to receive a large amount of data in batches. This can be used to globally configure all MID servers.
  • Type: true | false
  • Default value: true
GETBULK can also be set at the probe level or for an individual MID Server. Settings are listed in the order of precedence:
shazzam.chunk_size
Maximum number of IP addresses Shazzam will scan in parallel. This property primarily controls outbound port consumption.
  • Type: integer
  • Default value: 100

Create a MID Server property

Use a MID Server property to control either the behavior of all MID Servers or a particular MID Server.

Before you begin

Role required: admin

About this task

You set MID Server properties to override MID Server parameters. Configure MID Server properties in the MID Server plugin. Do not configure MID Server properties in the glide.properties file that is located in the properties folder of the agent. The glide.properties file gets overwritten during the upgrade process.

Procedure

  1. Navigate to MID Server > Properties.
  2. Click New.
  3. Fill in the fields, as appropriate (see table).
    Table 1. MID Server properties fields
    Field Description
    Name Enter the property name.
    Value You can enter the value you want the property to have.
    Note: If you are amending JDBC operations through the mid.property.jdbc_operations properties, you can enter verbs like BEGIN, END, IF, or common PL/SQL block statements. This will assist in being able to run CREATE or ALTER statements. You might have to restart the MID server before running some of the statements.
    MID Server Leave this field blank to set a MID Server property that affects all MID Servers. To set a MID Server property for a particular MID Server , select the MID Server.
  4. After setting any MID Server properties, restart the MID Server to ensure the properties sync with the instance.
Feedback