C ONCLUSIONES

Note: Changes to parameters only take effect when the MID server is started (or restarted).

Description Name(s) Details

debug.logging Optional, true/false, default false. If set to true, enables logging of MID server events and messages (both sent and received). Normally this parameter is only used by developers, but it is occasionally useful when troubleshooting a problem. Be aware that setting this parameter to true will cause intensive logging on the MID server, potentially using considerable disk space.

Debug logging level

debug.level Optional, integer (0-3), default 0. Controls how much debug logging will take place (if debug mode is enabled): 0 = none, 1 = little, 2 = some, and 3 = all.

Debug mode enable

debug Optional, true/false, default false. If true, enables debug logging on the MID server.

Normally this parameter is only used by developers, but it is occasionally useful when troubleshooting a problem. Be aware that setting this parameter to true will cause intensive logging on the MID server, potentially using considerable disk space.

Disable monitor checking

disable_monitors Optional, true/false, default false. It true, disables MID Server from actively checking for monitors on the instance.

Enable

mid.snmp.enable_auto_public Optional, true/false, default true. To disable the SNMP public community string, set this parameter to false.

Enable PowerShell for Discovery

mid.use_powershell Optional, true/false, default false. PowerShell must be installed on the MID Server and must be at Version 2 for PowerShell with Discovery to operate. If the correct version of PowerShell cannot be found, the MID Server uses WMIRunner instead.

Environment variable for SSH commands

mid.ssh.set_path Optional, true/false, default true. Sets the PATH environment variable for SSH commands.

mid.ssh.local Optional, true/false, default false. If set to true, executes commands for the MID Server host machine (localhost) via SSH rather than from a console. This allows long-running commands to execute properly.

Fixed MID Server version

mid.pinned.version Optional, string build timestamp. Names the fixed version for the MID Server.

Instance date format

instance.date.format Optional, string date/time pattern, default "yyyy-MM-dd HH:mm:ss". Set or change this parameter to let the MID server know what format the instance uses for date/times. The primary impact of setting this parameter is to allow the MID server to correctly refresh its start and stop times on the ServiceNow instance's MID server record. The format of this date/time string is identical to that used by the Java SimpleDateFormat class, documented here [1] in the section titled Date and Time Patterns.

Instance password

mid.instance.password or glide.glidesoap.password

Optional, string. If your ServiceNow instance has authentication enabled (the normal case), set this parameter to define the password the MID server should use to log into the instance.

Instance proxy enable

mid.instance.use_proxy or mid.proxy.use_proxy

Optional, true/false, default false. If your MID server must go through a web proxy to access the ServiceNow instance, set this parameter to true to instruct the MID server to use the proxy. Note that you must also set the proxy server's host and port, and perhaps the user name and password as well.

Instance proxy host

mid.proxy.host Optional, string. If your MID server must go through a web proxy to access the ServiceNow instance, set this parameter to define the proxy's host.

Instance proxy password

mid.proxy.password Optional, string. If your MID server must go through a web proxy to access the ServiceNow instance, and your proxy requires a password, set this parameter to define that password.

Instance proxy port

mid.proxy.port Optional, integer (0 - 65535). If your MID server must go through a web proxy to access the ServiceNow instance, set this parameter to define the proxy's port.

Instance proxy user name

mid.proxy.username Optional, string. If the MID Server must go through a web proxy to access the ServiceNow instance, and the proxy requires a user name, set this parameter to define that user name.

Instance URL url Required, string. Tells the MID server where to contact its associated ServiceNow instance. Normally this would be a URL like [2], where “example” would be replaced by the name of your instance. If your are hosting your own ServiceNow instance, then this URL will be determined by your organization.

Instance user name

mid.instance.username or glide.glidesoap.username

Optional, string. If your ServiceNow instance has authentication enabled (the normal case), set this parameter to define the user name the MID server should use to log into the instance.

MID Server auto-upgrade enable

auto_upgrade Optional, true/false, default true. If true or absent, enables the MID server to periodically check whether it should upgrade. If it is set to false, the MID server will remain on the same version – generally neither safe or useful.

MID Server connection cache

mid.connection_cache Optional, true/false, default true. By default this property causes connections to be cached. Set to false to disable connection caching. Used for ssh connections only (Discovery).

MID Server ECC query interval

query_backoff Optional, true/false, default false. Allows the interval at which the MID Server queries the ECC Queue to lengthen if the MID Server is idle. By default, the MID Server queries the ECC Queue for work every 15 seconds. In a system that employs a large number of MID Servers, these queries can produce unnecessary traffic during periods of light MID Server activity. When the query_backoff parameter is set to true, the query interval slowly lengthens for an idle MID Server. Eventually, the interval slows to one query every four minutes and holds at that rate until the MID Server has a job to do. When the MID Server starts work again, the query interval for that MID Server immediately increases to once every 15 seconds and continues at that rate until the demand on the MID Server backs off again.

MID Server ID

mid_sys_id Required, automatically set, string (GUID). Records the unique identifier of the MID server's record on the ServiceNow instance. This parameter should be empty when you initially configure a MID server, and you should never change it.

MID Server immediate response enable

glide.mid.fast.responses Optional, true/false, default false. Normally the MID server sends message to the ServiceNow instance serially (that is, one message at a time). Setting this parameter to true instructs the MID server to try sending messages to the instance as soon as they are ready. In Discovery, when many probes can be run in parallel, this means that often there will be multiple messages being simultaneously transmitted to the instance. Setting this parameter to true may decrease the time between a probe's completion and its response arriving at the instance. However, the multiple simultaneous messages consume resources on the instance, decreasing the instance's overall responsiveness. If there are communications problems, this parameter can also cause a "logjam" on the MID server, as threads normally used for running probes may become consumed for sending messages. Overall we recommend leaving this parameter out of your configuration; it would take a very special circumstance for it to make sense to set it true.

MID Server JMX enable

mid.jmx.enabled Optional, true/false, default false. If set to true, this parameter enables a JMX server on the MID server, exposing some management information to JMX consoles. This is an experimental feature, not officially released yet. Also, implementing JMX requires additional (and fairly complicated) configuration of the Java runtime environment.

Setting this parameter to true is only recommended for those with detailed knowledge of the Java security architecture, a specific need for JMX, and a strong desire to take unreasonable risks with production software.

MID Server max transmission queue size

glide.mid.max.sender.queue.size Optional, string, default "0.5g". When the MID server generates messages to the ServiceNow instance faster than it can send them, it queues them temporarily on the file system of the MID server's host. This queue is normally quite small, and is completely emptied as soon as the MID server is quiescent for a short period.

However, when there are communications problems between the MID server and the instance, and especially if there is an integration running on the MID server, this queue can grow in size. This parameter places an upper bound on how large the queue is allowed to get – the MID server will start deleting queued messages if this bound would be exceeded. The parameter is of the form {number}[{multiplier}], where {number} is any positive decimal number (including non-integers), and the optional multiplier is any spelling of "bytes", "kilobytes", "megabytes", "gigabytes", or "terabytes" (only the first character is tested, and the test is case-insensitive). The default multiplier is "bytes". Whitespace is liberally tolerated. The following strings all represent valid parameters: "1000000000", "0.5m", "5 GB", "7.67gigas",

"145.69392 mothers", and "1.1 tomatoes".

MID Server maximum number of probe threads

threads.max Optional, integer, default 25. Controls the number of execution threads (simultaneous work) that may be used by probes. This parameter provides direct control over how much CPU resource the MID server will consume on the computer that hosts it. To throttle the MID server's CPU consumption down, lower the number of threads. To make the MID server work faster, increase the number of threads.

MID Server name

name Required, string, default is YOUR_MIDSERVER_NAME_GOES_HERE If you

do not supply this parameter, the MID server will use the default value. Use this parameter to supply a name that's meaningful for you.

MID Server poll time

mid.poll.time Optional, integer, default 15. Allows you to override the default MID Server polling interval (in seconds).

MID Server refresh rate

MIDServerRefreshRate Optional, integer, default 65. Controls how often (in seconds) the MID server checks with the instance to determine if the MID Server should upgrade itself. The usual value for this parameter is 65 seconds. To change this value, add the parameter to the MID Server config.xml file, using the following syntax:

<parameter name="MIDServerRefreshRate" value="<N>"/>

MID Server SSH connection per host

mid.ssh_connections_per_host Optional, integer, default 3. Controls the number of concurrent probes the MID Server can run against a given host. Lowering the number of concurrent connections can slow Discovery.

MSSQL credentials for PowerShell

mid.powershell.use_mssqlauth Optional, true/false, default false. This parameter determines whether PowerShell should use Windows integrated security or SQL authentication when attempting to log into the MSSQL instance. PowerShell uses Windows integrated security by default.

Port probe packet interval

mid.shazzam.regulator.interval_ms Optional, integer, default 1. Sets the interval, in milliseconds, in which Shazzam can launch packets. This parameter works with the

mid.shazzam.regulator.packets_per_interval parameter to set the number of packets allowed in this interval. By default, Shazzam launches one packet each millisecond.

mid.shazzam.regulator.packets_per_interval Optional, integer, default 1. Sets the number of packets that Shazzam can launch in the configured time interval. This parameter works with the

mid.shazzam.regulator.interval_ms parameter, which sets that interval. By default, Shazzam launches one packet each millisecond.

PowerShell credentials

mid.powershell.use_credentials Optional, true/false, default true. This parameter tells Discovery to use the Windows credentials in the credentials table for PowerShell. To use PowerShell Discovery on a single domain, set this parameter to false, and then restart the MID Server. In this case, the MID Server runs the probes with the credentials of the user for the MID Server process.

PowerShell executable path

mid.powershell.path Optional, string URL. This parameter enables an administrator to point to a specific PowerShell on a MID Server in cases where more than one PowerShell is installed.

Supply the path (e.g. C:\mypowershell or C:\mypowershell\) to the folder containing the PowerShell executable, and powershell.exe is appended automatically to the URL. This parameter might be necessary, for example, when 32 bit and 64 bit PowerShells are active on the same MID Server, and it becomes necessary to launch the correct PowerShell for the context. Note that 64-bit Windows employs file system redirection and the MID server runs as a 32-bit application. If trying to specify a path in %WinDir%\System32, Windows will automatically redirect to

%WinDir%\SysWOW64. To avoid redirection, specify the path as

%WinDir%\Sysnative. An example would be instead of

"C:\WINDOWS\system32\WindowsPowerShell\v1.0\", specify

"C:\WINDOWS\sysnative\WindowsPowerShell\v1.0\".

Query logging enable

mid.show.queries Optional, true/false, default false. Setting this parameter to true instructs the MID server to log details about every query it makes to the ServiceNow instance.

Normally this parameter is only used by developers, but it is occasionally useful when troubleshooting a problem. Be aware that setting this parameter to true will cause intensive logging on the MID server, potentially using considerable disk space.

Remote logging disable

disable.remote.logging Optional, true/false, default false. If this parameter is set to true, the MID server will not log any information to the MID server log on the ServiceNow instance.

Relatively little information is logged on the instance in any case, but setting this parameter will cut that to zero.

Set the PATH environment paths for SSH commands

mid.ssh.path_override Optional, string. Configure an alternate SSH command path with this parameter to override the possible default paths (/usr/sbin: /usr/bin: /bin: /sbin). This MID Server parameter is overridden if an alternate SSH command path is configured in a probe parameter.

Shazzam chunk size

mid.shazzam.chunk_size Optional, integer, default 100. The maximum number of IP addresses that Shazzam scans in parallel. This parameter primarily controls outbound port consumption.

SSH connection error retry

mid.ssh_max_retries Optional, integer, default 1. The maximum amount of times to retry an SSH operation after a time-out. The system sleeps two seconds between each connection attempt. By default, the MID Server retries once only. Use the mid.ssh.max_retries parameter setting to override that default. Set the parameter to 0 to disable retries.

SSH remove command override

mid.ssh.alt_rm Optional, string, default /bin/rm -f. Sets a different SSH remove file command.

Status sending disable

disable.status Optional, true/false, default false. Normally the MID server sends a status report to the ServiceNow instance every 10 minutes. Setting this parameter to true will eliminate that report.

Suppress history file generation for SSH

mid.ssh.suppress_history Optional, true/false, default false. Suppress generation of the SSH history file.

Timeout in ms for SSH socket open

mid.ssh.socket_timeout Optional, integer, default 60,000. Some devices (such as systems with embedded controllers, like UPSs and PDUs) with SSH enabled require more than 30 seconds to respond to an authentication request. To prevent issues created by a socket timeout, this parameter provides a way to set a higher value.

Upgrade branch

glide.mid.autoupgrade.branch or mid.upgrade.branch

Optional, string. Defines a branch (a directory on the distribution server) from which the MID server should download its upgrades from. This might be set if you had a special MID server version for some reason. Normally you should not have this parameter in your configuration, and you should never include it without consulting with ServiceNow.

Upgrade proxy enable

mid.upgrade.use_proxy Optional, true/false, default false. If your MID server must go through a web proxy to access the upgrade URL, set this parameter to true to instruct the MID server to use the proxy. Note that you must also set the proxy server's host and port. Note that if the instance proxy user name and password are set, they will be used for the upgrade proxy as well.

Upgrade proxy host

glide.mid.autoupgrade.proxy_host or glide.glidesoap.proxy_host

Optional, string. If your MID server must go through a web proxy to access the upgrade URL, define the proxy's host here.

Upgrade proxy port

glide.mid.autoupgrade.proxy_port or glide.glidesoap.proxy_port

Optional, integer (0 - 65535). If your MID server must go through a web proxy to access the upgrade URL, define the proxy's port here.

Upgrade proxy user

glide.mid.autoupgrade.proxy_user Optional, string. If your MID server must go through a web proxy to access the upgrade URL, define the proxy's user name here.

Upgrade proxy password

glide.mid.autoupgrade.proxy_password Optional, string. If your MID server must go through a web proxy to access the upgrade URL, define the proxy's password here.

Upgrade URL glide.mid.autoupgrade.host Optional, string URL, default. [3] Controls where the MID server will download its upgrades from. Normally you should not set this parameter.

Use keyboard interactive authentication for SSH

mid.ssh.use_keyboard_interactive Optional, true/false, default false. Uses the keyboard interactive authentication mode in SSH daemons for MID Servers on which it is activated.