Configuration Changes Requiring Administrative Action

This page lists the set of configuration properties that require some form of administrative action for changes to take full effect.

Note that any changes to the java.properties file (which is used to specify the Java runtime and JVM options that should be used when running the Metrics Engine and associated tools) require that the dsjavaproperties tool be run to apply those changes. If the changes impact the Java runtime or JVM arguments used to run the Metrics Engine itself, then the server must be restarted.

Changelog Backend

• db-directory - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires that the Metrics Engine be stopped, the database directory manually relocated, and then the Metrics Engine restarted. While the Metrics Engine is stopped, the directory and files pertaining to this backend in the old database directory must be manually moved or copied to the new location.
• changelog-write-queue-capacity - The Changelog Backend must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• je-property - Changes to this configuration property will only take effect if the Metrics Engine is restarted.

LDIF Backend

• ldif-file - The LDIF Backend must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• is-private-backend - The LDIF Backend must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

JE Backend

• db-directory - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires that the Metrics Engine be stopped, the database directory manually relocated, and then the Metrics Engine restarted. While the Metrics Engine is stopped, the directory and files pertaining to this backend in the old database directory must be manually moved or copied to the new location.
• is-private-backend - The JE Backend must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• index-entry-limit - If any index keys have already reached this limit, indexes must be rebuilt before they will be allowed to use the new limit. Setting a large limit (greater than 10,000) could have a big impact on write performance and database growth on disk.
• exploded-index-entry-threshold - If any index keys have already reached this threshold, indexes need to be rebuilt before they are allowed to use the new threshold. Setting a large limit (greater than 10,000) could have a big impact on write performance and database growth on disk.
• id2children-index-entry-limit - If this limit is increased, then the contents of the backend must be exported to LDIF and re-imported to allow the new limit to be used for any id2children keys that had already hit the previous limit.
• id2subtree-index-entry-limit - If this limit is increased, then the contents of the backend must be exported to LDIF and re-imported to allow the new limit to be used for any id2subtree keys that had already hit the previous limit.
• db-evictor-lru-only - The JE Backend must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• db-evictor-nodes-per-scan - The JE Backend must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• db-evictor-critical-percentage - The JE Backend must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• db-log-file-max - The JE Backend must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• db-logging-file-handler-on - The JE Backend must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• db-logging-level - The JE Backend must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• db-checkpointer-wakeup-interval - The JE Backend must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• db-checkpointer-high-priority - The JE Backend must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• db-num-lock-tables - The JE Backend must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• db-clean-on-explicit-gc - The JE Backend must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• default-cache-mode - The JE Backend must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• id2entry-cache-mode - The JE Backend must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• dn2id-cache-mode - The JE Backend must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• id2children-cache-mode - The JE Backend must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• id2subtree-cache-mode - The JE Backend must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• dn2uri-cache-mode - The JE Backend must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Local DB Backend

• large-attribute-type - If the set of large attribute types is altered to add an attribute which is already in use in this backend, or to remove an attribute which already has large values in an alternate backend, then it may be necessary to re-import or manually perform some kind of administrative operation to ensure that the backend contents are updated properly.

Large Attribute Backend

• is-private-backend - The Large Attribute Backend must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• default-cache-mode - The Large Attribute Backend must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

JMX Connection Handler

• listen-port - The JMX Connection Handler must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• use-ssl - The JMX Connection Handler must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• ssl-cert-nickname - The JMX Connection Handler must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

LDAP Connection Handler

• listen-address - The LDAP Connection Handler must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• listen-port - The LDAP Connection Handler must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• use-ssl - The LDAP Connection Handler must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• ssl-cert-nickname - The LDAP Connection Handler must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• allow-tcp-reuse-address - The LDAP Connection Handler must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• max-cancel-handlers - The LDAP Connection Handler must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• num-request-handlers - The LDAP Connection Handler must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• request-handler-per-connection - The LDAP Connection Handler must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• ssl-client-auth-policy - The LDAP Connection Handler must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• accept-backlog - The LDAP Connection Handler must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

HTTP Connection Handler

• listen-address - The HTTP Connection Handler must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• listen-port - The HTTP Connection Handler must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• use-ssl - The HTTP Connection Handler must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• http-servlet-extension - The HTTP Connection Handler must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• web-application-extension - The HTTP Connection Handler must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• key-manager-provider - The HTTP Connection Handler must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• trust-manager-provider - The HTTP Connection Handler must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• num-request-handlers - The HTTP Connection Handler must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Crypto Manager

• ssl-cert-nickname - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Global Configuration

• location - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires a server restart
• allow-insecure-local-jmx-connections - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires a server restart

File Server HTTP Servlet Extension

• base-context-path - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

SCIM HTTP Servlet Extension

• base-context-path - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• debug-enabled - The Metrics Engine debug logger must be enabled and correctly configured for the debug messages to be forwarded.

LDAP SDK Debug Logger

• queue-size - The LDAP SDK Debug Logger must be restarted if this property is changed and the asynchronous property is set to true.

JDBC Based Access Log Publisher

• queue-size - The JDBC Based Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

Operation Timing Access Log Publisher

• log-file - The Operation Timing Access Log Publisher must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• queue-size - The Operation Timing Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

Scripted File Based Access Log Publisher

• log-file - The Scripted File Based Access Log Publisher must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• queue-size - The Scripted File Based Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

File Based Audit Log Publisher

• queue-size - The File Based Audit Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.
• log-file - The File Based Audit Log Publisher must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Writer Based Access Log Publisher

• queue-size - The Writer Based Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

Admin Alert Access Log Publisher

• queue-size - The Admin Alert Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

File Based Access Log Publisher

• log-file - The File Based Access Log Publisher must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Third Party File Based Access Log Publisher

• log-file - The Third Party File Based Access Log Publisher must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• queue-size - The Third Party File Based Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

Debug Access Log Publisher

• log-file - The Debug Access Log Publisher must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• queue-size - The Debug Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

File Based Error Log Publisher

• queue-size - The File Based Error Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.
• log-file - The File Based Error Log Publisher must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Third Party File Based Error Log Publisher

• log-file - The Third Party File Based Error Log Publisher must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• queue-size - The Third Party File Based Error Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

Scripted File Based Error Log Publisher

• log-file - The Scripted File Based Error Log Publisher must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• queue-size - The Scripted File Based Error Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

Syslog Based Error Log Publisher

• queue-size - The Syslog Based Error Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

JDBC Based Error Log Publisher

• queue-size - The JDBC Based Error Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

Detailed HTTP Operation Log Publisher

• log-file - The Detailed HTTP Operation Log Publisher must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• queue-size - The Detailed HTTP Operation Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

Common Log File HTTP Operation Log Publisher

• log-file - The Common Log File HTTP Operation Log Publisher must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• queue-size - The Common Log File HTTP Operation Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

File Based Debug Log Publisher

• queue-size - The File Based Debug Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.
• log-file - The File Based Debug Log Publisher must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

File Based Sync Log Publisher

• queue-size - The File Based Sync Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.
• log-file - The File Based Sync Log Publisher must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Sync Failed Ops Log Publisher

• queue-size - The Sync Failed Ops Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.
• log-file - The Sync Failed Ops Log Publisher must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Host System Monitor Provider

• enabled - Enabling host system cpu, memory, disk and network interface I/O monitoring requires running an external collector helper process except on Linux systems. Host system monitoring is not available on Windows systems. Enabling the host system monitor provider requires restarting the server except on Linux systems.

Monitoring Configuration

• second-resolution-sample-retention-duration - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires a server restart
• minute-resolution-sample-retention-duration - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires a server restart
• hour-resolution-sample-retention-duration - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires a server restart
• day-resolution-sample-retention-duration - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires a server restart
• num-concurrent-polling-threads - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires a server restart
• sample-cache-idle-series-timeout - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires a server restart
• sample-cache-max-cached-series - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires a server restart
• sample-cache-track-statistics - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires a server restart

Monitoring Database

• database-name - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires a server restart

Derby Monitoring Database

• derby-home - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires a server restart

Postgres Monitoring Database

• server-host-name - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires a server restart
• server-port - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires a server restart
• user-name - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires a server restart
• password - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires a server restart
• max-db-connections - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires a server restart

Password Policy

• idle-lockout-interval - Last login time tracking is required for idle account lockout to work properly. If you are enabling idle account lockout, then you should ensure that the last-login-time-attribute and last-login-time-format properties are also defined and that last login time tracking has been enabled long enough so that user accounts have had time to be marked with last login times. Ideally, last login time tracking should be enabled for at least as long as the idle lockout interval to ensure that users are not incorrectly locked out merely because their accounts do not have last login time information.

Plugin

• plugin-type - The Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Seven Bit Clean Plugin

• plugin-type - The Seven Bit Clean Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Entry UUID Plugin

• plugin-type - The Entry UUID Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Referral On Update Plugin

• plugin-type - The Referral On Update Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Delay Plugin

• plugin-type - The Delay Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Periodic GC Plugin

• plugin-type - The Periodic GC Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

DN Mapper Plugin

• plugin-type - The DN Mapper Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Attribute Mapper Plugin

• plugin-type - The Attribute Mapper Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

SNMP Subagent Plugin

• agentx-address - The SNMP Subagent Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• agentx-port - The SNMP Subagent Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• num-worker-threads - The SNMP Subagent Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Referential Integrity Plugin

• plugin-type - The Referential Integrity Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Change Subscription Notification Plugin

• plugin-type - The Change Subscription Notification Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Unique Attribute Plugin

• plugin-type - The Unique Attribute Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Changelog Password Encryption Plugin

• plugin-type - The Changelog Password Encryption Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Internal Search Rate Plugin

• plugin-type - The Internal Search Rate Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Periodic Stats Logger Plugin

• log-file - The Periodic Stats Logger Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Processing Time Histogram Plugin

• plugin-type - The Processing Time Histogram Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• histogram-category-boundary - The Processing Time Histogram Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. The Metrics Engine can only aggregate response-time data when the boundary values are the same across both time and monitored servers. If you change the boundary values on one monitored server, you should change them on all monitored servers.
• separate-monitor-entry-per-tracked-application - When setting this option to true, you must also set the per-application-ldap-stats property in the Stats Collector Plugin to per-application-only.

SNMP Master Agent Plugin

• listen-address - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• listen-port - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• agentx-listen-address - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• agentx-listen-port - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• notification-target-address - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• notification-target-port - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• agent-snmp-version - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• community-name - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• agent-security-name - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• agent-security-level - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• num-worker-threads - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Pass Through Authentication Plugin

• plugin-type - The Pass Through Authentication Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Last Mod Plugin

• plugin-type - The Last Mod Plugin must be disabled and re-enabled (or the Metrics Engine restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Web Application Extension

• base-context-path - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

UnboundID Work Queue

• num-worker-threads - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires a server restart
• num-write-worker-threads - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires a server restart
• num-administrative-session-worker-threads - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires a server restart
• num-queues - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires a server restart
• num-write-queues - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires a server restart
• max-work-queue-capacity - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires a server restart
• queue-type - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires a server restart

Wait Notify Work Queue

• num-worker-threads - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires a server restart

Traditional Work Queue

• max-work-queue-capacity - The Metrics Engine must be restarted for changes to this configuration property to take full effect. Modification requires a server restart