---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# MID Server properties

# MID Server properties {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 16 Minuten Lesedauer

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

|-|
|   |
[ ]

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

## MID Server properties {#r_MIDServerProperties__section_e1y_zky_sfb}

alias_filtering_behavior
:   Sets the behavior of Discovery aliases. Behaviors define how strictly the system enforces the use of credential aliases in Discovery schedules.

    * Type: string
    * Default value: loose

    {#r_MIDServerProperties__ul_fzb_p4d_j2b}  
    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.
    {#r_MIDServerProperties__ul_bh2_z4d_j2b}

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
    {#r_MIDServerProperties__ul_xwz_mym_mfb}

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
    {#r_MIDServerProperties__ul_wsw_tfh_nhb}

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
    {#r_MIDServerProperties__ul_psj_jjz_r1b}

mid.discovery.max_ci_count_per_page
:   Defines the maximum CI count per page.

    * Type: integer (bytes)
    * Default value: 500

    {#r_MIDServerProperties__ul_plz_skz_cmb}

    You can also configure this as a [configuration parameter on a individual MID Server](https://servicenow-prod.fluidtopics.net/VYH5xHLIPq1GhC9qbQDc9Q#t_SetMIDServerParameters "Use a MID Server parameter to control the behavior of a particular MID Server.").

mid.discovery.max_related_count_per_page
:
    * Type: integer
    * Default: 100
    {#r_MIDServerProperties__ul_ll4_kh1_lbc}

mid.discovery.max_relation_count_per_page
:   Splits the payload based on the number of relations in
    it.

    * Type: integer
    * Default: 10000
    {#r_MIDServerProperties__ul_yhg_1rp_cfc}

mid.discovery.max_total_items_size_per_page
:   Splits the payload based on the size of the items.

    * Type: integer
    * Default:
    {#r_MIDServerProperties__ul_egz_kh1_lbc}

mid.aws.sts.assume_role.disable_credential_caching
:   Set this property to true to prevent the caching of temporary
    credentials for Cloud Discovery. For more information, see [Access setup for AWS service
    accounts](https://www.servicenow.com/docs/access?context=access-aws-accounts&version=australia&pubname=australia-it-operations-management&ft:locale=en-US)
    [Access setup for AWS service accounts](https://www.servicenow.com/docs/access?context=access-aws-accounts&version=australia&pubname=australia-it-operations-management&ft:locale=en-US).

    * Type: true \| false
    * Default: false
    {#r_MIDServerProperties__ul_lbk_fkz_cfb}

mid.aws.sts.assume_role.credential_ttl_minutes
:   Set the number of minutes you want to cache temporary credentials for Cloud Discovery. For more information, see [Access setup for AWS service
    accounts](https://www.servicenow.com/docs/access?context=access-aws-accounts&version=australia&pubname=australia-it-operations-management&ft:locale=en-US)
    [Access setup for AWS service accounts](https://www.servicenow.com/docs/access?context=access-aws-accounts&version=australia&pubname=australia-it-operations-management&ft:locale=en-US).

    * Type: integer
    * Default: 60
    {#r_MIDServerProperties__ul_xym_3kz_cfb}

mid.ca.certificate.api.request.retry.count
:   Indicates how many times the Certificate Import query will retry after the rate limit
    has occurred.

    * Type: integer
    * Default: 3
    {#r_MIDServerProperties__ul_opd_fqn_3kb}

mid.ca.certificate.api.request.retry.interval
:   Used to delay Certificate import from CAs when the rate limit has occurred.

    * Type: integer
    * Default: 30000
    {#r_MIDServerProperties__ul_llb_1qn_3kb}

mid.cloud.discovery.bypass.proxy

:   This configuration parameter accepts a comma separated list of DNS/IP addresses of proxy servers. The listed proxy servers are bypassed during Cloud Discovery. To bypass proxies on multiple cloud service providers (such as
    AWS or Azure), a separate MID Server must be set up for each provider. Otherwise, the MID Server proxy configuration is followed normally.

    * Type: string
    * Default value: none
    {#r_MIDServerProperties__ul_kjd_jv5_gxb}

mid.discovery.file_transfer_protocol
:   Used to determine the file transfer method used for probes or patterns.

    * Type: Choice (SCP or SFTP)
    * Default: SCP
    {#r_MIDServerProperties__ul_wll_nnl_ntb}

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: 50000000

    {#r_MIDServerProperties__ul_ofs_qbr_t1b}

    You can also configure this as a [configuration
    parameter on a individual MID Server](https://servicenow-prod.fluidtopics.net/VYH5xHLIPq1GhC9qbQDc9Q#t_SetMIDServerParameters "Use a MID Server parameter to control the behavior of a particular 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](https://www.servicenow.com/docs/access?context=r-HorizontalPatternProbe&version=australia&pubname=australia-it-operations-management&ft:locale=en-US).

    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

    {#r_MIDServerProperties__ul_hyv_1jv_tp}

    You can also configure this as a [configuration
    parameter on a individual MID Server](https://servicenow-prod.fluidtopics.net/VYH5xHLIPq1GhC9qbQDc9Q#t_SetMIDServerParameters "Use a MID Server parameter to control the behavior of a particular MID Server.").

mid.discovery.multiprobe.skip_others_on_error
:   Prevents probes in a [multi-probe](https://www.servicenow.com/docs/access?context=r_MultiprobesIncludedWithDiscovery&version=australia&pubname=australia-it-operations-management&ft:locale=en-US) 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
    {#r_MIDServerProperties__ul_i4z_bn5_d3b}

mid.discovery.aws_ssm.kms_key_name

:   Using a dedicated key enhances security by verifying that applicative credentials are encrypted and securely retrieved at runtime, without being exposed in plain text. This step is optional and only necessary if you
    plan to use applicative credentials during discovery. To configure the MID Server to support secure credential handling during SSM Agent discovery, set the mid.discovery.aws_ssm.kms_key_name
    property to the name of the AWS KMS key.

    * Type: string
    * Default value: none
    {#r_MIDServerProperties__ul_ukk_wqg_cgc}

mid.discovery.aws_ssm.kms_key_region

:   Using a dedicated key enhances security by verifying that applicative credentials are encrypted and securely retrieved at runtime, without being exposed in plain text. This step is optional and only necessary if you
    plan to use applicative credentials during discovery. To configure the MID Server to support secure credential handling during SSM Agent discovery, set the mid.discovery.aws_ssm.kms_key_region
    property to the region where the key is located.

    * Type: string
    * Default value: none
    {#r_MIDServerProperties__ul_qs3_frg_cgc}

mid.discovery.aws_ssm.s3_bucket_name

:   Because the SSM Run Command console has a 24,000-character limit, results that exceed this limit must be stored in and retrieved from an S3 bucket. For Put File commands, the S3 bucket also serves as a transfer point
    between the MID Server and the AWS environment, enabling file delivery to target devices via SSM. To configure the MID Server to support these S3-based operations, set the
    mid.discovery.aws_ssm.s3_bucket_name property to the name of the S3 bucket used for SSM Agent discovery.

    * Type: string
    * Default value: none
    {#r_MIDServerProperties__ul_aty_3rg_cgc}

mid.discovery.aws_ssm.s3_bucket_region

:   Because the SSM Run Command console has a 24,000-character limit, results that exceed this limit must be stored in and retrieved from an S3 bucket. For Put File commands, the S3 bucket also serves as a transfer point
    between the MID Server and the AWS environment, enabling file delivery to target devices via SSM. To configure the MID Server to support these S3-based operations, set the bucket's region in the
    mid.discovery.aws_ssm.s3_bucket_region property.

    * Type: string
    * Default value: none
    {#r_MIDServerProperties__ul_kzm_lrg_cgc}

mid.discovery.aws_ssm.linux.fallback_root_user

:   When the glide.discovery.enable_ssm property is enabled, AWS SSM Discovery on Linux defaults to using the root user for command execution. If you prefer not to configure alternate user credentials
    on your EC2 instances, you must enable the mid.discovery.aws_ssm.linux.fallback_root_user property to allow fallback to root execution. When enabled, it automatically creates a record in the AWS
    SSM Instance Users \[aws_ssm_instance_user_credentials\] table with the user name root. However, if you leave this property set to false, you must configure non-root credentials to run Discovery commands.

    * Type: true \| false
    * Default value: false
    {#r_MIDServerProperties__ul_ahz_4rg_cgc}

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

    {#r_MIDServerProperties__ul_mgd_jjv_tp}

    You can also configure this as a [configuration
    parameter on a individual MID Server](https://servicenow-prod.fluidtopics.net/VYH5xHLIPq1GhC9qbQDc9Q#t_SetMIDServerParameters "Use a MID Server parameter to control the behavior of a particular MID Server.").

mid.http_classy.allow_credentials_over_http
:   Enables the HTTP Classify probe to send credentials over the HTTP protocol during discovery.

    * Type: true \| false
    * Default value: false

    {#r_MIDServerProperties__ul_w4k_ndw_zfc}  
    Warnung:  
    Enabling this setting can expose credentials to security risks, such as man-in-the-middle (MitM) attacks. Therefore, it's strongly recommended to keep this property set to false and use HTTPS whenever possible.

mid.install_server.base_uri

:   Modifying this system property requires maint privileges. The MID Server uses the
    value provided as the base URL when making requests for update files.

    * Type: string
    * Default value: https://install.service-now.com
    {#r_MIDServerProperties__ul_a43_v3h_35b}

mid.jdbc.datastream.max.record.size
:   Specifies the maximum record size in KB.

    * Type: integer
    * Default value: 64
    * Maximum value: 128
    {#r_MIDServerProperties__ul_nm5_cqk_h4b}

mid.jdbc.datastream.fail.when.attachement.limit.exceeded
:   Specifies if the data up to 4GB (four attachments, each of size 1GB) can be retrieved
    from the RDBMS. By default, a flow or action fails with an error, when there is data of
    more than 4GB to be retrieved. Set value to <kbd class="ph userinput">false</kbd> to retrieve
    data of size 4GB without an error.

    * Type: string
    * Default: true
    {#r_MIDServerProperties__ul_m2t_drk_h4b}

mid.keystore.max_backups
:   Specifies the maximum number of backups from manual key store operations through the
    manage_certificate script. If it is 0 or negative, no backup
    will be made.

    * Type: Integer
    * Default value: 3
    {#r_MIDServerProperties__ul_jjf_s2n_25b}

mid.keystore.max_live_backups
:   Specifies the maximum number of live backups from running MID server. If it is 0 or
    negative, no backup will be made.

    * Type: Integer
    * Default value: 2
    {#r_MIDServerProperties__ul_kwn_v2n_25b}

mid.keystore.backup_overwrite_timespan
:   Specifies the number of seconds from the current backup time to determine if a the
    most recent backup in that time span should be replaced by the new one instead of
    creating a new backup and so removing the oldest backup, should the number of backups
    exceed the maximum limit.

    * Type: Integer
    * Default value: 60
    {#r_MIDServerProperties__ul_y21_y2n_25b}

mid.log.command_audit.enable
:   Enables the MID Server command audit log.

    * Type: string
    * Default value: false
    {#r_MIDServerProperties__ul_ivn_224_wnb}

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$\\temp
    {#r_MIDServerProperties__ul_rvf_sm2_d3b}

mid.probe.collect_debug_info

:   An optional property to collect debug information. If this property is set to
    true,
    the probe collects credential debug information when it runs and puts that information
    in the payload of ECC input message. It doesn't affect how Discovery works.

    * Type: true \| false
    * Default value: false
    {#r_MIDServerProperties__ul_rpk_rvz_qjb}

mid.probe.use_legacy_forward_dns
:   Enables the legacy DNSNameResolver probe and disables the default DNSNameResolver
    probe. See [Probes used by Orchestration](https://www.servicenow.com/docs/access?context=r_OrchestrationProbes&version=australia&pubname=australia-integrate-applications&ft:locale=en-US) for
    more information.

    * Type: true \| false
    * Default value: false
    {#r_MIDServerProperties__ul_ewm_qzm_phb}

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
    {#r_MIDServerProperties__ul_xgs_kwm_phb}

mid.process_flow.log_listener.max_size
:   Sets the maximum size in bytes of memory available to save log messages for Workflow Studio 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
    {#r_MIDServerProperties__ul_xjy_jq2_wdb}

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
    {#r_MIDServerProperties__ul_yyb_gsd_pw}

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
    {#r_MIDServerProperties__ul_jmg_gsd_pw}

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
    {#r_MIDServerProperties__ul_xz1_prd_pw}

mid.property.powershell.use_base64_password
:   If the Credential is set to be specific to certain MID Servers, then the property can also be set to those same MID Servers. Leaving the MID Servers field empty will apply to all MID Servers.

    * Type: true \| false
    * Default value: false
    {#r_MIDServerProperties__ul_w1w_mkv_zyb}

mid.sa.prefer_powershell
:   Enables MID Server to use PowerShell Remoting.  
    Hinweis:  
    It is not recommended to change this property as it is being deprecated.

    * Type: True \| False
    * Default value: true
    {#r_MIDServerProperties__ul_z35_q1r_rfb}

mid.sa.ssh.use_sncssh
:   Toggles SSH between non-interactive and interactive modes. True corresponds to
    non-interactive mode and allows probes to open sessions with the device without waiting
    for a prompt. False corresponds to interactive mode, which requires interactive sessions
    with the device for network devices and servers.

    * Type: True \| False
    * Default value: true
    {#r_MIDServerProperties__ul_ucp_zl4_kmb}

mid.sa.windows.allowable_failures

:   Specifies the number of allowable failures before the MID Server stops executing the pattern. Once the limit is reached, the next failure will terminate the pattern. A failure occurs when a PowerShell command can't complete successfully due to issues such
    as authentication failure, command timeout, or command execution exceptions.

    * Type: integer
    * Default value: 2
    * Values:
      * 0: The first failure will terminate the pattern immediately.
      * 1: The first failure is tolerated; the second failure will terminate the pattern.
      * 2: Two failures are tolerated; the third failure will terminate the pattern.
      * -1: no maximum limit on failures; the pattern continues regardless of the number of failures.
      {#r_MIDServerProperties__ul_k5s_3qw_2hc}
    {#r_MIDServerProperties__ul_fg2_cxs_hgc}

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
    {#r_MIDServerProperties__ul_fbs_bkg_gy}

mid.shazzam.regulator.interval_ms
:   Sets the interval, in milliseconds, in which Shazzam can launch packets.

    * Type: integer
    * Default value: 1
    {#r_MIDServerProperties__ul_tpp_nq2_d3b}

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
    {#r_MIDServerProperties__ul_ngp_pq2_d3b}

mid.shazzam.threads
:   Specifies the number of concurrent threads that Shazzam uses. Setting this or the
    mid.shazzam.max_scanners_per_thread parameter to 0 disables Shazzam multi-thread
    optimization.

    * Type: Integer
    * Default value: 5
    {#r_MIDServerProperties__ul_nxl_1sb_x3b}

mid.shazzam.max_scanners_per_thread
:   Specifies the number of concurrent scanners processed by each Shazzam thread. Setting
    this or the mid.shazzam.threads parameter to 0 disables Shazzam optimization.

    * Type: Integer
    * Default value: 100
    {#r_MIDServerProperties__ul_zl1_4sb_x3b}

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
    {#r_MIDServerProperties__ul_ovf_jt1_lhb}

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: 5000
    {#r_MIDServerProperties__ul_fsd_yt1_lhb}

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

    {#r_MIDServerProperties__ul_brm_ln3_chb}  
    GETBULK can also be set at the probe level or for an individual MID Server. Settings are listed in the order of precedence:

    * [SNMP probe
      parameter](https://www.servicenow.com/docs/access?context=r_SNMPProbeParameters&version=australia&pubname=australia-it-operations-management&ft:locale=en-US)
    * [MID Server
      configuration parameter](https://servicenow-prod.fluidtopics.net/VYH5xHLIPq1GhC9qbQDc9Q#mid-server-parameters "Parameters control the behavior of a particular MID Server and have lower precedence than MID Server properties.")
    * MID Server properties
    {#r_MIDServerProperties__ul_wy2_2n5_dhb}

mid.ssh.algorithms.kex
:   Modifies the Key Exchange SSH algorithm priority list. The property accepts a comma
    separated lists with operators. The first name in the list is highest priority, last
    name in list is lowest priority. Adding a comma separated list without any operators
    replaces the default algorithm list. For more information, see [MID Server SSH cryptographic algorithms](https://servicenow-prod.fluidtopics.net/6XDl6hCCpG2wR7zHUqkWng "The MID Server utilizes SSH clients to perform many discovery actions. During the SSH handshake, both the client and server first determine which algorithms both parties support, then client picks the highest priority algorithm. For the Host Key Algorithm, the client picks highest priority algorithm which both parties support that matches the key type.").

    * Type: string
    * Default value: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1,diffie-hellman-group-exchange-sha1
    {#r_MIDServerProperties__ul_sgg_lms_xnb}

mid.ssh.algorithms.host_key​
:   Modifies the Host Key SSH algorithm priority list. The properties accept comma
    separated lists with operators. The first name in the list is highest priority, last
    name in list is lowest priority. Adding a comma separated list without any operators
    replaces the default algorithm list. For more information, see [MID Server SSH cryptographic algorithms](https://servicenow-prod.fluidtopics.net/6XDl6hCCpG2wR7zHUqkWng "The MID Server utilizes SSH clients to perform many discovery actions. During the SSH handshake, both the client and server first determine which algorithms both parties support, then client picks the highest priority algorithm. For the Host Key Algorithm, the client picks highest priority algorithm which both parties support that matches the key type.").

    * Type: string
    * Default value: ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,rsa-sha2-256,rsa-sha2-512,ssh-rsa,ssh-dss
    {#r_MIDServerProperties__ul_qdp_pms_xnb}

mid.ssh.algorithms.cipher
:   Modifies the Cipher SSH algorithm priority list. The properties accept comma separated
    lists with operators. The first name in the list is highest priority, last name in list
    is lowest priority. Adding a comma separated list without any operators replaces the
    default algorithm list. For more information, see [MID Server SSH cryptographic algorithms](https://servicenow-prod.fluidtopics.net/6XDl6hCCpG2wR7zHUqkWng "The MID Server utilizes SSH clients to perform many discovery actions. During the SSH handshake, both the client and server first determine which algorithms both parties support, then client picks the highest priority algorithm. For the Host Key Algorithm, the client picks highest priority algorithm which both parties support that matches the key type.").

    * Type: string
    * Default value: aes128-ctr,aes192-ctr,aes256-ctr,3des-ctr,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc
    {#r_MIDServerProperties__ul_ehv_pms_xnb}

mid.ssh.algorithms.mac
:   Modifies the MAC SSH algorithm priority list. The properties accept comma separated
    lists with operators. The first name in the list is highest priority, last name in list
    is lowest priority. Adding a comma separated list without any operators replaces the
    default algorithm list. For more information, see [MID Server SSH cryptographic algorithms](https://servicenow-prod.fluidtopics.net/6XDl6hCCpG2wR7zHUqkWng "The MID Server utilizes SSH clients to perform many discovery actions. During the SSH handshake, both the client and server first determine which algorithms both parties support, then client picks the highest priority algorithm. For the Host Key Algorithm, the client picks highest priority algorithm which both parties support that matches the key type.").

    * Type: string
    * Default value: hmac-sha2-256,hmac-sha1,hmac-sha2-512,hmac-sha1-96,mac-md5-96,hmac-md5
    {#r_MIDServerProperties__ul_hw1_qms_xnb}

shazzam.chunk_size
:   Maximum number of IP addresses Shazzam can scan in parallel. This property primarily
    controls outbound port consumption.

    * Type: integer
    * Default value: 100
    {#r_MIDServerProperties__ul_dnf_kp2_d3b}

mid.use_net_tools
:   Enables or disables the use of net-tools commands during discovery of devices running
    on the Linux operating system. Starting from Quebec, ITOM Visibility supports the iproute2 commands for discovery. By default,
    ITOM Visibility and discovery patterns first use net-tools commands,
    and only then, as a fallback, may use iproute2 commands. If all Linux-based devices and
    applications in your IT network use iproute2 commands, disable net-tools commands to
    make the discovery process more efficient.

    * Type: true \| false
    * Default value: true
    {#r_MIDServerProperties__ul_p5r_dgx_jnb}

mid.servicewatch.use_full_linux_netstat_path
:   Controls if the netstat command is executed with its full
    installation path. This command lists open ports on Linux servers during
    the process detection phase of the top-down discovery.

    * Type: true \| false
    * Default value: true
    {#r_MIDServerProperties__ul_mk4_tnv_nnb}

mid.servicewatch.num_paths_linux_netstat_to_check
:   Define the maximum number of installation paths to use during discovery of Linux servers. This property is relevant when you run the top-down
    discovery on Linux servers with several netstat installation paths, and
    the mid.servicewatch.use_full_linux_netstat_path property is set to
    true.

    The top-down discovery attempts to execute the netstat
    command using each of these installation paths. The result of the first successful
    execution is used to determine the list of open ports.

    * Type: true \| integer
    * Default value: 5
    {#r_MIDServerProperties__ul_khv_s4v_nnb}

mid.servicewatch.use_full_linux_ss_path

:   Controls if the ss command is executed with its full
    installation path. This command lists open ports on Linux servers
    during the process detection phase of the top-down discovery.

    * Type: true \| false
    * Default value: false
    {#r_MIDServerProperties__ul_pzf_ypv_nnb}

mid.servicewatch.num_paths_linux_ss_to_check
:   Define the maximum number of installation paths to use during discovery of Linux servers. This property is relevant when you run the top-down
    discovery on Linux servers with several ss installation paths, and the
    mid.servicewatch.use_full_linux_netstat_path property is set to
    true.

    The top-down discovery attempts to execute the ss command
    using each of these installation paths. The result of the first successful execution
    is used to determine the list of open ports.

    * Type: true \| integer
    * Default value: 5
    {#r_MIDServerProperties__ul_p2m_wpv_nnb}
**Zugehörige Konzepte**   

* [MID Server upgrades](https://servicenow-prod.fluidtopics.net/FHThP3zPMJs8jJC1nxVqog "Upgrade MID Servers manually, or automatically through the instance. MID Server automatic upgrade is triggered when the instance upgrades and the MID Server no longer has the same version. The new MID Server package is downloaded from install.service-now.com, replaces the old one, and the MID Server starts with the new version.")
* [MID Server dashboard](https://servicenow-prod.fluidtopics.net/MYHGRvRY22woR5yJ4ojrAg "The MID Server dashboard is a central place for MID Server users to monitor ongoing operations. The dashboard consists of reports and gauges that display information from the MID Server Status table.")
* [MID Server File Cleaner](https://servicenow-prod.fluidtopics.net/GpXSjvTBt1RCnM1fQpg3Qw "A monitor thread runs in the MID Server to clean up old files, to keep the size and quantity of files within the install folder manageable, and to prevent performance issues with the MID Servers.")
* [MID Server privileged commands](https://servicenow-prod.fluidtopics.net/wiZ0usMr7e9KjcSsNjCZIQ#c_PrivilegedCommandsForMIDServer "To discover certain information on a host server, the MID Server must run SSH commands with higher privileges. The platform provides default privileged commands for the MID Server to use and the ability to add additional commands to the system.")  
**Zugehörige Tasks**   

* [Manually start, stop, and restart a MID Server](https://servicenow-prod.fluidtopics.net/xnuvo9vYRDPE6l8~h5dlUA "If you did not start the MID Server at the end of the installation procedure, you can manually start the MID Server.")
* [Set the MID Server JVM memory size](https://servicenow-prod.fluidtopics.net/rVu6TD9zQbdsIOlZ5i18YQ "The MID Server starts with a default JVM memory allocation, but you can modify this setting in the configuration file.")
* [Pause the MID Server](https://servicenow-prod.fluidtopics.net/gge75dsElgGaBRUdzpAzjg#t_PauseTheMIDServer "Pause the MID Server to temporarily prevent it from polling the ECC Queue for work or sending Discovery results back to the instance.")  
**Zugehörige Verweise**   

* [MID Server system requirements](https://servicenow-prod.fluidtopics.net/cz~U8SBK9UwjNYMyKIBxOA "Use these minimum system requirements to allocate resources for computers hosting MID Servers.")
* [Resolving MID Server issues](https://servicenow-prod.fluidtopics.net/Lfl8ACE3f39JVBKvcThM7Q "Troubleshoot problems with the MID Server to find solutions. Monitor the MID Server to receive alerts about issues as they occur. Troubleshooting procedures exist to resolve specific problems with the MID Server. The Knowledge Base on Hi contains several articles to help you troubleshoot MID Server issues.")
* [MID Server parameters](https://servicenow-prod.fluidtopics.net/VYH5xHLIPq1GhC9qbQDc9Q#mid-server-parameters "Parameters control the behavior of a particular MID Server and have lower precedence than MID Server properties.")
* [MID Server Configuration Parameter settings and priority](https://servicenow-prod.fluidtopics.net/PqP96ecRuYupotmsL6tyKQ "The MID Server's settings reside in multiple tables and the MID Server prioritizes them in a set order. MIDConfigParameter must be defined with the correct type-style builders.")
* [MID Server protected records and reserved characters](https://servicenow-prod.fluidtopics.net/9Qj46OIDTGN0kXwwYX6gxQ "Some MID Server records cannot be altered. Certain special characters are pre-defined in XML and cannot be used in passwords.")
* [MIDSystem methods](https://servicenow-prod.fluidtopics.net/mM3TQJTR~rr6IghVfilArg "MIDSystem variables (referred to by the variable name ms.) provide a variety of methods to get information about the MID Server.")
* [MID Server heartbeat](https://servicenow-prod.fluidtopics.net/iyiaCdK4VdUNvsARghYGaA "The instance checks the MID Server for a response every 5 minutes, using a synthetic transaction monitoring system.")

## Create a MID Server property {#ariaid-title2}

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

### Vorbereitungen

Role required: admin

### Warum und wann dieser Vorgang ausgeführt wird

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.

### Prozedur

1. Navigate to AllMID ServerProperties.
2. Click New.
3. Fill in the fields, as appropriate (see table).  
   {#t_SetMIDServerProperties__table_ngk_tld_xp__entry__2}

   | Field | Description |
   |-|-|
   | Name | Enter the property name. |
   | Value | You can enter the value you want the property to have. Hinweis: 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. |
   [Tabelle : 1. MID Server properties fields]

   {#t_SetMIDServerProperties__table_ngk_tld_xp}
4. After setting any MID Server properties, restart the MID Server to ensure the properties sync with the instance.