MID Server properties

Use properties to control the behavior of probes and payloads on MID Servers.

The MID Server properties are in the MID Server Property [ecc_agent_property] table and can be accessed by navigating to MID Server > Properties. You must add these properties if they are not already present.
Table 1. MID Server properties
Name Description
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.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.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.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 parameter 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.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 . This property requires the Orchestration plugin.
  • Type: string
  • Default value: connectionFactory, queueConnectionFactory, topicConnectionFactory
mid.property.powershell.command.script.parameter_passing
  • Type: true | false
  • Default value: false
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.
Important: If you upgrade from Dublin or earlier and want to use the SNCSSH client, you must add this property to the MID Server Properties [ecc_agent_property] table and set it to true. If you do not set this property, all the MID Servers in the upgraded system will use J2SSH.
  • 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
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 if after you change the value of this property.
  • Type: true | false
  • Default value: false