MID Server connection parameters

These parameters control the MID Server connection to the instance.

Table 1. MID Server connection parameters
Label Names Description
Instance date format instance.date.format Specifies the format the instance uses for dates and times. The primary impact of setting this parameter is to allow the MID Server to correctly refresh its start and stop times on the MID Server record in ServiceNow. The format of this date/time string is identical to that used by the Java SimpleDateFormat class.
  • Type: string (Date format)
  • Default value: yyyy-MM-dd HH:mm:ss
MID Server immediate response enable glide.mid.fast.responses Instructs the MID Server to try sending messages to the instance as soon as they are ready. Normally the MID Servers ends message to the ServiceNow instance serially (that is, one message at a time). Since many probes can be run in parallel, there can be multiple messages 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, decreasing the overall instance responsiveness. If there are communications problems, this parameter's value can also cause a logjam on the MID Server, as threads normally used for running probes may become consumed for sending messages. Generally, leave this parameter out of your configuration. Setting it to true is meaningful only under very special circumstances.
  • Type: true | false
  • Default value: false
MID Server JMX enable mid.jmx.enabled Enables a JMX server on the MID Server , which exposes some management information to JMX consoles. Implementing JMX requires additional configuration of the Java runtime environment. Setting this parameter to true is only recommended for those with detailed knowledge of the Java security architecture and a specific need for JMX.
  • Type: true | false
  • Default value: false
MID Server max transmission queue size glide.mid.max.sender.queue.size Places an upper limit on how large the queue is allowed to get. The MID Server starts deleting queued messages if this limit is exceeded. 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 processing slows for a short period. However, this queue can grow in size when there are communication problems between the MID Server and the instance, and especially if there is an integration running on the MID Server , .
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. White space is liberally tolerated. The following strings all represent valid parameters: "1000000000", "0.5m", "5 GB", "7.67gigas", "145.69392 meg", and "1.1 terra".
  • Type: string
  • Default value: 0.5 GB
MID Server maximum number of probe threads threads.max Controls the number of execution threads (simultaneous work) that probes may use. This parameter provides direct control over what CPU resources the MID Server consumes on the computer that hosts it. To decrease the MID Server 's CPU consumption, lower the number of threads. To make the MID Server work faster, increase the number of threads. See Set MID Server Thread Use.
  • Type: integer (threads)
  • Default value: 25
Maximum amount of interactive messages to queue in memory for processing. threads.interactive.max Sets the maximum amount of interactive messages to queue in memory for processing.
  • Type: integer (threads)
  • Default value: 4
Maximum amount of expedited messages to queue in memory for processing. threads.expedited.max Sets the maximum amount of expedited messages to queue in memory for processing.
  • Type: integer (threads)
  • Default value: 4 (threads)
MID Server poll time mid.poll.time Sets the default MID Server polling interval (in seconds). This is the interval the MID Server waits before polling the ECC queue when the ECC queue is not busy. In addition to reacting to AMB messages, the system also polls the ECC queue at a regular interval in case the AMB connection is dropped.
  • Type: integer (seconds)
  • Default value: 40