dsconfig get-service-discovery-mechanism-prop — Shows Service Discovery Mechanism properties
dsconfig get-service-discovery-mechanism-prop
{options}
The dsconfig get-service-discovery-mechanism-prop command takes the following options:
--mechanism-name {name}
The name of the Service Discovery Mechanism.
Service Discovery Mechanism properties depend on the Service Discovery Mechanism type, which depends on the {name} you provide.
By default, OpenDJ directory server supports the following Service Discovery Mechanism types:
Default {name}: Replication Service Discovery Mechanism
Enabled by default: false
See the section called “Replication Service Discovery Mechanism” for the properties of this Service Discovery Mechanism type.
Default {name}: Static Service Discovery Mechanism
Enabled by default: false
See the section called “Static Service Discovery Mechanism” for the properties of this Service Discovery Mechanism type.
--property {property}
The name of a property to be displayed.
Service Discovery Mechanism properties depend on the Service Discovery Mechanism type, which depends on the {property} you provide.
By default, OpenDJ directory server supports the following Service Discovery Mechanism types:
Default {property}: Replication Service Discovery Mechanism
Enabled by default: false
See the section called “Replication Service Discovery Mechanism” for the properties of this Service Discovery Mechanism type.
Default {property}: Static Service Discovery Mechanism
Enabled by default: false
See the section called “Static Service Discovery Mechanism” for the properties of this Service Discovery Mechanism type.
-E | --record
Modifies the display output to show one property value per line.
Service Discovery Mechanism properties depend on the Service Discovery Mechanism type, which depends on the null you provide.
By default, OpenDJ directory server supports the following Service Discovery Mechanism types:
Default null: Replication Service Discovery Mechanism
Enabled by default: false
See the section called “Replication Service Discovery Mechanism” for the properties of this Service Discovery Mechanism type.
Default null: Static Service Discovery Mechanism
Enabled by default: false
See the section called “Static Service Discovery Mechanism” for the properties of this Service Discovery Mechanism type.
-z | --unit-size {unit}
Display size data using the specified unit. The value for UNIT can be one of b, kb, mb, gb, or tb (bytes, kilobytes, megabytes, gigabytes, or terabytes).
Service Discovery Mechanism properties depend on the Service Discovery Mechanism type, which depends on the {unit} you provide.
By default, OpenDJ directory server supports the following Service Discovery Mechanism types:
Default {unit}: Replication Service Discovery Mechanism
Enabled by default: false
See the section called “Replication Service Discovery Mechanism” for the properties of this Service Discovery Mechanism type.
Default {unit}: Static Service Discovery Mechanism
Enabled by default: false
See the section called “Static Service Discovery Mechanism” for the properties of this Service Discovery Mechanism type.
-m | --unit-time {unit}
Display time data using the specified unit. The value for UNIT can be one of ms, s, m, h, d, or w (milliseconds, seconds, minutes, hours, days, or weeks).
Service Discovery Mechanism properties depend on the Service Discovery Mechanism type, which depends on the {unit} you provide.
By default, OpenDJ directory server supports the following Service Discovery Mechanism types:
Default {unit}: Replication Service Discovery Mechanism
Enabled by default: false
See the section called “Replication Service Discovery Mechanism” for the properties of this Service Discovery Mechanism type.
Default {unit}: Static Service Discovery Mechanism
Enabled by default: false
See the section called “Static Service Discovery Mechanism” for the properties of this Service Discovery Mechanism type.
Service Discovery Mechanisms of type replication-service-discovery-mechanism have the following properties:
The bind DN for periodically reading replication server configurations The bind DN must be present on all replication servers and directory servers, it must be able to read the server configuration.
None
A valid DN.
No
Yes
None
No
No
The bind password for periodically reading replication server configurations The bind password must be the same on all replication and directory servers
None
A String
No
Yes
None
No
No
Interval between two replication server configuration discovery queries. Specifies how frequently to query a replication server configuration in order to discover information about available directory server replicas.
60s
Some property values take a time duration.
Durations are expressed as numbers followed by units.
For example 1 s
means one second,
and 2 w
means two weeks.
Some durations have minimum granularity or maximum units,
so you cannot necessary specify every duration
in milliseconds or weeks for example.
Some durations allow you to use a special value to mean unlimited.
Units are specified as follows.
ms
: milliseconds
s
: seconds
m
: minutes
h
: hours
d
: days
w
: weeks
Lower limit is 1 seconds.
No
No
None
No
No
Specifies the fully-qualified name of the Java class that provides the Replication Service Discovery Mechanism implementation.
org.opends.server.backends.proxy.ReplicationServiceDiscoveryMechanism
A Java class that implements or extends the class(es): org.opends.server.backends.proxy.ServiceDiscoveryMechanism
No
Yes
The Service Discovery Mechanism must be disabled and re-enabled for changes to this setting to take effect
Yes (Use --advanced in interactive mode.)
No
Specifies the name of the key manager that should be used with this Service Discovery Mechanism.
None
The DN of any Key Manager Provider. The referenced key manager provider must be enabled when the Service Discovery Mechanism is enabled and configured to use SSL or StartTLS.
No
No
None
Changes to this property take effect immediately, but only for subsequent attempts to access the key manager provider for associated client connections.
No
No
Replication domain group ID of preferred directory server replicas. Directory server replicas with this replication domain group ID will be preferred over other directory server replicas. Secondary server replicas will only be used when all primary server replicas become unavailable.
All the server replicas will be treated the same.
An integer value. Lower value is 0.
No
No
None
No
No
Specifies the list of replication servers to contact periodically when discovering server replicas.
None
A host name followed by a ":" and a port number.
Yes
Yes
None
No
No
Specifies the nicknames (also called the aliases) of the keys or key pairs that the Service Discovery Mechanism should use when performing SSL communication. The property can be used multiple times (referencing different nicknames) when server certificates with different public key algorithms are used in parallel (for example, RSA, DSA, and ECC-based algorithms). When a nickname refers to an asymmetric (public/private) key pair, the nickname for the public key certificate and associated private key entry must match exactly. A single nickname is used to retrieve both the public key and the private key. This is only applicable when the Service Discovery Mechanism is configured to use SSL.
Let the server decide.
A String
Yes
No
The Service Discovery Mechanism must be disabled and re-enabled for changes to this setting to take effect
No
No
Specifies the name of the trust manager that should be used with the Service Discovery Mechanism.
Use the trust manager provided by the JVM.
The DN of any Trust Manager Provider. The referenced trust manager provider must be enabled when the Service Discovery Mechanism is enabled and configured to use SSL or StartTLS.
No
No
None
Changes to this property take effect immediately, but only for subsequent attempts to access the trust manager provider for associated client connections.
No
No
Indicates whether the Service Discovery Mechanism should use SSL. If enabled, the Service Discovery Mechanism will use SSL to encrypt communication with the clients.
false
true
false
No
No
The Service Discovery Mechanism must be disabled and re-enabled for changes to this setting to take effect
No
No
Indicates whether the Service Discovery Mechanism should use Start TLS. If enabled, the Service Discovery Mechanism will use Start TLS to encrypt communication with remote servers.
false
true
false
No
No
The Service Discovery Mechanism must be disabled and re-enabled for changes to this setting to take effect
No
No
Service Discovery Mechanisms of type static-service-discovery-mechanism have the following properties:
Interval between two server configuration discovery executions. Specifies how frequently to read the configuration of the servers in order to discover their new information.
60s
Some property values take a time duration.
Durations are expressed as numbers followed by units.
For example 1 s
means one second,
and 2 w
means two weeks.
Some durations have minimum granularity or maximum units,
so you cannot necessary specify every duration
in milliseconds or weeks for example.
Some durations allow you to use a special value to mean unlimited.
Units are specified as follows.
ms
: milliseconds
s
: seconds
m
: minutes
h
: hours
d
: days
w
: weeks
Lower limit is 1 seconds.
No
No
None
No
No
Specifies the fully-qualified name of the Java class that provides the Static Service Discovery Mechanism implementation.
org.opends.server.backends.proxy.StaticServiceDiscoveryMechanism
A Java class that implements or extends the class(es): org.opends.server.backends.proxy.ServiceDiscoveryMechanism
No
Yes
The Service Discovery Mechanism must be disabled and re-enabled for changes to this setting to take effect
Yes (Use --advanced in interactive mode.)
No
Specifies the name of the key manager that should be used with this Service Discovery Mechanism.
None
The DN of any Key Manager Provider. The referenced key manager provider must be enabled when the Service Discovery Mechanism is enabled and configured to use SSL or StartTLS.
No
No
None
Changes to this property take effect immediately, but only for subsequent attempts to access the key manager provider for associated client connections.
No
No
Specifies a list of servers that will be used in preference to secondary servers when available.
None
A host name followed by a ":" and a port number.
Yes
No
None
No
No
Specifies a list of servers that will be used in place of primary servers when all primary servers are unavailable.
None
A host name followed by a ":" and a port number.
Yes
No
None
No
No
Specifies the nicknames (also called the aliases) of the keys or key pairs that the Service Discovery Mechanism should use when performing SSL communication. The property can be used multiple times (referencing different nicknames) when server certificates with different public key algorithms are used in parallel (for example, RSA, DSA, and ECC-based algorithms). When a nickname refers to an asymmetric (public/private) key pair, the nickname for the public key certificate and associated private key entry must match exactly. A single nickname is used to retrieve both the public key and the private key. This is only applicable when the Service Discovery Mechanism is configured to use SSL.
Let the server decide.
A String
Yes
No
The Service Discovery Mechanism must be disabled and re-enabled for changes to this setting to take effect
No
No
Specifies the name of the trust manager that should be used with the Service Discovery Mechanism.
Use the trust manager provided by the JVM.
The DN of any Trust Manager Provider. The referenced trust manager provider must be enabled when the Service Discovery Mechanism is enabled and configured to use SSL or StartTLS.
No
No
None
Changes to this property take effect immediately, but only for subsequent attempts to access the trust manager provider for associated client connections.
No
No
Indicates whether the Service Discovery Mechanism should use SSL. If enabled, the Service Discovery Mechanism will use SSL to encrypt communication with the clients.
false
true
false
No
No
The Service Discovery Mechanism must be disabled and re-enabled for changes to this setting to take effect
No
No
Indicates whether the Service Discovery Mechanism should use Start TLS. If enabled, the Service Discovery Mechanism will use Start TLS to encrypt communication with remote servers.
false
true
false
No
No
The Service Discovery Mechanism must be disabled and re-enabled for changes to this setting to take effect
No
No