Contents Now Platform Capabilities Previous Topic Next Topic MID Server properties Subscribe Log in to subscribe to topics and get notified when content changes. ... SAVE AS PDF Selected Topic Topic & Subtopics All Topics in Contents Share MID Server properties Properties control the behavior of all MID Servers or a particular MID Server. 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 Name Description 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. In Madrid Patch 2, or earlier, the default value is 20000. The default was increased in Madrid Patch 3 and subsequent releases. Type: integer Default value: 200000 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.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 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 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.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 after you change the value of this property. 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.sa.prefer_powershell Enables MID Server to use PowerShell Remoting. Type: True | False Default value: false 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. (This is available in version Madrid patch 2 and later.) 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: SNMP probe parameter MID Server configuration parameter MID Server properties 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 beginRole required: admin About this taskYou 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 Navigate to MID Server > Properties. Click New. 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. After setting any MID Server properties, restart the MID Server to ensure the properties sync with the instance. On this page Send Feedback Previous Topic Next Topic
MID Server properties Properties control the behavior of all MID Servers or a particular MID Server. 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 Name Description 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. In Madrid Patch 2, or earlier, the default value is 20000. The default was increased in Madrid Patch 3 and subsequent releases. Type: integer Default value: 200000 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.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 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 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.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 after you change the value of this property. 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.sa.prefer_powershell Enables MID Server to use PowerShell Remoting. Type: True | False Default value: false 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. (This is available in version Madrid patch 2 and later.) 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: SNMP probe parameter MID Server configuration parameter MID Server properties 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 beginRole required: admin About this taskYou 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 Navigate to MID Server > Properties. Click New. 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. After setting any MID Server properties, restart the MID Server to ensure the properties sync with the instance.
MID Server properties Properties control the behavior of all MID Servers or a particular MID Server. 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 Name Description 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. In Madrid Patch 2, or earlier, the default value is 20000. The default was increased in Madrid Patch 3 and subsequent releases. Type: integer Default value: 200000 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.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 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 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.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 after you change the value of this property. 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.sa.prefer_powershell Enables MID Server to use PowerShell Remoting. Type: True | False Default value: false 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. (This is available in version Madrid patch 2 and later.) 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: SNMP probe parameter MID Server configuration parameter MID Server properties 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 beginRole required: admin About this taskYou 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 Navigate to MID Server > Properties. Click New. 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. After setting any MID Server properties, restart the MID Server to ensure the properties sync with the instance.
MID Server properties Properties control the behavior of all MID Servers or a particular MID Server. 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 Name Description 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. In Madrid Patch 2, or earlier, the default value is 20000. The default was increased in Madrid Patch 3 and subsequent releases. Type: integer Default value: 200000 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.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 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 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.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 after you change the value of this property. 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.sa.prefer_powershell Enables MID Server to use PowerShell Remoting. Type: True | False Default value: false 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. (This is available in version Madrid patch 2 and later.) 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: SNMP probe parameter MID Server configuration parameter MID Server properties 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 beginRole required: admin About this taskYou 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 Navigate to MID Server > Properties. Click New. 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. After setting any MID Server properties, restart the MID Server to ensure the properties sync with the instance.
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 beginRole required: admin About this taskYou 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 Navigate to MID Server > Properties. Click New. 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. After setting any MID Server properties, restart the MID Server to ensure the properties sync with the instance.
