From 111a2ca97d898c95006362b307a8d3d6d964a45b Mon Sep 17 00:00:00 2001
From: jpikus <jpikus@localhost>
Date: Fri, 05 Dec 2008 07:42:25 +0000
Subject: [PATCH] L10n localization of the generated files
---
opends/src/admin/messages/AlertHandlerCfgDefn.properties | 11
opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_zh_CN.properties | 7
opends/src/admin/messages/SynchronizationProviderCfgDefn_ja.properties | 6
opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_fr.properties | 11
opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_fr.properties | 9
opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_zh_TW.properties | 20
opends/src/admin/messages/LocalDBVLVIndexCfgDefn_fr.properties | 23
opends/src/admin/messages/NetworkGroupPluginCfgDefn_fr.properties | 59
opends/src/admin/messages/MonitorBackendCfgDefn_ko.properties | 15
opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_ko.properties | 30
opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_de.properties | 5
opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_de.properties | 5
opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_es.properties | 6
opends/src/admin/messages/TrustManagerProviderCfgDefn_ja.properties | 5
opends/src/admin/messages/EqualityMatchingRuleCfgDefn_zh_CN.properties | 5
opends/src/admin/messages/TrustManagerProviderCfgDefn_zh_TW.properties | 5
opends/src/admin/messages/PasswordGeneratorCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn.properties | 6
opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_fr.properties | 6
opends/src/admin/messages/EntryUUIDPluginCfgDefn_es.properties | 59
opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_zh_CN.properties | 5
opends/src/admin/messages/AttributeSyntaxCfgDefn_zh_TW.properties | 5
opends/src/admin/messages/BackupBackendCfgDefn_de.properties | 18
opends/src/admin/messages/WorkflowElementCfgDefn_zh_TW.properties | 9
opends/src/admin/messages/LocalDBVLVIndexCfgDefn_zh_CN.properties | 23
opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_de.properties | 6
opends/src/admin/messages/EntryUUIDPluginCfgDefn_zh_TW.properties | 59
opends/src/admin/messages/SchemaBackendCfgDefn_fr.properties | 20
opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_de.properties | 19
opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_ja.properties | 7
opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn.properties | 59
opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_fr.properties | 6
opends/src/admin/messages/NetworkGroupCfgDefn_ko.properties | 20
opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_fr.properties | 21
opends/src/admin/messages/ErrorLogPublisherCfgDefn_ja.properties | 21
opends/src/admin/messages/TaskBackendCfgDefn_de.properties | 21
opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_fr.properties | 10
opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_ko.properties | 48
opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_es.properties | 5
opends/src/admin/messages/MonitorProviderCfgDefn_de.properties | 6
opends/src/admin/messages/WorkflowCfgDefn_ko.properties | 10
opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_zh_CN.properties | 15
opends/src/admin/messages/PasswordValidatorCfgDefn_fr.properties | 6
opends/src/admin/messages/EntryCacheCfgDefn_ko.properties | 6
opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_es.properties | 20
opends/src/admin/messages/RootCfgDefn_ja.properties | 127
opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_ko.properties | 5
opends/src/admin/messages/FingerprintCertificateMapperCfgDefn.properties | 13
opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn.properties | 13
opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_ja.properties | 18
opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_zh_TW.properties | 18
opends/src/admin/messages/StackTraceMonitorProviderCfgDefn.properties | 5
opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_zh_CN.properties | 19
opends/src/admin/messages/RootCfgDefn_fr.properties | 127
opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_ko.properties | 6
opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_fr.properties | 8
opends/src/admin/messages/FileSystemEntryCacheCfgDefn_ja.properties | 24
opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_es.properties | 5
opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_ko.properties | 18
opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_ko.properties | 7
opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_es.properties | 6
opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_de.properties | 5
opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_zh_TW.properties | 25
opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_ko.properties | 19
opends/src/admin/messages/MonitorProviderCfgDefn.properties | 6
opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_ja.properties | 19
opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn.properties | 5
opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_ja.properties | 6
opends/src/admin/messages/OrderingMatchingRuleCfgDefn.properties | 6
opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_fr.properties | 9
opends/src/admin/messages/RootDNCfgDefn_fr.properties | 29
opends/src/admin/messages/CryptoManagerCfgDefn_es.properties | 27
opends/src/admin/messages/LocalDBIndexCfgDefn_fr.properties | 18
opends/src/admin/messages/RootCfgDefn_zh_TW.properties | 127
opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_zh_CN.properties | 18
opends/src/admin/messages/LocalDBBackendCfgDefn_zh_TW.properties | 76
opends/src/admin/messages/FileSystemEntryCacheCfgDefn_ko.properties | 24
opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/MemberVirtualAttributeCfgDefn_es.properties | 22
opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_de.properties | 5
opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_fr.properties | 15
opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_de.properties | 20
opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_ko.properties | 5
opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_fr.properties | 8
opends/src/admin/messages/EntryCacheCfgDefn_de.properties | 6
opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_es.properties | 5
opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_de.properties | 5
opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_es.properties | 13
opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_ko.properties | 19
opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_ja.properties | 11
opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/JMXAlertHandlerCfgDefn_zh_TW.properties | 11
opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_zh_CN.properties | 9
opends/src/admin/messages/LDIFBackendCfgDefn_ko.properties | 18
opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn.properties | 5
opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_ja.properties | 9
opends/src/admin/messages/TaskBackendCfgDefn_es.properties | 21
opends/src/admin/messages/AccessLogPublisherCfgDefn_zh_CN.properties | 8
opends/src/admin/messages/BackupBackendCfgDefn_ko.properties | 18
opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_zh_CN.properties | 12
opends/src/admin/messages/ConnectionHandlerCfgDefn_zh_CN.properties | 13
opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_fr.properties | 18
opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_fr.properties | 5
opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_es.properties | 6
opends/src/admin/messages/BackupBackendCfgDefn_es.properties | 18
opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn.properties | 5
opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_es.properties | 59
opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_ko.properties | 8
opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn.properties | 17
opends/src/admin/messages/WorkflowCfgDefn_ja.properties | 10
opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_de.properties | 7
opends/src/admin/messages/DebugTargetCfgDefn.properties | 28
opends/src/admin/messages/PasswordGeneratorCfgDefn_ko.properties | 6
opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_ko.properties | 6
opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_ko.properties | 5
opends/src/admin/messages/EntryUUIDPluginCfgDefn_de.properties | 59
opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_de.properties | 10
opends/src/admin/messages/GroupImplementationCfgDefn_es.properties | 6
opends/src/admin/messages/LastModPluginCfgDefn_zh_CN.properties | 59
opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_ja.properties | 20
opends/src/admin/messages/LDIFBackendCfgDefn_de.properties | 18
opends/src/admin/messages/TaskBackendCfgDefn_zh_CN.properties | 21
opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_ko.properties | 20
opends/src/admin/messages/LDIFBackendCfgDefn_es.properties | 18
opends/src/admin/messages/MatchingRuleCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_es.properties | 59
opends/src/admin/messages/PasswordGeneratorCfgDefn_es.properties | 6
opends/src/admin/messages/WorkflowCfgDefn_zh_TW.properties | 10
opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_es.properties | 10
opends/src/admin/messages/LogRotationPolicyCfgDefn_es.properties | 4
opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_es.properties | 19
opends/src/admin/messages/TraditionalWorkQueueCfgDefn_zh_TW.properties | 10
opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_zh_TW.properties | 5
opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_ko.properties | 5
opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_de.properties | 59
opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_es.properties | 6
opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_zh_TW.properties | 31
opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_es.properties | 8
opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_zh_TW.properties | 16
opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_de.properties | 6
opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn.properties | 20
opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn.properties | 6
opends/src/admin/messages/SubstringMatchingRuleCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_de.properties | 8
opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_zh_CN.properties | 18
opends/src/admin/messages/FileSystemEntryCacheCfgDefn_zh_TW.properties | 24
opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_zh_TW.properties | 5
opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_ja.properties | 8
opends/src/admin/messages/PluginRootCfgDefn_fr.properties | 157
opends/src/admin/messages/ExtensionCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/PasswordGeneratorCfgDefn_de.properties | 6
opends/src/admin/messages/WorkQueueCfgDefn.properties | 5
opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_ko.properties | 8
opends/src/admin/messages/IdentityMapperCfgDefn_es.properties | 5
opends/src/admin/messages/LogRotationPolicyCfgDefn_de.properties | 4
opends/src/admin/messages/AdministrationConnectorCfgDefn_es.properties | 14
opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_ko.properties | 10
opends/src/admin/messages/LocalDBVLVIndexCfgDefn_ja.properties | 23
opends/src/admin/messages/PluginRootCfgDefn_ja.properties | 157
opends/src/admin/messages/LDIFBackendCfgDefn_zh_TW.properties | 18
opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_de.properties | 13
opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn.properties | 5
opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_ja.properties | 5
opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_ko.properties | 10
opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_ko.properties | 59
opends/src/admin/messages/GroupImplementationCfgDefn.properties | 6
opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_fr.properties | 65
opends/src/admin/messages/TrustStoreBackendCfgDefn_zh_TW.properties | 29
opends/src/admin/messages/LocalDBVLVIndexCfgDefn_ko.properties | 23
opends/src/admin/messages/SevenBitCleanPluginCfgDefn_zh_TW.properties | 63
opends/src/admin/messages/PasswordStorageSchemeCfgDefn_ja.properties | 6
opends/src/admin/messages/JMXConnectionHandlerCfgDefn_zh_TW.properties | 24
opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_es.properties | 20
opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn.properties | 20
opends/src/admin/messages/MatchingRuleCfgDefn_ja.properties | 6
opends/src/admin/messages/NetworkGroupCfgDefn_es.properties | 20
opends/src/admin/messages/ErrorLogPublisherCfgDefn_zh_TW.properties | 21
opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_ja.properties | 15
opends/src/admin/messages/NetworkGroupPluginCfgDefn_ko.properties | 59
opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_zh_CN.properties | 64
opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_fr.properties | 48
opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn.properties | 5
opends/src/admin/messages/FIFOEntryCacheCfgDefn_es.properties | 12
opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_ja.properties | 6
opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_zh_TW.properties | 5
opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_zh_CN.properties | 5
opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_ja.properties | 8
opends/src/admin/messages/RootCfgDefn.properties | 127
opends/src/admin/messages/TraditionalWorkQueueCfgDefn_es.properties | 10
opends/src/admin/messages/CertificateMapperCfgDefn.properties | 5
opends/src/admin/messages/IdentityMapperCfgDefn.properties | 5
opends/src/admin/messages/SevenBitCleanPluginCfgDefn_fr.properties | 63
opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn.properties | 6
opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_de.properties | 19
opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_de.properties | 5
opends/src/admin/messages/SASLMechanismHandlerCfgDefn_ja.properties | 6
opends/src/admin/messages/SevenBitCleanPluginCfgDefn_es.properties | 63
opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_es.properties | 17
opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_zh_TW.properties | 5
opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_fr.properties | 8
opends/src/admin/messages/LogRotationPolicyCfgDefn_ko.properties | 4
opends/src/admin/messages/FileSystemEntryCacheCfgDefn_de.properties | 24
opends/src/admin/messages/MonitorProviderCfgDefn_es.properties | 6
opends/src/admin/messages/CryptoManagerCfgDefn_de.properties | 27
opends/src/admin/messages/EntryCacheCfgDefn_ja.properties | 6
opends/src/admin/messages/TaskBackendCfgDefn_ko.properties | 21
opends/src/admin/messages/CertificateMapperCfgDefn_zh_TW.properties | 5
opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_fr.properties | 19
opends/src/admin/messages/TaskBackendCfgDefn_ja.properties | 21
opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_zh_CN.properties | 21
opends/src/admin/messages/MemberVirtualAttributeCfgDefn_de.properties | 22
opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_zh_CN.properties | 8
opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_zh_CN.properties | 8
opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_fr.properties | 7
opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_zh_TW.properties | 13
opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_es.properties | 5
opends/src/admin/messages/MemberVirtualAttributeCfgDefn_zh_TW.properties | 22
opends/src/admin/messages/ReplicationDomainCfgDefn_ja.properties | 29
opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_zh_TW.properties | 5
opends/src/admin/messages/IdentityMapperCfgDefn_zh_TW.properties | 5
opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_ko.properties | 6
opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_fr.properties | 6
opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_es.properties | 5
opends/src/admin/messages/FileSystemEntryCacheCfgDefn_fr.properties | 24
opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_es.properties | 7
opends/src/admin/messages/NetworkGroupCfgDefn_fr.properties | 20
opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/EntryUUIDPluginCfgDefn_ko.properties | 59
opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn.properties | 25
opends/src/admin/messages/LocalDBIndexCfgDefn_ja.properties | 18
opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_fr.properties | 6
opends/src/admin/messages/KeyManagerProviderCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_es.properties | 6
opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_zh_TW.properties | 10
opends/src/admin/messages/LogRetentionPolicyCfgDefn.properties | 4
opends/src/admin/messages/LocalDBIndexCfgDefn_ko.properties | 18
opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_de.properties | 5
opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn.properties | 24
opends/src/admin/messages/NetworkGroupCfgDefn_de.properties | 20
opends/src/admin/messages/RootCfgDefn_ko.properties | 127
opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_ja.properties | 5
opends/src/admin/messages/TrustManagerProviderCfgDefn_ko.properties | 5
opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_de.properties | 6
opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_fr.properties | 16
opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_ko.properties | 6
opends/src/admin/messages/NetworkGroupPluginCfgDefn_ja.properties | 59
opends/src/admin/messages/EntryCacheCfgDefn.properties | 6
opends/src/admin/messages/SASLMechanismHandlerCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/ExtensionCfgDefn_fr.properties | 6
opends/src/admin/messages/OrderingMatchingRuleCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/EqualityMatchingRuleCfgDefn.properties | 5
opends/src/admin/messages/WorkQueueCfgDefn_zh_TW.properties | 5
opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_ja.properties | 10
opends/src/admin/messages/PasswordStorageSchemeCfgDefn_ko.properties | 6
opends/src/admin/messages/TrustStoreBackendCfgDefn_de.properties | 29
opends/src/admin/messages/MonitorProviderCfgDefn_fr.properties | 6
opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_zh_TW.properties | 19
opends/src/admin/messages/MonitorBackendCfgDefn_ja.properties | 15
opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_ja.properties | 30
opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_ko.properties | 5
opends/src/admin/messages/MatchingRuleCfgDefn_ko.properties | 6
opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_zh_TW.properties | 17
opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_zh_TW.properties | 10
opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_fr.properties | 5
opends/src/admin/messages/TraditionalWorkQueueCfgDefn_de.properties | 10
opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_fr.properties | 7
opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn.properties | 8
opends/src/admin/messages/LogRetentionPolicyCfgDefn_de.properties | 4
opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn.properties | 28
opends/src/admin/messages/SevenBitCleanPluginCfgDefn_de.properties | 63
opends/src/admin/messages/FileSystemEntryCacheCfgDefn_es.properties | 24
opends/src/admin/messages/ErrorLogPublisherCfgDefn_ko.properties | 21
opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_fr.properties | 5
opends/src/admin/messages/MonitorBackendCfgDefn_zh_TW.properties | 15
opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_zh_CN.properties | 5
opends/src/admin/messages/DynamicGroupImplementationCfgDefn_zh_CN.properties | 5
opends/src/admin/messages/ReplicationServerCfgDefn.properties | 19
opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_es.properties | 7
opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_de.properties | 20
opends/src/admin/messages/SASLMechanismHandlerCfgDefn_ko.properties | 6
opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_es.properties | 5
opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_ja.properties | 5
opends/src/admin/messages/FIFOEntryCacheCfgDefn_de.properties | 12
opends/src/admin/messages/GlobalCfgDefn_fr.properties | 80
opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_ja.properties | 6
opends/src/admin/messages/JMXAlertHandlerCfgDefn_ja.properties | 11
opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn.properties | 12
opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_ko.properties | 5
opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_ko.properties | 6
opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_ja.properties | 10
opends/src/admin/messages/PasswordStorageSchemeCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/KeyManagerProviderCfgDefn_ja.properties | 6
opends/src/admin/messages/FIFOEntryCacheCfgDefn_fr.properties | 12
opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_es.properties | 19
opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_fr.properties | 24
opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_fr.properties | 25
opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_de.properties | 7
opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn.properties | 19
opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_de.properties | 21
opends/src/admin/messages/KeyManagerProviderCfgDefn_ko.properties | 6
opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_zh_TW.properties | 10
opends/src/admin/messages/PasswordValidatorCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/ConnectionHandlerCfgDefn_fr.properties | 13
opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_es.properties | 48
opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_zh_CN.properties | 8
opends/src/admin/messages/LogRetentionPolicyCfgDefn_es.properties | 4
opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_de.properties | 48
opends/src/admin/messages/SchemaBackendCfgDefn_zh_TW.properties | 20
opends/src/admin/messages/TrustStoreBackendCfgDefn_es.properties | 29
opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_zh_TW.properties | 20
opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_ja.properties | 5
opends/src/admin/messages/SynchronizationProviderCfgDefn_ko.properties | 6
opends/src/admin/messages/TrustStoreBackendCfgDefn_fr.properties | 29
opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_ja.properties | 6
opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_de.properties | 10
opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_de.properties | 68
opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_ja.properties | 5
opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_de.properties | 20
opends/src/admin/messages/VersionMonitorProviderCfgDefn_fr.properties | 5
opends/src/admin/messages/PasswordValidatorCfgDefn_de.properties | 6
opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_zh_TW.properties | 25
opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_de.properties | 6
opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_zh_CN.properties | 20
opends/src/admin/messages/FIFOEntryCacheCfgDefn_zh_TW.properties | 12
opends/src/admin/messages/SNMPConnectionHandlerCfgDefn.properties | 31
opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_ja.properties | 16
opends/src/admin/messages/AdministrationConnectorCfgDefn.properties | 14
opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_ko.properties | 5
opends/src/admin/messages/BackendCfgDefn_de.properties | 16
opends/src/admin/messages/ReplicationServerCfgDefn_ja.properties | 19
opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/BackupBackendCfgDefn_zh_TW.properties | 18
opends/src/admin/messages/LogRotationPolicyCfgDefn_fr.properties | 4
opends/src/admin/messages/LastModPluginCfgDefn_ko.properties | 59
opends/src/admin/messages/LDIFBackendCfgDefn_zh_CN.properties | 18
opends/src/admin/messages/DynamicGroupImplementationCfgDefn_ja.properties | 5
opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_zh_TW.properties | 5
opends/src/admin/messages/LocalDBIndexCfgDefn_de.properties | 18
opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_ko.properties | 24
opends/src/admin/messages/ErrorLogPublisherCfgDefn_zh_CN.properties | 21
opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_ja.properties | 6
opends/src/admin/messages/VersionMonitorProviderCfgDefn.properties | 5
opends/src/admin/messages/ChangeNumberControlPluginCfgDefn.properties | 59
opends/src/admin/messages/AdministrationConnectorCfgDefn_ko.properties | 14
opends/src/admin/messages/AttributeSyntaxCfgDefn_ja.properties | 5
opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_ko.properties | 5
opends/src/admin/messages/ReplicationDomainCfgDefn_zh_CN.properties | 29
opends/src/admin/messages/UniqueAttributePluginCfgDefn_de.properties | 62
opends/src/admin/messages/SevenBitCleanPluginCfgDefn_zh_CN.properties | 63
opends/src/admin/messages/DebugTargetCfgDefn_ko.properties | 28
opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_de.properties | 11
opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_es.properties | 6
opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_fr.properties | 59
opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn.properties | 30
opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_ja.properties | 6
opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_ja.properties | 13
opends/src/admin/messages/PluginRootCfgDefn_zh_TW.properties | 157
opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_fr.properties | 6
opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_ko.properties | 5
opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_zh_TW.properties | 9
opends/src/admin/messages/ProfilerPluginCfgDefn_es.properties | 72
opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_zh_TW.properties | 21
opends/src/admin/messages/VersionMonitorProviderCfgDefn_zh_CN.properties | 5
opends/src/admin/messages/StaticGroupImplementationCfgDefn_fr.properties | 6
opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_zh_TW.properties | 5
opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_zh_TW.properties | 10
opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_zh_TW.properties | 59
opends/src/admin/messages/LogRotationPolicyCfgDefn_zh_CN.properties | 4
opends/src/admin/messages/AdministrationConnectorCfgDefn_zh_CN.properties | 14
opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_zh_CN.properties | 5
opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_ja.properties | 59
opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_zh_CN.properties | 5
opends/src/admin/messages/LastModPluginCfgDefn_zh_TW.properties | 59
opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_ko.properties | 9
opends/src/admin/messages/GroupImplementationCfgDefn_ko.properties | 6
opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_de.properties | 5
opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_ko.properties | 17
opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_ko.properties | 5
opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_zh_TW.properties | 13
opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_ja.properties | 6
opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/ReplicationDomainCfgDefn_ko.properties | 29
opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_zh_TW.properties | 5
opends/src/admin/messages/MemoryBackendCfgDefn_zh_CN.properties | 16
opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_zh_TW.properties | 11
opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_ko.properties | 18
opends/src/admin/messages/RootDNCfgDefn_es.properties | 29
opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_de.properties | 6
opends/src/admin/messages/IdentityMapperCfgDefn_zh_CN.properties | 5
opends/src/admin/messages/ReplicationDomainCfgDefn.properties | 29
opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_zh_TW.properties | 19
opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_es.properties | 9
opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_fr.properties | 19
opends/src/admin/messages/PasswordGeneratorCfgDefn_fr.properties | 6
opends/src/admin/messages/AccessControlHandlerCfgDefn_de.properties | 6
opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_ja.properties | 59
opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_de.properties | 25
opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_es.properties | 20
opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_zh_TW.properties | 5
opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_es.properties | 6
opends/src/admin/messages/LogRotationPolicyCfgDefn_ja.properties | 4
opends/src/admin/messages/ReplicationDomainCfgDefn_de.properties | 29
opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_fr.properties | 13
opends/src/admin/messages/AttributeSyntaxCfgDefn_fr.properties | 5
opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_fr.properties | 8
opends/src/admin/messages/MonitorBackendCfgDefn.properties | 15
opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_fr.properties | 5
opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_es.properties | 31
opends/src/admin/messages/JMXConnectionHandlerCfgDefn_es.properties | 24
opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn.properties | 6
opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_ko.properties | 13
opends/src/admin/messages/ProfilerPluginCfgDefn_zh_TW.properties | 72
opends/src/admin/messages/LogPublisherCfgDefn_de.properties | 4
opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_es.properties | 19
opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_ko.properties | 5
opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_zh_TW.properties | 5
opends/src/admin/messages/LocalDBVLVIndexCfgDefn.properties | 23
opends/src/admin/messages/PasswordPolicyCfgDefn_es.properties | 73
opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn.properties | 10
opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_es.properties | 10
opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_de.properties | 9
opends/src/admin/messages/DebugLogPublisherCfgDefn_fr.properties | 32
opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn.properties | 6
opends/src/admin/messages/SynchronizationProviderCfgDefn.properties | 6
opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_zh_CN.properties | 65
opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_ja.properties | 5
opends/src/admin/messages/BackupBackendCfgDefn_fr.properties | 18
opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_ja.properties | 8
opends/src/admin/messages/UniqueAttributePluginCfgDefn_zh_CN.properties | 62
opends/src/admin/messages/EqualityMatchingRuleCfgDefn_de.properties | 5
opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_es.properties | 6
opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn.properties | 8
opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_zh_TW.properties | 13
opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_zh_TW.properties | 19
opends/src/admin/messages/BackendCfgDefn.properties | 16
opends/src/admin/messages/LocalDBVLVIndexCfgDefn_de.properties | 23
opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_fr.properties | 9
opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn.properties | 18
opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_ko.properties | 37
opends/src/admin/messages/LogPublisherCfgDefn.properties | 4
opends/src/admin/messages/PluginRootCfgDefn_es.properties | 157
opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_es.properties | 6
opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_zh_TW.properties | 19
opends/src/admin/messages/IdentityMapperCfgDefn_ko.properties | 5
opends/src/admin/messages/UniqueAttributePluginCfgDefn_ko.properties | 62
opends/src/admin/messages/AdministrationConnectorCfgDefn_de.properties | 14
opends/src/admin/messages/RootDSEBackendCfgDefn_zh_TW.properties | 7
opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_ko.properties | 5
opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn.properties | 5
opends/src/admin/messages/BackendCfgDefn_zh_TW.properties | 16
opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_de.properties | 65
opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn.properties | 18
opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_es.properties | 6
opends/src/admin/messages/StaticGroupImplementationCfgDefn.properties | 6
opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_es.properties | 8
opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_zh_CN.properties | 28
opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn.properties | 20
opends/src/admin/messages/UniqueAttributePluginCfgDefn.properties | 62
opends/src/admin/messages/VirtualAttributeCfgDefn_zh_CN.properties | 20
opends/src/admin/messages/AlertHandlerCfgDefn_es.properties | 11
opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_zh_TW.properties | 16
opends/src/admin/messages/LocalDBIndexCfgDefn_zh_CN.properties | 18
opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_ko.properties | 65
opends/src/admin/messages/MonitorProviderCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/IdentityMapperCfgDefn_fr.properties | 5
opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_es.properties | 9
opends/src/admin/messages/AlertHandlerCfgDefn_fr.properties | 11
opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn.properties | 19
opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_fr.properties | 6
opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_es.properties | 15
opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_de.properties | 37
opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/DebugTargetCfgDefn_de.properties | 28
opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/LDIFBackendCfgDefn_ja.properties | 18
opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn.properties | 5
opends/src/admin/messages/SynchronizationProviderCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_zh_TW.properties | 7
opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_fr.properties | 18
opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn.properties | 6
opends/src/admin/messages/PluginRootCfgDefn_ko.properties | 157
opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_de.properties | 64
opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_es.properties | 5
opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_es.properties | 9
opends/src/admin/messages/ProfilerPluginCfgDefn_ko.properties | 72
opends/src/admin/messages/RootDNUserCfgDefn_de.properties | 6
opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_ko.properties | 6
opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_fr.properties | 10
opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn.properties | 6
opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_ja.properties | 6
opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_ko.properties | 9
opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_zh_TW.properties | 9
opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn.properties | 6
opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_fr.properties | 6
opends/src/admin/messages/ErrorLogPublisherCfgDefn.properties | 21
opends/src/admin/messages/KeyManagerProviderCfgDefn.properties | 6
opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_zh_CN.properties | 20
opends/src/admin/messages/GroupImplementationCfgDefn_de.properties | 6
opends/src/admin/messages/BackupBackendCfgDefn_ja.properties | 18
opends/src/admin/messages/JMXConnectionHandlerCfgDefn_ja.properties | 24
opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_ko.properties | 9
opends/src/admin/messages/SevenBitCleanPluginCfgDefn.properties | 63
opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_es.properties | 6
opends/src/admin/messages/TrustManagerProviderCfgDefn_de.properties | 5
opends/src/admin/messages/DebugLogPublisherCfgDefn_ja.properties | 32
opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_ja.properties | 20
opends/src/admin/messages/LastModPluginCfgDefn_fr.properties | 59
opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_zh_CN.properties | 7
opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_zh_CN.properties | 5
opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_fr.properties | 5
opends/src/admin/messages/LastModPluginCfgDefn_es.properties | 59
opends/src/admin/messages/PasswordValidatorCfgDefn_ja.properties | 6
opends/src/admin/messages/ErrorLogPublisherCfgDefn_de.properties | 21
opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_fr.properties | 6
opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_fr.properties | 59
opends/src/admin/messages/ReplicationServerCfgDefn_de.properties | 19
opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_ko.properties | 5
opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_zh_TW.properties | 5
opends/src/admin/messages/DebugTargetCfgDefn_zh_TW.properties | 28
opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_fr.properties | 20
opends/src/admin/messages/WorkflowCfgDefn_fr.properties | 10
opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_de.properties | 5
opends/src/admin/messages/AccessLogPublisherCfgDefn_ja.properties | 8
opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_fr.properties | 18
opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_zh_CN.properties | 18
opends/src/admin/messages/NetworkGroupPluginCfgDefn_zh_TW.properties | 59
opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_ja.properties | 6
opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_ja.properties | 7
opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn.properties | 37
opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_zh_CN.properties | 37
opends/src/admin/messages/WorkflowCfgDefn_es.properties | 10
opends/src/admin/messages/RootDNCfgDefn_ja.properties | 29
opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_ja.properties | 6
opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn.properties | 6
opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_es.properties | 19
opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_de.properties | 5
opends/build.xml | 16
opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn.properties | 10
opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_ja.properties | 8
opends/src/admin/messages/NetworkGroupCfgDefn_zh_TW.properties | 20
opends/src/admin/messages/CertificateMapperCfgDefn_de.properties | 5
opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_es.properties | 18
opends/src/admin/messages/LocalDBBackendCfgDefn_de.properties | 76
opends/src/admin/messages/RootDSEBackendCfgDefn.properties | 7
opends/src/admin/messages/RootDSEBackendCfgDefn_ko.properties | 7
opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_ko.properties | 20
opends/src/admin/messages/LDIFConnectionHandlerCfgDefn.properties | 16
opends/src/admin/messages/CryptoManagerCfgDefn_zh_CN.properties | 27
opends/src/admin/messages/PluginCfgDefn_zh_TW.properties | 58
opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn.properties | 6
opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_fr.properties | 6
opends/src/admin/messages/MonitorProviderCfgDefn_ko.properties | 6
opends/src/admin/messages/RootDNUserCfgDefn.properties | 6
opends/src/admin/messages/SMTPAlertHandlerCfgDefn_de.properties | 18
opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_de.properties | 5
opends/src/admin/messages/CryptoManagerCfgDefn_ko.properties | 27
opends/src/admin/messages/PluginCfgDefn_de.properties | 58
opends/src/admin/messages/StaticGroupImplementationCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/JMXAlertHandlerCfgDefn_de.properties | 11
opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_de.properties | 6
opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn.properties | 8
opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn.properties | 6
opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_ja.properties | 48
opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_ja.properties | 5
opends/src/admin/messages/SASLMechanismHandlerCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/DebugLogPublisherCfgDefn_zh_CN.properties | 32
opends/src/admin/messages/KeyManagerProviderCfgDefn_de.properties | 6
opends/src/admin/messages/SASLMechanismHandlerCfgDefn_es.properties | 6
opends/src/admin/messages/DynamicGroupImplementationCfgDefn_de.properties | 5
opends/src/admin/messages/GlobalCfgDefn_zh_CN.properties | 80
opends/src/admin/messages/LocalDBBackendCfgDefn.properties | 76
opends/src/admin/messages/GlobalCfgDefn_ko.properties | 80
opends/src/admin/messages/MatchingRuleCfgDefn_fr.properties | 6
opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_de.properties | 30
opends/src/admin/messages/MemberVirtualAttributeCfgDefn_ko.properties | 22
opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_es.properties | 6
opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_ja.properties | 21
opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_zh_CN.properties | 10
opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_es.properties | 18
opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_zh_CN.properties | 30
opends/src/admin/messages/RootCfgDefn_de.properties | 127
opends/src/admin/messages/MatchingRuleCfgDefn_es.properties | 6
opends/src/admin/messages/JMXConnectionHandlerCfgDefn.properties | 24
opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_ko.properties | 5
opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_es.properties | 10
opends/src/admin/messages/SchemaBackendCfgDefn_ja.properties | 20
opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_zh_TW.properties | 8
opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_zh_TW.properties | 12
opends/src/admin/messages/NetworkGroupPluginCfgDefn_es.properties | 59
opends/src/admin/messages/SynchronizationProviderCfgDefn_de.properties | 6
opends/src/admin/messages/SASLMechanismHandlerCfgDefn.properties | 6
opends/src/admin/messages/SASLMechanismHandlerCfgDefn_fr.properties | 6
opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_zh_TW.properties | 8
opends/src/admin/messages/FileSystemEntryCacheCfgDefn.properties | 24
opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_de.properties | 16
opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_es.properties | 6
opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_es.properties | 10
opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_de.properties | 5
opends/src/admin/messages/MemberVirtualAttributeCfgDefn_zh_CN.properties | 22
opends/src/admin/messages/ExtensionCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_fr.properties | 10
opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_zh_CN.properties | 10
opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn.properties | 10
opends/src/admin/messages/NetworkGroupCriteriaCfgDefn.properties | 16
opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_ja.properties | 10
opends/src/admin/messages/PasswordStorageSchemeCfgDefn_de.properties | 6
opends/src/admin/messages/TrustStoreBackendCfgDefn_ko.properties | 29
opends/src/admin/messages/AccessControlHandlerCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/BlindTrustManagerProviderCfgDefn.properties | 6
opends/src/admin/messages/DynamicGroupImplementationCfgDefn.properties | 5
opends/src/admin/messages/PasswordPolicyCfgDefn_zh_TW.properties | 73
opends/src/admin/messages/LogRetentionPolicyCfgDefn_ja.properties | 4
opends/src/admin/messages/ExtensionCfgDefn_ko.properties | 6
opends/src/admin/messages/TraditionalWorkQueueCfgDefn_ko.properties | 10
opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn.properties | 8
opends/src/admin/messages/WorkflowElementCfgDefn_fr.properties | 9
opends/src/admin/messages/FIFOEntryCacheCfgDefn_ja.properties | 12
opends/src/admin/messages/MonitorBackendCfgDefn_fr.properties | 15
opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/SevenBitCleanPluginCfgDefn_ko.properties | 63
opends/src/admin/messages/AlertHandlerCfgDefn_zh_TW.properties | 11
opends/src/admin/messages/MonitorBackendCfgDefn_es.properties | 15
opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_es.properties | 6
opends/src/admin/messages/SubstringMatchingRuleCfgDefn_de.properties | 6
opends/src/admin/messages/WorkflowElementCfgDefn_es.properties | 9
opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_fr.properties | 6
opends/src/admin/messages/BackupBackendCfgDefn.properties | 18
opends/src/admin/messages/LogRetentionPolicyCfgDefn_zh_CN.properties | 4
opends/src/admin/messages/JMXAlertHandlerCfgDefn_zh_CN.properties | 11
opends/src/admin/messages/LocalDBIndexCfgDefn.properties | 18
opends/src/admin/messages/ConnectionHandlerCfgDefn_ja.properties | 13
opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_fr.properties | 6
opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_ja.properties | 19
opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_ko.properties | 25
opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn.properties | 48
opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_ja.properties | 16
opends/src/admin/messages/PasswordStorageSchemeCfgDefn.properties | 6
opends/src/admin/messages/RootDNUserCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_ko.properties | 5
opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_de.properties | 5
opends/src/admin/messages/EqualityMatchingRuleCfgDefn_ja.properties | 5
opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_ko.properties | 6
opends/src/admin/messages/CertificateMapperCfgDefn_ja.properties | 5
opends/src/admin/messages/AlertHandlerCfgDefn_ko.properties | 11
opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_ko.properties | 6
opends/src/admin/messages/RootDNCfgDefn.properties | 29
opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_ko.properties | 6
opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_ko.properties | 6
opends/src/admin/messages/StaticGroupImplementationCfgDefn_es.properties | 6
opends/src/admin/messages/RootDSEBackendCfgDefn_de.properties | 7
opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_fr.properties | 31
opends/src/admin/messages/BackendCfgDefn_fr.properties | 16
opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_ko.properties | 18
opends/src/admin/messages/MemberVirtualAttributeCfgDefn.properties | 22
opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn.properties | 19
opends/src/admin/messages/GlobalCfgDefn_es.properties | 80
opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_ja.properties | 6
opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_zh_TW.properties | 5
opends/src/admin/messages/TrustStoreBackendCfgDefn_zh_CN.properties | 29
opends/src/admin/messages/OrderingMatchingRuleCfgDefn_ja.properties | 6
opends/src/admin/messages/UniqueAttributePluginCfgDefn_fr.properties | 62
opends/src/admin/messages/SynchronizationProviderCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_de.properties | 6
opends/src/admin/messages/PasswordPolicyCfgDefn_fr.properties | 73
opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_ja.properties | 5
opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_ja.properties | 12
opends/src/admin/messages/ReplicationServerCfgDefn_es.properties | 19
opends/src/admin/messages/VersionMonitorProviderCfgDefn_de.properties | 5
opends/src/admin/messages/ProfilerPluginCfgDefn_fr.properties | 72
opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/DynamicGroupImplementationCfgDefn_es.properties | 5
opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_zh_CN.properties | 13
opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn.properties | 5
opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_fr.properties | 6
opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_zh_CN.properties | 5
opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_ja.properties | 25
opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_ja.properties | 6
opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_ja.properties | 20
opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_ja.properties | 64
opends/src/admin/messages/CertificateMapperCfgDefn_zh_CN.properties | 5
opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_es.properties | 13
opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_ko.properties | 6
opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_ko.properties | 64
opends/src/admin/messages/LogPublisherCfgDefn_ja.properties | 4
opends/src/admin/messages/WorkQueueCfgDefn_es.properties | 5
opends/src/admin/messages/AccessLogPublisherCfgDefn_ko.properties | 8
opends/src/admin/messages/LocalDBBackendCfgDefn_ja.properties | 76
opends/src/admin/messages/LocalDBBackendCfgDefn_fr.properties | 76
opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_zh_CN.properties | 5
opends/src/admin/messages/TaskBackendCfgDefn.properties | 21
opends/src/admin/messages/RootDNUserCfgDefn_ja.properties | 6
opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_fr.properties | 25
opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_es.properties | 16
opends/src/admin/messages/MatchingRuleCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/PluginRootCfgDefn.properties | 157
opends/src/admin/messages/VirtualAttributeCfgDefn_de.properties | 20
opends/src/admin/messages/DynamicGroupImplementationCfgDefn_zh_TW.properties | 5
opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_zh_TW.properties | 10
opends/src/admin/messages/JMXConnectionHandlerCfgDefn_fr.properties | 24
opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_de.properties | 19
opends/src/admin/messages/RootDNUserCfgDefn_ko.properties | 6
opends/src/admin/messages/WorkQueueCfgDefn_de.properties | 5
opends/src/admin/messages/SMTPAlertHandlerCfgDefn_zh_TW.properties | 18
opends/src/admin/messages/AttributeSyntaxCfgDefn_es.properties | 5
opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_zh_CN.properties | 5
opends/src/admin/messages/NetworkGroupCfgDefn.properties | 20
opends/src/admin/messages/StaticGroupImplementationCfgDefn_de.properties | 6
opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_es.properties | 6
opends/src/admin/messages/KeyManagerProviderCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/DebugLogPublisherCfgDefn_de.properties | 32
opends/src/admin/messages/EntryUUIDPluginCfgDefn.properties | 59
opends/src/admin/messages/UniqueAttributePluginCfgDefn_zh_TW.properties | 62
opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_ko.properties | 20
opends/src/admin/messages/EqualityMatchingRuleCfgDefn_fr.properties | 5
opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_zh_CN.properties | 10
opends/src/admin/messages/StaticGroupImplementationCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/LogRetentionPolicyCfgDefn_zh_TW.properties | 4
opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_ja.properties | 6
opends/src/admin/messages/VirtualAttributeCfgDefn_ko.properties | 20
opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_ko.properties | 13
opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_es.properties | 8
opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_zh_TW.properties | 8
opends/src/admin/messages/DebugTargetCfgDefn_es.properties | 28
opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_ja.properties | 18
opends/src/admin/messages/CertificateMapperCfgDefn_fr.properties | 5
opends/src/admin/messages/WorkQueueCfgDefn_zh_CN.properties | 5
opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_de.properties | 9
opends/src/admin/messages/MemoryBackendCfgDefn_de.properties | 16
opends/src/admin/messages/RootCfgDefn_zh_CN.properties | 127
opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_ja.properties | 6
opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn.properties | 5
opends/src/admin/messages/CertificateMapperCfgDefn_ko.properties | 5
opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_fr.properties | 6
opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_zh_CN.properties | 20
opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_es.properties | 6
opends/src/admin/messages/AccessLogPublisherCfgDefn_de.properties | 8
opends/src/admin/messages/DebugLogPublisherCfgDefn_ko.properties | 32
opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_fr.properties | 5
opends/src/admin/messages/PasswordPolicyCfgDefn_ja.properties | 73
opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn.properties | 7
opends/src/admin/messages/NetworkGroupPluginCfgDefn.properties | 59
opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_ja.properties | 31
opends/src/admin/messages/JMXAlertHandlerCfgDefn.properties | 11
opends/src/admin/messages/LogPublisherCfgDefn_fr.properties | 4
opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_de.properties | 8
opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_ko.properties | 6
opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_ja.properties | 6
opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_es.properties | 13
opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_fr.properties | 20
opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_ko.properties | 6
opends/src/admin/messages/ApproximateMatchingRuleCfgDefn.properties | 5
opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_ja.properties | 37
opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_ko.properties | 5
opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_de.properties | 6
opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_de.properties | 13
opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn.properties | 5
opends/src/admin/messages/AccessControlHandlerCfgDefn_ja.properties | 6
opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_de.properties | 6
opends/src/admin/messages/MemoryBackendCfgDefn_ko.properties | 16
opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_fr.properties | 37
opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_zh_TW.properties | 8
opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_fr.properties | 28
opends/src/admin/messages/UniqueAttributePluginCfgDefn_ja.properties | 62
opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_de.properties | 5
opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_ja.properties | 8
opends/src/admin/messages/VersionMonitorProviderCfgDefn_es.properties | 5
opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_ko.properties | 9
opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn.properties | 6
opends/src/admin/messages/AccessControlHandlerCfgDefn_fr.properties | 6
opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_ja.properties | 28
opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_zh_CN.properties | 5
opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_ko.properties | 5
opends/src/admin/messages/AlertHandlerCfgDefn_de.properties | 11
opends/src/admin/messages/LastModPluginCfgDefn.properties | 59
opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_zh_TW.properties | 5
opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_es.properties | 65
opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_zh_TW.properties | 30
opends/src/admin/messages/AlertHandlerCfgDefn_ja.properties | 11
opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_zh_CN.properties | 10
opends/src/admin/messages/MemoryBackendCfgDefn_es.properties | 16
opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_ja.properties | 10
opends/src/admin/messages/AccessControlHandlerCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/VersionMonitorProviderCfgDefn_ko.properties | 5
opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_ja.properties | 6
opends/src/admin/messages/TrustManagerProviderCfgDefn_zh_CN.properties | 5
opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_fr.properties | 6
opends/src/admin/messages/OrderingMatchingRuleCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_fr.properties | 5
opends/src/admin/messages/MemoryBackendCfgDefn_ja.properties | 16
opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_ko.properties | 28
opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_ja.properties | 9
opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_ko.properties | 8
opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_ko.properties | 10
opends/src/admin/messages/EqualityMatchingRuleCfgDefn_ko.properties | 5
opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_ja.properties | 5
opends/src/admin/messages/PasswordPolicyCfgDefn.properties | 73
opends/src/admin/messages/WorkflowElementCfgDefn_zh_CN.properties | 9
opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_de.properties | 6
opends/src/admin/messages/BackupBackendCfgDefn_zh_CN.properties | 18
opends/src/admin/messages/ExtensionCfgDefn.properties | 6
opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn.properties | 18
opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_fr.properties | 6
opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_es.properties | 5
opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_de.properties | 8
opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_zh_TW.properties | 20
opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_zh_CN.properties | 19
opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_de.properties | 12
opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_ko.properties | 6
opends/src/admin/messages/WorkQueueCfgDefn_ko.properties | 5
opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_de.properties | 5
opends/src/admin/messages/StaticGroupImplementationCfgDefn_ko.properties | 6
opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_zh_CN.properties | 48
opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_de.properties | 28
opends/src/admin/messages/SchemaBackendCfgDefn.properties | 20
opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_zh_TW.properties | 18
opends/src/admin/messages/OrderingMatchingRuleCfgDefn_de.properties | 6
opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_fr.properties | 5
opends/src/admin/messages/LocalDBBackendCfgDefn_zh_CN.properties | 76
opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_fr.properties | 5
opends/src/admin/messages/AlertHandlerCfgDefn_zh_CN.properties | 11
opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_zh_CN.properties | 10
opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_fr.properties | 5
opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_es.properties | 18
opends/src/admin/messages/WorkflowElementCfgDefn_ko.properties | 9
opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_zh_TW.properties | 18
opends/src/admin/messages/RootDNCfgDefn_zh_TW.properties | 29
opends/src/admin/messages/PasswordGeneratorCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/AccessLogPublisherCfgDefn_es.properties | 8
opends/src/admin/messages/AccessControlHandlerCfgDefn_ko.properties | 6
opends/src/admin/messages/AccessLogPublisherCfgDefn.properties | 8
opends/src/admin/messages/EqualityMatchingRuleCfgDefn_zh_TW.properties | 5
opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_fr.properties | 13
opends/src/admin/messages/LocalDBBackendCfgDefn_ko.properties | 76
opends/src/admin/messages/MatchingRuleCfgDefn.properties | 6
opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_es.properties | 5
opends/src/admin/messages/PluginCfgDefn_ja.properties | 58
opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_ko.properties | 25
opends/src/admin/messages/VirtualAttributeCfgDefn_es.properties | 20
opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn.properties | 10
opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_fr.properties | 17
opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_es.properties | 6
opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_de.properties | 13
opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_de.properties | 5
opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_ko.properties | 31
opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_de.properties | 6
opends/src/admin/messages/GlobalCfgDefn_de.properties | 80
opends/src/admin/messages/RootDSEBackendCfgDefn_es.properties | 7
opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_zh_TW.properties | 5
opends/src/admin/messages/DebugLogPublisherCfgDefn_es.properties | 32
opends/src/admin/messages/SMTPAlertHandlerCfgDefn_ja.properties | 18
opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_de.properties | 6
opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_ja.properties | 9
opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_de.properties | 6
opends/src/admin/messages/LogPublisherCfgDefn_zh_CN.properties | 4
opends/src/admin/messages/DynamicGroupImplementationCfgDefn_ko.properties | 5
opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_ja.properties | 6
opends/src/admin/messages/VirtualAttributeCfgDefn.properties | 20
opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_es.properties | 5
opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_zh_TW.properties | 5
opends/src/admin/messages/ReplicationDomainCfgDefn_zh_TW.properties | 29
opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_es.properties | 6
opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_ja.properties | 19
opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_de.properties | 16
opends/src/admin/messages/AttributeSyntaxCfgDefn_zh_CN.properties | 5
opends/src/admin/messages/AttributeSyntaxCfgDefn_de.properties | 5
opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_ko.properties | 6
opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_fr.properties | 6
opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_zh_CN.properties | 59
opends/src/admin/messages/LDIFBackendCfgDefn.properties | 18
opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_es.properties | 25
opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn.properties | 9
opends/src/admin/messages/WorkQueueCfgDefn_ja.properties | 5
opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_ko.properties | 16
opends/src/admin/messages/CryptoManagerCfgDefn_fr.properties | 27
opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_zh_CN.properties | 5
opends/src/admin/messages/MemberVirtualAttributeCfgDefn_fr.properties | 22
opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_es.properties | 8
opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_ko.properties | 19
opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn.properties | 6
opends/src/admin/messages/PasswordValidatorCfgDefn_es.properties | 6
opends/src/admin/messages/SchemaBackendCfgDefn_es.properties | 20
opends/src/admin/messages/WorkflowElementCfgDefn_ja.properties | 9
opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_zh_TW.properties | 68
opends/src/admin/messages/ReplicationServerCfgDefn_zh_TW.properties | 19
opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_fr.properties | 6
opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_ja.properties | 6
opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_zh_TW.properties | 9
opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn.properties | 5
opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_es.properties | 21
opends/src/admin/messages/ConnectionHandlerCfgDefn_de.properties | 13
opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_es.properties | 12
opends/src/admin/messages/TraditionalWorkQueueCfgDefn_zh_CN.properties | 10
opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_zh_CN.properties | 59
opends/src/admin/messages/OrderingMatchingRuleCfgDefn_es.properties | 6
opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_ja.properties | 6
opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_zh_CN.properties | 16
opends/src/admin/messages/SubstringMatchingRuleCfgDefn_ja.properties | 6
opends/src/admin/messages/BackendCfgDefn_ja.properties | 16
opends/src/admin/messages/OrderingMatchingRuleCfgDefn_fr.properties | 6
opends/src/admin/messages/ExtensionCfgDefn_de.properties | 6
opends/src/admin/messages/FIFOEntryCacheCfgDefn.properties | 12
opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn.properties | 5
opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_fr.properties | 12
opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_ko.properties | 10
opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_de.properties | 10
opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_es.properties | 5
opends/src/admin/messages/AccessControlHandlerCfgDefn.properties | 6
opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_zh_CN.properties | 31
opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_ja.properties | 10
opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_fr.properties | 10
opends/src/admin/messages/PasswordGeneratorCfgDefn.properties | 6
opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/WorkflowCfgDefn_zh_CN.properties | 10
opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_ko.properties | 10
opends/src/admin/messages/PluginCfgDefn_ko.properties | 58
opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_ko.properties | 68
opends/src/admin/messages/TraditionalWorkQueueCfgDefn_fr.properties | 10
opends/src/admin/messages/BackendCfgDefn_ko.properties | 16
opends/src/admin/messages/ConnectionHandlerCfgDefn_es.properties | 13
opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_de.properties | 19
opends/src/admin/messages/ExtensionCfgDefn_es.properties | 6
opends/src/admin/messages/PasswordValidatorCfgDefn.properties | 6
opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_zh_TW.properties | 65
opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_zh_CN.properties | 24
opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn.properties | 6
opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn.properties | 5
opends/src/admin/messages/ConnectionHandlerCfgDefn_zh_TW.properties | 13
opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_es.properties | 24
opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_fr.properties | 19
opends/src/admin/messages/GroupImplementationCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_de.properties | 24
opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_es.properties | 5
opends/src/admin/messages/SubstringMatchingRuleCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_ko.properties | 6
opends/src/admin/messages/EntryCacheCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_zh_TW.properties | 20
opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_ja.properties | 6
opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn.properties | 6
opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/LogRetentionPolicyCfgDefn_fr.properties | 4
opends/src/admin/messages/EntryUUIDPluginCfgDefn_zh_CN.properties | 59
opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_ja.properties | 68
opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_zh_CN.properties | 5
opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_de.properties | 5
opends/src/admin/messages/LocalDBBackendCfgDefn_es.properties | 76
opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_es.properties | 25
opends/src/admin/messages/LogPublisherCfgDefn_es.properties | 4
opends/src/admin/messages/SMTPAlertHandlerCfgDefn.properties | 18
opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn.properties | 10
opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_ko.properties | 5
opends/src/admin/messages/KeyManagerProviderCfgDefn_es.properties | 6
opends/src/admin/messages/SASLMechanismHandlerCfgDefn_de.properties | 6
opends/src/admin/messages/AttributeSyntaxCfgDefn.properties | 5
opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn.properties | 5
opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_es.properties | 10
opends/src/admin/messages/RootCfgDefn_es.properties | 127
opends/src/admin/messages/MemberVirtualAttributeCfgDefn_ja.properties | 22
opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn.properties | 10
opends/src/admin/messages/JMXConnectionHandlerCfgDefn_zh_CN.properties | 24
opends/src/admin/messages/SchemaBackendCfgDefn_de.properties | 20
opends/src/admin/messages/CryptoManagerCfgDefn.properties | 27
opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_zh_TW.properties | 48
opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_zh_TW.properties | 7
opends/src/admin/messages/LogRetentionPolicyCfgDefn_ko.properties | 4
opends/src/admin/messages/TrustStoreBackendCfgDefn.properties | 29
opends/src/admin/messages/AccessControlHandlerCfgDefn_es.properties | 6
opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_fr.properties | 6
opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_ko.properties | 6
opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_fr.properties | 6
opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_fr.properties | 20
opends/src/admin/messages/CryptoManagerCfgDefn_ja.properties | 27
opends/src/admin/messages/LogPublisherCfgDefn_zh_TW.properties | 4
opends/src/admin/messages/PluginCfgDefn.properties | 58
opends/src/admin/messages/ProfilerPluginCfgDefn.properties | 72
opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_es.properties | 5
opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_ja.properties | 5
opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_ja.properties | 5
opends/src/admin/messages/PasswordPolicyCfgDefn_de.properties | 73
opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn.properties | 6
opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn.properties | 6
opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_zh_CN.properties | 16
opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_ja.properties | 5
opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_de.properties | 8
opends/src/admin/messages/JMXAlertHandlerCfgDefn_ko.properties | 11
opends/src/admin/messages/GlobalCfgDefn_ja.properties | 80
opends/src/admin/messages/FileSystemEntryCacheCfgDefn_zh_CN.properties | 24
opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_zh_TW.properties | 37
opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_ja.properties | 13
opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn.properties | 21
opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_zh_TW.properties | 64
opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_de.properties | 25
opends/src/admin/messages/SubstringMatchingRuleCfgDefn_ko.properties | 6
opends/src/admin/messages/WorkQueueCfgDefn_fr.properties | 5
opends/src/admin/messages/DebugTargetCfgDefn_zh_CN.properties | 28
opends/src/admin/messages/LocalDBIndexCfgDefn_zh_TW.properties | 18
opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_fr.properties | 5
opends/src/admin/messages/TrustManagerProviderCfgDefn_es.properties | 5
opends/src/admin/messages/NetworkGroupPluginCfgDefn_de.properties | 59
opends/src/admin/messages/ProfilerPluginCfgDefn_de.properties | 72
opends/src/admin/messages/SMTPAlertHandlerCfgDefn_ko.properties | 18
opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_ko.properties | 8
opends/src/admin/messages/ErrorLogPublisherCfgDefn_es.properties | 21
opends/src/admin/messages/PluginCfgDefn_zh_CN.properties | 58
opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_de.properties | 6
opends/src/admin/messages/RootDNCfgDefn_de.properties | 29
opends/src/admin/messages/EntryUUIDPluginCfgDefn_fr.properties | 59
opends/src/admin/messages/TaskBackendCfgDefn_fr.properties | 21
opends/src/admin/messages/TaskBackendCfgDefn_zh_TW.properties | 21
opends/src/admin/messages/GroupImplementationCfgDefn_ja.properties | 6
opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_ko.properties | 13
opends/src/admin/messages/RootDSEBackendCfgDefn_fr.properties | 7
opends/src/admin/messages/CryptoManagerCfgDefn_zh_TW.properties | 27
opends/src/admin/messages/NetworkGroupCfgDefn_zh_CN.properties | 20
opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_ja.properties | 5
opends/src/admin/messages/MemoryBackendCfgDefn.properties | 16
opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_ko.properties | 59
opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_zh_TW.properties | 5
opends/src/admin/messages/CertificateMapperCfgDefn_es.properties | 5
opends/src/admin/messages/RootDNCfgDefn_zh_CN.properties | 29
opends/src/admin/messages/EntryUUIDPluginCfgDefn_ja.properties | 59
opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_de.properties | 9
opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_zh_TW.properties | 59
opends/src/admin/messages/NetworkGroupPluginCfgDefn_zh_CN.properties | 59
opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_zh_CN.properties | 9
opends/src/admin/messages/JMXConnectionHandlerCfgDefn_de.properties | 24
opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_ja.properties | 5
opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_fr.properties | 6
opends/src/admin/messages/SubstringMatchingRuleCfgDefn.properties | 6
opends/src/admin/messages/ExtendedOperationHandlerCfgDefn.properties | 5
opends/src/admin/messages/LastModPluginCfgDefn_ja.properties | 59
opends/src/admin/messages/ReplicationServerCfgDefn_fr.properties | 19
opends/src/admin/messages/VersionMonitorProviderCfgDefn_ja.properties | 5
opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_es.properties | 37
opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn.properties | 68
opends/src/admin/messages/GroupImplementationCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/AdministrationConnectorCfgDefn_ja.properties | 14
opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_fr.properties | 5
opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_ko.properties | 15
opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_es.properties | 20
opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_fr.properties | 10
opends/src/admin/messages/AccessLogPublisherCfgDefn_fr.properties | 8
opends/src/admin/messages/TrustManagerProviderCfgDefn.properties | 5
opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_fr.properties | 5
opends/src/admin/messages/EntryCacheCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/StaticGroupImplementationCfgDefn_ja.properties | 6
opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_es.properties | 28
opends/src/admin/messages/VirtualAttributeCfgDefn_fr.properties | 20
opends/src/admin/messages/DebugTargetCfgDefn_ja.properties | 28
opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_fr.properties | 6
opends/src/admin/messages/TraditionalWorkQueueCfgDefn.properties | 10
opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_es.properties | 11
opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_zh_CN.properties | 5
opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_zh_CN.properties | 20
opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_de.properties | 17
opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn.properties | 6
opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_es.properties | 6
opends/src/admin/messages/UniqueAttributePluginCfgDefn_es.properties | 62
opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_fr.properties | 20
opends/src/admin/messages/GlobalCfgDefn_zh_TW.properties | 80
opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_de.properties | 8
opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_zh_CN.properties | 13
opends/src/admin/messages/JMXConnectionHandlerCfgDefn_ko.properties | 24
opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_fr.properties | 13
opends/src/admin/messages/LDIFBackendCfgDefn_fr.properties | 18
opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_es.properties | 64
opends/src/admin/messages/RandomPasswordGeneratorCfgDefn.properties | 11
opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_zh_TW.properties | 5
opends/src/admin/messages/ReplicationServerCfgDefn_zh_CN.properties | 19
opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_de.properties | 18
opends/src/admin/messages/AttributeSyntaxCfgDefn_ko.properties | 5
opends/src/admin/messages/PluginRootCfgDefn_de.properties | 157
opends/src/admin/messages/LocalDBVLVIndexCfgDefn_es.properties | 23
opends/src/admin/messages/PasswordStorageSchemeCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn.properties | 64
opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_ja.properties | 5
opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn.properties | 15
opends/src/admin/messages/EqualityMatchingRuleCfgDefn_es.properties | 5
opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_de.properties | 15
opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn.properties | 19
opends/src/admin/messages/IdentityMapperCfgDefn_ja.properties | 5
opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_fr.properties | 8
opends/src/admin/messages/PasswordPolicyCfgDefn_ko.properties | 73
opends/src/admin/messages/SchemaBackendCfgDefn_zh_CN.properties | 20
opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_fr.properties | 19
opends/src/admin/messages/MemoryBackendCfgDefn_fr.properties | 16
opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_es.properties | 5
opends/src/admin/messages/DebugLogPublisherCfgDefn_zh_TW.properties | 32
opends/src/admin/messages/ReplicationServerCfgDefn_ko.properties | 19
opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_de.properties | 31
opends/src/admin/messages/RootDNUserCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_ja.properties | 65
opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_zh_CN.properties | 17
opends/src/admin/messages/DebugLogPublisherCfgDefn.properties | 32
opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_zh_TW.properties | 10
opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_de.properties | 9
opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_de.properties | 6
opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_es.properties | 6
opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn.properties | 13
opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_fr.properties | 5
opends/src/admin/messages/PasswordPolicyCfgDefn_zh_CN.properties | 73
opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_ja.properties | 19
opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn.properties | 8
opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_zh_CN.properties | 68
opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_de.properties | 10
opends/src/admin/messages/SMTPAlertHandlerCfgDefn_es.properties | 18
opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_de.properties | 6
opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_de.properties | 20
opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_fr.properties | 5
opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_ja.properties | 13
opends/src/admin/messages/MonitorProviderCfgDefn_ja.properties | 6
opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_ja.properties | 10
opends/src/admin/messages/AdministrationConnectorCfgDefn_fr.properties | 14
opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_es.properties | 8
opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_zh_CN.properties | 25
opends/src/admin/messages/IdentityMapperCfgDefn_de.properties | 5
opends/src/admin/messages/PasswordGeneratorCfgDefn_ja.properties | 6
opends/src/admin/messages/LocalDBVLVIndexCfgDefn_zh_TW.properties | 23
opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn.properties | 7
opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_ko.properties | 19
opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_zh_CN.properties | 25
opends/src/admin/messages/FIFOEntryCacheCfgDefn_zh_CN.properties | 12
opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/JMXAlertHandlerCfgDefn_es.properties | 11
opends/src/admin/messages/LDAPConnectionHandlerCfgDefn.properties | 65
opends/src/admin/messages/EntryCacheCfgDefn_es.properties | 6
opends/src/admin/messages/PluginCfgDefn_es.properties | 58
opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_es.properties | 5
opends/src/admin/messages/DebugTargetCfgDefn_fr.properties | 28
opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_de.properties | 6
opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_fr.properties | 30
opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/SubstringMatchingRuleCfgDefn_fr.properties | 6
opends/src/admin/messages/AdministrationConnectorCfgDefn_zh_TW.properties | 14
opends/src/admin/messages/RootDNCfgDefn_ko.properties | 29
opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn.properties | 9
opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_es.properties | 9
opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_de.properties | 59
opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_zh_TW.properties | 24
opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_ja.properties | 5
opends/src/admin/messages/PasswordValidatorCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/VirtualAttributeCfgDefn_zh_TW.properties | 20
opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_es.properties | 30
opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_de.properties | 10
opends/src/admin/messages/PasswordStorageSchemeCfgDefn_es.properties | 6
opends/src/admin/messages/ReplicationDomainCfgDefn_es.properties | 29
opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_zh_TW.properties | 5
opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_zh_TW.properties | 8
opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_ja.properties | 5
opends/src/admin/messages/GlobalCfgDefn.properties | 80
opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_de.properties | 18
opends/src/admin/messages/VirtualAttributeCfgDefn_ja.properties | 20
opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_es.properties | 5
opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_zh_CN.properties | 11
opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn.properties | 9
opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_fr.properties | 64
opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_zh_CN.properties | 5
opends/src/admin/messages/GroupImplementationCfgDefn_fr.properties | 6
opends/src/admin/messages/MonitorBackendCfgDefn_zh_CN.properties | 15
opends/src/admin/messages/NetworkGroupCfgDefn_ja.properties | 20
opends/src/admin/messages/ReplicationDomainCfgDefn_fr.properties | 29
opends/src/admin/messages/PluginCfgDefn_fr.properties | 58
opends/src/admin/messages/SchemaBackendCfgDefn_ko.properties | 20
opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_fr.properties | 5
opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_de.properties | 18
opends/src/admin/messages/SMTPAlertHandlerCfgDefn_fr.properties | 18
opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_zh_CN.properties | 5
opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_ko.properties | 20
opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_fr.properties | 9
opends/src/admin/messages/EntryCacheCfgDefn_fr.properties | 6
opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_ja.properties | 5
opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_zh_CN.properties | 9
opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_zh_TW.properties | 15
opends/src/admin/messages/LastModPluginCfgDefn_de.properties | 59
opends/src/admin/messages/LogPublisherCfgDefn_ko.properties | 4
opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn.properties | 9
opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_ja.properties | 17
opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_ko.properties | 21
opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_ja.properties | 18
opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/RootDNUserCfgDefn_fr.properties | 6
opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_ko.properties | 6
opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_ja.properties | 9
opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_ko.properties | 11
opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn.properties | 25
opends/src/admin/messages/LocalDBIndexCfgDefn_es.properties | 18
opends/src/admin/messages/RootDSEBackendCfgDefn_ja.properties | 7
opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_es.properties | 5
opends/src/admin/messages/PluginRootCfgDefn_zh_CN.properties | 157
opends/src/admin/messages/LogRotationPolicyCfgDefn_zh_TW.properties | 4
opends/src/admin/messages/WorkflowElementCfgDefn.properties | 9
opends/src/admin/messages/RootDNUserCfgDefn_es.properties | 6
opends/src/admin/messages/SMTPAlertHandlerCfgDefn_zh_CN.properties | 18
opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_zh_CN.properties | 5
opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_de.properties | 5
opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_ko.properties | 8
opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_ko.properties | 6
opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_zh_CN.properties | 9
opends/src/admin/messages/VersionMonitorProviderCfgDefn_zh_TW.properties | 5
opends/src/admin/messages/WorkflowCfgDefn_de.properties | 10
opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_es.properties | 6
opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_es.properties | 5
opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_zh_CN.properties | 19
opends/src/admin/messages/ProfilerPluginCfgDefn_ja.properties | 72
opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_fr.properties | 5
opends/src/admin/messages/ErrorLogPublisherCfgDefn_fr.properties | 21
opends/src/admin/messages/BackendCfgDefn_es.properties | 16
opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_ja.properties | 20
opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_es.properties | 10
opends/src/admin/messages/TrustManagerProviderCfgDefn_fr.properties | 5
opends/src/admin/messages/WorkflowCfgDefn.properties | 10
opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_ja.properties | 6
opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_zh_CN.properties | 13
opends/src/admin/messages/SubstringMatchingRuleCfgDefn_es.properties | 6
opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_fr.properties | 16
opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_es.properties | 68
opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/SevenBitCleanPluginCfgDefn_ja.properties | 63
opends/src/admin/messages/OrderingMatchingRuleCfgDefn_ko.properties | 6
opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_ko.properties | 7
opends/src/admin/messages/MemoryBackendCfgDefn_zh_TW.properties | 16
opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn.properties | 6
opends/src/admin/messages/SynchronizationProviderCfgDefn_fr.properties | 6
opends/src/admin/messages/ProfilerPluginCfgDefn_zh_CN.properties | 72
opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_zh_TW.properties | 9
opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_de.properties | 6
opends/src/admin/messages/BackendCfgDefn_zh_CN.properties | 16
opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_ko.properties | 12
opends/src/admin/messages/DynamicGroupImplementationCfgDefn_fr.properties | 5
opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_zh_CN.properties | 8
opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_zh_CN.properties | 5
opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_ko.properties | 16
opends/src/admin/messages/PasswordValidatorCfgDefn_ko.properties | 6
opends/src/admin/messages/ConnectionHandlerCfgDefn.properties | 13
opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_ko.properties | 6
opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn.properties | 5
opends/src/admin/messages/PasswordStorageSchemeCfgDefn_fr.properties | 6
opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_zh_CN.properties | 10
opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_ko.properties | 6
opends/src/admin/messages/RootDSEBackendCfgDefn_zh_CN.properties | 7
opends/src/admin/messages/JMXAlertHandlerCfgDefn_fr.properties | 11
opends/src/admin/messages/SynchronizationProviderCfgDefn_es.properties | 6
opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_fr.properties | 68
opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_zh_TW.properties | 28
opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_ja.properties | 25
opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn.properties | 6
opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_de.properties | 6
opends/src/admin/messages/MonitorProviderCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_de.properties | 6
opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_de.properties | 10
opends/src/admin/messages/MatchingRuleCfgDefn_de.properties | 6
opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_ja.properties | 24
opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_fr.properties | 10
opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_de.properties | 6
opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_es.properties | 16
opends/src/admin/messages/FIFOEntryCacheCfgDefn_ko.properties | 12
opends/src/admin/messages/TraditionalWorkQueueCfgDefn_ja.properties | 10
opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_zh_CN.properties | 8
opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn.properties | 20
opends/src/admin/messages/WorkflowElementCfgDefn_de.properties | 9
opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_zh_TW.properties | 6
opends/src/admin/messages/ConnectionHandlerCfgDefn_ko.properties | 13
opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_zh_CN.properties | 19
opends/src/admin/messages/MonitorBackendCfgDefn_de.properties | 15
opends/src/admin/messages/TrustStoreBackendCfgDefn_ja.properties | 29
opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_ko.properties | 10
opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_fr.properties | 5
opends/src/admin/messages/LogRotationPolicyCfgDefn.properties | 4
opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_zh_CN.properties | 6
opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_zh_CN.properties | 5
opends/src/admin/messages/ExtensionCfgDefn_ja.properties | 6
opends/src/admin/messages/AccessLogPublisherCfgDefn_zh_TW.properties | 8
opends/src/admin/messages/KeyManagerProviderCfgDefn_fr.properties | 6
1,297 files changed, 23,944 insertions(+), 0 deletions(-)
diff --git a/opends/build.xml b/opends/build.xml
index d975784..33238c9 100644
--- a/opends/build.xml
+++ b/opends/build.xml
@@ -147,6 +147,10 @@
<property name="msg.package.dir" location="${classes.dir}/messages" />
<property name="msg.src.dir" location="${msg.dir}/src" />
+ <!-- Properties for L10n for generating messages. -->
+ <property name="msgl10n.prop.dir" location="src/admin/messages/" />
+
+
<!-- Properties for SNMP extension. -->
<property name="snmp.mib.dir" location="src/snmp/resource/mib" />
<property name="snmp.security.dir" location="src/snmp/resource/security" />
@@ -695,6 +699,13 @@
</copy>
</target>
+ <!-- copy the l10n message properties files (for generated messages)-->
+ <target name="copyl10nmessages">
+ <echo message="JPI"/>
+ <copy todir="${msg.package.dir}">
+ <fileset dir="${msgl10n.prop.dir}" />
+ </copy>
+ </target>
<!--
@@ -760,6 +771,7 @@
<!-- copy the message properties files -->
<antcall target="copymessages" />
+
<!-- copy the message descriptor registry file -->
<copy todir="${classes.dir}/org/opends/messages"
file="${msg.javagen.dir}/org/opends/messages/descriptors.reg" />
@@ -916,6 +928,10 @@
<!-- copy the message properties files -->
<antcall target="copymessages" />
+ <!-- copy the l10n message properties files -->
+ <antcall target="copyl10nmessages" />
+
+
<!-- copy the message descriptor registry file -->
<copy todir="${classes.dir}/org/opends/messages"
file="${msg.javagen.dir}/org/opends/messages/descriptors.reg" />
diff --git a/opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn.properties b/opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn.properties
new file mode 100644
index 0000000..7612cc0
--- /dev/null
+++ b/opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=AES Password Storage Scheme
+user-friendly-plural-name=AES Password Storage Schemes
+synopsis=The AES Password Storage Scheme provides a mechanism for encoding user passwords using the AES reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "AES".
+property.enabled.synopsis=Indicates whether the AES Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the AES Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_de.properties b/opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_de.properties
new file mode 100644
index 0000000..7612cc0
--- /dev/null
+++ b/opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=AES Password Storage Scheme
+user-friendly-plural-name=AES Password Storage Schemes
+synopsis=The AES Password Storage Scheme provides a mechanism for encoding user passwords using the AES reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "AES".
+property.enabled.synopsis=Indicates whether the AES Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the AES Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_es.properties b/opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_es.properties
new file mode 100644
index 0000000..7612cc0
--- /dev/null
+++ b/opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=AES Password Storage Scheme
+user-friendly-plural-name=AES Password Storage Schemes
+synopsis=The AES Password Storage Scheme provides a mechanism for encoding user passwords using the AES reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "AES".
+property.enabled.synopsis=Indicates whether the AES Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the AES Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_fr.properties b/opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_fr.properties
new file mode 100644
index 0000000..7612cc0
--- /dev/null
+++ b/opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=AES Password Storage Scheme
+user-friendly-plural-name=AES Password Storage Schemes
+synopsis=The AES Password Storage Scheme provides a mechanism for encoding user passwords using the AES reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "AES".
+property.enabled.synopsis=Indicates whether the AES Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the AES Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_ja.properties b/opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_ja.properties
new file mode 100644
index 0000000..7612cc0
--- /dev/null
+++ b/opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=AES Password Storage Scheme
+user-friendly-plural-name=AES Password Storage Schemes
+synopsis=The AES Password Storage Scheme provides a mechanism for encoding user passwords using the AES reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "AES".
+property.enabled.synopsis=Indicates whether the AES Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the AES Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_ko.properties b/opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_ko.properties
new file mode 100644
index 0000000..7612cc0
--- /dev/null
+++ b/opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=AES Password Storage Scheme
+user-friendly-plural-name=AES Password Storage Schemes
+synopsis=The AES Password Storage Scheme provides a mechanism for encoding user passwords using the AES reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "AES".
+property.enabled.synopsis=Indicates whether the AES Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the AES Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_zh_CN.properties b/opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..7612cc0
--- /dev/null
+++ b/opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=AES Password Storage Scheme
+user-friendly-plural-name=AES Password Storage Schemes
+synopsis=The AES Password Storage Scheme provides a mechanism for encoding user passwords using the AES reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "AES".
+property.enabled.synopsis=Indicates whether the AES Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the AES Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_zh_TW.properties b/opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..7612cc0
--- /dev/null
+++ b/opends/src/admin/messages/AESPasswordStorageSchemeCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=AES Password Storage Scheme
+user-friendly-plural-name=AES Password Storage Schemes
+synopsis=The AES Password Storage Scheme provides a mechanism for encoding user passwords using the AES reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "AES".
+property.enabled.synopsis=Indicates whether the AES Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the AES Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/AccessControlHandlerCfgDefn.properties b/opends/src/admin/messages/AccessControlHandlerCfgDefn.properties
new file mode 100644
index 0000000..dc75a18
--- /dev/null
+++ b/opends/src/admin/messages/AccessControlHandlerCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Access Control Handler
+user-friendly-plural-name=Access Control Handlers
+synopsis=Access Control Handlers manage the application-wide access control. The OpenDS access control handler is defined through an extensible interface, so that alternate implementations can be created. Only one access control handler may be active in the server at any given time.
+description=Note that OpenDS also has a privilege subsystem, which may have an impact on what clients may be allowed to do in the server. For example, any user with the bypass-acl privilege is not subject to access control checking regardless of whether the access control implementation is enabled.
+property.enabled.synopsis=Indicates whether the Access Control Handler is enabled. If set to FALSE, then no access control is enforced, and any client (including unauthenticated or anonymous clients) could be allowed to perform any operation if not subject to other restrictions, such as those enforced by the privilege subsystem.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Access Control Handler implementation.
diff --git a/opends/src/admin/messages/AccessControlHandlerCfgDefn_de.properties b/opends/src/admin/messages/AccessControlHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..dc75a18
--- /dev/null
+++ b/opends/src/admin/messages/AccessControlHandlerCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Access Control Handler
+user-friendly-plural-name=Access Control Handlers
+synopsis=Access Control Handlers manage the application-wide access control. The OpenDS access control handler is defined through an extensible interface, so that alternate implementations can be created. Only one access control handler may be active in the server at any given time.
+description=Note that OpenDS also has a privilege subsystem, which may have an impact on what clients may be allowed to do in the server. For example, any user with the bypass-acl privilege is not subject to access control checking regardless of whether the access control implementation is enabled.
+property.enabled.synopsis=Indicates whether the Access Control Handler is enabled. If set to FALSE, then no access control is enforced, and any client (including unauthenticated or anonymous clients) could be allowed to perform any operation if not subject to other restrictions, such as those enforced by the privilege subsystem.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Access Control Handler implementation.
diff --git a/opends/src/admin/messages/AccessControlHandlerCfgDefn_es.properties b/opends/src/admin/messages/AccessControlHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..dc75a18
--- /dev/null
+++ b/opends/src/admin/messages/AccessControlHandlerCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Access Control Handler
+user-friendly-plural-name=Access Control Handlers
+synopsis=Access Control Handlers manage the application-wide access control. The OpenDS access control handler is defined through an extensible interface, so that alternate implementations can be created. Only one access control handler may be active in the server at any given time.
+description=Note that OpenDS also has a privilege subsystem, which may have an impact on what clients may be allowed to do in the server. For example, any user with the bypass-acl privilege is not subject to access control checking regardless of whether the access control implementation is enabled.
+property.enabled.synopsis=Indicates whether the Access Control Handler is enabled. If set to FALSE, then no access control is enforced, and any client (including unauthenticated or anonymous clients) could be allowed to perform any operation if not subject to other restrictions, such as those enforced by the privilege subsystem.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Access Control Handler implementation.
diff --git a/opends/src/admin/messages/AccessControlHandlerCfgDefn_fr.properties b/opends/src/admin/messages/AccessControlHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..dc75a18
--- /dev/null
+++ b/opends/src/admin/messages/AccessControlHandlerCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Access Control Handler
+user-friendly-plural-name=Access Control Handlers
+synopsis=Access Control Handlers manage the application-wide access control. The OpenDS access control handler is defined through an extensible interface, so that alternate implementations can be created. Only one access control handler may be active in the server at any given time.
+description=Note that OpenDS also has a privilege subsystem, which may have an impact on what clients may be allowed to do in the server. For example, any user with the bypass-acl privilege is not subject to access control checking regardless of whether the access control implementation is enabled.
+property.enabled.synopsis=Indicates whether the Access Control Handler is enabled. If set to FALSE, then no access control is enforced, and any client (including unauthenticated or anonymous clients) could be allowed to perform any operation if not subject to other restrictions, such as those enforced by the privilege subsystem.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Access Control Handler implementation.
diff --git a/opends/src/admin/messages/AccessControlHandlerCfgDefn_ja.properties b/opends/src/admin/messages/AccessControlHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..dc75a18
--- /dev/null
+++ b/opends/src/admin/messages/AccessControlHandlerCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Access Control Handler
+user-friendly-plural-name=Access Control Handlers
+synopsis=Access Control Handlers manage the application-wide access control. The OpenDS access control handler is defined through an extensible interface, so that alternate implementations can be created. Only one access control handler may be active in the server at any given time.
+description=Note that OpenDS also has a privilege subsystem, which may have an impact on what clients may be allowed to do in the server. For example, any user with the bypass-acl privilege is not subject to access control checking regardless of whether the access control implementation is enabled.
+property.enabled.synopsis=Indicates whether the Access Control Handler is enabled. If set to FALSE, then no access control is enforced, and any client (including unauthenticated or anonymous clients) could be allowed to perform any operation if not subject to other restrictions, such as those enforced by the privilege subsystem.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Access Control Handler implementation.
diff --git a/opends/src/admin/messages/AccessControlHandlerCfgDefn_ko.properties b/opends/src/admin/messages/AccessControlHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..dc75a18
--- /dev/null
+++ b/opends/src/admin/messages/AccessControlHandlerCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Access Control Handler
+user-friendly-plural-name=Access Control Handlers
+synopsis=Access Control Handlers manage the application-wide access control. The OpenDS access control handler is defined through an extensible interface, so that alternate implementations can be created. Only one access control handler may be active in the server at any given time.
+description=Note that OpenDS also has a privilege subsystem, which may have an impact on what clients may be allowed to do in the server. For example, any user with the bypass-acl privilege is not subject to access control checking regardless of whether the access control implementation is enabled.
+property.enabled.synopsis=Indicates whether the Access Control Handler is enabled. If set to FALSE, then no access control is enforced, and any client (including unauthenticated or anonymous clients) could be allowed to perform any operation if not subject to other restrictions, such as those enforced by the privilege subsystem.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Access Control Handler implementation.
diff --git a/opends/src/admin/messages/AccessControlHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/AccessControlHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..dc75a18
--- /dev/null
+++ b/opends/src/admin/messages/AccessControlHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Access Control Handler
+user-friendly-plural-name=Access Control Handlers
+synopsis=Access Control Handlers manage the application-wide access control. The OpenDS access control handler is defined through an extensible interface, so that alternate implementations can be created. Only one access control handler may be active in the server at any given time.
+description=Note that OpenDS also has a privilege subsystem, which may have an impact on what clients may be allowed to do in the server. For example, any user with the bypass-acl privilege is not subject to access control checking regardless of whether the access control implementation is enabled.
+property.enabled.synopsis=Indicates whether the Access Control Handler is enabled. If set to FALSE, then no access control is enforced, and any client (including unauthenticated or anonymous clients) could be allowed to perform any operation if not subject to other restrictions, such as those enforced by the privilege subsystem.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Access Control Handler implementation.
diff --git a/opends/src/admin/messages/AccessControlHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/AccessControlHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..dc75a18
--- /dev/null
+++ b/opends/src/admin/messages/AccessControlHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Access Control Handler
+user-friendly-plural-name=Access Control Handlers
+synopsis=Access Control Handlers manage the application-wide access control. The OpenDS access control handler is defined through an extensible interface, so that alternate implementations can be created. Only one access control handler may be active in the server at any given time.
+description=Note that OpenDS also has a privilege subsystem, which may have an impact on what clients may be allowed to do in the server. For example, any user with the bypass-acl privilege is not subject to access control checking regardless of whether the access control implementation is enabled.
+property.enabled.synopsis=Indicates whether the Access Control Handler is enabled. If set to FALSE, then no access control is enforced, and any client (including unauthenticated or anonymous clients) could be allowed to perform any operation if not subject to other restrictions, such as those enforced by the privilege subsystem.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Access Control Handler implementation.
diff --git a/opends/src/admin/messages/AccessLogPublisherCfgDefn.properties b/opends/src/admin/messages/AccessLogPublisherCfgDefn.properties
new file mode 100644
index 0000000..14822ef
--- /dev/null
+++ b/opends/src/admin/messages/AccessLogPublisherCfgDefn.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Access Log Publisher
+user-friendly-plural-name=Access Log Publishers
+synopsis=Access Log Publishers are responsible for distributing access log messages from the access logger to a destination.
+description=Access log messages provide information about the types of operations processed by the server.
+property.enabled.synopsis=Indicates whether the Access Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Access Log Publisher implementation.
+property.suppress-internal-operations.synopsis=Indicates whether internal operations (for example, operations that are initiated by plugins) should be logged along with the operations that are requested by users.
+property.suppress-synchronization-operations.synopsis=Indicates whether access messages that are generated by synchronization operations should be suppressed.
diff --git a/opends/src/admin/messages/AccessLogPublisherCfgDefn_de.properties b/opends/src/admin/messages/AccessLogPublisherCfgDefn_de.properties
new file mode 100644
index 0000000..14822ef
--- /dev/null
+++ b/opends/src/admin/messages/AccessLogPublisherCfgDefn_de.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Access Log Publisher
+user-friendly-plural-name=Access Log Publishers
+synopsis=Access Log Publishers are responsible for distributing access log messages from the access logger to a destination.
+description=Access log messages provide information about the types of operations processed by the server.
+property.enabled.synopsis=Indicates whether the Access Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Access Log Publisher implementation.
+property.suppress-internal-operations.synopsis=Indicates whether internal operations (for example, operations that are initiated by plugins) should be logged along with the operations that are requested by users.
+property.suppress-synchronization-operations.synopsis=Indicates whether access messages that are generated by synchronization operations should be suppressed.
diff --git a/opends/src/admin/messages/AccessLogPublisherCfgDefn_es.properties b/opends/src/admin/messages/AccessLogPublisherCfgDefn_es.properties
new file mode 100644
index 0000000..14822ef
--- /dev/null
+++ b/opends/src/admin/messages/AccessLogPublisherCfgDefn_es.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Access Log Publisher
+user-friendly-plural-name=Access Log Publishers
+synopsis=Access Log Publishers are responsible for distributing access log messages from the access logger to a destination.
+description=Access log messages provide information about the types of operations processed by the server.
+property.enabled.synopsis=Indicates whether the Access Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Access Log Publisher implementation.
+property.suppress-internal-operations.synopsis=Indicates whether internal operations (for example, operations that are initiated by plugins) should be logged along with the operations that are requested by users.
+property.suppress-synchronization-operations.synopsis=Indicates whether access messages that are generated by synchronization operations should be suppressed.
diff --git a/opends/src/admin/messages/AccessLogPublisherCfgDefn_fr.properties b/opends/src/admin/messages/AccessLogPublisherCfgDefn_fr.properties
new file mode 100644
index 0000000..14822ef
--- /dev/null
+++ b/opends/src/admin/messages/AccessLogPublisherCfgDefn_fr.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Access Log Publisher
+user-friendly-plural-name=Access Log Publishers
+synopsis=Access Log Publishers are responsible for distributing access log messages from the access logger to a destination.
+description=Access log messages provide information about the types of operations processed by the server.
+property.enabled.synopsis=Indicates whether the Access Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Access Log Publisher implementation.
+property.suppress-internal-operations.synopsis=Indicates whether internal operations (for example, operations that are initiated by plugins) should be logged along with the operations that are requested by users.
+property.suppress-synchronization-operations.synopsis=Indicates whether access messages that are generated by synchronization operations should be suppressed.
diff --git a/opends/src/admin/messages/AccessLogPublisherCfgDefn_ja.properties b/opends/src/admin/messages/AccessLogPublisherCfgDefn_ja.properties
new file mode 100644
index 0000000..14822ef
--- /dev/null
+++ b/opends/src/admin/messages/AccessLogPublisherCfgDefn_ja.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Access Log Publisher
+user-friendly-plural-name=Access Log Publishers
+synopsis=Access Log Publishers are responsible for distributing access log messages from the access logger to a destination.
+description=Access log messages provide information about the types of operations processed by the server.
+property.enabled.synopsis=Indicates whether the Access Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Access Log Publisher implementation.
+property.suppress-internal-operations.synopsis=Indicates whether internal operations (for example, operations that are initiated by plugins) should be logged along with the operations that are requested by users.
+property.suppress-synchronization-operations.synopsis=Indicates whether access messages that are generated by synchronization operations should be suppressed.
diff --git a/opends/src/admin/messages/AccessLogPublisherCfgDefn_ko.properties b/opends/src/admin/messages/AccessLogPublisherCfgDefn_ko.properties
new file mode 100644
index 0000000..14822ef
--- /dev/null
+++ b/opends/src/admin/messages/AccessLogPublisherCfgDefn_ko.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Access Log Publisher
+user-friendly-plural-name=Access Log Publishers
+synopsis=Access Log Publishers are responsible for distributing access log messages from the access logger to a destination.
+description=Access log messages provide information about the types of operations processed by the server.
+property.enabled.synopsis=Indicates whether the Access Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Access Log Publisher implementation.
+property.suppress-internal-operations.synopsis=Indicates whether internal operations (for example, operations that are initiated by plugins) should be logged along with the operations that are requested by users.
+property.suppress-synchronization-operations.synopsis=Indicates whether access messages that are generated by synchronization operations should be suppressed.
diff --git a/opends/src/admin/messages/AccessLogPublisherCfgDefn_zh_CN.properties b/opends/src/admin/messages/AccessLogPublisherCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..14822ef
--- /dev/null
+++ b/opends/src/admin/messages/AccessLogPublisherCfgDefn_zh_CN.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Access Log Publisher
+user-friendly-plural-name=Access Log Publishers
+synopsis=Access Log Publishers are responsible for distributing access log messages from the access logger to a destination.
+description=Access log messages provide information about the types of operations processed by the server.
+property.enabled.synopsis=Indicates whether the Access Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Access Log Publisher implementation.
+property.suppress-internal-operations.synopsis=Indicates whether internal operations (for example, operations that are initiated by plugins) should be logged along with the operations that are requested by users.
+property.suppress-synchronization-operations.synopsis=Indicates whether access messages that are generated by synchronization operations should be suppressed.
diff --git a/opends/src/admin/messages/AccessLogPublisherCfgDefn_zh_TW.properties b/opends/src/admin/messages/AccessLogPublisherCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..14822ef
--- /dev/null
+++ b/opends/src/admin/messages/AccessLogPublisherCfgDefn_zh_TW.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Access Log Publisher
+user-friendly-plural-name=Access Log Publishers
+synopsis=Access Log Publishers are responsible for distributing access log messages from the access logger to a destination.
+description=Access log messages provide information about the types of operations processed by the server.
+property.enabled.synopsis=Indicates whether the Access Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Access Log Publisher implementation.
+property.suppress-internal-operations.synopsis=Indicates whether internal operations (for example, operations that are initiated by plugins) should be logged along with the operations that are requested by users.
+property.suppress-synchronization-operations.synopsis=Indicates whether access messages that are generated by synchronization operations should be suppressed.
diff --git a/opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn.properties b/opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn.properties
new file mode 100644
index 0000000..c8b6311
--- /dev/null
+++ b/opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Account Status Notification Handler
+user-friendly-plural-name=Account Status Notification Handlers
+synopsis=Account Status Notification Handlers are invoked to provide notification to users in some form (for example, by an email message) when the status of a user's account has changed in some way. The Account Status Notification Handler can be used to notify the user and/or administrators of the change.
+property.enabled.synopsis=Indicates whether the Account Status Notification Handler is enabled. Only enabled handlers are invoked whenever a related event occurs in the server.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Account Status Notification Handler implementation.
diff --git a/opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_de.properties b/opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..c8b6311
--- /dev/null
+++ b/opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_de.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Account Status Notification Handler
+user-friendly-plural-name=Account Status Notification Handlers
+synopsis=Account Status Notification Handlers are invoked to provide notification to users in some form (for example, by an email message) when the status of a user's account has changed in some way. The Account Status Notification Handler can be used to notify the user and/or administrators of the change.
+property.enabled.synopsis=Indicates whether the Account Status Notification Handler is enabled. Only enabled handlers are invoked whenever a related event occurs in the server.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Account Status Notification Handler implementation.
diff --git a/opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_es.properties b/opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..c8b6311
--- /dev/null
+++ b/opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_es.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Account Status Notification Handler
+user-friendly-plural-name=Account Status Notification Handlers
+synopsis=Account Status Notification Handlers are invoked to provide notification to users in some form (for example, by an email message) when the status of a user's account has changed in some way. The Account Status Notification Handler can be used to notify the user and/or administrators of the change.
+property.enabled.synopsis=Indicates whether the Account Status Notification Handler is enabled. Only enabled handlers are invoked whenever a related event occurs in the server.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Account Status Notification Handler implementation.
diff --git a/opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_fr.properties b/opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..c8b6311
--- /dev/null
+++ b/opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_fr.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Account Status Notification Handler
+user-friendly-plural-name=Account Status Notification Handlers
+synopsis=Account Status Notification Handlers are invoked to provide notification to users in some form (for example, by an email message) when the status of a user's account has changed in some way. The Account Status Notification Handler can be used to notify the user and/or administrators of the change.
+property.enabled.synopsis=Indicates whether the Account Status Notification Handler is enabled. Only enabled handlers are invoked whenever a related event occurs in the server.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Account Status Notification Handler implementation.
diff --git a/opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_ja.properties b/opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..c8b6311
--- /dev/null
+++ b/opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_ja.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Account Status Notification Handler
+user-friendly-plural-name=Account Status Notification Handlers
+synopsis=Account Status Notification Handlers are invoked to provide notification to users in some form (for example, by an email message) when the status of a user's account has changed in some way. The Account Status Notification Handler can be used to notify the user and/or administrators of the change.
+property.enabled.synopsis=Indicates whether the Account Status Notification Handler is enabled. Only enabled handlers are invoked whenever a related event occurs in the server.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Account Status Notification Handler implementation.
diff --git a/opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_ko.properties b/opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..c8b6311
--- /dev/null
+++ b/opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_ko.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Account Status Notification Handler
+user-friendly-plural-name=Account Status Notification Handlers
+synopsis=Account Status Notification Handlers are invoked to provide notification to users in some form (for example, by an email message) when the status of a user's account has changed in some way. The Account Status Notification Handler can be used to notify the user and/or administrators of the change.
+property.enabled.synopsis=Indicates whether the Account Status Notification Handler is enabled. Only enabled handlers are invoked whenever a related event occurs in the server.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Account Status Notification Handler implementation.
diff --git a/opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..c8b6311
--- /dev/null
+++ b/opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Account Status Notification Handler
+user-friendly-plural-name=Account Status Notification Handlers
+synopsis=Account Status Notification Handlers are invoked to provide notification to users in some form (for example, by an email message) when the status of a user's account has changed in some way. The Account Status Notification Handler can be used to notify the user and/or administrators of the change.
+property.enabled.synopsis=Indicates whether the Account Status Notification Handler is enabled. Only enabled handlers are invoked whenever a related event occurs in the server.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Account Status Notification Handler implementation.
diff --git a/opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..c8b6311
--- /dev/null
+++ b/opends/src/admin/messages/AccountStatusNotificationHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Account Status Notification Handler
+user-friendly-plural-name=Account Status Notification Handlers
+synopsis=Account Status Notification Handlers are invoked to provide notification to users in some form (for example, by an email message) when the status of a user's account has changed in some way. The Account Status Notification Handler can be used to notify the user and/or administrators of the change.
+property.enabled.synopsis=Indicates whether the Account Status Notification Handler is enabled. Only enabled handlers are invoked whenever a related event occurs in the server.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Account Status Notification Handler implementation.
diff --git a/opends/src/admin/messages/AdministrationConnectorCfgDefn.properties b/opends/src/admin/messages/AdministrationConnectorCfgDefn.properties
new file mode 100644
index 0000000..f098329
--- /dev/null
+++ b/opends/src/admin/messages/AdministrationConnectorCfgDefn.properties
@@ -0,0 +1,14 @@
+user-friendly-name=Administration Connector
+user-friendly-plural-name=Administration Connectors
+synopsis=The Administration Connector is used to interact with administration tools using LDAP.
+description=It is a dedicated entry point for administration.
+property.key-manager-provider.synopsis=Specifies the name of the key manager that is used with the Administration Connector .
+property.key-manager-provider.syntax.aggregation.constraint-synopsis=The referenced key manager provider must be enabled.
+property.listen-address.synopsis=Specifies the address or set of addresses on which this Administration Connector should listen for connections from LDAP clients.
+property.listen-address.description=Multiple addresses may be provided as separate values for this attribute. If no values are provided, then the Administration Connector listens on all interfaces.
+property.listen-port.synopsis=Specifies the port number on which the Administration Connector will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the Administration Connector will use when performing SSL communication.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.trust-manager-provider.synopsis=Specifies the name of the trust manager that is used with the Administration Connector .
+property.trust-manager-provider.syntax.aggregation.constraint-synopsis=The referenced trust manager provider must be enabled.
diff --git a/opends/src/admin/messages/AdministrationConnectorCfgDefn_de.properties b/opends/src/admin/messages/AdministrationConnectorCfgDefn_de.properties
new file mode 100644
index 0000000..f098329
--- /dev/null
+++ b/opends/src/admin/messages/AdministrationConnectorCfgDefn_de.properties
@@ -0,0 +1,14 @@
+user-friendly-name=Administration Connector
+user-friendly-plural-name=Administration Connectors
+synopsis=The Administration Connector is used to interact with administration tools using LDAP.
+description=It is a dedicated entry point for administration.
+property.key-manager-provider.synopsis=Specifies the name of the key manager that is used with the Administration Connector .
+property.key-manager-provider.syntax.aggregation.constraint-synopsis=The referenced key manager provider must be enabled.
+property.listen-address.synopsis=Specifies the address or set of addresses on which this Administration Connector should listen for connections from LDAP clients.
+property.listen-address.description=Multiple addresses may be provided as separate values for this attribute. If no values are provided, then the Administration Connector listens on all interfaces.
+property.listen-port.synopsis=Specifies the port number on which the Administration Connector will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the Administration Connector will use when performing SSL communication.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.trust-manager-provider.synopsis=Specifies the name of the trust manager that is used with the Administration Connector .
+property.trust-manager-provider.syntax.aggregation.constraint-synopsis=The referenced trust manager provider must be enabled.
diff --git a/opends/src/admin/messages/AdministrationConnectorCfgDefn_es.properties b/opends/src/admin/messages/AdministrationConnectorCfgDefn_es.properties
new file mode 100644
index 0000000..f098329
--- /dev/null
+++ b/opends/src/admin/messages/AdministrationConnectorCfgDefn_es.properties
@@ -0,0 +1,14 @@
+user-friendly-name=Administration Connector
+user-friendly-plural-name=Administration Connectors
+synopsis=The Administration Connector is used to interact with administration tools using LDAP.
+description=It is a dedicated entry point for administration.
+property.key-manager-provider.synopsis=Specifies the name of the key manager that is used with the Administration Connector .
+property.key-manager-provider.syntax.aggregation.constraint-synopsis=The referenced key manager provider must be enabled.
+property.listen-address.synopsis=Specifies the address or set of addresses on which this Administration Connector should listen for connections from LDAP clients.
+property.listen-address.description=Multiple addresses may be provided as separate values for this attribute. If no values are provided, then the Administration Connector listens on all interfaces.
+property.listen-port.synopsis=Specifies the port number on which the Administration Connector will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the Administration Connector will use when performing SSL communication.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.trust-manager-provider.synopsis=Specifies the name of the trust manager that is used with the Administration Connector .
+property.trust-manager-provider.syntax.aggregation.constraint-synopsis=The referenced trust manager provider must be enabled.
diff --git a/opends/src/admin/messages/AdministrationConnectorCfgDefn_fr.properties b/opends/src/admin/messages/AdministrationConnectorCfgDefn_fr.properties
new file mode 100644
index 0000000..f098329
--- /dev/null
+++ b/opends/src/admin/messages/AdministrationConnectorCfgDefn_fr.properties
@@ -0,0 +1,14 @@
+user-friendly-name=Administration Connector
+user-friendly-plural-name=Administration Connectors
+synopsis=The Administration Connector is used to interact with administration tools using LDAP.
+description=It is a dedicated entry point for administration.
+property.key-manager-provider.synopsis=Specifies the name of the key manager that is used with the Administration Connector .
+property.key-manager-provider.syntax.aggregation.constraint-synopsis=The referenced key manager provider must be enabled.
+property.listen-address.synopsis=Specifies the address or set of addresses on which this Administration Connector should listen for connections from LDAP clients.
+property.listen-address.description=Multiple addresses may be provided as separate values for this attribute. If no values are provided, then the Administration Connector listens on all interfaces.
+property.listen-port.synopsis=Specifies the port number on which the Administration Connector will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the Administration Connector will use when performing SSL communication.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.trust-manager-provider.synopsis=Specifies the name of the trust manager that is used with the Administration Connector .
+property.trust-manager-provider.syntax.aggregation.constraint-synopsis=The referenced trust manager provider must be enabled.
diff --git a/opends/src/admin/messages/AdministrationConnectorCfgDefn_ja.properties b/opends/src/admin/messages/AdministrationConnectorCfgDefn_ja.properties
new file mode 100644
index 0000000..f098329
--- /dev/null
+++ b/opends/src/admin/messages/AdministrationConnectorCfgDefn_ja.properties
@@ -0,0 +1,14 @@
+user-friendly-name=Administration Connector
+user-friendly-plural-name=Administration Connectors
+synopsis=The Administration Connector is used to interact with administration tools using LDAP.
+description=It is a dedicated entry point for administration.
+property.key-manager-provider.synopsis=Specifies the name of the key manager that is used with the Administration Connector .
+property.key-manager-provider.syntax.aggregation.constraint-synopsis=The referenced key manager provider must be enabled.
+property.listen-address.synopsis=Specifies the address or set of addresses on which this Administration Connector should listen for connections from LDAP clients.
+property.listen-address.description=Multiple addresses may be provided as separate values for this attribute. If no values are provided, then the Administration Connector listens on all interfaces.
+property.listen-port.synopsis=Specifies the port number on which the Administration Connector will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the Administration Connector will use when performing SSL communication.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.trust-manager-provider.synopsis=Specifies the name of the trust manager that is used with the Administration Connector .
+property.trust-manager-provider.syntax.aggregation.constraint-synopsis=The referenced trust manager provider must be enabled.
diff --git a/opends/src/admin/messages/AdministrationConnectorCfgDefn_ko.properties b/opends/src/admin/messages/AdministrationConnectorCfgDefn_ko.properties
new file mode 100644
index 0000000..f098329
--- /dev/null
+++ b/opends/src/admin/messages/AdministrationConnectorCfgDefn_ko.properties
@@ -0,0 +1,14 @@
+user-friendly-name=Administration Connector
+user-friendly-plural-name=Administration Connectors
+synopsis=The Administration Connector is used to interact with administration tools using LDAP.
+description=It is a dedicated entry point for administration.
+property.key-manager-provider.synopsis=Specifies the name of the key manager that is used with the Administration Connector .
+property.key-manager-provider.syntax.aggregation.constraint-synopsis=The referenced key manager provider must be enabled.
+property.listen-address.synopsis=Specifies the address or set of addresses on which this Administration Connector should listen for connections from LDAP clients.
+property.listen-address.description=Multiple addresses may be provided as separate values for this attribute. If no values are provided, then the Administration Connector listens on all interfaces.
+property.listen-port.synopsis=Specifies the port number on which the Administration Connector will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the Administration Connector will use when performing SSL communication.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.trust-manager-provider.synopsis=Specifies the name of the trust manager that is used with the Administration Connector .
+property.trust-manager-provider.syntax.aggregation.constraint-synopsis=The referenced trust manager provider must be enabled.
diff --git a/opends/src/admin/messages/AdministrationConnectorCfgDefn_zh_CN.properties b/opends/src/admin/messages/AdministrationConnectorCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..f098329
--- /dev/null
+++ b/opends/src/admin/messages/AdministrationConnectorCfgDefn_zh_CN.properties
@@ -0,0 +1,14 @@
+user-friendly-name=Administration Connector
+user-friendly-plural-name=Administration Connectors
+synopsis=The Administration Connector is used to interact with administration tools using LDAP.
+description=It is a dedicated entry point for administration.
+property.key-manager-provider.synopsis=Specifies the name of the key manager that is used with the Administration Connector .
+property.key-manager-provider.syntax.aggregation.constraint-synopsis=The referenced key manager provider must be enabled.
+property.listen-address.synopsis=Specifies the address or set of addresses on which this Administration Connector should listen for connections from LDAP clients.
+property.listen-address.description=Multiple addresses may be provided as separate values for this attribute. If no values are provided, then the Administration Connector listens on all interfaces.
+property.listen-port.synopsis=Specifies the port number on which the Administration Connector will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the Administration Connector will use when performing SSL communication.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.trust-manager-provider.synopsis=Specifies the name of the trust manager that is used with the Administration Connector .
+property.trust-manager-provider.syntax.aggregation.constraint-synopsis=The referenced trust manager provider must be enabled.
diff --git a/opends/src/admin/messages/AdministrationConnectorCfgDefn_zh_TW.properties b/opends/src/admin/messages/AdministrationConnectorCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..f098329
--- /dev/null
+++ b/opends/src/admin/messages/AdministrationConnectorCfgDefn_zh_TW.properties
@@ -0,0 +1,14 @@
+user-friendly-name=Administration Connector
+user-friendly-plural-name=Administration Connectors
+synopsis=The Administration Connector is used to interact with administration tools using LDAP.
+description=It is a dedicated entry point for administration.
+property.key-manager-provider.synopsis=Specifies the name of the key manager that is used with the Administration Connector .
+property.key-manager-provider.syntax.aggregation.constraint-synopsis=The referenced key manager provider must be enabled.
+property.listen-address.synopsis=Specifies the address or set of addresses on which this Administration Connector should listen for connections from LDAP clients.
+property.listen-address.description=Multiple addresses may be provided as separate values for this attribute. If no values are provided, then the Administration Connector listens on all interfaces.
+property.listen-port.synopsis=Specifies the port number on which the Administration Connector will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the Administration Connector will use when performing SSL communication.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.trust-manager-provider.synopsis=Specifies the name of the trust manager that is used with the Administration Connector .
+property.trust-manager-provider.syntax.aggregation.constraint-synopsis=The referenced trust manager provider must be enabled.
diff --git a/opends/src/admin/messages/AlertHandlerCfgDefn.properties b/opends/src/admin/messages/AlertHandlerCfgDefn.properties
new file mode 100644
index 0000000..4ea6c72
--- /dev/null
+++ b/opends/src/admin/messages/AlertHandlerCfgDefn.properties
@@ -0,0 +1,11 @@
+user-friendly-name=Alert Handler
+user-friendly-plural-name=Alert Handlers
+synopsis=Alert Handlers are used to notify administrators of significant problems or notable events that occur in the Directory Server.
+property.disabled-alert-type.synopsis=Specifies the names of the alert types that are disabled for this alert handler.
+property.disabled-alert-type.description=If there are any values for this attribute, then no alerts with any of the specified types are allowed. If there are no values for this attribute, then only alerts with a type included in the set of enabled alert types are allowed, or if there are no values for the enabled alert types option, then all alert types are allowed.
+property.disabled-alert-type.default-behavior.alias.synopsis=If there is a set of enabled alert types, then only alerts with one of those types are allowed. Otherwise, all alerts are allowed.
+property.enabled.synopsis=Indicates whether the Alert Handler is enabled.
+property.enabled-alert-type.synopsis=Specifies the names of the alert types that are enabled for this alert handler.
+property.enabled-alert-type.description=If there are any values for this attribute, then only alerts with one of the specified types are allowed (unless they are also included in the disabled alert types). If there are no values for this attribute, then any alert with a type not included in the list of disabled alert types is allowed.
+property.enabled-alert-type.default-behavior.alias.synopsis=All alerts with types not included in the set of disabled alert types are allowed.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Alert Handler implementation.
diff --git a/opends/src/admin/messages/AlertHandlerCfgDefn_de.properties b/opends/src/admin/messages/AlertHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..4ea6c72
--- /dev/null
+++ b/opends/src/admin/messages/AlertHandlerCfgDefn_de.properties
@@ -0,0 +1,11 @@
+user-friendly-name=Alert Handler
+user-friendly-plural-name=Alert Handlers
+synopsis=Alert Handlers are used to notify administrators of significant problems or notable events that occur in the Directory Server.
+property.disabled-alert-type.synopsis=Specifies the names of the alert types that are disabled for this alert handler.
+property.disabled-alert-type.description=If there are any values for this attribute, then no alerts with any of the specified types are allowed. If there are no values for this attribute, then only alerts with a type included in the set of enabled alert types are allowed, or if there are no values for the enabled alert types option, then all alert types are allowed.
+property.disabled-alert-type.default-behavior.alias.synopsis=If there is a set of enabled alert types, then only alerts with one of those types are allowed. Otherwise, all alerts are allowed.
+property.enabled.synopsis=Indicates whether the Alert Handler is enabled.
+property.enabled-alert-type.synopsis=Specifies the names of the alert types that are enabled for this alert handler.
+property.enabled-alert-type.description=If there are any values for this attribute, then only alerts with one of the specified types are allowed (unless they are also included in the disabled alert types). If there are no values for this attribute, then any alert with a type not included in the list of disabled alert types is allowed.
+property.enabled-alert-type.default-behavior.alias.synopsis=All alerts with types not included in the set of disabled alert types are allowed.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Alert Handler implementation.
diff --git a/opends/src/admin/messages/AlertHandlerCfgDefn_es.properties b/opends/src/admin/messages/AlertHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..4ea6c72
--- /dev/null
+++ b/opends/src/admin/messages/AlertHandlerCfgDefn_es.properties
@@ -0,0 +1,11 @@
+user-friendly-name=Alert Handler
+user-friendly-plural-name=Alert Handlers
+synopsis=Alert Handlers are used to notify administrators of significant problems or notable events that occur in the Directory Server.
+property.disabled-alert-type.synopsis=Specifies the names of the alert types that are disabled for this alert handler.
+property.disabled-alert-type.description=If there are any values for this attribute, then no alerts with any of the specified types are allowed. If there are no values for this attribute, then only alerts with a type included in the set of enabled alert types are allowed, or if there are no values for the enabled alert types option, then all alert types are allowed.
+property.disabled-alert-type.default-behavior.alias.synopsis=If there is a set of enabled alert types, then only alerts with one of those types are allowed. Otherwise, all alerts are allowed.
+property.enabled.synopsis=Indicates whether the Alert Handler is enabled.
+property.enabled-alert-type.synopsis=Specifies the names of the alert types that are enabled for this alert handler.
+property.enabled-alert-type.description=If there are any values for this attribute, then only alerts with one of the specified types are allowed (unless they are also included in the disabled alert types). If there are no values for this attribute, then any alert with a type not included in the list of disabled alert types is allowed.
+property.enabled-alert-type.default-behavior.alias.synopsis=All alerts with types not included in the set of disabled alert types are allowed.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Alert Handler implementation.
diff --git a/opends/src/admin/messages/AlertHandlerCfgDefn_fr.properties b/opends/src/admin/messages/AlertHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..4ea6c72
--- /dev/null
+++ b/opends/src/admin/messages/AlertHandlerCfgDefn_fr.properties
@@ -0,0 +1,11 @@
+user-friendly-name=Alert Handler
+user-friendly-plural-name=Alert Handlers
+synopsis=Alert Handlers are used to notify administrators of significant problems or notable events that occur in the Directory Server.
+property.disabled-alert-type.synopsis=Specifies the names of the alert types that are disabled for this alert handler.
+property.disabled-alert-type.description=If there are any values for this attribute, then no alerts with any of the specified types are allowed. If there are no values for this attribute, then only alerts with a type included in the set of enabled alert types are allowed, or if there are no values for the enabled alert types option, then all alert types are allowed.
+property.disabled-alert-type.default-behavior.alias.synopsis=If there is a set of enabled alert types, then only alerts with one of those types are allowed. Otherwise, all alerts are allowed.
+property.enabled.synopsis=Indicates whether the Alert Handler is enabled.
+property.enabled-alert-type.synopsis=Specifies the names of the alert types that are enabled for this alert handler.
+property.enabled-alert-type.description=If there are any values for this attribute, then only alerts with one of the specified types are allowed (unless they are also included in the disabled alert types). If there are no values for this attribute, then any alert with a type not included in the list of disabled alert types is allowed.
+property.enabled-alert-type.default-behavior.alias.synopsis=All alerts with types not included in the set of disabled alert types are allowed.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Alert Handler implementation.
diff --git a/opends/src/admin/messages/AlertHandlerCfgDefn_ja.properties b/opends/src/admin/messages/AlertHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..4ea6c72
--- /dev/null
+++ b/opends/src/admin/messages/AlertHandlerCfgDefn_ja.properties
@@ -0,0 +1,11 @@
+user-friendly-name=Alert Handler
+user-friendly-plural-name=Alert Handlers
+synopsis=Alert Handlers are used to notify administrators of significant problems or notable events that occur in the Directory Server.
+property.disabled-alert-type.synopsis=Specifies the names of the alert types that are disabled for this alert handler.
+property.disabled-alert-type.description=If there are any values for this attribute, then no alerts with any of the specified types are allowed. If there are no values for this attribute, then only alerts with a type included in the set of enabled alert types are allowed, or if there are no values for the enabled alert types option, then all alert types are allowed.
+property.disabled-alert-type.default-behavior.alias.synopsis=If there is a set of enabled alert types, then only alerts with one of those types are allowed. Otherwise, all alerts are allowed.
+property.enabled.synopsis=Indicates whether the Alert Handler is enabled.
+property.enabled-alert-type.synopsis=Specifies the names of the alert types that are enabled for this alert handler.
+property.enabled-alert-type.description=If there are any values for this attribute, then only alerts with one of the specified types are allowed (unless they are also included in the disabled alert types). If there are no values for this attribute, then any alert with a type not included in the list of disabled alert types is allowed.
+property.enabled-alert-type.default-behavior.alias.synopsis=All alerts with types not included in the set of disabled alert types are allowed.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Alert Handler implementation.
diff --git a/opends/src/admin/messages/AlertHandlerCfgDefn_ko.properties b/opends/src/admin/messages/AlertHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..4ea6c72
--- /dev/null
+++ b/opends/src/admin/messages/AlertHandlerCfgDefn_ko.properties
@@ -0,0 +1,11 @@
+user-friendly-name=Alert Handler
+user-friendly-plural-name=Alert Handlers
+synopsis=Alert Handlers are used to notify administrators of significant problems or notable events that occur in the Directory Server.
+property.disabled-alert-type.synopsis=Specifies the names of the alert types that are disabled for this alert handler.
+property.disabled-alert-type.description=If there are any values for this attribute, then no alerts with any of the specified types are allowed. If there are no values for this attribute, then only alerts with a type included in the set of enabled alert types are allowed, or if there are no values for the enabled alert types option, then all alert types are allowed.
+property.disabled-alert-type.default-behavior.alias.synopsis=If there is a set of enabled alert types, then only alerts with one of those types are allowed. Otherwise, all alerts are allowed.
+property.enabled.synopsis=Indicates whether the Alert Handler is enabled.
+property.enabled-alert-type.synopsis=Specifies the names of the alert types that are enabled for this alert handler.
+property.enabled-alert-type.description=If there are any values for this attribute, then only alerts with one of the specified types are allowed (unless they are also included in the disabled alert types). If there are no values for this attribute, then any alert with a type not included in the list of disabled alert types is allowed.
+property.enabled-alert-type.default-behavior.alias.synopsis=All alerts with types not included in the set of disabled alert types are allowed.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Alert Handler implementation.
diff --git a/opends/src/admin/messages/AlertHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/AlertHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..4ea6c72
--- /dev/null
+++ b/opends/src/admin/messages/AlertHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,11 @@
+user-friendly-name=Alert Handler
+user-friendly-plural-name=Alert Handlers
+synopsis=Alert Handlers are used to notify administrators of significant problems or notable events that occur in the Directory Server.
+property.disabled-alert-type.synopsis=Specifies the names of the alert types that are disabled for this alert handler.
+property.disabled-alert-type.description=If there are any values for this attribute, then no alerts with any of the specified types are allowed. If there are no values for this attribute, then only alerts with a type included in the set of enabled alert types are allowed, or if there are no values for the enabled alert types option, then all alert types are allowed.
+property.disabled-alert-type.default-behavior.alias.synopsis=If there is a set of enabled alert types, then only alerts with one of those types are allowed. Otherwise, all alerts are allowed.
+property.enabled.synopsis=Indicates whether the Alert Handler is enabled.
+property.enabled-alert-type.synopsis=Specifies the names of the alert types that are enabled for this alert handler.
+property.enabled-alert-type.description=If there are any values for this attribute, then only alerts with one of the specified types are allowed (unless they are also included in the disabled alert types). If there are no values for this attribute, then any alert with a type not included in the list of disabled alert types is allowed.
+property.enabled-alert-type.default-behavior.alias.synopsis=All alerts with types not included in the set of disabled alert types are allowed.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Alert Handler implementation.
diff --git a/opends/src/admin/messages/AlertHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/AlertHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..4ea6c72
--- /dev/null
+++ b/opends/src/admin/messages/AlertHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,11 @@
+user-friendly-name=Alert Handler
+user-friendly-plural-name=Alert Handlers
+synopsis=Alert Handlers are used to notify administrators of significant problems or notable events that occur in the Directory Server.
+property.disabled-alert-type.synopsis=Specifies the names of the alert types that are disabled for this alert handler.
+property.disabled-alert-type.description=If there are any values for this attribute, then no alerts with any of the specified types are allowed. If there are no values for this attribute, then only alerts with a type included in the set of enabled alert types are allowed, or if there are no values for the enabled alert types option, then all alert types are allowed.
+property.disabled-alert-type.default-behavior.alias.synopsis=If there is a set of enabled alert types, then only alerts with one of those types are allowed. Otherwise, all alerts are allowed.
+property.enabled.synopsis=Indicates whether the Alert Handler is enabled.
+property.enabled-alert-type.synopsis=Specifies the names of the alert types that are enabled for this alert handler.
+property.enabled-alert-type.description=If there are any values for this attribute, then only alerts with one of the specified types are allowed (unless they are also included in the disabled alert types). If there are no values for this attribute, then any alert with a type not included in the list of disabled alert types is allowed.
+property.enabled-alert-type.default-behavior.alias.synopsis=All alerts with types not included in the set of disabled alert types are allowed.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Alert Handler implementation.
diff --git a/opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn.properties b/opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn.properties
new file mode 100644
index 0000000..a505b95
--- /dev/null
+++ b/opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Anonymous SASL Mechanism Handler
+user-friendly-plural-name=Anonymous SASL Mechanism Handlers
+synopsis=The ANONYMOUS SASL mechanism provides the ability for clients to perform an anonymous bind using a SASL mechanism.
+description=The only real benefit that this provides over a normal anonymous bind (that is, using simple authentication with no password) is that the ANONYMOUS SASL mechanism also allows the client to include a trace string in the request. This trace string can help identify the application that performed the bind (although since there is no authentication, there is no assurance that some other client did not spoof that trace string).
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_de.properties b/opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..a505b95
--- /dev/null
+++ b/opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Anonymous SASL Mechanism Handler
+user-friendly-plural-name=Anonymous SASL Mechanism Handlers
+synopsis=The ANONYMOUS SASL mechanism provides the ability for clients to perform an anonymous bind using a SASL mechanism.
+description=The only real benefit that this provides over a normal anonymous bind (that is, using simple authentication with no password) is that the ANONYMOUS SASL mechanism also allows the client to include a trace string in the request. This trace string can help identify the application that performed the bind (although since there is no authentication, there is no assurance that some other client did not spoof that trace string).
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_es.properties b/opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..a505b95
--- /dev/null
+++ b/opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Anonymous SASL Mechanism Handler
+user-friendly-plural-name=Anonymous SASL Mechanism Handlers
+synopsis=The ANONYMOUS SASL mechanism provides the ability for clients to perform an anonymous bind using a SASL mechanism.
+description=The only real benefit that this provides over a normal anonymous bind (that is, using simple authentication with no password) is that the ANONYMOUS SASL mechanism also allows the client to include a trace string in the request. This trace string can help identify the application that performed the bind (although since there is no authentication, there is no assurance that some other client did not spoof that trace string).
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_fr.properties b/opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..a505b95
--- /dev/null
+++ b/opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Anonymous SASL Mechanism Handler
+user-friendly-plural-name=Anonymous SASL Mechanism Handlers
+synopsis=The ANONYMOUS SASL mechanism provides the ability for clients to perform an anonymous bind using a SASL mechanism.
+description=The only real benefit that this provides over a normal anonymous bind (that is, using simple authentication with no password) is that the ANONYMOUS SASL mechanism also allows the client to include a trace string in the request. This trace string can help identify the application that performed the bind (although since there is no authentication, there is no assurance that some other client did not spoof that trace string).
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_ja.properties b/opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..a505b95
--- /dev/null
+++ b/opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Anonymous SASL Mechanism Handler
+user-friendly-plural-name=Anonymous SASL Mechanism Handlers
+synopsis=The ANONYMOUS SASL mechanism provides the ability for clients to perform an anonymous bind using a SASL mechanism.
+description=The only real benefit that this provides over a normal anonymous bind (that is, using simple authentication with no password) is that the ANONYMOUS SASL mechanism also allows the client to include a trace string in the request. This trace string can help identify the application that performed the bind (although since there is no authentication, there is no assurance that some other client did not spoof that trace string).
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_ko.properties b/opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..a505b95
--- /dev/null
+++ b/opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Anonymous SASL Mechanism Handler
+user-friendly-plural-name=Anonymous SASL Mechanism Handlers
+synopsis=The ANONYMOUS SASL mechanism provides the ability for clients to perform an anonymous bind using a SASL mechanism.
+description=The only real benefit that this provides over a normal anonymous bind (that is, using simple authentication with no password) is that the ANONYMOUS SASL mechanism also allows the client to include a trace string in the request. This trace string can help identify the application that performed the bind (although since there is no authentication, there is no assurance that some other client did not spoof that trace string).
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..a505b95
--- /dev/null
+++ b/opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Anonymous SASL Mechanism Handler
+user-friendly-plural-name=Anonymous SASL Mechanism Handlers
+synopsis=The ANONYMOUS SASL mechanism provides the ability for clients to perform an anonymous bind using a SASL mechanism.
+description=The only real benefit that this provides over a normal anonymous bind (that is, using simple authentication with no password) is that the ANONYMOUS SASL mechanism also allows the client to include a trace string in the request. This trace string can help identify the application that performed the bind (although since there is no authentication, there is no assurance that some other client did not spoof that trace string).
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..a505b95
--- /dev/null
+++ b/opends/src/admin/messages/AnonymousSASLMechanismHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Anonymous SASL Mechanism Handler
+user-friendly-plural-name=Anonymous SASL Mechanism Handlers
+synopsis=The ANONYMOUS SASL mechanism provides the ability for clients to perform an anonymous bind using a SASL mechanism.
+description=The only real benefit that this provides over a normal anonymous bind (that is, using simple authentication with no password) is that the ANONYMOUS SASL mechanism also allows the client to include a trace string in the request. This trace string can help identify the application that performed the bind (although since there is no authentication, there is no assurance that some other client did not spoof that trace string).
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/ApproximateMatchingRuleCfgDefn.properties b/opends/src/admin/messages/ApproximateMatchingRuleCfgDefn.properties
new file mode 100644
index 0000000..3382116
--- /dev/null
+++ b/opends/src/admin/messages/ApproximateMatchingRuleCfgDefn.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Approximate Matching Rule
+user-friendly-plural-name=Approximate Matching Rules
+synopsis=Approximate Matching Rules define a set of rules for performing approximate matching operations against assertion values. In many cases, approximate matching is based on a "sounds like" operation.
+property.enabled.synopsis=Indicates whether the Approximate Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Approximate Matching Rule implementation.
diff --git a/opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_de.properties b/opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_de.properties
new file mode 100644
index 0000000..3382116
--- /dev/null
+++ b/opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_de.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Approximate Matching Rule
+user-friendly-plural-name=Approximate Matching Rules
+synopsis=Approximate Matching Rules define a set of rules for performing approximate matching operations against assertion values. In many cases, approximate matching is based on a "sounds like" operation.
+property.enabled.synopsis=Indicates whether the Approximate Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Approximate Matching Rule implementation.
diff --git a/opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_es.properties b/opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_es.properties
new file mode 100644
index 0000000..3382116
--- /dev/null
+++ b/opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_es.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Approximate Matching Rule
+user-friendly-plural-name=Approximate Matching Rules
+synopsis=Approximate Matching Rules define a set of rules for performing approximate matching operations against assertion values. In many cases, approximate matching is based on a "sounds like" operation.
+property.enabled.synopsis=Indicates whether the Approximate Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Approximate Matching Rule implementation.
diff --git a/opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_fr.properties b/opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_fr.properties
new file mode 100644
index 0000000..3382116
--- /dev/null
+++ b/opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_fr.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Approximate Matching Rule
+user-friendly-plural-name=Approximate Matching Rules
+synopsis=Approximate Matching Rules define a set of rules for performing approximate matching operations against assertion values. In many cases, approximate matching is based on a "sounds like" operation.
+property.enabled.synopsis=Indicates whether the Approximate Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Approximate Matching Rule implementation.
diff --git a/opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_ja.properties b/opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_ja.properties
new file mode 100644
index 0000000..3382116
--- /dev/null
+++ b/opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_ja.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Approximate Matching Rule
+user-friendly-plural-name=Approximate Matching Rules
+synopsis=Approximate Matching Rules define a set of rules for performing approximate matching operations against assertion values. In many cases, approximate matching is based on a "sounds like" operation.
+property.enabled.synopsis=Indicates whether the Approximate Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Approximate Matching Rule implementation.
diff --git a/opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_ko.properties b/opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_ko.properties
new file mode 100644
index 0000000..3382116
--- /dev/null
+++ b/opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_ko.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Approximate Matching Rule
+user-friendly-plural-name=Approximate Matching Rules
+synopsis=Approximate Matching Rules define a set of rules for performing approximate matching operations against assertion values. In many cases, approximate matching is based on a "sounds like" operation.
+property.enabled.synopsis=Indicates whether the Approximate Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Approximate Matching Rule implementation.
diff --git a/opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_zh_CN.properties b/opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..3382116
--- /dev/null
+++ b/opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_zh_CN.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Approximate Matching Rule
+user-friendly-plural-name=Approximate Matching Rules
+synopsis=Approximate Matching Rules define a set of rules for performing approximate matching operations against assertion values. In many cases, approximate matching is based on a "sounds like" operation.
+property.enabled.synopsis=Indicates whether the Approximate Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Approximate Matching Rule implementation.
diff --git a/opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_zh_TW.properties b/opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..3382116
--- /dev/null
+++ b/opends/src/admin/messages/ApproximateMatchingRuleCfgDefn_zh_TW.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Approximate Matching Rule
+user-friendly-plural-name=Approximate Matching Rules
+synopsis=Approximate Matching Rules define a set of rules for performing approximate matching operations against assertion values. In many cases, approximate matching is based on a "sounds like" operation.
+property.enabled.synopsis=Indicates whether the Approximate Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Approximate Matching Rule implementation.
diff --git a/opends/src/admin/messages/AttributeSyntaxCfgDefn.properties b/opends/src/admin/messages/AttributeSyntaxCfgDefn.properties
new file mode 100644
index 0000000..389609f
--- /dev/null
+++ b/opends/src/admin/messages/AttributeSyntaxCfgDefn.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Attribute Syntax
+user-friendly-plural-name=Attribute Syntaxes
+synopsis=Attribute Syntaxes define the type of data that may be stored in an attribute with that syntax. A syntax is generally associated with a set of matching rules that indicate how to perform matching operations against values of that syntax.
+property.enabled.synopsis=Indicates whether the Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Attribute Syntax implementation.
diff --git a/opends/src/admin/messages/AttributeSyntaxCfgDefn_de.properties b/opends/src/admin/messages/AttributeSyntaxCfgDefn_de.properties
new file mode 100644
index 0000000..389609f
--- /dev/null
+++ b/opends/src/admin/messages/AttributeSyntaxCfgDefn_de.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Attribute Syntax
+user-friendly-plural-name=Attribute Syntaxes
+synopsis=Attribute Syntaxes define the type of data that may be stored in an attribute with that syntax. A syntax is generally associated with a set of matching rules that indicate how to perform matching operations against values of that syntax.
+property.enabled.synopsis=Indicates whether the Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Attribute Syntax implementation.
diff --git a/opends/src/admin/messages/AttributeSyntaxCfgDefn_es.properties b/opends/src/admin/messages/AttributeSyntaxCfgDefn_es.properties
new file mode 100644
index 0000000..389609f
--- /dev/null
+++ b/opends/src/admin/messages/AttributeSyntaxCfgDefn_es.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Attribute Syntax
+user-friendly-plural-name=Attribute Syntaxes
+synopsis=Attribute Syntaxes define the type of data that may be stored in an attribute with that syntax. A syntax is generally associated with a set of matching rules that indicate how to perform matching operations against values of that syntax.
+property.enabled.synopsis=Indicates whether the Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Attribute Syntax implementation.
diff --git a/opends/src/admin/messages/AttributeSyntaxCfgDefn_fr.properties b/opends/src/admin/messages/AttributeSyntaxCfgDefn_fr.properties
new file mode 100644
index 0000000..389609f
--- /dev/null
+++ b/opends/src/admin/messages/AttributeSyntaxCfgDefn_fr.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Attribute Syntax
+user-friendly-plural-name=Attribute Syntaxes
+synopsis=Attribute Syntaxes define the type of data that may be stored in an attribute with that syntax. A syntax is generally associated with a set of matching rules that indicate how to perform matching operations against values of that syntax.
+property.enabled.synopsis=Indicates whether the Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Attribute Syntax implementation.
diff --git a/opends/src/admin/messages/AttributeSyntaxCfgDefn_ja.properties b/opends/src/admin/messages/AttributeSyntaxCfgDefn_ja.properties
new file mode 100644
index 0000000..389609f
--- /dev/null
+++ b/opends/src/admin/messages/AttributeSyntaxCfgDefn_ja.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Attribute Syntax
+user-friendly-plural-name=Attribute Syntaxes
+synopsis=Attribute Syntaxes define the type of data that may be stored in an attribute with that syntax. A syntax is generally associated with a set of matching rules that indicate how to perform matching operations against values of that syntax.
+property.enabled.synopsis=Indicates whether the Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Attribute Syntax implementation.
diff --git a/opends/src/admin/messages/AttributeSyntaxCfgDefn_ko.properties b/opends/src/admin/messages/AttributeSyntaxCfgDefn_ko.properties
new file mode 100644
index 0000000..389609f
--- /dev/null
+++ b/opends/src/admin/messages/AttributeSyntaxCfgDefn_ko.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Attribute Syntax
+user-friendly-plural-name=Attribute Syntaxes
+synopsis=Attribute Syntaxes define the type of data that may be stored in an attribute with that syntax. A syntax is generally associated with a set of matching rules that indicate how to perform matching operations against values of that syntax.
+property.enabled.synopsis=Indicates whether the Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Attribute Syntax implementation.
diff --git a/opends/src/admin/messages/AttributeSyntaxCfgDefn_zh_CN.properties b/opends/src/admin/messages/AttributeSyntaxCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..389609f
--- /dev/null
+++ b/opends/src/admin/messages/AttributeSyntaxCfgDefn_zh_CN.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Attribute Syntax
+user-friendly-plural-name=Attribute Syntaxes
+synopsis=Attribute Syntaxes define the type of data that may be stored in an attribute with that syntax. A syntax is generally associated with a set of matching rules that indicate how to perform matching operations against values of that syntax.
+property.enabled.synopsis=Indicates whether the Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Attribute Syntax implementation.
diff --git a/opends/src/admin/messages/AttributeSyntaxCfgDefn_zh_TW.properties b/opends/src/admin/messages/AttributeSyntaxCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..389609f
--- /dev/null
+++ b/opends/src/admin/messages/AttributeSyntaxCfgDefn_zh_TW.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Attribute Syntax
+user-friendly-plural-name=Attribute Syntaxes
+synopsis=Attribute Syntaxes define the type of data that may be stored in an attribute with that syntax. A syntax is generally associated with a set of matching rules that indicate how to perform matching operations against values of that syntax.
+property.enabled.synopsis=Indicates whether the Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Attribute Syntax implementation.
diff --git a/opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn.properties b/opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn.properties
new file mode 100644
index 0000000..ac8e152
--- /dev/null
+++ b/opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn.properties
@@ -0,0 +1,7 @@
+user-friendly-name=Attribute Type Description Attribute Syntax
+user-friendly-plural-name=Attribute Type Description Attribute Syntaxes
+synopsis=Attribute Type Description Attribute Syntaxes describe the format of the directory schema attribute type definitions.
+property.enabled.synopsis=Indicates whether the Attribute Type Description Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Attribute Type Description Attribute Syntax implementation.
+property.strip-syntax-min-upper-bound.synopsis=Indicates whether the suggested minimum upper bound appended to an attribute's syntax OID in it's schema definition Attribute Type Description is stripped off.
+property.strip-syntax-min-upper-bound.description=When retrieving the server's schema, some APIs (JNDI) fail in their syntax lookup methods, because they do not parse this value correctly. This configuration option allows the server to be configured to provide schema definitions these APIs can parse correctly.
diff --git a/opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_de.properties b/opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_de.properties
new file mode 100644
index 0000000..ac8e152
--- /dev/null
+++ b/opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_de.properties
@@ -0,0 +1,7 @@
+user-friendly-name=Attribute Type Description Attribute Syntax
+user-friendly-plural-name=Attribute Type Description Attribute Syntaxes
+synopsis=Attribute Type Description Attribute Syntaxes describe the format of the directory schema attribute type definitions.
+property.enabled.synopsis=Indicates whether the Attribute Type Description Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Attribute Type Description Attribute Syntax implementation.
+property.strip-syntax-min-upper-bound.synopsis=Indicates whether the suggested minimum upper bound appended to an attribute's syntax OID in it's schema definition Attribute Type Description is stripped off.
+property.strip-syntax-min-upper-bound.description=When retrieving the server's schema, some APIs (JNDI) fail in their syntax lookup methods, because they do not parse this value correctly. This configuration option allows the server to be configured to provide schema definitions these APIs can parse correctly.
diff --git a/opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_es.properties b/opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_es.properties
new file mode 100644
index 0000000..ac8e152
--- /dev/null
+++ b/opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_es.properties
@@ -0,0 +1,7 @@
+user-friendly-name=Attribute Type Description Attribute Syntax
+user-friendly-plural-name=Attribute Type Description Attribute Syntaxes
+synopsis=Attribute Type Description Attribute Syntaxes describe the format of the directory schema attribute type definitions.
+property.enabled.synopsis=Indicates whether the Attribute Type Description Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Attribute Type Description Attribute Syntax implementation.
+property.strip-syntax-min-upper-bound.synopsis=Indicates whether the suggested minimum upper bound appended to an attribute's syntax OID in it's schema definition Attribute Type Description is stripped off.
+property.strip-syntax-min-upper-bound.description=When retrieving the server's schema, some APIs (JNDI) fail in their syntax lookup methods, because they do not parse this value correctly. This configuration option allows the server to be configured to provide schema definitions these APIs can parse correctly.
diff --git a/opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_fr.properties b/opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_fr.properties
new file mode 100644
index 0000000..ac8e152
--- /dev/null
+++ b/opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_fr.properties
@@ -0,0 +1,7 @@
+user-friendly-name=Attribute Type Description Attribute Syntax
+user-friendly-plural-name=Attribute Type Description Attribute Syntaxes
+synopsis=Attribute Type Description Attribute Syntaxes describe the format of the directory schema attribute type definitions.
+property.enabled.synopsis=Indicates whether the Attribute Type Description Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Attribute Type Description Attribute Syntax implementation.
+property.strip-syntax-min-upper-bound.synopsis=Indicates whether the suggested minimum upper bound appended to an attribute's syntax OID in it's schema definition Attribute Type Description is stripped off.
+property.strip-syntax-min-upper-bound.description=When retrieving the server's schema, some APIs (JNDI) fail in their syntax lookup methods, because they do not parse this value correctly. This configuration option allows the server to be configured to provide schema definitions these APIs can parse correctly.
diff --git a/opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_ja.properties b/opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_ja.properties
new file mode 100644
index 0000000..ac8e152
--- /dev/null
+++ b/opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_ja.properties
@@ -0,0 +1,7 @@
+user-friendly-name=Attribute Type Description Attribute Syntax
+user-friendly-plural-name=Attribute Type Description Attribute Syntaxes
+synopsis=Attribute Type Description Attribute Syntaxes describe the format of the directory schema attribute type definitions.
+property.enabled.synopsis=Indicates whether the Attribute Type Description Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Attribute Type Description Attribute Syntax implementation.
+property.strip-syntax-min-upper-bound.synopsis=Indicates whether the suggested minimum upper bound appended to an attribute's syntax OID in it's schema definition Attribute Type Description is stripped off.
+property.strip-syntax-min-upper-bound.description=When retrieving the server's schema, some APIs (JNDI) fail in their syntax lookup methods, because they do not parse this value correctly. This configuration option allows the server to be configured to provide schema definitions these APIs can parse correctly.
diff --git a/opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_ko.properties b/opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_ko.properties
new file mode 100644
index 0000000..ac8e152
--- /dev/null
+++ b/opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_ko.properties
@@ -0,0 +1,7 @@
+user-friendly-name=Attribute Type Description Attribute Syntax
+user-friendly-plural-name=Attribute Type Description Attribute Syntaxes
+synopsis=Attribute Type Description Attribute Syntaxes describe the format of the directory schema attribute type definitions.
+property.enabled.synopsis=Indicates whether the Attribute Type Description Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Attribute Type Description Attribute Syntax implementation.
+property.strip-syntax-min-upper-bound.synopsis=Indicates whether the suggested minimum upper bound appended to an attribute's syntax OID in it's schema definition Attribute Type Description is stripped off.
+property.strip-syntax-min-upper-bound.description=When retrieving the server's schema, some APIs (JNDI) fail in their syntax lookup methods, because they do not parse this value correctly. This configuration option allows the server to be configured to provide schema definitions these APIs can parse correctly.
diff --git a/opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_zh_CN.properties b/opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..ac8e152
--- /dev/null
+++ b/opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_zh_CN.properties
@@ -0,0 +1,7 @@
+user-friendly-name=Attribute Type Description Attribute Syntax
+user-friendly-plural-name=Attribute Type Description Attribute Syntaxes
+synopsis=Attribute Type Description Attribute Syntaxes describe the format of the directory schema attribute type definitions.
+property.enabled.synopsis=Indicates whether the Attribute Type Description Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Attribute Type Description Attribute Syntax implementation.
+property.strip-syntax-min-upper-bound.synopsis=Indicates whether the suggested minimum upper bound appended to an attribute's syntax OID in it's schema definition Attribute Type Description is stripped off.
+property.strip-syntax-min-upper-bound.description=When retrieving the server's schema, some APIs (JNDI) fail in their syntax lookup methods, because they do not parse this value correctly. This configuration option allows the server to be configured to provide schema definitions these APIs can parse correctly.
diff --git a/opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_zh_TW.properties b/opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..ac8e152
--- /dev/null
+++ b/opends/src/admin/messages/AttributeTypeDescriptionAttributeSyntaxCfgDefn_zh_TW.properties
@@ -0,0 +1,7 @@
+user-friendly-name=Attribute Type Description Attribute Syntax
+user-friendly-plural-name=Attribute Type Description Attribute Syntaxes
+synopsis=Attribute Type Description Attribute Syntaxes describe the format of the directory schema attribute type definitions.
+property.enabled.synopsis=Indicates whether the Attribute Type Description Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Attribute Type Description Attribute Syntax implementation.
+property.strip-syntax-min-upper-bound.synopsis=Indicates whether the suggested minimum upper bound appended to an attribute's syntax OID in it's schema definition Attribute Type Description is stripped off.
+property.strip-syntax-min-upper-bound.description=When retrieving the server's schema, some APIs (JNDI) fail in their syntax lookup methods, because they do not parse this value correctly. This configuration option allows the server to be configured to provide schema definitions these APIs can parse correctly.
diff --git a/opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn.properties b/opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn.properties
new file mode 100644
index 0000000..3bfdab5
--- /dev/null
+++ b/opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Attribute Value Password Validator
+user-friendly-plural-name=Attribute Value Password Validators
+synopsis=The Attribute Value Password Validator attempts to determine whether a proposed password is acceptable for use by determining whether that password is contained in any attribute within the user's entry.
+description=It can be configured to look in all attributes or in a specified subset of attributes.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.match-attribute.synopsis=Specifies the name(s) of the attribute(s) whose values should be checked to determine whether they match the provided password. If no values are provided, then the server checks if the proposed password matches the value of any attribute in the user's entry.
+property.match-attribute.default-behavior.alias.synopsis=All attributes in the user entry will be checked.
+property.test-reversed-password.synopsis=Indicates whether this password validator should test the reversed value of the provided password as well as the order in which it was given.
diff --git a/opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_de.properties b/opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_de.properties
new file mode 100644
index 0000000..3bfdab5
--- /dev/null
+++ b/opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_de.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Attribute Value Password Validator
+user-friendly-plural-name=Attribute Value Password Validators
+synopsis=The Attribute Value Password Validator attempts to determine whether a proposed password is acceptable for use by determining whether that password is contained in any attribute within the user's entry.
+description=It can be configured to look in all attributes or in a specified subset of attributes.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.match-attribute.synopsis=Specifies the name(s) of the attribute(s) whose values should be checked to determine whether they match the provided password. If no values are provided, then the server checks if the proposed password matches the value of any attribute in the user's entry.
+property.match-attribute.default-behavior.alias.synopsis=All attributes in the user entry will be checked.
+property.test-reversed-password.synopsis=Indicates whether this password validator should test the reversed value of the provided password as well as the order in which it was given.
diff --git a/opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_es.properties b/opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_es.properties
new file mode 100644
index 0000000..3bfdab5
--- /dev/null
+++ b/opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_es.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Attribute Value Password Validator
+user-friendly-plural-name=Attribute Value Password Validators
+synopsis=The Attribute Value Password Validator attempts to determine whether a proposed password is acceptable for use by determining whether that password is contained in any attribute within the user's entry.
+description=It can be configured to look in all attributes or in a specified subset of attributes.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.match-attribute.synopsis=Specifies the name(s) of the attribute(s) whose values should be checked to determine whether they match the provided password. If no values are provided, then the server checks if the proposed password matches the value of any attribute in the user's entry.
+property.match-attribute.default-behavior.alias.synopsis=All attributes in the user entry will be checked.
+property.test-reversed-password.synopsis=Indicates whether this password validator should test the reversed value of the provided password as well as the order in which it was given.
diff --git a/opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_fr.properties b/opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_fr.properties
new file mode 100644
index 0000000..3bfdab5
--- /dev/null
+++ b/opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_fr.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Attribute Value Password Validator
+user-friendly-plural-name=Attribute Value Password Validators
+synopsis=The Attribute Value Password Validator attempts to determine whether a proposed password is acceptable for use by determining whether that password is contained in any attribute within the user's entry.
+description=It can be configured to look in all attributes or in a specified subset of attributes.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.match-attribute.synopsis=Specifies the name(s) of the attribute(s) whose values should be checked to determine whether they match the provided password. If no values are provided, then the server checks if the proposed password matches the value of any attribute in the user's entry.
+property.match-attribute.default-behavior.alias.synopsis=All attributes in the user entry will be checked.
+property.test-reversed-password.synopsis=Indicates whether this password validator should test the reversed value of the provided password as well as the order in which it was given.
diff --git a/opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_ja.properties b/opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_ja.properties
new file mode 100644
index 0000000..3bfdab5
--- /dev/null
+++ b/opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_ja.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Attribute Value Password Validator
+user-friendly-plural-name=Attribute Value Password Validators
+synopsis=The Attribute Value Password Validator attempts to determine whether a proposed password is acceptable for use by determining whether that password is contained in any attribute within the user's entry.
+description=It can be configured to look in all attributes or in a specified subset of attributes.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.match-attribute.synopsis=Specifies the name(s) of the attribute(s) whose values should be checked to determine whether they match the provided password. If no values are provided, then the server checks if the proposed password matches the value of any attribute in the user's entry.
+property.match-attribute.default-behavior.alias.synopsis=All attributes in the user entry will be checked.
+property.test-reversed-password.synopsis=Indicates whether this password validator should test the reversed value of the provided password as well as the order in which it was given.
diff --git a/opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_ko.properties b/opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_ko.properties
new file mode 100644
index 0000000..3bfdab5
--- /dev/null
+++ b/opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_ko.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Attribute Value Password Validator
+user-friendly-plural-name=Attribute Value Password Validators
+synopsis=The Attribute Value Password Validator attempts to determine whether a proposed password is acceptable for use by determining whether that password is contained in any attribute within the user's entry.
+description=It can be configured to look in all attributes or in a specified subset of attributes.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.match-attribute.synopsis=Specifies the name(s) of the attribute(s) whose values should be checked to determine whether they match the provided password. If no values are provided, then the server checks if the proposed password matches the value of any attribute in the user's entry.
+property.match-attribute.default-behavior.alias.synopsis=All attributes in the user entry will be checked.
+property.test-reversed-password.synopsis=Indicates whether this password validator should test the reversed value of the provided password as well as the order in which it was given.
diff --git a/opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_zh_CN.properties b/opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..3bfdab5
--- /dev/null
+++ b/opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_zh_CN.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Attribute Value Password Validator
+user-friendly-plural-name=Attribute Value Password Validators
+synopsis=The Attribute Value Password Validator attempts to determine whether a proposed password is acceptable for use by determining whether that password is contained in any attribute within the user's entry.
+description=It can be configured to look in all attributes or in a specified subset of attributes.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.match-attribute.synopsis=Specifies the name(s) of the attribute(s) whose values should be checked to determine whether they match the provided password. If no values are provided, then the server checks if the proposed password matches the value of any attribute in the user's entry.
+property.match-attribute.default-behavior.alias.synopsis=All attributes in the user entry will be checked.
+property.test-reversed-password.synopsis=Indicates whether this password validator should test the reversed value of the provided password as well as the order in which it was given.
diff --git a/opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_zh_TW.properties b/opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..3bfdab5
--- /dev/null
+++ b/opends/src/admin/messages/AttributeValuePasswordValidatorCfgDefn_zh_TW.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Attribute Value Password Validator
+user-friendly-plural-name=Attribute Value Password Validators
+synopsis=The Attribute Value Password Validator attempts to determine whether a proposed password is acceptable for use by determining whether that password is contained in any attribute within the user's entry.
+description=It can be configured to look in all attributes or in a specified subset of attributes.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.match-attribute.synopsis=Specifies the name(s) of the attribute(s) whose values should be checked to determine whether they match the provided password. If no values are provided, then the server checks if the proposed password matches the value of any attribute in the user's entry.
+property.match-attribute.default-behavior.alias.synopsis=All attributes in the user entry will be checked.
+property.test-reversed-password.synopsis=Indicates whether this password validator should test the reversed value of the provided password as well as the order in which it was given.
diff --git a/opends/src/admin/messages/BackendCfgDefn.properties b/opends/src/admin/messages/BackendCfgDefn.properties
new file mode 100644
index 0000000..deaa7b7
--- /dev/null
+++ b/opends/src/admin/messages/BackendCfgDefn.properties
@@ -0,0 +1,16 @@
+user-friendly-name=Backend
+user-friendly-plural-name=Backends
+synopsis=Backends are responsible for providing access to the underlying data presented by the server.
+description=The data may be stored locally in an embedded database, remotely in an external system, or generated on the fly (for example, calculated from other information that is available).
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/BackendCfgDefn_de.properties b/opends/src/admin/messages/BackendCfgDefn_de.properties
new file mode 100644
index 0000000..deaa7b7
--- /dev/null
+++ b/opends/src/admin/messages/BackendCfgDefn_de.properties
@@ -0,0 +1,16 @@
+user-friendly-name=Backend
+user-friendly-plural-name=Backends
+synopsis=Backends are responsible for providing access to the underlying data presented by the server.
+description=The data may be stored locally in an embedded database, remotely in an external system, or generated on the fly (for example, calculated from other information that is available).
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/BackendCfgDefn_es.properties b/opends/src/admin/messages/BackendCfgDefn_es.properties
new file mode 100644
index 0000000..deaa7b7
--- /dev/null
+++ b/opends/src/admin/messages/BackendCfgDefn_es.properties
@@ -0,0 +1,16 @@
+user-friendly-name=Backend
+user-friendly-plural-name=Backends
+synopsis=Backends are responsible for providing access to the underlying data presented by the server.
+description=The data may be stored locally in an embedded database, remotely in an external system, or generated on the fly (for example, calculated from other information that is available).
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/BackendCfgDefn_fr.properties b/opends/src/admin/messages/BackendCfgDefn_fr.properties
new file mode 100644
index 0000000..deaa7b7
--- /dev/null
+++ b/opends/src/admin/messages/BackendCfgDefn_fr.properties
@@ -0,0 +1,16 @@
+user-friendly-name=Backend
+user-friendly-plural-name=Backends
+synopsis=Backends are responsible for providing access to the underlying data presented by the server.
+description=The data may be stored locally in an embedded database, remotely in an external system, or generated on the fly (for example, calculated from other information that is available).
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/BackendCfgDefn_ja.properties b/opends/src/admin/messages/BackendCfgDefn_ja.properties
new file mode 100644
index 0000000..deaa7b7
--- /dev/null
+++ b/opends/src/admin/messages/BackendCfgDefn_ja.properties
@@ -0,0 +1,16 @@
+user-friendly-name=Backend
+user-friendly-plural-name=Backends
+synopsis=Backends are responsible for providing access to the underlying data presented by the server.
+description=The data may be stored locally in an embedded database, remotely in an external system, or generated on the fly (for example, calculated from other information that is available).
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/BackendCfgDefn_ko.properties b/opends/src/admin/messages/BackendCfgDefn_ko.properties
new file mode 100644
index 0000000..deaa7b7
--- /dev/null
+++ b/opends/src/admin/messages/BackendCfgDefn_ko.properties
@@ -0,0 +1,16 @@
+user-friendly-name=Backend
+user-friendly-plural-name=Backends
+synopsis=Backends are responsible for providing access to the underlying data presented by the server.
+description=The data may be stored locally in an embedded database, remotely in an external system, or generated on the fly (for example, calculated from other information that is available).
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/BackendCfgDefn_zh_CN.properties b/opends/src/admin/messages/BackendCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..deaa7b7
--- /dev/null
+++ b/opends/src/admin/messages/BackendCfgDefn_zh_CN.properties
@@ -0,0 +1,16 @@
+user-friendly-name=Backend
+user-friendly-plural-name=Backends
+synopsis=Backends are responsible for providing access to the underlying data presented by the server.
+description=The data may be stored locally in an embedded database, remotely in an external system, or generated on the fly (for example, calculated from other information that is available).
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/BackendCfgDefn_zh_TW.properties b/opends/src/admin/messages/BackendCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..deaa7b7
--- /dev/null
+++ b/opends/src/admin/messages/BackendCfgDefn_zh_TW.properties
@@ -0,0 +1,16 @@
+user-friendly-name=Backend
+user-friendly-plural-name=Backends
+synopsis=Backends are responsible for providing access to the underlying data presented by the server.
+description=The data may be stored locally in an embedded database, remotely in an external system, or generated on the fly (for example, calculated from other information that is available).
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/BackupBackendCfgDefn.properties b/opends/src/admin/messages/BackupBackendCfgDefn.properties
new file mode 100644
index 0000000..ec642e2
--- /dev/null
+++ b/opends/src/admin/messages/BackupBackendCfgDefn.properties
@@ -0,0 +1,18 @@
+user-friendly-name=Backup Backend
+user-friendly-plural-name=Backup Backends
+synopsis=The Backup Backend provides read-only access to the set of backups that are available for the OpenDS Directory Server.
+description=It is provided as a convenience feature that makes it easier to determine what backups are available to be restored if necessary.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.backup-directory.synopsis=Specifies the path to a backup directory containing one or more backups for a particular backend.
+property.backup-directory.description=This is a multivalued property. Each value may specify a different backup directory if desired (one for each backend for which backups are taken). Values may be either absolute paths or paths that are relative to the base of the OpenDS Directory Server installation.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/BackupBackendCfgDefn_de.properties b/opends/src/admin/messages/BackupBackendCfgDefn_de.properties
new file mode 100644
index 0000000..ec642e2
--- /dev/null
+++ b/opends/src/admin/messages/BackupBackendCfgDefn_de.properties
@@ -0,0 +1,18 @@
+user-friendly-name=Backup Backend
+user-friendly-plural-name=Backup Backends
+synopsis=The Backup Backend provides read-only access to the set of backups that are available for the OpenDS Directory Server.
+description=It is provided as a convenience feature that makes it easier to determine what backups are available to be restored if necessary.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.backup-directory.synopsis=Specifies the path to a backup directory containing one or more backups for a particular backend.
+property.backup-directory.description=This is a multivalued property. Each value may specify a different backup directory if desired (one for each backend for which backups are taken). Values may be either absolute paths or paths that are relative to the base of the OpenDS Directory Server installation.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/BackupBackendCfgDefn_es.properties b/opends/src/admin/messages/BackupBackendCfgDefn_es.properties
new file mode 100644
index 0000000..ec642e2
--- /dev/null
+++ b/opends/src/admin/messages/BackupBackendCfgDefn_es.properties
@@ -0,0 +1,18 @@
+user-friendly-name=Backup Backend
+user-friendly-plural-name=Backup Backends
+synopsis=The Backup Backend provides read-only access to the set of backups that are available for the OpenDS Directory Server.
+description=It is provided as a convenience feature that makes it easier to determine what backups are available to be restored if necessary.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.backup-directory.synopsis=Specifies the path to a backup directory containing one or more backups for a particular backend.
+property.backup-directory.description=This is a multivalued property. Each value may specify a different backup directory if desired (one for each backend for which backups are taken). Values may be either absolute paths or paths that are relative to the base of the OpenDS Directory Server installation.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/BackupBackendCfgDefn_fr.properties b/opends/src/admin/messages/BackupBackendCfgDefn_fr.properties
new file mode 100644
index 0000000..ec642e2
--- /dev/null
+++ b/opends/src/admin/messages/BackupBackendCfgDefn_fr.properties
@@ -0,0 +1,18 @@
+user-friendly-name=Backup Backend
+user-friendly-plural-name=Backup Backends
+synopsis=The Backup Backend provides read-only access to the set of backups that are available for the OpenDS Directory Server.
+description=It is provided as a convenience feature that makes it easier to determine what backups are available to be restored if necessary.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.backup-directory.synopsis=Specifies the path to a backup directory containing one or more backups for a particular backend.
+property.backup-directory.description=This is a multivalued property. Each value may specify a different backup directory if desired (one for each backend for which backups are taken). Values may be either absolute paths or paths that are relative to the base of the OpenDS Directory Server installation.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/BackupBackendCfgDefn_ja.properties b/opends/src/admin/messages/BackupBackendCfgDefn_ja.properties
new file mode 100644
index 0000000..ec642e2
--- /dev/null
+++ b/opends/src/admin/messages/BackupBackendCfgDefn_ja.properties
@@ -0,0 +1,18 @@
+user-friendly-name=Backup Backend
+user-friendly-plural-name=Backup Backends
+synopsis=The Backup Backend provides read-only access to the set of backups that are available for the OpenDS Directory Server.
+description=It is provided as a convenience feature that makes it easier to determine what backups are available to be restored if necessary.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.backup-directory.synopsis=Specifies the path to a backup directory containing one or more backups for a particular backend.
+property.backup-directory.description=This is a multivalued property. Each value may specify a different backup directory if desired (one for each backend for which backups are taken). Values may be either absolute paths or paths that are relative to the base of the OpenDS Directory Server installation.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/BackupBackendCfgDefn_ko.properties b/opends/src/admin/messages/BackupBackendCfgDefn_ko.properties
new file mode 100644
index 0000000..ec642e2
--- /dev/null
+++ b/opends/src/admin/messages/BackupBackendCfgDefn_ko.properties
@@ -0,0 +1,18 @@
+user-friendly-name=Backup Backend
+user-friendly-plural-name=Backup Backends
+synopsis=The Backup Backend provides read-only access to the set of backups that are available for the OpenDS Directory Server.
+description=It is provided as a convenience feature that makes it easier to determine what backups are available to be restored if necessary.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.backup-directory.synopsis=Specifies the path to a backup directory containing one or more backups for a particular backend.
+property.backup-directory.description=This is a multivalued property. Each value may specify a different backup directory if desired (one for each backend for which backups are taken). Values may be either absolute paths or paths that are relative to the base of the OpenDS Directory Server installation.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/BackupBackendCfgDefn_zh_CN.properties b/opends/src/admin/messages/BackupBackendCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..ec642e2
--- /dev/null
+++ b/opends/src/admin/messages/BackupBackendCfgDefn_zh_CN.properties
@@ -0,0 +1,18 @@
+user-friendly-name=Backup Backend
+user-friendly-plural-name=Backup Backends
+synopsis=The Backup Backend provides read-only access to the set of backups that are available for the OpenDS Directory Server.
+description=It is provided as a convenience feature that makes it easier to determine what backups are available to be restored if necessary.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.backup-directory.synopsis=Specifies the path to a backup directory containing one or more backups for a particular backend.
+property.backup-directory.description=This is a multivalued property. Each value may specify a different backup directory if desired (one for each backend for which backups are taken). Values may be either absolute paths or paths that are relative to the base of the OpenDS Directory Server installation.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/BackupBackendCfgDefn_zh_TW.properties b/opends/src/admin/messages/BackupBackendCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..ec642e2
--- /dev/null
+++ b/opends/src/admin/messages/BackupBackendCfgDefn_zh_TW.properties
@@ -0,0 +1,18 @@
+user-friendly-name=Backup Backend
+user-friendly-plural-name=Backup Backends
+synopsis=The Backup Backend provides read-only access to the set of backups that are available for the OpenDS Directory Server.
+description=It is provided as a convenience feature that makes it easier to determine what backups are available to be restored if necessary.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.backup-directory.synopsis=Specifies the path to a backup directory containing one or more backups for a particular backend.
+property.backup-directory.description=This is a multivalued property. Each value may specify a different backup directory if desired (one for each backend for which backups are taken). Values may be either absolute paths or paths that are relative to the base of the OpenDS Directory Server installation.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn.properties b/opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn.properties
new file mode 100644
index 0000000..5d5d8a7
--- /dev/null
+++ b/opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Base64 Password Storage Scheme
+user-friendly-plural-name=Base64 Password Storage Schemes
+synopsis=The Base64 Password Storage Scheme provides a mechanism for encoding user passwords using the BASE64 encoding mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "BASE64". The Base64 Password Storage Scheme merely obscures the password so that the clear-text password is not available to casual observers. However, it offers no real protection and should only be used if there are client applications that specifically require this capability.
+property.enabled.synopsis=Indicates whether the Base64 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Base64 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_de.properties b/opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_de.properties
new file mode 100644
index 0000000..5d5d8a7
--- /dev/null
+++ b/opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Base64 Password Storage Scheme
+user-friendly-plural-name=Base64 Password Storage Schemes
+synopsis=The Base64 Password Storage Scheme provides a mechanism for encoding user passwords using the BASE64 encoding mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "BASE64". The Base64 Password Storage Scheme merely obscures the password so that the clear-text password is not available to casual observers. However, it offers no real protection and should only be used if there are client applications that specifically require this capability.
+property.enabled.synopsis=Indicates whether the Base64 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Base64 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_es.properties b/opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_es.properties
new file mode 100644
index 0000000..5d5d8a7
--- /dev/null
+++ b/opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Base64 Password Storage Scheme
+user-friendly-plural-name=Base64 Password Storage Schemes
+synopsis=The Base64 Password Storage Scheme provides a mechanism for encoding user passwords using the BASE64 encoding mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "BASE64". The Base64 Password Storage Scheme merely obscures the password so that the clear-text password is not available to casual observers. However, it offers no real protection and should only be used if there are client applications that specifically require this capability.
+property.enabled.synopsis=Indicates whether the Base64 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Base64 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_fr.properties b/opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_fr.properties
new file mode 100644
index 0000000..5d5d8a7
--- /dev/null
+++ b/opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Base64 Password Storage Scheme
+user-friendly-plural-name=Base64 Password Storage Schemes
+synopsis=The Base64 Password Storage Scheme provides a mechanism for encoding user passwords using the BASE64 encoding mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "BASE64". The Base64 Password Storage Scheme merely obscures the password so that the clear-text password is not available to casual observers. However, it offers no real protection and should only be used if there are client applications that specifically require this capability.
+property.enabled.synopsis=Indicates whether the Base64 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Base64 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_ja.properties b/opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_ja.properties
new file mode 100644
index 0000000..5d5d8a7
--- /dev/null
+++ b/opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Base64 Password Storage Scheme
+user-friendly-plural-name=Base64 Password Storage Schemes
+synopsis=The Base64 Password Storage Scheme provides a mechanism for encoding user passwords using the BASE64 encoding mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "BASE64". The Base64 Password Storage Scheme merely obscures the password so that the clear-text password is not available to casual observers. However, it offers no real protection and should only be used if there are client applications that specifically require this capability.
+property.enabled.synopsis=Indicates whether the Base64 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Base64 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_ko.properties b/opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_ko.properties
new file mode 100644
index 0000000..5d5d8a7
--- /dev/null
+++ b/opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Base64 Password Storage Scheme
+user-friendly-plural-name=Base64 Password Storage Schemes
+synopsis=The Base64 Password Storage Scheme provides a mechanism for encoding user passwords using the BASE64 encoding mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "BASE64". The Base64 Password Storage Scheme merely obscures the password so that the clear-text password is not available to casual observers. However, it offers no real protection and should only be used if there are client applications that specifically require this capability.
+property.enabled.synopsis=Indicates whether the Base64 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Base64 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_zh_CN.properties b/opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..5d5d8a7
--- /dev/null
+++ b/opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Base64 Password Storage Scheme
+user-friendly-plural-name=Base64 Password Storage Schemes
+synopsis=The Base64 Password Storage Scheme provides a mechanism for encoding user passwords using the BASE64 encoding mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "BASE64". The Base64 Password Storage Scheme merely obscures the password so that the clear-text password is not available to casual observers. However, it offers no real protection and should only be used if there are client applications that specifically require this capability.
+property.enabled.synopsis=Indicates whether the Base64 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Base64 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_zh_TW.properties b/opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..5d5d8a7
--- /dev/null
+++ b/opends/src/admin/messages/Base64PasswordStorageSchemeCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Base64 Password Storage Scheme
+user-friendly-plural-name=Base64 Password Storage Schemes
+synopsis=The Base64 Password Storage Scheme provides a mechanism for encoding user passwords using the BASE64 encoding mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "BASE64". The Base64 Password Storage Scheme merely obscures the password so that the clear-text password is not available to casual observers. However, it offers no real protection and should only be used if there are client applications that specifically require this capability.
+property.enabled.synopsis=Indicates whether the Base64 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Base64 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/BlindTrustManagerProviderCfgDefn.properties b/opends/src/admin/messages/BlindTrustManagerProviderCfgDefn.properties
new file mode 100644
index 0000000..3808346
--- /dev/null
+++ b/opends/src/admin/messages/BlindTrustManagerProviderCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Blind Trust Manager Provider
+user-friendly-plural-name=Blind Trust Manager Providers
+synopsis=The blind trust manager provider always trusts any certificate that is presented to it, regardless of its issuer, subject, and validity dates.
+description=Use the blind trust manager provider only for testing purposes, because it allows clients to use forged certificates and authenticate as virtually any user in the server.
+property.enabled.synopsis=Indicate whether the Blind Trust Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Blind Trust Manager Provider implementation.
diff --git a/opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_de.properties b/opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_de.properties
new file mode 100644
index 0000000..3808346
--- /dev/null
+++ b/opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Blind Trust Manager Provider
+user-friendly-plural-name=Blind Trust Manager Providers
+synopsis=The blind trust manager provider always trusts any certificate that is presented to it, regardless of its issuer, subject, and validity dates.
+description=Use the blind trust manager provider only for testing purposes, because it allows clients to use forged certificates and authenticate as virtually any user in the server.
+property.enabled.synopsis=Indicate whether the Blind Trust Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Blind Trust Manager Provider implementation.
diff --git a/opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_es.properties b/opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_es.properties
new file mode 100644
index 0000000..3808346
--- /dev/null
+++ b/opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Blind Trust Manager Provider
+user-friendly-plural-name=Blind Trust Manager Providers
+synopsis=The blind trust manager provider always trusts any certificate that is presented to it, regardless of its issuer, subject, and validity dates.
+description=Use the blind trust manager provider only for testing purposes, because it allows clients to use forged certificates and authenticate as virtually any user in the server.
+property.enabled.synopsis=Indicate whether the Blind Trust Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Blind Trust Manager Provider implementation.
diff --git a/opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_fr.properties b/opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_fr.properties
new file mode 100644
index 0000000..3808346
--- /dev/null
+++ b/opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Blind Trust Manager Provider
+user-friendly-plural-name=Blind Trust Manager Providers
+synopsis=The blind trust manager provider always trusts any certificate that is presented to it, regardless of its issuer, subject, and validity dates.
+description=Use the blind trust manager provider only for testing purposes, because it allows clients to use forged certificates and authenticate as virtually any user in the server.
+property.enabled.synopsis=Indicate whether the Blind Trust Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Blind Trust Manager Provider implementation.
diff --git a/opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_ja.properties b/opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_ja.properties
new file mode 100644
index 0000000..3808346
--- /dev/null
+++ b/opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Blind Trust Manager Provider
+user-friendly-plural-name=Blind Trust Manager Providers
+synopsis=The blind trust manager provider always trusts any certificate that is presented to it, regardless of its issuer, subject, and validity dates.
+description=Use the blind trust manager provider only for testing purposes, because it allows clients to use forged certificates and authenticate as virtually any user in the server.
+property.enabled.synopsis=Indicate whether the Blind Trust Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Blind Trust Manager Provider implementation.
diff --git a/opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_ko.properties b/opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_ko.properties
new file mode 100644
index 0000000..3808346
--- /dev/null
+++ b/opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Blind Trust Manager Provider
+user-friendly-plural-name=Blind Trust Manager Providers
+synopsis=The blind trust manager provider always trusts any certificate that is presented to it, regardless of its issuer, subject, and validity dates.
+description=Use the blind trust manager provider only for testing purposes, because it allows clients to use forged certificates and authenticate as virtually any user in the server.
+property.enabled.synopsis=Indicate whether the Blind Trust Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Blind Trust Manager Provider implementation.
diff --git a/opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_zh_CN.properties b/opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..3808346
--- /dev/null
+++ b/opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Blind Trust Manager Provider
+user-friendly-plural-name=Blind Trust Manager Providers
+synopsis=The blind trust manager provider always trusts any certificate that is presented to it, regardless of its issuer, subject, and validity dates.
+description=Use the blind trust manager provider only for testing purposes, because it allows clients to use forged certificates and authenticate as virtually any user in the server.
+property.enabled.synopsis=Indicate whether the Blind Trust Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Blind Trust Manager Provider implementation.
diff --git a/opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_zh_TW.properties b/opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..3808346
--- /dev/null
+++ b/opends/src/admin/messages/BlindTrustManagerProviderCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Blind Trust Manager Provider
+user-friendly-plural-name=Blind Trust Manager Providers
+synopsis=The blind trust manager provider always trusts any certificate that is presented to it, regardless of its issuer, subject, and validity dates.
+description=Use the blind trust manager provider only for testing purposes, because it allows clients to use forged certificates and authenticate as virtually any user in the server.
+property.enabled.synopsis=Indicate whether the Blind Trust Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Blind Trust Manager Provider implementation.
diff --git a/opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn.properties b/opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn.properties
new file mode 100644
index 0000000..e9504ab
--- /dev/null
+++ b/opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Blowfish Password Storage Scheme
+user-friendly-plural-name=Blowfish Password Storage Schemes
+synopsis=The Blowfish Password Storage Scheme provides a mechanism for encoding user passwords using the Blowfish reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "BLOWFISH".
+property.enabled.synopsis=Indicates whether the Blowfish Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Blowfish Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_de.properties b/opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_de.properties
new file mode 100644
index 0000000..e9504ab
--- /dev/null
+++ b/opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Blowfish Password Storage Scheme
+user-friendly-plural-name=Blowfish Password Storage Schemes
+synopsis=The Blowfish Password Storage Scheme provides a mechanism for encoding user passwords using the Blowfish reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "BLOWFISH".
+property.enabled.synopsis=Indicates whether the Blowfish Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Blowfish Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_es.properties b/opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_es.properties
new file mode 100644
index 0000000..e9504ab
--- /dev/null
+++ b/opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Blowfish Password Storage Scheme
+user-friendly-plural-name=Blowfish Password Storage Schemes
+synopsis=The Blowfish Password Storage Scheme provides a mechanism for encoding user passwords using the Blowfish reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "BLOWFISH".
+property.enabled.synopsis=Indicates whether the Blowfish Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Blowfish Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_fr.properties b/opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_fr.properties
new file mode 100644
index 0000000..e9504ab
--- /dev/null
+++ b/opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Blowfish Password Storage Scheme
+user-friendly-plural-name=Blowfish Password Storage Schemes
+synopsis=The Blowfish Password Storage Scheme provides a mechanism for encoding user passwords using the Blowfish reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "BLOWFISH".
+property.enabled.synopsis=Indicates whether the Blowfish Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Blowfish Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_ja.properties b/opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_ja.properties
new file mode 100644
index 0000000..e9504ab
--- /dev/null
+++ b/opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Blowfish Password Storage Scheme
+user-friendly-plural-name=Blowfish Password Storage Schemes
+synopsis=The Blowfish Password Storage Scheme provides a mechanism for encoding user passwords using the Blowfish reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "BLOWFISH".
+property.enabled.synopsis=Indicates whether the Blowfish Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Blowfish Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_ko.properties b/opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_ko.properties
new file mode 100644
index 0000000..e9504ab
--- /dev/null
+++ b/opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Blowfish Password Storage Scheme
+user-friendly-plural-name=Blowfish Password Storage Schemes
+synopsis=The Blowfish Password Storage Scheme provides a mechanism for encoding user passwords using the Blowfish reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "BLOWFISH".
+property.enabled.synopsis=Indicates whether the Blowfish Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Blowfish Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_zh_CN.properties b/opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..e9504ab
--- /dev/null
+++ b/opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Blowfish Password Storage Scheme
+user-friendly-plural-name=Blowfish Password Storage Schemes
+synopsis=The Blowfish Password Storage Scheme provides a mechanism for encoding user passwords using the Blowfish reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "BLOWFISH".
+property.enabled.synopsis=Indicates whether the Blowfish Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Blowfish Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_zh_TW.properties b/opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..e9504ab
--- /dev/null
+++ b/opends/src/admin/messages/BlowfishPasswordStorageSchemeCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Blowfish Password Storage Scheme
+user-friendly-plural-name=Blowfish Password Storage Schemes
+synopsis=The Blowfish Password Storage Scheme provides a mechanism for encoding user passwords using the Blowfish reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "BLOWFISH".
+property.enabled.synopsis=Indicates whether the Blowfish Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Blowfish Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn.properties b/opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn.properties
new file mode 100644
index 0000000..0d8819f
--- /dev/null
+++ b/opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Cancel Extended Operation Handler
+user-friendly-plural-name=Cancel Extended Operation Handlers
+synopsis=The Cancel Extended Operation Handler provides support for the LDAP cancel extended operation as defined in RFC 3909.
+description=It allows clients to cancel operations initiated from earlier requests. The property ensures that both the cancel request and the operation being canceled receives response messages.
+property.enabled.synopsis=Indicates whether the Cancel Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Cancel Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_de.properties b/opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..0d8819f
--- /dev/null
+++ b/opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Cancel Extended Operation Handler
+user-friendly-plural-name=Cancel Extended Operation Handlers
+synopsis=The Cancel Extended Operation Handler provides support for the LDAP cancel extended operation as defined in RFC 3909.
+description=It allows clients to cancel operations initiated from earlier requests. The property ensures that both the cancel request and the operation being canceled receives response messages.
+property.enabled.synopsis=Indicates whether the Cancel Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Cancel Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_es.properties b/opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..0d8819f
--- /dev/null
+++ b/opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Cancel Extended Operation Handler
+user-friendly-plural-name=Cancel Extended Operation Handlers
+synopsis=The Cancel Extended Operation Handler provides support for the LDAP cancel extended operation as defined in RFC 3909.
+description=It allows clients to cancel operations initiated from earlier requests. The property ensures that both the cancel request and the operation being canceled receives response messages.
+property.enabled.synopsis=Indicates whether the Cancel Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Cancel Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_fr.properties b/opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..0d8819f
--- /dev/null
+++ b/opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Cancel Extended Operation Handler
+user-friendly-plural-name=Cancel Extended Operation Handlers
+synopsis=The Cancel Extended Operation Handler provides support for the LDAP cancel extended operation as defined in RFC 3909.
+description=It allows clients to cancel operations initiated from earlier requests. The property ensures that both the cancel request and the operation being canceled receives response messages.
+property.enabled.synopsis=Indicates whether the Cancel Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Cancel Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_ja.properties b/opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..0d8819f
--- /dev/null
+++ b/opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Cancel Extended Operation Handler
+user-friendly-plural-name=Cancel Extended Operation Handlers
+synopsis=The Cancel Extended Operation Handler provides support for the LDAP cancel extended operation as defined in RFC 3909.
+description=It allows clients to cancel operations initiated from earlier requests. The property ensures that both the cancel request and the operation being canceled receives response messages.
+property.enabled.synopsis=Indicates whether the Cancel Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Cancel Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_ko.properties b/opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..0d8819f
--- /dev/null
+++ b/opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Cancel Extended Operation Handler
+user-friendly-plural-name=Cancel Extended Operation Handlers
+synopsis=The Cancel Extended Operation Handler provides support for the LDAP cancel extended operation as defined in RFC 3909.
+description=It allows clients to cancel operations initiated from earlier requests. The property ensures that both the cancel request and the operation being canceled receives response messages.
+property.enabled.synopsis=Indicates whether the Cancel Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Cancel Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..0d8819f
--- /dev/null
+++ b/opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Cancel Extended Operation Handler
+user-friendly-plural-name=Cancel Extended Operation Handlers
+synopsis=The Cancel Extended Operation Handler provides support for the LDAP cancel extended operation as defined in RFC 3909.
+description=It allows clients to cancel operations initiated from earlier requests. The property ensures that both the cancel request and the operation being canceled receives response messages.
+property.enabled.synopsis=Indicates whether the Cancel Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Cancel Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..0d8819f
--- /dev/null
+++ b/opends/src/admin/messages/CancelExtendedOperationHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Cancel Extended Operation Handler
+user-friendly-plural-name=Cancel Extended Operation Handlers
+synopsis=The Cancel Extended Operation Handler provides support for the LDAP cancel extended operation as defined in RFC 3909.
+description=It allows clients to cancel operations initiated from earlier requests. The property ensures that both the cancel request and the operation being canceled receives response messages.
+property.enabled.synopsis=Indicates whether the Cancel Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Cancel Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/CertificateMapperCfgDefn.properties b/opends/src/admin/messages/CertificateMapperCfgDefn.properties
new file mode 100644
index 0000000..faada6e
--- /dev/null
+++ b/opends/src/admin/messages/CertificateMapperCfgDefn.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Certificate Mapper
+user-friendly-plural-name=Certificate Mappers
+synopsis=Certificate Mappers are responsible for establishing a mapping between a client certificate and the entry for the user that corresponds to that certificate.
+property.enabled.synopsis=Indicates whether the Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Certificate Mapper implementation.
diff --git a/opends/src/admin/messages/CertificateMapperCfgDefn_de.properties b/opends/src/admin/messages/CertificateMapperCfgDefn_de.properties
new file mode 100644
index 0000000..faada6e
--- /dev/null
+++ b/opends/src/admin/messages/CertificateMapperCfgDefn_de.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Certificate Mapper
+user-friendly-plural-name=Certificate Mappers
+synopsis=Certificate Mappers are responsible for establishing a mapping between a client certificate and the entry for the user that corresponds to that certificate.
+property.enabled.synopsis=Indicates whether the Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Certificate Mapper implementation.
diff --git a/opends/src/admin/messages/CertificateMapperCfgDefn_es.properties b/opends/src/admin/messages/CertificateMapperCfgDefn_es.properties
new file mode 100644
index 0000000..faada6e
--- /dev/null
+++ b/opends/src/admin/messages/CertificateMapperCfgDefn_es.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Certificate Mapper
+user-friendly-plural-name=Certificate Mappers
+synopsis=Certificate Mappers are responsible for establishing a mapping between a client certificate and the entry for the user that corresponds to that certificate.
+property.enabled.synopsis=Indicates whether the Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Certificate Mapper implementation.
diff --git a/opends/src/admin/messages/CertificateMapperCfgDefn_fr.properties b/opends/src/admin/messages/CertificateMapperCfgDefn_fr.properties
new file mode 100644
index 0000000..faada6e
--- /dev/null
+++ b/opends/src/admin/messages/CertificateMapperCfgDefn_fr.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Certificate Mapper
+user-friendly-plural-name=Certificate Mappers
+synopsis=Certificate Mappers are responsible for establishing a mapping between a client certificate and the entry for the user that corresponds to that certificate.
+property.enabled.synopsis=Indicates whether the Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Certificate Mapper implementation.
diff --git a/opends/src/admin/messages/CertificateMapperCfgDefn_ja.properties b/opends/src/admin/messages/CertificateMapperCfgDefn_ja.properties
new file mode 100644
index 0000000..faada6e
--- /dev/null
+++ b/opends/src/admin/messages/CertificateMapperCfgDefn_ja.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Certificate Mapper
+user-friendly-plural-name=Certificate Mappers
+synopsis=Certificate Mappers are responsible for establishing a mapping between a client certificate and the entry for the user that corresponds to that certificate.
+property.enabled.synopsis=Indicates whether the Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Certificate Mapper implementation.
diff --git a/opends/src/admin/messages/CertificateMapperCfgDefn_ko.properties b/opends/src/admin/messages/CertificateMapperCfgDefn_ko.properties
new file mode 100644
index 0000000..faada6e
--- /dev/null
+++ b/opends/src/admin/messages/CertificateMapperCfgDefn_ko.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Certificate Mapper
+user-friendly-plural-name=Certificate Mappers
+synopsis=Certificate Mappers are responsible for establishing a mapping between a client certificate and the entry for the user that corresponds to that certificate.
+property.enabled.synopsis=Indicates whether the Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Certificate Mapper implementation.
diff --git a/opends/src/admin/messages/CertificateMapperCfgDefn_zh_CN.properties b/opends/src/admin/messages/CertificateMapperCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..faada6e
--- /dev/null
+++ b/opends/src/admin/messages/CertificateMapperCfgDefn_zh_CN.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Certificate Mapper
+user-friendly-plural-name=Certificate Mappers
+synopsis=Certificate Mappers are responsible for establishing a mapping between a client certificate and the entry for the user that corresponds to that certificate.
+property.enabled.synopsis=Indicates whether the Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Certificate Mapper implementation.
diff --git a/opends/src/admin/messages/CertificateMapperCfgDefn_zh_TW.properties b/opends/src/admin/messages/CertificateMapperCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..faada6e
--- /dev/null
+++ b/opends/src/admin/messages/CertificateMapperCfgDefn_zh_TW.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Certificate Mapper
+user-friendly-plural-name=Certificate Mappers
+synopsis=Certificate Mappers are responsible for establishing a mapping between a client certificate and the entry for the user that corresponds to that certificate.
+property.enabled.synopsis=Indicates whether the Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Certificate Mapper implementation.
diff --git a/opends/src/admin/messages/ChangeNumberControlPluginCfgDefn.properties b/opends/src/admin/messages/ChangeNumberControlPluginCfgDefn.properties
new file mode 100644
index 0000000..c41521e
--- /dev/null
+++ b/opends/src/admin/messages/ChangeNumberControlPluginCfgDefn.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Change Number Control Plugin
+user-friendly-plural-name=Change Number Control Plugins
+synopsis=The Change Number Control Plugin returns the change number generated by the replication subsystem.
+description=The Change Number Control Plugin returns the change number generated by the Multi-Master Replication subsystem when : - the Multi-Master Replication is configured and enabled - the request is a write operation (add, delete, moidfy, moddn) - the control is part of a request. If all of the above are true, the response contains a control response with a string representing the change number. The implementation for the chnage number control plug-in is contained in the org.opends.server.plugins.ChangeNumberControlPlugin class. It must be configured with the postOperationAdd, postOperationDelete, postOperationModify and postOperationModifyDN plug-in types, but it does not have any other custom configuration.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_de.properties b/opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_de.properties
new file mode 100644
index 0000000..c41521e
--- /dev/null
+++ b/opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_de.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Change Number Control Plugin
+user-friendly-plural-name=Change Number Control Plugins
+synopsis=The Change Number Control Plugin returns the change number generated by the replication subsystem.
+description=The Change Number Control Plugin returns the change number generated by the Multi-Master Replication subsystem when : - the Multi-Master Replication is configured and enabled - the request is a write operation (add, delete, moidfy, moddn) - the control is part of a request. If all of the above are true, the response contains a control response with a string representing the change number. The implementation for the chnage number control plug-in is contained in the org.opends.server.plugins.ChangeNumberControlPlugin class. It must be configured with the postOperationAdd, postOperationDelete, postOperationModify and postOperationModifyDN plug-in types, but it does not have any other custom configuration.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_es.properties b/opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_es.properties
new file mode 100644
index 0000000..c41521e
--- /dev/null
+++ b/opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_es.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Change Number Control Plugin
+user-friendly-plural-name=Change Number Control Plugins
+synopsis=The Change Number Control Plugin returns the change number generated by the replication subsystem.
+description=The Change Number Control Plugin returns the change number generated by the Multi-Master Replication subsystem when : - the Multi-Master Replication is configured and enabled - the request is a write operation (add, delete, moidfy, moddn) - the control is part of a request. If all of the above are true, the response contains a control response with a string representing the change number. The implementation for the chnage number control plug-in is contained in the org.opends.server.plugins.ChangeNumberControlPlugin class. It must be configured with the postOperationAdd, postOperationDelete, postOperationModify and postOperationModifyDN plug-in types, but it does not have any other custom configuration.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_fr.properties b/opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_fr.properties
new file mode 100644
index 0000000..c41521e
--- /dev/null
+++ b/opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_fr.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Change Number Control Plugin
+user-friendly-plural-name=Change Number Control Plugins
+synopsis=The Change Number Control Plugin returns the change number generated by the replication subsystem.
+description=The Change Number Control Plugin returns the change number generated by the Multi-Master Replication subsystem when : - the Multi-Master Replication is configured and enabled - the request is a write operation (add, delete, moidfy, moddn) - the control is part of a request. If all of the above are true, the response contains a control response with a string representing the change number. The implementation for the chnage number control plug-in is contained in the org.opends.server.plugins.ChangeNumberControlPlugin class. It must be configured with the postOperationAdd, postOperationDelete, postOperationModify and postOperationModifyDN plug-in types, but it does not have any other custom configuration.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_ja.properties b/opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_ja.properties
new file mode 100644
index 0000000..c41521e
--- /dev/null
+++ b/opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_ja.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Change Number Control Plugin
+user-friendly-plural-name=Change Number Control Plugins
+synopsis=The Change Number Control Plugin returns the change number generated by the replication subsystem.
+description=The Change Number Control Plugin returns the change number generated by the Multi-Master Replication subsystem when : - the Multi-Master Replication is configured and enabled - the request is a write operation (add, delete, moidfy, moddn) - the control is part of a request. If all of the above are true, the response contains a control response with a string representing the change number. The implementation for the chnage number control plug-in is contained in the org.opends.server.plugins.ChangeNumberControlPlugin class. It must be configured with the postOperationAdd, postOperationDelete, postOperationModify and postOperationModifyDN plug-in types, but it does not have any other custom configuration.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_ko.properties b/opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_ko.properties
new file mode 100644
index 0000000..c41521e
--- /dev/null
+++ b/opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_ko.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Change Number Control Plugin
+user-friendly-plural-name=Change Number Control Plugins
+synopsis=The Change Number Control Plugin returns the change number generated by the replication subsystem.
+description=The Change Number Control Plugin returns the change number generated by the Multi-Master Replication subsystem when : - the Multi-Master Replication is configured and enabled - the request is a write operation (add, delete, moidfy, moddn) - the control is part of a request. If all of the above are true, the response contains a control response with a string representing the change number. The implementation for the chnage number control plug-in is contained in the org.opends.server.plugins.ChangeNumberControlPlugin class. It must be configured with the postOperationAdd, postOperationDelete, postOperationModify and postOperationModifyDN plug-in types, but it does not have any other custom configuration.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_zh_CN.properties b/opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..c41521e
--- /dev/null
+++ b/opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_zh_CN.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Change Number Control Plugin
+user-friendly-plural-name=Change Number Control Plugins
+synopsis=The Change Number Control Plugin returns the change number generated by the replication subsystem.
+description=The Change Number Control Plugin returns the change number generated by the Multi-Master Replication subsystem when : - the Multi-Master Replication is configured and enabled - the request is a write operation (add, delete, moidfy, moddn) - the control is part of a request. If all of the above are true, the response contains a control response with a string representing the change number. The implementation for the chnage number control plug-in is contained in the org.opends.server.plugins.ChangeNumberControlPlugin class. It must be configured with the postOperationAdd, postOperationDelete, postOperationModify and postOperationModifyDN plug-in types, but it does not have any other custom configuration.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_zh_TW.properties b/opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..c41521e
--- /dev/null
+++ b/opends/src/admin/messages/ChangeNumberControlPluginCfgDefn_zh_TW.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Change Number Control Plugin
+user-friendly-plural-name=Change Number Control Plugins
+synopsis=The Change Number Control Plugin returns the change number generated by the replication subsystem.
+description=The Change Number Control Plugin returns the change number generated by the Multi-Master Replication subsystem when : - the Multi-Master Replication is configured and enabled - the request is a write operation (add, delete, moidfy, moddn) - the control is part of a request. If all of the above are true, the response contains a control response with a string representing the change number. The implementation for the chnage number control plug-in is contained in the org.opends.server.plugins.ChangeNumberControlPlugin class. It must be configured with the postOperationAdd, postOperationDelete, postOperationModify and postOperationModifyDN plug-in types, but it does not have any other custom configuration.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn.properties b/opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn.properties
new file mode 100644
index 0000000..5749635
--- /dev/null
+++ b/opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Character Set Password Validator
+user-friendly-plural-name=Character Set Password Validators
+synopsis=The Character Set Password Validator determines whether a proposed password is acceptable by checking whether it contains a sufficient number of characters from one or more user-defined character sets.
+description=For example, the validator can ensure that passwords must have at least one lowercase letter, one uppercase letter, one digit, and one symbol.
+property.allow-unclassified-characters.synopsis=Indicates whether this password validator allows passwords to contain characters outside of any of the user-defined character sets.
+property.allow-unclassified-characters.description=If this is "false", then only those characters in the user-defined character sets may be used in passwords. Any password containing a character not included in any character set will be rejected.
+property.character-set.synopsis=Specifies a character set containing characters that a password may contain and a value indicating the minimum number of characters required from that set.
+property.character-set.description=Each value must be an integer (indicating the minimum required characters from the set) followed by a colon and the characters to include in that set (for example, "3:abcdefghijklmnopqrstuvwxyz" indicates that a user password must contain at least three characters from the set of lowercase ASCII letters). Multiple character sets can be defined in separate values, although no character can appear in more than one character set.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
diff --git a/opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_de.properties b/opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_de.properties
new file mode 100644
index 0000000..5749635
--- /dev/null
+++ b/opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_de.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Character Set Password Validator
+user-friendly-plural-name=Character Set Password Validators
+synopsis=The Character Set Password Validator determines whether a proposed password is acceptable by checking whether it contains a sufficient number of characters from one or more user-defined character sets.
+description=For example, the validator can ensure that passwords must have at least one lowercase letter, one uppercase letter, one digit, and one symbol.
+property.allow-unclassified-characters.synopsis=Indicates whether this password validator allows passwords to contain characters outside of any of the user-defined character sets.
+property.allow-unclassified-characters.description=If this is "false", then only those characters in the user-defined character sets may be used in passwords. Any password containing a character not included in any character set will be rejected.
+property.character-set.synopsis=Specifies a character set containing characters that a password may contain and a value indicating the minimum number of characters required from that set.
+property.character-set.description=Each value must be an integer (indicating the minimum required characters from the set) followed by a colon and the characters to include in that set (for example, "3:abcdefghijklmnopqrstuvwxyz" indicates that a user password must contain at least three characters from the set of lowercase ASCII letters). Multiple character sets can be defined in separate values, although no character can appear in more than one character set.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
diff --git a/opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_es.properties b/opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_es.properties
new file mode 100644
index 0000000..5749635
--- /dev/null
+++ b/opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_es.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Character Set Password Validator
+user-friendly-plural-name=Character Set Password Validators
+synopsis=The Character Set Password Validator determines whether a proposed password is acceptable by checking whether it contains a sufficient number of characters from one or more user-defined character sets.
+description=For example, the validator can ensure that passwords must have at least one lowercase letter, one uppercase letter, one digit, and one symbol.
+property.allow-unclassified-characters.synopsis=Indicates whether this password validator allows passwords to contain characters outside of any of the user-defined character sets.
+property.allow-unclassified-characters.description=If this is "false", then only those characters in the user-defined character sets may be used in passwords. Any password containing a character not included in any character set will be rejected.
+property.character-set.synopsis=Specifies a character set containing characters that a password may contain and a value indicating the minimum number of characters required from that set.
+property.character-set.description=Each value must be an integer (indicating the minimum required characters from the set) followed by a colon and the characters to include in that set (for example, "3:abcdefghijklmnopqrstuvwxyz" indicates that a user password must contain at least three characters from the set of lowercase ASCII letters). Multiple character sets can be defined in separate values, although no character can appear in more than one character set.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
diff --git a/opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_fr.properties b/opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_fr.properties
new file mode 100644
index 0000000..5749635
--- /dev/null
+++ b/opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_fr.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Character Set Password Validator
+user-friendly-plural-name=Character Set Password Validators
+synopsis=The Character Set Password Validator determines whether a proposed password is acceptable by checking whether it contains a sufficient number of characters from one or more user-defined character sets.
+description=For example, the validator can ensure that passwords must have at least one lowercase letter, one uppercase letter, one digit, and one symbol.
+property.allow-unclassified-characters.synopsis=Indicates whether this password validator allows passwords to contain characters outside of any of the user-defined character sets.
+property.allow-unclassified-characters.description=If this is "false", then only those characters in the user-defined character sets may be used in passwords. Any password containing a character not included in any character set will be rejected.
+property.character-set.synopsis=Specifies a character set containing characters that a password may contain and a value indicating the minimum number of characters required from that set.
+property.character-set.description=Each value must be an integer (indicating the minimum required characters from the set) followed by a colon and the characters to include in that set (for example, "3:abcdefghijklmnopqrstuvwxyz" indicates that a user password must contain at least three characters from the set of lowercase ASCII letters). Multiple character sets can be defined in separate values, although no character can appear in more than one character set.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
diff --git a/opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_ja.properties b/opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_ja.properties
new file mode 100644
index 0000000..5749635
--- /dev/null
+++ b/opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_ja.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Character Set Password Validator
+user-friendly-plural-name=Character Set Password Validators
+synopsis=The Character Set Password Validator determines whether a proposed password is acceptable by checking whether it contains a sufficient number of characters from one or more user-defined character sets.
+description=For example, the validator can ensure that passwords must have at least one lowercase letter, one uppercase letter, one digit, and one symbol.
+property.allow-unclassified-characters.synopsis=Indicates whether this password validator allows passwords to contain characters outside of any of the user-defined character sets.
+property.allow-unclassified-characters.description=If this is "false", then only those characters in the user-defined character sets may be used in passwords. Any password containing a character not included in any character set will be rejected.
+property.character-set.synopsis=Specifies a character set containing characters that a password may contain and a value indicating the minimum number of characters required from that set.
+property.character-set.description=Each value must be an integer (indicating the minimum required characters from the set) followed by a colon and the characters to include in that set (for example, "3:abcdefghijklmnopqrstuvwxyz" indicates that a user password must contain at least three characters from the set of lowercase ASCII letters). Multiple character sets can be defined in separate values, although no character can appear in more than one character set.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
diff --git a/opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_ko.properties b/opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_ko.properties
new file mode 100644
index 0000000..5749635
--- /dev/null
+++ b/opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_ko.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Character Set Password Validator
+user-friendly-plural-name=Character Set Password Validators
+synopsis=The Character Set Password Validator determines whether a proposed password is acceptable by checking whether it contains a sufficient number of characters from one or more user-defined character sets.
+description=For example, the validator can ensure that passwords must have at least one lowercase letter, one uppercase letter, one digit, and one symbol.
+property.allow-unclassified-characters.synopsis=Indicates whether this password validator allows passwords to contain characters outside of any of the user-defined character sets.
+property.allow-unclassified-characters.description=If this is "false", then only those characters in the user-defined character sets may be used in passwords. Any password containing a character not included in any character set will be rejected.
+property.character-set.synopsis=Specifies a character set containing characters that a password may contain and a value indicating the minimum number of characters required from that set.
+property.character-set.description=Each value must be an integer (indicating the minimum required characters from the set) followed by a colon and the characters to include in that set (for example, "3:abcdefghijklmnopqrstuvwxyz" indicates that a user password must contain at least three characters from the set of lowercase ASCII letters). Multiple character sets can be defined in separate values, although no character can appear in more than one character set.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
diff --git a/opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_zh_CN.properties b/opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..5749635
--- /dev/null
+++ b/opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_zh_CN.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Character Set Password Validator
+user-friendly-plural-name=Character Set Password Validators
+synopsis=The Character Set Password Validator determines whether a proposed password is acceptable by checking whether it contains a sufficient number of characters from one or more user-defined character sets.
+description=For example, the validator can ensure that passwords must have at least one lowercase letter, one uppercase letter, one digit, and one symbol.
+property.allow-unclassified-characters.synopsis=Indicates whether this password validator allows passwords to contain characters outside of any of the user-defined character sets.
+property.allow-unclassified-characters.description=If this is "false", then only those characters in the user-defined character sets may be used in passwords. Any password containing a character not included in any character set will be rejected.
+property.character-set.synopsis=Specifies a character set containing characters that a password may contain and a value indicating the minimum number of characters required from that set.
+property.character-set.description=Each value must be an integer (indicating the minimum required characters from the set) followed by a colon and the characters to include in that set (for example, "3:abcdefghijklmnopqrstuvwxyz" indicates that a user password must contain at least three characters from the set of lowercase ASCII letters). Multiple character sets can be defined in separate values, although no character can appear in more than one character set.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
diff --git a/opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_zh_TW.properties b/opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..5749635
--- /dev/null
+++ b/opends/src/admin/messages/CharacterSetPasswordValidatorCfgDefn_zh_TW.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Character Set Password Validator
+user-friendly-plural-name=Character Set Password Validators
+synopsis=The Character Set Password Validator determines whether a proposed password is acceptable by checking whether it contains a sufficient number of characters from one or more user-defined character sets.
+description=For example, the validator can ensure that passwords must have at least one lowercase letter, one uppercase letter, one digit, and one symbol.
+property.allow-unclassified-characters.synopsis=Indicates whether this password validator allows passwords to contain characters outside of any of the user-defined character sets.
+property.allow-unclassified-characters.description=If this is "false", then only those characters in the user-defined character sets may be used in passwords. Any password containing a character not included in any character set will be rejected.
+property.character-set.synopsis=Specifies a character set containing characters that a password may contain and a value indicating the minimum number of characters required from that set.
+property.character-set.description=Each value must be an integer (indicating the minimum required characters from the set) followed by a colon and the characters to include in that set (for example, "3:abcdefghijklmnopqrstuvwxyz" indicates that a user password must contain at least three characters from the set of lowercase ASCII letters). Multiple character sets can be defined in separate values, although no character can appear in more than one character set.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
diff --git a/opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn.properties b/opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn.properties
new file mode 100644
index 0000000..499b2cc
--- /dev/null
+++ b/opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Clear Password Storage Scheme
+user-friendly-plural-name=Clear Password Storage Schemes
+synopsis=The Clear Password Storage Scheme provides a mechanism for storing user passwords in clear text, without any form of obfuscation.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "CLEAR". The Clear Password Storage Scheme should only be used if there are client applications that specifically require this capability.
+property.enabled.synopsis=Indicates whether the Clear Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Clear Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_de.properties b/opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_de.properties
new file mode 100644
index 0000000..499b2cc
--- /dev/null
+++ b/opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Clear Password Storage Scheme
+user-friendly-plural-name=Clear Password Storage Schemes
+synopsis=The Clear Password Storage Scheme provides a mechanism for storing user passwords in clear text, without any form of obfuscation.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "CLEAR". The Clear Password Storage Scheme should only be used if there are client applications that specifically require this capability.
+property.enabled.synopsis=Indicates whether the Clear Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Clear Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_es.properties b/opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_es.properties
new file mode 100644
index 0000000..499b2cc
--- /dev/null
+++ b/opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Clear Password Storage Scheme
+user-friendly-plural-name=Clear Password Storage Schemes
+synopsis=The Clear Password Storage Scheme provides a mechanism for storing user passwords in clear text, without any form of obfuscation.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "CLEAR". The Clear Password Storage Scheme should only be used if there are client applications that specifically require this capability.
+property.enabled.synopsis=Indicates whether the Clear Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Clear Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_fr.properties b/opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_fr.properties
new file mode 100644
index 0000000..499b2cc
--- /dev/null
+++ b/opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Clear Password Storage Scheme
+user-friendly-plural-name=Clear Password Storage Schemes
+synopsis=The Clear Password Storage Scheme provides a mechanism for storing user passwords in clear text, without any form of obfuscation.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "CLEAR". The Clear Password Storage Scheme should only be used if there are client applications that specifically require this capability.
+property.enabled.synopsis=Indicates whether the Clear Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Clear Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_ja.properties b/opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_ja.properties
new file mode 100644
index 0000000..499b2cc
--- /dev/null
+++ b/opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Clear Password Storage Scheme
+user-friendly-plural-name=Clear Password Storage Schemes
+synopsis=The Clear Password Storage Scheme provides a mechanism for storing user passwords in clear text, without any form of obfuscation.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "CLEAR". The Clear Password Storage Scheme should only be used if there are client applications that specifically require this capability.
+property.enabled.synopsis=Indicates whether the Clear Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Clear Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_ko.properties b/opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_ko.properties
new file mode 100644
index 0000000..499b2cc
--- /dev/null
+++ b/opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Clear Password Storage Scheme
+user-friendly-plural-name=Clear Password Storage Schemes
+synopsis=The Clear Password Storage Scheme provides a mechanism for storing user passwords in clear text, without any form of obfuscation.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "CLEAR". The Clear Password Storage Scheme should only be used if there are client applications that specifically require this capability.
+property.enabled.synopsis=Indicates whether the Clear Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Clear Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_zh_CN.properties b/opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..499b2cc
--- /dev/null
+++ b/opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Clear Password Storage Scheme
+user-friendly-plural-name=Clear Password Storage Schemes
+synopsis=The Clear Password Storage Scheme provides a mechanism for storing user passwords in clear text, without any form of obfuscation.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "CLEAR". The Clear Password Storage Scheme should only be used if there are client applications that specifically require this capability.
+property.enabled.synopsis=Indicates whether the Clear Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Clear Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_zh_TW.properties b/opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..499b2cc
--- /dev/null
+++ b/opends/src/admin/messages/ClearPasswordStorageSchemeCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Clear Password Storage Scheme
+user-friendly-plural-name=Clear Password Storage Schemes
+synopsis=The Clear Password Storage Scheme provides a mechanism for storing user passwords in clear text, without any form of obfuscation.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "CLEAR". The Clear Password Storage Scheme should only be used if there are client applications that specifically require this capability.
+property.enabled.synopsis=Indicates whether the Clear Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Clear Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn.properties b/opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn.properties
new file mode 100644
index 0000000..67c3386
--- /dev/null
+++ b/opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Client Connection Monitor Provider
+user-friendly-plural-name=Client Connection Monitor Providers
+synopsis=The Client Connection Monitor Provider exposes monitor information about the set of client connections that are established to the Directory Server.
+property.enabled.synopsis=Indicates whether the Client Connection Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Client Connection Monitor Provider implementation.
diff --git a/opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_de.properties b/opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_de.properties
new file mode 100644
index 0000000..67c3386
--- /dev/null
+++ b/opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_de.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Client Connection Monitor Provider
+user-friendly-plural-name=Client Connection Monitor Providers
+synopsis=The Client Connection Monitor Provider exposes monitor information about the set of client connections that are established to the Directory Server.
+property.enabled.synopsis=Indicates whether the Client Connection Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Client Connection Monitor Provider implementation.
diff --git a/opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_es.properties b/opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_es.properties
new file mode 100644
index 0000000..67c3386
--- /dev/null
+++ b/opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_es.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Client Connection Monitor Provider
+user-friendly-plural-name=Client Connection Monitor Providers
+synopsis=The Client Connection Monitor Provider exposes monitor information about the set of client connections that are established to the Directory Server.
+property.enabled.synopsis=Indicates whether the Client Connection Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Client Connection Monitor Provider implementation.
diff --git a/opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_fr.properties b/opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_fr.properties
new file mode 100644
index 0000000..67c3386
--- /dev/null
+++ b/opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_fr.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Client Connection Monitor Provider
+user-friendly-plural-name=Client Connection Monitor Providers
+synopsis=The Client Connection Monitor Provider exposes monitor information about the set of client connections that are established to the Directory Server.
+property.enabled.synopsis=Indicates whether the Client Connection Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Client Connection Monitor Provider implementation.
diff --git a/opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_ja.properties b/opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_ja.properties
new file mode 100644
index 0000000..67c3386
--- /dev/null
+++ b/opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_ja.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Client Connection Monitor Provider
+user-friendly-plural-name=Client Connection Monitor Providers
+synopsis=The Client Connection Monitor Provider exposes monitor information about the set of client connections that are established to the Directory Server.
+property.enabled.synopsis=Indicates whether the Client Connection Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Client Connection Monitor Provider implementation.
diff --git a/opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_ko.properties b/opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_ko.properties
new file mode 100644
index 0000000..67c3386
--- /dev/null
+++ b/opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_ko.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Client Connection Monitor Provider
+user-friendly-plural-name=Client Connection Monitor Providers
+synopsis=The Client Connection Monitor Provider exposes monitor information about the set of client connections that are established to the Directory Server.
+property.enabled.synopsis=Indicates whether the Client Connection Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Client Connection Monitor Provider implementation.
diff --git a/opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_zh_CN.properties b/opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..67c3386
--- /dev/null
+++ b/opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_zh_CN.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Client Connection Monitor Provider
+user-friendly-plural-name=Client Connection Monitor Providers
+synopsis=The Client Connection Monitor Provider exposes monitor information about the set of client connections that are established to the Directory Server.
+property.enabled.synopsis=Indicates whether the Client Connection Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Client Connection Monitor Provider implementation.
diff --git a/opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_zh_TW.properties b/opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..67c3386
--- /dev/null
+++ b/opends/src/admin/messages/ClientConnectionMonitorProviderCfgDefn_zh_TW.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Client Connection Monitor Provider
+user-friendly-plural-name=Client Connection Monitor Providers
+synopsis=The Client Connection Monitor Provider exposes monitor information about the set of client connections that are established to the Directory Server.
+property.enabled.synopsis=Indicates whether the Client Connection Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Client Connection Monitor Provider implementation.
diff --git a/opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn.properties b/opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn.properties
new file mode 100644
index 0000000..4d1ddd4
--- /dev/null
+++ b/opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn.properties
@@ -0,0 +1,15 @@
+user-friendly-name=Config File Handler Backend
+user-friendly-plural-name=Config File Handler Backends
+synopsis=The Config File Handler Backend allows clients to access the server configuration over protocol, and allow both read and write operations. Note: Modify DN operations are not supported for entries in the server configuration.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_de.properties b/opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_de.properties
new file mode 100644
index 0000000..4d1ddd4
--- /dev/null
+++ b/opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_de.properties
@@ -0,0 +1,15 @@
+user-friendly-name=Config File Handler Backend
+user-friendly-plural-name=Config File Handler Backends
+synopsis=The Config File Handler Backend allows clients to access the server configuration over protocol, and allow both read and write operations. Note: Modify DN operations are not supported for entries in the server configuration.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_es.properties b/opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_es.properties
new file mode 100644
index 0000000..4d1ddd4
--- /dev/null
+++ b/opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_es.properties
@@ -0,0 +1,15 @@
+user-friendly-name=Config File Handler Backend
+user-friendly-plural-name=Config File Handler Backends
+synopsis=The Config File Handler Backend allows clients to access the server configuration over protocol, and allow both read and write operations. Note: Modify DN operations are not supported for entries in the server configuration.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_fr.properties b/opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_fr.properties
new file mode 100644
index 0000000..4d1ddd4
--- /dev/null
+++ b/opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_fr.properties
@@ -0,0 +1,15 @@
+user-friendly-name=Config File Handler Backend
+user-friendly-plural-name=Config File Handler Backends
+synopsis=The Config File Handler Backend allows clients to access the server configuration over protocol, and allow both read and write operations. Note: Modify DN operations are not supported for entries in the server configuration.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_ja.properties b/opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_ja.properties
new file mode 100644
index 0000000..4d1ddd4
--- /dev/null
+++ b/opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_ja.properties
@@ -0,0 +1,15 @@
+user-friendly-name=Config File Handler Backend
+user-friendly-plural-name=Config File Handler Backends
+synopsis=The Config File Handler Backend allows clients to access the server configuration over protocol, and allow both read and write operations. Note: Modify DN operations are not supported for entries in the server configuration.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_ko.properties b/opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_ko.properties
new file mode 100644
index 0000000..4d1ddd4
--- /dev/null
+++ b/opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_ko.properties
@@ -0,0 +1,15 @@
+user-friendly-name=Config File Handler Backend
+user-friendly-plural-name=Config File Handler Backends
+synopsis=The Config File Handler Backend allows clients to access the server configuration over protocol, and allow both read and write operations. Note: Modify DN operations are not supported for entries in the server configuration.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_zh_CN.properties b/opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..4d1ddd4
--- /dev/null
+++ b/opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_zh_CN.properties
@@ -0,0 +1,15 @@
+user-friendly-name=Config File Handler Backend
+user-friendly-plural-name=Config File Handler Backends
+synopsis=The Config File Handler Backend allows clients to access the server configuration over protocol, and allow both read and write operations. Note: Modify DN operations are not supported for entries in the server configuration.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_zh_TW.properties b/opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..4d1ddd4
--- /dev/null
+++ b/opends/src/admin/messages/ConfigFileHandlerBackendCfgDefn_zh_TW.properties
@@ -0,0 +1,15 @@
+user-friendly-name=Config File Handler Backend
+user-friendly-plural-name=Config File Handler Backends
+synopsis=The Config File Handler Backend allows clients to access the server configuration over protocol, and allow both read and write operations. Note: Modify DN operations are not supported for entries in the server configuration.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/ConnectionHandlerCfgDefn.properties b/opends/src/admin/messages/ConnectionHandlerCfgDefn.properties
new file mode 100644
index 0000000..2ee45c2
--- /dev/null
+++ b/opends/src/admin/messages/ConnectionHandlerCfgDefn.properties
@@ -0,0 +1,13 @@
+user-friendly-name=Connection Handler
+user-friendly-plural-name=Connection Handlers
+synopsis=Connection Handlers are responsible for handling all interaction with the clients, including accepting the connections, reading requests, and sending responses.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Connection Handler implementation.
diff --git a/opends/src/admin/messages/ConnectionHandlerCfgDefn_de.properties b/opends/src/admin/messages/ConnectionHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..2ee45c2
--- /dev/null
+++ b/opends/src/admin/messages/ConnectionHandlerCfgDefn_de.properties
@@ -0,0 +1,13 @@
+user-friendly-name=Connection Handler
+user-friendly-plural-name=Connection Handlers
+synopsis=Connection Handlers are responsible for handling all interaction with the clients, including accepting the connections, reading requests, and sending responses.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Connection Handler implementation.
diff --git a/opends/src/admin/messages/ConnectionHandlerCfgDefn_es.properties b/opends/src/admin/messages/ConnectionHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..2ee45c2
--- /dev/null
+++ b/opends/src/admin/messages/ConnectionHandlerCfgDefn_es.properties
@@ -0,0 +1,13 @@
+user-friendly-name=Connection Handler
+user-friendly-plural-name=Connection Handlers
+synopsis=Connection Handlers are responsible for handling all interaction with the clients, including accepting the connections, reading requests, and sending responses.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Connection Handler implementation.
diff --git a/opends/src/admin/messages/ConnectionHandlerCfgDefn_fr.properties b/opends/src/admin/messages/ConnectionHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..2ee45c2
--- /dev/null
+++ b/opends/src/admin/messages/ConnectionHandlerCfgDefn_fr.properties
@@ -0,0 +1,13 @@
+user-friendly-name=Connection Handler
+user-friendly-plural-name=Connection Handlers
+synopsis=Connection Handlers are responsible for handling all interaction with the clients, including accepting the connections, reading requests, and sending responses.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Connection Handler implementation.
diff --git a/opends/src/admin/messages/ConnectionHandlerCfgDefn_ja.properties b/opends/src/admin/messages/ConnectionHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..2ee45c2
--- /dev/null
+++ b/opends/src/admin/messages/ConnectionHandlerCfgDefn_ja.properties
@@ -0,0 +1,13 @@
+user-friendly-name=Connection Handler
+user-friendly-plural-name=Connection Handlers
+synopsis=Connection Handlers are responsible for handling all interaction with the clients, including accepting the connections, reading requests, and sending responses.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Connection Handler implementation.
diff --git a/opends/src/admin/messages/ConnectionHandlerCfgDefn_ko.properties b/opends/src/admin/messages/ConnectionHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..2ee45c2
--- /dev/null
+++ b/opends/src/admin/messages/ConnectionHandlerCfgDefn_ko.properties
@@ -0,0 +1,13 @@
+user-friendly-name=Connection Handler
+user-friendly-plural-name=Connection Handlers
+synopsis=Connection Handlers are responsible for handling all interaction with the clients, including accepting the connections, reading requests, and sending responses.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Connection Handler implementation.
diff --git a/opends/src/admin/messages/ConnectionHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/ConnectionHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..2ee45c2
--- /dev/null
+++ b/opends/src/admin/messages/ConnectionHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,13 @@
+user-friendly-name=Connection Handler
+user-friendly-plural-name=Connection Handlers
+synopsis=Connection Handlers are responsible for handling all interaction with the clients, including accepting the connections, reading requests, and sending responses.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Connection Handler implementation.
diff --git a/opends/src/admin/messages/ConnectionHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/ConnectionHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..2ee45c2
--- /dev/null
+++ b/opends/src/admin/messages/ConnectionHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,13 @@
+user-friendly-name=Connection Handler
+user-friendly-plural-name=Connection Handlers
+synopsis=Connection Handlers are responsible for handling all interaction with the clients, including accepting the connections, reading requests, and sending responses.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Connection Handler implementation.
diff --git a/opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn.properties b/opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn.properties
new file mode 100644
index 0000000..3e149fb
--- /dev/null
+++ b/opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Cram MD5 SASL Mechanism Handler
+user-friendly-plural-name=Cram MD5 SASL Mechanism Handlers
+synopsis=The CRAM-MD5 SASL mechanism provides the ability for clients to perform password-based authentication in a manner that does not expose their password in the clear.
+description=Rather than including the password in the bind request, the CRAM-MD5 mechanism uses a two-step process in which the client needs only to prove that it knows the password. The server sends randomly-generated data to the client that is to be used in the process, which makes it resistant to replay attacks. The one-way message digest algorithm ensures that the original clear-text password is not exposed. Note that the algorithm used by the CRAM-MD5 mechanism requires that both the client and the server have access to the clear-text password (or potentially a value that is derived from the clear-text password). In order to authenticate to the server using CRAM-MD5, the password for a user's account must be encoded using a reversible password storage scheme that allows the server to have access to the clear-text value.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper used with this SASL mechanism handler to match the authentication ID included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Cram MD5 SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_de.properties b/opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..3e149fb
--- /dev/null
+++ b/opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_de.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Cram MD5 SASL Mechanism Handler
+user-friendly-plural-name=Cram MD5 SASL Mechanism Handlers
+synopsis=The CRAM-MD5 SASL mechanism provides the ability for clients to perform password-based authentication in a manner that does not expose their password in the clear.
+description=Rather than including the password in the bind request, the CRAM-MD5 mechanism uses a two-step process in which the client needs only to prove that it knows the password. The server sends randomly-generated data to the client that is to be used in the process, which makes it resistant to replay attacks. The one-way message digest algorithm ensures that the original clear-text password is not exposed. Note that the algorithm used by the CRAM-MD5 mechanism requires that both the client and the server have access to the clear-text password (or potentially a value that is derived from the clear-text password). In order to authenticate to the server using CRAM-MD5, the password for a user's account must be encoded using a reversible password storage scheme that allows the server to have access to the clear-text value.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper used with this SASL mechanism handler to match the authentication ID included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Cram MD5 SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_es.properties b/opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..3e149fb
--- /dev/null
+++ b/opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_es.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Cram MD5 SASL Mechanism Handler
+user-friendly-plural-name=Cram MD5 SASL Mechanism Handlers
+synopsis=The CRAM-MD5 SASL mechanism provides the ability for clients to perform password-based authentication in a manner that does not expose their password in the clear.
+description=Rather than including the password in the bind request, the CRAM-MD5 mechanism uses a two-step process in which the client needs only to prove that it knows the password. The server sends randomly-generated data to the client that is to be used in the process, which makes it resistant to replay attacks. The one-way message digest algorithm ensures that the original clear-text password is not exposed. Note that the algorithm used by the CRAM-MD5 mechanism requires that both the client and the server have access to the clear-text password (or potentially a value that is derived from the clear-text password). In order to authenticate to the server using CRAM-MD5, the password for a user's account must be encoded using a reversible password storage scheme that allows the server to have access to the clear-text value.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper used with this SASL mechanism handler to match the authentication ID included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Cram MD5 SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_fr.properties b/opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..3e149fb
--- /dev/null
+++ b/opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_fr.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Cram MD5 SASL Mechanism Handler
+user-friendly-plural-name=Cram MD5 SASL Mechanism Handlers
+synopsis=The CRAM-MD5 SASL mechanism provides the ability for clients to perform password-based authentication in a manner that does not expose their password in the clear.
+description=Rather than including the password in the bind request, the CRAM-MD5 mechanism uses a two-step process in which the client needs only to prove that it knows the password. The server sends randomly-generated data to the client that is to be used in the process, which makes it resistant to replay attacks. The one-way message digest algorithm ensures that the original clear-text password is not exposed. Note that the algorithm used by the CRAM-MD5 mechanism requires that both the client and the server have access to the clear-text password (or potentially a value that is derived from the clear-text password). In order to authenticate to the server using CRAM-MD5, the password for a user's account must be encoded using a reversible password storage scheme that allows the server to have access to the clear-text value.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper used with this SASL mechanism handler to match the authentication ID included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Cram MD5 SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_ja.properties b/opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..3e149fb
--- /dev/null
+++ b/opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_ja.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Cram MD5 SASL Mechanism Handler
+user-friendly-plural-name=Cram MD5 SASL Mechanism Handlers
+synopsis=The CRAM-MD5 SASL mechanism provides the ability for clients to perform password-based authentication in a manner that does not expose their password in the clear.
+description=Rather than including the password in the bind request, the CRAM-MD5 mechanism uses a two-step process in which the client needs only to prove that it knows the password. The server sends randomly-generated data to the client that is to be used in the process, which makes it resistant to replay attacks. The one-way message digest algorithm ensures that the original clear-text password is not exposed. Note that the algorithm used by the CRAM-MD5 mechanism requires that both the client and the server have access to the clear-text password (or potentially a value that is derived from the clear-text password). In order to authenticate to the server using CRAM-MD5, the password for a user's account must be encoded using a reversible password storage scheme that allows the server to have access to the clear-text value.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper used with this SASL mechanism handler to match the authentication ID included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Cram MD5 SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_ko.properties b/opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..3e149fb
--- /dev/null
+++ b/opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_ko.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Cram MD5 SASL Mechanism Handler
+user-friendly-plural-name=Cram MD5 SASL Mechanism Handlers
+synopsis=The CRAM-MD5 SASL mechanism provides the ability for clients to perform password-based authentication in a manner that does not expose their password in the clear.
+description=Rather than including the password in the bind request, the CRAM-MD5 mechanism uses a two-step process in which the client needs only to prove that it knows the password. The server sends randomly-generated data to the client that is to be used in the process, which makes it resistant to replay attacks. The one-way message digest algorithm ensures that the original clear-text password is not exposed. Note that the algorithm used by the CRAM-MD5 mechanism requires that both the client and the server have access to the clear-text password (or potentially a value that is derived from the clear-text password). In order to authenticate to the server using CRAM-MD5, the password for a user's account must be encoded using a reversible password storage scheme that allows the server to have access to the clear-text value.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper used with this SASL mechanism handler to match the authentication ID included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Cram MD5 SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..3e149fb
--- /dev/null
+++ b/opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Cram MD5 SASL Mechanism Handler
+user-friendly-plural-name=Cram MD5 SASL Mechanism Handlers
+synopsis=The CRAM-MD5 SASL mechanism provides the ability for clients to perform password-based authentication in a manner that does not expose their password in the clear.
+description=Rather than including the password in the bind request, the CRAM-MD5 mechanism uses a two-step process in which the client needs only to prove that it knows the password. The server sends randomly-generated data to the client that is to be used in the process, which makes it resistant to replay attacks. The one-way message digest algorithm ensures that the original clear-text password is not exposed. Note that the algorithm used by the CRAM-MD5 mechanism requires that both the client and the server have access to the clear-text password (or potentially a value that is derived from the clear-text password). In order to authenticate to the server using CRAM-MD5, the password for a user's account must be encoded using a reversible password storage scheme that allows the server to have access to the clear-text value.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper used with this SASL mechanism handler to match the authentication ID included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Cram MD5 SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..3e149fb
--- /dev/null
+++ b/opends/src/admin/messages/CramMD5SASLMechanismHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Cram MD5 SASL Mechanism Handler
+user-friendly-plural-name=Cram MD5 SASL Mechanism Handlers
+synopsis=The CRAM-MD5 SASL mechanism provides the ability for clients to perform password-based authentication in a manner that does not expose their password in the clear.
+description=Rather than including the password in the bind request, the CRAM-MD5 mechanism uses a two-step process in which the client needs only to prove that it knows the password. The server sends randomly-generated data to the client that is to be used in the process, which makes it resistant to replay attacks. The one-way message digest algorithm ensures that the original clear-text password is not exposed. Note that the algorithm used by the CRAM-MD5 mechanism requires that both the client and the server have access to the clear-text password (or potentially a value that is derived from the clear-text password). In order to authenticate to the server using CRAM-MD5, the password for a user's account must be encoded using a reversible password storage scheme that allows the server to have access to the clear-text value.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper used with this SASL mechanism handler to match the authentication ID included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Cram MD5 SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn.properties b/opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn.properties
new file mode 100644
index 0000000..cef7031
--- /dev/null
+++ b/opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Crypt Password Storage Scheme
+user-friendly-plural-name=Crypt Password Storage Schemes
+synopsis=The Crypt Password Storage Scheme provides a mechanism for encoding user passwords using the UNIX crypt algorithm.
+description=This implementation contains only an implementation for the user password syntax, with a storage scheme name of "CRYPT". Even though it is a one-way digest, the Crypt Password Storage Scheme is relatively weak by today's standards. Because it supports only a 12-bit salt (meaning that there are only 4096 possible ways to encode a given password), it is also vulnerable to dictionary attacks. You should therefore use this storage scheme only in cases where an external application expects to retrieve the password and verify it outside of the directory, rather than by performing an LDAP bind.
+property.enabled.synopsis=Indicates whether the Crypt Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Crypt Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_de.properties b/opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_de.properties
new file mode 100644
index 0000000..cef7031
--- /dev/null
+++ b/opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Crypt Password Storage Scheme
+user-friendly-plural-name=Crypt Password Storage Schemes
+synopsis=The Crypt Password Storage Scheme provides a mechanism for encoding user passwords using the UNIX crypt algorithm.
+description=This implementation contains only an implementation for the user password syntax, with a storage scheme name of "CRYPT". Even though it is a one-way digest, the Crypt Password Storage Scheme is relatively weak by today's standards. Because it supports only a 12-bit salt (meaning that there are only 4096 possible ways to encode a given password), it is also vulnerable to dictionary attacks. You should therefore use this storage scheme only in cases where an external application expects to retrieve the password and verify it outside of the directory, rather than by performing an LDAP bind.
+property.enabled.synopsis=Indicates whether the Crypt Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Crypt Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_es.properties b/opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_es.properties
new file mode 100644
index 0000000..cef7031
--- /dev/null
+++ b/opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Crypt Password Storage Scheme
+user-friendly-plural-name=Crypt Password Storage Schemes
+synopsis=The Crypt Password Storage Scheme provides a mechanism for encoding user passwords using the UNIX crypt algorithm.
+description=This implementation contains only an implementation for the user password syntax, with a storage scheme name of "CRYPT". Even though it is a one-way digest, the Crypt Password Storage Scheme is relatively weak by today's standards. Because it supports only a 12-bit salt (meaning that there are only 4096 possible ways to encode a given password), it is also vulnerable to dictionary attacks. You should therefore use this storage scheme only in cases where an external application expects to retrieve the password and verify it outside of the directory, rather than by performing an LDAP bind.
+property.enabled.synopsis=Indicates whether the Crypt Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Crypt Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_fr.properties b/opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_fr.properties
new file mode 100644
index 0000000..cef7031
--- /dev/null
+++ b/opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Crypt Password Storage Scheme
+user-friendly-plural-name=Crypt Password Storage Schemes
+synopsis=The Crypt Password Storage Scheme provides a mechanism for encoding user passwords using the UNIX crypt algorithm.
+description=This implementation contains only an implementation for the user password syntax, with a storage scheme name of "CRYPT". Even though it is a one-way digest, the Crypt Password Storage Scheme is relatively weak by today's standards. Because it supports only a 12-bit salt (meaning that there are only 4096 possible ways to encode a given password), it is also vulnerable to dictionary attacks. You should therefore use this storage scheme only in cases where an external application expects to retrieve the password and verify it outside of the directory, rather than by performing an LDAP bind.
+property.enabled.synopsis=Indicates whether the Crypt Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Crypt Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_ja.properties b/opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_ja.properties
new file mode 100644
index 0000000..cef7031
--- /dev/null
+++ b/opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Crypt Password Storage Scheme
+user-friendly-plural-name=Crypt Password Storage Schemes
+synopsis=The Crypt Password Storage Scheme provides a mechanism for encoding user passwords using the UNIX crypt algorithm.
+description=This implementation contains only an implementation for the user password syntax, with a storage scheme name of "CRYPT". Even though it is a one-way digest, the Crypt Password Storage Scheme is relatively weak by today's standards. Because it supports only a 12-bit salt (meaning that there are only 4096 possible ways to encode a given password), it is also vulnerable to dictionary attacks. You should therefore use this storage scheme only in cases where an external application expects to retrieve the password and verify it outside of the directory, rather than by performing an LDAP bind.
+property.enabled.synopsis=Indicates whether the Crypt Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Crypt Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_ko.properties b/opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_ko.properties
new file mode 100644
index 0000000..cef7031
--- /dev/null
+++ b/opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Crypt Password Storage Scheme
+user-friendly-plural-name=Crypt Password Storage Schemes
+synopsis=The Crypt Password Storage Scheme provides a mechanism for encoding user passwords using the UNIX crypt algorithm.
+description=This implementation contains only an implementation for the user password syntax, with a storage scheme name of "CRYPT". Even though it is a one-way digest, the Crypt Password Storage Scheme is relatively weak by today's standards. Because it supports only a 12-bit salt (meaning that there are only 4096 possible ways to encode a given password), it is also vulnerable to dictionary attacks. You should therefore use this storage scheme only in cases where an external application expects to retrieve the password and verify it outside of the directory, rather than by performing an LDAP bind.
+property.enabled.synopsis=Indicates whether the Crypt Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Crypt Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_zh_CN.properties b/opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..cef7031
--- /dev/null
+++ b/opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Crypt Password Storage Scheme
+user-friendly-plural-name=Crypt Password Storage Schemes
+synopsis=The Crypt Password Storage Scheme provides a mechanism for encoding user passwords using the UNIX crypt algorithm.
+description=This implementation contains only an implementation for the user password syntax, with a storage scheme name of "CRYPT". Even though it is a one-way digest, the Crypt Password Storage Scheme is relatively weak by today's standards. Because it supports only a 12-bit salt (meaning that there are only 4096 possible ways to encode a given password), it is also vulnerable to dictionary attacks. You should therefore use this storage scheme only in cases where an external application expects to retrieve the password and verify it outside of the directory, rather than by performing an LDAP bind.
+property.enabled.synopsis=Indicates whether the Crypt Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Crypt Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_zh_TW.properties b/opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..cef7031
--- /dev/null
+++ b/opends/src/admin/messages/CryptPasswordStorageSchemeCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Crypt Password Storage Scheme
+user-friendly-plural-name=Crypt Password Storage Schemes
+synopsis=The Crypt Password Storage Scheme provides a mechanism for encoding user passwords using the UNIX crypt algorithm.
+description=This implementation contains only an implementation for the user password syntax, with a storage scheme name of "CRYPT". Even though it is a one-way digest, the Crypt Password Storage Scheme is relatively weak by today's standards. Because it supports only a 12-bit salt (meaning that there are only 4096 possible ways to encode a given password), it is also vulnerable to dictionary attacks. You should therefore use this storage scheme only in cases where an external application expects to retrieve the password and verify it outside of the directory, rather than by performing an LDAP bind.
+property.enabled.synopsis=Indicates whether the Crypt Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Crypt Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/CryptoManagerCfgDefn.properties b/opends/src/admin/messages/CryptoManagerCfgDefn.properties
new file mode 100644
index 0000000..a130bfd
--- /dev/null
+++ b/opends/src/admin/messages/CryptoManagerCfgDefn.properties
@@ -0,0 +1,27 @@
+user-friendly-name=Crypto Manager
+user-friendly-plural-name=Crypto Managers
+synopsis=The Crypto Manager provides a common interface for performing compression, decompression, hashing, encryption and other kinds of cryptographic operations.
+property.cipher-key-length.synopsis=Specifies the key length in bits for the preferred cipher.
+property.cipher-key-length.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.cipher-transformation.synopsis=Specifies the cipher for the Directory Server using the syntax algorithm/mode/padding.
+property.cipher-transformation.description=The full transformation is required: specifying only an algorithm and allowing the cipher provider to supply the default mode and padding is not supported, because there is no guarantee these default values are the same among different implementations. Some cipher algorithms, including RC4 and ARCFOUR, do not have a mode or padding, and hence must be specified using NONE for the mode field and NoPadding for the padding field. For example, RC4/NONE/NoPadding.
+property.cipher-transformation.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.digest-algorithm.synopsis=Specifies the preferred message digest algorithm for the Directory Server.
+property.digest-algorithm.requires-admin-action.synopsis=Changes to this property take effect immediately and only affect cryptographic operations performed after the change.
+property.key-wrapping-transformation.synopsis=The preferred key wrapping transformation for the Directory Server. This value must be the same for all server instances in a replication topology.
+property.key-wrapping-transformation.requires-admin-action.synopsis=Changes to this property will take effect immediately but will only affect cryptographic operations performed after the change.
+property.mac-algorithm.synopsis=Specifies the preferred MAC algorithm for the Directory Server.
+property.mac-algorithm.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.mac-key-length.synopsis=Specifies the key length in bits for the preferred MAC algorithm.
+property.mac-key-length.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the Crypto Manager should use when performing SSL communication.
+property.ssl-cert-nickname.description=This is only applicable when the Crypto Manager is configured to use SSL.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.ssl-cipher-suite.synopsis=Specifies the names of the SSL cipher suites that are allowed for use in SSL or TLS communication.
+property.ssl-cipher-suite.default-behavior.alias.synopsis=Uses the default set of SSL cipher suites provided by the server's JVM.
+property.ssl-cipher-suite.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
+property.ssl-encryption.synopsis=Specifies whether SSL/TLS is used to provide encrypted communication between two OpenDS server components.
+property.ssl-encryption.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
+property.ssl-protocol.synopsis=Specifies the names of the SSL protocols that are allowed for use in SSL or TLS communication.
+property.ssl-protocol.default-behavior.alias.synopsis=Uses the default set of SSL protocols provided by the server's JVM.
+property.ssl-protocol.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
diff --git a/opends/src/admin/messages/CryptoManagerCfgDefn_de.properties b/opends/src/admin/messages/CryptoManagerCfgDefn_de.properties
new file mode 100644
index 0000000..a130bfd
--- /dev/null
+++ b/opends/src/admin/messages/CryptoManagerCfgDefn_de.properties
@@ -0,0 +1,27 @@
+user-friendly-name=Crypto Manager
+user-friendly-plural-name=Crypto Managers
+synopsis=The Crypto Manager provides a common interface for performing compression, decompression, hashing, encryption and other kinds of cryptographic operations.
+property.cipher-key-length.synopsis=Specifies the key length in bits for the preferred cipher.
+property.cipher-key-length.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.cipher-transformation.synopsis=Specifies the cipher for the Directory Server using the syntax algorithm/mode/padding.
+property.cipher-transformation.description=The full transformation is required: specifying only an algorithm and allowing the cipher provider to supply the default mode and padding is not supported, because there is no guarantee these default values are the same among different implementations. Some cipher algorithms, including RC4 and ARCFOUR, do not have a mode or padding, and hence must be specified using NONE for the mode field and NoPadding for the padding field. For example, RC4/NONE/NoPadding.
+property.cipher-transformation.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.digest-algorithm.synopsis=Specifies the preferred message digest algorithm for the Directory Server.
+property.digest-algorithm.requires-admin-action.synopsis=Changes to this property take effect immediately and only affect cryptographic operations performed after the change.
+property.key-wrapping-transformation.synopsis=The preferred key wrapping transformation for the Directory Server. This value must be the same for all server instances in a replication topology.
+property.key-wrapping-transformation.requires-admin-action.synopsis=Changes to this property will take effect immediately but will only affect cryptographic operations performed after the change.
+property.mac-algorithm.synopsis=Specifies the preferred MAC algorithm for the Directory Server.
+property.mac-algorithm.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.mac-key-length.synopsis=Specifies the key length in bits for the preferred MAC algorithm.
+property.mac-key-length.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the Crypto Manager should use when performing SSL communication.
+property.ssl-cert-nickname.description=This is only applicable when the Crypto Manager is configured to use SSL.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.ssl-cipher-suite.synopsis=Specifies the names of the SSL cipher suites that are allowed for use in SSL or TLS communication.
+property.ssl-cipher-suite.default-behavior.alias.synopsis=Uses the default set of SSL cipher suites provided by the server's JVM.
+property.ssl-cipher-suite.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
+property.ssl-encryption.synopsis=Specifies whether SSL/TLS is used to provide encrypted communication between two OpenDS server components.
+property.ssl-encryption.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
+property.ssl-protocol.synopsis=Specifies the names of the SSL protocols that are allowed for use in SSL or TLS communication.
+property.ssl-protocol.default-behavior.alias.synopsis=Uses the default set of SSL protocols provided by the server's JVM.
+property.ssl-protocol.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
diff --git a/opends/src/admin/messages/CryptoManagerCfgDefn_es.properties b/opends/src/admin/messages/CryptoManagerCfgDefn_es.properties
new file mode 100644
index 0000000..a130bfd
--- /dev/null
+++ b/opends/src/admin/messages/CryptoManagerCfgDefn_es.properties
@@ -0,0 +1,27 @@
+user-friendly-name=Crypto Manager
+user-friendly-plural-name=Crypto Managers
+synopsis=The Crypto Manager provides a common interface for performing compression, decompression, hashing, encryption and other kinds of cryptographic operations.
+property.cipher-key-length.synopsis=Specifies the key length in bits for the preferred cipher.
+property.cipher-key-length.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.cipher-transformation.synopsis=Specifies the cipher for the Directory Server using the syntax algorithm/mode/padding.
+property.cipher-transformation.description=The full transformation is required: specifying only an algorithm and allowing the cipher provider to supply the default mode and padding is not supported, because there is no guarantee these default values are the same among different implementations. Some cipher algorithms, including RC4 and ARCFOUR, do not have a mode or padding, and hence must be specified using NONE for the mode field and NoPadding for the padding field. For example, RC4/NONE/NoPadding.
+property.cipher-transformation.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.digest-algorithm.synopsis=Specifies the preferred message digest algorithm for the Directory Server.
+property.digest-algorithm.requires-admin-action.synopsis=Changes to this property take effect immediately and only affect cryptographic operations performed after the change.
+property.key-wrapping-transformation.synopsis=The preferred key wrapping transformation for the Directory Server. This value must be the same for all server instances in a replication topology.
+property.key-wrapping-transformation.requires-admin-action.synopsis=Changes to this property will take effect immediately but will only affect cryptographic operations performed after the change.
+property.mac-algorithm.synopsis=Specifies the preferred MAC algorithm for the Directory Server.
+property.mac-algorithm.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.mac-key-length.synopsis=Specifies the key length in bits for the preferred MAC algorithm.
+property.mac-key-length.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the Crypto Manager should use when performing SSL communication.
+property.ssl-cert-nickname.description=This is only applicable when the Crypto Manager is configured to use SSL.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.ssl-cipher-suite.synopsis=Specifies the names of the SSL cipher suites that are allowed for use in SSL or TLS communication.
+property.ssl-cipher-suite.default-behavior.alias.synopsis=Uses the default set of SSL cipher suites provided by the server's JVM.
+property.ssl-cipher-suite.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
+property.ssl-encryption.synopsis=Specifies whether SSL/TLS is used to provide encrypted communication between two OpenDS server components.
+property.ssl-encryption.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
+property.ssl-protocol.synopsis=Specifies the names of the SSL protocols that are allowed for use in SSL or TLS communication.
+property.ssl-protocol.default-behavior.alias.synopsis=Uses the default set of SSL protocols provided by the server's JVM.
+property.ssl-protocol.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
diff --git a/opends/src/admin/messages/CryptoManagerCfgDefn_fr.properties b/opends/src/admin/messages/CryptoManagerCfgDefn_fr.properties
new file mode 100644
index 0000000..a130bfd
--- /dev/null
+++ b/opends/src/admin/messages/CryptoManagerCfgDefn_fr.properties
@@ -0,0 +1,27 @@
+user-friendly-name=Crypto Manager
+user-friendly-plural-name=Crypto Managers
+synopsis=The Crypto Manager provides a common interface for performing compression, decompression, hashing, encryption and other kinds of cryptographic operations.
+property.cipher-key-length.synopsis=Specifies the key length in bits for the preferred cipher.
+property.cipher-key-length.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.cipher-transformation.synopsis=Specifies the cipher for the Directory Server using the syntax algorithm/mode/padding.
+property.cipher-transformation.description=The full transformation is required: specifying only an algorithm and allowing the cipher provider to supply the default mode and padding is not supported, because there is no guarantee these default values are the same among different implementations. Some cipher algorithms, including RC4 and ARCFOUR, do not have a mode or padding, and hence must be specified using NONE for the mode field and NoPadding for the padding field. For example, RC4/NONE/NoPadding.
+property.cipher-transformation.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.digest-algorithm.synopsis=Specifies the preferred message digest algorithm for the Directory Server.
+property.digest-algorithm.requires-admin-action.synopsis=Changes to this property take effect immediately and only affect cryptographic operations performed after the change.
+property.key-wrapping-transformation.synopsis=The preferred key wrapping transformation for the Directory Server. This value must be the same for all server instances in a replication topology.
+property.key-wrapping-transformation.requires-admin-action.synopsis=Changes to this property will take effect immediately but will only affect cryptographic operations performed after the change.
+property.mac-algorithm.synopsis=Specifies the preferred MAC algorithm for the Directory Server.
+property.mac-algorithm.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.mac-key-length.synopsis=Specifies the key length in bits for the preferred MAC algorithm.
+property.mac-key-length.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the Crypto Manager should use when performing SSL communication.
+property.ssl-cert-nickname.description=This is only applicable when the Crypto Manager is configured to use SSL.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.ssl-cipher-suite.synopsis=Specifies the names of the SSL cipher suites that are allowed for use in SSL or TLS communication.
+property.ssl-cipher-suite.default-behavior.alias.synopsis=Uses the default set of SSL cipher suites provided by the server's JVM.
+property.ssl-cipher-suite.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
+property.ssl-encryption.synopsis=Specifies whether SSL/TLS is used to provide encrypted communication between two OpenDS server components.
+property.ssl-encryption.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
+property.ssl-protocol.synopsis=Specifies the names of the SSL protocols that are allowed for use in SSL or TLS communication.
+property.ssl-protocol.default-behavior.alias.synopsis=Uses the default set of SSL protocols provided by the server's JVM.
+property.ssl-protocol.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
diff --git a/opends/src/admin/messages/CryptoManagerCfgDefn_ja.properties b/opends/src/admin/messages/CryptoManagerCfgDefn_ja.properties
new file mode 100644
index 0000000..a130bfd
--- /dev/null
+++ b/opends/src/admin/messages/CryptoManagerCfgDefn_ja.properties
@@ -0,0 +1,27 @@
+user-friendly-name=Crypto Manager
+user-friendly-plural-name=Crypto Managers
+synopsis=The Crypto Manager provides a common interface for performing compression, decompression, hashing, encryption and other kinds of cryptographic operations.
+property.cipher-key-length.synopsis=Specifies the key length in bits for the preferred cipher.
+property.cipher-key-length.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.cipher-transformation.synopsis=Specifies the cipher for the Directory Server using the syntax algorithm/mode/padding.
+property.cipher-transformation.description=The full transformation is required: specifying only an algorithm and allowing the cipher provider to supply the default mode and padding is not supported, because there is no guarantee these default values are the same among different implementations. Some cipher algorithms, including RC4 and ARCFOUR, do not have a mode or padding, and hence must be specified using NONE for the mode field and NoPadding for the padding field. For example, RC4/NONE/NoPadding.
+property.cipher-transformation.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.digest-algorithm.synopsis=Specifies the preferred message digest algorithm for the Directory Server.
+property.digest-algorithm.requires-admin-action.synopsis=Changes to this property take effect immediately and only affect cryptographic operations performed after the change.
+property.key-wrapping-transformation.synopsis=The preferred key wrapping transformation for the Directory Server. This value must be the same for all server instances in a replication topology.
+property.key-wrapping-transformation.requires-admin-action.synopsis=Changes to this property will take effect immediately but will only affect cryptographic operations performed after the change.
+property.mac-algorithm.synopsis=Specifies the preferred MAC algorithm for the Directory Server.
+property.mac-algorithm.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.mac-key-length.synopsis=Specifies the key length in bits for the preferred MAC algorithm.
+property.mac-key-length.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the Crypto Manager should use when performing SSL communication.
+property.ssl-cert-nickname.description=This is only applicable when the Crypto Manager is configured to use SSL.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.ssl-cipher-suite.synopsis=Specifies the names of the SSL cipher suites that are allowed for use in SSL or TLS communication.
+property.ssl-cipher-suite.default-behavior.alias.synopsis=Uses the default set of SSL cipher suites provided by the server's JVM.
+property.ssl-cipher-suite.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
+property.ssl-encryption.synopsis=Specifies whether SSL/TLS is used to provide encrypted communication between two OpenDS server components.
+property.ssl-encryption.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
+property.ssl-protocol.synopsis=Specifies the names of the SSL protocols that are allowed for use in SSL or TLS communication.
+property.ssl-protocol.default-behavior.alias.synopsis=Uses the default set of SSL protocols provided by the server's JVM.
+property.ssl-protocol.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
diff --git a/opends/src/admin/messages/CryptoManagerCfgDefn_ko.properties b/opends/src/admin/messages/CryptoManagerCfgDefn_ko.properties
new file mode 100644
index 0000000..a130bfd
--- /dev/null
+++ b/opends/src/admin/messages/CryptoManagerCfgDefn_ko.properties
@@ -0,0 +1,27 @@
+user-friendly-name=Crypto Manager
+user-friendly-plural-name=Crypto Managers
+synopsis=The Crypto Manager provides a common interface for performing compression, decompression, hashing, encryption and other kinds of cryptographic operations.
+property.cipher-key-length.synopsis=Specifies the key length in bits for the preferred cipher.
+property.cipher-key-length.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.cipher-transformation.synopsis=Specifies the cipher for the Directory Server using the syntax algorithm/mode/padding.
+property.cipher-transformation.description=The full transformation is required: specifying only an algorithm and allowing the cipher provider to supply the default mode and padding is not supported, because there is no guarantee these default values are the same among different implementations. Some cipher algorithms, including RC4 and ARCFOUR, do not have a mode or padding, and hence must be specified using NONE for the mode field and NoPadding for the padding field. For example, RC4/NONE/NoPadding.
+property.cipher-transformation.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.digest-algorithm.synopsis=Specifies the preferred message digest algorithm for the Directory Server.
+property.digest-algorithm.requires-admin-action.synopsis=Changes to this property take effect immediately and only affect cryptographic operations performed after the change.
+property.key-wrapping-transformation.synopsis=The preferred key wrapping transformation for the Directory Server. This value must be the same for all server instances in a replication topology.
+property.key-wrapping-transformation.requires-admin-action.synopsis=Changes to this property will take effect immediately but will only affect cryptographic operations performed after the change.
+property.mac-algorithm.synopsis=Specifies the preferred MAC algorithm for the Directory Server.
+property.mac-algorithm.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.mac-key-length.synopsis=Specifies the key length in bits for the preferred MAC algorithm.
+property.mac-key-length.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the Crypto Manager should use when performing SSL communication.
+property.ssl-cert-nickname.description=This is only applicable when the Crypto Manager is configured to use SSL.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.ssl-cipher-suite.synopsis=Specifies the names of the SSL cipher suites that are allowed for use in SSL or TLS communication.
+property.ssl-cipher-suite.default-behavior.alias.synopsis=Uses the default set of SSL cipher suites provided by the server's JVM.
+property.ssl-cipher-suite.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
+property.ssl-encryption.synopsis=Specifies whether SSL/TLS is used to provide encrypted communication between two OpenDS server components.
+property.ssl-encryption.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
+property.ssl-protocol.synopsis=Specifies the names of the SSL protocols that are allowed for use in SSL or TLS communication.
+property.ssl-protocol.default-behavior.alias.synopsis=Uses the default set of SSL protocols provided by the server's JVM.
+property.ssl-protocol.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
diff --git a/opends/src/admin/messages/CryptoManagerCfgDefn_zh_CN.properties b/opends/src/admin/messages/CryptoManagerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..a130bfd
--- /dev/null
+++ b/opends/src/admin/messages/CryptoManagerCfgDefn_zh_CN.properties
@@ -0,0 +1,27 @@
+user-friendly-name=Crypto Manager
+user-friendly-plural-name=Crypto Managers
+synopsis=The Crypto Manager provides a common interface for performing compression, decompression, hashing, encryption and other kinds of cryptographic operations.
+property.cipher-key-length.synopsis=Specifies the key length in bits for the preferred cipher.
+property.cipher-key-length.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.cipher-transformation.synopsis=Specifies the cipher for the Directory Server using the syntax algorithm/mode/padding.
+property.cipher-transformation.description=The full transformation is required: specifying only an algorithm and allowing the cipher provider to supply the default mode and padding is not supported, because there is no guarantee these default values are the same among different implementations. Some cipher algorithms, including RC4 and ARCFOUR, do not have a mode or padding, and hence must be specified using NONE for the mode field and NoPadding for the padding field. For example, RC4/NONE/NoPadding.
+property.cipher-transformation.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.digest-algorithm.synopsis=Specifies the preferred message digest algorithm for the Directory Server.
+property.digest-algorithm.requires-admin-action.synopsis=Changes to this property take effect immediately and only affect cryptographic operations performed after the change.
+property.key-wrapping-transformation.synopsis=The preferred key wrapping transformation for the Directory Server. This value must be the same for all server instances in a replication topology.
+property.key-wrapping-transformation.requires-admin-action.synopsis=Changes to this property will take effect immediately but will only affect cryptographic operations performed after the change.
+property.mac-algorithm.synopsis=Specifies the preferred MAC algorithm for the Directory Server.
+property.mac-algorithm.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.mac-key-length.synopsis=Specifies the key length in bits for the preferred MAC algorithm.
+property.mac-key-length.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the Crypto Manager should use when performing SSL communication.
+property.ssl-cert-nickname.description=This is only applicable when the Crypto Manager is configured to use SSL.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.ssl-cipher-suite.synopsis=Specifies the names of the SSL cipher suites that are allowed for use in SSL or TLS communication.
+property.ssl-cipher-suite.default-behavior.alias.synopsis=Uses the default set of SSL cipher suites provided by the server's JVM.
+property.ssl-cipher-suite.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
+property.ssl-encryption.synopsis=Specifies whether SSL/TLS is used to provide encrypted communication between two OpenDS server components.
+property.ssl-encryption.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
+property.ssl-protocol.synopsis=Specifies the names of the SSL protocols that are allowed for use in SSL or TLS communication.
+property.ssl-protocol.default-behavior.alias.synopsis=Uses the default set of SSL protocols provided by the server's JVM.
+property.ssl-protocol.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
diff --git a/opends/src/admin/messages/CryptoManagerCfgDefn_zh_TW.properties b/opends/src/admin/messages/CryptoManagerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..a130bfd
--- /dev/null
+++ b/opends/src/admin/messages/CryptoManagerCfgDefn_zh_TW.properties
@@ -0,0 +1,27 @@
+user-friendly-name=Crypto Manager
+user-friendly-plural-name=Crypto Managers
+synopsis=The Crypto Manager provides a common interface for performing compression, decompression, hashing, encryption and other kinds of cryptographic operations.
+property.cipher-key-length.synopsis=Specifies the key length in bits for the preferred cipher.
+property.cipher-key-length.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.cipher-transformation.synopsis=Specifies the cipher for the Directory Server using the syntax algorithm/mode/padding.
+property.cipher-transformation.description=The full transformation is required: specifying only an algorithm and allowing the cipher provider to supply the default mode and padding is not supported, because there is no guarantee these default values are the same among different implementations. Some cipher algorithms, including RC4 and ARCFOUR, do not have a mode or padding, and hence must be specified using NONE for the mode field and NoPadding for the padding field. For example, RC4/NONE/NoPadding.
+property.cipher-transformation.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.digest-algorithm.synopsis=Specifies the preferred message digest algorithm for the Directory Server.
+property.digest-algorithm.requires-admin-action.synopsis=Changes to this property take effect immediately and only affect cryptographic operations performed after the change.
+property.key-wrapping-transformation.synopsis=The preferred key wrapping transformation for the Directory Server. This value must be the same for all server instances in a replication topology.
+property.key-wrapping-transformation.requires-admin-action.synopsis=Changes to this property will take effect immediately but will only affect cryptographic operations performed after the change.
+property.mac-algorithm.synopsis=Specifies the preferred MAC algorithm for the Directory Server.
+property.mac-algorithm.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.mac-key-length.synopsis=Specifies the key length in bits for the preferred MAC algorithm.
+property.mac-key-length.requires-admin-action.synopsis=Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the Crypto Manager should use when performing SSL communication.
+property.ssl-cert-nickname.description=This is only applicable when the Crypto Manager is configured to use SSL.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.ssl-cipher-suite.synopsis=Specifies the names of the SSL cipher suites that are allowed for use in SSL or TLS communication.
+property.ssl-cipher-suite.default-behavior.alias.synopsis=Uses the default set of SSL cipher suites provided by the server's JVM.
+property.ssl-cipher-suite.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
+property.ssl-encryption.synopsis=Specifies whether SSL/TLS is used to provide encrypted communication between two OpenDS server components.
+property.ssl-encryption.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
+property.ssl-protocol.synopsis=Specifies the names of the SSL protocols that are allowed for use in SSL or TLS communication.
+property.ssl-protocol.default-behavior.alias.synopsis=Uses the default set of SSL protocols provided by the server's JVM.
+property.ssl-protocol.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
diff --git a/opends/src/admin/messages/DebugLogPublisherCfgDefn.properties b/opends/src/admin/messages/DebugLogPublisherCfgDefn.properties
new file mode 100644
index 0000000..b218f2c
--- /dev/null
+++ b/opends/src/admin/messages/DebugLogPublisherCfgDefn.properties
@@ -0,0 +1,32 @@
+user-friendly-name=Debug Log Publisher
+user-friendly-plural-name=Debug Log Publishers
+synopsis=Debug Log Publishers are responsible for distributing debug log messages from the debug logger to a destination.
+description=Debug log messages provide information that can be used for debugging or troubleshooting problems in the server, or for providing more detailed information about the processing that the server performs.
+property.default-debug-category.synopsis=The debug message categories to be logged when none of the defined targets match the message.
+property.default-debug-category.default-behavior.alias.synopsis=Messages with any category will be logged if they have a sufficient debug level.
+property.default-debug-category.syntax.enumeration.value.caught.synopsis=Exception caught.
+property.default-debug-category.syntax.enumeration.value.constructor.synopsis=Constructor entry.
+property.default-debug-category.syntax.enumeration.value.data.synopsis=Raw data dump.
+property.default-debug-category.syntax.enumeration.value.database-access.synopsis=Access to a backend database.
+property.default-debug-category.syntax.enumeration.value.enter.synopsis=Method entry.
+property.default-debug-category.syntax.enumeration.value.exit.synopsis=Method exit.
+property.default-debug-category.syntax.enumeration.value.message.synopsis=Arbitrary debug message.
+property.default-debug-category.syntax.enumeration.value.protocol.synopsis=Protocol element dump.
+property.default-debug-category.syntax.enumeration.value.thrown.synopsis=Exception throw from method.
+property.default-debug-level.synopsis=The lowest severity level of debug messages to log when none of the defined targets match the message.
+property.default-debug-level.syntax.enumeration.value.all.synopsis=Messages with any severity level will be logged.
+property.default-debug-level.syntax.enumeration.value.disabled.synopsis=No messages will be logged.
+property.default-debug-level.syntax.enumeration.value.error.synopsis=Messages with severity level of ERROR or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.info.synopsis=Messages with severity level of INFO or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.verbose.synopsis=Messages with severity level of VERBOSE or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.warning.synopsis=Messages with severity level of WARNING or higher will be logged.
+property.default-include-throwable-cause.synopsis=Indicates whether to include the cause of exceptions in exception thrown and caught messages logged by default.
+property.default-omit-method-entry-arguments.synopsis=Indicates whether to include method arguments in debug messages logged by default.
+property.default-omit-method-return-value.synopsis=Indicates whether to include the return value in debug messages logged by default.
+property.default-throwable-stack-frames.synopsis=Indicates the number of stack frames to include in the stack trace for method entry and exception thrown messages.
+property.enabled.synopsis=Indicates whether the Debug Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Debug Log Publisher implementation.
+relation.debug-target.user-friendly-name=Debug Target
+relation.debug-target.user-friendly-plural-name=Debug Targets
+relation.debug-target.synopsis=Debug Targets define the types of messages logged by the debug logPublisher.
+relation.debug-target.description=Debug targets allow for fine-grain control of which messages are logged based on the package, class, or method that generated the message. Each debug target configuration entry resides below the entry with RDN of "cn=Debug Target" immediately below the parent ds-cfg-debug-log-publisher entry.
diff --git a/opends/src/admin/messages/DebugLogPublisherCfgDefn_de.properties b/opends/src/admin/messages/DebugLogPublisherCfgDefn_de.properties
new file mode 100644
index 0000000..b218f2c
--- /dev/null
+++ b/opends/src/admin/messages/DebugLogPublisherCfgDefn_de.properties
@@ -0,0 +1,32 @@
+user-friendly-name=Debug Log Publisher
+user-friendly-plural-name=Debug Log Publishers
+synopsis=Debug Log Publishers are responsible for distributing debug log messages from the debug logger to a destination.
+description=Debug log messages provide information that can be used for debugging or troubleshooting problems in the server, or for providing more detailed information about the processing that the server performs.
+property.default-debug-category.synopsis=The debug message categories to be logged when none of the defined targets match the message.
+property.default-debug-category.default-behavior.alias.synopsis=Messages with any category will be logged if they have a sufficient debug level.
+property.default-debug-category.syntax.enumeration.value.caught.synopsis=Exception caught.
+property.default-debug-category.syntax.enumeration.value.constructor.synopsis=Constructor entry.
+property.default-debug-category.syntax.enumeration.value.data.synopsis=Raw data dump.
+property.default-debug-category.syntax.enumeration.value.database-access.synopsis=Access to a backend database.
+property.default-debug-category.syntax.enumeration.value.enter.synopsis=Method entry.
+property.default-debug-category.syntax.enumeration.value.exit.synopsis=Method exit.
+property.default-debug-category.syntax.enumeration.value.message.synopsis=Arbitrary debug message.
+property.default-debug-category.syntax.enumeration.value.protocol.synopsis=Protocol element dump.
+property.default-debug-category.syntax.enumeration.value.thrown.synopsis=Exception throw from method.
+property.default-debug-level.synopsis=The lowest severity level of debug messages to log when none of the defined targets match the message.
+property.default-debug-level.syntax.enumeration.value.all.synopsis=Messages with any severity level will be logged.
+property.default-debug-level.syntax.enumeration.value.disabled.synopsis=No messages will be logged.
+property.default-debug-level.syntax.enumeration.value.error.synopsis=Messages with severity level of ERROR or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.info.synopsis=Messages with severity level of INFO or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.verbose.synopsis=Messages with severity level of VERBOSE or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.warning.synopsis=Messages with severity level of WARNING or higher will be logged.
+property.default-include-throwable-cause.synopsis=Indicates whether to include the cause of exceptions in exception thrown and caught messages logged by default.
+property.default-omit-method-entry-arguments.synopsis=Indicates whether to include method arguments in debug messages logged by default.
+property.default-omit-method-return-value.synopsis=Indicates whether to include the return value in debug messages logged by default.
+property.default-throwable-stack-frames.synopsis=Indicates the number of stack frames to include in the stack trace for method entry and exception thrown messages.
+property.enabled.synopsis=Indicates whether the Debug Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Debug Log Publisher implementation.
+relation.debug-target.user-friendly-name=Debug Target
+relation.debug-target.user-friendly-plural-name=Debug Targets
+relation.debug-target.synopsis=Debug Targets define the types of messages logged by the debug logPublisher.
+relation.debug-target.description=Debug targets allow for fine-grain control of which messages are logged based on the package, class, or method that generated the message. Each debug target configuration entry resides below the entry with RDN of "cn=Debug Target" immediately below the parent ds-cfg-debug-log-publisher entry.
diff --git a/opends/src/admin/messages/DebugLogPublisherCfgDefn_es.properties b/opends/src/admin/messages/DebugLogPublisherCfgDefn_es.properties
new file mode 100644
index 0000000..b218f2c
--- /dev/null
+++ b/opends/src/admin/messages/DebugLogPublisherCfgDefn_es.properties
@@ -0,0 +1,32 @@
+user-friendly-name=Debug Log Publisher
+user-friendly-plural-name=Debug Log Publishers
+synopsis=Debug Log Publishers are responsible for distributing debug log messages from the debug logger to a destination.
+description=Debug log messages provide information that can be used for debugging or troubleshooting problems in the server, or for providing more detailed information about the processing that the server performs.
+property.default-debug-category.synopsis=The debug message categories to be logged when none of the defined targets match the message.
+property.default-debug-category.default-behavior.alias.synopsis=Messages with any category will be logged if they have a sufficient debug level.
+property.default-debug-category.syntax.enumeration.value.caught.synopsis=Exception caught.
+property.default-debug-category.syntax.enumeration.value.constructor.synopsis=Constructor entry.
+property.default-debug-category.syntax.enumeration.value.data.synopsis=Raw data dump.
+property.default-debug-category.syntax.enumeration.value.database-access.synopsis=Access to a backend database.
+property.default-debug-category.syntax.enumeration.value.enter.synopsis=Method entry.
+property.default-debug-category.syntax.enumeration.value.exit.synopsis=Method exit.
+property.default-debug-category.syntax.enumeration.value.message.synopsis=Arbitrary debug message.
+property.default-debug-category.syntax.enumeration.value.protocol.synopsis=Protocol element dump.
+property.default-debug-category.syntax.enumeration.value.thrown.synopsis=Exception throw from method.
+property.default-debug-level.synopsis=The lowest severity level of debug messages to log when none of the defined targets match the message.
+property.default-debug-level.syntax.enumeration.value.all.synopsis=Messages with any severity level will be logged.
+property.default-debug-level.syntax.enumeration.value.disabled.synopsis=No messages will be logged.
+property.default-debug-level.syntax.enumeration.value.error.synopsis=Messages with severity level of ERROR or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.info.synopsis=Messages with severity level of INFO or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.verbose.synopsis=Messages with severity level of VERBOSE or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.warning.synopsis=Messages with severity level of WARNING or higher will be logged.
+property.default-include-throwable-cause.synopsis=Indicates whether to include the cause of exceptions in exception thrown and caught messages logged by default.
+property.default-omit-method-entry-arguments.synopsis=Indicates whether to include method arguments in debug messages logged by default.
+property.default-omit-method-return-value.synopsis=Indicates whether to include the return value in debug messages logged by default.
+property.default-throwable-stack-frames.synopsis=Indicates the number of stack frames to include in the stack trace for method entry and exception thrown messages.
+property.enabled.synopsis=Indicates whether the Debug Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Debug Log Publisher implementation.
+relation.debug-target.user-friendly-name=Debug Target
+relation.debug-target.user-friendly-plural-name=Debug Targets
+relation.debug-target.synopsis=Debug Targets define the types of messages logged by the debug logPublisher.
+relation.debug-target.description=Debug targets allow for fine-grain control of which messages are logged based on the package, class, or method that generated the message. Each debug target configuration entry resides below the entry with RDN of "cn=Debug Target" immediately below the parent ds-cfg-debug-log-publisher entry.
diff --git a/opends/src/admin/messages/DebugLogPublisherCfgDefn_fr.properties b/opends/src/admin/messages/DebugLogPublisherCfgDefn_fr.properties
new file mode 100644
index 0000000..b218f2c
--- /dev/null
+++ b/opends/src/admin/messages/DebugLogPublisherCfgDefn_fr.properties
@@ -0,0 +1,32 @@
+user-friendly-name=Debug Log Publisher
+user-friendly-plural-name=Debug Log Publishers
+synopsis=Debug Log Publishers are responsible for distributing debug log messages from the debug logger to a destination.
+description=Debug log messages provide information that can be used for debugging or troubleshooting problems in the server, or for providing more detailed information about the processing that the server performs.
+property.default-debug-category.synopsis=The debug message categories to be logged when none of the defined targets match the message.
+property.default-debug-category.default-behavior.alias.synopsis=Messages with any category will be logged if they have a sufficient debug level.
+property.default-debug-category.syntax.enumeration.value.caught.synopsis=Exception caught.
+property.default-debug-category.syntax.enumeration.value.constructor.synopsis=Constructor entry.
+property.default-debug-category.syntax.enumeration.value.data.synopsis=Raw data dump.
+property.default-debug-category.syntax.enumeration.value.database-access.synopsis=Access to a backend database.
+property.default-debug-category.syntax.enumeration.value.enter.synopsis=Method entry.
+property.default-debug-category.syntax.enumeration.value.exit.synopsis=Method exit.
+property.default-debug-category.syntax.enumeration.value.message.synopsis=Arbitrary debug message.
+property.default-debug-category.syntax.enumeration.value.protocol.synopsis=Protocol element dump.
+property.default-debug-category.syntax.enumeration.value.thrown.synopsis=Exception throw from method.
+property.default-debug-level.synopsis=The lowest severity level of debug messages to log when none of the defined targets match the message.
+property.default-debug-level.syntax.enumeration.value.all.synopsis=Messages with any severity level will be logged.
+property.default-debug-level.syntax.enumeration.value.disabled.synopsis=No messages will be logged.
+property.default-debug-level.syntax.enumeration.value.error.synopsis=Messages with severity level of ERROR or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.info.synopsis=Messages with severity level of INFO or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.verbose.synopsis=Messages with severity level of VERBOSE or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.warning.synopsis=Messages with severity level of WARNING or higher will be logged.
+property.default-include-throwable-cause.synopsis=Indicates whether to include the cause of exceptions in exception thrown and caught messages logged by default.
+property.default-omit-method-entry-arguments.synopsis=Indicates whether to include method arguments in debug messages logged by default.
+property.default-omit-method-return-value.synopsis=Indicates whether to include the return value in debug messages logged by default.
+property.default-throwable-stack-frames.synopsis=Indicates the number of stack frames to include in the stack trace for method entry and exception thrown messages.
+property.enabled.synopsis=Indicates whether the Debug Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Debug Log Publisher implementation.
+relation.debug-target.user-friendly-name=Debug Target
+relation.debug-target.user-friendly-plural-name=Debug Targets
+relation.debug-target.synopsis=Debug Targets define the types of messages logged by the debug logPublisher.
+relation.debug-target.description=Debug targets allow for fine-grain control of which messages are logged based on the package, class, or method that generated the message. Each debug target configuration entry resides below the entry with RDN of "cn=Debug Target" immediately below the parent ds-cfg-debug-log-publisher entry.
diff --git a/opends/src/admin/messages/DebugLogPublisherCfgDefn_ja.properties b/opends/src/admin/messages/DebugLogPublisherCfgDefn_ja.properties
new file mode 100644
index 0000000..b218f2c
--- /dev/null
+++ b/opends/src/admin/messages/DebugLogPublisherCfgDefn_ja.properties
@@ -0,0 +1,32 @@
+user-friendly-name=Debug Log Publisher
+user-friendly-plural-name=Debug Log Publishers
+synopsis=Debug Log Publishers are responsible for distributing debug log messages from the debug logger to a destination.
+description=Debug log messages provide information that can be used for debugging or troubleshooting problems in the server, or for providing more detailed information about the processing that the server performs.
+property.default-debug-category.synopsis=The debug message categories to be logged when none of the defined targets match the message.
+property.default-debug-category.default-behavior.alias.synopsis=Messages with any category will be logged if they have a sufficient debug level.
+property.default-debug-category.syntax.enumeration.value.caught.synopsis=Exception caught.
+property.default-debug-category.syntax.enumeration.value.constructor.synopsis=Constructor entry.
+property.default-debug-category.syntax.enumeration.value.data.synopsis=Raw data dump.
+property.default-debug-category.syntax.enumeration.value.database-access.synopsis=Access to a backend database.
+property.default-debug-category.syntax.enumeration.value.enter.synopsis=Method entry.
+property.default-debug-category.syntax.enumeration.value.exit.synopsis=Method exit.
+property.default-debug-category.syntax.enumeration.value.message.synopsis=Arbitrary debug message.
+property.default-debug-category.syntax.enumeration.value.protocol.synopsis=Protocol element dump.
+property.default-debug-category.syntax.enumeration.value.thrown.synopsis=Exception throw from method.
+property.default-debug-level.synopsis=The lowest severity level of debug messages to log when none of the defined targets match the message.
+property.default-debug-level.syntax.enumeration.value.all.synopsis=Messages with any severity level will be logged.
+property.default-debug-level.syntax.enumeration.value.disabled.synopsis=No messages will be logged.
+property.default-debug-level.syntax.enumeration.value.error.synopsis=Messages with severity level of ERROR or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.info.synopsis=Messages with severity level of INFO or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.verbose.synopsis=Messages with severity level of VERBOSE or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.warning.synopsis=Messages with severity level of WARNING or higher will be logged.
+property.default-include-throwable-cause.synopsis=Indicates whether to include the cause of exceptions in exception thrown and caught messages logged by default.
+property.default-omit-method-entry-arguments.synopsis=Indicates whether to include method arguments in debug messages logged by default.
+property.default-omit-method-return-value.synopsis=Indicates whether to include the return value in debug messages logged by default.
+property.default-throwable-stack-frames.synopsis=Indicates the number of stack frames to include in the stack trace for method entry and exception thrown messages.
+property.enabled.synopsis=Indicates whether the Debug Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Debug Log Publisher implementation.
+relation.debug-target.user-friendly-name=Debug Target
+relation.debug-target.user-friendly-plural-name=Debug Targets
+relation.debug-target.synopsis=Debug Targets define the types of messages logged by the debug logPublisher.
+relation.debug-target.description=Debug targets allow for fine-grain control of which messages are logged based on the package, class, or method that generated the message. Each debug target configuration entry resides below the entry with RDN of "cn=Debug Target" immediately below the parent ds-cfg-debug-log-publisher entry.
diff --git a/opends/src/admin/messages/DebugLogPublisherCfgDefn_ko.properties b/opends/src/admin/messages/DebugLogPublisherCfgDefn_ko.properties
new file mode 100644
index 0000000..b218f2c
--- /dev/null
+++ b/opends/src/admin/messages/DebugLogPublisherCfgDefn_ko.properties
@@ -0,0 +1,32 @@
+user-friendly-name=Debug Log Publisher
+user-friendly-plural-name=Debug Log Publishers
+synopsis=Debug Log Publishers are responsible for distributing debug log messages from the debug logger to a destination.
+description=Debug log messages provide information that can be used for debugging or troubleshooting problems in the server, or for providing more detailed information about the processing that the server performs.
+property.default-debug-category.synopsis=The debug message categories to be logged when none of the defined targets match the message.
+property.default-debug-category.default-behavior.alias.synopsis=Messages with any category will be logged if they have a sufficient debug level.
+property.default-debug-category.syntax.enumeration.value.caught.synopsis=Exception caught.
+property.default-debug-category.syntax.enumeration.value.constructor.synopsis=Constructor entry.
+property.default-debug-category.syntax.enumeration.value.data.synopsis=Raw data dump.
+property.default-debug-category.syntax.enumeration.value.database-access.synopsis=Access to a backend database.
+property.default-debug-category.syntax.enumeration.value.enter.synopsis=Method entry.
+property.default-debug-category.syntax.enumeration.value.exit.synopsis=Method exit.
+property.default-debug-category.syntax.enumeration.value.message.synopsis=Arbitrary debug message.
+property.default-debug-category.syntax.enumeration.value.protocol.synopsis=Protocol element dump.
+property.default-debug-category.syntax.enumeration.value.thrown.synopsis=Exception throw from method.
+property.default-debug-level.synopsis=The lowest severity level of debug messages to log when none of the defined targets match the message.
+property.default-debug-level.syntax.enumeration.value.all.synopsis=Messages with any severity level will be logged.
+property.default-debug-level.syntax.enumeration.value.disabled.synopsis=No messages will be logged.
+property.default-debug-level.syntax.enumeration.value.error.synopsis=Messages with severity level of ERROR or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.info.synopsis=Messages with severity level of INFO or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.verbose.synopsis=Messages with severity level of VERBOSE or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.warning.synopsis=Messages with severity level of WARNING or higher will be logged.
+property.default-include-throwable-cause.synopsis=Indicates whether to include the cause of exceptions in exception thrown and caught messages logged by default.
+property.default-omit-method-entry-arguments.synopsis=Indicates whether to include method arguments in debug messages logged by default.
+property.default-omit-method-return-value.synopsis=Indicates whether to include the return value in debug messages logged by default.
+property.default-throwable-stack-frames.synopsis=Indicates the number of stack frames to include in the stack trace for method entry and exception thrown messages.
+property.enabled.synopsis=Indicates whether the Debug Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Debug Log Publisher implementation.
+relation.debug-target.user-friendly-name=Debug Target
+relation.debug-target.user-friendly-plural-name=Debug Targets
+relation.debug-target.synopsis=Debug Targets define the types of messages logged by the debug logPublisher.
+relation.debug-target.description=Debug targets allow for fine-grain control of which messages are logged based on the package, class, or method that generated the message. Each debug target configuration entry resides below the entry with RDN of "cn=Debug Target" immediately below the parent ds-cfg-debug-log-publisher entry.
diff --git a/opends/src/admin/messages/DebugLogPublisherCfgDefn_zh_CN.properties b/opends/src/admin/messages/DebugLogPublisherCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..b218f2c
--- /dev/null
+++ b/opends/src/admin/messages/DebugLogPublisherCfgDefn_zh_CN.properties
@@ -0,0 +1,32 @@
+user-friendly-name=Debug Log Publisher
+user-friendly-plural-name=Debug Log Publishers
+synopsis=Debug Log Publishers are responsible for distributing debug log messages from the debug logger to a destination.
+description=Debug log messages provide information that can be used for debugging or troubleshooting problems in the server, or for providing more detailed information about the processing that the server performs.
+property.default-debug-category.synopsis=The debug message categories to be logged when none of the defined targets match the message.
+property.default-debug-category.default-behavior.alias.synopsis=Messages with any category will be logged if they have a sufficient debug level.
+property.default-debug-category.syntax.enumeration.value.caught.synopsis=Exception caught.
+property.default-debug-category.syntax.enumeration.value.constructor.synopsis=Constructor entry.
+property.default-debug-category.syntax.enumeration.value.data.synopsis=Raw data dump.
+property.default-debug-category.syntax.enumeration.value.database-access.synopsis=Access to a backend database.
+property.default-debug-category.syntax.enumeration.value.enter.synopsis=Method entry.
+property.default-debug-category.syntax.enumeration.value.exit.synopsis=Method exit.
+property.default-debug-category.syntax.enumeration.value.message.synopsis=Arbitrary debug message.
+property.default-debug-category.syntax.enumeration.value.protocol.synopsis=Protocol element dump.
+property.default-debug-category.syntax.enumeration.value.thrown.synopsis=Exception throw from method.
+property.default-debug-level.synopsis=The lowest severity level of debug messages to log when none of the defined targets match the message.
+property.default-debug-level.syntax.enumeration.value.all.synopsis=Messages with any severity level will be logged.
+property.default-debug-level.syntax.enumeration.value.disabled.synopsis=No messages will be logged.
+property.default-debug-level.syntax.enumeration.value.error.synopsis=Messages with severity level of ERROR or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.info.synopsis=Messages with severity level of INFO or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.verbose.synopsis=Messages with severity level of VERBOSE or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.warning.synopsis=Messages with severity level of WARNING or higher will be logged.
+property.default-include-throwable-cause.synopsis=Indicates whether to include the cause of exceptions in exception thrown and caught messages logged by default.
+property.default-omit-method-entry-arguments.synopsis=Indicates whether to include method arguments in debug messages logged by default.
+property.default-omit-method-return-value.synopsis=Indicates whether to include the return value in debug messages logged by default.
+property.default-throwable-stack-frames.synopsis=Indicates the number of stack frames to include in the stack trace for method entry and exception thrown messages.
+property.enabled.synopsis=Indicates whether the Debug Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Debug Log Publisher implementation.
+relation.debug-target.user-friendly-name=Debug Target
+relation.debug-target.user-friendly-plural-name=Debug Targets
+relation.debug-target.synopsis=Debug Targets define the types of messages logged by the debug logPublisher.
+relation.debug-target.description=Debug targets allow for fine-grain control of which messages are logged based on the package, class, or method that generated the message. Each debug target configuration entry resides below the entry with RDN of "cn=Debug Target" immediately below the parent ds-cfg-debug-log-publisher entry.
diff --git a/opends/src/admin/messages/DebugLogPublisherCfgDefn_zh_TW.properties b/opends/src/admin/messages/DebugLogPublisherCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..b218f2c
--- /dev/null
+++ b/opends/src/admin/messages/DebugLogPublisherCfgDefn_zh_TW.properties
@@ -0,0 +1,32 @@
+user-friendly-name=Debug Log Publisher
+user-friendly-plural-name=Debug Log Publishers
+synopsis=Debug Log Publishers are responsible for distributing debug log messages from the debug logger to a destination.
+description=Debug log messages provide information that can be used for debugging or troubleshooting problems in the server, or for providing more detailed information about the processing that the server performs.
+property.default-debug-category.synopsis=The debug message categories to be logged when none of the defined targets match the message.
+property.default-debug-category.default-behavior.alias.synopsis=Messages with any category will be logged if they have a sufficient debug level.
+property.default-debug-category.syntax.enumeration.value.caught.synopsis=Exception caught.
+property.default-debug-category.syntax.enumeration.value.constructor.synopsis=Constructor entry.
+property.default-debug-category.syntax.enumeration.value.data.synopsis=Raw data dump.
+property.default-debug-category.syntax.enumeration.value.database-access.synopsis=Access to a backend database.
+property.default-debug-category.syntax.enumeration.value.enter.synopsis=Method entry.
+property.default-debug-category.syntax.enumeration.value.exit.synopsis=Method exit.
+property.default-debug-category.syntax.enumeration.value.message.synopsis=Arbitrary debug message.
+property.default-debug-category.syntax.enumeration.value.protocol.synopsis=Protocol element dump.
+property.default-debug-category.syntax.enumeration.value.thrown.synopsis=Exception throw from method.
+property.default-debug-level.synopsis=The lowest severity level of debug messages to log when none of the defined targets match the message.
+property.default-debug-level.syntax.enumeration.value.all.synopsis=Messages with any severity level will be logged.
+property.default-debug-level.syntax.enumeration.value.disabled.synopsis=No messages will be logged.
+property.default-debug-level.syntax.enumeration.value.error.synopsis=Messages with severity level of ERROR or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.info.synopsis=Messages with severity level of INFO or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.verbose.synopsis=Messages with severity level of VERBOSE or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.warning.synopsis=Messages with severity level of WARNING or higher will be logged.
+property.default-include-throwable-cause.synopsis=Indicates whether to include the cause of exceptions in exception thrown and caught messages logged by default.
+property.default-omit-method-entry-arguments.synopsis=Indicates whether to include method arguments in debug messages logged by default.
+property.default-omit-method-return-value.synopsis=Indicates whether to include the return value in debug messages logged by default.
+property.default-throwable-stack-frames.synopsis=Indicates the number of stack frames to include in the stack trace for method entry and exception thrown messages.
+property.enabled.synopsis=Indicates whether the Debug Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Debug Log Publisher implementation.
+relation.debug-target.user-friendly-name=Debug Target
+relation.debug-target.user-friendly-plural-name=Debug Targets
+relation.debug-target.synopsis=Debug Targets define the types of messages logged by the debug logPublisher.
+relation.debug-target.description=Debug targets allow for fine-grain control of which messages are logged based on the package, class, or method that generated the message. Each debug target configuration entry resides below the entry with RDN of "cn=Debug Target" immediately below the parent ds-cfg-debug-log-publisher entry.
diff --git a/opends/src/admin/messages/DebugTargetCfgDefn.properties b/opends/src/admin/messages/DebugTargetCfgDefn.properties
new file mode 100644
index 0000000..ebe7a3e
--- /dev/null
+++ b/opends/src/admin/messages/DebugTargetCfgDefn.properties
@@ -0,0 +1,28 @@
+user-friendly-name=Debug Target
+user-friendly-plural-name=Debug Targets
+synopsis=Debug Targets define the types of messages logged by the debug logPublisher.
+description=Debug targets allow for fine-grain control of which messages are logged based on the package, class, or method that generated the message. Each debug target configuration entry resides below the entry with RDN of "cn=Debug Target" immediately below the parent ds-cfg-debug-log-publisher entry.
+property.debug-category.synopsis=Specifies the debug message categories to be logged.
+property.debug-category.default-behavior.alias.synopsis=Messages with any category are logged if they have a sufficient debug level.
+property.debug-category.syntax.enumeration.value.caught.synopsis=Exception caught
+property.debug-category.syntax.enumeration.value.constructor.synopsis=Constructor entry
+property.debug-category.syntax.enumeration.value.data.synopsis=Raw data dump
+property.debug-category.syntax.enumeration.value.database-access.synopsis=Access to a backend database.
+property.debug-category.syntax.enumeration.value.enter.synopsis=Method entry
+property.debug-category.syntax.enumeration.value.exit.synopsis=Method exit
+property.debug-category.syntax.enumeration.value.message.synopsis=Arbitrary debug message
+property.debug-category.syntax.enumeration.value.protocol.synopsis=Protocol element dump
+property.debug-category.syntax.enumeration.value.thrown.synopsis=Exception throw from method
+property.debug-level.synopsis=Specifies the lowest severity level of debug messages to log.
+property.debug-level.syntax.enumeration.value.all.synopsis=Messages with any severity level are logged.
+property.debug-level.syntax.enumeration.value.disabled.synopsis=No messages are logged.
+property.debug-level.syntax.enumeration.value.error.synopsis=Messages with severity level of ERROR or higher are logged.
+property.debug-level.syntax.enumeration.value.info.synopsis=Messages with severity level of INFO or higher are logged.
+property.debug-level.syntax.enumeration.value.verbose.synopsis=Messages with severity level of VERBOSE or higher are logged.
+property.debug-level.syntax.enumeration.value.warning.synopsis=Messages with severity level of WARNING or higher are logged.
+property.debug-scope.synopsis=Specifies the fully-qualified OpenDS Java package, class, or method affected by the settings in this target definition. Use the number character (#) to separate the class name and the method name (that is, org.opends.server.core.DirectoryServer#startUp).
+property.debug-scope.syntax.string.pattern.synopsis=The fully-qualified OpenDS Java package, class, or method name.
+property.include-throwable-cause.synopsis=Specifies the property to indicate whether to include the cause of exceptions in exception thrown and caught messages.
+property.omit-method-entry-arguments.synopsis=Specifies the property to indicate whether to include method arguments in debug messages.
+property.omit-method-return-value.synopsis=Specifies the property to indicate whether to include the return value in debug messages.
+property.throwable-stack-frames.synopsis=Specifies the property to indicate the number of stack frames to include in the stack trace for method entry and exception thrown messages.
diff --git a/opends/src/admin/messages/DebugTargetCfgDefn_de.properties b/opends/src/admin/messages/DebugTargetCfgDefn_de.properties
new file mode 100644
index 0000000..ebe7a3e
--- /dev/null
+++ b/opends/src/admin/messages/DebugTargetCfgDefn_de.properties
@@ -0,0 +1,28 @@
+user-friendly-name=Debug Target
+user-friendly-plural-name=Debug Targets
+synopsis=Debug Targets define the types of messages logged by the debug logPublisher.
+description=Debug targets allow for fine-grain control of which messages are logged based on the package, class, or method that generated the message. Each debug target configuration entry resides below the entry with RDN of "cn=Debug Target" immediately below the parent ds-cfg-debug-log-publisher entry.
+property.debug-category.synopsis=Specifies the debug message categories to be logged.
+property.debug-category.default-behavior.alias.synopsis=Messages with any category are logged if they have a sufficient debug level.
+property.debug-category.syntax.enumeration.value.caught.synopsis=Exception caught
+property.debug-category.syntax.enumeration.value.constructor.synopsis=Constructor entry
+property.debug-category.syntax.enumeration.value.data.synopsis=Raw data dump
+property.debug-category.syntax.enumeration.value.database-access.synopsis=Access to a backend database.
+property.debug-category.syntax.enumeration.value.enter.synopsis=Method entry
+property.debug-category.syntax.enumeration.value.exit.synopsis=Method exit
+property.debug-category.syntax.enumeration.value.message.synopsis=Arbitrary debug message
+property.debug-category.syntax.enumeration.value.protocol.synopsis=Protocol element dump
+property.debug-category.syntax.enumeration.value.thrown.synopsis=Exception throw from method
+property.debug-level.synopsis=Specifies the lowest severity level of debug messages to log.
+property.debug-level.syntax.enumeration.value.all.synopsis=Messages with any severity level are logged.
+property.debug-level.syntax.enumeration.value.disabled.synopsis=No messages are logged.
+property.debug-level.syntax.enumeration.value.error.synopsis=Messages with severity level of ERROR or higher are logged.
+property.debug-level.syntax.enumeration.value.info.synopsis=Messages with severity level of INFO or higher are logged.
+property.debug-level.syntax.enumeration.value.verbose.synopsis=Messages with severity level of VERBOSE or higher are logged.
+property.debug-level.syntax.enumeration.value.warning.synopsis=Messages with severity level of WARNING or higher are logged.
+property.debug-scope.synopsis=Specifies the fully-qualified OpenDS Java package, class, or method affected by the settings in this target definition. Use the number character (#) to separate the class name and the method name (that is, org.opends.server.core.DirectoryServer#startUp).
+property.debug-scope.syntax.string.pattern.synopsis=The fully-qualified OpenDS Java package, class, or method name.
+property.include-throwable-cause.synopsis=Specifies the property to indicate whether to include the cause of exceptions in exception thrown and caught messages.
+property.omit-method-entry-arguments.synopsis=Specifies the property to indicate whether to include method arguments in debug messages.
+property.omit-method-return-value.synopsis=Specifies the property to indicate whether to include the return value in debug messages.
+property.throwable-stack-frames.synopsis=Specifies the property to indicate the number of stack frames to include in the stack trace for method entry and exception thrown messages.
diff --git a/opends/src/admin/messages/DebugTargetCfgDefn_es.properties b/opends/src/admin/messages/DebugTargetCfgDefn_es.properties
new file mode 100644
index 0000000..ebe7a3e
--- /dev/null
+++ b/opends/src/admin/messages/DebugTargetCfgDefn_es.properties
@@ -0,0 +1,28 @@
+user-friendly-name=Debug Target
+user-friendly-plural-name=Debug Targets
+synopsis=Debug Targets define the types of messages logged by the debug logPublisher.
+description=Debug targets allow for fine-grain control of which messages are logged based on the package, class, or method that generated the message. Each debug target configuration entry resides below the entry with RDN of "cn=Debug Target" immediately below the parent ds-cfg-debug-log-publisher entry.
+property.debug-category.synopsis=Specifies the debug message categories to be logged.
+property.debug-category.default-behavior.alias.synopsis=Messages with any category are logged if they have a sufficient debug level.
+property.debug-category.syntax.enumeration.value.caught.synopsis=Exception caught
+property.debug-category.syntax.enumeration.value.constructor.synopsis=Constructor entry
+property.debug-category.syntax.enumeration.value.data.synopsis=Raw data dump
+property.debug-category.syntax.enumeration.value.database-access.synopsis=Access to a backend database.
+property.debug-category.syntax.enumeration.value.enter.synopsis=Method entry
+property.debug-category.syntax.enumeration.value.exit.synopsis=Method exit
+property.debug-category.syntax.enumeration.value.message.synopsis=Arbitrary debug message
+property.debug-category.syntax.enumeration.value.protocol.synopsis=Protocol element dump
+property.debug-category.syntax.enumeration.value.thrown.synopsis=Exception throw from method
+property.debug-level.synopsis=Specifies the lowest severity level of debug messages to log.
+property.debug-level.syntax.enumeration.value.all.synopsis=Messages with any severity level are logged.
+property.debug-level.syntax.enumeration.value.disabled.synopsis=No messages are logged.
+property.debug-level.syntax.enumeration.value.error.synopsis=Messages with severity level of ERROR or higher are logged.
+property.debug-level.syntax.enumeration.value.info.synopsis=Messages with severity level of INFO or higher are logged.
+property.debug-level.syntax.enumeration.value.verbose.synopsis=Messages with severity level of VERBOSE or higher are logged.
+property.debug-level.syntax.enumeration.value.warning.synopsis=Messages with severity level of WARNING or higher are logged.
+property.debug-scope.synopsis=Specifies the fully-qualified OpenDS Java package, class, or method affected by the settings in this target definition. Use the number character (#) to separate the class name and the method name (that is, org.opends.server.core.DirectoryServer#startUp).
+property.debug-scope.syntax.string.pattern.synopsis=The fully-qualified OpenDS Java package, class, or method name.
+property.include-throwable-cause.synopsis=Specifies the property to indicate whether to include the cause of exceptions in exception thrown and caught messages.
+property.omit-method-entry-arguments.synopsis=Specifies the property to indicate whether to include method arguments in debug messages.
+property.omit-method-return-value.synopsis=Specifies the property to indicate whether to include the return value in debug messages.
+property.throwable-stack-frames.synopsis=Specifies the property to indicate the number of stack frames to include in the stack trace for method entry and exception thrown messages.
diff --git a/opends/src/admin/messages/DebugTargetCfgDefn_fr.properties b/opends/src/admin/messages/DebugTargetCfgDefn_fr.properties
new file mode 100644
index 0000000..ebe7a3e
--- /dev/null
+++ b/opends/src/admin/messages/DebugTargetCfgDefn_fr.properties
@@ -0,0 +1,28 @@
+user-friendly-name=Debug Target
+user-friendly-plural-name=Debug Targets
+synopsis=Debug Targets define the types of messages logged by the debug logPublisher.
+description=Debug targets allow for fine-grain control of which messages are logged based on the package, class, or method that generated the message. Each debug target configuration entry resides below the entry with RDN of "cn=Debug Target" immediately below the parent ds-cfg-debug-log-publisher entry.
+property.debug-category.synopsis=Specifies the debug message categories to be logged.
+property.debug-category.default-behavior.alias.synopsis=Messages with any category are logged if they have a sufficient debug level.
+property.debug-category.syntax.enumeration.value.caught.synopsis=Exception caught
+property.debug-category.syntax.enumeration.value.constructor.synopsis=Constructor entry
+property.debug-category.syntax.enumeration.value.data.synopsis=Raw data dump
+property.debug-category.syntax.enumeration.value.database-access.synopsis=Access to a backend database.
+property.debug-category.syntax.enumeration.value.enter.synopsis=Method entry
+property.debug-category.syntax.enumeration.value.exit.synopsis=Method exit
+property.debug-category.syntax.enumeration.value.message.synopsis=Arbitrary debug message
+property.debug-category.syntax.enumeration.value.protocol.synopsis=Protocol element dump
+property.debug-category.syntax.enumeration.value.thrown.synopsis=Exception throw from method
+property.debug-level.synopsis=Specifies the lowest severity level of debug messages to log.
+property.debug-level.syntax.enumeration.value.all.synopsis=Messages with any severity level are logged.
+property.debug-level.syntax.enumeration.value.disabled.synopsis=No messages are logged.
+property.debug-level.syntax.enumeration.value.error.synopsis=Messages with severity level of ERROR or higher are logged.
+property.debug-level.syntax.enumeration.value.info.synopsis=Messages with severity level of INFO or higher are logged.
+property.debug-level.syntax.enumeration.value.verbose.synopsis=Messages with severity level of VERBOSE or higher are logged.
+property.debug-level.syntax.enumeration.value.warning.synopsis=Messages with severity level of WARNING or higher are logged.
+property.debug-scope.synopsis=Specifies the fully-qualified OpenDS Java package, class, or method affected by the settings in this target definition. Use the number character (#) to separate the class name and the method name (that is, org.opends.server.core.DirectoryServer#startUp).
+property.debug-scope.syntax.string.pattern.synopsis=The fully-qualified OpenDS Java package, class, or method name.
+property.include-throwable-cause.synopsis=Specifies the property to indicate whether to include the cause of exceptions in exception thrown and caught messages.
+property.omit-method-entry-arguments.synopsis=Specifies the property to indicate whether to include method arguments in debug messages.
+property.omit-method-return-value.synopsis=Specifies the property to indicate whether to include the return value in debug messages.
+property.throwable-stack-frames.synopsis=Specifies the property to indicate the number of stack frames to include in the stack trace for method entry and exception thrown messages.
diff --git a/opends/src/admin/messages/DebugTargetCfgDefn_ja.properties b/opends/src/admin/messages/DebugTargetCfgDefn_ja.properties
new file mode 100644
index 0000000..ebe7a3e
--- /dev/null
+++ b/opends/src/admin/messages/DebugTargetCfgDefn_ja.properties
@@ -0,0 +1,28 @@
+user-friendly-name=Debug Target
+user-friendly-plural-name=Debug Targets
+synopsis=Debug Targets define the types of messages logged by the debug logPublisher.
+description=Debug targets allow for fine-grain control of which messages are logged based on the package, class, or method that generated the message. Each debug target configuration entry resides below the entry with RDN of "cn=Debug Target" immediately below the parent ds-cfg-debug-log-publisher entry.
+property.debug-category.synopsis=Specifies the debug message categories to be logged.
+property.debug-category.default-behavior.alias.synopsis=Messages with any category are logged if they have a sufficient debug level.
+property.debug-category.syntax.enumeration.value.caught.synopsis=Exception caught
+property.debug-category.syntax.enumeration.value.constructor.synopsis=Constructor entry
+property.debug-category.syntax.enumeration.value.data.synopsis=Raw data dump
+property.debug-category.syntax.enumeration.value.database-access.synopsis=Access to a backend database.
+property.debug-category.syntax.enumeration.value.enter.synopsis=Method entry
+property.debug-category.syntax.enumeration.value.exit.synopsis=Method exit
+property.debug-category.syntax.enumeration.value.message.synopsis=Arbitrary debug message
+property.debug-category.syntax.enumeration.value.protocol.synopsis=Protocol element dump
+property.debug-category.syntax.enumeration.value.thrown.synopsis=Exception throw from method
+property.debug-level.synopsis=Specifies the lowest severity level of debug messages to log.
+property.debug-level.syntax.enumeration.value.all.synopsis=Messages with any severity level are logged.
+property.debug-level.syntax.enumeration.value.disabled.synopsis=No messages are logged.
+property.debug-level.syntax.enumeration.value.error.synopsis=Messages with severity level of ERROR or higher are logged.
+property.debug-level.syntax.enumeration.value.info.synopsis=Messages with severity level of INFO or higher are logged.
+property.debug-level.syntax.enumeration.value.verbose.synopsis=Messages with severity level of VERBOSE or higher are logged.
+property.debug-level.syntax.enumeration.value.warning.synopsis=Messages with severity level of WARNING or higher are logged.
+property.debug-scope.synopsis=Specifies the fully-qualified OpenDS Java package, class, or method affected by the settings in this target definition. Use the number character (#) to separate the class name and the method name (that is, org.opends.server.core.DirectoryServer#startUp).
+property.debug-scope.syntax.string.pattern.synopsis=The fully-qualified OpenDS Java package, class, or method name.
+property.include-throwable-cause.synopsis=Specifies the property to indicate whether to include the cause of exceptions in exception thrown and caught messages.
+property.omit-method-entry-arguments.synopsis=Specifies the property to indicate whether to include method arguments in debug messages.
+property.omit-method-return-value.synopsis=Specifies the property to indicate whether to include the return value in debug messages.
+property.throwable-stack-frames.synopsis=Specifies the property to indicate the number of stack frames to include in the stack trace for method entry and exception thrown messages.
diff --git a/opends/src/admin/messages/DebugTargetCfgDefn_ko.properties b/opends/src/admin/messages/DebugTargetCfgDefn_ko.properties
new file mode 100644
index 0000000..ebe7a3e
--- /dev/null
+++ b/opends/src/admin/messages/DebugTargetCfgDefn_ko.properties
@@ -0,0 +1,28 @@
+user-friendly-name=Debug Target
+user-friendly-plural-name=Debug Targets
+synopsis=Debug Targets define the types of messages logged by the debug logPublisher.
+description=Debug targets allow for fine-grain control of which messages are logged based on the package, class, or method that generated the message. Each debug target configuration entry resides below the entry with RDN of "cn=Debug Target" immediately below the parent ds-cfg-debug-log-publisher entry.
+property.debug-category.synopsis=Specifies the debug message categories to be logged.
+property.debug-category.default-behavior.alias.synopsis=Messages with any category are logged if they have a sufficient debug level.
+property.debug-category.syntax.enumeration.value.caught.synopsis=Exception caught
+property.debug-category.syntax.enumeration.value.constructor.synopsis=Constructor entry
+property.debug-category.syntax.enumeration.value.data.synopsis=Raw data dump
+property.debug-category.syntax.enumeration.value.database-access.synopsis=Access to a backend database.
+property.debug-category.syntax.enumeration.value.enter.synopsis=Method entry
+property.debug-category.syntax.enumeration.value.exit.synopsis=Method exit
+property.debug-category.syntax.enumeration.value.message.synopsis=Arbitrary debug message
+property.debug-category.syntax.enumeration.value.protocol.synopsis=Protocol element dump
+property.debug-category.syntax.enumeration.value.thrown.synopsis=Exception throw from method
+property.debug-level.synopsis=Specifies the lowest severity level of debug messages to log.
+property.debug-level.syntax.enumeration.value.all.synopsis=Messages with any severity level are logged.
+property.debug-level.syntax.enumeration.value.disabled.synopsis=No messages are logged.
+property.debug-level.syntax.enumeration.value.error.synopsis=Messages with severity level of ERROR or higher are logged.
+property.debug-level.syntax.enumeration.value.info.synopsis=Messages with severity level of INFO or higher are logged.
+property.debug-level.syntax.enumeration.value.verbose.synopsis=Messages with severity level of VERBOSE or higher are logged.
+property.debug-level.syntax.enumeration.value.warning.synopsis=Messages with severity level of WARNING or higher are logged.
+property.debug-scope.synopsis=Specifies the fully-qualified OpenDS Java package, class, or method affected by the settings in this target definition. Use the number character (#) to separate the class name and the method name (that is, org.opends.server.core.DirectoryServer#startUp).
+property.debug-scope.syntax.string.pattern.synopsis=The fully-qualified OpenDS Java package, class, or method name.
+property.include-throwable-cause.synopsis=Specifies the property to indicate whether to include the cause of exceptions in exception thrown and caught messages.
+property.omit-method-entry-arguments.synopsis=Specifies the property to indicate whether to include method arguments in debug messages.
+property.omit-method-return-value.synopsis=Specifies the property to indicate whether to include the return value in debug messages.
+property.throwable-stack-frames.synopsis=Specifies the property to indicate the number of stack frames to include in the stack trace for method entry and exception thrown messages.
diff --git a/opends/src/admin/messages/DebugTargetCfgDefn_zh_CN.properties b/opends/src/admin/messages/DebugTargetCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..ebe7a3e
--- /dev/null
+++ b/opends/src/admin/messages/DebugTargetCfgDefn_zh_CN.properties
@@ -0,0 +1,28 @@
+user-friendly-name=Debug Target
+user-friendly-plural-name=Debug Targets
+synopsis=Debug Targets define the types of messages logged by the debug logPublisher.
+description=Debug targets allow for fine-grain control of which messages are logged based on the package, class, or method that generated the message. Each debug target configuration entry resides below the entry with RDN of "cn=Debug Target" immediately below the parent ds-cfg-debug-log-publisher entry.
+property.debug-category.synopsis=Specifies the debug message categories to be logged.
+property.debug-category.default-behavior.alias.synopsis=Messages with any category are logged if they have a sufficient debug level.
+property.debug-category.syntax.enumeration.value.caught.synopsis=Exception caught
+property.debug-category.syntax.enumeration.value.constructor.synopsis=Constructor entry
+property.debug-category.syntax.enumeration.value.data.synopsis=Raw data dump
+property.debug-category.syntax.enumeration.value.database-access.synopsis=Access to a backend database.
+property.debug-category.syntax.enumeration.value.enter.synopsis=Method entry
+property.debug-category.syntax.enumeration.value.exit.synopsis=Method exit
+property.debug-category.syntax.enumeration.value.message.synopsis=Arbitrary debug message
+property.debug-category.syntax.enumeration.value.protocol.synopsis=Protocol element dump
+property.debug-category.syntax.enumeration.value.thrown.synopsis=Exception throw from method
+property.debug-level.synopsis=Specifies the lowest severity level of debug messages to log.
+property.debug-level.syntax.enumeration.value.all.synopsis=Messages with any severity level are logged.
+property.debug-level.syntax.enumeration.value.disabled.synopsis=No messages are logged.
+property.debug-level.syntax.enumeration.value.error.synopsis=Messages with severity level of ERROR or higher are logged.
+property.debug-level.syntax.enumeration.value.info.synopsis=Messages with severity level of INFO or higher are logged.
+property.debug-level.syntax.enumeration.value.verbose.synopsis=Messages with severity level of VERBOSE or higher are logged.
+property.debug-level.syntax.enumeration.value.warning.synopsis=Messages with severity level of WARNING or higher are logged.
+property.debug-scope.synopsis=Specifies the fully-qualified OpenDS Java package, class, or method affected by the settings in this target definition. Use the number character (#) to separate the class name and the method name (that is, org.opends.server.core.DirectoryServer#startUp).
+property.debug-scope.syntax.string.pattern.synopsis=The fully-qualified OpenDS Java package, class, or method name.
+property.include-throwable-cause.synopsis=Specifies the property to indicate whether to include the cause of exceptions in exception thrown and caught messages.
+property.omit-method-entry-arguments.synopsis=Specifies the property to indicate whether to include method arguments in debug messages.
+property.omit-method-return-value.synopsis=Specifies the property to indicate whether to include the return value in debug messages.
+property.throwable-stack-frames.synopsis=Specifies the property to indicate the number of stack frames to include in the stack trace for method entry and exception thrown messages.
diff --git a/opends/src/admin/messages/DebugTargetCfgDefn_zh_TW.properties b/opends/src/admin/messages/DebugTargetCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..ebe7a3e
--- /dev/null
+++ b/opends/src/admin/messages/DebugTargetCfgDefn_zh_TW.properties
@@ -0,0 +1,28 @@
+user-friendly-name=Debug Target
+user-friendly-plural-name=Debug Targets
+synopsis=Debug Targets define the types of messages logged by the debug logPublisher.
+description=Debug targets allow for fine-grain control of which messages are logged based on the package, class, or method that generated the message. Each debug target configuration entry resides below the entry with RDN of "cn=Debug Target" immediately below the parent ds-cfg-debug-log-publisher entry.
+property.debug-category.synopsis=Specifies the debug message categories to be logged.
+property.debug-category.default-behavior.alias.synopsis=Messages with any category are logged if they have a sufficient debug level.
+property.debug-category.syntax.enumeration.value.caught.synopsis=Exception caught
+property.debug-category.syntax.enumeration.value.constructor.synopsis=Constructor entry
+property.debug-category.syntax.enumeration.value.data.synopsis=Raw data dump
+property.debug-category.syntax.enumeration.value.database-access.synopsis=Access to a backend database.
+property.debug-category.syntax.enumeration.value.enter.synopsis=Method entry
+property.debug-category.syntax.enumeration.value.exit.synopsis=Method exit
+property.debug-category.syntax.enumeration.value.message.synopsis=Arbitrary debug message
+property.debug-category.syntax.enumeration.value.protocol.synopsis=Protocol element dump
+property.debug-category.syntax.enumeration.value.thrown.synopsis=Exception throw from method
+property.debug-level.synopsis=Specifies the lowest severity level of debug messages to log.
+property.debug-level.syntax.enumeration.value.all.synopsis=Messages with any severity level are logged.
+property.debug-level.syntax.enumeration.value.disabled.synopsis=No messages are logged.
+property.debug-level.syntax.enumeration.value.error.synopsis=Messages with severity level of ERROR or higher are logged.
+property.debug-level.syntax.enumeration.value.info.synopsis=Messages with severity level of INFO or higher are logged.
+property.debug-level.syntax.enumeration.value.verbose.synopsis=Messages with severity level of VERBOSE or higher are logged.
+property.debug-level.syntax.enumeration.value.warning.synopsis=Messages with severity level of WARNING or higher are logged.
+property.debug-scope.synopsis=Specifies the fully-qualified OpenDS Java package, class, or method affected by the settings in this target definition. Use the number character (#) to separate the class name and the method name (that is, org.opends.server.core.DirectoryServer#startUp).
+property.debug-scope.syntax.string.pattern.synopsis=The fully-qualified OpenDS Java package, class, or method name.
+property.include-throwable-cause.synopsis=Specifies the property to indicate whether to include the cause of exceptions in exception thrown and caught messages.
+property.omit-method-entry-arguments.synopsis=Specifies the property to indicate whether to include method arguments in debug messages.
+property.omit-method-return-value.synopsis=Specifies the property to indicate whether to include the return value in debug messages.
+property.throwable-stack-frames.synopsis=Specifies the property to indicate the number of stack frames to include in the stack trace for method entry and exception thrown messages.
diff --git a/opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn.properties b/opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn.properties
new file mode 100644
index 0000000..1a44b5c
--- /dev/null
+++ b/opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn.properties
@@ -0,0 +1,13 @@
+user-friendly-name=Dictionary Password Validator
+user-friendly-plural-name=Dictionary Password Validators
+synopsis=The Dictionary Password Validator determines whether a proposed password is acceptable based on whether the given password value appears in a provided dictionary file.
+description=A large dictionary file is provided with the server, but the administrator can supply an alternate dictionary. In this case, then the dictionary must be a plain-text file with one word per line.
+property.case-sensitive-validation.synopsis=Indicates whether this password validator is to treat password characters in a case-sensitive manner.
+property.case-sensitive-validation.description=If it is set to true, then the validator rejects a password only if it appears in the dictionary with exactly the same capitalization as provided by the user.
+property.dictionary-file.synopsis=Specifies the path to the file containing a list of words that cannot be used as passwords.
+property.dictionary-file.description=It should be formatted with one word per line. The value can be an absolute path or a path that is relative to the OpenDS Directory Server instance root.
+property.dictionary-file.syntax.string.pattern.synopsis=The path to any text file contained on the system that is readable by the server.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.test-reversed-password.synopsis=Indicates whether this password validator is to test the reversed value of the provided password as well as the order in which it was given.
+property.test-reversed-password.description=For example, if the user provides a new password of "password" and this configuration attribute is set to true, then the value "drowssap" is also tested against attribute values in the user's entry.
diff --git a/opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_de.properties b/opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_de.properties
new file mode 100644
index 0000000..1a44b5c
--- /dev/null
+++ b/opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_de.properties
@@ -0,0 +1,13 @@
+user-friendly-name=Dictionary Password Validator
+user-friendly-plural-name=Dictionary Password Validators
+synopsis=The Dictionary Password Validator determines whether a proposed password is acceptable based on whether the given password value appears in a provided dictionary file.
+description=A large dictionary file is provided with the server, but the administrator can supply an alternate dictionary. In this case, then the dictionary must be a plain-text file with one word per line.
+property.case-sensitive-validation.synopsis=Indicates whether this password validator is to treat password characters in a case-sensitive manner.
+property.case-sensitive-validation.description=If it is set to true, then the validator rejects a password only if it appears in the dictionary with exactly the same capitalization as provided by the user.
+property.dictionary-file.synopsis=Specifies the path to the file containing a list of words that cannot be used as passwords.
+property.dictionary-file.description=It should be formatted with one word per line. The value can be an absolute path or a path that is relative to the OpenDS Directory Server instance root.
+property.dictionary-file.syntax.string.pattern.synopsis=The path to any text file contained on the system that is readable by the server.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.test-reversed-password.synopsis=Indicates whether this password validator is to test the reversed value of the provided password as well as the order in which it was given.
+property.test-reversed-password.description=For example, if the user provides a new password of "password" and this configuration attribute is set to true, then the value "drowssap" is also tested against attribute values in the user's entry.
diff --git a/opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_es.properties b/opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_es.properties
new file mode 100644
index 0000000..1a44b5c
--- /dev/null
+++ b/opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_es.properties
@@ -0,0 +1,13 @@
+user-friendly-name=Dictionary Password Validator
+user-friendly-plural-name=Dictionary Password Validators
+synopsis=The Dictionary Password Validator determines whether a proposed password is acceptable based on whether the given password value appears in a provided dictionary file.
+description=A large dictionary file is provided with the server, but the administrator can supply an alternate dictionary. In this case, then the dictionary must be a plain-text file with one word per line.
+property.case-sensitive-validation.synopsis=Indicates whether this password validator is to treat password characters in a case-sensitive manner.
+property.case-sensitive-validation.description=If it is set to true, then the validator rejects a password only if it appears in the dictionary with exactly the same capitalization as provided by the user.
+property.dictionary-file.synopsis=Specifies the path to the file containing a list of words that cannot be used as passwords.
+property.dictionary-file.description=It should be formatted with one word per line. The value can be an absolute path or a path that is relative to the OpenDS Directory Server instance root.
+property.dictionary-file.syntax.string.pattern.synopsis=The path to any text file contained on the system that is readable by the server.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.test-reversed-password.synopsis=Indicates whether this password validator is to test the reversed value of the provided password as well as the order in which it was given.
+property.test-reversed-password.description=For example, if the user provides a new password of "password" and this configuration attribute is set to true, then the value "drowssap" is also tested against attribute values in the user's entry.
diff --git a/opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_fr.properties b/opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_fr.properties
new file mode 100644
index 0000000..1a44b5c
--- /dev/null
+++ b/opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_fr.properties
@@ -0,0 +1,13 @@
+user-friendly-name=Dictionary Password Validator
+user-friendly-plural-name=Dictionary Password Validators
+synopsis=The Dictionary Password Validator determines whether a proposed password is acceptable based on whether the given password value appears in a provided dictionary file.
+description=A large dictionary file is provided with the server, but the administrator can supply an alternate dictionary. In this case, then the dictionary must be a plain-text file with one word per line.
+property.case-sensitive-validation.synopsis=Indicates whether this password validator is to treat password characters in a case-sensitive manner.
+property.case-sensitive-validation.description=If it is set to true, then the validator rejects a password only if it appears in the dictionary with exactly the same capitalization as provided by the user.
+property.dictionary-file.synopsis=Specifies the path to the file containing a list of words that cannot be used as passwords.
+property.dictionary-file.description=It should be formatted with one word per line. The value can be an absolute path or a path that is relative to the OpenDS Directory Server instance root.
+property.dictionary-file.syntax.string.pattern.synopsis=The path to any text file contained on the system that is readable by the server.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.test-reversed-password.synopsis=Indicates whether this password validator is to test the reversed value of the provided password as well as the order in which it was given.
+property.test-reversed-password.description=For example, if the user provides a new password of "password" and this configuration attribute is set to true, then the value "drowssap" is also tested against attribute values in the user's entry.
diff --git a/opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_ja.properties b/opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_ja.properties
new file mode 100644
index 0000000..1a44b5c
--- /dev/null
+++ b/opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_ja.properties
@@ -0,0 +1,13 @@
+user-friendly-name=Dictionary Password Validator
+user-friendly-plural-name=Dictionary Password Validators
+synopsis=The Dictionary Password Validator determines whether a proposed password is acceptable based on whether the given password value appears in a provided dictionary file.
+description=A large dictionary file is provided with the server, but the administrator can supply an alternate dictionary. In this case, then the dictionary must be a plain-text file with one word per line.
+property.case-sensitive-validation.synopsis=Indicates whether this password validator is to treat password characters in a case-sensitive manner.
+property.case-sensitive-validation.description=If it is set to true, then the validator rejects a password only if it appears in the dictionary with exactly the same capitalization as provided by the user.
+property.dictionary-file.synopsis=Specifies the path to the file containing a list of words that cannot be used as passwords.
+property.dictionary-file.description=It should be formatted with one word per line. The value can be an absolute path or a path that is relative to the OpenDS Directory Server instance root.
+property.dictionary-file.syntax.string.pattern.synopsis=The path to any text file contained on the system that is readable by the server.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.test-reversed-password.synopsis=Indicates whether this password validator is to test the reversed value of the provided password as well as the order in which it was given.
+property.test-reversed-password.description=For example, if the user provides a new password of "password" and this configuration attribute is set to true, then the value "drowssap" is also tested against attribute values in the user's entry.
diff --git a/opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_ko.properties b/opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_ko.properties
new file mode 100644
index 0000000..1a44b5c
--- /dev/null
+++ b/opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_ko.properties
@@ -0,0 +1,13 @@
+user-friendly-name=Dictionary Password Validator
+user-friendly-plural-name=Dictionary Password Validators
+synopsis=The Dictionary Password Validator determines whether a proposed password is acceptable based on whether the given password value appears in a provided dictionary file.
+description=A large dictionary file is provided with the server, but the administrator can supply an alternate dictionary. In this case, then the dictionary must be a plain-text file with one word per line.
+property.case-sensitive-validation.synopsis=Indicates whether this password validator is to treat password characters in a case-sensitive manner.
+property.case-sensitive-validation.description=If it is set to true, then the validator rejects a password only if it appears in the dictionary with exactly the same capitalization as provided by the user.
+property.dictionary-file.synopsis=Specifies the path to the file containing a list of words that cannot be used as passwords.
+property.dictionary-file.description=It should be formatted with one word per line. The value can be an absolute path or a path that is relative to the OpenDS Directory Server instance root.
+property.dictionary-file.syntax.string.pattern.synopsis=The path to any text file contained on the system that is readable by the server.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.test-reversed-password.synopsis=Indicates whether this password validator is to test the reversed value of the provided password as well as the order in which it was given.
+property.test-reversed-password.description=For example, if the user provides a new password of "password" and this configuration attribute is set to true, then the value "drowssap" is also tested against attribute values in the user's entry.
diff --git a/opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_zh_CN.properties b/opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..1a44b5c
--- /dev/null
+++ b/opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_zh_CN.properties
@@ -0,0 +1,13 @@
+user-friendly-name=Dictionary Password Validator
+user-friendly-plural-name=Dictionary Password Validators
+synopsis=The Dictionary Password Validator determines whether a proposed password is acceptable based on whether the given password value appears in a provided dictionary file.
+description=A large dictionary file is provided with the server, but the administrator can supply an alternate dictionary. In this case, then the dictionary must be a plain-text file with one word per line.
+property.case-sensitive-validation.synopsis=Indicates whether this password validator is to treat password characters in a case-sensitive manner.
+property.case-sensitive-validation.description=If it is set to true, then the validator rejects a password only if it appears in the dictionary with exactly the same capitalization as provided by the user.
+property.dictionary-file.synopsis=Specifies the path to the file containing a list of words that cannot be used as passwords.
+property.dictionary-file.description=It should be formatted with one word per line. The value can be an absolute path or a path that is relative to the OpenDS Directory Server instance root.
+property.dictionary-file.syntax.string.pattern.synopsis=The path to any text file contained on the system that is readable by the server.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.test-reversed-password.synopsis=Indicates whether this password validator is to test the reversed value of the provided password as well as the order in which it was given.
+property.test-reversed-password.description=For example, if the user provides a new password of "password" and this configuration attribute is set to true, then the value "drowssap" is also tested against attribute values in the user's entry.
diff --git a/opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_zh_TW.properties b/opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..1a44b5c
--- /dev/null
+++ b/opends/src/admin/messages/DictionaryPasswordValidatorCfgDefn_zh_TW.properties
@@ -0,0 +1,13 @@
+user-friendly-name=Dictionary Password Validator
+user-friendly-plural-name=Dictionary Password Validators
+synopsis=The Dictionary Password Validator determines whether a proposed password is acceptable based on whether the given password value appears in a provided dictionary file.
+description=A large dictionary file is provided with the server, but the administrator can supply an alternate dictionary. In this case, then the dictionary must be a plain-text file with one word per line.
+property.case-sensitive-validation.synopsis=Indicates whether this password validator is to treat password characters in a case-sensitive manner.
+property.case-sensitive-validation.description=If it is set to true, then the validator rejects a password only if it appears in the dictionary with exactly the same capitalization as provided by the user.
+property.dictionary-file.synopsis=Specifies the path to the file containing a list of words that cannot be used as passwords.
+property.dictionary-file.description=It should be formatted with one word per line. The value can be an absolute path or a path that is relative to the OpenDS Directory Server instance root.
+property.dictionary-file.syntax.string.pattern.synopsis=The path to any text file contained on the system that is readable by the server.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.test-reversed-password.synopsis=Indicates whether this password validator is to test the reversed value of the provided password as well as the order in which it was given.
+property.test-reversed-password.description=For example, if the user provides a new password of "password" and this configuration attribute is set to true, then the value "drowssap" is also tested against attribute values in the user's entry.
diff --git a/opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn.properties b/opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn.properties
new file mode 100644
index 0000000..109991c
--- /dev/null
+++ b/opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Digest MD5 SASL Mechanism Handler
+user-friendly-plural-name=Digest MD5 SASL Mechanism Handlers
+synopsis=The DIGEST-MD5 SASL mechanism is used to perform all processing related to SASL DIGEST-MD5 authentication.
+description=The DIGEST-MD5 SASL mechanism is very similar to the CRAM-MD5 mechanism in that it allows for password-based authentication without exposing the password in the clear (although it does require that both the client and the server have access to the clear-text password). Like the CRAM-MD5 mechanism, it uses data that is randomly generated by the server to make it resistant to replay attacks, but it also includes randomly-generated data from the client, which makes it also resistant to problems resulting from weak server-side random number generation.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that is to be used with this SASL mechanism handler to match the authentication or authorization ID included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Digest MD5 SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
+property.quality-of-protection.synopsis=The name of a property that specifies the quality of protection the server will support.
+property.quality-of-protection.syntax.enumeration.value.confidentiality.synopsis=Quality of protection equals authentication with integrity and confidentiality protection.
+property.quality-of-protection.syntax.enumeration.value.integrity.synopsis=Quality of protection equals authentication with integrity protection.
+property.quality-of-protection.syntax.enumeration.value.none.synopsis=QOP equals authentication only.
+property.realm.synopsis=Specifies the realms that is to be used by the server for DIGEST-MD5 authentication.
+property.realm.description=If this value is not provided, then the server defaults to use the fully qualified hostname of the machine.
+property.realm.default-behavior.alias.synopsis=If this value is not provided, then the server defaults to use the fully qualified hostname of the machine.
+property.realm.syntax.string.pattern.synopsis=Any realm string that does not contain a comma.
+property.server-fqdn.synopsis=Specifies the DNS-resolvable fully-qualified domain name for the server that is used when validating the digest-uri parameter during the authentication process.
+property.server-fqdn.description=If this configuration attribute is present, then the server expects that clients use a digest-uri equal to "ldap/" followed by the value of this attribute. For example, if the attribute has a value of "directory.example.com", then the server expects clients to use a digest-uri of "ldap/directory.example.com". If no value is provided, then the server does not attempt to validate the digest-uri provided by the client and accepts any value.
+property.server-fqdn.default-behavior.alias.synopsis=The server attempts to determine the fully-qualified domain name dynamically.
+property.server-fqdn.syntax.string.pattern.synopsis=The fully-qualified address that is expected for clients to use when connecting to the server and authenticating via DIGEST-MD5.
diff --git a/opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_de.properties b/opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..109991c
--- /dev/null
+++ b/opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_de.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Digest MD5 SASL Mechanism Handler
+user-friendly-plural-name=Digest MD5 SASL Mechanism Handlers
+synopsis=The DIGEST-MD5 SASL mechanism is used to perform all processing related to SASL DIGEST-MD5 authentication.
+description=The DIGEST-MD5 SASL mechanism is very similar to the CRAM-MD5 mechanism in that it allows for password-based authentication without exposing the password in the clear (although it does require that both the client and the server have access to the clear-text password). Like the CRAM-MD5 mechanism, it uses data that is randomly generated by the server to make it resistant to replay attacks, but it also includes randomly-generated data from the client, which makes it also resistant to problems resulting from weak server-side random number generation.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that is to be used with this SASL mechanism handler to match the authentication or authorization ID included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Digest MD5 SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
+property.quality-of-protection.synopsis=The name of a property that specifies the quality of protection the server will support.
+property.quality-of-protection.syntax.enumeration.value.confidentiality.synopsis=Quality of protection equals authentication with integrity and confidentiality protection.
+property.quality-of-protection.syntax.enumeration.value.integrity.synopsis=Quality of protection equals authentication with integrity protection.
+property.quality-of-protection.syntax.enumeration.value.none.synopsis=QOP equals authentication only.
+property.realm.synopsis=Specifies the realms that is to be used by the server for DIGEST-MD5 authentication.
+property.realm.description=If this value is not provided, then the server defaults to use the fully qualified hostname of the machine.
+property.realm.default-behavior.alias.synopsis=If this value is not provided, then the server defaults to use the fully qualified hostname of the machine.
+property.realm.syntax.string.pattern.synopsis=Any realm string that does not contain a comma.
+property.server-fqdn.synopsis=Specifies the DNS-resolvable fully-qualified domain name for the server that is used when validating the digest-uri parameter during the authentication process.
+property.server-fqdn.description=If this configuration attribute is present, then the server expects that clients use a digest-uri equal to "ldap/" followed by the value of this attribute. For example, if the attribute has a value of "directory.example.com", then the server expects clients to use a digest-uri of "ldap/directory.example.com". If no value is provided, then the server does not attempt to validate the digest-uri provided by the client and accepts any value.
+property.server-fqdn.default-behavior.alias.synopsis=The server attempts to determine the fully-qualified domain name dynamically.
+property.server-fqdn.syntax.string.pattern.synopsis=The fully-qualified address that is expected for clients to use when connecting to the server and authenticating via DIGEST-MD5.
diff --git a/opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_es.properties b/opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..109991c
--- /dev/null
+++ b/opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_es.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Digest MD5 SASL Mechanism Handler
+user-friendly-plural-name=Digest MD5 SASL Mechanism Handlers
+synopsis=The DIGEST-MD5 SASL mechanism is used to perform all processing related to SASL DIGEST-MD5 authentication.
+description=The DIGEST-MD5 SASL mechanism is very similar to the CRAM-MD5 mechanism in that it allows for password-based authentication without exposing the password in the clear (although it does require that both the client and the server have access to the clear-text password). Like the CRAM-MD5 mechanism, it uses data that is randomly generated by the server to make it resistant to replay attacks, but it also includes randomly-generated data from the client, which makes it also resistant to problems resulting from weak server-side random number generation.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that is to be used with this SASL mechanism handler to match the authentication or authorization ID included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Digest MD5 SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
+property.quality-of-protection.synopsis=The name of a property that specifies the quality of protection the server will support.
+property.quality-of-protection.syntax.enumeration.value.confidentiality.synopsis=Quality of protection equals authentication with integrity and confidentiality protection.
+property.quality-of-protection.syntax.enumeration.value.integrity.synopsis=Quality of protection equals authentication with integrity protection.
+property.quality-of-protection.syntax.enumeration.value.none.synopsis=QOP equals authentication only.
+property.realm.synopsis=Specifies the realms that is to be used by the server for DIGEST-MD5 authentication.
+property.realm.description=If this value is not provided, then the server defaults to use the fully qualified hostname of the machine.
+property.realm.default-behavior.alias.synopsis=If this value is not provided, then the server defaults to use the fully qualified hostname of the machine.
+property.realm.syntax.string.pattern.synopsis=Any realm string that does not contain a comma.
+property.server-fqdn.synopsis=Specifies the DNS-resolvable fully-qualified domain name for the server that is used when validating the digest-uri parameter during the authentication process.
+property.server-fqdn.description=If this configuration attribute is present, then the server expects that clients use a digest-uri equal to "ldap/" followed by the value of this attribute. For example, if the attribute has a value of "directory.example.com", then the server expects clients to use a digest-uri of "ldap/directory.example.com". If no value is provided, then the server does not attempt to validate the digest-uri provided by the client and accepts any value.
+property.server-fqdn.default-behavior.alias.synopsis=The server attempts to determine the fully-qualified domain name dynamically.
+property.server-fqdn.syntax.string.pattern.synopsis=The fully-qualified address that is expected for clients to use when connecting to the server and authenticating via DIGEST-MD5.
diff --git a/opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_fr.properties b/opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..109991c
--- /dev/null
+++ b/opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_fr.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Digest MD5 SASL Mechanism Handler
+user-friendly-plural-name=Digest MD5 SASL Mechanism Handlers
+synopsis=The DIGEST-MD5 SASL mechanism is used to perform all processing related to SASL DIGEST-MD5 authentication.
+description=The DIGEST-MD5 SASL mechanism is very similar to the CRAM-MD5 mechanism in that it allows for password-based authentication without exposing the password in the clear (although it does require that both the client and the server have access to the clear-text password). Like the CRAM-MD5 mechanism, it uses data that is randomly generated by the server to make it resistant to replay attacks, but it also includes randomly-generated data from the client, which makes it also resistant to problems resulting from weak server-side random number generation.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that is to be used with this SASL mechanism handler to match the authentication or authorization ID included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Digest MD5 SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
+property.quality-of-protection.synopsis=The name of a property that specifies the quality of protection the server will support.
+property.quality-of-protection.syntax.enumeration.value.confidentiality.synopsis=Quality of protection equals authentication with integrity and confidentiality protection.
+property.quality-of-protection.syntax.enumeration.value.integrity.synopsis=Quality of protection equals authentication with integrity protection.
+property.quality-of-protection.syntax.enumeration.value.none.synopsis=QOP equals authentication only.
+property.realm.synopsis=Specifies the realms that is to be used by the server for DIGEST-MD5 authentication.
+property.realm.description=If this value is not provided, then the server defaults to use the fully qualified hostname of the machine.
+property.realm.default-behavior.alias.synopsis=If this value is not provided, then the server defaults to use the fully qualified hostname of the machine.
+property.realm.syntax.string.pattern.synopsis=Any realm string that does not contain a comma.
+property.server-fqdn.synopsis=Specifies the DNS-resolvable fully-qualified domain name for the server that is used when validating the digest-uri parameter during the authentication process.
+property.server-fqdn.description=If this configuration attribute is present, then the server expects that clients use a digest-uri equal to "ldap/" followed by the value of this attribute. For example, if the attribute has a value of "directory.example.com", then the server expects clients to use a digest-uri of "ldap/directory.example.com". If no value is provided, then the server does not attempt to validate the digest-uri provided by the client and accepts any value.
+property.server-fqdn.default-behavior.alias.synopsis=The server attempts to determine the fully-qualified domain name dynamically.
+property.server-fqdn.syntax.string.pattern.synopsis=The fully-qualified address that is expected for clients to use when connecting to the server and authenticating via DIGEST-MD5.
diff --git a/opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_ja.properties b/opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..109991c
--- /dev/null
+++ b/opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_ja.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Digest MD5 SASL Mechanism Handler
+user-friendly-plural-name=Digest MD5 SASL Mechanism Handlers
+synopsis=The DIGEST-MD5 SASL mechanism is used to perform all processing related to SASL DIGEST-MD5 authentication.
+description=The DIGEST-MD5 SASL mechanism is very similar to the CRAM-MD5 mechanism in that it allows for password-based authentication without exposing the password in the clear (although it does require that both the client and the server have access to the clear-text password). Like the CRAM-MD5 mechanism, it uses data that is randomly generated by the server to make it resistant to replay attacks, but it also includes randomly-generated data from the client, which makes it also resistant to problems resulting from weak server-side random number generation.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that is to be used with this SASL mechanism handler to match the authentication or authorization ID included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Digest MD5 SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
+property.quality-of-protection.synopsis=The name of a property that specifies the quality of protection the server will support.
+property.quality-of-protection.syntax.enumeration.value.confidentiality.synopsis=Quality of protection equals authentication with integrity and confidentiality protection.
+property.quality-of-protection.syntax.enumeration.value.integrity.synopsis=Quality of protection equals authentication with integrity protection.
+property.quality-of-protection.syntax.enumeration.value.none.synopsis=QOP equals authentication only.
+property.realm.synopsis=Specifies the realms that is to be used by the server for DIGEST-MD5 authentication.
+property.realm.description=If this value is not provided, then the server defaults to use the fully qualified hostname of the machine.
+property.realm.default-behavior.alias.synopsis=If this value is not provided, then the server defaults to use the fully qualified hostname of the machine.
+property.realm.syntax.string.pattern.synopsis=Any realm string that does not contain a comma.
+property.server-fqdn.synopsis=Specifies the DNS-resolvable fully-qualified domain name for the server that is used when validating the digest-uri parameter during the authentication process.
+property.server-fqdn.description=If this configuration attribute is present, then the server expects that clients use a digest-uri equal to "ldap/" followed by the value of this attribute. For example, if the attribute has a value of "directory.example.com", then the server expects clients to use a digest-uri of "ldap/directory.example.com". If no value is provided, then the server does not attempt to validate the digest-uri provided by the client and accepts any value.
+property.server-fqdn.default-behavior.alias.synopsis=The server attempts to determine the fully-qualified domain name dynamically.
+property.server-fqdn.syntax.string.pattern.synopsis=The fully-qualified address that is expected for clients to use when connecting to the server and authenticating via DIGEST-MD5.
diff --git a/opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_ko.properties b/opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..109991c
--- /dev/null
+++ b/opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_ko.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Digest MD5 SASL Mechanism Handler
+user-friendly-plural-name=Digest MD5 SASL Mechanism Handlers
+synopsis=The DIGEST-MD5 SASL mechanism is used to perform all processing related to SASL DIGEST-MD5 authentication.
+description=The DIGEST-MD5 SASL mechanism is very similar to the CRAM-MD5 mechanism in that it allows for password-based authentication without exposing the password in the clear (although it does require that both the client and the server have access to the clear-text password). Like the CRAM-MD5 mechanism, it uses data that is randomly generated by the server to make it resistant to replay attacks, but it also includes randomly-generated data from the client, which makes it also resistant to problems resulting from weak server-side random number generation.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that is to be used with this SASL mechanism handler to match the authentication or authorization ID included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Digest MD5 SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
+property.quality-of-protection.synopsis=The name of a property that specifies the quality of protection the server will support.
+property.quality-of-protection.syntax.enumeration.value.confidentiality.synopsis=Quality of protection equals authentication with integrity and confidentiality protection.
+property.quality-of-protection.syntax.enumeration.value.integrity.synopsis=Quality of protection equals authentication with integrity protection.
+property.quality-of-protection.syntax.enumeration.value.none.synopsis=QOP equals authentication only.
+property.realm.synopsis=Specifies the realms that is to be used by the server for DIGEST-MD5 authentication.
+property.realm.description=If this value is not provided, then the server defaults to use the fully qualified hostname of the machine.
+property.realm.default-behavior.alias.synopsis=If this value is not provided, then the server defaults to use the fully qualified hostname of the machine.
+property.realm.syntax.string.pattern.synopsis=Any realm string that does not contain a comma.
+property.server-fqdn.synopsis=Specifies the DNS-resolvable fully-qualified domain name for the server that is used when validating the digest-uri parameter during the authentication process.
+property.server-fqdn.description=If this configuration attribute is present, then the server expects that clients use a digest-uri equal to "ldap/" followed by the value of this attribute. For example, if the attribute has a value of "directory.example.com", then the server expects clients to use a digest-uri of "ldap/directory.example.com". If no value is provided, then the server does not attempt to validate the digest-uri provided by the client and accepts any value.
+property.server-fqdn.default-behavior.alias.synopsis=The server attempts to determine the fully-qualified domain name dynamically.
+property.server-fqdn.syntax.string.pattern.synopsis=The fully-qualified address that is expected for clients to use when connecting to the server and authenticating via DIGEST-MD5.
diff --git a/opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..109991c
--- /dev/null
+++ b/opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Digest MD5 SASL Mechanism Handler
+user-friendly-plural-name=Digest MD5 SASL Mechanism Handlers
+synopsis=The DIGEST-MD5 SASL mechanism is used to perform all processing related to SASL DIGEST-MD5 authentication.
+description=The DIGEST-MD5 SASL mechanism is very similar to the CRAM-MD5 mechanism in that it allows for password-based authentication without exposing the password in the clear (although it does require that both the client and the server have access to the clear-text password). Like the CRAM-MD5 mechanism, it uses data that is randomly generated by the server to make it resistant to replay attacks, but it also includes randomly-generated data from the client, which makes it also resistant to problems resulting from weak server-side random number generation.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that is to be used with this SASL mechanism handler to match the authentication or authorization ID included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Digest MD5 SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
+property.quality-of-protection.synopsis=The name of a property that specifies the quality of protection the server will support.
+property.quality-of-protection.syntax.enumeration.value.confidentiality.synopsis=Quality of protection equals authentication with integrity and confidentiality protection.
+property.quality-of-protection.syntax.enumeration.value.integrity.synopsis=Quality of protection equals authentication with integrity protection.
+property.quality-of-protection.syntax.enumeration.value.none.synopsis=QOP equals authentication only.
+property.realm.synopsis=Specifies the realms that is to be used by the server for DIGEST-MD5 authentication.
+property.realm.description=If this value is not provided, then the server defaults to use the fully qualified hostname of the machine.
+property.realm.default-behavior.alias.synopsis=If this value is not provided, then the server defaults to use the fully qualified hostname of the machine.
+property.realm.syntax.string.pattern.synopsis=Any realm string that does not contain a comma.
+property.server-fqdn.synopsis=Specifies the DNS-resolvable fully-qualified domain name for the server that is used when validating the digest-uri parameter during the authentication process.
+property.server-fqdn.description=If this configuration attribute is present, then the server expects that clients use a digest-uri equal to "ldap/" followed by the value of this attribute. For example, if the attribute has a value of "directory.example.com", then the server expects clients to use a digest-uri of "ldap/directory.example.com". If no value is provided, then the server does not attempt to validate the digest-uri provided by the client and accepts any value.
+property.server-fqdn.default-behavior.alias.synopsis=The server attempts to determine the fully-qualified domain name dynamically.
+property.server-fqdn.syntax.string.pattern.synopsis=The fully-qualified address that is expected for clients to use when connecting to the server and authenticating via DIGEST-MD5.
diff --git a/opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..109991c
--- /dev/null
+++ b/opends/src/admin/messages/DigestMD5SASLMechanismHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Digest MD5 SASL Mechanism Handler
+user-friendly-plural-name=Digest MD5 SASL Mechanism Handlers
+synopsis=The DIGEST-MD5 SASL mechanism is used to perform all processing related to SASL DIGEST-MD5 authentication.
+description=The DIGEST-MD5 SASL mechanism is very similar to the CRAM-MD5 mechanism in that it allows for password-based authentication without exposing the password in the clear (although it does require that both the client and the server have access to the clear-text password). Like the CRAM-MD5 mechanism, it uses data that is randomly generated by the server to make it resistant to replay attacks, but it also includes randomly-generated data from the client, which makes it also resistant to problems resulting from weak server-side random number generation.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that is to be used with this SASL mechanism handler to match the authentication or authorization ID included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Digest MD5 SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
+property.quality-of-protection.synopsis=The name of a property that specifies the quality of protection the server will support.
+property.quality-of-protection.syntax.enumeration.value.confidentiality.synopsis=Quality of protection equals authentication with integrity and confidentiality protection.
+property.quality-of-protection.syntax.enumeration.value.integrity.synopsis=Quality of protection equals authentication with integrity protection.
+property.quality-of-protection.syntax.enumeration.value.none.synopsis=QOP equals authentication only.
+property.realm.synopsis=Specifies the realms that is to be used by the server for DIGEST-MD5 authentication.
+property.realm.description=If this value is not provided, then the server defaults to use the fully qualified hostname of the machine.
+property.realm.default-behavior.alias.synopsis=If this value is not provided, then the server defaults to use the fully qualified hostname of the machine.
+property.realm.syntax.string.pattern.synopsis=Any realm string that does not contain a comma.
+property.server-fqdn.synopsis=Specifies the DNS-resolvable fully-qualified domain name for the server that is used when validating the digest-uri parameter during the authentication process.
+property.server-fqdn.description=If this configuration attribute is present, then the server expects that clients use a digest-uri equal to "ldap/" followed by the value of this attribute. For example, if the attribute has a value of "directory.example.com", then the server expects clients to use a digest-uri of "ldap/directory.example.com". If no value is provided, then the server does not attempt to validate the digest-uri provided by the client and accepts any value.
+property.server-fqdn.default-behavior.alias.synopsis=The server attempts to determine the fully-qualified domain name dynamically.
+property.server-fqdn.syntax.string.pattern.synopsis=The fully-qualified address that is expected for clients to use when connecting to the server and authenticating via DIGEST-MD5.
diff --git a/opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn.properties b/opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn.properties
new file mode 100644
index 0000000..e86d9b3
--- /dev/null
+++ b/opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn.properties
@@ -0,0 +1,7 @@
+user-friendly-name=Directory String Attribute Syntax
+user-friendly-plural-name=Directory String Attribute Syntaxes
+synopsis=The Directory String Attribute Syntax defines an attribute syntax for storing arbitrary string (and sometimes binary) data.
+property.allow-zero-length-values.synopsis=Indicates whether zero-length (that is, an empty string) values are allowed.
+property.allow-zero-length-values.description=This is technically not allowed by the revised LDAPv3 specification, but some environments may require it for backward compatibility with servers that do allow it.
+property.enabled.synopsis=Indicates whether the Directory String Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Directory String Attribute Syntax implementation.
diff --git a/opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_de.properties b/opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_de.properties
new file mode 100644
index 0000000..e86d9b3
--- /dev/null
+++ b/opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_de.properties
@@ -0,0 +1,7 @@
+user-friendly-name=Directory String Attribute Syntax
+user-friendly-plural-name=Directory String Attribute Syntaxes
+synopsis=The Directory String Attribute Syntax defines an attribute syntax for storing arbitrary string (and sometimes binary) data.
+property.allow-zero-length-values.synopsis=Indicates whether zero-length (that is, an empty string) values are allowed.
+property.allow-zero-length-values.description=This is technically not allowed by the revised LDAPv3 specification, but some environments may require it for backward compatibility with servers that do allow it.
+property.enabled.synopsis=Indicates whether the Directory String Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Directory String Attribute Syntax implementation.
diff --git a/opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_es.properties b/opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_es.properties
new file mode 100644
index 0000000..e86d9b3
--- /dev/null
+++ b/opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_es.properties
@@ -0,0 +1,7 @@
+user-friendly-name=Directory String Attribute Syntax
+user-friendly-plural-name=Directory String Attribute Syntaxes
+synopsis=The Directory String Attribute Syntax defines an attribute syntax for storing arbitrary string (and sometimes binary) data.
+property.allow-zero-length-values.synopsis=Indicates whether zero-length (that is, an empty string) values are allowed.
+property.allow-zero-length-values.description=This is technically not allowed by the revised LDAPv3 specification, but some environments may require it for backward compatibility with servers that do allow it.
+property.enabled.synopsis=Indicates whether the Directory String Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Directory String Attribute Syntax implementation.
diff --git a/opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_fr.properties b/opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_fr.properties
new file mode 100644
index 0000000..e86d9b3
--- /dev/null
+++ b/opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_fr.properties
@@ -0,0 +1,7 @@
+user-friendly-name=Directory String Attribute Syntax
+user-friendly-plural-name=Directory String Attribute Syntaxes
+synopsis=The Directory String Attribute Syntax defines an attribute syntax for storing arbitrary string (and sometimes binary) data.
+property.allow-zero-length-values.synopsis=Indicates whether zero-length (that is, an empty string) values are allowed.
+property.allow-zero-length-values.description=This is technically not allowed by the revised LDAPv3 specification, but some environments may require it for backward compatibility with servers that do allow it.
+property.enabled.synopsis=Indicates whether the Directory String Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Directory String Attribute Syntax implementation.
diff --git a/opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_ja.properties b/opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_ja.properties
new file mode 100644
index 0000000..e86d9b3
--- /dev/null
+++ b/opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_ja.properties
@@ -0,0 +1,7 @@
+user-friendly-name=Directory String Attribute Syntax
+user-friendly-plural-name=Directory String Attribute Syntaxes
+synopsis=The Directory String Attribute Syntax defines an attribute syntax for storing arbitrary string (and sometimes binary) data.
+property.allow-zero-length-values.synopsis=Indicates whether zero-length (that is, an empty string) values are allowed.
+property.allow-zero-length-values.description=This is technically not allowed by the revised LDAPv3 specification, but some environments may require it for backward compatibility with servers that do allow it.
+property.enabled.synopsis=Indicates whether the Directory String Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Directory String Attribute Syntax implementation.
diff --git a/opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_ko.properties b/opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_ko.properties
new file mode 100644
index 0000000..e86d9b3
--- /dev/null
+++ b/opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_ko.properties
@@ -0,0 +1,7 @@
+user-friendly-name=Directory String Attribute Syntax
+user-friendly-plural-name=Directory String Attribute Syntaxes
+synopsis=The Directory String Attribute Syntax defines an attribute syntax for storing arbitrary string (and sometimes binary) data.
+property.allow-zero-length-values.synopsis=Indicates whether zero-length (that is, an empty string) values are allowed.
+property.allow-zero-length-values.description=This is technically not allowed by the revised LDAPv3 specification, but some environments may require it for backward compatibility with servers that do allow it.
+property.enabled.synopsis=Indicates whether the Directory String Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Directory String Attribute Syntax implementation.
diff --git a/opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_zh_CN.properties b/opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..e86d9b3
--- /dev/null
+++ b/opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_zh_CN.properties
@@ -0,0 +1,7 @@
+user-friendly-name=Directory String Attribute Syntax
+user-friendly-plural-name=Directory String Attribute Syntaxes
+synopsis=The Directory String Attribute Syntax defines an attribute syntax for storing arbitrary string (and sometimes binary) data.
+property.allow-zero-length-values.synopsis=Indicates whether zero-length (that is, an empty string) values are allowed.
+property.allow-zero-length-values.description=This is technically not allowed by the revised LDAPv3 specification, but some environments may require it for backward compatibility with servers that do allow it.
+property.enabled.synopsis=Indicates whether the Directory String Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Directory String Attribute Syntax implementation.
diff --git a/opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_zh_TW.properties b/opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..e86d9b3
--- /dev/null
+++ b/opends/src/admin/messages/DirectoryStringAttributeSyntaxCfgDefn_zh_TW.properties
@@ -0,0 +1,7 @@
+user-friendly-name=Directory String Attribute Syntax
+user-friendly-plural-name=Directory String Attribute Syntaxes
+synopsis=The Directory String Attribute Syntax defines an attribute syntax for storing arbitrary string (and sometimes binary) data.
+property.allow-zero-length-values.synopsis=Indicates whether zero-length (that is, an empty string) values are allowed.
+property.allow-zero-length-values.description=This is technically not allowed by the revised LDAPv3 specification, but some environments may require it for backward compatibility with servers that do allow it.
+property.enabled.synopsis=Indicates whether the Directory String Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Directory String Attribute Syntax implementation.
diff --git a/opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn.properties b/opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn.properties
new file mode 100644
index 0000000..06dd8c3
--- /dev/null
+++ b/opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Dsee Compat Access Control Handler
+user-friendly-plural-name=Dseecompat Access Control Handlers
+synopsis=The Dsee Compat Access Control Handler provides an implementation that uses syntax compatible with the Sun Java System Directory Server Enterprise Edition access control handlers.
+property.enabled.synopsis=Indicates whether the Dsee Compat Access Control Handler is enabled. If set to FALSE, then no access control is enforced, and any client (including unauthenticated or anonymous clients) could be allowed to perform any operation if not subject to other restrictions, such as those enforced by the privilege subsystem.
+property.global-aci.synopsis=Defines global access control rules.
+property.global-aci.description=Global access control rules apply to all entries anywhere in the data managed by the Directory Server. The global access control rules may be overridden by more specific access control rules placed in the data.
+property.global-aci.default-behavior.alias.synopsis=No global access control rules are defined, which means that no access is allowed for any data in the server unless specifically granted by access control rules in the data.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Dsee Compat Access Control Handler implementation.
diff --git a/opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_de.properties b/opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..06dd8c3
--- /dev/null
+++ b/opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_de.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Dsee Compat Access Control Handler
+user-friendly-plural-name=Dseecompat Access Control Handlers
+synopsis=The Dsee Compat Access Control Handler provides an implementation that uses syntax compatible with the Sun Java System Directory Server Enterprise Edition access control handlers.
+property.enabled.synopsis=Indicates whether the Dsee Compat Access Control Handler is enabled. If set to FALSE, then no access control is enforced, and any client (including unauthenticated or anonymous clients) could be allowed to perform any operation if not subject to other restrictions, such as those enforced by the privilege subsystem.
+property.global-aci.synopsis=Defines global access control rules.
+property.global-aci.description=Global access control rules apply to all entries anywhere in the data managed by the Directory Server. The global access control rules may be overridden by more specific access control rules placed in the data.
+property.global-aci.default-behavior.alias.synopsis=No global access control rules are defined, which means that no access is allowed for any data in the server unless specifically granted by access control rules in the data.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Dsee Compat Access Control Handler implementation.
diff --git a/opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_es.properties b/opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..06dd8c3
--- /dev/null
+++ b/opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_es.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Dsee Compat Access Control Handler
+user-friendly-plural-name=Dseecompat Access Control Handlers
+synopsis=The Dsee Compat Access Control Handler provides an implementation that uses syntax compatible with the Sun Java System Directory Server Enterprise Edition access control handlers.
+property.enabled.synopsis=Indicates whether the Dsee Compat Access Control Handler is enabled. If set to FALSE, then no access control is enforced, and any client (including unauthenticated or anonymous clients) could be allowed to perform any operation if not subject to other restrictions, such as those enforced by the privilege subsystem.
+property.global-aci.synopsis=Defines global access control rules.
+property.global-aci.description=Global access control rules apply to all entries anywhere in the data managed by the Directory Server. The global access control rules may be overridden by more specific access control rules placed in the data.
+property.global-aci.default-behavior.alias.synopsis=No global access control rules are defined, which means that no access is allowed for any data in the server unless specifically granted by access control rules in the data.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Dsee Compat Access Control Handler implementation.
diff --git a/opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_fr.properties b/opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..06dd8c3
--- /dev/null
+++ b/opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_fr.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Dsee Compat Access Control Handler
+user-friendly-plural-name=Dseecompat Access Control Handlers
+synopsis=The Dsee Compat Access Control Handler provides an implementation that uses syntax compatible with the Sun Java System Directory Server Enterprise Edition access control handlers.
+property.enabled.synopsis=Indicates whether the Dsee Compat Access Control Handler is enabled. If set to FALSE, then no access control is enforced, and any client (including unauthenticated or anonymous clients) could be allowed to perform any operation if not subject to other restrictions, such as those enforced by the privilege subsystem.
+property.global-aci.synopsis=Defines global access control rules.
+property.global-aci.description=Global access control rules apply to all entries anywhere in the data managed by the Directory Server. The global access control rules may be overridden by more specific access control rules placed in the data.
+property.global-aci.default-behavior.alias.synopsis=No global access control rules are defined, which means that no access is allowed for any data in the server unless specifically granted by access control rules in the data.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Dsee Compat Access Control Handler implementation.
diff --git a/opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_ja.properties b/opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..06dd8c3
--- /dev/null
+++ b/opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_ja.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Dsee Compat Access Control Handler
+user-friendly-plural-name=Dseecompat Access Control Handlers
+synopsis=The Dsee Compat Access Control Handler provides an implementation that uses syntax compatible with the Sun Java System Directory Server Enterprise Edition access control handlers.
+property.enabled.synopsis=Indicates whether the Dsee Compat Access Control Handler is enabled. If set to FALSE, then no access control is enforced, and any client (including unauthenticated or anonymous clients) could be allowed to perform any operation if not subject to other restrictions, such as those enforced by the privilege subsystem.
+property.global-aci.synopsis=Defines global access control rules.
+property.global-aci.description=Global access control rules apply to all entries anywhere in the data managed by the Directory Server. The global access control rules may be overridden by more specific access control rules placed in the data.
+property.global-aci.default-behavior.alias.synopsis=No global access control rules are defined, which means that no access is allowed for any data in the server unless specifically granted by access control rules in the data.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Dsee Compat Access Control Handler implementation.
diff --git a/opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_ko.properties b/opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..06dd8c3
--- /dev/null
+++ b/opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_ko.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Dsee Compat Access Control Handler
+user-friendly-plural-name=Dseecompat Access Control Handlers
+synopsis=The Dsee Compat Access Control Handler provides an implementation that uses syntax compatible with the Sun Java System Directory Server Enterprise Edition access control handlers.
+property.enabled.synopsis=Indicates whether the Dsee Compat Access Control Handler is enabled. If set to FALSE, then no access control is enforced, and any client (including unauthenticated or anonymous clients) could be allowed to perform any operation if not subject to other restrictions, such as those enforced by the privilege subsystem.
+property.global-aci.synopsis=Defines global access control rules.
+property.global-aci.description=Global access control rules apply to all entries anywhere in the data managed by the Directory Server. The global access control rules may be overridden by more specific access control rules placed in the data.
+property.global-aci.default-behavior.alias.synopsis=No global access control rules are defined, which means that no access is allowed for any data in the server unless specifically granted by access control rules in the data.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Dsee Compat Access Control Handler implementation.
diff --git a/opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..06dd8c3
--- /dev/null
+++ b/opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Dsee Compat Access Control Handler
+user-friendly-plural-name=Dseecompat Access Control Handlers
+synopsis=The Dsee Compat Access Control Handler provides an implementation that uses syntax compatible with the Sun Java System Directory Server Enterprise Edition access control handlers.
+property.enabled.synopsis=Indicates whether the Dsee Compat Access Control Handler is enabled. If set to FALSE, then no access control is enforced, and any client (including unauthenticated or anonymous clients) could be allowed to perform any operation if not subject to other restrictions, such as those enforced by the privilege subsystem.
+property.global-aci.synopsis=Defines global access control rules.
+property.global-aci.description=Global access control rules apply to all entries anywhere in the data managed by the Directory Server. The global access control rules may be overridden by more specific access control rules placed in the data.
+property.global-aci.default-behavior.alias.synopsis=No global access control rules are defined, which means that no access is allowed for any data in the server unless specifically granted by access control rules in the data.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Dsee Compat Access Control Handler implementation.
diff --git a/opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..06dd8c3
--- /dev/null
+++ b/opends/src/admin/messages/DseeCompatAccessControlHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Dsee Compat Access Control Handler
+user-friendly-plural-name=Dseecompat Access Control Handlers
+synopsis=The Dsee Compat Access Control Handler provides an implementation that uses syntax compatible with the Sun Java System Directory Server Enterprise Edition access control handlers.
+property.enabled.synopsis=Indicates whether the Dsee Compat Access Control Handler is enabled. If set to FALSE, then no access control is enforced, and any client (including unauthenticated or anonymous clients) could be allowed to perform any operation if not subject to other restrictions, such as those enforced by the privilege subsystem.
+property.global-aci.synopsis=Defines global access control rules.
+property.global-aci.description=Global access control rules apply to all entries anywhere in the data managed by the Directory Server. The global access control rules may be overridden by more specific access control rules placed in the data.
+property.global-aci.default-behavior.alias.synopsis=No global access control rules are defined, which means that no access is allowed for any data in the server unless specifically granted by access control rules in the data.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Dsee Compat Access Control Handler implementation.
diff --git a/opends/src/admin/messages/DynamicGroupImplementationCfgDefn.properties b/opends/src/admin/messages/DynamicGroupImplementationCfgDefn.properties
new file mode 100644
index 0000000..58d9d76
--- /dev/null
+++ b/opends/src/admin/messages/DynamicGroupImplementationCfgDefn.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Dynamic Group Implementation
+user-friendly-plural-name=Dynamic Group Implementations
+synopsis=The Dynamic Group Implementation provides a grouping mechanism in which the group membership is determined based on criteria defined in one or more LDAP URLs.
+property.enabled.synopsis=Indicates whether the Dynamic Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Dynamic Group Implementation implementation.
diff --git a/opends/src/admin/messages/DynamicGroupImplementationCfgDefn_de.properties b/opends/src/admin/messages/DynamicGroupImplementationCfgDefn_de.properties
new file mode 100644
index 0000000..58d9d76
--- /dev/null
+++ b/opends/src/admin/messages/DynamicGroupImplementationCfgDefn_de.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Dynamic Group Implementation
+user-friendly-plural-name=Dynamic Group Implementations
+synopsis=The Dynamic Group Implementation provides a grouping mechanism in which the group membership is determined based on criteria defined in one or more LDAP URLs.
+property.enabled.synopsis=Indicates whether the Dynamic Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Dynamic Group Implementation implementation.
diff --git a/opends/src/admin/messages/DynamicGroupImplementationCfgDefn_es.properties b/opends/src/admin/messages/DynamicGroupImplementationCfgDefn_es.properties
new file mode 100644
index 0000000..58d9d76
--- /dev/null
+++ b/opends/src/admin/messages/DynamicGroupImplementationCfgDefn_es.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Dynamic Group Implementation
+user-friendly-plural-name=Dynamic Group Implementations
+synopsis=The Dynamic Group Implementation provides a grouping mechanism in which the group membership is determined based on criteria defined in one or more LDAP URLs.
+property.enabled.synopsis=Indicates whether the Dynamic Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Dynamic Group Implementation implementation.
diff --git a/opends/src/admin/messages/DynamicGroupImplementationCfgDefn_fr.properties b/opends/src/admin/messages/DynamicGroupImplementationCfgDefn_fr.properties
new file mode 100644
index 0000000..58d9d76
--- /dev/null
+++ b/opends/src/admin/messages/DynamicGroupImplementationCfgDefn_fr.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Dynamic Group Implementation
+user-friendly-plural-name=Dynamic Group Implementations
+synopsis=The Dynamic Group Implementation provides a grouping mechanism in which the group membership is determined based on criteria defined in one or more LDAP URLs.
+property.enabled.synopsis=Indicates whether the Dynamic Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Dynamic Group Implementation implementation.
diff --git a/opends/src/admin/messages/DynamicGroupImplementationCfgDefn_ja.properties b/opends/src/admin/messages/DynamicGroupImplementationCfgDefn_ja.properties
new file mode 100644
index 0000000..58d9d76
--- /dev/null
+++ b/opends/src/admin/messages/DynamicGroupImplementationCfgDefn_ja.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Dynamic Group Implementation
+user-friendly-plural-name=Dynamic Group Implementations
+synopsis=The Dynamic Group Implementation provides a grouping mechanism in which the group membership is determined based on criteria defined in one or more LDAP URLs.
+property.enabled.synopsis=Indicates whether the Dynamic Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Dynamic Group Implementation implementation.
diff --git a/opends/src/admin/messages/DynamicGroupImplementationCfgDefn_ko.properties b/opends/src/admin/messages/DynamicGroupImplementationCfgDefn_ko.properties
new file mode 100644
index 0000000..58d9d76
--- /dev/null
+++ b/opends/src/admin/messages/DynamicGroupImplementationCfgDefn_ko.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Dynamic Group Implementation
+user-friendly-plural-name=Dynamic Group Implementations
+synopsis=The Dynamic Group Implementation provides a grouping mechanism in which the group membership is determined based on criteria defined in one or more LDAP URLs.
+property.enabled.synopsis=Indicates whether the Dynamic Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Dynamic Group Implementation implementation.
diff --git a/opends/src/admin/messages/DynamicGroupImplementationCfgDefn_zh_CN.properties b/opends/src/admin/messages/DynamicGroupImplementationCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..58d9d76
--- /dev/null
+++ b/opends/src/admin/messages/DynamicGroupImplementationCfgDefn_zh_CN.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Dynamic Group Implementation
+user-friendly-plural-name=Dynamic Group Implementations
+synopsis=The Dynamic Group Implementation provides a grouping mechanism in which the group membership is determined based on criteria defined in one or more LDAP URLs.
+property.enabled.synopsis=Indicates whether the Dynamic Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Dynamic Group Implementation implementation.
diff --git a/opends/src/admin/messages/DynamicGroupImplementationCfgDefn_zh_TW.properties b/opends/src/admin/messages/DynamicGroupImplementationCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..58d9d76
--- /dev/null
+++ b/opends/src/admin/messages/DynamicGroupImplementationCfgDefn_zh_TW.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Dynamic Group Implementation
+user-friendly-plural-name=Dynamic Group Implementations
+synopsis=The Dynamic Group Implementation provides a grouping mechanism in which the group membership is determined based on criteria defined in one or more LDAP URLs.
+property.enabled.synopsis=Indicates whether the Dynamic Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Dynamic Group Implementation implementation.
diff --git a/opends/src/admin/messages/EntryCacheCfgDefn.properties b/opends/src/admin/messages/EntryCacheCfgDefn.properties
new file mode 100644
index 0000000..f3da6f8
--- /dev/null
+++ b/opends/src/admin/messages/EntryCacheCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Entry Cache
+user-friendly-plural-name=Entry Caches
+synopsis=Entry Caches are responsible for caching entries which are likely to be accessed by client applications in order to improve Directory Server performance.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.enabled.synopsis=Indicates whether the Entry Cache is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Entry Cache implementation.
diff --git a/opends/src/admin/messages/EntryCacheCfgDefn_de.properties b/opends/src/admin/messages/EntryCacheCfgDefn_de.properties
new file mode 100644
index 0000000..f3da6f8
--- /dev/null
+++ b/opends/src/admin/messages/EntryCacheCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Entry Cache
+user-friendly-plural-name=Entry Caches
+synopsis=Entry Caches are responsible for caching entries which are likely to be accessed by client applications in order to improve Directory Server performance.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.enabled.synopsis=Indicates whether the Entry Cache is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Entry Cache implementation.
diff --git a/opends/src/admin/messages/EntryCacheCfgDefn_es.properties b/opends/src/admin/messages/EntryCacheCfgDefn_es.properties
new file mode 100644
index 0000000..f3da6f8
--- /dev/null
+++ b/opends/src/admin/messages/EntryCacheCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Entry Cache
+user-friendly-plural-name=Entry Caches
+synopsis=Entry Caches are responsible for caching entries which are likely to be accessed by client applications in order to improve Directory Server performance.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.enabled.synopsis=Indicates whether the Entry Cache is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Entry Cache implementation.
diff --git a/opends/src/admin/messages/EntryCacheCfgDefn_fr.properties b/opends/src/admin/messages/EntryCacheCfgDefn_fr.properties
new file mode 100644
index 0000000..f3da6f8
--- /dev/null
+++ b/opends/src/admin/messages/EntryCacheCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Entry Cache
+user-friendly-plural-name=Entry Caches
+synopsis=Entry Caches are responsible for caching entries which are likely to be accessed by client applications in order to improve Directory Server performance.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.enabled.synopsis=Indicates whether the Entry Cache is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Entry Cache implementation.
diff --git a/opends/src/admin/messages/EntryCacheCfgDefn_ja.properties b/opends/src/admin/messages/EntryCacheCfgDefn_ja.properties
new file mode 100644
index 0000000..f3da6f8
--- /dev/null
+++ b/opends/src/admin/messages/EntryCacheCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Entry Cache
+user-friendly-plural-name=Entry Caches
+synopsis=Entry Caches are responsible for caching entries which are likely to be accessed by client applications in order to improve Directory Server performance.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.enabled.synopsis=Indicates whether the Entry Cache is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Entry Cache implementation.
diff --git a/opends/src/admin/messages/EntryCacheCfgDefn_ko.properties b/opends/src/admin/messages/EntryCacheCfgDefn_ko.properties
new file mode 100644
index 0000000..f3da6f8
--- /dev/null
+++ b/opends/src/admin/messages/EntryCacheCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Entry Cache
+user-friendly-plural-name=Entry Caches
+synopsis=Entry Caches are responsible for caching entries which are likely to be accessed by client applications in order to improve Directory Server performance.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.enabled.synopsis=Indicates whether the Entry Cache is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Entry Cache implementation.
diff --git a/opends/src/admin/messages/EntryCacheCfgDefn_zh_CN.properties b/opends/src/admin/messages/EntryCacheCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..f3da6f8
--- /dev/null
+++ b/opends/src/admin/messages/EntryCacheCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Entry Cache
+user-friendly-plural-name=Entry Caches
+synopsis=Entry Caches are responsible for caching entries which are likely to be accessed by client applications in order to improve Directory Server performance.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.enabled.synopsis=Indicates whether the Entry Cache is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Entry Cache implementation.
diff --git a/opends/src/admin/messages/EntryCacheCfgDefn_zh_TW.properties b/opends/src/admin/messages/EntryCacheCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..f3da6f8
--- /dev/null
+++ b/opends/src/admin/messages/EntryCacheCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Entry Cache
+user-friendly-plural-name=Entry Caches
+synopsis=Entry Caches are responsible for caching entries which are likely to be accessed by client applications in order to improve Directory Server performance.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.enabled.synopsis=Indicates whether the Entry Cache is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Entry Cache implementation.
diff --git a/opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn.properties b/opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn.properties
new file mode 100644
index 0000000..0785243
--- /dev/null
+++ b/opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Entry Cache Monitor Provider
+user-friendly-plural-name=Entry Cache Monitor Providers
+synopsis=The Entry Cache Monitor Provider exposes monitor information about the state of Directory Server entry caches.
+property.enabled.synopsis=Indicates whether the Entry Cache Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Entry Cache Monitor Provider implementation.
diff --git a/opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_de.properties b/opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_de.properties
new file mode 100644
index 0000000..0785243
--- /dev/null
+++ b/opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_de.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Entry Cache Monitor Provider
+user-friendly-plural-name=Entry Cache Monitor Providers
+synopsis=The Entry Cache Monitor Provider exposes monitor information about the state of Directory Server entry caches.
+property.enabled.synopsis=Indicates whether the Entry Cache Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Entry Cache Monitor Provider implementation.
diff --git a/opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_es.properties b/opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_es.properties
new file mode 100644
index 0000000..0785243
--- /dev/null
+++ b/opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_es.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Entry Cache Monitor Provider
+user-friendly-plural-name=Entry Cache Monitor Providers
+synopsis=The Entry Cache Monitor Provider exposes monitor information about the state of Directory Server entry caches.
+property.enabled.synopsis=Indicates whether the Entry Cache Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Entry Cache Monitor Provider implementation.
diff --git a/opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_fr.properties b/opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_fr.properties
new file mode 100644
index 0000000..0785243
--- /dev/null
+++ b/opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_fr.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Entry Cache Monitor Provider
+user-friendly-plural-name=Entry Cache Monitor Providers
+synopsis=The Entry Cache Monitor Provider exposes monitor information about the state of Directory Server entry caches.
+property.enabled.synopsis=Indicates whether the Entry Cache Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Entry Cache Monitor Provider implementation.
diff --git a/opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_ja.properties b/opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_ja.properties
new file mode 100644
index 0000000..0785243
--- /dev/null
+++ b/opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_ja.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Entry Cache Monitor Provider
+user-friendly-plural-name=Entry Cache Monitor Providers
+synopsis=The Entry Cache Monitor Provider exposes monitor information about the state of Directory Server entry caches.
+property.enabled.synopsis=Indicates whether the Entry Cache Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Entry Cache Monitor Provider implementation.
diff --git a/opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_ko.properties b/opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_ko.properties
new file mode 100644
index 0000000..0785243
--- /dev/null
+++ b/opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_ko.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Entry Cache Monitor Provider
+user-friendly-plural-name=Entry Cache Monitor Providers
+synopsis=The Entry Cache Monitor Provider exposes monitor information about the state of Directory Server entry caches.
+property.enabled.synopsis=Indicates whether the Entry Cache Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Entry Cache Monitor Provider implementation.
diff --git a/opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_zh_CN.properties b/opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..0785243
--- /dev/null
+++ b/opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_zh_CN.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Entry Cache Monitor Provider
+user-friendly-plural-name=Entry Cache Monitor Providers
+synopsis=The Entry Cache Monitor Provider exposes monitor information about the state of Directory Server entry caches.
+property.enabled.synopsis=Indicates whether the Entry Cache Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Entry Cache Monitor Provider implementation.
diff --git a/opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_zh_TW.properties b/opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..0785243
--- /dev/null
+++ b/opends/src/admin/messages/EntryCacheMonitorProviderCfgDefn_zh_TW.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Entry Cache Monitor Provider
+user-friendly-plural-name=Entry Cache Monitor Providers
+synopsis=The Entry Cache Monitor Provider exposes monitor information about the state of Directory Server entry caches.
+property.enabled.synopsis=Indicates whether the Entry Cache Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Entry Cache Monitor Provider implementation.
diff --git a/opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn.properties b/opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn.properties
new file mode 100644
index 0000000..496f627
--- /dev/null
+++ b/opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Entry DN Virtual Attribute
+user-friendly-plural-name=Entry DN Virtual Attributes
+synopsis=The Entry DN Virtual Attribute generates the entryDN operational attribute in directory entries, which contains a normalized form of the entry's DN.
+description=This attribute is defined in the draft-zeilenga-ldap-entrydn Internet Draft and contains the DN of the entry in which it is contained. This component provides the ability to use search filters containing the entry's DN.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Entry DN Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_de.properties b/opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_de.properties
new file mode 100644
index 0000000..496f627
--- /dev/null
+++ b/opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_de.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Entry DN Virtual Attribute
+user-friendly-plural-name=Entry DN Virtual Attributes
+synopsis=The Entry DN Virtual Attribute generates the entryDN operational attribute in directory entries, which contains a normalized form of the entry's DN.
+description=This attribute is defined in the draft-zeilenga-ldap-entrydn Internet Draft and contains the DN of the entry in which it is contained. This component provides the ability to use search filters containing the entry's DN.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Entry DN Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_es.properties b/opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_es.properties
new file mode 100644
index 0000000..496f627
--- /dev/null
+++ b/opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_es.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Entry DN Virtual Attribute
+user-friendly-plural-name=Entry DN Virtual Attributes
+synopsis=The Entry DN Virtual Attribute generates the entryDN operational attribute in directory entries, which contains a normalized form of the entry's DN.
+description=This attribute is defined in the draft-zeilenga-ldap-entrydn Internet Draft and contains the DN of the entry in which it is contained. This component provides the ability to use search filters containing the entry's DN.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Entry DN Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_fr.properties b/opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_fr.properties
new file mode 100644
index 0000000..496f627
--- /dev/null
+++ b/opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_fr.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Entry DN Virtual Attribute
+user-friendly-plural-name=Entry DN Virtual Attributes
+synopsis=The Entry DN Virtual Attribute generates the entryDN operational attribute in directory entries, which contains a normalized form of the entry's DN.
+description=This attribute is defined in the draft-zeilenga-ldap-entrydn Internet Draft and contains the DN of the entry in which it is contained. This component provides the ability to use search filters containing the entry's DN.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Entry DN Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_ja.properties b/opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_ja.properties
new file mode 100644
index 0000000..496f627
--- /dev/null
+++ b/opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_ja.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Entry DN Virtual Attribute
+user-friendly-plural-name=Entry DN Virtual Attributes
+synopsis=The Entry DN Virtual Attribute generates the entryDN operational attribute in directory entries, which contains a normalized form of the entry's DN.
+description=This attribute is defined in the draft-zeilenga-ldap-entrydn Internet Draft and contains the DN of the entry in which it is contained. This component provides the ability to use search filters containing the entry's DN.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Entry DN Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_ko.properties b/opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_ko.properties
new file mode 100644
index 0000000..496f627
--- /dev/null
+++ b/opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_ko.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Entry DN Virtual Attribute
+user-friendly-plural-name=Entry DN Virtual Attributes
+synopsis=The Entry DN Virtual Attribute generates the entryDN operational attribute in directory entries, which contains a normalized form of the entry's DN.
+description=This attribute is defined in the draft-zeilenga-ldap-entrydn Internet Draft and contains the DN of the entry in which it is contained. This component provides the ability to use search filters containing the entry's DN.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Entry DN Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_zh_CN.properties b/opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..496f627
--- /dev/null
+++ b/opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_zh_CN.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Entry DN Virtual Attribute
+user-friendly-plural-name=Entry DN Virtual Attributes
+synopsis=The Entry DN Virtual Attribute generates the entryDN operational attribute in directory entries, which contains a normalized form of the entry's DN.
+description=This attribute is defined in the draft-zeilenga-ldap-entrydn Internet Draft and contains the DN of the entry in which it is contained. This component provides the ability to use search filters containing the entry's DN.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Entry DN Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_zh_TW.properties b/opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..496f627
--- /dev/null
+++ b/opends/src/admin/messages/EntryDNVirtualAttributeCfgDefn_zh_TW.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Entry DN Virtual Attribute
+user-friendly-plural-name=Entry DN Virtual Attributes
+synopsis=The Entry DN Virtual Attribute generates the entryDN operational attribute in directory entries, which contains a normalized form of the entry's DN.
+description=This attribute is defined in the draft-zeilenga-ldap-entrydn Internet Draft and contains the DN of the entry in which it is contained. This component provides the ability to use search filters containing the entry's DN.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Entry DN Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/EntryUUIDPluginCfgDefn.properties b/opends/src/admin/messages/EntryUUIDPluginCfgDefn.properties
new file mode 100644
index 0000000..ec32bb8
--- /dev/null
+++ b/opends/src/admin/messages/EntryUUIDPluginCfgDefn.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Entry UUID Plugin
+user-friendly-plural-name=Entry UUID Plugins
+synopsis=The Entry UUID Plugin generates values for the entryUUID operational attribute whenever an entry is added via protocol or imported from LDIF.
+description=The entryUUID plug-in ensures that all entries added to the server, whether through an LDAP add operation or via an LDIF import, are assigned an entryUUID operational attribute if they do not already have one. The entryUUID attribute contains a universally unique identifier that can be used to identify an entry in a manner that does not change (even in the event of a modify DN operation). This plug-in generates a random UUID for entries created by an add operation, but the UUID is constructed from the DN of the entry during an LDIF import (which means that the same LDIF file can be imported on different systems but still get the same value for the entryUUID attribute). This behavior is based on the specification contained in RFC 4530. The implementation for the entry UUID plug-in is contained in the org.opends.server.plugins.EntryUUIDPlugin class. It must be configured with the preOperationAdd and ldifImport plug-in types, but it does not have any other custom configuration. This plug-in must be enabled in any directory that is intended to be used in a synchronization environment.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/EntryUUIDPluginCfgDefn_de.properties b/opends/src/admin/messages/EntryUUIDPluginCfgDefn_de.properties
new file mode 100644
index 0000000..ec32bb8
--- /dev/null
+++ b/opends/src/admin/messages/EntryUUIDPluginCfgDefn_de.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Entry UUID Plugin
+user-friendly-plural-name=Entry UUID Plugins
+synopsis=The Entry UUID Plugin generates values for the entryUUID operational attribute whenever an entry is added via protocol or imported from LDIF.
+description=The entryUUID plug-in ensures that all entries added to the server, whether through an LDAP add operation or via an LDIF import, are assigned an entryUUID operational attribute if they do not already have one. The entryUUID attribute contains a universally unique identifier that can be used to identify an entry in a manner that does not change (even in the event of a modify DN operation). This plug-in generates a random UUID for entries created by an add operation, but the UUID is constructed from the DN of the entry during an LDIF import (which means that the same LDIF file can be imported on different systems but still get the same value for the entryUUID attribute). This behavior is based on the specification contained in RFC 4530. The implementation for the entry UUID plug-in is contained in the org.opends.server.plugins.EntryUUIDPlugin class. It must be configured with the preOperationAdd and ldifImport plug-in types, but it does not have any other custom configuration. This plug-in must be enabled in any directory that is intended to be used in a synchronization environment.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/EntryUUIDPluginCfgDefn_es.properties b/opends/src/admin/messages/EntryUUIDPluginCfgDefn_es.properties
new file mode 100644
index 0000000..ec32bb8
--- /dev/null
+++ b/opends/src/admin/messages/EntryUUIDPluginCfgDefn_es.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Entry UUID Plugin
+user-friendly-plural-name=Entry UUID Plugins
+synopsis=The Entry UUID Plugin generates values for the entryUUID operational attribute whenever an entry is added via protocol or imported from LDIF.
+description=The entryUUID plug-in ensures that all entries added to the server, whether through an LDAP add operation or via an LDIF import, are assigned an entryUUID operational attribute if they do not already have one. The entryUUID attribute contains a universally unique identifier that can be used to identify an entry in a manner that does not change (even in the event of a modify DN operation). This plug-in generates a random UUID for entries created by an add operation, but the UUID is constructed from the DN of the entry during an LDIF import (which means that the same LDIF file can be imported on different systems but still get the same value for the entryUUID attribute). This behavior is based on the specification contained in RFC 4530. The implementation for the entry UUID plug-in is contained in the org.opends.server.plugins.EntryUUIDPlugin class. It must be configured with the preOperationAdd and ldifImport plug-in types, but it does not have any other custom configuration. This plug-in must be enabled in any directory that is intended to be used in a synchronization environment.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/EntryUUIDPluginCfgDefn_fr.properties b/opends/src/admin/messages/EntryUUIDPluginCfgDefn_fr.properties
new file mode 100644
index 0000000..ec32bb8
--- /dev/null
+++ b/opends/src/admin/messages/EntryUUIDPluginCfgDefn_fr.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Entry UUID Plugin
+user-friendly-plural-name=Entry UUID Plugins
+synopsis=The Entry UUID Plugin generates values for the entryUUID operational attribute whenever an entry is added via protocol or imported from LDIF.
+description=The entryUUID plug-in ensures that all entries added to the server, whether through an LDAP add operation or via an LDIF import, are assigned an entryUUID operational attribute if they do not already have one. The entryUUID attribute contains a universally unique identifier that can be used to identify an entry in a manner that does not change (even in the event of a modify DN operation). This plug-in generates a random UUID for entries created by an add operation, but the UUID is constructed from the DN of the entry during an LDIF import (which means that the same LDIF file can be imported on different systems but still get the same value for the entryUUID attribute). This behavior is based on the specification contained in RFC 4530. The implementation for the entry UUID plug-in is contained in the org.opends.server.plugins.EntryUUIDPlugin class. It must be configured with the preOperationAdd and ldifImport plug-in types, but it does not have any other custom configuration. This plug-in must be enabled in any directory that is intended to be used in a synchronization environment.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/EntryUUIDPluginCfgDefn_ja.properties b/opends/src/admin/messages/EntryUUIDPluginCfgDefn_ja.properties
new file mode 100644
index 0000000..ec32bb8
--- /dev/null
+++ b/opends/src/admin/messages/EntryUUIDPluginCfgDefn_ja.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Entry UUID Plugin
+user-friendly-plural-name=Entry UUID Plugins
+synopsis=The Entry UUID Plugin generates values for the entryUUID operational attribute whenever an entry is added via protocol or imported from LDIF.
+description=The entryUUID plug-in ensures that all entries added to the server, whether through an LDAP add operation or via an LDIF import, are assigned an entryUUID operational attribute if they do not already have one. The entryUUID attribute contains a universally unique identifier that can be used to identify an entry in a manner that does not change (even in the event of a modify DN operation). This plug-in generates a random UUID for entries created by an add operation, but the UUID is constructed from the DN of the entry during an LDIF import (which means that the same LDIF file can be imported on different systems but still get the same value for the entryUUID attribute). This behavior is based on the specification contained in RFC 4530. The implementation for the entry UUID plug-in is contained in the org.opends.server.plugins.EntryUUIDPlugin class. It must be configured with the preOperationAdd and ldifImport plug-in types, but it does not have any other custom configuration. This plug-in must be enabled in any directory that is intended to be used in a synchronization environment.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/EntryUUIDPluginCfgDefn_ko.properties b/opends/src/admin/messages/EntryUUIDPluginCfgDefn_ko.properties
new file mode 100644
index 0000000..ec32bb8
--- /dev/null
+++ b/opends/src/admin/messages/EntryUUIDPluginCfgDefn_ko.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Entry UUID Plugin
+user-friendly-plural-name=Entry UUID Plugins
+synopsis=The Entry UUID Plugin generates values for the entryUUID operational attribute whenever an entry is added via protocol or imported from LDIF.
+description=The entryUUID plug-in ensures that all entries added to the server, whether through an LDAP add operation or via an LDIF import, are assigned an entryUUID operational attribute if they do not already have one. The entryUUID attribute contains a universally unique identifier that can be used to identify an entry in a manner that does not change (even in the event of a modify DN operation). This plug-in generates a random UUID for entries created by an add operation, but the UUID is constructed from the DN of the entry during an LDIF import (which means that the same LDIF file can be imported on different systems but still get the same value for the entryUUID attribute). This behavior is based on the specification contained in RFC 4530. The implementation for the entry UUID plug-in is contained in the org.opends.server.plugins.EntryUUIDPlugin class. It must be configured with the preOperationAdd and ldifImport plug-in types, but it does not have any other custom configuration. This plug-in must be enabled in any directory that is intended to be used in a synchronization environment.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/EntryUUIDPluginCfgDefn_zh_CN.properties b/opends/src/admin/messages/EntryUUIDPluginCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..ec32bb8
--- /dev/null
+++ b/opends/src/admin/messages/EntryUUIDPluginCfgDefn_zh_CN.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Entry UUID Plugin
+user-friendly-plural-name=Entry UUID Plugins
+synopsis=The Entry UUID Plugin generates values for the entryUUID operational attribute whenever an entry is added via protocol or imported from LDIF.
+description=The entryUUID plug-in ensures that all entries added to the server, whether through an LDAP add operation or via an LDIF import, are assigned an entryUUID operational attribute if they do not already have one. The entryUUID attribute contains a universally unique identifier that can be used to identify an entry in a manner that does not change (even in the event of a modify DN operation). This plug-in generates a random UUID for entries created by an add operation, but the UUID is constructed from the DN of the entry during an LDIF import (which means that the same LDIF file can be imported on different systems but still get the same value for the entryUUID attribute). This behavior is based on the specification contained in RFC 4530. The implementation for the entry UUID plug-in is contained in the org.opends.server.plugins.EntryUUIDPlugin class. It must be configured with the preOperationAdd and ldifImport plug-in types, but it does not have any other custom configuration. This plug-in must be enabled in any directory that is intended to be used in a synchronization environment.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/EntryUUIDPluginCfgDefn_zh_TW.properties b/opends/src/admin/messages/EntryUUIDPluginCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..ec32bb8
--- /dev/null
+++ b/opends/src/admin/messages/EntryUUIDPluginCfgDefn_zh_TW.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Entry UUID Plugin
+user-friendly-plural-name=Entry UUID Plugins
+synopsis=The Entry UUID Plugin generates values for the entryUUID operational attribute whenever an entry is added via protocol or imported from LDIF.
+description=The entryUUID plug-in ensures that all entries added to the server, whether through an LDAP add operation or via an LDIF import, are assigned an entryUUID operational attribute if they do not already have one. The entryUUID attribute contains a universally unique identifier that can be used to identify an entry in a manner that does not change (even in the event of a modify DN operation). This plug-in generates a random UUID for entries created by an add operation, but the UUID is constructed from the DN of the entry during an LDIF import (which means that the same LDIF file can be imported on different systems but still get the same value for the entryUUID attribute). This behavior is based on the specification contained in RFC 4530. The implementation for the entry UUID plug-in is contained in the org.opends.server.plugins.EntryUUIDPlugin class. It must be configured with the preOperationAdd and ldifImport plug-in types, but it does not have any other custom configuration. This plug-in must be enabled in any directory that is intended to be used in a synchronization environment.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn.properties b/opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn.properties
new file mode 100644
index 0000000..8e4fb8d
--- /dev/null
+++ b/opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Entry UUID Virtual Attribute
+user-friendly-plural-name=Entry UUID Virtual Attributes
+synopsis=The Entry UUID Virtual Attribute ensures that all entries contained in private backends have values for the entryUUID operational attribute.
+description=The entryUUID values are generated based on a normalized representation of the entry's DN, which does not cause a consistency problem because OpenDS does not allow modify DN operations to be performed in private backends.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Entry UUID Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_de.properties b/opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_de.properties
new file mode 100644
index 0000000..8e4fb8d
--- /dev/null
+++ b/opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_de.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Entry UUID Virtual Attribute
+user-friendly-plural-name=Entry UUID Virtual Attributes
+synopsis=The Entry UUID Virtual Attribute ensures that all entries contained in private backends have values for the entryUUID operational attribute.
+description=The entryUUID values are generated based on a normalized representation of the entry's DN, which does not cause a consistency problem because OpenDS does not allow modify DN operations to be performed in private backends.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Entry UUID Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_es.properties b/opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_es.properties
new file mode 100644
index 0000000..8e4fb8d
--- /dev/null
+++ b/opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_es.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Entry UUID Virtual Attribute
+user-friendly-plural-name=Entry UUID Virtual Attributes
+synopsis=The Entry UUID Virtual Attribute ensures that all entries contained in private backends have values for the entryUUID operational attribute.
+description=The entryUUID values are generated based on a normalized representation of the entry's DN, which does not cause a consistency problem because OpenDS does not allow modify DN operations to be performed in private backends.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Entry UUID Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_fr.properties b/opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_fr.properties
new file mode 100644
index 0000000..8e4fb8d
--- /dev/null
+++ b/opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_fr.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Entry UUID Virtual Attribute
+user-friendly-plural-name=Entry UUID Virtual Attributes
+synopsis=The Entry UUID Virtual Attribute ensures that all entries contained in private backends have values for the entryUUID operational attribute.
+description=The entryUUID values are generated based on a normalized representation of the entry's DN, which does not cause a consistency problem because OpenDS does not allow modify DN operations to be performed in private backends.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Entry UUID Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_ja.properties b/opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_ja.properties
new file mode 100644
index 0000000..8e4fb8d
--- /dev/null
+++ b/opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_ja.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Entry UUID Virtual Attribute
+user-friendly-plural-name=Entry UUID Virtual Attributes
+synopsis=The Entry UUID Virtual Attribute ensures that all entries contained in private backends have values for the entryUUID operational attribute.
+description=The entryUUID values are generated based on a normalized representation of the entry's DN, which does not cause a consistency problem because OpenDS does not allow modify DN operations to be performed in private backends.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Entry UUID Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_ko.properties b/opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_ko.properties
new file mode 100644
index 0000000..8e4fb8d
--- /dev/null
+++ b/opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_ko.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Entry UUID Virtual Attribute
+user-friendly-plural-name=Entry UUID Virtual Attributes
+synopsis=The Entry UUID Virtual Attribute ensures that all entries contained in private backends have values for the entryUUID operational attribute.
+description=The entryUUID values are generated based on a normalized representation of the entry's DN, which does not cause a consistency problem because OpenDS does not allow modify DN operations to be performed in private backends.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Entry UUID Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_zh_CN.properties b/opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..8e4fb8d
--- /dev/null
+++ b/opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_zh_CN.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Entry UUID Virtual Attribute
+user-friendly-plural-name=Entry UUID Virtual Attributes
+synopsis=The Entry UUID Virtual Attribute ensures that all entries contained in private backends have values for the entryUUID operational attribute.
+description=The entryUUID values are generated based on a normalized representation of the entry's DN, which does not cause a consistency problem because OpenDS does not allow modify DN operations to be performed in private backends.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Entry UUID Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_zh_TW.properties b/opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..8e4fb8d
--- /dev/null
+++ b/opends/src/admin/messages/EntryUUIDVirtualAttributeCfgDefn_zh_TW.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Entry UUID Virtual Attribute
+user-friendly-plural-name=Entry UUID Virtual Attributes
+synopsis=The Entry UUID Virtual Attribute ensures that all entries contained in private backends have values for the entryUUID operational attribute.
+description=The entryUUID values are generated based on a normalized representation of the entry's DN, which does not cause a consistency problem because OpenDS does not allow modify DN operations to be performed in private backends.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Entry UUID Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/EqualityMatchingRuleCfgDefn.properties b/opends/src/admin/messages/EqualityMatchingRuleCfgDefn.properties
new file mode 100644
index 0000000..3de7e48
--- /dev/null
+++ b/opends/src/admin/messages/EqualityMatchingRuleCfgDefn.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Equality Matching Rule
+user-friendly-plural-name=Equality Matching Rules
+synopsis=Equality Matching Rules define a set of rules for performing equality matching operations against assertion values (that is, to determine whether an attribute value equals an assertion value).
+property.enabled.synopsis=Indicates whether the Equality Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Equality Matching Rule implementation.
diff --git a/opends/src/admin/messages/EqualityMatchingRuleCfgDefn_de.properties b/opends/src/admin/messages/EqualityMatchingRuleCfgDefn_de.properties
new file mode 100644
index 0000000..3de7e48
--- /dev/null
+++ b/opends/src/admin/messages/EqualityMatchingRuleCfgDefn_de.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Equality Matching Rule
+user-friendly-plural-name=Equality Matching Rules
+synopsis=Equality Matching Rules define a set of rules for performing equality matching operations against assertion values (that is, to determine whether an attribute value equals an assertion value).
+property.enabled.synopsis=Indicates whether the Equality Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Equality Matching Rule implementation.
diff --git a/opends/src/admin/messages/EqualityMatchingRuleCfgDefn_es.properties b/opends/src/admin/messages/EqualityMatchingRuleCfgDefn_es.properties
new file mode 100644
index 0000000..3de7e48
--- /dev/null
+++ b/opends/src/admin/messages/EqualityMatchingRuleCfgDefn_es.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Equality Matching Rule
+user-friendly-plural-name=Equality Matching Rules
+synopsis=Equality Matching Rules define a set of rules for performing equality matching operations against assertion values (that is, to determine whether an attribute value equals an assertion value).
+property.enabled.synopsis=Indicates whether the Equality Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Equality Matching Rule implementation.
diff --git a/opends/src/admin/messages/EqualityMatchingRuleCfgDefn_fr.properties b/opends/src/admin/messages/EqualityMatchingRuleCfgDefn_fr.properties
new file mode 100644
index 0000000..3de7e48
--- /dev/null
+++ b/opends/src/admin/messages/EqualityMatchingRuleCfgDefn_fr.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Equality Matching Rule
+user-friendly-plural-name=Equality Matching Rules
+synopsis=Equality Matching Rules define a set of rules for performing equality matching operations against assertion values (that is, to determine whether an attribute value equals an assertion value).
+property.enabled.synopsis=Indicates whether the Equality Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Equality Matching Rule implementation.
diff --git a/opends/src/admin/messages/EqualityMatchingRuleCfgDefn_ja.properties b/opends/src/admin/messages/EqualityMatchingRuleCfgDefn_ja.properties
new file mode 100644
index 0000000..3de7e48
--- /dev/null
+++ b/opends/src/admin/messages/EqualityMatchingRuleCfgDefn_ja.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Equality Matching Rule
+user-friendly-plural-name=Equality Matching Rules
+synopsis=Equality Matching Rules define a set of rules for performing equality matching operations against assertion values (that is, to determine whether an attribute value equals an assertion value).
+property.enabled.synopsis=Indicates whether the Equality Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Equality Matching Rule implementation.
diff --git a/opends/src/admin/messages/EqualityMatchingRuleCfgDefn_ko.properties b/opends/src/admin/messages/EqualityMatchingRuleCfgDefn_ko.properties
new file mode 100644
index 0000000..3de7e48
--- /dev/null
+++ b/opends/src/admin/messages/EqualityMatchingRuleCfgDefn_ko.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Equality Matching Rule
+user-friendly-plural-name=Equality Matching Rules
+synopsis=Equality Matching Rules define a set of rules for performing equality matching operations against assertion values (that is, to determine whether an attribute value equals an assertion value).
+property.enabled.synopsis=Indicates whether the Equality Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Equality Matching Rule implementation.
diff --git a/opends/src/admin/messages/EqualityMatchingRuleCfgDefn_zh_CN.properties b/opends/src/admin/messages/EqualityMatchingRuleCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..3de7e48
--- /dev/null
+++ b/opends/src/admin/messages/EqualityMatchingRuleCfgDefn_zh_CN.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Equality Matching Rule
+user-friendly-plural-name=Equality Matching Rules
+synopsis=Equality Matching Rules define a set of rules for performing equality matching operations against assertion values (that is, to determine whether an attribute value equals an assertion value).
+property.enabled.synopsis=Indicates whether the Equality Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Equality Matching Rule implementation.
diff --git a/opends/src/admin/messages/EqualityMatchingRuleCfgDefn_zh_TW.properties b/opends/src/admin/messages/EqualityMatchingRuleCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..3de7e48
--- /dev/null
+++ b/opends/src/admin/messages/EqualityMatchingRuleCfgDefn_zh_TW.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Equality Matching Rule
+user-friendly-plural-name=Equality Matching Rules
+synopsis=Equality Matching Rules define a set of rules for performing equality matching operations against assertion values (that is, to determine whether an attribute value equals an assertion value).
+property.enabled.synopsis=Indicates whether the Equality Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Equality Matching Rule implementation.
diff --git a/opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn.properties b/opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn.properties
new file mode 100644
index 0000000..a596ded
--- /dev/null
+++ b/opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn.properties
@@ -0,0 +1,18 @@
+user-friendly-name=Error Log Account Status Notification Handler
+user-friendly-plural-name=Error Log Account Status Notification Handlers
+synopsis=The Error Log Account Status Notification Handler is a notification handler that writes information to the server error log whenever an appropriate account status event occurs.
+property.account-status-notification-type.synopsis=Indicates which types of event can trigger an account status notification.
+property.account-status-notification-type.syntax.enumeration.value.account-disabled.synopsis=Generate a notification whenever a user account has been disabled by an administrator.
+property.account-status-notification-type.syntax.enumeration.value.account-enabled.synopsis=Generate a notification whenever a user account has been enabled by an administrator.
+property.account-status-notification-type.syntax.enumeration.value.account-expired.synopsis=Generate a notification whenever a user authentication has failed because the account has expired.
+property.account-status-notification-type.syntax.enumeration.value.account-idle-locked.synopsis=Generate a notification whenever a user account has been locked because it was idle for too long.
+property.account-status-notification-type.syntax.enumeration.value.account-permanently-locked.synopsis=Generate a notification whenever a user account has been permanently locked after too many failed attempts.
+property.account-status-notification-type.syntax.enumeration.value.account-reset-locked.synopsis=Generate a notification whenever a user account has been locked, because the password had been reset by an administrator but not changed by the user within the required interval.
+property.account-status-notification-type.syntax.enumeration.value.account-temporarily-locked.synopsis=Generate a notification whenever a user account has been temporarily locked after too many failed attempts.
+property.account-status-notification-type.syntax.enumeration.value.account-unlocked.synopsis=Generate a notification whenever a user account has been unlocked by an administrator.
+property.account-status-notification-type.syntax.enumeration.value.password-changed.synopsis=Generate a notification whenever a user changes his/her own password.
+property.account-status-notification-type.syntax.enumeration.value.password-expired.synopsis=Generate a notification whenever a user authentication has failed because the password has expired.
+property.account-status-notification-type.syntax.enumeration.value.password-expiring.synopsis=Generate a notification whenever a password expiration warning is encountered for a user password for the first time.
+property.account-status-notification-type.syntax.enumeration.value.password-reset.synopsis=Generate a notification whenever a user's password is reset by an administrator.
+property.enabled.synopsis=Indicates whether the Error Log Account Status Notification Handler is enabled. Only enabled handlers are invoked whenever a related event occurs in the server.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Error Log Account Status Notification Handler implementation.
diff --git a/opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_de.properties b/opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..a596ded
--- /dev/null
+++ b/opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_de.properties
@@ -0,0 +1,18 @@
+user-friendly-name=Error Log Account Status Notification Handler
+user-friendly-plural-name=Error Log Account Status Notification Handlers
+synopsis=The Error Log Account Status Notification Handler is a notification handler that writes information to the server error log whenever an appropriate account status event occurs.
+property.account-status-notification-type.synopsis=Indicates which types of event can trigger an account status notification.
+property.account-status-notification-type.syntax.enumeration.value.account-disabled.synopsis=Generate a notification whenever a user account has been disabled by an administrator.
+property.account-status-notification-type.syntax.enumeration.value.account-enabled.synopsis=Generate a notification whenever a user account has been enabled by an administrator.
+property.account-status-notification-type.syntax.enumeration.value.account-expired.synopsis=Generate a notification whenever a user authentication has failed because the account has expired.
+property.account-status-notification-type.syntax.enumeration.value.account-idle-locked.synopsis=Generate a notification whenever a user account has been locked because it was idle for too long.
+property.account-status-notification-type.syntax.enumeration.value.account-permanently-locked.synopsis=Generate a notification whenever a user account has been permanently locked after too many failed attempts.
+property.account-status-notification-type.syntax.enumeration.value.account-reset-locked.synopsis=Generate a notification whenever a user account has been locked, because the password had been reset by an administrator but not changed by the user within the required interval.
+property.account-status-notification-type.syntax.enumeration.value.account-temporarily-locked.synopsis=Generate a notification whenever a user account has been temporarily locked after too many failed attempts.
+property.account-status-notification-type.syntax.enumeration.value.account-unlocked.synopsis=Generate a notification whenever a user account has been unlocked by an administrator.
+property.account-status-notification-type.syntax.enumeration.value.password-changed.synopsis=Generate a notification whenever a user changes his/her own password.
+property.account-status-notification-type.syntax.enumeration.value.password-expired.synopsis=Generate a notification whenever a user authentication has failed because the password has expired.
+property.account-status-notification-type.syntax.enumeration.value.password-expiring.synopsis=Generate a notification whenever a password expiration warning is encountered for a user password for the first time.
+property.account-status-notification-type.syntax.enumeration.value.password-reset.synopsis=Generate a notification whenever a user's password is reset by an administrator.
+property.enabled.synopsis=Indicates whether the Error Log Account Status Notification Handler is enabled. Only enabled handlers are invoked whenever a related event occurs in the server.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Error Log Account Status Notification Handler implementation.
diff --git a/opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_es.properties b/opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..a596ded
--- /dev/null
+++ b/opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_es.properties
@@ -0,0 +1,18 @@
+user-friendly-name=Error Log Account Status Notification Handler
+user-friendly-plural-name=Error Log Account Status Notification Handlers
+synopsis=The Error Log Account Status Notification Handler is a notification handler that writes information to the server error log whenever an appropriate account status event occurs.
+property.account-status-notification-type.synopsis=Indicates which types of event can trigger an account status notification.
+property.account-status-notification-type.syntax.enumeration.value.account-disabled.synopsis=Generate a notification whenever a user account has been disabled by an administrator.
+property.account-status-notification-type.syntax.enumeration.value.account-enabled.synopsis=Generate a notification whenever a user account has been enabled by an administrator.
+property.account-status-notification-type.syntax.enumeration.value.account-expired.synopsis=Generate a notification whenever a user authentication has failed because the account has expired.
+property.account-status-notification-type.syntax.enumeration.value.account-idle-locked.synopsis=Generate a notification whenever a user account has been locked because it was idle for too long.
+property.account-status-notification-type.syntax.enumeration.value.account-permanently-locked.synopsis=Generate a notification whenever a user account has been permanently locked after too many failed attempts.
+property.account-status-notification-type.syntax.enumeration.value.account-reset-locked.synopsis=Generate a notification whenever a user account has been locked, because the password had been reset by an administrator but not changed by the user within the required interval.
+property.account-status-notification-type.syntax.enumeration.value.account-temporarily-locked.synopsis=Generate a notification whenever a user account has been temporarily locked after too many failed attempts.
+property.account-status-notification-type.syntax.enumeration.value.account-unlocked.synopsis=Generate a notification whenever a user account has been unlocked by an administrator.
+property.account-status-notification-type.syntax.enumeration.value.password-changed.synopsis=Generate a notification whenever a user changes his/her own password.
+property.account-status-notification-type.syntax.enumeration.value.password-expired.synopsis=Generate a notification whenever a user authentication has failed because the password has expired.
+property.account-status-notification-type.syntax.enumeration.value.password-expiring.synopsis=Generate a notification whenever a password expiration warning is encountered for a user password for the first time.
+property.account-status-notification-type.syntax.enumeration.value.password-reset.synopsis=Generate a notification whenever a user's password is reset by an administrator.
+property.enabled.synopsis=Indicates whether the Error Log Account Status Notification Handler is enabled. Only enabled handlers are invoked whenever a related event occurs in the server.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Error Log Account Status Notification Handler implementation.
diff --git a/opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_fr.properties b/opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..a596ded
--- /dev/null
+++ b/opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_fr.properties
@@ -0,0 +1,18 @@
+user-friendly-name=Error Log Account Status Notification Handler
+user-friendly-plural-name=Error Log Account Status Notification Handlers
+synopsis=The Error Log Account Status Notification Handler is a notification handler that writes information to the server error log whenever an appropriate account status event occurs.
+property.account-status-notification-type.synopsis=Indicates which types of event can trigger an account status notification.
+property.account-status-notification-type.syntax.enumeration.value.account-disabled.synopsis=Generate a notification whenever a user account has been disabled by an administrator.
+property.account-status-notification-type.syntax.enumeration.value.account-enabled.synopsis=Generate a notification whenever a user account has been enabled by an administrator.
+property.account-status-notification-type.syntax.enumeration.value.account-expired.synopsis=Generate a notification whenever a user authentication has failed because the account has expired.
+property.account-status-notification-type.syntax.enumeration.value.account-idle-locked.synopsis=Generate a notification whenever a user account has been locked because it was idle for too long.
+property.account-status-notification-type.syntax.enumeration.value.account-permanently-locked.synopsis=Generate a notification whenever a user account has been permanently locked after too many failed attempts.
+property.account-status-notification-type.syntax.enumeration.value.account-reset-locked.synopsis=Generate a notification whenever a user account has been locked, because the password had been reset by an administrator but not changed by the user within the required interval.
+property.account-status-notification-type.syntax.enumeration.value.account-temporarily-locked.synopsis=Generate a notification whenever a user account has been temporarily locked after too many failed attempts.
+property.account-status-notification-type.syntax.enumeration.value.account-unlocked.synopsis=Generate a notification whenever a user account has been unlocked by an administrator.
+property.account-status-notification-type.syntax.enumeration.value.password-changed.synopsis=Generate a notification whenever a user changes his/her own password.
+property.account-status-notification-type.syntax.enumeration.value.password-expired.synopsis=Generate a notification whenever a user authentication has failed because the password has expired.
+property.account-status-notification-type.syntax.enumeration.value.password-expiring.synopsis=Generate a notification whenever a password expiration warning is encountered for a user password for the first time.
+property.account-status-notification-type.syntax.enumeration.value.password-reset.synopsis=Generate a notification whenever a user's password is reset by an administrator.
+property.enabled.synopsis=Indicates whether the Error Log Account Status Notification Handler is enabled. Only enabled handlers are invoked whenever a related event occurs in the server.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Error Log Account Status Notification Handler implementation.
diff --git a/opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_ja.properties b/opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..a596ded
--- /dev/null
+++ b/opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_ja.properties
@@ -0,0 +1,18 @@
+user-friendly-name=Error Log Account Status Notification Handler
+user-friendly-plural-name=Error Log Account Status Notification Handlers
+synopsis=The Error Log Account Status Notification Handler is a notification handler that writes information to the server error log whenever an appropriate account status event occurs.
+property.account-status-notification-type.synopsis=Indicates which types of event can trigger an account status notification.
+property.account-status-notification-type.syntax.enumeration.value.account-disabled.synopsis=Generate a notification whenever a user account has been disabled by an administrator.
+property.account-status-notification-type.syntax.enumeration.value.account-enabled.synopsis=Generate a notification whenever a user account has been enabled by an administrator.
+property.account-status-notification-type.syntax.enumeration.value.account-expired.synopsis=Generate a notification whenever a user authentication has failed because the account has expired.
+property.account-status-notification-type.syntax.enumeration.value.account-idle-locked.synopsis=Generate a notification whenever a user account has been locked because it was idle for too long.
+property.account-status-notification-type.syntax.enumeration.value.account-permanently-locked.synopsis=Generate a notification whenever a user account has been permanently locked after too many failed attempts.
+property.account-status-notification-type.syntax.enumeration.value.account-reset-locked.synopsis=Generate a notification whenever a user account has been locked, because the password had been reset by an administrator but not changed by the user within the required interval.
+property.account-status-notification-type.syntax.enumeration.value.account-temporarily-locked.synopsis=Generate a notification whenever a user account has been temporarily locked after too many failed attempts.
+property.account-status-notification-type.syntax.enumeration.value.account-unlocked.synopsis=Generate a notification whenever a user account has been unlocked by an administrator.
+property.account-status-notification-type.syntax.enumeration.value.password-changed.synopsis=Generate a notification whenever a user changes his/her own password.
+property.account-status-notification-type.syntax.enumeration.value.password-expired.synopsis=Generate a notification whenever a user authentication has failed because the password has expired.
+property.account-status-notification-type.syntax.enumeration.value.password-expiring.synopsis=Generate a notification whenever a password expiration warning is encountered for a user password for the first time.
+property.account-status-notification-type.syntax.enumeration.value.password-reset.synopsis=Generate a notification whenever a user's password is reset by an administrator.
+property.enabled.synopsis=Indicates whether the Error Log Account Status Notification Handler is enabled. Only enabled handlers are invoked whenever a related event occurs in the server.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Error Log Account Status Notification Handler implementation.
diff --git a/opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_ko.properties b/opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..a596ded
--- /dev/null
+++ b/opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_ko.properties
@@ -0,0 +1,18 @@
+user-friendly-name=Error Log Account Status Notification Handler
+user-friendly-plural-name=Error Log Account Status Notification Handlers
+synopsis=The Error Log Account Status Notification Handler is a notification handler that writes information to the server error log whenever an appropriate account status event occurs.
+property.account-status-notification-type.synopsis=Indicates which types of event can trigger an account status notification.
+property.account-status-notification-type.syntax.enumeration.value.account-disabled.synopsis=Generate a notification whenever a user account has been disabled by an administrator.
+property.account-status-notification-type.syntax.enumeration.value.account-enabled.synopsis=Generate a notification whenever a user account has been enabled by an administrator.
+property.account-status-notification-type.syntax.enumeration.value.account-expired.synopsis=Generate a notification whenever a user authentication has failed because the account has expired.
+property.account-status-notification-type.syntax.enumeration.value.account-idle-locked.synopsis=Generate a notification whenever a user account has been locked because it was idle for too long.
+property.account-status-notification-type.syntax.enumeration.value.account-permanently-locked.synopsis=Generate a notification whenever a user account has been permanently locked after too many failed attempts.
+property.account-status-notification-type.syntax.enumeration.value.account-reset-locked.synopsis=Generate a notification whenever a user account has been locked, because the password had been reset by an administrator but not changed by the user within the required interval.
+property.account-status-notification-type.syntax.enumeration.value.account-temporarily-locked.synopsis=Generate a notification whenever a user account has been temporarily locked after too many failed attempts.
+property.account-status-notification-type.syntax.enumeration.value.account-unlocked.synopsis=Generate a notification whenever a user account has been unlocked by an administrator.
+property.account-status-notification-type.syntax.enumeration.value.password-changed.synopsis=Generate a notification whenever a user changes his/her own password.
+property.account-status-notification-type.syntax.enumeration.value.password-expired.synopsis=Generate a notification whenever a user authentication has failed because the password has expired.
+property.account-status-notification-type.syntax.enumeration.value.password-expiring.synopsis=Generate a notification whenever a password expiration warning is encountered for a user password for the first time.
+property.account-status-notification-type.syntax.enumeration.value.password-reset.synopsis=Generate a notification whenever a user's password is reset by an administrator.
+property.enabled.synopsis=Indicates whether the Error Log Account Status Notification Handler is enabled. Only enabled handlers are invoked whenever a related event occurs in the server.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Error Log Account Status Notification Handler implementation.
diff --git a/opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..a596ded
--- /dev/null
+++ b/opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,18 @@
+user-friendly-name=Error Log Account Status Notification Handler
+user-friendly-plural-name=Error Log Account Status Notification Handlers
+synopsis=The Error Log Account Status Notification Handler is a notification handler that writes information to the server error log whenever an appropriate account status event occurs.
+property.account-status-notification-type.synopsis=Indicates which types of event can trigger an account status notification.
+property.account-status-notification-type.syntax.enumeration.value.account-disabled.synopsis=Generate a notification whenever a user account has been disabled by an administrator.
+property.account-status-notification-type.syntax.enumeration.value.account-enabled.synopsis=Generate a notification whenever a user account has been enabled by an administrator.
+property.account-status-notification-type.syntax.enumeration.value.account-expired.synopsis=Generate a notification whenever a user authentication has failed because the account has expired.
+property.account-status-notification-type.syntax.enumeration.value.account-idle-locked.synopsis=Generate a notification whenever a user account has been locked because it was idle for too long.
+property.account-status-notification-type.syntax.enumeration.value.account-permanently-locked.synopsis=Generate a notification whenever a user account has been permanently locked after too many failed attempts.
+property.account-status-notification-type.syntax.enumeration.value.account-reset-locked.synopsis=Generate a notification whenever a user account has been locked, because the password had been reset by an administrator but not changed by the user within the required interval.
+property.account-status-notification-type.syntax.enumeration.value.account-temporarily-locked.synopsis=Generate a notification whenever a user account has been temporarily locked after too many failed attempts.
+property.account-status-notification-type.syntax.enumeration.value.account-unlocked.synopsis=Generate a notification whenever a user account has been unlocked by an administrator.
+property.account-status-notification-type.syntax.enumeration.value.password-changed.synopsis=Generate a notification whenever a user changes his/her own password.
+property.account-status-notification-type.syntax.enumeration.value.password-expired.synopsis=Generate a notification whenever a user authentication has failed because the password has expired.
+property.account-status-notification-type.syntax.enumeration.value.password-expiring.synopsis=Generate a notification whenever a password expiration warning is encountered for a user password for the first time.
+property.account-status-notification-type.syntax.enumeration.value.password-reset.synopsis=Generate a notification whenever a user's password is reset by an administrator.
+property.enabled.synopsis=Indicates whether the Error Log Account Status Notification Handler is enabled. Only enabled handlers are invoked whenever a related event occurs in the server.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Error Log Account Status Notification Handler implementation.
diff --git a/opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..a596ded
--- /dev/null
+++ b/opends/src/admin/messages/ErrorLogAccountStatusNotificationHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,18 @@
+user-friendly-name=Error Log Account Status Notification Handler
+user-friendly-plural-name=Error Log Account Status Notification Handlers
+synopsis=The Error Log Account Status Notification Handler is a notification handler that writes information to the server error log whenever an appropriate account status event occurs.
+property.account-status-notification-type.synopsis=Indicates which types of event can trigger an account status notification.
+property.account-status-notification-type.syntax.enumeration.value.account-disabled.synopsis=Generate a notification whenever a user account has been disabled by an administrator.
+property.account-status-notification-type.syntax.enumeration.value.account-enabled.synopsis=Generate a notification whenever a user account has been enabled by an administrator.
+property.account-status-notification-type.syntax.enumeration.value.account-expired.synopsis=Generate a notification whenever a user authentication has failed because the account has expired.
+property.account-status-notification-type.syntax.enumeration.value.account-idle-locked.synopsis=Generate a notification whenever a user account has been locked because it was idle for too long.
+property.account-status-notification-type.syntax.enumeration.value.account-permanently-locked.synopsis=Generate a notification whenever a user account has been permanently locked after too many failed attempts.
+property.account-status-notification-type.syntax.enumeration.value.account-reset-locked.synopsis=Generate a notification whenever a user account has been locked, because the password had been reset by an administrator but not changed by the user within the required interval.
+property.account-status-notification-type.syntax.enumeration.value.account-temporarily-locked.synopsis=Generate a notification whenever a user account has been temporarily locked after too many failed attempts.
+property.account-status-notification-type.syntax.enumeration.value.account-unlocked.synopsis=Generate a notification whenever a user account has been unlocked by an administrator.
+property.account-status-notification-type.syntax.enumeration.value.password-changed.synopsis=Generate a notification whenever a user changes his/her own password.
+property.account-status-notification-type.syntax.enumeration.value.password-expired.synopsis=Generate a notification whenever a user authentication has failed because the password has expired.
+property.account-status-notification-type.syntax.enumeration.value.password-expiring.synopsis=Generate a notification whenever a password expiration warning is encountered for a user password for the first time.
+property.account-status-notification-type.syntax.enumeration.value.password-reset.synopsis=Generate a notification whenever a user's password is reset by an administrator.
+property.enabled.synopsis=Indicates whether the Error Log Account Status Notification Handler is enabled. Only enabled handlers are invoked whenever a related event occurs in the server.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Error Log Account Status Notification Handler implementation.
diff --git a/opends/src/admin/messages/ErrorLogPublisherCfgDefn.properties b/opends/src/admin/messages/ErrorLogPublisherCfgDefn.properties
new file mode 100644
index 0000000..ae05071
--- /dev/null
+++ b/opends/src/admin/messages/ErrorLogPublisherCfgDefn.properties
@@ -0,0 +1,21 @@
+user-friendly-name=Error Log Publisher
+user-friendly-plural-name=Error Log Publishers
+synopsis=Error Log Publishers are responsible for distributing error log messages from the error logger to a destination.
+description=Error log messages provide information about any warnings, errors, or significant events that are encountered during server processing.
+property.default-severity.synopsis=Specifies the default severity levels for the logger.
+property.default-severity.syntax.enumeration.value.all.synopsis=Messages of all severity levels are logged.
+property.default-severity.syntax.enumeration.value.debug.synopsis=The error log severity that is used for messages that provide debugging information triggered during processing.
+property.default-severity.syntax.enumeration.value.fatal-error.synopsis=The error log severity that is used for messages that provide information about fatal errors which may force the server to shut down or operate in a significantly degraded state.
+property.default-severity.syntax.enumeration.value.info.synopsis=The error log severity that is used for messages that provide information about significant events within the server that are not warnings or errors.
+property.default-severity.syntax.enumeration.value.mild-error.synopsis=The error log severity that is used for messages that provide information about mild (recoverable) errors encountered during processing.
+property.default-severity.syntax.enumeration.value.mild-warning.synopsis=The error log severity that is used for messages that provide information about mild warnings triggered during processing.
+property.default-severity.syntax.enumeration.value.none.synopsis=No messages of any severity are logged by default. This value is intended to be used in conjunction with the override-severity property to define an error logger that will publish no error message beside the errors of a given category.
+property.default-severity.syntax.enumeration.value.notice.synopsis=The error log severity that is used for the most important informational messages (i.e., information that should almost always be logged but is not associated with a warning or error condition).
+property.default-severity.syntax.enumeration.value.severe-error.synopsis=The error log severity that is used for messages that provide information about severe errors encountered during processing.
+property.default-severity.syntax.enumeration.value.severe-warning.synopsis=The error log severity that is used for messages that provide information about severe warnings triggered during processing.
+property.enabled.synopsis=Indicates whether the Error Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Error Log Publisher implementation.
+property.override-severity.synopsis=Specifies the override severity levels for the logger based on the category of the messages.
+property.override-severity.description=Each override severity level should include the category and the severity levels to log for that category, for example, core=mild-error,info,mild-warning. Valid categories are: core, extensions, protocol, config, log, util, schema, plugin, jeb, backend, tools, task, access-control, admin, sync, version, quicksetup, admin-tool, dsconfig, user-defined. Valid severities are: all, fatal-error, info, mild-error, mild-warning, notice, severe-error, severe-warning, debug.
+property.override-severity.default-behavior.alias.synopsis=All messages with the default severity levels are logged.
+property.override-severity.syntax.string.pattern.synopsis=A string in the form category=severity1,severity2...
diff --git a/opends/src/admin/messages/ErrorLogPublisherCfgDefn_de.properties b/opends/src/admin/messages/ErrorLogPublisherCfgDefn_de.properties
new file mode 100644
index 0000000..ae05071
--- /dev/null
+++ b/opends/src/admin/messages/ErrorLogPublisherCfgDefn_de.properties
@@ -0,0 +1,21 @@
+user-friendly-name=Error Log Publisher
+user-friendly-plural-name=Error Log Publishers
+synopsis=Error Log Publishers are responsible for distributing error log messages from the error logger to a destination.
+description=Error log messages provide information about any warnings, errors, or significant events that are encountered during server processing.
+property.default-severity.synopsis=Specifies the default severity levels for the logger.
+property.default-severity.syntax.enumeration.value.all.synopsis=Messages of all severity levels are logged.
+property.default-severity.syntax.enumeration.value.debug.synopsis=The error log severity that is used for messages that provide debugging information triggered during processing.
+property.default-severity.syntax.enumeration.value.fatal-error.synopsis=The error log severity that is used for messages that provide information about fatal errors which may force the server to shut down or operate in a significantly degraded state.
+property.default-severity.syntax.enumeration.value.info.synopsis=The error log severity that is used for messages that provide information about significant events within the server that are not warnings or errors.
+property.default-severity.syntax.enumeration.value.mild-error.synopsis=The error log severity that is used for messages that provide information about mild (recoverable) errors encountered during processing.
+property.default-severity.syntax.enumeration.value.mild-warning.synopsis=The error log severity that is used for messages that provide information about mild warnings triggered during processing.
+property.default-severity.syntax.enumeration.value.none.synopsis=No messages of any severity are logged by default. This value is intended to be used in conjunction with the override-severity property to define an error logger that will publish no error message beside the errors of a given category.
+property.default-severity.syntax.enumeration.value.notice.synopsis=The error log severity that is used for the most important informational messages (i.e., information that should almost always be logged but is not associated with a warning or error condition).
+property.default-severity.syntax.enumeration.value.severe-error.synopsis=The error log severity that is used for messages that provide information about severe errors encountered during processing.
+property.default-severity.syntax.enumeration.value.severe-warning.synopsis=The error log severity that is used for messages that provide information about severe warnings triggered during processing.
+property.enabled.synopsis=Indicates whether the Error Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Error Log Publisher implementation.
+property.override-severity.synopsis=Specifies the override severity levels for the logger based on the category of the messages.
+property.override-severity.description=Each override severity level should include the category and the severity levels to log for that category, for example, core=mild-error,info,mild-warning. Valid categories are: core, extensions, protocol, config, log, util, schema, plugin, jeb, backend, tools, task, access-control, admin, sync, version, quicksetup, admin-tool, dsconfig, user-defined. Valid severities are: all, fatal-error, info, mild-error, mild-warning, notice, severe-error, severe-warning, debug.
+property.override-severity.default-behavior.alias.synopsis=All messages with the default severity levels are logged.
+property.override-severity.syntax.string.pattern.synopsis=A string in the form category=severity1,severity2...
diff --git a/opends/src/admin/messages/ErrorLogPublisherCfgDefn_es.properties b/opends/src/admin/messages/ErrorLogPublisherCfgDefn_es.properties
new file mode 100644
index 0000000..ae05071
--- /dev/null
+++ b/opends/src/admin/messages/ErrorLogPublisherCfgDefn_es.properties
@@ -0,0 +1,21 @@
+user-friendly-name=Error Log Publisher
+user-friendly-plural-name=Error Log Publishers
+synopsis=Error Log Publishers are responsible for distributing error log messages from the error logger to a destination.
+description=Error log messages provide information about any warnings, errors, or significant events that are encountered during server processing.
+property.default-severity.synopsis=Specifies the default severity levels for the logger.
+property.default-severity.syntax.enumeration.value.all.synopsis=Messages of all severity levels are logged.
+property.default-severity.syntax.enumeration.value.debug.synopsis=The error log severity that is used for messages that provide debugging information triggered during processing.
+property.default-severity.syntax.enumeration.value.fatal-error.synopsis=The error log severity that is used for messages that provide information about fatal errors which may force the server to shut down or operate in a significantly degraded state.
+property.default-severity.syntax.enumeration.value.info.synopsis=The error log severity that is used for messages that provide information about significant events within the server that are not warnings or errors.
+property.default-severity.syntax.enumeration.value.mild-error.synopsis=The error log severity that is used for messages that provide information about mild (recoverable) errors encountered during processing.
+property.default-severity.syntax.enumeration.value.mild-warning.synopsis=The error log severity that is used for messages that provide information about mild warnings triggered during processing.
+property.default-severity.syntax.enumeration.value.none.synopsis=No messages of any severity are logged by default. This value is intended to be used in conjunction with the override-severity property to define an error logger that will publish no error message beside the errors of a given category.
+property.default-severity.syntax.enumeration.value.notice.synopsis=The error log severity that is used for the most important informational messages (i.e., information that should almost always be logged but is not associated with a warning or error condition).
+property.default-severity.syntax.enumeration.value.severe-error.synopsis=The error log severity that is used for messages that provide information about severe errors encountered during processing.
+property.default-severity.syntax.enumeration.value.severe-warning.synopsis=The error log severity that is used for messages that provide information about severe warnings triggered during processing.
+property.enabled.synopsis=Indicates whether the Error Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Error Log Publisher implementation.
+property.override-severity.synopsis=Specifies the override severity levels for the logger based on the category of the messages.
+property.override-severity.description=Each override severity level should include the category and the severity levels to log for that category, for example, core=mild-error,info,mild-warning. Valid categories are: core, extensions, protocol, config, log, util, schema, plugin, jeb, backend, tools, task, access-control, admin, sync, version, quicksetup, admin-tool, dsconfig, user-defined. Valid severities are: all, fatal-error, info, mild-error, mild-warning, notice, severe-error, severe-warning, debug.
+property.override-severity.default-behavior.alias.synopsis=All messages with the default severity levels are logged.
+property.override-severity.syntax.string.pattern.synopsis=A string in the form category=severity1,severity2...
diff --git a/opends/src/admin/messages/ErrorLogPublisherCfgDefn_fr.properties b/opends/src/admin/messages/ErrorLogPublisherCfgDefn_fr.properties
new file mode 100644
index 0000000..ae05071
--- /dev/null
+++ b/opends/src/admin/messages/ErrorLogPublisherCfgDefn_fr.properties
@@ -0,0 +1,21 @@
+user-friendly-name=Error Log Publisher
+user-friendly-plural-name=Error Log Publishers
+synopsis=Error Log Publishers are responsible for distributing error log messages from the error logger to a destination.
+description=Error log messages provide information about any warnings, errors, or significant events that are encountered during server processing.
+property.default-severity.synopsis=Specifies the default severity levels for the logger.
+property.default-severity.syntax.enumeration.value.all.synopsis=Messages of all severity levels are logged.
+property.default-severity.syntax.enumeration.value.debug.synopsis=The error log severity that is used for messages that provide debugging information triggered during processing.
+property.default-severity.syntax.enumeration.value.fatal-error.synopsis=The error log severity that is used for messages that provide information about fatal errors which may force the server to shut down or operate in a significantly degraded state.
+property.default-severity.syntax.enumeration.value.info.synopsis=The error log severity that is used for messages that provide information about significant events within the server that are not warnings or errors.
+property.default-severity.syntax.enumeration.value.mild-error.synopsis=The error log severity that is used for messages that provide information about mild (recoverable) errors encountered during processing.
+property.default-severity.syntax.enumeration.value.mild-warning.synopsis=The error log severity that is used for messages that provide information about mild warnings triggered during processing.
+property.default-severity.syntax.enumeration.value.none.synopsis=No messages of any severity are logged by default. This value is intended to be used in conjunction with the override-severity property to define an error logger that will publish no error message beside the errors of a given category.
+property.default-severity.syntax.enumeration.value.notice.synopsis=The error log severity that is used for the most important informational messages (i.e., information that should almost always be logged but is not associated with a warning or error condition).
+property.default-severity.syntax.enumeration.value.severe-error.synopsis=The error log severity that is used for messages that provide information about severe errors encountered during processing.
+property.default-severity.syntax.enumeration.value.severe-warning.synopsis=The error log severity that is used for messages that provide information about severe warnings triggered during processing.
+property.enabled.synopsis=Indicates whether the Error Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Error Log Publisher implementation.
+property.override-severity.synopsis=Specifies the override severity levels for the logger based on the category of the messages.
+property.override-severity.description=Each override severity level should include the category and the severity levels to log for that category, for example, core=mild-error,info,mild-warning. Valid categories are: core, extensions, protocol, config, log, util, schema, plugin, jeb, backend, tools, task, access-control, admin, sync, version, quicksetup, admin-tool, dsconfig, user-defined. Valid severities are: all, fatal-error, info, mild-error, mild-warning, notice, severe-error, severe-warning, debug.
+property.override-severity.default-behavior.alias.synopsis=All messages with the default severity levels are logged.
+property.override-severity.syntax.string.pattern.synopsis=A string in the form category=severity1,severity2...
diff --git a/opends/src/admin/messages/ErrorLogPublisherCfgDefn_ja.properties b/opends/src/admin/messages/ErrorLogPublisherCfgDefn_ja.properties
new file mode 100644
index 0000000..ae05071
--- /dev/null
+++ b/opends/src/admin/messages/ErrorLogPublisherCfgDefn_ja.properties
@@ -0,0 +1,21 @@
+user-friendly-name=Error Log Publisher
+user-friendly-plural-name=Error Log Publishers
+synopsis=Error Log Publishers are responsible for distributing error log messages from the error logger to a destination.
+description=Error log messages provide information about any warnings, errors, or significant events that are encountered during server processing.
+property.default-severity.synopsis=Specifies the default severity levels for the logger.
+property.default-severity.syntax.enumeration.value.all.synopsis=Messages of all severity levels are logged.
+property.default-severity.syntax.enumeration.value.debug.synopsis=The error log severity that is used for messages that provide debugging information triggered during processing.
+property.default-severity.syntax.enumeration.value.fatal-error.synopsis=The error log severity that is used for messages that provide information about fatal errors which may force the server to shut down or operate in a significantly degraded state.
+property.default-severity.syntax.enumeration.value.info.synopsis=The error log severity that is used for messages that provide information about significant events within the server that are not warnings or errors.
+property.default-severity.syntax.enumeration.value.mild-error.synopsis=The error log severity that is used for messages that provide information about mild (recoverable) errors encountered during processing.
+property.default-severity.syntax.enumeration.value.mild-warning.synopsis=The error log severity that is used for messages that provide information about mild warnings triggered during processing.
+property.default-severity.syntax.enumeration.value.none.synopsis=No messages of any severity are logged by default. This value is intended to be used in conjunction with the override-severity property to define an error logger that will publish no error message beside the errors of a given category.
+property.default-severity.syntax.enumeration.value.notice.synopsis=The error log severity that is used for the most important informational messages (i.e., information that should almost always be logged but is not associated with a warning or error condition).
+property.default-severity.syntax.enumeration.value.severe-error.synopsis=The error log severity that is used for messages that provide information about severe errors encountered during processing.
+property.default-severity.syntax.enumeration.value.severe-warning.synopsis=The error log severity that is used for messages that provide information about severe warnings triggered during processing.
+property.enabled.synopsis=Indicates whether the Error Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Error Log Publisher implementation.
+property.override-severity.synopsis=Specifies the override severity levels for the logger based on the category of the messages.
+property.override-severity.description=Each override severity level should include the category and the severity levels to log for that category, for example, core=mild-error,info,mild-warning. Valid categories are: core, extensions, protocol, config, log, util, schema, plugin, jeb, backend, tools, task, access-control, admin, sync, version, quicksetup, admin-tool, dsconfig, user-defined. Valid severities are: all, fatal-error, info, mild-error, mild-warning, notice, severe-error, severe-warning, debug.
+property.override-severity.default-behavior.alias.synopsis=All messages with the default severity levels are logged.
+property.override-severity.syntax.string.pattern.synopsis=A string in the form category=severity1,severity2...
diff --git a/opends/src/admin/messages/ErrorLogPublisherCfgDefn_ko.properties b/opends/src/admin/messages/ErrorLogPublisherCfgDefn_ko.properties
new file mode 100644
index 0000000..ae05071
--- /dev/null
+++ b/opends/src/admin/messages/ErrorLogPublisherCfgDefn_ko.properties
@@ -0,0 +1,21 @@
+user-friendly-name=Error Log Publisher
+user-friendly-plural-name=Error Log Publishers
+synopsis=Error Log Publishers are responsible for distributing error log messages from the error logger to a destination.
+description=Error log messages provide information about any warnings, errors, or significant events that are encountered during server processing.
+property.default-severity.synopsis=Specifies the default severity levels for the logger.
+property.default-severity.syntax.enumeration.value.all.synopsis=Messages of all severity levels are logged.
+property.default-severity.syntax.enumeration.value.debug.synopsis=The error log severity that is used for messages that provide debugging information triggered during processing.
+property.default-severity.syntax.enumeration.value.fatal-error.synopsis=The error log severity that is used for messages that provide information about fatal errors which may force the server to shut down or operate in a significantly degraded state.
+property.default-severity.syntax.enumeration.value.info.synopsis=The error log severity that is used for messages that provide information about significant events within the server that are not warnings or errors.
+property.default-severity.syntax.enumeration.value.mild-error.synopsis=The error log severity that is used for messages that provide information about mild (recoverable) errors encountered during processing.
+property.default-severity.syntax.enumeration.value.mild-warning.synopsis=The error log severity that is used for messages that provide information about mild warnings triggered during processing.
+property.default-severity.syntax.enumeration.value.none.synopsis=No messages of any severity are logged by default. This value is intended to be used in conjunction with the override-severity property to define an error logger that will publish no error message beside the errors of a given category.
+property.default-severity.syntax.enumeration.value.notice.synopsis=The error log severity that is used for the most important informational messages (i.e., information that should almost always be logged but is not associated with a warning or error condition).
+property.default-severity.syntax.enumeration.value.severe-error.synopsis=The error log severity that is used for messages that provide information about severe errors encountered during processing.
+property.default-severity.syntax.enumeration.value.severe-warning.synopsis=The error log severity that is used for messages that provide information about severe warnings triggered during processing.
+property.enabled.synopsis=Indicates whether the Error Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Error Log Publisher implementation.
+property.override-severity.synopsis=Specifies the override severity levels for the logger based on the category of the messages.
+property.override-severity.description=Each override severity level should include the category and the severity levels to log for that category, for example, core=mild-error,info,mild-warning. Valid categories are: core, extensions, protocol, config, log, util, schema, plugin, jeb, backend, tools, task, access-control, admin, sync, version, quicksetup, admin-tool, dsconfig, user-defined. Valid severities are: all, fatal-error, info, mild-error, mild-warning, notice, severe-error, severe-warning, debug.
+property.override-severity.default-behavior.alias.synopsis=All messages with the default severity levels are logged.
+property.override-severity.syntax.string.pattern.synopsis=A string in the form category=severity1,severity2...
diff --git a/opends/src/admin/messages/ErrorLogPublisherCfgDefn_zh_CN.properties b/opends/src/admin/messages/ErrorLogPublisherCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..ae05071
--- /dev/null
+++ b/opends/src/admin/messages/ErrorLogPublisherCfgDefn_zh_CN.properties
@@ -0,0 +1,21 @@
+user-friendly-name=Error Log Publisher
+user-friendly-plural-name=Error Log Publishers
+synopsis=Error Log Publishers are responsible for distributing error log messages from the error logger to a destination.
+description=Error log messages provide information about any warnings, errors, or significant events that are encountered during server processing.
+property.default-severity.synopsis=Specifies the default severity levels for the logger.
+property.default-severity.syntax.enumeration.value.all.synopsis=Messages of all severity levels are logged.
+property.default-severity.syntax.enumeration.value.debug.synopsis=The error log severity that is used for messages that provide debugging information triggered during processing.
+property.default-severity.syntax.enumeration.value.fatal-error.synopsis=The error log severity that is used for messages that provide information about fatal errors which may force the server to shut down or operate in a significantly degraded state.
+property.default-severity.syntax.enumeration.value.info.synopsis=The error log severity that is used for messages that provide information about significant events within the server that are not warnings or errors.
+property.default-severity.syntax.enumeration.value.mild-error.synopsis=The error log severity that is used for messages that provide information about mild (recoverable) errors encountered during processing.
+property.default-severity.syntax.enumeration.value.mild-warning.synopsis=The error log severity that is used for messages that provide information about mild warnings triggered during processing.
+property.default-severity.syntax.enumeration.value.none.synopsis=No messages of any severity are logged by default. This value is intended to be used in conjunction with the override-severity property to define an error logger that will publish no error message beside the errors of a given category.
+property.default-severity.syntax.enumeration.value.notice.synopsis=The error log severity that is used for the most important informational messages (i.e., information that should almost always be logged but is not associated with a warning or error condition).
+property.default-severity.syntax.enumeration.value.severe-error.synopsis=The error log severity that is used for messages that provide information about severe errors encountered during processing.
+property.default-severity.syntax.enumeration.value.severe-warning.synopsis=The error log severity that is used for messages that provide information about severe warnings triggered during processing.
+property.enabled.synopsis=Indicates whether the Error Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Error Log Publisher implementation.
+property.override-severity.synopsis=Specifies the override severity levels for the logger based on the category of the messages.
+property.override-severity.description=Each override severity level should include the category and the severity levels to log for that category, for example, core=mild-error,info,mild-warning. Valid categories are: core, extensions, protocol, config, log, util, schema, plugin, jeb, backend, tools, task, access-control, admin, sync, version, quicksetup, admin-tool, dsconfig, user-defined. Valid severities are: all, fatal-error, info, mild-error, mild-warning, notice, severe-error, severe-warning, debug.
+property.override-severity.default-behavior.alias.synopsis=All messages with the default severity levels are logged.
+property.override-severity.syntax.string.pattern.synopsis=A string in the form category=severity1,severity2...
diff --git a/opends/src/admin/messages/ErrorLogPublisherCfgDefn_zh_TW.properties b/opends/src/admin/messages/ErrorLogPublisherCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..ae05071
--- /dev/null
+++ b/opends/src/admin/messages/ErrorLogPublisherCfgDefn_zh_TW.properties
@@ -0,0 +1,21 @@
+user-friendly-name=Error Log Publisher
+user-friendly-plural-name=Error Log Publishers
+synopsis=Error Log Publishers are responsible for distributing error log messages from the error logger to a destination.
+description=Error log messages provide information about any warnings, errors, or significant events that are encountered during server processing.
+property.default-severity.synopsis=Specifies the default severity levels for the logger.
+property.default-severity.syntax.enumeration.value.all.synopsis=Messages of all severity levels are logged.
+property.default-severity.syntax.enumeration.value.debug.synopsis=The error log severity that is used for messages that provide debugging information triggered during processing.
+property.default-severity.syntax.enumeration.value.fatal-error.synopsis=The error log severity that is used for messages that provide information about fatal errors which may force the server to shut down or operate in a significantly degraded state.
+property.default-severity.syntax.enumeration.value.info.synopsis=The error log severity that is used for messages that provide information about significant events within the server that are not warnings or errors.
+property.default-severity.syntax.enumeration.value.mild-error.synopsis=The error log severity that is used for messages that provide information about mild (recoverable) errors encountered during processing.
+property.default-severity.syntax.enumeration.value.mild-warning.synopsis=The error log severity that is used for messages that provide information about mild warnings triggered during processing.
+property.default-severity.syntax.enumeration.value.none.synopsis=No messages of any severity are logged by default. This value is intended to be used in conjunction with the override-severity property to define an error logger that will publish no error message beside the errors of a given category.
+property.default-severity.syntax.enumeration.value.notice.synopsis=The error log severity that is used for the most important informational messages (i.e., information that should almost always be logged but is not associated with a warning or error condition).
+property.default-severity.syntax.enumeration.value.severe-error.synopsis=The error log severity that is used for messages that provide information about severe errors encountered during processing.
+property.default-severity.syntax.enumeration.value.severe-warning.synopsis=The error log severity that is used for messages that provide information about severe warnings triggered during processing.
+property.enabled.synopsis=Indicates whether the Error Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Error Log Publisher implementation.
+property.override-severity.synopsis=Specifies the override severity levels for the logger based on the category of the messages.
+property.override-severity.description=Each override severity level should include the category and the severity levels to log for that category, for example, core=mild-error,info,mild-warning. Valid categories are: core, extensions, protocol, config, log, util, schema, plugin, jeb, backend, tools, task, access-control, admin, sync, version, quicksetup, admin-tool, dsconfig, user-defined. Valid severities are: all, fatal-error, info, mild-error, mild-warning, notice, severe-error, severe-warning, debug.
+property.override-severity.default-behavior.alias.synopsis=All messages with the default severity levels are logged.
+property.override-severity.syntax.string.pattern.synopsis=A string in the form category=severity1,severity2...
diff --git a/opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn.properties b/opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn.properties
new file mode 100644
index 0000000..f08a007
--- /dev/null
+++ b/opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Exact Match Identity Mapper
+user-friendly-plural-name=Exact Match Identity Mappers
+synopsis=The Exact Match Identity Mapper maps an identifier string to user entries by searching for the entry containing a specified attribute whose value is the provided identifier. For example, the username provided by the client for DIGEST-MD5 authentication must match the value of the uid attribute
+property.enabled.synopsis=Indicates whether the Exact Match Identity Mapper is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Exact Match Identity Mapper implementation.
+property.match-attribute.synopsis=Specifies the attribute whose value should exactly match the ID string provided to this identity mapper.
+property.match-attribute.description=At least one value must be provided. All values must refer to the name or OID of an attribute type defined in the Directory Server schema. If multiple attributes or OIDs are provided, at least one of those attributes must contain the provided ID string value in exactly one entry. The internal search performed includes a logical OR across all of these values.
+property.match-base-dn.synopsis=Specifies the set of base DNs below which to search for users.
+property.match-base-dn.description=The base DNs will be used when performing searches to map the provided ID string to a user entry. If multiple values are given, searches are performed below all specified base DNs.
+property.match-base-dn.default-behavior.alias.synopsis=The server searches below all public naming contexts.
diff --git a/opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_de.properties b/opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_de.properties
new file mode 100644
index 0000000..f08a007
--- /dev/null
+++ b/opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_de.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Exact Match Identity Mapper
+user-friendly-plural-name=Exact Match Identity Mappers
+synopsis=The Exact Match Identity Mapper maps an identifier string to user entries by searching for the entry containing a specified attribute whose value is the provided identifier. For example, the username provided by the client for DIGEST-MD5 authentication must match the value of the uid attribute
+property.enabled.synopsis=Indicates whether the Exact Match Identity Mapper is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Exact Match Identity Mapper implementation.
+property.match-attribute.synopsis=Specifies the attribute whose value should exactly match the ID string provided to this identity mapper.
+property.match-attribute.description=At least one value must be provided. All values must refer to the name or OID of an attribute type defined in the Directory Server schema. If multiple attributes or OIDs are provided, at least one of those attributes must contain the provided ID string value in exactly one entry. The internal search performed includes a logical OR across all of these values.
+property.match-base-dn.synopsis=Specifies the set of base DNs below which to search for users.
+property.match-base-dn.description=The base DNs will be used when performing searches to map the provided ID string to a user entry. If multiple values are given, searches are performed below all specified base DNs.
+property.match-base-dn.default-behavior.alias.synopsis=The server searches below all public naming contexts.
diff --git a/opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_es.properties b/opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_es.properties
new file mode 100644
index 0000000..f08a007
--- /dev/null
+++ b/opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_es.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Exact Match Identity Mapper
+user-friendly-plural-name=Exact Match Identity Mappers
+synopsis=The Exact Match Identity Mapper maps an identifier string to user entries by searching for the entry containing a specified attribute whose value is the provided identifier. For example, the username provided by the client for DIGEST-MD5 authentication must match the value of the uid attribute
+property.enabled.synopsis=Indicates whether the Exact Match Identity Mapper is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Exact Match Identity Mapper implementation.
+property.match-attribute.synopsis=Specifies the attribute whose value should exactly match the ID string provided to this identity mapper.
+property.match-attribute.description=At least one value must be provided. All values must refer to the name or OID of an attribute type defined in the Directory Server schema. If multiple attributes or OIDs are provided, at least one of those attributes must contain the provided ID string value in exactly one entry. The internal search performed includes a logical OR across all of these values.
+property.match-base-dn.synopsis=Specifies the set of base DNs below which to search for users.
+property.match-base-dn.description=The base DNs will be used when performing searches to map the provided ID string to a user entry. If multiple values are given, searches are performed below all specified base DNs.
+property.match-base-dn.default-behavior.alias.synopsis=The server searches below all public naming contexts.
diff --git a/opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_fr.properties b/opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_fr.properties
new file mode 100644
index 0000000..f08a007
--- /dev/null
+++ b/opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_fr.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Exact Match Identity Mapper
+user-friendly-plural-name=Exact Match Identity Mappers
+synopsis=The Exact Match Identity Mapper maps an identifier string to user entries by searching for the entry containing a specified attribute whose value is the provided identifier. For example, the username provided by the client for DIGEST-MD5 authentication must match the value of the uid attribute
+property.enabled.synopsis=Indicates whether the Exact Match Identity Mapper is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Exact Match Identity Mapper implementation.
+property.match-attribute.synopsis=Specifies the attribute whose value should exactly match the ID string provided to this identity mapper.
+property.match-attribute.description=At least one value must be provided. All values must refer to the name or OID of an attribute type defined in the Directory Server schema. If multiple attributes or OIDs are provided, at least one of those attributes must contain the provided ID string value in exactly one entry. The internal search performed includes a logical OR across all of these values.
+property.match-base-dn.synopsis=Specifies the set of base DNs below which to search for users.
+property.match-base-dn.description=The base DNs will be used when performing searches to map the provided ID string to a user entry. If multiple values are given, searches are performed below all specified base DNs.
+property.match-base-dn.default-behavior.alias.synopsis=The server searches below all public naming contexts.
diff --git a/opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_ja.properties b/opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_ja.properties
new file mode 100644
index 0000000..f08a007
--- /dev/null
+++ b/opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_ja.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Exact Match Identity Mapper
+user-friendly-plural-name=Exact Match Identity Mappers
+synopsis=The Exact Match Identity Mapper maps an identifier string to user entries by searching for the entry containing a specified attribute whose value is the provided identifier. For example, the username provided by the client for DIGEST-MD5 authentication must match the value of the uid attribute
+property.enabled.synopsis=Indicates whether the Exact Match Identity Mapper is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Exact Match Identity Mapper implementation.
+property.match-attribute.synopsis=Specifies the attribute whose value should exactly match the ID string provided to this identity mapper.
+property.match-attribute.description=At least one value must be provided. All values must refer to the name or OID of an attribute type defined in the Directory Server schema. If multiple attributes or OIDs are provided, at least one of those attributes must contain the provided ID string value in exactly one entry. The internal search performed includes a logical OR across all of these values.
+property.match-base-dn.synopsis=Specifies the set of base DNs below which to search for users.
+property.match-base-dn.description=The base DNs will be used when performing searches to map the provided ID string to a user entry. If multiple values are given, searches are performed below all specified base DNs.
+property.match-base-dn.default-behavior.alias.synopsis=The server searches below all public naming contexts.
diff --git a/opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_ko.properties b/opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_ko.properties
new file mode 100644
index 0000000..f08a007
--- /dev/null
+++ b/opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_ko.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Exact Match Identity Mapper
+user-friendly-plural-name=Exact Match Identity Mappers
+synopsis=The Exact Match Identity Mapper maps an identifier string to user entries by searching for the entry containing a specified attribute whose value is the provided identifier. For example, the username provided by the client for DIGEST-MD5 authentication must match the value of the uid attribute
+property.enabled.synopsis=Indicates whether the Exact Match Identity Mapper is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Exact Match Identity Mapper implementation.
+property.match-attribute.synopsis=Specifies the attribute whose value should exactly match the ID string provided to this identity mapper.
+property.match-attribute.description=At least one value must be provided. All values must refer to the name or OID of an attribute type defined in the Directory Server schema. If multiple attributes or OIDs are provided, at least one of those attributes must contain the provided ID string value in exactly one entry. The internal search performed includes a logical OR across all of these values.
+property.match-base-dn.synopsis=Specifies the set of base DNs below which to search for users.
+property.match-base-dn.description=The base DNs will be used when performing searches to map the provided ID string to a user entry. If multiple values are given, searches are performed below all specified base DNs.
+property.match-base-dn.default-behavior.alias.synopsis=The server searches below all public naming contexts.
diff --git a/opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_zh_CN.properties b/opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..f08a007
--- /dev/null
+++ b/opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_zh_CN.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Exact Match Identity Mapper
+user-friendly-plural-name=Exact Match Identity Mappers
+synopsis=The Exact Match Identity Mapper maps an identifier string to user entries by searching for the entry containing a specified attribute whose value is the provided identifier. For example, the username provided by the client for DIGEST-MD5 authentication must match the value of the uid attribute
+property.enabled.synopsis=Indicates whether the Exact Match Identity Mapper is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Exact Match Identity Mapper implementation.
+property.match-attribute.synopsis=Specifies the attribute whose value should exactly match the ID string provided to this identity mapper.
+property.match-attribute.description=At least one value must be provided. All values must refer to the name or OID of an attribute type defined in the Directory Server schema. If multiple attributes or OIDs are provided, at least one of those attributes must contain the provided ID string value in exactly one entry. The internal search performed includes a logical OR across all of these values.
+property.match-base-dn.synopsis=Specifies the set of base DNs below which to search for users.
+property.match-base-dn.description=The base DNs will be used when performing searches to map the provided ID string to a user entry. If multiple values are given, searches are performed below all specified base DNs.
+property.match-base-dn.default-behavior.alias.synopsis=The server searches below all public naming contexts.
diff --git a/opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_zh_TW.properties b/opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..f08a007
--- /dev/null
+++ b/opends/src/admin/messages/ExactMatchIdentityMapperCfgDefn_zh_TW.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Exact Match Identity Mapper
+user-friendly-plural-name=Exact Match Identity Mappers
+synopsis=The Exact Match Identity Mapper maps an identifier string to user entries by searching for the entry containing a specified attribute whose value is the provided identifier. For example, the username provided by the client for DIGEST-MD5 authentication must match the value of the uid attribute
+property.enabled.synopsis=Indicates whether the Exact Match Identity Mapper is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Exact Match Identity Mapper implementation.
+property.match-attribute.synopsis=Specifies the attribute whose value should exactly match the ID string provided to this identity mapper.
+property.match-attribute.description=At least one value must be provided. All values must refer to the name or OID of an attribute type defined in the Directory Server schema. If multiple attributes or OIDs are provided, at least one of those attributes must contain the provided ID string value in exactly one entry. The internal search performed includes a logical OR across all of these values.
+property.match-base-dn.synopsis=Specifies the set of base DNs below which to search for users.
+property.match-base-dn.description=The base DNs will be used when performing searches to map the provided ID string to a user entry. If multiple values are given, searches are performed below all specified base DNs.
+property.match-base-dn.default-behavior.alias.synopsis=The server searches below all public naming contexts.
diff --git a/opends/src/admin/messages/ExtendedOperationHandlerCfgDefn.properties b/opends/src/admin/messages/ExtendedOperationHandlerCfgDefn.properties
new file mode 100644
index 0000000..850ceb3
--- /dev/null
+++ b/opends/src/admin/messages/ExtendedOperationHandlerCfgDefn.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Extended Operation Handler
+user-friendly-plural-name=Extended Operation Handlers
+synopsis=Extended Operation Handlers processes the different types of extended operations in the server.
+property.enabled.synopsis=Indicates whether the Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_de.properties b/opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..850ceb3
--- /dev/null
+++ b/opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_de.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Extended Operation Handler
+user-friendly-plural-name=Extended Operation Handlers
+synopsis=Extended Operation Handlers processes the different types of extended operations in the server.
+property.enabled.synopsis=Indicates whether the Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_es.properties b/opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..850ceb3
--- /dev/null
+++ b/opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_es.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Extended Operation Handler
+user-friendly-plural-name=Extended Operation Handlers
+synopsis=Extended Operation Handlers processes the different types of extended operations in the server.
+property.enabled.synopsis=Indicates whether the Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_fr.properties b/opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..850ceb3
--- /dev/null
+++ b/opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_fr.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Extended Operation Handler
+user-friendly-plural-name=Extended Operation Handlers
+synopsis=Extended Operation Handlers processes the different types of extended operations in the server.
+property.enabled.synopsis=Indicates whether the Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_ja.properties b/opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..850ceb3
--- /dev/null
+++ b/opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_ja.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Extended Operation Handler
+user-friendly-plural-name=Extended Operation Handlers
+synopsis=Extended Operation Handlers processes the different types of extended operations in the server.
+property.enabled.synopsis=Indicates whether the Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_ko.properties b/opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..850ceb3
--- /dev/null
+++ b/opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_ko.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Extended Operation Handler
+user-friendly-plural-name=Extended Operation Handlers
+synopsis=Extended Operation Handlers processes the different types of extended operations in the server.
+property.enabled.synopsis=Indicates whether the Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..850ceb3
--- /dev/null
+++ b/opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Extended Operation Handler
+user-friendly-plural-name=Extended Operation Handlers
+synopsis=Extended Operation Handlers processes the different types of extended operations in the server.
+property.enabled.synopsis=Indicates whether the Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..850ceb3
--- /dev/null
+++ b/opends/src/admin/messages/ExtendedOperationHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Extended Operation Handler
+user-friendly-plural-name=Extended Operation Handlers
+synopsis=Extended Operation Handlers processes the different types of extended operations in the server.
+property.enabled.synopsis=Indicates whether the Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/ExtensionCfgDefn.properties b/opends/src/admin/messages/ExtensionCfgDefn.properties
new file mode 100644
index 0000000..147835f
--- /dev/null
+++ b/opends/src/admin/messages/ExtensionCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Extension
+user-friendly-plural-name=Extensions
+synopsis=The Extension allows to extend the configuration with new type of objects.
+description=It is an entry point for extensions that requires configuration objects that does not inherit from an existing top-level object.
+property.enabled.synopsis=Indicates whether the Extension is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Extension implementation.
diff --git a/opends/src/admin/messages/ExtensionCfgDefn_de.properties b/opends/src/admin/messages/ExtensionCfgDefn_de.properties
new file mode 100644
index 0000000..147835f
--- /dev/null
+++ b/opends/src/admin/messages/ExtensionCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Extension
+user-friendly-plural-name=Extensions
+synopsis=The Extension allows to extend the configuration with new type of objects.
+description=It is an entry point for extensions that requires configuration objects that does not inherit from an existing top-level object.
+property.enabled.synopsis=Indicates whether the Extension is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Extension implementation.
diff --git a/opends/src/admin/messages/ExtensionCfgDefn_es.properties b/opends/src/admin/messages/ExtensionCfgDefn_es.properties
new file mode 100644
index 0000000..147835f
--- /dev/null
+++ b/opends/src/admin/messages/ExtensionCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Extension
+user-friendly-plural-name=Extensions
+synopsis=The Extension allows to extend the configuration with new type of objects.
+description=It is an entry point for extensions that requires configuration objects that does not inherit from an existing top-level object.
+property.enabled.synopsis=Indicates whether the Extension is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Extension implementation.
diff --git a/opends/src/admin/messages/ExtensionCfgDefn_fr.properties b/opends/src/admin/messages/ExtensionCfgDefn_fr.properties
new file mode 100644
index 0000000..147835f
--- /dev/null
+++ b/opends/src/admin/messages/ExtensionCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Extension
+user-friendly-plural-name=Extensions
+synopsis=The Extension allows to extend the configuration with new type of objects.
+description=It is an entry point for extensions that requires configuration objects that does not inherit from an existing top-level object.
+property.enabled.synopsis=Indicates whether the Extension is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Extension implementation.
diff --git a/opends/src/admin/messages/ExtensionCfgDefn_ja.properties b/opends/src/admin/messages/ExtensionCfgDefn_ja.properties
new file mode 100644
index 0000000..147835f
--- /dev/null
+++ b/opends/src/admin/messages/ExtensionCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Extension
+user-friendly-plural-name=Extensions
+synopsis=The Extension allows to extend the configuration with new type of objects.
+description=It is an entry point for extensions that requires configuration objects that does not inherit from an existing top-level object.
+property.enabled.synopsis=Indicates whether the Extension is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Extension implementation.
diff --git a/opends/src/admin/messages/ExtensionCfgDefn_ko.properties b/opends/src/admin/messages/ExtensionCfgDefn_ko.properties
new file mode 100644
index 0000000..147835f
--- /dev/null
+++ b/opends/src/admin/messages/ExtensionCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Extension
+user-friendly-plural-name=Extensions
+synopsis=The Extension allows to extend the configuration with new type of objects.
+description=It is an entry point for extensions that requires configuration objects that does not inherit from an existing top-level object.
+property.enabled.synopsis=Indicates whether the Extension is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Extension implementation.
diff --git a/opends/src/admin/messages/ExtensionCfgDefn_zh_CN.properties b/opends/src/admin/messages/ExtensionCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..147835f
--- /dev/null
+++ b/opends/src/admin/messages/ExtensionCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Extension
+user-friendly-plural-name=Extensions
+synopsis=The Extension allows to extend the configuration with new type of objects.
+description=It is an entry point for extensions that requires configuration objects that does not inherit from an existing top-level object.
+property.enabled.synopsis=Indicates whether the Extension is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Extension implementation.
diff --git a/opends/src/admin/messages/ExtensionCfgDefn_zh_TW.properties b/opends/src/admin/messages/ExtensionCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..147835f
--- /dev/null
+++ b/opends/src/admin/messages/ExtensionCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Extension
+user-friendly-plural-name=Extensions
+synopsis=The Extension allows to extend the configuration with new type of objects.
+description=It is an entry point for extensions that requires configuration objects that does not inherit from an existing top-level object.
+property.enabled.synopsis=Indicates whether the Extension is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Extension implementation.
diff --git a/opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn.properties b/opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn.properties
new file mode 100644
index 0000000..2109426
--- /dev/null
+++ b/opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn.properties
@@ -0,0 +1,13 @@
+user-friendly-name=External SASL Mechanism Handler
+user-friendly-plural-name=External SASL Mechanism Handlers
+synopsis=The External SASL Mechanism Handler performs all processing related to SASL EXTERNAL authentication.
+property.certificate-attribute.synopsis=Specifies the name of the attribute to hold user certificates.
+property.certificate-attribute.description=This property must specify the name of a valid attribute type defined in the server schema.
+property.certificate-mapper.synopsis=Specifies the name of the certificate mapper that should be used to match client certificates to user entries.
+property.certificate-mapper.syntax.aggregation.constraint-synopsis=The referenced certificate mapper must be enabled when the External SASL Mechanism Handler is enabled.
+property.certificate-validation-policy.synopsis=Indicates whether to attempt to validate the peer certificate against a certificate held in the user's entry.
+property.certificate-validation-policy.syntax.enumeration.value.always.synopsis=Always require the peer certificate to be present in the user's entry.
+property.certificate-validation-policy.syntax.enumeration.value.ifpresent.synopsis=If the user's entry contains one or more certificates, require that one of them match the peer certificate.
+property.certificate-validation-policy.syntax.enumeration.value.never.synopsis=Do not look for the peer certificate to be present in the user's entry.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_de.properties b/opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..2109426
--- /dev/null
+++ b/opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_de.properties
@@ -0,0 +1,13 @@
+user-friendly-name=External SASL Mechanism Handler
+user-friendly-plural-name=External SASL Mechanism Handlers
+synopsis=The External SASL Mechanism Handler performs all processing related to SASL EXTERNAL authentication.
+property.certificate-attribute.synopsis=Specifies the name of the attribute to hold user certificates.
+property.certificate-attribute.description=This property must specify the name of a valid attribute type defined in the server schema.
+property.certificate-mapper.synopsis=Specifies the name of the certificate mapper that should be used to match client certificates to user entries.
+property.certificate-mapper.syntax.aggregation.constraint-synopsis=The referenced certificate mapper must be enabled when the External SASL Mechanism Handler is enabled.
+property.certificate-validation-policy.synopsis=Indicates whether to attempt to validate the peer certificate against a certificate held in the user's entry.
+property.certificate-validation-policy.syntax.enumeration.value.always.synopsis=Always require the peer certificate to be present in the user's entry.
+property.certificate-validation-policy.syntax.enumeration.value.ifpresent.synopsis=If the user's entry contains one or more certificates, require that one of them match the peer certificate.
+property.certificate-validation-policy.syntax.enumeration.value.never.synopsis=Do not look for the peer certificate to be present in the user's entry.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_es.properties b/opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..2109426
--- /dev/null
+++ b/opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_es.properties
@@ -0,0 +1,13 @@
+user-friendly-name=External SASL Mechanism Handler
+user-friendly-plural-name=External SASL Mechanism Handlers
+synopsis=The External SASL Mechanism Handler performs all processing related to SASL EXTERNAL authentication.
+property.certificate-attribute.synopsis=Specifies the name of the attribute to hold user certificates.
+property.certificate-attribute.description=This property must specify the name of a valid attribute type defined in the server schema.
+property.certificate-mapper.synopsis=Specifies the name of the certificate mapper that should be used to match client certificates to user entries.
+property.certificate-mapper.syntax.aggregation.constraint-synopsis=The referenced certificate mapper must be enabled when the External SASL Mechanism Handler is enabled.
+property.certificate-validation-policy.synopsis=Indicates whether to attempt to validate the peer certificate against a certificate held in the user's entry.
+property.certificate-validation-policy.syntax.enumeration.value.always.synopsis=Always require the peer certificate to be present in the user's entry.
+property.certificate-validation-policy.syntax.enumeration.value.ifpresent.synopsis=If the user's entry contains one or more certificates, require that one of them match the peer certificate.
+property.certificate-validation-policy.syntax.enumeration.value.never.synopsis=Do not look for the peer certificate to be present in the user's entry.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_fr.properties b/opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..2109426
--- /dev/null
+++ b/opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_fr.properties
@@ -0,0 +1,13 @@
+user-friendly-name=External SASL Mechanism Handler
+user-friendly-plural-name=External SASL Mechanism Handlers
+synopsis=The External SASL Mechanism Handler performs all processing related to SASL EXTERNAL authentication.
+property.certificate-attribute.synopsis=Specifies the name of the attribute to hold user certificates.
+property.certificate-attribute.description=This property must specify the name of a valid attribute type defined in the server schema.
+property.certificate-mapper.synopsis=Specifies the name of the certificate mapper that should be used to match client certificates to user entries.
+property.certificate-mapper.syntax.aggregation.constraint-synopsis=The referenced certificate mapper must be enabled when the External SASL Mechanism Handler is enabled.
+property.certificate-validation-policy.synopsis=Indicates whether to attempt to validate the peer certificate against a certificate held in the user's entry.
+property.certificate-validation-policy.syntax.enumeration.value.always.synopsis=Always require the peer certificate to be present in the user's entry.
+property.certificate-validation-policy.syntax.enumeration.value.ifpresent.synopsis=If the user's entry contains one or more certificates, require that one of them match the peer certificate.
+property.certificate-validation-policy.syntax.enumeration.value.never.synopsis=Do not look for the peer certificate to be present in the user's entry.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_ja.properties b/opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..2109426
--- /dev/null
+++ b/opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_ja.properties
@@ -0,0 +1,13 @@
+user-friendly-name=External SASL Mechanism Handler
+user-friendly-plural-name=External SASL Mechanism Handlers
+synopsis=The External SASL Mechanism Handler performs all processing related to SASL EXTERNAL authentication.
+property.certificate-attribute.synopsis=Specifies the name of the attribute to hold user certificates.
+property.certificate-attribute.description=This property must specify the name of a valid attribute type defined in the server schema.
+property.certificate-mapper.synopsis=Specifies the name of the certificate mapper that should be used to match client certificates to user entries.
+property.certificate-mapper.syntax.aggregation.constraint-synopsis=The referenced certificate mapper must be enabled when the External SASL Mechanism Handler is enabled.
+property.certificate-validation-policy.synopsis=Indicates whether to attempt to validate the peer certificate against a certificate held in the user's entry.
+property.certificate-validation-policy.syntax.enumeration.value.always.synopsis=Always require the peer certificate to be present in the user's entry.
+property.certificate-validation-policy.syntax.enumeration.value.ifpresent.synopsis=If the user's entry contains one or more certificates, require that one of them match the peer certificate.
+property.certificate-validation-policy.syntax.enumeration.value.never.synopsis=Do not look for the peer certificate to be present in the user's entry.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_ko.properties b/opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..2109426
--- /dev/null
+++ b/opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_ko.properties
@@ -0,0 +1,13 @@
+user-friendly-name=External SASL Mechanism Handler
+user-friendly-plural-name=External SASL Mechanism Handlers
+synopsis=The External SASL Mechanism Handler performs all processing related to SASL EXTERNAL authentication.
+property.certificate-attribute.synopsis=Specifies the name of the attribute to hold user certificates.
+property.certificate-attribute.description=This property must specify the name of a valid attribute type defined in the server schema.
+property.certificate-mapper.synopsis=Specifies the name of the certificate mapper that should be used to match client certificates to user entries.
+property.certificate-mapper.syntax.aggregation.constraint-synopsis=The referenced certificate mapper must be enabled when the External SASL Mechanism Handler is enabled.
+property.certificate-validation-policy.synopsis=Indicates whether to attempt to validate the peer certificate against a certificate held in the user's entry.
+property.certificate-validation-policy.syntax.enumeration.value.always.synopsis=Always require the peer certificate to be present in the user's entry.
+property.certificate-validation-policy.syntax.enumeration.value.ifpresent.synopsis=If the user's entry contains one or more certificates, require that one of them match the peer certificate.
+property.certificate-validation-policy.syntax.enumeration.value.never.synopsis=Do not look for the peer certificate to be present in the user's entry.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..2109426
--- /dev/null
+++ b/opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,13 @@
+user-friendly-name=External SASL Mechanism Handler
+user-friendly-plural-name=External SASL Mechanism Handlers
+synopsis=The External SASL Mechanism Handler performs all processing related to SASL EXTERNAL authentication.
+property.certificate-attribute.synopsis=Specifies the name of the attribute to hold user certificates.
+property.certificate-attribute.description=This property must specify the name of a valid attribute type defined in the server schema.
+property.certificate-mapper.synopsis=Specifies the name of the certificate mapper that should be used to match client certificates to user entries.
+property.certificate-mapper.syntax.aggregation.constraint-synopsis=The referenced certificate mapper must be enabled when the External SASL Mechanism Handler is enabled.
+property.certificate-validation-policy.synopsis=Indicates whether to attempt to validate the peer certificate against a certificate held in the user's entry.
+property.certificate-validation-policy.syntax.enumeration.value.always.synopsis=Always require the peer certificate to be present in the user's entry.
+property.certificate-validation-policy.syntax.enumeration.value.ifpresent.synopsis=If the user's entry contains one or more certificates, require that one of them match the peer certificate.
+property.certificate-validation-policy.syntax.enumeration.value.never.synopsis=Do not look for the peer certificate to be present in the user's entry.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..2109426
--- /dev/null
+++ b/opends/src/admin/messages/ExternalSASLMechanismHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,13 @@
+user-friendly-name=External SASL Mechanism Handler
+user-friendly-plural-name=External SASL Mechanism Handlers
+synopsis=The External SASL Mechanism Handler performs all processing related to SASL EXTERNAL authentication.
+property.certificate-attribute.synopsis=Specifies the name of the attribute to hold user certificates.
+property.certificate-attribute.description=This property must specify the name of a valid attribute type defined in the server schema.
+property.certificate-mapper.synopsis=Specifies the name of the certificate mapper that should be used to match client certificates to user entries.
+property.certificate-mapper.syntax.aggregation.constraint-synopsis=The referenced certificate mapper must be enabled when the External SASL Mechanism Handler is enabled.
+property.certificate-validation-policy.synopsis=Indicates whether to attempt to validate the peer certificate against a certificate held in the user's entry.
+property.certificate-validation-policy.syntax.enumeration.value.always.synopsis=Always require the peer certificate to be present in the user's entry.
+property.certificate-validation-policy.syntax.enumeration.value.ifpresent.synopsis=If the user's entry contains one or more certificates, require that one of them match the peer certificate.
+property.certificate-validation-policy.syntax.enumeration.value.never.synopsis=Do not look for the peer certificate to be present in the user's entry.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/FIFOEntryCacheCfgDefn.properties b/opends/src/admin/messages/FIFOEntryCacheCfgDefn.properties
new file mode 100644
index 0000000..bdf0464
--- /dev/null
+++ b/opends/src/admin/messages/FIFOEntryCacheCfgDefn.properties
@@ -0,0 +1,12 @@
+user-friendly-name=FIFO Entry Cache
+user-friendly-plural-name=FIFO Entry Caches
+synopsis=FIFO Entry Caches use a FIFO queue to keep track of the cached entries.
+description=Entries that have been in the cache the longest are the most likely candidates for purging if space is needed. In contrast to other cache structures, the selection of entries to purge is not based on how frequently or recently the entries have been accessed. This requires significantly less locking (it will only be required when an entry is added or removed from the cache, rather than each time an entry is accessed). Cache sizing is based on the percentage of free memory within the JVM, such that if enough memory is free, then adding an entry to the cache will not require purging, but if more than a specified percentage of the available memory within the JVM is already consumed, then one or more entries will need to be removed in order to make room for a new entry. It is also possible to configure a maximum number of entries for the cache. If this is specified, then the number of entries will not be allowed to exceed this value, but it may not be possible to hold this many entries if the available memory fills up first. Other configurable parameters for this cache include the maximum length of time to block while waiting to acquire a lock, and a set of filters that may be used to define criteria for determining which entries are stored in the cache. If a filter list is provided, then only entries matching at least one of the given filters will be stored in the cache.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.enabled.synopsis=Indicates whether the FIFO Entry Cache is enabled.
+property.exclude-filter.synopsis=The set of filters that define the entries that should be excluded from the cache.
+property.include-filter.synopsis=The set of filters that define the entries that should be included in the cache.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the FIFO Entry Cache implementation.
+property.lock-timeout.synopsis=Specifies the length of time to wait while attempting to acquire a read or write lock.
+property.max-entries.synopsis=Specifies the maximum number of entries that we will allow in the cache.
+property.max-memory-percent.synopsis=Specifies the maximum memory usage for the entry cache as a percentage of the total JVM memory.
diff --git a/opends/src/admin/messages/FIFOEntryCacheCfgDefn_de.properties b/opends/src/admin/messages/FIFOEntryCacheCfgDefn_de.properties
new file mode 100644
index 0000000..bdf0464
--- /dev/null
+++ b/opends/src/admin/messages/FIFOEntryCacheCfgDefn_de.properties
@@ -0,0 +1,12 @@
+user-friendly-name=FIFO Entry Cache
+user-friendly-plural-name=FIFO Entry Caches
+synopsis=FIFO Entry Caches use a FIFO queue to keep track of the cached entries.
+description=Entries that have been in the cache the longest are the most likely candidates for purging if space is needed. In contrast to other cache structures, the selection of entries to purge is not based on how frequently or recently the entries have been accessed. This requires significantly less locking (it will only be required when an entry is added or removed from the cache, rather than each time an entry is accessed). Cache sizing is based on the percentage of free memory within the JVM, such that if enough memory is free, then adding an entry to the cache will not require purging, but if more than a specified percentage of the available memory within the JVM is already consumed, then one or more entries will need to be removed in order to make room for a new entry. It is also possible to configure a maximum number of entries for the cache. If this is specified, then the number of entries will not be allowed to exceed this value, but it may not be possible to hold this many entries if the available memory fills up first. Other configurable parameters for this cache include the maximum length of time to block while waiting to acquire a lock, and a set of filters that may be used to define criteria for determining which entries are stored in the cache. If a filter list is provided, then only entries matching at least one of the given filters will be stored in the cache.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.enabled.synopsis=Indicates whether the FIFO Entry Cache is enabled.
+property.exclude-filter.synopsis=The set of filters that define the entries that should be excluded from the cache.
+property.include-filter.synopsis=The set of filters that define the entries that should be included in the cache.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the FIFO Entry Cache implementation.
+property.lock-timeout.synopsis=Specifies the length of time to wait while attempting to acquire a read or write lock.
+property.max-entries.synopsis=Specifies the maximum number of entries that we will allow in the cache.
+property.max-memory-percent.synopsis=Specifies the maximum memory usage for the entry cache as a percentage of the total JVM memory.
diff --git a/opends/src/admin/messages/FIFOEntryCacheCfgDefn_es.properties b/opends/src/admin/messages/FIFOEntryCacheCfgDefn_es.properties
new file mode 100644
index 0000000..bdf0464
--- /dev/null
+++ b/opends/src/admin/messages/FIFOEntryCacheCfgDefn_es.properties
@@ -0,0 +1,12 @@
+user-friendly-name=FIFO Entry Cache
+user-friendly-plural-name=FIFO Entry Caches
+synopsis=FIFO Entry Caches use a FIFO queue to keep track of the cached entries.
+description=Entries that have been in the cache the longest are the most likely candidates for purging if space is needed. In contrast to other cache structures, the selection of entries to purge is not based on how frequently or recently the entries have been accessed. This requires significantly less locking (it will only be required when an entry is added or removed from the cache, rather than each time an entry is accessed). Cache sizing is based on the percentage of free memory within the JVM, such that if enough memory is free, then adding an entry to the cache will not require purging, but if more than a specified percentage of the available memory within the JVM is already consumed, then one or more entries will need to be removed in order to make room for a new entry. It is also possible to configure a maximum number of entries for the cache. If this is specified, then the number of entries will not be allowed to exceed this value, but it may not be possible to hold this many entries if the available memory fills up first. Other configurable parameters for this cache include the maximum length of time to block while waiting to acquire a lock, and a set of filters that may be used to define criteria for determining which entries are stored in the cache. If a filter list is provided, then only entries matching at least one of the given filters will be stored in the cache.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.enabled.synopsis=Indicates whether the FIFO Entry Cache is enabled.
+property.exclude-filter.synopsis=The set of filters that define the entries that should be excluded from the cache.
+property.include-filter.synopsis=The set of filters that define the entries that should be included in the cache.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the FIFO Entry Cache implementation.
+property.lock-timeout.synopsis=Specifies the length of time to wait while attempting to acquire a read or write lock.
+property.max-entries.synopsis=Specifies the maximum number of entries that we will allow in the cache.
+property.max-memory-percent.synopsis=Specifies the maximum memory usage for the entry cache as a percentage of the total JVM memory.
diff --git a/opends/src/admin/messages/FIFOEntryCacheCfgDefn_fr.properties b/opends/src/admin/messages/FIFOEntryCacheCfgDefn_fr.properties
new file mode 100644
index 0000000..bdf0464
--- /dev/null
+++ b/opends/src/admin/messages/FIFOEntryCacheCfgDefn_fr.properties
@@ -0,0 +1,12 @@
+user-friendly-name=FIFO Entry Cache
+user-friendly-plural-name=FIFO Entry Caches
+synopsis=FIFO Entry Caches use a FIFO queue to keep track of the cached entries.
+description=Entries that have been in the cache the longest are the most likely candidates for purging if space is needed. In contrast to other cache structures, the selection of entries to purge is not based on how frequently or recently the entries have been accessed. This requires significantly less locking (it will only be required when an entry is added or removed from the cache, rather than each time an entry is accessed). Cache sizing is based on the percentage of free memory within the JVM, such that if enough memory is free, then adding an entry to the cache will not require purging, but if more than a specified percentage of the available memory within the JVM is already consumed, then one or more entries will need to be removed in order to make room for a new entry. It is also possible to configure a maximum number of entries for the cache. If this is specified, then the number of entries will not be allowed to exceed this value, but it may not be possible to hold this many entries if the available memory fills up first. Other configurable parameters for this cache include the maximum length of time to block while waiting to acquire a lock, and a set of filters that may be used to define criteria for determining which entries are stored in the cache. If a filter list is provided, then only entries matching at least one of the given filters will be stored in the cache.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.enabled.synopsis=Indicates whether the FIFO Entry Cache is enabled.
+property.exclude-filter.synopsis=The set of filters that define the entries that should be excluded from the cache.
+property.include-filter.synopsis=The set of filters that define the entries that should be included in the cache.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the FIFO Entry Cache implementation.
+property.lock-timeout.synopsis=Specifies the length of time to wait while attempting to acquire a read or write lock.
+property.max-entries.synopsis=Specifies the maximum number of entries that we will allow in the cache.
+property.max-memory-percent.synopsis=Specifies the maximum memory usage for the entry cache as a percentage of the total JVM memory.
diff --git a/opends/src/admin/messages/FIFOEntryCacheCfgDefn_ja.properties b/opends/src/admin/messages/FIFOEntryCacheCfgDefn_ja.properties
new file mode 100644
index 0000000..bdf0464
--- /dev/null
+++ b/opends/src/admin/messages/FIFOEntryCacheCfgDefn_ja.properties
@@ -0,0 +1,12 @@
+user-friendly-name=FIFO Entry Cache
+user-friendly-plural-name=FIFO Entry Caches
+synopsis=FIFO Entry Caches use a FIFO queue to keep track of the cached entries.
+description=Entries that have been in the cache the longest are the most likely candidates for purging if space is needed. In contrast to other cache structures, the selection of entries to purge is not based on how frequently or recently the entries have been accessed. This requires significantly less locking (it will only be required when an entry is added or removed from the cache, rather than each time an entry is accessed). Cache sizing is based on the percentage of free memory within the JVM, such that if enough memory is free, then adding an entry to the cache will not require purging, but if more than a specified percentage of the available memory within the JVM is already consumed, then one or more entries will need to be removed in order to make room for a new entry. It is also possible to configure a maximum number of entries for the cache. If this is specified, then the number of entries will not be allowed to exceed this value, but it may not be possible to hold this many entries if the available memory fills up first. Other configurable parameters for this cache include the maximum length of time to block while waiting to acquire a lock, and a set of filters that may be used to define criteria for determining which entries are stored in the cache. If a filter list is provided, then only entries matching at least one of the given filters will be stored in the cache.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.enabled.synopsis=Indicates whether the FIFO Entry Cache is enabled.
+property.exclude-filter.synopsis=The set of filters that define the entries that should be excluded from the cache.
+property.include-filter.synopsis=The set of filters that define the entries that should be included in the cache.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the FIFO Entry Cache implementation.
+property.lock-timeout.synopsis=Specifies the length of time to wait while attempting to acquire a read or write lock.
+property.max-entries.synopsis=Specifies the maximum number of entries that we will allow in the cache.
+property.max-memory-percent.synopsis=Specifies the maximum memory usage for the entry cache as a percentage of the total JVM memory.
diff --git a/opends/src/admin/messages/FIFOEntryCacheCfgDefn_ko.properties b/opends/src/admin/messages/FIFOEntryCacheCfgDefn_ko.properties
new file mode 100644
index 0000000..bdf0464
--- /dev/null
+++ b/opends/src/admin/messages/FIFOEntryCacheCfgDefn_ko.properties
@@ -0,0 +1,12 @@
+user-friendly-name=FIFO Entry Cache
+user-friendly-plural-name=FIFO Entry Caches
+synopsis=FIFO Entry Caches use a FIFO queue to keep track of the cached entries.
+description=Entries that have been in the cache the longest are the most likely candidates for purging if space is needed. In contrast to other cache structures, the selection of entries to purge is not based on how frequently or recently the entries have been accessed. This requires significantly less locking (it will only be required when an entry is added or removed from the cache, rather than each time an entry is accessed). Cache sizing is based on the percentage of free memory within the JVM, such that if enough memory is free, then adding an entry to the cache will not require purging, but if more than a specified percentage of the available memory within the JVM is already consumed, then one or more entries will need to be removed in order to make room for a new entry. It is also possible to configure a maximum number of entries for the cache. If this is specified, then the number of entries will not be allowed to exceed this value, but it may not be possible to hold this many entries if the available memory fills up first. Other configurable parameters for this cache include the maximum length of time to block while waiting to acquire a lock, and a set of filters that may be used to define criteria for determining which entries are stored in the cache. If a filter list is provided, then only entries matching at least one of the given filters will be stored in the cache.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.enabled.synopsis=Indicates whether the FIFO Entry Cache is enabled.
+property.exclude-filter.synopsis=The set of filters that define the entries that should be excluded from the cache.
+property.include-filter.synopsis=The set of filters that define the entries that should be included in the cache.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the FIFO Entry Cache implementation.
+property.lock-timeout.synopsis=Specifies the length of time to wait while attempting to acquire a read or write lock.
+property.max-entries.synopsis=Specifies the maximum number of entries that we will allow in the cache.
+property.max-memory-percent.synopsis=Specifies the maximum memory usage for the entry cache as a percentage of the total JVM memory.
diff --git a/opends/src/admin/messages/FIFOEntryCacheCfgDefn_zh_CN.properties b/opends/src/admin/messages/FIFOEntryCacheCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..bdf0464
--- /dev/null
+++ b/opends/src/admin/messages/FIFOEntryCacheCfgDefn_zh_CN.properties
@@ -0,0 +1,12 @@
+user-friendly-name=FIFO Entry Cache
+user-friendly-plural-name=FIFO Entry Caches
+synopsis=FIFO Entry Caches use a FIFO queue to keep track of the cached entries.
+description=Entries that have been in the cache the longest are the most likely candidates for purging if space is needed. In contrast to other cache structures, the selection of entries to purge is not based on how frequently or recently the entries have been accessed. This requires significantly less locking (it will only be required when an entry is added or removed from the cache, rather than each time an entry is accessed). Cache sizing is based on the percentage of free memory within the JVM, such that if enough memory is free, then adding an entry to the cache will not require purging, but if more than a specified percentage of the available memory within the JVM is already consumed, then one or more entries will need to be removed in order to make room for a new entry. It is also possible to configure a maximum number of entries for the cache. If this is specified, then the number of entries will not be allowed to exceed this value, but it may not be possible to hold this many entries if the available memory fills up first. Other configurable parameters for this cache include the maximum length of time to block while waiting to acquire a lock, and a set of filters that may be used to define criteria for determining which entries are stored in the cache. If a filter list is provided, then only entries matching at least one of the given filters will be stored in the cache.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.enabled.synopsis=Indicates whether the FIFO Entry Cache is enabled.
+property.exclude-filter.synopsis=The set of filters that define the entries that should be excluded from the cache.
+property.include-filter.synopsis=The set of filters that define the entries that should be included in the cache.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the FIFO Entry Cache implementation.
+property.lock-timeout.synopsis=Specifies the length of time to wait while attempting to acquire a read or write lock.
+property.max-entries.synopsis=Specifies the maximum number of entries that we will allow in the cache.
+property.max-memory-percent.synopsis=Specifies the maximum memory usage for the entry cache as a percentage of the total JVM memory.
diff --git a/opends/src/admin/messages/FIFOEntryCacheCfgDefn_zh_TW.properties b/opends/src/admin/messages/FIFOEntryCacheCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..bdf0464
--- /dev/null
+++ b/opends/src/admin/messages/FIFOEntryCacheCfgDefn_zh_TW.properties
@@ -0,0 +1,12 @@
+user-friendly-name=FIFO Entry Cache
+user-friendly-plural-name=FIFO Entry Caches
+synopsis=FIFO Entry Caches use a FIFO queue to keep track of the cached entries.
+description=Entries that have been in the cache the longest are the most likely candidates for purging if space is needed. In contrast to other cache structures, the selection of entries to purge is not based on how frequently or recently the entries have been accessed. This requires significantly less locking (it will only be required when an entry is added or removed from the cache, rather than each time an entry is accessed). Cache sizing is based on the percentage of free memory within the JVM, such that if enough memory is free, then adding an entry to the cache will not require purging, but if more than a specified percentage of the available memory within the JVM is already consumed, then one or more entries will need to be removed in order to make room for a new entry. It is also possible to configure a maximum number of entries for the cache. If this is specified, then the number of entries will not be allowed to exceed this value, but it may not be possible to hold this many entries if the available memory fills up first. Other configurable parameters for this cache include the maximum length of time to block while waiting to acquire a lock, and a set of filters that may be used to define criteria for determining which entries are stored in the cache. If a filter list is provided, then only entries matching at least one of the given filters will be stored in the cache.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.enabled.synopsis=Indicates whether the FIFO Entry Cache is enabled.
+property.exclude-filter.synopsis=The set of filters that define the entries that should be excluded from the cache.
+property.include-filter.synopsis=The set of filters that define the entries that should be included in the cache.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the FIFO Entry Cache implementation.
+property.lock-timeout.synopsis=Specifies the length of time to wait while attempting to acquire a read or write lock.
+property.max-entries.synopsis=Specifies the maximum number of entries that we will allow in the cache.
+property.max-memory-percent.synopsis=Specifies the maximum memory usage for the entry cache as a percentage of the total JVM memory.
diff --git a/opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn.properties b/opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn.properties
new file mode 100644
index 0000000..ce70eb7
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn.properties
@@ -0,0 +1,25 @@
+user-friendly-name=File Based Access Log Publisher
+user-friendly-plural-name=File Based Access Log Publishers
+synopsis=File Based Access Log Publishers publish access messages to the file system.
+property.append.synopsis=Specifies whether to append to existing log files.
+property.asynchronous.synopsis=Indicates whether the File Based Access Log Publisher will publish records asynchronously.
+property.auto-flush.synopsis=Specifies whether to flush the writer after every log record.
+property.auto-flush.description=If the asynchronous writes option is used, the writer is flushed after all the log records in the queue are written.
+property.buffer-size.synopsis=Specifies the log file buffer size.
+property.enabled.synopsis=Indicates whether the File Based Access Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Access Log Publisher implementation.
+property.log-file.synopsis=The file name to use for the log files generated by the File Based Access Log Publisher. The path to the file is relative to the server root.
+property.log-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.log-file-permissions.synopsis=The UNIX permissions of the log files created by this File Based Access Log Publisher.
+property.log-file-permissions.syntax.string.pattern.synopsis=A valid UNIX mode string. The mode string must contain three digits between zero and seven.
+property.queue-size.synopsis=The maximum number of log records that can be stored in the asynchronous queue.
+property.queue-size.requires-admin-action.synopsis=The File Based Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.
+property.retention-policy.synopsis=The retention policy to use for the File Based Access Log Publisher .
+property.retention-policy.description=When multiple policies are used, log files are cleaned when any of the policy's conditions are met.
+property.retention-policy.default-behavior.alias.synopsis=No retention policy is used and log files are never cleaned.
+property.rotation-policy.synopsis=The rotation policy to use for the File Based Access Log Publisher .
+property.rotation-policy.description=When multiple policies are used, rotation will occur if any policy's conditions are met.
+property.rotation-policy.default-behavior.alias.synopsis=No rotation policy is used and log rotation will not occur.
+property.suppress-internal-operations.synopsis=Indicates whether internal operations (for example, operations that are initiated by plugins) should be logged along with the operations that are requested by users.
+property.suppress-synchronization-operations.synopsis=Indicates whether access messages that are generated by synchronization operations should be suppressed.
+property.time-interval.synopsis=Specifies the interval at which to check whether the log files need to be rotated.
diff --git a/opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_de.properties b/opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_de.properties
new file mode 100644
index 0000000..ce70eb7
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_de.properties
@@ -0,0 +1,25 @@
+user-friendly-name=File Based Access Log Publisher
+user-friendly-plural-name=File Based Access Log Publishers
+synopsis=File Based Access Log Publishers publish access messages to the file system.
+property.append.synopsis=Specifies whether to append to existing log files.
+property.asynchronous.synopsis=Indicates whether the File Based Access Log Publisher will publish records asynchronously.
+property.auto-flush.synopsis=Specifies whether to flush the writer after every log record.
+property.auto-flush.description=If the asynchronous writes option is used, the writer is flushed after all the log records in the queue are written.
+property.buffer-size.synopsis=Specifies the log file buffer size.
+property.enabled.synopsis=Indicates whether the File Based Access Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Access Log Publisher implementation.
+property.log-file.synopsis=The file name to use for the log files generated by the File Based Access Log Publisher. The path to the file is relative to the server root.
+property.log-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.log-file-permissions.synopsis=The UNIX permissions of the log files created by this File Based Access Log Publisher.
+property.log-file-permissions.syntax.string.pattern.synopsis=A valid UNIX mode string. The mode string must contain three digits between zero and seven.
+property.queue-size.synopsis=The maximum number of log records that can be stored in the asynchronous queue.
+property.queue-size.requires-admin-action.synopsis=The File Based Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.
+property.retention-policy.synopsis=The retention policy to use for the File Based Access Log Publisher .
+property.retention-policy.description=When multiple policies are used, log files are cleaned when any of the policy's conditions are met.
+property.retention-policy.default-behavior.alias.synopsis=No retention policy is used and log files are never cleaned.
+property.rotation-policy.synopsis=The rotation policy to use for the File Based Access Log Publisher .
+property.rotation-policy.description=When multiple policies are used, rotation will occur if any policy's conditions are met.
+property.rotation-policy.default-behavior.alias.synopsis=No rotation policy is used and log rotation will not occur.
+property.suppress-internal-operations.synopsis=Indicates whether internal operations (for example, operations that are initiated by plugins) should be logged along with the operations that are requested by users.
+property.suppress-synchronization-operations.synopsis=Indicates whether access messages that are generated by synchronization operations should be suppressed.
+property.time-interval.synopsis=Specifies the interval at which to check whether the log files need to be rotated.
diff --git a/opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_es.properties b/opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_es.properties
new file mode 100644
index 0000000..ce70eb7
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_es.properties
@@ -0,0 +1,25 @@
+user-friendly-name=File Based Access Log Publisher
+user-friendly-plural-name=File Based Access Log Publishers
+synopsis=File Based Access Log Publishers publish access messages to the file system.
+property.append.synopsis=Specifies whether to append to existing log files.
+property.asynchronous.synopsis=Indicates whether the File Based Access Log Publisher will publish records asynchronously.
+property.auto-flush.synopsis=Specifies whether to flush the writer after every log record.
+property.auto-flush.description=If the asynchronous writes option is used, the writer is flushed after all the log records in the queue are written.
+property.buffer-size.synopsis=Specifies the log file buffer size.
+property.enabled.synopsis=Indicates whether the File Based Access Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Access Log Publisher implementation.
+property.log-file.synopsis=The file name to use for the log files generated by the File Based Access Log Publisher. The path to the file is relative to the server root.
+property.log-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.log-file-permissions.synopsis=The UNIX permissions of the log files created by this File Based Access Log Publisher.
+property.log-file-permissions.syntax.string.pattern.synopsis=A valid UNIX mode string. The mode string must contain three digits between zero and seven.
+property.queue-size.synopsis=The maximum number of log records that can be stored in the asynchronous queue.
+property.queue-size.requires-admin-action.synopsis=The File Based Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.
+property.retention-policy.synopsis=The retention policy to use for the File Based Access Log Publisher .
+property.retention-policy.description=When multiple policies are used, log files are cleaned when any of the policy's conditions are met.
+property.retention-policy.default-behavior.alias.synopsis=No retention policy is used and log files are never cleaned.
+property.rotation-policy.synopsis=The rotation policy to use for the File Based Access Log Publisher .
+property.rotation-policy.description=When multiple policies are used, rotation will occur if any policy's conditions are met.
+property.rotation-policy.default-behavior.alias.synopsis=No rotation policy is used and log rotation will not occur.
+property.suppress-internal-operations.synopsis=Indicates whether internal operations (for example, operations that are initiated by plugins) should be logged along with the operations that are requested by users.
+property.suppress-synchronization-operations.synopsis=Indicates whether access messages that are generated by synchronization operations should be suppressed.
+property.time-interval.synopsis=Specifies the interval at which to check whether the log files need to be rotated.
diff --git a/opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_fr.properties b/opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_fr.properties
new file mode 100644
index 0000000..ce70eb7
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_fr.properties
@@ -0,0 +1,25 @@
+user-friendly-name=File Based Access Log Publisher
+user-friendly-plural-name=File Based Access Log Publishers
+synopsis=File Based Access Log Publishers publish access messages to the file system.
+property.append.synopsis=Specifies whether to append to existing log files.
+property.asynchronous.synopsis=Indicates whether the File Based Access Log Publisher will publish records asynchronously.
+property.auto-flush.synopsis=Specifies whether to flush the writer after every log record.
+property.auto-flush.description=If the asynchronous writes option is used, the writer is flushed after all the log records in the queue are written.
+property.buffer-size.synopsis=Specifies the log file buffer size.
+property.enabled.synopsis=Indicates whether the File Based Access Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Access Log Publisher implementation.
+property.log-file.synopsis=The file name to use for the log files generated by the File Based Access Log Publisher. The path to the file is relative to the server root.
+property.log-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.log-file-permissions.synopsis=The UNIX permissions of the log files created by this File Based Access Log Publisher.
+property.log-file-permissions.syntax.string.pattern.synopsis=A valid UNIX mode string. The mode string must contain three digits between zero and seven.
+property.queue-size.synopsis=The maximum number of log records that can be stored in the asynchronous queue.
+property.queue-size.requires-admin-action.synopsis=The File Based Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.
+property.retention-policy.synopsis=The retention policy to use for the File Based Access Log Publisher .
+property.retention-policy.description=When multiple policies are used, log files are cleaned when any of the policy's conditions are met.
+property.retention-policy.default-behavior.alias.synopsis=No retention policy is used and log files are never cleaned.
+property.rotation-policy.synopsis=The rotation policy to use for the File Based Access Log Publisher .
+property.rotation-policy.description=When multiple policies are used, rotation will occur if any policy's conditions are met.
+property.rotation-policy.default-behavior.alias.synopsis=No rotation policy is used and log rotation will not occur.
+property.suppress-internal-operations.synopsis=Indicates whether internal operations (for example, operations that are initiated by plugins) should be logged along with the operations that are requested by users.
+property.suppress-synchronization-operations.synopsis=Indicates whether access messages that are generated by synchronization operations should be suppressed.
+property.time-interval.synopsis=Specifies the interval at which to check whether the log files need to be rotated.
diff --git a/opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_ja.properties b/opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_ja.properties
new file mode 100644
index 0000000..ce70eb7
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_ja.properties
@@ -0,0 +1,25 @@
+user-friendly-name=File Based Access Log Publisher
+user-friendly-plural-name=File Based Access Log Publishers
+synopsis=File Based Access Log Publishers publish access messages to the file system.
+property.append.synopsis=Specifies whether to append to existing log files.
+property.asynchronous.synopsis=Indicates whether the File Based Access Log Publisher will publish records asynchronously.
+property.auto-flush.synopsis=Specifies whether to flush the writer after every log record.
+property.auto-flush.description=If the asynchronous writes option is used, the writer is flushed after all the log records in the queue are written.
+property.buffer-size.synopsis=Specifies the log file buffer size.
+property.enabled.synopsis=Indicates whether the File Based Access Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Access Log Publisher implementation.
+property.log-file.synopsis=The file name to use for the log files generated by the File Based Access Log Publisher. The path to the file is relative to the server root.
+property.log-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.log-file-permissions.synopsis=The UNIX permissions of the log files created by this File Based Access Log Publisher.
+property.log-file-permissions.syntax.string.pattern.synopsis=A valid UNIX mode string. The mode string must contain three digits between zero and seven.
+property.queue-size.synopsis=The maximum number of log records that can be stored in the asynchronous queue.
+property.queue-size.requires-admin-action.synopsis=The File Based Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.
+property.retention-policy.synopsis=The retention policy to use for the File Based Access Log Publisher .
+property.retention-policy.description=When multiple policies are used, log files are cleaned when any of the policy's conditions are met.
+property.retention-policy.default-behavior.alias.synopsis=No retention policy is used and log files are never cleaned.
+property.rotation-policy.synopsis=The rotation policy to use for the File Based Access Log Publisher .
+property.rotation-policy.description=When multiple policies are used, rotation will occur if any policy's conditions are met.
+property.rotation-policy.default-behavior.alias.synopsis=No rotation policy is used and log rotation will not occur.
+property.suppress-internal-operations.synopsis=Indicates whether internal operations (for example, operations that are initiated by plugins) should be logged along with the operations that are requested by users.
+property.suppress-synchronization-operations.synopsis=Indicates whether access messages that are generated by synchronization operations should be suppressed.
+property.time-interval.synopsis=Specifies the interval at which to check whether the log files need to be rotated.
diff --git a/opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_ko.properties b/opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_ko.properties
new file mode 100644
index 0000000..ce70eb7
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_ko.properties
@@ -0,0 +1,25 @@
+user-friendly-name=File Based Access Log Publisher
+user-friendly-plural-name=File Based Access Log Publishers
+synopsis=File Based Access Log Publishers publish access messages to the file system.
+property.append.synopsis=Specifies whether to append to existing log files.
+property.asynchronous.synopsis=Indicates whether the File Based Access Log Publisher will publish records asynchronously.
+property.auto-flush.synopsis=Specifies whether to flush the writer after every log record.
+property.auto-flush.description=If the asynchronous writes option is used, the writer is flushed after all the log records in the queue are written.
+property.buffer-size.synopsis=Specifies the log file buffer size.
+property.enabled.synopsis=Indicates whether the File Based Access Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Access Log Publisher implementation.
+property.log-file.synopsis=The file name to use for the log files generated by the File Based Access Log Publisher. The path to the file is relative to the server root.
+property.log-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.log-file-permissions.synopsis=The UNIX permissions of the log files created by this File Based Access Log Publisher.
+property.log-file-permissions.syntax.string.pattern.synopsis=A valid UNIX mode string. The mode string must contain three digits between zero and seven.
+property.queue-size.synopsis=The maximum number of log records that can be stored in the asynchronous queue.
+property.queue-size.requires-admin-action.synopsis=The File Based Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.
+property.retention-policy.synopsis=The retention policy to use for the File Based Access Log Publisher .
+property.retention-policy.description=When multiple policies are used, log files are cleaned when any of the policy's conditions are met.
+property.retention-policy.default-behavior.alias.synopsis=No retention policy is used and log files are never cleaned.
+property.rotation-policy.synopsis=The rotation policy to use for the File Based Access Log Publisher .
+property.rotation-policy.description=When multiple policies are used, rotation will occur if any policy's conditions are met.
+property.rotation-policy.default-behavior.alias.synopsis=No rotation policy is used and log rotation will not occur.
+property.suppress-internal-operations.synopsis=Indicates whether internal operations (for example, operations that are initiated by plugins) should be logged along with the operations that are requested by users.
+property.suppress-synchronization-operations.synopsis=Indicates whether access messages that are generated by synchronization operations should be suppressed.
+property.time-interval.synopsis=Specifies the interval at which to check whether the log files need to be rotated.
diff --git a/opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_zh_CN.properties b/opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..ce70eb7
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_zh_CN.properties
@@ -0,0 +1,25 @@
+user-friendly-name=File Based Access Log Publisher
+user-friendly-plural-name=File Based Access Log Publishers
+synopsis=File Based Access Log Publishers publish access messages to the file system.
+property.append.synopsis=Specifies whether to append to existing log files.
+property.asynchronous.synopsis=Indicates whether the File Based Access Log Publisher will publish records asynchronously.
+property.auto-flush.synopsis=Specifies whether to flush the writer after every log record.
+property.auto-flush.description=If the asynchronous writes option is used, the writer is flushed after all the log records in the queue are written.
+property.buffer-size.synopsis=Specifies the log file buffer size.
+property.enabled.synopsis=Indicates whether the File Based Access Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Access Log Publisher implementation.
+property.log-file.synopsis=The file name to use for the log files generated by the File Based Access Log Publisher. The path to the file is relative to the server root.
+property.log-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.log-file-permissions.synopsis=The UNIX permissions of the log files created by this File Based Access Log Publisher.
+property.log-file-permissions.syntax.string.pattern.synopsis=A valid UNIX mode string. The mode string must contain three digits between zero and seven.
+property.queue-size.synopsis=The maximum number of log records that can be stored in the asynchronous queue.
+property.queue-size.requires-admin-action.synopsis=The File Based Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.
+property.retention-policy.synopsis=The retention policy to use for the File Based Access Log Publisher .
+property.retention-policy.description=When multiple policies are used, log files are cleaned when any of the policy's conditions are met.
+property.retention-policy.default-behavior.alias.synopsis=No retention policy is used and log files are never cleaned.
+property.rotation-policy.synopsis=The rotation policy to use for the File Based Access Log Publisher .
+property.rotation-policy.description=When multiple policies are used, rotation will occur if any policy's conditions are met.
+property.rotation-policy.default-behavior.alias.synopsis=No rotation policy is used and log rotation will not occur.
+property.suppress-internal-operations.synopsis=Indicates whether internal operations (for example, operations that are initiated by plugins) should be logged along with the operations that are requested by users.
+property.suppress-synchronization-operations.synopsis=Indicates whether access messages that are generated by synchronization operations should be suppressed.
+property.time-interval.synopsis=Specifies the interval at which to check whether the log files need to be rotated.
diff --git a/opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_zh_TW.properties b/opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..ce70eb7
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedAccessLogPublisherCfgDefn_zh_TW.properties
@@ -0,0 +1,25 @@
+user-friendly-name=File Based Access Log Publisher
+user-friendly-plural-name=File Based Access Log Publishers
+synopsis=File Based Access Log Publishers publish access messages to the file system.
+property.append.synopsis=Specifies whether to append to existing log files.
+property.asynchronous.synopsis=Indicates whether the File Based Access Log Publisher will publish records asynchronously.
+property.auto-flush.synopsis=Specifies whether to flush the writer after every log record.
+property.auto-flush.description=If the asynchronous writes option is used, the writer is flushed after all the log records in the queue are written.
+property.buffer-size.synopsis=Specifies the log file buffer size.
+property.enabled.synopsis=Indicates whether the File Based Access Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Access Log Publisher implementation.
+property.log-file.synopsis=The file name to use for the log files generated by the File Based Access Log Publisher. The path to the file is relative to the server root.
+property.log-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.log-file-permissions.synopsis=The UNIX permissions of the log files created by this File Based Access Log Publisher.
+property.log-file-permissions.syntax.string.pattern.synopsis=A valid UNIX mode string. The mode string must contain three digits between zero and seven.
+property.queue-size.synopsis=The maximum number of log records that can be stored in the asynchronous queue.
+property.queue-size.requires-admin-action.synopsis=The File Based Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.
+property.retention-policy.synopsis=The retention policy to use for the File Based Access Log Publisher .
+property.retention-policy.description=When multiple policies are used, log files are cleaned when any of the policy's conditions are met.
+property.retention-policy.default-behavior.alias.synopsis=No retention policy is used and log files are never cleaned.
+property.rotation-policy.synopsis=The rotation policy to use for the File Based Access Log Publisher .
+property.rotation-policy.description=When multiple policies are used, rotation will occur if any policy's conditions are met.
+property.rotation-policy.default-behavior.alias.synopsis=No rotation policy is used and log rotation will not occur.
+property.suppress-internal-operations.synopsis=Indicates whether internal operations (for example, operations that are initiated by plugins) should be logged along with the operations that are requested by users.
+property.suppress-synchronization-operations.synopsis=Indicates whether access messages that are generated by synchronization operations should be suppressed.
+property.time-interval.synopsis=Specifies the interval at which to check whether the log files need to be rotated.
diff --git a/opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn.properties b/opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn.properties
new file mode 100644
index 0000000..5136661
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn.properties
@@ -0,0 +1,48 @@
+user-friendly-name=File Based Debug Log Publisher
+user-friendly-plural-name=File Based Debug Log Publishers
+synopsis=File Based Debug Log Publishers publish debug messages to the file system.
+property.append.synopsis=Specifies whether to append to existing log files.
+property.asynchronous.synopsis=Indicates whether the File Based Debug Log Publisher will publish records asynchronously.
+property.auto-flush.synopsis=Specifies whether to flush the writer after every log record.
+property.auto-flush.description=If the asynchronous writes option is used, the writer is flushed after all the log records in the queue are written.
+property.buffer-size.synopsis=Specifies the log file buffer size.
+property.default-debug-category.synopsis=The debug message categories to be logged when none of the defined targets match the message.
+property.default-debug-category.default-behavior.alias.synopsis=Messages with any category will be logged if they have a sufficient debug level.
+property.default-debug-category.syntax.enumeration.value.caught.synopsis=Exception caught.
+property.default-debug-category.syntax.enumeration.value.constructor.synopsis=Constructor entry.
+property.default-debug-category.syntax.enumeration.value.data.synopsis=Raw data dump.
+property.default-debug-category.syntax.enumeration.value.database-access.synopsis=Access to a backend database.
+property.default-debug-category.syntax.enumeration.value.enter.synopsis=Method entry.
+property.default-debug-category.syntax.enumeration.value.exit.synopsis=Method exit.
+property.default-debug-category.syntax.enumeration.value.message.synopsis=Arbitrary debug message.
+property.default-debug-category.syntax.enumeration.value.protocol.synopsis=Protocol element dump.
+property.default-debug-category.syntax.enumeration.value.thrown.synopsis=Exception throw from method.
+property.default-debug-level.synopsis=The lowest severity level of debug messages to log when none of the defined targets match the message.
+property.default-debug-level.syntax.enumeration.value.all.synopsis=Messages with any severity level will be logged.
+property.default-debug-level.syntax.enumeration.value.disabled.synopsis=No messages will be logged.
+property.default-debug-level.syntax.enumeration.value.error.synopsis=Messages with severity level of ERROR or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.info.synopsis=Messages with severity level of INFO or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.verbose.synopsis=Messages with severity level of VERBOSE or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.warning.synopsis=Messages with severity level of WARNING or higher will be logged.
+property.default-include-throwable-cause.synopsis=Indicates whether to include the cause of exceptions in exception thrown and caught messages logged by default.
+property.default-omit-method-entry-arguments.synopsis=Indicates whether to include method arguments in debug messages logged by default.
+property.default-omit-method-return-value.synopsis=Indicates whether to include the return value in debug messages logged by default.
+property.default-throwable-stack-frames.synopsis=Indicates the number of stack frames to include in the stack trace for method entry and exception thrown messages.
+property.enabled.synopsis=Indicates whether the File Based Debug Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Debug Log Publisher implementation.
+property.log-file.synopsis=The file name to use for the log files generated by the File Based Debug Log Publisher .
+property.log-file.description=The path to the file is relative to the server root.
+property.log-file-permissions.synopsis=The UNIX permissions of the log files created by this File Based Debug Log Publisher .
+property.log-file-permissions.syntax.string.pattern.synopsis=A valid UNIX mode string. The mode string must contain three digits between zero and seven.
+property.queue-size.synopsis=The maximum number of log records that can be stored in the asynchronous queue.
+property.retention-policy.synopsis=The retention policy to use for the File Based Debug Log Publisher .
+property.retention-policy.description=When multiple policies are used, log files are cleaned when any of the policy's conditions are met.
+property.retention-policy.default-behavior.alias.synopsis=No retention policy is used and log files are never cleaned.
+property.rotation-policy.synopsis=The rotation policy to use for the File Based Debug Log Publisher .
+property.rotation-policy.description=When multiple policies are used, rotation will occur if any policy's conditions are met.
+property.rotation-policy.default-behavior.alias.synopsis=No rotation policy is used and log rotation will not occur.
+property.time-interval.synopsis=Specifies the interval at which to check whether the log files need to be rotated.
+relation.debug-target.user-friendly-name=Debug Target
+relation.debug-target.user-friendly-plural-name=Debug Targets
+relation.debug-target.synopsis=Debug Targets define the types of messages logged by the debug logPublisher.
+relation.debug-target.description=Debug targets allow for fine-grain control of which messages are logged based on the package, class, or method that generated the message. Each debug target configuration entry resides below the entry with RDN of "cn=Debug Target" immediately below the parent ds-cfg-debug-log-publisher entry.
diff --git a/opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_de.properties b/opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_de.properties
new file mode 100644
index 0000000..5136661
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_de.properties
@@ -0,0 +1,48 @@
+user-friendly-name=File Based Debug Log Publisher
+user-friendly-plural-name=File Based Debug Log Publishers
+synopsis=File Based Debug Log Publishers publish debug messages to the file system.
+property.append.synopsis=Specifies whether to append to existing log files.
+property.asynchronous.synopsis=Indicates whether the File Based Debug Log Publisher will publish records asynchronously.
+property.auto-flush.synopsis=Specifies whether to flush the writer after every log record.
+property.auto-flush.description=If the asynchronous writes option is used, the writer is flushed after all the log records in the queue are written.
+property.buffer-size.synopsis=Specifies the log file buffer size.
+property.default-debug-category.synopsis=The debug message categories to be logged when none of the defined targets match the message.
+property.default-debug-category.default-behavior.alias.synopsis=Messages with any category will be logged if they have a sufficient debug level.
+property.default-debug-category.syntax.enumeration.value.caught.synopsis=Exception caught.
+property.default-debug-category.syntax.enumeration.value.constructor.synopsis=Constructor entry.
+property.default-debug-category.syntax.enumeration.value.data.synopsis=Raw data dump.
+property.default-debug-category.syntax.enumeration.value.database-access.synopsis=Access to a backend database.
+property.default-debug-category.syntax.enumeration.value.enter.synopsis=Method entry.
+property.default-debug-category.syntax.enumeration.value.exit.synopsis=Method exit.
+property.default-debug-category.syntax.enumeration.value.message.synopsis=Arbitrary debug message.
+property.default-debug-category.syntax.enumeration.value.protocol.synopsis=Protocol element dump.
+property.default-debug-category.syntax.enumeration.value.thrown.synopsis=Exception throw from method.
+property.default-debug-level.synopsis=The lowest severity level of debug messages to log when none of the defined targets match the message.
+property.default-debug-level.syntax.enumeration.value.all.synopsis=Messages with any severity level will be logged.
+property.default-debug-level.syntax.enumeration.value.disabled.synopsis=No messages will be logged.
+property.default-debug-level.syntax.enumeration.value.error.synopsis=Messages with severity level of ERROR or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.info.synopsis=Messages with severity level of INFO or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.verbose.synopsis=Messages with severity level of VERBOSE or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.warning.synopsis=Messages with severity level of WARNING or higher will be logged.
+property.default-include-throwable-cause.synopsis=Indicates whether to include the cause of exceptions in exception thrown and caught messages logged by default.
+property.default-omit-method-entry-arguments.synopsis=Indicates whether to include method arguments in debug messages logged by default.
+property.default-omit-method-return-value.synopsis=Indicates whether to include the return value in debug messages logged by default.
+property.default-throwable-stack-frames.synopsis=Indicates the number of stack frames to include in the stack trace for method entry and exception thrown messages.
+property.enabled.synopsis=Indicates whether the File Based Debug Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Debug Log Publisher implementation.
+property.log-file.synopsis=The file name to use for the log files generated by the File Based Debug Log Publisher .
+property.log-file.description=The path to the file is relative to the server root.
+property.log-file-permissions.synopsis=The UNIX permissions of the log files created by this File Based Debug Log Publisher .
+property.log-file-permissions.syntax.string.pattern.synopsis=A valid UNIX mode string. The mode string must contain three digits between zero and seven.
+property.queue-size.synopsis=The maximum number of log records that can be stored in the asynchronous queue.
+property.retention-policy.synopsis=The retention policy to use for the File Based Debug Log Publisher .
+property.retention-policy.description=When multiple policies are used, log files are cleaned when any of the policy's conditions are met.
+property.retention-policy.default-behavior.alias.synopsis=No retention policy is used and log files are never cleaned.
+property.rotation-policy.synopsis=The rotation policy to use for the File Based Debug Log Publisher .
+property.rotation-policy.description=When multiple policies are used, rotation will occur if any policy's conditions are met.
+property.rotation-policy.default-behavior.alias.synopsis=No rotation policy is used and log rotation will not occur.
+property.time-interval.synopsis=Specifies the interval at which to check whether the log files need to be rotated.
+relation.debug-target.user-friendly-name=Debug Target
+relation.debug-target.user-friendly-plural-name=Debug Targets
+relation.debug-target.synopsis=Debug Targets define the types of messages logged by the debug logPublisher.
+relation.debug-target.description=Debug targets allow for fine-grain control of which messages are logged based on the package, class, or method that generated the message. Each debug target configuration entry resides below the entry with RDN of "cn=Debug Target" immediately below the parent ds-cfg-debug-log-publisher entry.
diff --git a/opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_es.properties b/opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_es.properties
new file mode 100644
index 0000000..5136661
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_es.properties
@@ -0,0 +1,48 @@
+user-friendly-name=File Based Debug Log Publisher
+user-friendly-plural-name=File Based Debug Log Publishers
+synopsis=File Based Debug Log Publishers publish debug messages to the file system.
+property.append.synopsis=Specifies whether to append to existing log files.
+property.asynchronous.synopsis=Indicates whether the File Based Debug Log Publisher will publish records asynchronously.
+property.auto-flush.synopsis=Specifies whether to flush the writer after every log record.
+property.auto-flush.description=If the asynchronous writes option is used, the writer is flushed after all the log records in the queue are written.
+property.buffer-size.synopsis=Specifies the log file buffer size.
+property.default-debug-category.synopsis=The debug message categories to be logged when none of the defined targets match the message.
+property.default-debug-category.default-behavior.alias.synopsis=Messages with any category will be logged if they have a sufficient debug level.
+property.default-debug-category.syntax.enumeration.value.caught.synopsis=Exception caught.
+property.default-debug-category.syntax.enumeration.value.constructor.synopsis=Constructor entry.
+property.default-debug-category.syntax.enumeration.value.data.synopsis=Raw data dump.
+property.default-debug-category.syntax.enumeration.value.database-access.synopsis=Access to a backend database.
+property.default-debug-category.syntax.enumeration.value.enter.synopsis=Method entry.
+property.default-debug-category.syntax.enumeration.value.exit.synopsis=Method exit.
+property.default-debug-category.syntax.enumeration.value.message.synopsis=Arbitrary debug message.
+property.default-debug-category.syntax.enumeration.value.protocol.synopsis=Protocol element dump.
+property.default-debug-category.syntax.enumeration.value.thrown.synopsis=Exception throw from method.
+property.default-debug-level.synopsis=The lowest severity level of debug messages to log when none of the defined targets match the message.
+property.default-debug-level.syntax.enumeration.value.all.synopsis=Messages with any severity level will be logged.
+property.default-debug-level.syntax.enumeration.value.disabled.synopsis=No messages will be logged.
+property.default-debug-level.syntax.enumeration.value.error.synopsis=Messages with severity level of ERROR or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.info.synopsis=Messages with severity level of INFO or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.verbose.synopsis=Messages with severity level of VERBOSE or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.warning.synopsis=Messages with severity level of WARNING or higher will be logged.
+property.default-include-throwable-cause.synopsis=Indicates whether to include the cause of exceptions in exception thrown and caught messages logged by default.
+property.default-omit-method-entry-arguments.synopsis=Indicates whether to include method arguments in debug messages logged by default.
+property.default-omit-method-return-value.synopsis=Indicates whether to include the return value in debug messages logged by default.
+property.default-throwable-stack-frames.synopsis=Indicates the number of stack frames to include in the stack trace for method entry and exception thrown messages.
+property.enabled.synopsis=Indicates whether the File Based Debug Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Debug Log Publisher implementation.
+property.log-file.synopsis=The file name to use for the log files generated by the File Based Debug Log Publisher .
+property.log-file.description=The path to the file is relative to the server root.
+property.log-file-permissions.synopsis=The UNIX permissions of the log files created by this File Based Debug Log Publisher .
+property.log-file-permissions.syntax.string.pattern.synopsis=A valid UNIX mode string. The mode string must contain three digits between zero and seven.
+property.queue-size.synopsis=The maximum number of log records that can be stored in the asynchronous queue.
+property.retention-policy.synopsis=The retention policy to use for the File Based Debug Log Publisher .
+property.retention-policy.description=When multiple policies are used, log files are cleaned when any of the policy's conditions are met.
+property.retention-policy.default-behavior.alias.synopsis=No retention policy is used and log files are never cleaned.
+property.rotation-policy.synopsis=The rotation policy to use for the File Based Debug Log Publisher .
+property.rotation-policy.description=When multiple policies are used, rotation will occur if any policy's conditions are met.
+property.rotation-policy.default-behavior.alias.synopsis=No rotation policy is used and log rotation will not occur.
+property.time-interval.synopsis=Specifies the interval at which to check whether the log files need to be rotated.
+relation.debug-target.user-friendly-name=Debug Target
+relation.debug-target.user-friendly-plural-name=Debug Targets
+relation.debug-target.synopsis=Debug Targets define the types of messages logged by the debug logPublisher.
+relation.debug-target.description=Debug targets allow for fine-grain control of which messages are logged based on the package, class, or method that generated the message. Each debug target configuration entry resides below the entry with RDN of "cn=Debug Target" immediately below the parent ds-cfg-debug-log-publisher entry.
diff --git a/opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_fr.properties b/opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_fr.properties
new file mode 100644
index 0000000..5136661
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_fr.properties
@@ -0,0 +1,48 @@
+user-friendly-name=File Based Debug Log Publisher
+user-friendly-plural-name=File Based Debug Log Publishers
+synopsis=File Based Debug Log Publishers publish debug messages to the file system.
+property.append.synopsis=Specifies whether to append to existing log files.
+property.asynchronous.synopsis=Indicates whether the File Based Debug Log Publisher will publish records asynchronously.
+property.auto-flush.synopsis=Specifies whether to flush the writer after every log record.
+property.auto-flush.description=If the asynchronous writes option is used, the writer is flushed after all the log records in the queue are written.
+property.buffer-size.synopsis=Specifies the log file buffer size.
+property.default-debug-category.synopsis=The debug message categories to be logged when none of the defined targets match the message.
+property.default-debug-category.default-behavior.alias.synopsis=Messages with any category will be logged if they have a sufficient debug level.
+property.default-debug-category.syntax.enumeration.value.caught.synopsis=Exception caught.
+property.default-debug-category.syntax.enumeration.value.constructor.synopsis=Constructor entry.
+property.default-debug-category.syntax.enumeration.value.data.synopsis=Raw data dump.
+property.default-debug-category.syntax.enumeration.value.database-access.synopsis=Access to a backend database.
+property.default-debug-category.syntax.enumeration.value.enter.synopsis=Method entry.
+property.default-debug-category.syntax.enumeration.value.exit.synopsis=Method exit.
+property.default-debug-category.syntax.enumeration.value.message.synopsis=Arbitrary debug message.
+property.default-debug-category.syntax.enumeration.value.protocol.synopsis=Protocol element dump.
+property.default-debug-category.syntax.enumeration.value.thrown.synopsis=Exception throw from method.
+property.default-debug-level.synopsis=The lowest severity level of debug messages to log when none of the defined targets match the message.
+property.default-debug-level.syntax.enumeration.value.all.synopsis=Messages with any severity level will be logged.
+property.default-debug-level.syntax.enumeration.value.disabled.synopsis=No messages will be logged.
+property.default-debug-level.syntax.enumeration.value.error.synopsis=Messages with severity level of ERROR or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.info.synopsis=Messages with severity level of INFO or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.verbose.synopsis=Messages with severity level of VERBOSE or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.warning.synopsis=Messages with severity level of WARNING or higher will be logged.
+property.default-include-throwable-cause.synopsis=Indicates whether to include the cause of exceptions in exception thrown and caught messages logged by default.
+property.default-omit-method-entry-arguments.synopsis=Indicates whether to include method arguments in debug messages logged by default.
+property.default-omit-method-return-value.synopsis=Indicates whether to include the return value in debug messages logged by default.
+property.default-throwable-stack-frames.synopsis=Indicates the number of stack frames to include in the stack trace for method entry and exception thrown messages.
+property.enabled.synopsis=Indicates whether the File Based Debug Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Debug Log Publisher implementation.
+property.log-file.synopsis=The file name to use for the log files generated by the File Based Debug Log Publisher .
+property.log-file.description=The path to the file is relative to the server root.
+property.log-file-permissions.synopsis=The UNIX permissions of the log files created by this File Based Debug Log Publisher .
+property.log-file-permissions.syntax.string.pattern.synopsis=A valid UNIX mode string. The mode string must contain three digits between zero and seven.
+property.queue-size.synopsis=The maximum number of log records that can be stored in the asynchronous queue.
+property.retention-policy.synopsis=The retention policy to use for the File Based Debug Log Publisher .
+property.retention-policy.description=When multiple policies are used, log files are cleaned when any of the policy's conditions are met.
+property.retention-policy.default-behavior.alias.synopsis=No retention policy is used and log files are never cleaned.
+property.rotation-policy.synopsis=The rotation policy to use for the File Based Debug Log Publisher .
+property.rotation-policy.description=When multiple policies are used, rotation will occur if any policy's conditions are met.
+property.rotation-policy.default-behavior.alias.synopsis=No rotation policy is used and log rotation will not occur.
+property.time-interval.synopsis=Specifies the interval at which to check whether the log files need to be rotated.
+relation.debug-target.user-friendly-name=Debug Target
+relation.debug-target.user-friendly-plural-name=Debug Targets
+relation.debug-target.synopsis=Debug Targets define the types of messages logged by the debug logPublisher.
+relation.debug-target.description=Debug targets allow for fine-grain control of which messages are logged based on the package, class, or method that generated the message. Each debug target configuration entry resides below the entry with RDN of "cn=Debug Target" immediately below the parent ds-cfg-debug-log-publisher entry.
diff --git a/opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_ja.properties b/opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_ja.properties
new file mode 100644
index 0000000..5136661
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_ja.properties
@@ -0,0 +1,48 @@
+user-friendly-name=File Based Debug Log Publisher
+user-friendly-plural-name=File Based Debug Log Publishers
+synopsis=File Based Debug Log Publishers publish debug messages to the file system.
+property.append.synopsis=Specifies whether to append to existing log files.
+property.asynchronous.synopsis=Indicates whether the File Based Debug Log Publisher will publish records asynchronously.
+property.auto-flush.synopsis=Specifies whether to flush the writer after every log record.
+property.auto-flush.description=If the asynchronous writes option is used, the writer is flushed after all the log records in the queue are written.
+property.buffer-size.synopsis=Specifies the log file buffer size.
+property.default-debug-category.synopsis=The debug message categories to be logged when none of the defined targets match the message.
+property.default-debug-category.default-behavior.alias.synopsis=Messages with any category will be logged if they have a sufficient debug level.
+property.default-debug-category.syntax.enumeration.value.caught.synopsis=Exception caught.
+property.default-debug-category.syntax.enumeration.value.constructor.synopsis=Constructor entry.
+property.default-debug-category.syntax.enumeration.value.data.synopsis=Raw data dump.
+property.default-debug-category.syntax.enumeration.value.database-access.synopsis=Access to a backend database.
+property.default-debug-category.syntax.enumeration.value.enter.synopsis=Method entry.
+property.default-debug-category.syntax.enumeration.value.exit.synopsis=Method exit.
+property.default-debug-category.syntax.enumeration.value.message.synopsis=Arbitrary debug message.
+property.default-debug-category.syntax.enumeration.value.protocol.synopsis=Protocol element dump.
+property.default-debug-category.syntax.enumeration.value.thrown.synopsis=Exception throw from method.
+property.default-debug-level.synopsis=The lowest severity level of debug messages to log when none of the defined targets match the message.
+property.default-debug-level.syntax.enumeration.value.all.synopsis=Messages with any severity level will be logged.
+property.default-debug-level.syntax.enumeration.value.disabled.synopsis=No messages will be logged.
+property.default-debug-level.syntax.enumeration.value.error.synopsis=Messages with severity level of ERROR or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.info.synopsis=Messages with severity level of INFO or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.verbose.synopsis=Messages with severity level of VERBOSE or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.warning.synopsis=Messages with severity level of WARNING or higher will be logged.
+property.default-include-throwable-cause.synopsis=Indicates whether to include the cause of exceptions in exception thrown and caught messages logged by default.
+property.default-omit-method-entry-arguments.synopsis=Indicates whether to include method arguments in debug messages logged by default.
+property.default-omit-method-return-value.synopsis=Indicates whether to include the return value in debug messages logged by default.
+property.default-throwable-stack-frames.synopsis=Indicates the number of stack frames to include in the stack trace for method entry and exception thrown messages.
+property.enabled.synopsis=Indicates whether the File Based Debug Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Debug Log Publisher implementation.
+property.log-file.synopsis=The file name to use for the log files generated by the File Based Debug Log Publisher .
+property.log-file.description=The path to the file is relative to the server root.
+property.log-file-permissions.synopsis=The UNIX permissions of the log files created by this File Based Debug Log Publisher .
+property.log-file-permissions.syntax.string.pattern.synopsis=A valid UNIX mode string. The mode string must contain three digits between zero and seven.
+property.queue-size.synopsis=The maximum number of log records that can be stored in the asynchronous queue.
+property.retention-policy.synopsis=The retention policy to use for the File Based Debug Log Publisher .
+property.retention-policy.description=When multiple policies are used, log files are cleaned when any of the policy's conditions are met.
+property.retention-policy.default-behavior.alias.synopsis=No retention policy is used and log files are never cleaned.
+property.rotation-policy.synopsis=The rotation policy to use for the File Based Debug Log Publisher .
+property.rotation-policy.description=When multiple policies are used, rotation will occur if any policy's conditions are met.
+property.rotation-policy.default-behavior.alias.synopsis=No rotation policy is used and log rotation will not occur.
+property.time-interval.synopsis=Specifies the interval at which to check whether the log files need to be rotated.
+relation.debug-target.user-friendly-name=Debug Target
+relation.debug-target.user-friendly-plural-name=Debug Targets
+relation.debug-target.synopsis=Debug Targets define the types of messages logged by the debug logPublisher.
+relation.debug-target.description=Debug targets allow for fine-grain control of which messages are logged based on the package, class, or method that generated the message. Each debug target configuration entry resides below the entry with RDN of "cn=Debug Target" immediately below the parent ds-cfg-debug-log-publisher entry.
diff --git a/opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_ko.properties b/opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_ko.properties
new file mode 100644
index 0000000..5136661
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_ko.properties
@@ -0,0 +1,48 @@
+user-friendly-name=File Based Debug Log Publisher
+user-friendly-plural-name=File Based Debug Log Publishers
+synopsis=File Based Debug Log Publishers publish debug messages to the file system.
+property.append.synopsis=Specifies whether to append to existing log files.
+property.asynchronous.synopsis=Indicates whether the File Based Debug Log Publisher will publish records asynchronously.
+property.auto-flush.synopsis=Specifies whether to flush the writer after every log record.
+property.auto-flush.description=If the asynchronous writes option is used, the writer is flushed after all the log records in the queue are written.
+property.buffer-size.synopsis=Specifies the log file buffer size.
+property.default-debug-category.synopsis=The debug message categories to be logged when none of the defined targets match the message.
+property.default-debug-category.default-behavior.alias.synopsis=Messages with any category will be logged if they have a sufficient debug level.
+property.default-debug-category.syntax.enumeration.value.caught.synopsis=Exception caught.
+property.default-debug-category.syntax.enumeration.value.constructor.synopsis=Constructor entry.
+property.default-debug-category.syntax.enumeration.value.data.synopsis=Raw data dump.
+property.default-debug-category.syntax.enumeration.value.database-access.synopsis=Access to a backend database.
+property.default-debug-category.syntax.enumeration.value.enter.synopsis=Method entry.
+property.default-debug-category.syntax.enumeration.value.exit.synopsis=Method exit.
+property.default-debug-category.syntax.enumeration.value.message.synopsis=Arbitrary debug message.
+property.default-debug-category.syntax.enumeration.value.protocol.synopsis=Protocol element dump.
+property.default-debug-category.syntax.enumeration.value.thrown.synopsis=Exception throw from method.
+property.default-debug-level.synopsis=The lowest severity level of debug messages to log when none of the defined targets match the message.
+property.default-debug-level.syntax.enumeration.value.all.synopsis=Messages with any severity level will be logged.
+property.default-debug-level.syntax.enumeration.value.disabled.synopsis=No messages will be logged.
+property.default-debug-level.syntax.enumeration.value.error.synopsis=Messages with severity level of ERROR or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.info.synopsis=Messages with severity level of INFO or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.verbose.synopsis=Messages with severity level of VERBOSE or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.warning.synopsis=Messages with severity level of WARNING or higher will be logged.
+property.default-include-throwable-cause.synopsis=Indicates whether to include the cause of exceptions in exception thrown and caught messages logged by default.
+property.default-omit-method-entry-arguments.synopsis=Indicates whether to include method arguments in debug messages logged by default.
+property.default-omit-method-return-value.synopsis=Indicates whether to include the return value in debug messages logged by default.
+property.default-throwable-stack-frames.synopsis=Indicates the number of stack frames to include in the stack trace for method entry and exception thrown messages.
+property.enabled.synopsis=Indicates whether the File Based Debug Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Debug Log Publisher implementation.
+property.log-file.synopsis=The file name to use for the log files generated by the File Based Debug Log Publisher .
+property.log-file.description=The path to the file is relative to the server root.
+property.log-file-permissions.synopsis=The UNIX permissions of the log files created by this File Based Debug Log Publisher .
+property.log-file-permissions.syntax.string.pattern.synopsis=A valid UNIX mode string. The mode string must contain three digits between zero and seven.
+property.queue-size.synopsis=The maximum number of log records that can be stored in the asynchronous queue.
+property.retention-policy.synopsis=The retention policy to use for the File Based Debug Log Publisher .
+property.retention-policy.description=When multiple policies are used, log files are cleaned when any of the policy's conditions are met.
+property.retention-policy.default-behavior.alias.synopsis=No retention policy is used and log files are never cleaned.
+property.rotation-policy.synopsis=The rotation policy to use for the File Based Debug Log Publisher .
+property.rotation-policy.description=When multiple policies are used, rotation will occur if any policy's conditions are met.
+property.rotation-policy.default-behavior.alias.synopsis=No rotation policy is used and log rotation will not occur.
+property.time-interval.synopsis=Specifies the interval at which to check whether the log files need to be rotated.
+relation.debug-target.user-friendly-name=Debug Target
+relation.debug-target.user-friendly-plural-name=Debug Targets
+relation.debug-target.synopsis=Debug Targets define the types of messages logged by the debug logPublisher.
+relation.debug-target.description=Debug targets allow for fine-grain control of which messages are logged based on the package, class, or method that generated the message. Each debug target configuration entry resides below the entry with RDN of "cn=Debug Target" immediately below the parent ds-cfg-debug-log-publisher entry.
diff --git a/opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_zh_CN.properties b/opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..5136661
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_zh_CN.properties
@@ -0,0 +1,48 @@
+user-friendly-name=File Based Debug Log Publisher
+user-friendly-plural-name=File Based Debug Log Publishers
+synopsis=File Based Debug Log Publishers publish debug messages to the file system.
+property.append.synopsis=Specifies whether to append to existing log files.
+property.asynchronous.synopsis=Indicates whether the File Based Debug Log Publisher will publish records asynchronously.
+property.auto-flush.synopsis=Specifies whether to flush the writer after every log record.
+property.auto-flush.description=If the asynchronous writes option is used, the writer is flushed after all the log records in the queue are written.
+property.buffer-size.synopsis=Specifies the log file buffer size.
+property.default-debug-category.synopsis=The debug message categories to be logged when none of the defined targets match the message.
+property.default-debug-category.default-behavior.alias.synopsis=Messages with any category will be logged if they have a sufficient debug level.
+property.default-debug-category.syntax.enumeration.value.caught.synopsis=Exception caught.
+property.default-debug-category.syntax.enumeration.value.constructor.synopsis=Constructor entry.
+property.default-debug-category.syntax.enumeration.value.data.synopsis=Raw data dump.
+property.default-debug-category.syntax.enumeration.value.database-access.synopsis=Access to a backend database.
+property.default-debug-category.syntax.enumeration.value.enter.synopsis=Method entry.
+property.default-debug-category.syntax.enumeration.value.exit.synopsis=Method exit.
+property.default-debug-category.syntax.enumeration.value.message.synopsis=Arbitrary debug message.
+property.default-debug-category.syntax.enumeration.value.protocol.synopsis=Protocol element dump.
+property.default-debug-category.syntax.enumeration.value.thrown.synopsis=Exception throw from method.
+property.default-debug-level.synopsis=The lowest severity level of debug messages to log when none of the defined targets match the message.
+property.default-debug-level.syntax.enumeration.value.all.synopsis=Messages with any severity level will be logged.
+property.default-debug-level.syntax.enumeration.value.disabled.synopsis=No messages will be logged.
+property.default-debug-level.syntax.enumeration.value.error.synopsis=Messages with severity level of ERROR or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.info.synopsis=Messages with severity level of INFO or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.verbose.synopsis=Messages with severity level of VERBOSE or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.warning.synopsis=Messages with severity level of WARNING or higher will be logged.
+property.default-include-throwable-cause.synopsis=Indicates whether to include the cause of exceptions in exception thrown and caught messages logged by default.
+property.default-omit-method-entry-arguments.synopsis=Indicates whether to include method arguments in debug messages logged by default.
+property.default-omit-method-return-value.synopsis=Indicates whether to include the return value in debug messages logged by default.
+property.default-throwable-stack-frames.synopsis=Indicates the number of stack frames to include in the stack trace for method entry and exception thrown messages.
+property.enabled.synopsis=Indicates whether the File Based Debug Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Debug Log Publisher implementation.
+property.log-file.synopsis=The file name to use for the log files generated by the File Based Debug Log Publisher .
+property.log-file.description=The path to the file is relative to the server root.
+property.log-file-permissions.synopsis=The UNIX permissions of the log files created by this File Based Debug Log Publisher .
+property.log-file-permissions.syntax.string.pattern.synopsis=A valid UNIX mode string. The mode string must contain three digits between zero and seven.
+property.queue-size.synopsis=The maximum number of log records that can be stored in the asynchronous queue.
+property.retention-policy.synopsis=The retention policy to use for the File Based Debug Log Publisher .
+property.retention-policy.description=When multiple policies are used, log files are cleaned when any of the policy's conditions are met.
+property.retention-policy.default-behavior.alias.synopsis=No retention policy is used and log files are never cleaned.
+property.rotation-policy.synopsis=The rotation policy to use for the File Based Debug Log Publisher .
+property.rotation-policy.description=When multiple policies are used, rotation will occur if any policy's conditions are met.
+property.rotation-policy.default-behavior.alias.synopsis=No rotation policy is used and log rotation will not occur.
+property.time-interval.synopsis=Specifies the interval at which to check whether the log files need to be rotated.
+relation.debug-target.user-friendly-name=Debug Target
+relation.debug-target.user-friendly-plural-name=Debug Targets
+relation.debug-target.synopsis=Debug Targets define the types of messages logged by the debug logPublisher.
+relation.debug-target.description=Debug targets allow for fine-grain control of which messages are logged based on the package, class, or method that generated the message. Each debug target configuration entry resides below the entry with RDN of "cn=Debug Target" immediately below the parent ds-cfg-debug-log-publisher entry.
diff --git a/opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_zh_TW.properties b/opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..5136661
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedDebugLogPublisherCfgDefn_zh_TW.properties
@@ -0,0 +1,48 @@
+user-friendly-name=File Based Debug Log Publisher
+user-friendly-plural-name=File Based Debug Log Publishers
+synopsis=File Based Debug Log Publishers publish debug messages to the file system.
+property.append.synopsis=Specifies whether to append to existing log files.
+property.asynchronous.synopsis=Indicates whether the File Based Debug Log Publisher will publish records asynchronously.
+property.auto-flush.synopsis=Specifies whether to flush the writer after every log record.
+property.auto-flush.description=If the asynchronous writes option is used, the writer is flushed after all the log records in the queue are written.
+property.buffer-size.synopsis=Specifies the log file buffer size.
+property.default-debug-category.synopsis=The debug message categories to be logged when none of the defined targets match the message.
+property.default-debug-category.default-behavior.alias.synopsis=Messages with any category will be logged if they have a sufficient debug level.
+property.default-debug-category.syntax.enumeration.value.caught.synopsis=Exception caught.
+property.default-debug-category.syntax.enumeration.value.constructor.synopsis=Constructor entry.
+property.default-debug-category.syntax.enumeration.value.data.synopsis=Raw data dump.
+property.default-debug-category.syntax.enumeration.value.database-access.synopsis=Access to a backend database.
+property.default-debug-category.syntax.enumeration.value.enter.synopsis=Method entry.
+property.default-debug-category.syntax.enumeration.value.exit.synopsis=Method exit.
+property.default-debug-category.syntax.enumeration.value.message.synopsis=Arbitrary debug message.
+property.default-debug-category.syntax.enumeration.value.protocol.synopsis=Protocol element dump.
+property.default-debug-category.syntax.enumeration.value.thrown.synopsis=Exception throw from method.
+property.default-debug-level.synopsis=The lowest severity level of debug messages to log when none of the defined targets match the message.
+property.default-debug-level.syntax.enumeration.value.all.synopsis=Messages with any severity level will be logged.
+property.default-debug-level.syntax.enumeration.value.disabled.synopsis=No messages will be logged.
+property.default-debug-level.syntax.enumeration.value.error.synopsis=Messages with severity level of ERROR or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.info.synopsis=Messages with severity level of INFO or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.verbose.synopsis=Messages with severity level of VERBOSE or higher will be logged.
+property.default-debug-level.syntax.enumeration.value.warning.synopsis=Messages with severity level of WARNING or higher will be logged.
+property.default-include-throwable-cause.synopsis=Indicates whether to include the cause of exceptions in exception thrown and caught messages logged by default.
+property.default-omit-method-entry-arguments.synopsis=Indicates whether to include method arguments in debug messages logged by default.
+property.default-omit-method-return-value.synopsis=Indicates whether to include the return value in debug messages logged by default.
+property.default-throwable-stack-frames.synopsis=Indicates the number of stack frames to include in the stack trace for method entry and exception thrown messages.
+property.enabled.synopsis=Indicates whether the File Based Debug Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Debug Log Publisher implementation.
+property.log-file.synopsis=The file name to use for the log files generated by the File Based Debug Log Publisher .
+property.log-file.description=The path to the file is relative to the server root.
+property.log-file-permissions.synopsis=The UNIX permissions of the log files created by this File Based Debug Log Publisher .
+property.log-file-permissions.syntax.string.pattern.synopsis=A valid UNIX mode string. The mode string must contain three digits between zero and seven.
+property.queue-size.synopsis=The maximum number of log records that can be stored in the asynchronous queue.
+property.retention-policy.synopsis=The retention policy to use for the File Based Debug Log Publisher .
+property.retention-policy.description=When multiple policies are used, log files are cleaned when any of the policy's conditions are met.
+property.retention-policy.default-behavior.alias.synopsis=No retention policy is used and log files are never cleaned.
+property.rotation-policy.synopsis=The rotation policy to use for the File Based Debug Log Publisher .
+property.rotation-policy.description=When multiple policies are used, rotation will occur if any policy's conditions are met.
+property.rotation-policy.default-behavior.alias.synopsis=No rotation policy is used and log rotation will not occur.
+property.time-interval.synopsis=Specifies the interval at which to check whether the log files need to be rotated.
+relation.debug-target.user-friendly-name=Debug Target
+relation.debug-target.user-friendly-plural-name=Debug Targets
+relation.debug-target.synopsis=Debug Targets define the types of messages logged by the debug logPublisher.
+relation.debug-target.description=Debug targets allow for fine-grain control of which messages are logged based on the package, class, or method that generated the message. Each debug target configuration entry resides below the entry with RDN of "cn=Debug Target" immediately below the parent ds-cfg-debug-log-publisher entry.
diff --git a/opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn.properties b/opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn.properties
new file mode 100644
index 0000000..5d9a251
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn.properties
@@ -0,0 +1,37 @@
+user-friendly-name=File Based Error Log Publisher
+user-friendly-plural-name=File Based Error Log Publishers
+synopsis=File Based Error Log Publishers publish error messages to the file system.
+property.append.synopsis=Specifies whether to append to existing log files.
+property.asynchronous.synopsis=Indicates whether the File Based Error Log Publisher will publish records asynchronously.
+property.auto-flush.synopsis=Specifies whether to flush the writer after every log record.
+property.auto-flush.description=If the asynchronous writes option is used, the writer will be flushed after all the log records in the queue are written.
+property.buffer-size.synopsis=Specifies the log file buffer size.
+property.default-severity.synopsis=Specifies the default severity levels for the logger.
+property.default-severity.syntax.enumeration.value.all.synopsis=Messages of all severity levels are logged.
+property.default-severity.syntax.enumeration.value.debug.synopsis=The error log severity that is used for messages that provide debugging information triggered during processing.
+property.default-severity.syntax.enumeration.value.fatal-error.synopsis=The error log severity that is used for messages that provide information about fatal errors which may force the server to shut down or operate in a significantly degraded state.
+property.default-severity.syntax.enumeration.value.info.synopsis=The error log severity that is used for messages that provide information about significant events within the server that are not warnings or errors.
+property.default-severity.syntax.enumeration.value.mild-error.synopsis=The error log severity that is used for messages that provide information about mild (recoverable) errors encountered during processing.
+property.default-severity.syntax.enumeration.value.mild-warning.synopsis=The error log severity that is used for messages that provide information about mild warnings triggered during processing.
+property.default-severity.syntax.enumeration.value.none.synopsis=No messages of any severity are logged by default. This value is intended to be used in conjunction with the override-severity property to define an error logger that will publish no error message beside the errors of a given category.
+property.default-severity.syntax.enumeration.value.notice.synopsis=The error log severity that is used for the most important informational messages (i.e., information that should almost always be logged but is not associated with a warning or error condition).
+property.default-severity.syntax.enumeration.value.severe-error.synopsis=The error log severity that is used for messages that provide information about severe errors encountered during processing.
+property.default-severity.syntax.enumeration.value.severe-warning.synopsis=The error log severity that is used for messages that provide information about severe warnings triggered during processing.
+property.enabled.synopsis=Indicates whether the File Based Error Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Error Log Publisher implementation.
+property.log-file.synopsis=The file name to use for the log files generated by the File Based Error Log Publisher .
+property.log-file.description=The path to the file is relative to the server root.
+property.log-file-permissions.synopsis=The UNIX permissions of the log files created by this File Based Error Log Publisher .
+property.log-file-permissions.syntax.string.pattern.synopsis=A valid UNIX mode string. The mode string must contain three digits between zero and seven.
+property.override-severity.synopsis=Specifies the override severity levels for the logger based on the category of the messages.
+property.override-severity.description=Each override severity level should include the category and the severity levels to log for that category, for example, core=mild-error,info,mild-warning. Valid categories are: core, extensions, protocol, config, log, util, schema, plugin, jeb, backend, tools, task, access-control, admin, sync, version, quicksetup, admin-tool, dsconfig, user-defined. Valid severities are: all, fatal-error, info, mild-error, mild-warning, notice, severe-error, severe-warning, debug.
+property.override-severity.default-behavior.alias.synopsis=All messages with the default severity levels are logged.
+property.override-severity.syntax.string.pattern.synopsis=A string in the form category=severity1,severity2...
+property.queue-size.synopsis=The maximum number of log records that can be stored in the asynchronous queue.
+property.retention-policy.synopsis=The retention policy to use for the File Based Error Log Publisher .
+property.retention-policy.description=When multiple policies are used, log files will be cleaned when any of the policy's conditions are met.
+property.retention-policy.default-behavior.alias.synopsis=No retention policy is used and log files will never be cleaned.
+property.rotation-policy.synopsis=The rotation policy to use for the File Based Error Log Publisher .
+property.rotation-policy.description=When multiple policies are used, rotation will occur if any policy's conditions are met.
+property.rotation-policy.default-behavior.alias.synopsis=No rotation policy is used and log rotation will not occur.
+property.time-interval.synopsis=Specifies the interval at which to check whether the log files need to be rotated.
diff --git a/opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_de.properties b/opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_de.properties
new file mode 100644
index 0000000..5d9a251
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_de.properties
@@ -0,0 +1,37 @@
+user-friendly-name=File Based Error Log Publisher
+user-friendly-plural-name=File Based Error Log Publishers
+synopsis=File Based Error Log Publishers publish error messages to the file system.
+property.append.synopsis=Specifies whether to append to existing log files.
+property.asynchronous.synopsis=Indicates whether the File Based Error Log Publisher will publish records asynchronously.
+property.auto-flush.synopsis=Specifies whether to flush the writer after every log record.
+property.auto-flush.description=If the asynchronous writes option is used, the writer will be flushed after all the log records in the queue are written.
+property.buffer-size.synopsis=Specifies the log file buffer size.
+property.default-severity.synopsis=Specifies the default severity levels for the logger.
+property.default-severity.syntax.enumeration.value.all.synopsis=Messages of all severity levels are logged.
+property.default-severity.syntax.enumeration.value.debug.synopsis=The error log severity that is used for messages that provide debugging information triggered during processing.
+property.default-severity.syntax.enumeration.value.fatal-error.synopsis=The error log severity that is used for messages that provide information about fatal errors which may force the server to shut down or operate in a significantly degraded state.
+property.default-severity.syntax.enumeration.value.info.synopsis=The error log severity that is used for messages that provide information about significant events within the server that are not warnings or errors.
+property.default-severity.syntax.enumeration.value.mild-error.synopsis=The error log severity that is used for messages that provide information about mild (recoverable) errors encountered during processing.
+property.default-severity.syntax.enumeration.value.mild-warning.synopsis=The error log severity that is used for messages that provide information about mild warnings triggered during processing.
+property.default-severity.syntax.enumeration.value.none.synopsis=No messages of any severity are logged by default. This value is intended to be used in conjunction with the override-severity property to define an error logger that will publish no error message beside the errors of a given category.
+property.default-severity.syntax.enumeration.value.notice.synopsis=The error log severity that is used for the most important informational messages (i.e., information that should almost always be logged but is not associated with a warning or error condition).
+property.default-severity.syntax.enumeration.value.severe-error.synopsis=The error log severity that is used for messages that provide information about severe errors encountered during processing.
+property.default-severity.syntax.enumeration.value.severe-warning.synopsis=The error log severity that is used for messages that provide information about severe warnings triggered during processing.
+property.enabled.synopsis=Indicates whether the File Based Error Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Error Log Publisher implementation.
+property.log-file.synopsis=The file name to use for the log files generated by the File Based Error Log Publisher .
+property.log-file.description=The path to the file is relative to the server root.
+property.log-file-permissions.synopsis=The UNIX permissions of the log files created by this File Based Error Log Publisher .
+property.log-file-permissions.syntax.string.pattern.synopsis=A valid UNIX mode string. The mode string must contain three digits between zero and seven.
+property.override-severity.synopsis=Specifies the override severity levels for the logger based on the category of the messages.
+property.override-severity.description=Each override severity level should include the category and the severity levels to log for that category, for example, core=mild-error,info,mild-warning. Valid categories are: core, extensions, protocol, config, log, util, schema, plugin, jeb, backend, tools, task, access-control, admin, sync, version, quicksetup, admin-tool, dsconfig, user-defined. Valid severities are: all, fatal-error, info, mild-error, mild-warning, notice, severe-error, severe-warning, debug.
+property.override-severity.default-behavior.alias.synopsis=All messages with the default severity levels are logged.
+property.override-severity.syntax.string.pattern.synopsis=A string in the form category=severity1,severity2...
+property.queue-size.synopsis=The maximum number of log records that can be stored in the asynchronous queue.
+property.retention-policy.synopsis=The retention policy to use for the File Based Error Log Publisher .
+property.retention-policy.description=When multiple policies are used, log files will be cleaned when any of the policy's conditions are met.
+property.retention-policy.default-behavior.alias.synopsis=No retention policy is used and log files will never be cleaned.
+property.rotation-policy.synopsis=The rotation policy to use for the File Based Error Log Publisher .
+property.rotation-policy.description=When multiple policies are used, rotation will occur if any policy's conditions are met.
+property.rotation-policy.default-behavior.alias.synopsis=No rotation policy is used and log rotation will not occur.
+property.time-interval.synopsis=Specifies the interval at which to check whether the log files need to be rotated.
diff --git a/opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_es.properties b/opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_es.properties
new file mode 100644
index 0000000..5d9a251
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_es.properties
@@ -0,0 +1,37 @@
+user-friendly-name=File Based Error Log Publisher
+user-friendly-plural-name=File Based Error Log Publishers
+synopsis=File Based Error Log Publishers publish error messages to the file system.
+property.append.synopsis=Specifies whether to append to existing log files.
+property.asynchronous.synopsis=Indicates whether the File Based Error Log Publisher will publish records asynchronously.
+property.auto-flush.synopsis=Specifies whether to flush the writer after every log record.
+property.auto-flush.description=If the asynchronous writes option is used, the writer will be flushed after all the log records in the queue are written.
+property.buffer-size.synopsis=Specifies the log file buffer size.
+property.default-severity.synopsis=Specifies the default severity levels for the logger.
+property.default-severity.syntax.enumeration.value.all.synopsis=Messages of all severity levels are logged.
+property.default-severity.syntax.enumeration.value.debug.synopsis=The error log severity that is used for messages that provide debugging information triggered during processing.
+property.default-severity.syntax.enumeration.value.fatal-error.synopsis=The error log severity that is used for messages that provide information about fatal errors which may force the server to shut down or operate in a significantly degraded state.
+property.default-severity.syntax.enumeration.value.info.synopsis=The error log severity that is used for messages that provide information about significant events within the server that are not warnings or errors.
+property.default-severity.syntax.enumeration.value.mild-error.synopsis=The error log severity that is used for messages that provide information about mild (recoverable) errors encountered during processing.
+property.default-severity.syntax.enumeration.value.mild-warning.synopsis=The error log severity that is used for messages that provide information about mild warnings triggered during processing.
+property.default-severity.syntax.enumeration.value.none.synopsis=No messages of any severity are logged by default. This value is intended to be used in conjunction with the override-severity property to define an error logger that will publish no error message beside the errors of a given category.
+property.default-severity.syntax.enumeration.value.notice.synopsis=The error log severity that is used for the most important informational messages (i.e., information that should almost always be logged but is not associated with a warning or error condition).
+property.default-severity.syntax.enumeration.value.severe-error.synopsis=The error log severity that is used for messages that provide information about severe errors encountered during processing.
+property.default-severity.syntax.enumeration.value.severe-warning.synopsis=The error log severity that is used for messages that provide information about severe warnings triggered during processing.
+property.enabled.synopsis=Indicates whether the File Based Error Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Error Log Publisher implementation.
+property.log-file.synopsis=The file name to use for the log files generated by the File Based Error Log Publisher .
+property.log-file.description=The path to the file is relative to the server root.
+property.log-file-permissions.synopsis=The UNIX permissions of the log files created by this File Based Error Log Publisher .
+property.log-file-permissions.syntax.string.pattern.synopsis=A valid UNIX mode string. The mode string must contain three digits between zero and seven.
+property.override-severity.synopsis=Specifies the override severity levels for the logger based on the category of the messages.
+property.override-severity.description=Each override severity level should include the category and the severity levels to log for that category, for example, core=mild-error,info,mild-warning. Valid categories are: core, extensions, protocol, config, log, util, schema, plugin, jeb, backend, tools, task, access-control, admin, sync, version, quicksetup, admin-tool, dsconfig, user-defined. Valid severities are: all, fatal-error, info, mild-error, mild-warning, notice, severe-error, severe-warning, debug.
+property.override-severity.default-behavior.alias.synopsis=All messages with the default severity levels are logged.
+property.override-severity.syntax.string.pattern.synopsis=A string in the form category=severity1,severity2...
+property.queue-size.synopsis=The maximum number of log records that can be stored in the asynchronous queue.
+property.retention-policy.synopsis=The retention policy to use for the File Based Error Log Publisher .
+property.retention-policy.description=When multiple policies are used, log files will be cleaned when any of the policy's conditions are met.
+property.retention-policy.default-behavior.alias.synopsis=No retention policy is used and log files will never be cleaned.
+property.rotation-policy.synopsis=The rotation policy to use for the File Based Error Log Publisher .
+property.rotation-policy.description=When multiple policies are used, rotation will occur if any policy's conditions are met.
+property.rotation-policy.default-behavior.alias.synopsis=No rotation policy is used and log rotation will not occur.
+property.time-interval.synopsis=Specifies the interval at which to check whether the log files need to be rotated.
diff --git a/opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_fr.properties b/opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_fr.properties
new file mode 100644
index 0000000..5d9a251
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_fr.properties
@@ -0,0 +1,37 @@
+user-friendly-name=File Based Error Log Publisher
+user-friendly-plural-name=File Based Error Log Publishers
+synopsis=File Based Error Log Publishers publish error messages to the file system.
+property.append.synopsis=Specifies whether to append to existing log files.
+property.asynchronous.synopsis=Indicates whether the File Based Error Log Publisher will publish records asynchronously.
+property.auto-flush.synopsis=Specifies whether to flush the writer after every log record.
+property.auto-flush.description=If the asynchronous writes option is used, the writer will be flushed after all the log records in the queue are written.
+property.buffer-size.synopsis=Specifies the log file buffer size.
+property.default-severity.synopsis=Specifies the default severity levels for the logger.
+property.default-severity.syntax.enumeration.value.all.synopsis=Messages of all severity levels are logged.
+property.default-severity.syntax.enumeration.value.debug.synopsis=The error log severity that is used for messages that provide debugging information triggered during processing.
+property.default-severity.syntax.enumeration.value.fatal-error.synopsis=The error log severity that is used for messages that provide information about fatal errors which may force the server to shut down or operate in a significantly degraded state.
+property.default-severity.syntax.enumeration.value.info.synopsis=The error log severity that is used for messages that provide information about significant events within the server that are not warnings or errors.
+property.default-severity.syntax.enumeration.value.mild-error.synopsis=The error log severity that is used for messages that provide information about mild (recoverable) errors encountered during processing.
+property.default-severity.syntax.enumeration.value.mild-warning.synopsis=The error log severity that is used for messages that provide information about mild warnings triggered during processing.
+property.default-severity.syntax.enumeration.value.none.synopsis=No messages of any severity are logged by default. This value is intended to be used in conjunction with the override-severity property to define an error logger that will publish no error message beside the errors of a given category.
+property.default-severity.syntax.enumeration.value.notice.synopsis=The error log severity that is used for the most important informational messages (i.e., information that should almost always be logged but is not associated with a warning or error condition).
+property.default-severity.syntax.enumeration.value.severe-error.synopsis=The error log severity that is used for messages that provide information about severe errors encountered during processing.
+property.default-severity.syntax.enumeration.value.severe-warning.synopsis=The error log severity that is used for messages that provide information about severe warnings triggered during processing.
+property.enabled.synopsis=Indicates whether the File Based Error Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Error Log Publisher implementation.
+property.log-file.synopsis=The file name to use for the log files generated by the File Based Error Log Publisher .
+property.log-file.description=The path to the file is relative to the server root.
+property.log-file-permissions.synopsis=The UNIX permissions of the log files created by this File Based Error Log Publisher .
+property.log-file-permissions.syntax.string.pattern.synopsis=A valid UNIX mode string. The mode string must contain three digits between zero and seven.
+property.override-severity.synopsis=Specifies the override severity levels for the logger based on the category of the messages.
+property.override-severity.description=Each override severity level should include the category and the severity levels to log for that category, for example, core=mild-error,info,mild-warning. Valid categories are: core, extensions, protocol, config, log, util, schema, plugin, jeb, backend, tools, task, access-control, admin, sync, version, quicksetup, admin-tool, dsconfig, user-defined. Valid severities are: all, fatal-error, info, mild-error, mild-warning, notice, severe-error, severe-warning, debug.
+property.override-severity.default-behavior.alias.synopsis=All messages with the default severity levels are logged.
+property.override-severity.syntax.string.pattern.synopsis=A string in the form category=severity1,severity2...
+property.queue-size.synopsis=The maximum number of log records that can be stored in the asynchronous queue.
+property.retention-policy.synopsis=The retention policy to use for the File Based Error Log Publisher .
+property.retention-policy.description=When multiple policies are used, log files will be cleaned when any of the policy's conditions are met.
+property.retention-policy.default-behavior.alias.synopsis=No retention policy is used and log files will never be cleaned.
+property.rotation-policy.synopsis=The rotation policy to use for the File Based Error Log Publisher .
+property.rotation-policy.description=When multiple policies are used, rotation will occur if any policy's conditions are met.
+property.rotation-policy.default-behavior.alias.synopsis=No rotation policy is used and log rotation will not occur.
+property.time-interval.synopsis=Specifies the interval at which to check whether the log files need to be rotated.
diff --git a/opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_ja.properties b/opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_ja.properties
new file mode 100644
index 0000000..5d9a251
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_ja.properties
@@ -0,0 +1,37 @@
+user-friendly-name=File Based Error Log Publisher
+user-friendly-plural-name=File Based Error Log Publishers
+synopsis=File Based Error Log Publishers publish error messages to the file system.
+property.append.synopsis=Specifies whether to append to existing log files.
+property.asynchronous.synopsis=Indicates whether the File Based Error Log Publisher will publish records asynchronously.
+property.auto-flush.synopsis=Specifies whether to flush the writer after every log record.
+property.auto-flush.description=If the asynchronous writes option is used, the writer will be flushed after all the log records in the queue are written.
+property.buffer-size.synopsis=Specifies the log file buffer size.
+property.default-severity.synopsis=Specifies the default severity levels for the logger.
+property.default-severity.syntax.enumeration.value.all.synopsis=Messages of all severity levels are logged.
+property.default-severity.syntax.enumeration.value.debug.synopsis=The error log severity that is used for messages that provide debugging information triggered during processing.
+property.default-severity.syntax.enumeration.value.fatal-error.synopsis=The error log severity that is used for messages that provide information about fatal errors which may force the server to shut down or operate in a significantly degraded state.
+property.default-severity.syntax.enumeration.value.info.synopsis=The error log severity that is used for messages that provide information about significant events within the server that are not warnings or errors.
+property.default-severity.syntax.enumeration.value.mild-error.synopsis=The error log severity that is used for messages that provide information about mild (recoverable) errors encountered during processing.
+property.default-severity.syntax.enumeration.value.mild-warning.synopsis=The error log severity that is used for messages that provide information about mild warnings triggered during processing.
+property.default-severity.syntax.enumeration.value.none.synopsis=No messages of any severity are logged by default. This value is intended to be used in conjunction with the override-severity property to define an error logger that will publish no error message beside the errors of a given category.
+property.default-severity.syntax.enumeration.value.notice.synopsis=The error log severity that is used for the most important informational messages (i.e., information that should almost always be logged but is not associated with a warning or error condition).
+property.default-severity.syntax.enumeration.value.severe-error.synopsis=The error log severity that is used for messages that provide information about severe errors encountered during processing.
+property.default-severity.syntax.enumeration.value.severe-warning.synopsis=The error log severity that is used for messages that provide information about severe warnings triggered during processing.
+property.enabled.synopsis=Indicates whether the File Based Error Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Error Log Publisher implementation.
+property.log-file.synopsis=The file name to use for the log files generated by the File Based Error Log Publisher .
+property.log-file.description=The path to the file is relative to the server root.
+property.log-file-permissions.synopsis=The UNIX permissions of the log files created by this File Based Error Log Publisher .
+property.log-file-permissions.syntax.string.pattern.synopsis=A valid UNIX mode string. The mode string must contain three digits between zero and seven.
+property.override-severity.synopsis=Specifies the override severity levels for the logger based on the category of the messages.
+property.override-severity.description=Each override severity level should include the category and the severity levels to log for that category, for example, core=mild-error,info,mild-warning. Valid categories are: core, extensions, protocol, config, log, util, schema, plugin, jeb, backend, tools, task, access-control, admin, sync, version, quicksetup, admin-tool, dsconfig, user-defined. Valid severities are: all, fatal-error, info, mild-error, mild-warning, notice, severe-error, severe-warning, debug.
+property.override-severity.default-behavior.alias.synopsis=All messages with the default severity levels are logged.
+property.override-severity.syntax.string.pattern.synopsis=A string in the form category=severity1,severity2...
+property.queue-size.synopsis=The maximum number of log records that can be stored in the asynchronous queue.
+property.retention-policy.synopsis=The retention policy to use for the File Based Error Log Publisher .
+property.retention-policy.description=When multiple policies are used, log files will be cleaned when any of the policy's conditions are met.
+property.retention-policy.default-behavior.alias.synopsis=No retention policy is used and log files will never be cleaned.
+property.rotation-policy.synopsis=The rotation policy to use for the File Based Error Log Publisher .
+property.rotation-policy.description=When multiple policies are used, rotation will occur if any policy's conditions are met.
+property.rotation-policy.default-behavior.alias.synopsis=No rotation policy is used and log rotation will not occur.
+property.time-interval.synopsis=Specifies the interval at which to check whether the log files need to be rotated.
diff --git a/opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_ko.properties b/opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_ko.properties
new file mode 100644
index 0000000..5d9a251
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_ko.properties
@@ -0,0 +1,37 @@
+user-friendly-name=File Based Error Log Publisher
+user-friendly-plural-name=File Based Error Log Publishers
+synopsis=File Based Error Log Publishers publish error messages to the file system.
+property.append.synopsis=Specifies whether to append to existing log files.
+property.asynchronous.synopsis=Indicates whether the File Based Error Log Publisher will publish records asynchronously.
+property.auto-flush.synopsis=Specifies whether to flush the writer after every log record.
+property.auto-flush.description=If the asynchronous writes option is used, the writer will be flushed after all the log records in the queue are written.
+property.buffer-size.synopsis=Specifies the log file buffer size.
+property.default-severity.synopsis=Specifies the default severity levels for the logger.
+property.default-severity.syntax.enumeration.value.all.synopsis=Messages of all severity levels are logged.
+property.default-severity.syntax.enumeration.value.debug.synopsis=The error log severity that is used for messages that provide debugging information triggered during processing.
+property.default-severity.syntax.enumeration.value.fatal-error.synopsis=The error log severity that is used for messages that provide information about fatal errors which may force the server to shut down or operate in a significantly degraded state.
+property.default-severity.syntax.enumeration.value.info.synopsis=The error log severity that is used for messages that provide information about significant events within the server that are not warnings or errors.
+property.default-severity.syntax.enumeration.value.mild-error.synopsis=The error log severity that is used for messages that provide information about mild (recoverable) errors encountered during processing.
+property.default-severity.syntax.enumeration.value.mild-warning.synopsis=The error log severity that is used for messages that provide information about mild warnings triggered during processing.
+property.default-severity.syntax.enumeration.value.none.synopsis=No messages of any severity are logged by default. This value is intended to be used in conjunction with the override-severity property to define an error logger that will publish no error message beside the errors of a given category.
+property.default-severity.syntax.enumeration.value.notice.synopsis=The error log severity that is used for the most important informational messages (i.e., information that should almost always be logged but is not associated with a warning or error condition).
+property.default-severity.syntax.enumeration.value.severe-error.synopsis=The error log severity that is used for messages that provide information about severe errors encountered during processing.
+property.default-severity.syntax.enumeration.value.severe-warning.synopsis=The error log severity that is used for messages that provide information about severe warnings triggered during processing.
+property.enabled.synopsis=Indicates whether the File Based Error Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Error Log Publisher implementation.
+property.log-file.synopsis=The file name to use for the log files generated by the File Based Error Log Publisher .
+property.log-file.description=The path to the file is relative to the server root.
+property.log-file-permissions.synopsis=The UNIX permissions of the log files created by this File Based Error Log Publisher .
+property.log-file-permissions.syntax.string.pattern.synopsis=A valid UNIX mode string. The mode string must contain three digits between zero and seven.
+property.override-severity.synopsis=Specifies the override severity levels for the logger based on the category of the messages.
+property.override-severity.description=Each override severity level should include the category and the severity levels to log for that category, for example, core=mild-error,info,mild-warning. Valid categories are: core, extensions, protocol, config, log, util, schema, plugin, jeb, backend, tools, task, access-control, admin, sync, version, quicksetup, admin-tool, dsconfig, user-defined. Valid severities are: all, fatal-error, info, mild-error, mild-warning, notice, severe-error, severe-warning, debug.
+property.override-severity.default-behavior.alias.synopsis=All messages with the default severity levels are logged.
+property.override-severity.syntax.string.pattern.synopsis=A string in the form category=severity1,severity2...
+property.queue-size.synopsis=The maximum number of log records that can be stored in the asynchronous queue.
+property.retention-policy.synopsis=The retention policy to use for the File Based Error Log Publisher .
+property.retention-policy.description=When multiple policies are used, log files will be cleaned when any of the policy's conditions are met.
+property.retention-policy.default-behavior.alias.synopsis=No retention policy is used and log files will never be cleaned.
+property.rotation-policy.synopsis=The rotation policy to use for the File Based Error Log Publisher .
+property.rotation-policy.description=When multiple policies are used, rotation will occur if any policy's conditions are met.
+property.rotation-policy.default-behavior.alias.synopsis=No rotation policy is used and log rotation will not occur.
+property.time-interval.synopsis=Specifies the interval at which to check whether the log files need to be rotated.
diff --git a/opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_zh_CN.properties b/opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..5d9a251
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_zh_CN.properties
@@ -0,0 +1,37 @@
+user-friendly-name=File Based Error Log Publisher
+user-friendly-plural-name=File Based Error Log Publishers
+synopsis=File Based Error Log Publishers publish error messages to the file system.
+property.append.synopsis=Specifies whether to append to existing log files.
+property.asynchronous.synopsis=Indicates whether the File Based Error Log Publisher will publish records asynchronously.
+property.auto-flush.synopsis=Specifies whether to flush the writer after every log record.
+property.auto-flush.description=If the asynchronous writes option is used, the writer will be flushed after all the log records in the queue are written.
+property.buffer-size.synopsis=Specifies the log file buffer size.
+property.default-severity.synopsis=Specifies the default severity levels for the logger.
+property.default-severity.syntax.enumeration.value.all.synopsis=Messages of all severity levels are logged.
+property.default-severity.syntax.enumeration.value.debug.synopsis=The error log severity that is used for messages that provide debugging information triggered during processing.
+property.default-severity.syntax.enumeration.value.fatal-error.synopsis=The error log severity that is used for messages that provide information about fatal errors which may force the server to shut down or operate in a significantly degraded state.
+property.default-severity.syntax.enumeration.value.info.synopsis=The error log severity that is used for messages that provide information about significant events within the server that are not warnings or errors.
+property.default-severity.syntax.enumeration.value.mild-error.synopsis=The error log severity that is used for messages that provide information about mild (recoverable) errors encountered during processing.
+property.default-severity.syntax.enumeration.value.mild-warning.synopsis=The error log severity that is used for messages that provide information about mild warnings triggered during processing.
+property.default-severity.syntax.enumeration.value.none.synopsis=No messages of any severity are logged by default. This value is intended to be used in conjunction with the override-severity property to define an error logger that will publish no error message beside the errors of a given category.
+property.default-severity.syntax.enumeration.value.notice.synopsis=The error log severity that is used for the most important informational messages (i.e., information that should almost always be logged but is not associated with a warning or error condition).
+property.default-severity.syntax.enumeration.value.severe-error.synopsis=The error log severity that is used for messages that provide information about severe errors encountered during processing.
+property.default-severity.syntax.enumeration.value.severe-warning.synopsis=The error log severity that is used for messages that provide information about severe warnings triggered during processing.
+property.enabled.synopsis=Indicates whether the File Based Error Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Error Log Publisher implementation.
+property.log-file.synopsis=The file name to use for the log files generated by the File Based Error Log Publisher .
+property.log-file.description=The path to the file is relative to the server root.
+property.log-file-permissions.synopsis=The UNIX permissions of the log files created by this File Based Error Log Publisher .
+property.log-file-permissions.syntax.string.pattern.synopsis=A valid UNIX mode string. The mode string must contain three digits between zero and seven.
+property.override-severity.synopsis=Specifies the override severity levels for the logger based on the category of the messages.
+property.override-severity.description=Each override severity level should include the category and the severity levels to log for that category, for example, core=mild-error,info,mild-warning. Valid categories are: core, extensions, protocol, config, log, util, schema, plugin, jeb, backend, tools, task, access-control, admin, sync, version, quicksetup, admin-tool, dsconfig, user-defined. Valid severities are: all, fatal-error, info, mild-error, mild-warning, notice, severe-error, severe-warning, debug.
+property.override-severity.default-behavior.alias.synopsis=All messages with the default severity levels are logged.
+property.override-severity.syntax.string.pattern.synopsis=A string in the form category=severity1,severity2...
+property.queue-size.synopsis=The maximum number of log records that can be stored in the asynchronous queue.
+property.retention-policy.synopsis=The retention policy to use for the File Based Error Log Publisher .
+property.retention-policy.description=When multiple policies are used, log files will be cleaned when any of the policy's conditions are met.
+property.retention-policy.default-behavior.alias.synopsis=No retention policy is used and log files will never be cleaned.
+property.rotation-policy.synopsis=The rotation policy to use for the File Based Error Log Publisher .
+property.rotation-policy.description=When multiple policies are used, rotation will occur if any policy's conditions are met.
+property.rotation-policy.default-behavior.alias.synopsis=No rotation policy is used and log rotation will not occur.
+property.time-interval.synopsis=Specifies the interval at which to check whether the log files need to be rotated.
diff --git a/opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_zh_TW.properties b/opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..5d9a251
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedErrorLogPublisherCfgDefn_zh_TW.properties
@@ -0,0 +1,37 @@
+user-friendly-name=File Based Error Log Publisher
+user-friendly-plural-name=File Based Error Log Publishers
+synopsis=File Based Error Log Publishers publish error messages to the file system.
+property.append.synopsis=Specifies whether to append to existing log files.
+property.asynchronous.synopsis=Indicates whether the File Based Error Log Publisher will publish records asynchronously.
+property.auto-flush.synopsis=Specifies whether to flush the writer after every log record.
+property.auto-flush.description=If the asynchronous writes option is used, the writer will be flushed after all the log records in the queue are written.
+property.buffer-size.synopsis=Specifies the log file buffer size.
+property.default-severity.synopsis=Specifies the default severity levels for the logger.
+property.default-severity.syntax.enumeration.value.all.synopsis=Messages of all severity levels are logged.
+property.default-severity.syntax.enumeration.value.debug.synopsis=The error log severity that is used for messages that provide debugging information triggered during processing.
+property.default-severity.syntax.enumeration.value.fatal-error.synopsis=The error log severity that is used for messages that provide information about fatal errors which may force the server to shut down or operate in a significantly degraded state.
+property.default-severity.syntax.enumeration.value.info.synopsis=The error log severity that is used for messages that provide information about significant events within the server that are not warnings or errors.
+property.default-severity.syntax.enumeration.value.mild-error.synopsis=The error log severity that is used for messages that provide information about mild (recoverable) errors encountered during processing.
+property.default-severity.syntax.enumeration.value.mild-warning.synopsis=The error log severity that is used for messages that provide information about mild warnings triggered during processing.
+property.default-severity.syntax.enumeration.value.none.synopsis=No messages of any severity are logged by default. This value is intended to be used in conjunction with the override-severity property to define an error logger that will publish no error message beside the errors of a given category.
+property.default-severity.syntax.enumeration.value.notice.synopsis=The error log severity that is used for the most important informational messages (i.e., information that should almost always be logged but is not associated with a warning or error condition).
+property.default-severity.syntax.enumeration.value.severe-error.synopsis=The error log severity that is used for messages that provide information about severe errors encountered during processing.
+property.default-severity.syntax.enumeration.value.severe-warning.synopsis=The error log severity that is used for messages that provide information about severe warnings triggered during processing.
+property.enabled.synopsis=Indicates whether the File Based Error Log Publisher is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Error Log Publisher implementation.
+property.log-file.synopsis=The file name to use for the log files generated by the File Based Error Log Publisher .
+property.log-file.description=The path to the file is relative to the server root.
+property.log-file-permissions.synopsis=The UNIX permissions of the log files created by this File Based Error Log Publisher .
+property.log-file-permissions.syntax.string.pattern.synopsis=A valid UNIX mode string. The mode string must contain three digits between zero and seven.
+property.override-severity.synopsis=Specifies the override severity levels for the logger based on the category of the messages.
+property.override-severity.description=Each override severity level should include the category and the severity levels to log for that category, for example, core=mild-error,info,mild-warning. Valid categories are: core, extensions, protocol, config, log, util, schema, plugin, jeb, backend, tools, task, access-control, admin, sync, version, quicksetup, admin-tool, dsconfig, user-defined. Valid severities are: all, fatal-error, info, mild-error, mild-warning, notice, severe-error, severe-warning, debug.
+property.override-severity.default-behavior.alias.synopsis=All messages with the default severity levels are logged.
+property.override-severity.syntax.string.pattern.synopsis=A string in the form category=severity1,severity2...
+property.queue-size.synopsis=The maximum number of log records that can be stored in the asynchronous queue.
+property.retention-policy.synopsis=The retention policy to use for the File Based Error Log Publisher .
+property.retention-policy.description=When multiple policies are used, log files will be cleaned when any of the policy's conditions are met.
+property.retention-policy.default-behavior.alias.synopsis=No retention policy is used and log files will never be cleaned.
+property.rotation-policy.synopsis=The rotation policy to use for the File Based Error Log Publisher .
+property.rotation-policy.description=When multiple policies are used, rotation will occur if any policy's conditions are met.
+property.rotation-policy.default-behavior.alias.synopsis=No rotation policy is used and log rotation will not occur.
+property.time-interval.synopsis=Specifies the interval at which to check whether the log files need to be rotated.
diff --git a/opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn.properties b/opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn.properties
new file mode 100644
index 0000000..328eb2c
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn.properties
@@ -0,0 +1,24 @@
+user-friendly-name=File Based Key Manager Provider
+user-friendly-plural-name=File Based Key Manager Providers
+synopsis=The File Based Key Manager Provider can be used to obtain the server certificate from a key store file on the local file system.
+description=Multiple file formats may be supported, depending on the providers supported by the underlying Java runtime environment.
+constraint.1.synopsis=The key store pin must be specified using one of the key-store-pin properties when the File Based Key Manager Provider is enabled.
+property.enabled.synopsis=Indicates whether the File Based Key Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Key Manager Provider implementation.
+property.key-store-file.synopsis=Specifies the path to the file that contains the private key information. This may be an absolute path, or a path that is relative to the OpenDS Directory Server instance root.
+property.key-store-file.description=Changes to this property will take effect the next time that the key manager is accessed.
+property.key-store-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.key-store-pin.synopsis=Specifies the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.syntax.string.pattern.synopsis=The name of a defined environment variable that contains the clear-text PIN required to access the contents of the key store.
+property.key-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.key-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-property.syntax.string.pattern.synopsis=The name of a defined Java property.
+property.key-store-type.synopsis=Specifies the format for the data in the key store file.
+property.key-store-type.description=Valid values should always include 'JKS' and 'PKCS12', but different implementations may allow other values as well. If no value is provided, the JVM-default value is used. Changes to this configuration attribute will take effect the next time that the key manager is accessed.
+property.key-store-type.syntax.string.pattern.synopsis=Any key store format supported by the Java runtime environment.
diff --git a/opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_de.properties b/opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_de.properties
new file mode 100644
index 0000000..328eb2c
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_de.properties
@@ -0,0 +1,24 @@
+user-friendly-name=File Based Key Manager Provider
+user-friendly-plural-name=File Based Key Manager Providers
+synopsis=The File Based Key Manager Provider can be used to obtain the server certificate from a key store file on the local file system.
+description=Multiple file formats may be supported, depending on the providers supported by the underlying Java runtime environment.
+constraint.1.synopsis=The key store pin must be specified using one of the key-store-pin properties when the File Based Key Manager Provider is enabled.
+property.enabled.synopsis=Indicates whether the File Based Key Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Key Manager Provider implementation.
+property.key-store-file.synopsis=Specifies the path to the file that contains the private key information. This may be an absolute path, or a path that is relative to the OpenDS Directory Server instance root.
+property.key-store-file.description=Changes to this property will take effect the next time that the key manager is accessed.
+property.key-store-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.key-store-pin.synopsis=Specifies the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.syntax.string.pattern.synopsis=The name of a defined environment variable that contains the clear-text PIN required to access the contents of the key store.
+property.key-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.key-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-property.syntax.string.pattern.synopsis=The name of a defined Java property.
+property.key-store-type.synopsis=Specifies the format for the data in the key store file.
+property.key-store-type.description=Valid values should always include 'JKS' and 'PKCS12', but different implementations may allow other values as well. If no value is provided, the JVM-default value is used. Changes to this configuration attribute will take effect the next time that the key manager is accessed.
+property.key-store-type.syntax.string.pattern.synopsis=Any key store format supported by the Java runtime environment.
diff --git a/opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_es.properties b/opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_es.properties
new file mode 100644
index 0000000..328eb2c
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_es.properties
@@ -0,0 +1,24 @@
+user-friendly-name=File Based Key Manager Provider
+user-friendly-plural-name=File Based Key Manager Providers
+synopsis=The File Based Key Manager Provider can be used to obtain the server certificate from a key store file on the local file system.
+description=Multiple file formats may be supported, depending on the providers supported by the underlying Java runtime environment.
+constraint.1.synopsis=The key store pin must be specified using one of the key-store-pin properties when the File Based Key Manager Provider is enabled.
+property.enabled.synopsis=Indicates whether the File Based Key Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Key Manager Provider implementation.
+property.key-store-file.synopsis=Specifies the path to the file that contains the private key information. This may be an absolute path, or a path that is relative to the OpenDS Directory Server instance root.
+property.key-store-file.description=Changes to this property will take effect the next time that the key manager is accessed.
+property.key-store-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.key-store-pin.synopsis=Specifies the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.syntax.string.pattern.synopsis=The name of a defined environment variable that contains the clear-text PIN required to access the contents of the key store.
+property.key-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.key-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-property.syntax.string.pattern.synopsis=The name of a defined Java property.
+property.key-store-type.synopsis=Specifies the format for the data in the key store file.
+property.key-store-type.description=Valid values should always include 'JKS' and 'PKCS12', but different implementations may allow other values as well. If no value is provided, the JVM-default value is used. Changes to this configuration attribute will take effect the next time that the key manager is accessed.
+property.key-store-type.syntax.string.pattern.synopsis=Any key store format supported by the Java runtime environment.
diff --git a/opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_fr.properties b/opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_fr.properties
new file mode 100644
index 0000000..328eb2c
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_fr.properties
@@ -0,0 +1,24 @@
+user-friendly-name=File Based Key Manager Provider
+user-friendly-plural-name=File Based Key Manager Providers
+synopsis=The File Based Key Manager Provider can be used to obtain the server certificate from a key store file on the local file system.
+description=Multiple file formats may be supported, depending on the providers supported by the underlying Java runtime environment.
+constraint.1.synopsis=The key store pin must be specified using one of the key-store-pin properties when the File Based Key Manager Provider is enabled.
+property.enabled.synopsis=Indicates whether the File Based Key Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Key Manager Provider implementation.
+property.key-store-file.synopsis=Specifies the path to the file that contains the private key information. This may be an absolute path, or a path that is relative to the OpenDS Directory Server instance root.
+property.key-store-file.description=Changes to this property will take effect the next time that the key manager is accessed.
+property.key-store-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.key-store-pin.synopsis=Specifies the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.syntax.string.pattern.synopsis=The name of a defined environment variable that contains the clear-text PIN required to access the contents of the key store.
+property.key-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.key-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-property.syntax.string.pattern.synopsis=The name of a defined Java property.
+property.key-store-type.synopsis=Specifies the format for the data in the key store file.
+property.key-store-type.description=Valid values should always include 'JKS' and 'PKCS12', but different implementations may allow other values as well. If no value is provided, the JVM-default value is used. Changes to this configuration attribute will take effect the next time that the key manager is accessed.
+property.key-store-type.syntax.string.pattern.synopsis=Any key store format supported by the Java runtime environment.
diff --git a/opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_ja.properties b/opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_ja.properties
new file mode 100644
index 0000000..328eb2c
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_ja.properties
@@ -0,0 +1,24 @@
+user-friendly-name=File Based Key Manager Provider
+user-friendly-plural-name=File Based Key Manager Providers
+synopsis=The File Based Key Manager Provider can be used to obtain the server certificate from a key store file on the local file system.
+description=Multiple file formats may be supported, depending on the providers supported by the underlying Java runtime environment.
+constraint.1.synopsis=The key store pin must be specified using one of the key-store-pin properties when the File Based Key Manager Provider is enabled.
+property.enabled.synopsis=Indicates whether the File Based Key Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Key Manager Provider implementation.
+property.key-store-file.synopsis=Specifies the path to the file that contains the private key information. This may be an absolute path, or a path that is relative to the OpenDS Directory Server instance root.
+property.key-store-file.description=Changes to this property will take effect the next time that the key manager is accessed.
+property.key-store-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.key-store-pin.synopsis=Specifies the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.syntax.string.pattern.synopsis=The name of a defined environment variable that contains the clear-text PIN required to access the contents of the key store.
+property.key-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.key-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-property.syntax.string.pattern.synopsis=The name of a defined Java property.
+property.key-store-type.synopsis=Specifies the format for the data in the key store file.
+property.key-store-type.description=Valid values should always include 'JKS' and 'PKCS12', but different implementations may allow other values as well. If no value is provided, the JVM-default value is used. Changes to this configuration attribute will take effect the next time that the key manager is accessed.
+property.key-store-type.syntax.string.pattern.synopsis=Any key store format supported by the Java runtime environment.
diff --git a/opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_ko.properties b/opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_ko.properties
new file mode 100644
index 0000000..328eb2c
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_ko.properties
@@ -0,0 +1,24 @@
+user-friendly-name=File Based Key Manager Provider
+user-friendly-plural-name=File Based Key Manager Providers
+synopsis=The File Based Key Manager Provider can be used to obtain the server certificate from a key store file on the local file system.
+description=Multiple file formats may be supported, depending on the providers supported by the underlying Java runtime environment.
+constraint.1.synopsis=The key store pin must be specified using one of the key-store-pin properties when the File Based Key Manager Provider is enabled.
+property.enabled.synopsis=Indicates whether the File Based Key Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Key Manager Provider implementation.
+property.key-store-file.synopsis=Specifies the path to the file that contains the private key information. This may be an absolute path, or a path that is relative to the OpenDS Directory Server instance root.
+property.key-store-file.description=Changes to this property will take effect the next time that the key manager is accessed.
+property.key-store-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.key-store-pin.synopsis=Specifies the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.syntax.string.pattern.synopsis=The name of a defined environment variable that contains the clear-text PIN required to access the contents of the key store.
+property.key-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.key-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-property.syntax.string.pattern.synopsis=The name of a defined Java property.
+property.key-store-type.synopsis=Specifies the format for the data in the key store file.
+property.key-store-type.description=Valid values should always include 'JKS' and 'PKCS12', but different implementations may allow other values as well. If no value is provided, the JVM-default value is used. Changes to this configuration attribute will take effect the next time that the key manager is accessed.
+property.key-store-type.syntax.string.pattern.synopsis=Any key store format supported by the Java runtime environment.
diff --git a/opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_zh_CN.properties b/opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..328eb2c
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_zh_CN.properties
@@ -0,0 +1,24 @@
+user-friendly-name=File Based Key Manager Provider
+user-friendly-plural-name=File Based Key Manager Providers
+synopsis=The File Based Key Manager Provider can be used to obtain the server certificate from a key store file on the local file system.
+description=Multiple file formats may be supported, depending on the providers supported by the underlying Java runtime environment.
+constraint.1.synopsis=The key store pin must be specified using one of the key-store-pin properties when the File Based Key Manager Provider is enabled.
+property.enabled.synopsis=Indicates whether the File Based Key Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Key Manager Provider implementation.
+property.key-store-file.synopsis=Specifies the path to the file that contains the private key information. This may be an absolute path, or a path that is relative to the OpenDS Directory Server instance root.
+property.key-store-file.description=Changes to this property will take effect the next time that the key manager is accessed.
+property.key-store-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.key-store-pin.synopsis=Specifies the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.syntax.string.pattern.synopsis=The name of a defined environment variable that contains the clear-text PIN required to access the contents of the key store.
+property.key-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.key-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-property.syntax.string.pattern.synopsis=The name of a defined Java property.
+property.key-store-type.synopsis=Specifies the format for the data in the key store file.
+property.key-store-type.description=Valid values should always include 'JKS' and 'PKCS12', but different implementations may allow other values as well. If no value is provided, the JVM-default value is used. Changes to this configuration attribute will take effect the next time that the key manager is accessed.
+property.key-store-type.syntax.string.pattern.synopsis=Any key store format supported by the Java runtime environment.
diff --git a/opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_zh_TW.properties b/opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..328eb2c
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedKeyManagerProviderCfgDefn_zh_TW.properties
@@ -0,0 +1,24 @@
+user-friendly-name=File Based Key Manager Provider
+user-friendly-plural-name=File Based Key Manager Providers
+synopsis=The File Based Key Manager Provider can be used to obtain the server certificate from a key store file on the local file system.
+description=Multiple file formats may be supported, depending on the providers supported by the underlying Java runtime environment.
+constraint.1.synopsis=The key store pin must be specified using one of the key-store-pin properties when the File Based Key Manager Provider is enabled.
+property.enabled.synopsis=Indicates whether the File Based Key Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Key Manager Provider implementation.
+property.key-store-file.synopsis=Specifies the path to the file that contains the private key information. This may be an absolute path, or a path that is relative to the OpenDS Directory Server instance root.
+property.key-store-file.description=Changes to this property will take effect the next time that the key manager is accessed.
+property.key-store-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.key-store-pin.synopsis=Specifies the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.syntax.string.pattern.synopsis=The name of a defined environment variable that contains the clear-text PIN required to access the contents of the key store.
+property.key-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.key-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the File Based Key Manager Provider .
+property.key-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Key Manager Provider is accessed.
+property.key-store-pin-property.syntax.string.pattern.synopsis=The name of a defined Java property.
+property.key-store-type.synopsis=Specifies the format for the data in the key store file.
+property.key-store-type.description=Valid values should always include 'JKS' and 'PKCS12', but different implementations may allow other values as well. If no value is provided, the JVM-default value is used. Changes to this configuration attribute will take effect the next time that the key manager is accessed.
+property.key-store-type.syntax.string.pattern.synopsis=Any key store format supported by the Java runtime environment.
diff --git a/opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn.properties b/opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn.properties
new file mode 100644
index 0000000..6ab8533
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn.properties
@@ -0,0 +1,20 @@
+user-friendly-name=File Based Trust Manager Provider
+user-friendly-plural-name=File Based Trust Manager Providers
+synopsis=The file-based trust manager provider determines whether to trust a presented certificate based on whether that certificate exists in a server trust store file.
+description=The trust store file can be in either JKS (the default Java key store format) or PKCS#12 (a standard certificate format) form.
+property.enabled.synopsis=Indicate whether the File Based Trust Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Trust Manager Provider implementation.
+property.trust-store-file.synopsis=Specifies the path to the file containing the trust information. It can be an absolute path or a path that is relative to the OpenDS Directory Server instance root.
+property.trust-store-file.description=Changes to this configuration attribute take effect the next time that the trust manager is accessed.
+property.trust-store-file.syntax.string.pattern.synopsis=An absolute path or a path that is relative to the OpenDS Directory Server instance root.
+property.trust-store-pin.synopsis=Specifies the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-type.synopsis=Specifies the format for the data in the trust store file.
+property.trust-store-type.description=Valid values always include 'JKS' and 'PKCS12', but different implementations can allow other values as well. If no value is provided, then the JVM default value is used. Changes to this configuration attribute take effect the next time that the trust manager is accessed.
+property.trust-store-type.syntax.string.pattern.synopsis=Any key store format supported by the Java runtime environment. The "JKS" and "PKCS12" formats are typically available in Java environments.
diff --git a/opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_de.properties b/opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_de.properties
new file mode 100644
index 0000000..6ab8533
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_de.properties
@@ -0,0 +1,20 @@
+user-friendly-name=File Based Trust Manager Provider
+user-friendly-plural-name=File Based Trust Manager Providers
+synopsis=The file-based trust manager provider determines whether to trust a presented certificate based on whether that certificate exists in a server trust store file.
+description=The trust store file can be in either JKS (the default Java key store format) or PKCS#12 (a standard certificate format) form.
+property.enabled.synopsis=Indicate whether the File Based Trust Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Trust Manager Provider implementation.
+property.trust-store-file.synopsis=Specifies the path to the file containing the trust information. It can be an absolute path or a path that is relative to the OpenDS Directory Server instance root.
+property.trust-store-file.description=Changes to this configuration attribute take effect the next time that the trust manager is accessed.
+property.trust-store-file.syntax.string.pattern.synopsis=An absolute path or a path that is relative to the OpenDS Directory Server instance root.
+property.trust-store-pin.synopsis=Specifies the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-type.synopsis=Specifies the format for the data in the trust store file.
+property.trust-store-type.description=Valid values always include 'JKS' and 'PKCS12', but different implementations can allow other values as well. If no value is provided, then the JVM default value is used. Changes to this configuration attribute take effect the next time that the trust manager is accessed.
+property.trust-store-type.syntax.string.pattern.synopsis=Any key store format supported by the Java runtime environment. The "JKS" and "PKCS12" formats are typically available in Java environments.
diff --git a/opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_es.properties b/opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_es.properties
new file mode 100644
index 0000000..6ab8533
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_es.properties
@@ -0,0 +1,20 @@
+user-friendly-name=File Based Trust Manager Provider
+user-friendly-plural-name=File Based Trust Manager Providers
+synopsis=The file-based trust manager provider determines whether to trust a presented certificate based on whether that certificate exists in a server trust store file.
+description=The trust store file can be in either JKS (the default Java key store format) or PKCS#12 (a standard certificate format) form.
+property.enabled.synopsis=Indicate whether the File Based Trust Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Trust Manager Provider implementation.
+property.trust-store-file.synopsis=Specifies the path to the file containing the trust information. It can be an absolute path or a path that is relative to the OpenDS Directory Server instance root.
+property.trust-store-file.description=Changes to this configuration attribute take effect the next time that the trust manager is accessed.
+property.trust-store-file.syntax.string.pattern.synopsis=An absolute path or a path that is relative to the OpenDS Directory Server instance root.
+property.trust-store-pin.synopsis=Specifies the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-type.synopsis=Specifies the format for the data in the trust store file.
+property.trust-store-type.description=Valid values always include 'JKS' and 'PKCS12', but different implementations can allow other values as well. If no value is provided, then the JVM default value is used. Changes to this configuration attribute take effect the next time that the trust manager is accessed.
+property.trust-store-type.syntax.string.pattern.synopsis=Any key store format supported by the Java runtime environment. The "JKS" and "PKCS12" formats are typically available in Java environments.
diff --git a/opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_fr.properties b/opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_fr.properties
new file mode 100644
index 0000000..6ab8533
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_fr.properties
@@ -0,0 +1,20 @@
+user-friendly-name=File Based Trust Manager Provider
+user-friendly-plural-name=File Based Trust Manager Providers
+synopsis=The file-based trust manager provider determines whether to trust a presented certificate based on whether that certificate exists in a server trust store file.
+description=The trust store file can be in either JKS (the default Java key store format) or PKCS#12 (a standard certificate format) form.
+property.enabled.synopsis=Indicate whether the File Based Trust Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Trust Manager Provider implementation.
+property.trust-store-file.synopsis=Specifies the path to the file containing the trust information. It can be an absolute path or a path that is relative to the OpenDS Directory Server instance root.
+property.trust-store-file.description=Changes to this configuration attribute take effect the next time that the trust manager is accessed.
+property.trust-store-file.syntax.string.pattern.synopsis=An absolute path or a path that is relative to the OpenDS Directory Server instance root.
+property.trust-store-pin.synopsis=Specifies the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-type.synopsis=Specifies the format for the data in the trust store file.
+property.trust-store-type.description=Valid values always include 'JKS' and 'PKCS12', but different implementations can allow other values as well. If no value is provided, then the JVM default value is used. Changes to this configuration attribute take effect the next time that the trust manager is accessed.
+property.trust-store-type.syntax.string.pattern.synopsis=Any key store format supported by the Java runtime environment. The "JKS" and "PKCS12" formats are typically available in Java environments.
diff --git a/opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_ja.properties b/opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_ja.properties
new file mode 100644
index 0000000..6ab8533
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_ja.properties
@@ -0,0 +1,20 @@
+user-friendly-name=File Based Trust Manager Provider
+user-friendly-plural-name=File Based Trust Manager Providers
+synopsis=The file-based trust manager provider determines whether to trust a presented certificate based on whether that certificate exists in a server trust store file.
+description=The trust store file can be in either JKS (the default Java key store format) or PKCS#12 (a standard certificate format) form.
+property.enabled.synopsis=Indicate whether the File Based Trust Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Trust Manager Provider implementation.
+property.trust-store-file.synopsis=Specifies the path to the file containing the trust information. It can be an absolute path or a path that is relative to the OpenDS Directory Server instance root.
+property.trust-store-file.description=Changes to this configuration attribute take effect the next time that the trust manager is accessed.
+property.trust-store-file.syntax.string.pattern.synopsis=An absolute path or a path that is relative to the OpenDS Directory Server instance root.
+property.trust-store-pin.synopsis=Specifies the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-type.synopsis=Specifies the format for the data in the trust store file.
+property.trust-store-type.description=Valid values always include 'JKS' and 'PKCS12', but different implementations can allow other values as well. If no value is provided, then the JVM default value is used. Changes to this configuration attribute take effect the next time that the trust manager is accessed.
+property.trust-store-type.syntax.string.pattern.synopsis=Any key store format supported by the Java runtime environment. The "JKS" and "PKCS12" formats are typically available in Java environments.
diff --git a/opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_ko.properties b/opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_ko.properties
new file mode 100644
index 0000000..6ab8533
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_ko.properties
@@ -0,0 +1,20 @@
+user-friendly-name=File Based Trust Manager Provider
+user-friendly-plural-name=File Based Trust Manager Providers
+synopsis=The file-based trust manager provider determines whether to trust a presented certificate based on whether that certificate exists in a server trust store file.
+description=The trust store file can be in either JKS (the default Java key store format) or PKCS#12 (a standard certificate format) form.
+property.enabled.synopsis=Indicate whether the File Based Trust Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Trust Manager Provider implementation.
+property.trust-store-file.synopsis=Specifies the path to the file containing the trust information. It can be an absolute path or a path that is relative to the OpenDS Directory Server instance root.
+property.trust-store-file.description=Changes to this configuration attribute take effect the next time that the trust manager is accessed.
+property.trust-store-file.syntax.string.pattern.synopsis=An absolute path or a path that is relative to the OpenDS Directory Server instance root.
+property.trust-store-pin.synopsis=Specifies the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-type.synopsis=Specifies the format for the data in the trust store file.
+property.trust-store-type.description=Valid values always include 'JKS' and 'PKCS12', but different implementations can allow other values as well. If no value is provided, then the JVM default value is used. Changes to this configuration attribute take effect the next time that the trust manager is accessed.
+property.trust-store-type.syntax.string.pattern.synopsis=Any key store format supported by the Java runtime environment. The "JKS" and "PKCS12" formats are typically available in Java environments.
diff --git a/opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_zh_CN.properties b/opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..6ab8533
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_zh_CN.properties
@@ -0,0 +1,20 @@
+user-friendly-name=File Based Trust Manager Provider
+user-friendly-plural-name=File Based Trust Manager Providers
+synopsis=The file-based trust manager provider determines whether to trust a presented certificate based on whether that certificate exists in a server trust store file.
+description=The trust store file can be in either JKS (the default Java key store format) or PKCS#12 (a standard certificate format) form.
+property.enabled.synopsis=Indicate whether the File Based Trust Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Trust Manager Provider implementation.
+property.trust-store-file.synopsis=Specifies the path to the file containing the trust information. It can be an absolute path or a path that is relative to the OpenDS Directory Server instance root.
+property.trust-store-file.description=Changes to this configuration attribute take effect the next time that the trust manager is accessed.
+property.trust-store-file.syntax.string.pattern.synopsis=An absolute path or a path that is relative to the OpenDS Directory Server instance root.
+property.trust-store-pin.synopsis=Specifies the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-type.synopsis=Specifies the format for the data in the trust store file.
+property.trust-store-type.description=Valid values always include 'JKS' and 'PKCS12', but different implementations can allow other values as well. If no value is provided, then the JVM default value is used. Changes to this configuration attribute take effect the next time that the trust manager is accessed.
+property.trust-store-type.syntax.string.pattern.synopsis=Any key store format supported by the Java runtime environment. The "JKS" and "PKCS12" formats are typically available in Java environments.
diff --git a/opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_zh_TW.properties b/opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..6ab8533
--- /dev/null
+++ b/opends/src/admin/messages/FileBasedTrustManagerProviderCfgDefn_zh_TW.properties
@@ -0,0 +1,20 @@
+user-friendly-name=File Based Trust Manager Provider
+user-friendly-plural-name=File Based Trust Manager Providers
+synopsis=The file-based trust manager provider determines whether to trust a presented certificate based on whether that certificate exists in a server trust store file.
+description=The trust store file can be in either JKS (the default Java key store format) or PKCS#12 (a standard certificate format) form.
+property.enabled.synopsis=Indicate whether the File Based Trust Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the File Based Trust Manager Provider implementation.
+property.trust-store-file.synopsis=Specifies the path to the file containing the trust information. It can be an absolute path or a path that is relative to the OpenDS Directory Server instance root.
+property.trust-store-file.description=Changes to this configuration attribute take effect the next time that the trust manager is accessed.
+property.trust-store-file.syntax.string.pattern.synopsis=An absolute path or a path that is relative to the OpenDS Directory Server instance root.
+property.trust-store-pin.synopsis=Specifies the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the File Based Trust Manager Provider .
+property.trust-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the File Based Trust Manager Provider is accessed.
+property.trust-store-type.synopsis=Specifies the format for the data in the trust store file.
+property.trust-store-type.description=Valid values always include 'JKS' and 'PKCS12', but different implementations can allow other values as well. If no value is provided, then the JVM default value is used. Changes to this configuration attribute take effect the next time that the trust manager is accessed.
+property.trust-store-type.syntax.string.pattern.synopsis=Any key store format supported by the Java runtime environment. The "JKS" and "PKCS12" formats are typically available in Java environments.
diff --git a/opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn.properties b/opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn.properties
new file mode 100644
index 0000000..8e95df5
--- /dev/null
+++ b/opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn.properties
@@ -0,0 +1,5 @@
+user-friendly-name=File Count Log Retention Policy
+user-friendly-plural-name=File Count Log Retention Policies
+synopsis=Retention policy based on the number of rotated log files on disk.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the File Count Log Retention Policy implementation.
+property.number-of-files.synopsis=Specifies the number of archived log files to retain before the oldest ones are cleaned.
diff --git a/opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_de.properties b/opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_de.properties
new file mode 100644
index 0000000..8e95df5
--- /dev/null
+++ b/opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_de.properties
@@ -0,0 +1,5 @@
+user-friendly-name=File Count Log Retention Policy
+user-friendly-plural-name=File Count Log Retention Policies
+synopsis=Retention policy based on the number of rotated log files on disk.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the File Count Log Retention Policy implementation.
+property.number-of-files.synopsis=Specifies the number of archived log files to retain before the oldest ones are cleaned.
diff --git a/opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_es.properties b/opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_es.properties
new file mode 100644
index 0000000..8e95df5
--- /dev/null
+++ b/opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_es.properties
@@ -0,0 +1,5 @@
+user-friendly-name=File Count Log Retention Policy
+user-friendly-plural-name=File Count Log Retention Policies
+synopsis=Retention policy based on the number of rotated log files on disk.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the File Count Log Retention Policy implementation.
+property.number-of-files.synopsis=Specifies the number of archived log files to retain before the oldest ones are cleaned.
diff --git a/opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_fr.properties b/opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_fr.properties
new file mode 100644
index 0000000..8e95df5
--- /dev/null
+++ b/opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_fr.properties
@@ -0,0 +1,5 @@
+user-friendly-name=File Count Log Retention Policy
+user-friendly-plural-name=File Count Log Retention Policies
+synopsis=Retention policy based on the number of rotated log files on disk.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the File Count Log Retention Policy implementation.
+property.number-of-files.synopsis=Specifies the number of archived log files to retain before the oldest ones are cleaned.
diff --git a/opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_ja.properties b/opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_ja.properties
new file mode 100644
index 0000000..8e95df5
--- /dev/null
+++ b/opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_ja.properties
@@ -0,0 +1,5 @@
+user-friendly-name=File Count Log Retention Policy
+user-friendly-plural-name=File Count Log Retention Policies
+synopsis=Retention policy based on the number of rotated log files on disk.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the File Count Log Retention Policy implementation.
+property.number-of-files.synopsis=Specifies the number of archived log files to retain before the oldest ones are cleaned.
diff --git a/opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_ko.properties b/opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_ko.properties
new file mode 100644
index 0000000..8e95df5
--- /dev/null
+++ b/opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_ko.properties
@@ -0,0 +1,5 @@
+user-friendly-name=File Count Log Retention Policy
+user-friendly-plural-name=File Count Log Retention Policies
+synopsis=Retention policy based on the number of rotated log files on disk.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the File Count Log Retention Policy implementation.
+property.number-of-files.synopsis=Specifies the number of archived log files to retain before the oldest ones are cleaned.
diff --git a/opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_zh_CN.properties b/opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..8e95df5
--- /dev/null
+++ b/opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_zh_CN.properties
@@ -0,0 +1,5 @@
+user-friendly-name=File Count Log Retention Policy
+user-friendly-plural-name=File Count Log Retention Policies
+synopsis=Retention policy based on the number of rotated log files on disk.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the File Count Log Retention Policy implementation.
+property.number-of-files.synopsis=Specifies the number of archived log files to retain before the oldest ones are cleaned.
diff --git a/opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_zh_TW.properties b/opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..8e95df5
--- /dev/null
+++ b/opends/src/admin/messages/FileCountLogRetentionPolicyCfgDefn_zh_TW.properties
@@ -0,0 +1,5 @@
+user-friendly-name=File Count Log Retention Policy
+user-friendly-plural-name=File Count Log Retention Policies
+synopsis=Retention policy based on the number of rotated log files on disk.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the File Count Log Retention Policy implementation.
+property.number-of-files.synopsis=Specifies the number of archived log files to retain before the oldest ones are cleaned.
diff --git a/opends/src/admin/messages/FileSystemEntryCacheCfgDefn.properties b/opends/src/admin/messages/FileSystemEntryCacheCfgDefn.properties
new file mode 100644
index 0000000..20b0e6e
--- /dev/null
+++ b/opends/src/admin/messages/FileSystemEntryCacheCfgDefn.properties
@@ -0,0 +1,24 @@
+user-friendly-name=File System Entry Cache
+user-friendly-plural-name=File System Entry Caches
+synopsis=The File System Entry Cache is an entry cache implementation which uses a JE database to keep track of the entries.
+description=For best performance, the JE database should reside in a memory based file system although any file system will do for this cache to function. Entries are maintained either by FIFO (default) or LRU-based (configurable) list implementation. Cache sizing is based on the size of free space available in the file system, such that if enough memory is free, then adding an entry to the cache will not require purging. If more than the specified size of the file system available space is already consumed, then one or more entries need to be removed in order to make room for a new entry. It is also possible to configure a maximum number of entries for the cache. If this is specified, then the number of entries are not allowed to exceed this value, but it may not be possible to hold this many entries if the available memory fills up first. Other configurable parameters for this cache include the maximum length of time to block while waiting to acquire a lock, and a set of filters that may be used to define criteria for determining which entries are stored in the cache. If a set of filters are provided then an entry must match at least one of them in order to be stored in the cache. JE environment cache size can also be configured either as a percentage of the free memory available in the JVM, or as an absolute size in bytes. This cache has a persistence property which, if enabled, allows for the contents of the cache to persist across server or cache restarts.
+property.cache-directory.synopsis=Specifies the directory in which the JE environment should store the cache.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.cache-type.synopsis=Specifies the policy which should be used for purging entries from the cache.
+property.cache-type.syntax.enumeration.value.fifo.synopsis=FIFO based entry cache.
+property.cache-type.syntax.enumeration.value.lru.synopsis=LRU based entry cache.
+property.compact-encoding.synopsis=Indicates whether the cache should use a compact form when encoding cache entries by compressing the attribute descriptions and object class sets.
+property.compact-encoding.description=Note that compression does not preserve user-supplied capitalization in the object class and attribute type names.
+property.compact-encoding.requires-admin-action.synopsis=Changing this property only affects the encoding of the cache entries put in the cache after the change is made. It will not be retroactively applied to existing cache entries.
+property.db-cache-percent.synopsis=Specifies the maximum memory usage for the internal JE cache as a percentage of the total JVM memory.
+property.db-cache-size.synopsis=Specifies the maximum JVM memory usage in bytes for the internal JE cache.
+property.enabled.synopsis=Indicates whether the File System Entry Cache is enabled.
+property.exclude-filter.synopsis=The set of filters that define the entries that should be excluded from the cache.
+property.include-filter.synopsis=The set of filters that define the entries that should be included in the cache.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the File System Entry Cache implementation.
+property.je-property.synopsis=Specifies the environment properties for the Berkeley DB Java Edition database providing the backend for this entry cache.
+property.je-property.description=Any Berkeley DB Java Edition property can be specified using the following form: property-name=property-value. Refer to the OpenDS documentation for further information on related properties, their implications and range values. The definitive identification of all the property parameters available in the example.properties file in the Berkeley DB Java Edition distribution.
+property.lock-timeout.synopsis=The length of time to wait while attempting to acquire a read or write lock.
+property.max-entries.synopsis=The maximum number of entries allowed in the cache.
+property.max-memory-size.synopsis=The maximum size of the entry cache in bytes.
+property.persistent-cache.synopsis=Specifies whether the cache should persist across restarts.
diff --git a/opends/src/admin/messages/FileSystemEntryCacheCfgDefn_de.properties b/opends/src/admin/messages/FileSystemEntryCacheCfgDefn_de.properties
new file mode 100644
index 0000000..20b0e6e
--- /dev/null
+++ b/opends/src/admin/messages/FileSystemEntryCacheCfgDefn_de.properties
@@ -0,0 +1,24 @@
+user-friendly-name=File System Entry Cache
+user-friendly-plural-name=File System Entry Caches
+synopsis=The File System Entry Cache is an entry cache implementation which uses a JE database to keep track of the entries.
+description=For best performance, the JE database should reside in a memory based file system although any file system will do for this cache to function. Entries are maintained either by FIFO (default) or LRU-based (configurable) list implementation. Cache sizing is based on the size of free space available in the file system, such that if enough memory is free, then adding an entry to the cache will not require purging. If more than the specified size of the file system available space is already consumed, then one or more entries need to be removed in order to make room for a new entry. It is also possible to configure a maximum number of entries for the cache. If this is specified, then the number of entries are not allowed to exceed this value, but it may not be possible to hold this many entries if the available memory fills up first. Other configurable parameters for this cache include the maximum length of time to block while waiting to acquire a lock, and a set of filters that may be used to define criteria for determining which entries are stored in the cache. If a set of filters are provided then an entry must match at least one of them in order to be stored in the cache. JE environment cache size can also be configured either as a percentage of the free memory available in the JVM, or as an absolute size in bytes. This cache has a persistence property which, if enabled, allows for the contents of the cache to persist across server or cache restarts.
+property.cache-directory.synopsis=Specifies the directory in which the JE environment should store the cache.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.cache-type.synopsis=Specifies the policy which should be used for purging entries from the cache.
+property.cache-type.syntax.enumeration.value.fifo.synopsis=FIFO based entry cache.
+property.cache-type.syntax.enumeration.value.lru.synopsis=LRU based entry cache.
+property.compact-encoding.synopsis=Indicates whether the cache should use a compact form when encoding cache entries by compressing the attribute descriptions and object class sets.
+property.compact-encoding.description=Note that compression does not preserve user-supplied capitalization in the object class and attribute type names.
+property.compact-encoding.requires-admin-action.synopsis=Changing this property only affects the encoding of the cache entries put in the cache after the change is made. It will not be retroactively applied to existing cache entries.
+property.db-cache-percent.synopsis=Specifies the maximum memory usage for the internal JE cache as a percentage of the total JVM memory.
+property.db-cache-size.synopsis=Specifies the maximum JVM memory usage in bytes for the internal JE cache.
+property.enabled.synopsis=Indicates whether the File System Entry Cache is enabled.
+property.exclude-filter.synopsis=The set of filters that define the entries that should be excluded from the cache.
+property.include-filter.synopsis=The set of filters that define the entries that should be included in the cache.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the File System Entry Cache implementation.
+property.je-property.synopsis=Specifies the environment properties for the Berkeley DB Java Edition database providing the backend for this entry cache.
+property.je-property.description=Any Berkeley DB Java Edition property can be specified using the following form: property-name=property-value. Refer to the OpenDS documentation for further information on related properties, their implications and range values. The definitive identification of all the property parameters available in the example.properties file in the Berkeley DB Java Edition distribution.
+property.lock-timeout.synopsis=The length of time to wait while attempting to acquire a read or write lock.
+property.max-entries.synopsis=The maximum number of entries allowed in the cache.
+property.max-memory-size.synopsis=The maximum size of the entry cache in bytes.
+property.persistent-cache.synopsis=Specifies whether the cache should persist across restarts.
diff --git a/opends/src/admin/messages/FileSystemEntryCacheCfgDefn_es.properties b/opends/src/admin/messages/FileSystemEntryCacheCfgDefn_es.properties
new file mode 100644
index 0000000..20b0e6e
--- /dev/null
+++ b/opends/src/admin/messages/FileSystemEntryCacheCfgDefn_es.properties
@@ -0,0 +1,24 @@
+user-friendly-name=File System Entry Cache
+user-friendly-plural-name=File System Entry Caches
+synopsis=The File System Entry Cache is an entry cache implementation which uses a JE database to keep track of the entries.
+description=For best performance, the JE database should reside in a memory based file system although any file system will do for this cache to function. Entries are maintained either by FIFO (default) or LRU-based (configurable) list implementation. Cache sizing is based on the size of free space available in the file system, such that if enough memory is free, then adding an entry to the cache will not require purging. If more than the specified size of the file system available space is already consumed, then one or more entries need to be removed in order to make room for a new entry. It is also possible to configure a maximum number of entries for the cache. If this is specified, then the number of entries are not allowed to exceed this value, but it may not be possible to hold this many entries if the available memory fills up first. Other configurable parameters for this cache include the maximum length of time to block while waiting to acquire a lock, and a set of filters that may be used to define criteria for determining which entries are stored in the cache. If a set of filters are provided then an entry must match at least one of them in order to be stored in the cache. JE environment cache size can also be configured either as a percentage of the free memory available in the JVM, or as an absolute size in bytes. This cache has a persistence property which, if enabled, allows for the contents of the cache to persist across server or cache restarts.
+property.cache-directory.synopsis=Specifies the directory in which the JE environment should store the cache.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.cache-type.synopsis=Specifies the policy which should be used for purging entries from the cache.
+property.cache-type.syntax.enumeration.value.fifo.synopsis=FIFO based entry cache.
+property.cache-type.syntax.enumeration.value.lru.synopsis=LRU based entry cache.
+property.compact-encoding.synopsis=Indicates whether the cache should use a compact form when encoding cache entries by compressing the attribute descriptions and object class sets.
+property.compact-encoding.description=Note that compression does not preserve user-supplied capitalization in the object class and attribute type names.
+property.compact-encoding.requires-admin-action.synopsis=Changing this property only affects the encoding of the cache entries put in the cache after the change is made. It will not be retroactively applied to existing cache entries.
+property.db-cache-percent.synopsis=Specifies the maximum memory usage for the internal JE cache as a percentage of the total JVM memory.
+property.db-cache-size.synopsis=Specifies the maximum JVM memory usage in bytes for the internal JE cache.
+property.enabled.synopsis=Indicates whether the File System Entry Cache is enabled.
+property.exclude-filter.synopsis=The set of filters that define the entries that should be excluded from the cache.
+property.include-filter.synopsis=The set of filters that define the entries that should be included in the cache.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the File System Entry Cache implementation.
+property.je-property.synopsis=Specifies the environment properties for the Berkeley DB Java Edition database providing the backend for this entry cache.
+property.je-property.description=Any Berkeley DB Java Edition property can be specified using the following form: property-name=property-value. Refer to the OpenDS documentation for further information on related properties, their implications and range values. The definitive identification of all the property parameters available in the example.properties file in the Berkeley DB Java Edition distribution.
+property.lock-timeout.synopsis=The length of time to wait while attempting to acquire a read or write lock.
+property.max-entries.synopsis=The maximum number of entries allowed in the cache.
+property.max-memory-size.synopsis=The maximum size of the entry cache in bytes.
+property.persistent-cache.synopsis=Specifies whether the cache should persist across restarts.
diff --git a/opends/src/admin/messages/FileSystemEntryCacheCfgDefn_fr.properties b/opends/src/admin/messages/FileSystemEntryCacheCfgDefn_fr.properties
new file mode 100644
index 0000000..20b0e6e
--- /dev/null
+++ b/opends/src/admin/messages/FileSystemEntryCacheCfgDefn_fr.properties
@@ -0,0 +1,24 @@
+user-friendly-name=File System Entry Cache
+user-friendly-plural-name=File System Entry Caches
+synopsis=The File System Entry Cache is an entry cache implementation which uses a JE database to keep track of the entries.
+description=For best performance, the JE database should reside in a memory based file system although any file system will do for this cache to function. Entries are maintained either by FIFO (default) or LRU-based (configurable) list implementation. Cache sizing is based on the size of free space available in the file system, such that if enough memory is free, then adding an entry to the cache will not require purging. If more than the specified size of the file system available space is already consumed, then one or more entries need to be removed in order to make room for a new entry. It is also possible to configure a maximum number of entries for the cache. If this is specified, then the number of entries are not allowed to exceed this value, but it may not be possible to hold this many entries if the available memory fills up first. Other configurable parameters for this cache include the maximum length of time to block while waiting to acquire a lock, and a set of filters that may be used to define criteria for determining which entries are stored in the cache. If a set of filters are provided then an entry must match at least one of them in order to be stored in the cache. JE environment cache size can also be configured either as a percentage of the free memory available in the JVM, or as an absolute size in bytes. This cache has a persistence property which, if enabled, allows for the contents of the cache to persist across server or cache restarts.
+property.cache-directory.synopsis=Specifies the directory in which the JE environment should store the cache.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.cache-type.synopsis=Specifies the policy which should be used for purging entries from the cache.
+property.cache-type.syntax.enumeration.value.fifo.synopsis=FIFO based entry cache.
+property.cache-type.syntax.enumeration.value.lru.synopsis=LRU based entry cache.
+property.compact-encoding.synopsis=Indicates whether the cache should use a compact form when encoding cache entries by compressing the attribute descriptions and object class sets.
+property.compact-encoding.description=Note that compression does not preserve user-supplied capitalization in the object class and attribute type names.
+property.compact-encoding.requires-admin-action.synopsis=Changing this property only affects the encoding of the cache entries put in the cache after the change is made. It will not be retroactively applied to existing cache entries.
+property.db-cache-percent.synopsis=Specifies the maximum memory usage for the internal JE cache as a percentage of the total JVM memory.
+property.db-cache-size.synopsis=Specifies the maximum JVM memory usage in bytes for the internal JE cache.
+property.enabled.synopsis=Indicates whether the File System Entry Cache is enabled.
+property.exclude-filter.synopsis=The set of filters that define the entries that should be excluded from the cache.
+property.include-filter.synopsis=The set of filters that define the entries that should be included in the cache.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the File System Entry Cache implementation.
+property.je-property.synopsis=Specifies the environment properties for the Berkeley DB Java Edition database providing the backend for this entry cache.
+property.je-property.description=Any Berkeley DB Java Edition property can be specified using the following form: property-name=property-value. Refer to the OpenDS documentation for further information on related properties, their implications and range values. The definitive identification of all the property parameters available in the example.properties file in the Berkeley DB Java Edition distribution.
+property.lock-timeout.synopsis=The length of time to wait while attempting to acquire a read or write lock.
+property.max-entries.synopsis=The maximum number of entries allowed in the cache.
+property.max-memory-size.synopsis=The maximum size of the entry cache in bytes.
+property.persistent-cache.synopsis=Specifies whether the cache should persist across restarts.
diff --git a/opends/src/admin/messages/FileSystemEntryCacheCfgDefn_ja.properties b/opends/src/admin/messages/FileSystemEntryCacheCfgDefn_ja.properties
new file mode 100644
index 0000000..20b0e6e
--- /dev/null
+++ b/opends/src/admin/messages/FileSystemEntryCacheCfgDefn_ja.properties
@@ -0,0 +1,24 @@
+user-friendly-name=File System Entry Cache
+user-friendly-plural-name=File System Entry Caches
+synopsis=The File System Entry Cache is an entry cache implementation which uses a JE database to keep track of the entries.
+description=For best performance, the JE database should reside in a memory based file system although any file system will do for this cache to function. Entries are maintained either by FIFO (default) or LRU-based (configurable) list implementation. Cache sizing is based on the size of free space available in the file system, such that if enough memory is free, then adding an entry to the cache will not require purging. If more than the specified size of the file system available space is already consumed, then one or more entries need to be removed in order to make room for a new entry. It is also possible to configure a maximum number of entries for the cache. If this is specified, then the number of entries are not allowed to exceed this value, but it may not be possible to hold this many entries if the available memory fills up first. Other configurable parameters for this cache include the maximum length of time to block while waiting to acquire a lock, and a set of filters that may be used to define criteria for determining which entries are stored in the cache. If a set of filters are provided then an entry must match at least one of them in order to be stored in the cache. JE environment cache size can also be configured either as a percentage of the free memory available in the JVM, or as an absolute size in bytes. This cache has a persistence property which, if enabled, allows for the contents of the cache to persist across server or cache restarts.
+property.cache-directory.synopsis=Specifies the directory in which the JE environment should store the cache.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.cache-type.synopsis=Specifies the policy which should be used for purging entries from the cache.
+property.cache-type.syntax.enumeration.value.fifo.synopsis=FIFO based entry cache.
+property.cache-type.syntax.enumeration.value.lru.synopsis=LRU based entry cache.
+property.compact-encoding.synopsis=Indicates whether the cache should use a compact form when encoding cache entries by compressing the attribute descriptions and object class sets.
+property.compact-encoding.description=Note that compression does not preserve user-supplied capitalization in the object class and attribute type names.
+property.compact-encoding.requires-admin-action.synopsis=Changing this property only affects the encoding of the cache entries put in the cache after the change is made. It will not be retroactively applied to existing cache entries.
+property.db-cache-percent.synopsis=Specifies the maximum memory usage for the internal JE cache as a percentage of the total JVM memory.
+property.db-cache-size.synopsis=Specifies the maximum JVM memory usage in bytes for the internal JE cache.
+property.enabled.synopsis=Indicates whether the File System Entry Cache is enabled.
+property.exclude-filter.synopsis=The set of filters that define the entries that should be excluded from the cache.
+property.include-filter.synopsis=The set of filters that define the entries that should be included in the cache.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the File System Entry Cache implementation.
+property.je-property.synopsis=Specifies the environment properties for the Berkeley DB Java Edition database providing the backend for this entry cache.
+property.je-property.description=Any Berkeley DB Java Edition property can be specified using the following form: property-name=property-value. Refer to the OpenDS documentation for further information on related properties, their implications and range values. The definitive identification of all the property parameters available in the example.properties file in the Berkeley DB Java Edition distribution.
+property.lock-timeout.synopsis=The length of time to wait while attempting to acquire a read or write lock.
+property.max-entries.synopsis=The maximum number of entries allowed in the cache.
+property.max-memory-size.synopsis=The maximum size of the entry cache in bytes.
+property.persistent-cache.synopsis=Specifies whether the cache should persist across restarts.
diff --git a/opends/src/admin/messages/FileSystemEntryCacheCfgDefn_ko.properties b/opends/src/admin/messages/FileSystemEntryCacheCfgDefn_ko.properties
new file mode 100644
index 0000000..20b0e6e
--- /dev/null
+++ b/opends/src/admin/messages/FileSystemEntryCacheCfgDefn_ko.properties
@@ -0,0 +1,24 @@
+user-friendly-name=File System Entry Cache
+user-friendly-plural-name=File System Entry Caches
+synopsis=The File System Entry Cache is an entry cache implementation which uses a JE database to keep track of the entries.
+description=For best performance, the JE database should reside in a memory based file system although any file system will do for this cache to function. Entries are maintained either by FIFO (default) or LRU-based (configurable) list implementation. Cache sizing is based on the size of free space available in the file system, such that if enough memory is free, then adding an entry to the cache will not require purging. If more than the specified size of the file system available space is already consumed, then one or more entries need to be removed in order to make room for a new entry. It is also possible to configure a maximum number of entries for the cache. If this is specified, then the number of entries are not allowed to exceed this value, but it may not be possible to hold this many entries if the available memory fills up first. Other configurable parameters for this cache include the maximum length of time to block while waiting to acquire a lock, and a set of filters that may be used to define criteria for determining which entries are stored in the cache. If a set of filters are provided then an entry must match at least one of them in order to be stored in the cache. JE environment cache size can also be configured either as a percentage of the free memory available in the JVM, or as an absolute size in bytes. This cache has a persistence property which, if enabled, allows for the contents of the cache to persist across server or cache restarts.
+property.cache-directory.synopsis=Specifies the directory in which the JE environment should store the cache.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.cache-type.synopsis=Specifies the policy which should be used for purging entries from the cache.
+property.cache-type.syntax.enumeration.value.fifo.synopsis=FIFO based entry cache.
+property.cache-type.syntax.enumeration.value.lru.synopsis=LRU based entry cache.
+property.compact-encoding.synopsis=Indicates whether the cache should use a compact form when encoding cache entries by compressing the attribute descriptions and object class sets.
+property.compact-encoding.description=Note that compression does not preserve user-supplied capitalization in the object class and attribute type names.
+property.compact-encoding.requires-admin-action.synopsis=Changing this property only affects the encoding of the cache entries put in the cache after the change is made. It will not be retroactively applied to existing cache entries.
+property.db-cache-percent.synopsis=Specifies the maximum memory usage for the internal JE cache as a percentage of the total JVM memory.
+property.db-cache-size.synopsis=Specifies the maximum JVM memory usage in bytes for the internal JE cache.
+property.enabled.synopsis=Indicates whether the File System Entry Cache is enabled.
+property.exclude-filter.synopsis=The set of filters that define the entries that should be excluded from the cache.
+property.include-filter.synopsis=The set of filters that define the entries that should be included in the cache.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the File System Entry Cache implementation.
+property.je-property.synopsis=Specifies the environment properties for the Berkeley DB Java Edition database providing the backend for this entry cache.
+property.je-property.description=Any Berkeley DB Java Edition property can be specified using the following form: property-name=property-value. Refer to the OpenDS documentation for further information on related properties, their implications and range values. The definitive identification of all the property parameters available in the example.properties file in the Berkeley DB Java Edition distribution.
+property.lock-timeout.synopsis=The length of time to wait while attempting to acquire a read or write lock.
+property.max-entries.synopsis=The maximum number of entries allowed in the cache.
+property.max-memory-size.synopsis=The maximum size of the entry cache in bytes.
+property.persistent-cache.synopsis=Specifies whether the cache should persist across restarts.
diff --git a/opends/src/admin/messages/FileSystemEntryCacheCfgDefn_zh_CN.properties b/opends/src/admin/messages/FileSystemEntryCacheCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..20b0e6e
--- /dev/null
+++ b/opends/src/admin/messages/FileSystemEntryCacheCfgDefn_zh_CN.properties
@@ -0,0 +1,24 @@
+user-friendly-name=File System Entry Cache
+user-friendly-plural-name=File System Entry Caches
+synopsis=The File System Entry Cache is an entry cache implementation which uses a JE database to keep track of the entries.
+description=For best performance, the JE database should reside in a memory based file system although any file system will do for this cache to function. Entries are maintained either by FIFO (default) or LRU-based (configurable) list implementation. Cache sizing is based on the size of free space available in the file system, such that if enough memory is free, then adding an entry to the cache will not require purging. If more than the specified size of the file system available space is already consumed, then one or more entries need to be removed in order to make room for a new entry. It is also possible to configure a maximum number of entries for the cache. If this is specified, then the number of entries are not allowed to exceed this value, but it may not be possible to hold this many entries if the available memory fills up first. Other configurable parameters for this cache include the maximum length of time to block while waiting to acquire a lock, and a set of filters that may be used to define criteria for determining which entries are stored in the cache. If a set of filters are provided then an entry must match at least one of them in order to be stored in the cache. JE environment cache size can also be configured either as a percentage of the free memory available in the JVM, or as an absolute size in bytes. This cache has a persistence property which, if enabled, allows for the contents of the cache to persist across server or cache restarts.
+property.cache-directory.synopsis=Specifies the directory in which the JE environment should store the cache.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.cache-type.synopsis=Specifies the policy which should be used for purging entries from the cache.
+property.cache-type.syntax.enumeration.value.fifo.synopsis=FIFO based entry cache.
+property.cache-type.syntax.enumeration.value.lru.synopsis=LRU based entry cache.
+property.compact-encoding.synopsis=Indicates whether the cache should use a compact form when encoding cache entries by compressing the attribute descriptions and object class sets.
+property.compact-encoding.description=Note that compression does not preserve user-supplied capitalization in the object class and attribute type names.
+property.compact-encoding.requires-admin-action.synopsis=Changing this property only affects the encoding of the cache entries put in the cache after the change is made. It will not be retroactively applied to existing cache entries.
+property.db-cache-percent.synopsis=Specifies the maximum memory usage for the internal JE cache as a percentage of the total JVM memory.
+property.db-cache-size.synopsis=Specifies the maximum JVM memory usage in bytes for the internal JE cache.
+property.enabled.synopsis=Indicates whether the File System Entry Cache is enabled.
+property.exclude-filter.synopsis=The set of filters that define the entries that should be excluded from the cache.
+property.include-filter.synopsis=The set of filters that define the entries that should be included in the cache.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the File System Entry Cache implementation.
+property.je-property.synopsis=Specifies the environment properties for the Berkeley DB Java Edition database providing the backend for this entry cache.
+property.je-property.description=Any Berkeley DB Java Edition property can be specified using the following form: property-name=property-value. Refer to the OpenDS documentation for further information on related properties, their implications and range values. The definitive identification of all the property parameters available in the example.properties file in the Berkeley DB Java Edition distribution.
+property.lock-timeout.synopsis=The length of time to wait while attempting to acquire a read or write lock.
+property.max-entries.synopsis=The maximum number of entries allowed in the cache.
+property.max-memory-size.synopsis=The maximum size of the entry cache in bytes.
+property.persistent-cache.synopsis=Specifies whether the cache should persist across restarts.
diff --git a/opends/src/admin/messages/FileSystemEntryCacheCfgDefn_zh_TW.properties b/opends/src/admin/messages/FileSystemEntryCacheCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..20b0e6e
--- /dev/null
+++ b/opends/src/admin/messages/FileSystemEntryCacheCfgDefn_zh_TW.properties
@@ -0,0 +1,24 @@
+user-friendly-name=File System Entry Cache
+user-friendly-plural-name=File System Entry Caches
+synopsis=The File System Entry Cache is an entry cache implementation which uses a JE database to keep track of the entries.
+description=For best performance, the JE database should reside in a memory based file system although any file system will do for this cache to function. Entries are maintained either by FIFO (default) or LRU-based (configurable) list implementation. Cache sizing is based on the size of free space available in the file system, such that if enough memory is free, then adding an entry to the cache will not require purging. If more than the specified size of the file system available space is already consumed, then one or more entries need to be removed in order to make room for a new entry. It is also possible to configure a maximum number of entries for the cache. If this is specified, then the number of entries are not allowed to exceed this value, but it may not be possible to hold this many entries if the available memory fills up first. Other configurable parameters for this cache include the maximum length of time to block while waiting to acquire a lock, and a set of filters that may be used to define criteria for determining which entries are stored in the cache. If a set of filters are provided then an entry must match at least one of them in order to be stored in the cache. JE environment cache size can also be configured either as a percentage of the free memory available in the JVM, or as an absolute size in bytes. This cache has a persistence property which, if enabled, allows for the contents of the cache to persist across server or cache restarts.
+property.cache-directory.synopsis=Specifies the directory in which the JE environment should store the cache.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.cache-type.synopsis=Specifies the policy which should be used for purging entries from the cache.
+property.cache-type.syntax.enumeration.value.fifo.synopsis=FIFO based entry cache.
+property.cache-type.syntax.enumeration.value.lru.synopsis=LRU based entry cache.
+property.compact-encoding.synopsis=Indicates whether the cache should use a compact form when encoding cache entries by compressing the attribute descriptions and object class sets.
+property.compact-encoding.description=Note that compression does not preserve user-supplied capitalization in the object class and attribute type names.
+property.compact-encoding.requires-admin-action.synopsis=Changing this property only affects the encoding of the cache entries put in the cache after the change is made. It will not be retroactively applied to existing cache entries.
+property.db-cache-percent.synopsis=Specifies the maximum memory usage for the internal JE cache as a percentage of the total JVM memory.
+property.db-cache-size.synopsis=Specifies the maximum JVM memory usage in bytes for the internal JE cache.
+property.enabled.synopsis=Indicates whether the File System Entry Cache is enabled.
+property.exclude-filter.synopsis=The set of filters that define the entries that should be excluded from the cache.
+property.include-filter.synopsis=The set of filters that define the entries that should be included in the cache.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the File System Entry Cache implementation.
+property.je-property.synopsis=Specifies the environment properties for the Berkeley DB Java Edition database providing the backend for this entry cache.
+property.je-property.description=Any Berkeley DB Java Edition property can be specified using the following form: property-name=property-value. Refer to the OpenDS documentation for further information on related properties, their implications and range values. The definitive identification of all the property parameters available in the example.properties file in the Berkeley DB Java Edition distribution.
+property.lock-timeout.synopsis=The length of time to wait while attempting to acquire a read or write lock.
+property.max-entries.synopsis=The maximum number of entries allowed in the cache.
+property.max-memory-size.synopsis=The maximum size of the entry cache in bytes.
+property.persistent-cache.synopsis=Specifies whether the cache should persist across restarts.
diff --git a/opends/src/admin/messages/FingerprintCertificateMapperCfgDefn.properties b/opends/src/admin/messages/FingerprintCertificateMapperCfgDefn.properties
new file mode 100644
index 0000000..856e795
--- /dev/null
+++ b/opends/src/admin/messages/FingerprintCertificateMapperCfgDefn.properties
@@ -0,0 +1,13 @@
+user-friendly-name=Fingerprint Certificate Mapper
+user-friendly-plural-name=Fingerprint Certificate Mappers
+synopsis=The Fingerprint Certificate Mapper maps client certificates to user entries by looking for the MD5 or SHA1 fingerprint in a specified attribute of user entries.
+property.enabled.synopsis=Indicates whether the Fingerprint Certificate Mapper is enabled.
+property.fingerprint-algorithm.synopsis=Specifies the name of the digest algorithm to compute the fingerprint of client certificates.
+property.fingerprint-algorithm.syntax.enumeration.value.md5.synopsis=Use the MD5 digest algorithm to compute certificate fingerprints.
+property.fingerprint-algorithm.syntax.enumeration.value.sha1.synopsis=Use the SHA-1 digest algorithm to compute certificate fingerprints.
+property.fingerprint-attribute.synopsis=Specifies the attribute in which to look for the fingerprint.
+property.fingerprint-attribute.description=Values of the fingerprint attribute should exactly match the MD5 or SHA1 representation of the certificate fingerprint.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Fingerprint Certificate Mapper implementation.
+property.user-base-dn.synopsis=Specifies the set of base DNs below which to search for users.
+property.user-base-dn.description=The base DNs are used when performing searches to map the client certificates to a user entry.
+property.user-base-dn.default-behavior.alias.synopsis=The server performs the search in all public naming contexts.
diff --git a/opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_de.properties b/opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_de.properties
new file mode 100644
index 0000000..856e795
--- /dev/null
+++ b/opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_de.properties
@@ -0,0 +1,13 @@
+user-friendly-name=Fingerprint Certificate Mapper
+user-friendly-plural-name=Fingerprint Certificate Mappers
+synopsis=The Fingerprint Certificate Mapper maps client certificates to user entries by looking for the MD5 or SHA1 fingerprint in a specified attribute of user entries.
+property.enabled.synopsis=Indicates whether the Fingerprint Certificate Mapper is enabled.
+property.fingerprint-algorithm.synopsis=Specifies the name of the digest algorithm to compute the fingerprint of client certificates.
+property.fingerprint-algorithm.syntax.enumeration.value.md5.synopsis=Use the MD5 digest algorithm to compute certificate fingerprints.
+property.fingerprint-algorithm.syntax.enumeration.value.sha1.synopsis=Use the SHA-1 digest algorithm to compute certificate fingerprints.
+property.fingerprint-attribute.synopsis=Specifies the attribute in which to look for the fingerprint.
+property.fingerprint-attribute.description=Values of the fingerprint attribute should exactly match the MD5 or SHA1 representation of the certificate fingerprint.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Fingerprint Certificate Mapper implementation.
+property.user-base-dn.synopsis=Specifies the set of base DNs below which to search for users.
+property.user-base-dn.description=The base DNs are used when performing searches to map the client certificates to a user entry.
+property.user-base-dn.default-behavior.alias.synopsis=The server performs the search in all public naming contexts.
diff --git a/opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_es.properties b/opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_es.properties
new file mode 100644
index 0000000..856e795
--- /dev/null
+++ b/opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_es.properties
@@ -0,0 +1,13 @@
+user-friendly-name=Fingerprint Certificate Mapper
+user-friendly-plural-name=Fingerprint Certificate Mappers
+synopsis=The Fingerprint Certificate Mapper maps client certificates to user entries by looking for the MD5 or SHA1 fingerprint in a specified attribute of user entries.
+property.enabled.synopsis=Indicates whether the Fingerprint Certificate Mapper is enabled.
+property.fingerprint-algorithm.synopsis=Specifies the name of the digest algorithm to compute the fingerprint of client certificates.
+property.fingerprint-algorithm.syntax.enumeration.value.md5.synopsis=Use the MD5 digest algorithm to compute certificate fingerprints.
+property.fingerprint-algorithm.syntax.enumeration.value.sha1.synopsis=Use the SHA-1 digest algorithm to compute certificate fingerprints.
+property.fingerprint-attribute.synopsis=Specifies the attribute in which to look for the fingerprint.
+property.fingerprint-attribute.description=Values of the fingerprint attribute should exactly match the MD5 or SHA1 representation of the certificate fingerprint.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Fingerprint Certificate Mapper implementation.
+property.user-base-dn.synopsis=Specifies the set of base DNs below which to search for users.
+property.user-base-dn.description=The base DNs are used when performing searches to map the client certificates to a user entry.
+property.user-base-dn.default-behavior.alias.synopsis=The server performs the search in all public naming contexts.
diff --git a/opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_fr.properties b/opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_fr.properties
new file mode 100644
index 0000000..856e795
--- /dev/null
+++ b/opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_fr.properties
@@ -0,0 +1,13 @@
+user-friendly-name=Fingerprint Certificate Mapper
+user-friendly-plural-name=Fingerprint Certificate Mappers
+synopsis=The Fingerprint Certificate Mapper maps client certificates to user entries by looking for the MD5 or SHA1 fingerprint in a specified attribute of user entries.
+property.enabled.synopsis=Indicates whether the Fingerprint Certificate Mapper is enabled.
+property.fingerprint-algorithm.synopsis=Specifies the name of the digest algorithm to compute the fingerprint of client certificates.
+property.fingerprint-algorithm.syntax.enumeration.value.md5.synopsis=Use the MD5 digest algorithm to compute certificate fingerprints.
+property.fingerprint-algorithm.syntax.enumeration.value.sha1.synopsis=Use the SHA-1 digest algorithm to compute certificate fingerprints.
+property.fingerprint-attribute.synopsis=Specifies the attribute in which to look for the fingerprint.
+property.fingerprint-attribute.description=Values of the fingerprint attribute should exactly match the MD5 or SHA1 representation of the certificate fingerprint.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Fingerprint Certificate Mapper implementation.
+property.user-base-dn.synopsis=Specifies the set of base DNs below which to search for users.
+property.user-base-dn.description=The base DNs are used when performing searches to map the client certificates to a user entry.
+property.user-base-dn.default-behavior.alias.synopsis=The server performs the search in all public naming contexts.
diff --git a/opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_ja.properties b/opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_ja.properties
new file mode 100644
index 0000000..856e795
--- /dev/null
+++ b/opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_ja.properties
@@ -0,0 +1,13 @@
+user-friendly-name=Fingerprint Certificate Mapper
+user-friendly-plural-name=Fingerprint Certificate Mappers
+synopsis=The Fingerprint Certificate Mapper maps client certificates to user entries by looking for the MD5 or SHA1 fingerprint in a specified attribute of user entries.
+property.enabled.synopsis=Indicates whether the Fingerprint Certificate Mapper is enabled.
+property.fingerprint-algorithm.synopsis=Specifies the name of the digest algorithm to compute the fingerprint of client certificates.
+property.fingerprint-algorithm.syntax.enumeration.value.md5.synopsis=Use the MD5 digest algorithm to compute certificate fingerprints.
+property.fingerprint-algorithm.syntax.enumeration.value.sha1.synopsis=Use the SHA-1 digest algorithm to compute certificate fingerprints.
+property.fingerprint-attribute.synopsis=Specifies the attribute in which to look for the fingerprint.
+property.fingerprint-attribute.description=Values of the fingerprint attribute should exactly match the MD5 or SHA1 representation of the certificate fingerprint.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Fingerprint Certificate Mapper implementation.
+property.user-base-dn.synopsis=Specifies the set of base DNs below which to search for users.
+property.user-base-dn.description=The base DNs are used when performing searches to map the client certificates to a user entry.
+property.user-base-dn.default-behavior.alias.synopsis=The server performs the search in all public naming contexts.
diff --git a/opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_ko.properties b/opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_ko.properties
new file mode 100644
index 0000000..856e795
--- /dev/null
+++ b/opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_ko.properties
@@ -0,0 +1,13 @@
+user-friendly-name=Fingerprint Certificate Mapper
+user-friendly-plural-name=Fingerprint Certificate Mappers
+synopsis=The Fingerprint Certificate Mapper maps client certificates to user entries by looking for the MD5 or SHA1 fingerprint in a specified attribute of user entries.
+property.enabled.synopsis=Indicates whether the Fingerprint Certificate Mapper is enabled.
+property.fingerprint-algorithm.synopsis=Specifies the name of the digest algorithm to compute the fingerprint of client certificates.
+property.fingerprint-algorithm.syntax.enumeration.value.md5.synopsis=Use the MD5 digest algorithm to compute certificate fingerprints.
+property.fingerprint-algorithm.syntax.enumeration.value.sha1.synopsis=Use the SHA-1 digest algorithm to compute certificate fingerprints.
+property.fingerprint-attribute.synopsis=Specifies the attribute in which to look for the fingerprint.
+property.fingerprint-attribute.description=Values of the fingerprint attribute should exactly match the MD5 or SHA1 representation of the certificate fingerprint.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Fingerprint Certificate Mapper implementation.
+property.user-base-dn.synopsis=Specifies the set of base DNs below which to search for users.
+property.user-base-dn.description=The base DNs are used when performing searches to map the client certificates to a user entry.
+property.user-base-dn.default-behavior.alias.synopsis=The server performs the search in all public naming contexts.
diff --git a/opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_zh_CN.properties b/opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..856e795
--- /dev/null
+++ b/opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_zh_CN.properties
@@ -0,0 +1,13 @@
+user-friendly-name=Fingerprint Certificate Mapper
+user-friendly-plural-name=Fingerprint Certificate Mappers
+synopsis=The Fingerprint Certificate Mapper maps client certificates to user entries by looking for the MD5 or SHA1 fingerprint in a specified attribute of user entries.
+property.enabled.synopsis=Indicates whether the Fingerprint Certificate Mapper is enabled.
+property.fingerprint-algorithm.synopsis=Specifies the name of the digest algorithm to compute the fingerprint of client certificates.
+property.fingerprint-algorithm.syntax.enumeration.value.md5.synopsis=Use the MD5 digest algorithm to compute certificate fingerprints.
+property.fingerprint-algorithm.syntax.enumeration.value.sha1.synopsis=Use the SHA-1 digest algorithm to compute certificate fingerprints.
+property.fingerprint-attribute.synopsis=Specifies the attribute in which to look for the fingerprint.
+property.fingerprint-attribute.description=Values of the fingerprint attribute should exactly match the MD5 or SHA1 representation of the certificate fingerprint.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Fingerprint Certificate Mapper implementation.
+property.user-base-dn.synopsis=Specifies the set of base DNs below which to search for users.
+property.user-base-dn.description=The base DNs are used when performing searches to map the client certificates to a user entry.
+property.user-base-dn.default-behavior.alias.synopsis=The server performs the search in all public naming contexts.
diff --git a/opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_zh_TW.properties b/opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..856e795
--- /dev/null
+++ b/opends/src/admin/messages/FingerprintCertificateMapperCfgDefn_zh_TW.properties
@@ -0,0 +1,13 @@
+user-friendly-name=Fingerprint Certificate Mapper
+user-friendly-plural-name=Fingerprint Certificate Mappers
+synopsis=The Fingerprint Certificate Mapper maps client certificates to user entries by looking for the MD5 or SHA1 fingerprint in a specified attribute of user entries.
+property.enabled.synopsis=Indicates whether the Fingerprint Certificate Mapper is enabled.
+property.fingerprint-algorithm.synopsis=Specifies the name of the digest algorithm to compute the fingerprint of client certificates.
+property.fingerprint-algorithm.syntax.enumeration.value.md5.synopsis=Use the MD5 digest algorithm to compute certificate fingerprints.
+property.fingerprint-algorithm.syntax.enumeration.value.sha1.synopsis=Use the SHA-1 digest algorithm to compute certificate fingerprints.
+property.fingerprint-attribute.synopsis=Specifies the attribute in which to look for the fingerprint.
+property.fingerprint-attribute.description=Values of the fingerprint attribute should exactly match the MD5 or SHA1 representation of the certificate fingerprint.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Fingerprint Certificate Mapper implementation.
+property.user-base-dn.synopsis=Specifies the set of base DNs below which to search for users.
+property.user-base-dn.description=The base DNs are used when performing searches to map the client certificates to a user entry.
+property.user-base-dn.default-behavior.alias.synopsis=The server performs the search in all public naming contexts.
diff --git a/opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn.properties b/opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn.properties
new file mode 100644
index 0000000..14443f7
--- /dev/null
+++ b/opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Fixed Time Log Rotation Policy
+user-friendly-plural-name=Fixed Time Log Rotation Policies
+synopsis=Rotation policy based on a fixed time of day.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Fixed Time Log Rotation Policy implementation.
+property.time-of-day.synopsis=Specifies the time of day at which log rotation should occur.
+property.time-of-day.syntax.string.pattern.synopsis=24 hour time of day in HHmm format.
diff --git a/opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_de.properties b/opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_de.properties
new file mode 100644
index 0000000..14443f7
--- /dev/null
+++ b/opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Fixed Time Log Rotation Policy
+user-friendly-plural-name=Fixed Time Log Rotation Policies
+synopsis=Rotation policy based on a fixed time of day.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Fixed Time Log Rotation Policy implementation.
+property.time-of-day.synopsis=Specifies the time of day at which log rotation should occur.
+property.time-of-day.syntax.string.pattern.synopsis=24 hour time of day in HHmm format.
diff --git a/opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_es.properties b/opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_es.properties
new file mode 100644
index 0000000..14443f7
--- /dev/null
+++ b/opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Fixed Time Log Rotation Policy
+user-friendly-plural-name=Fixed Time Log Rotation Policies
+synopsis=Rotation policy based on a fixed time of day.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Fixed Time Log Rotation Policy implementation.
+property.time-of-day.synopsis=Specifies the time of day at which log rotation should occur.
+property.time-of-day.syntax.string.pattern.synopsis=24 hour time of day in HHmm format.
diff --git a/opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_fr.properties b/opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_fr.properties
new file mode 100644
index 0000000..14443f7
--- /dev/null
+++ b/opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Fixed Time Log Rotation Policy
+user-friendly-plural-name=Fixed Time Log Rotation Policies
+synopsis=Rotation policy based on a fixed time of day.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Fixed Time Log Rotation Policy implementation.
+property.time-of-day.synopsis=Specifies the time of day at which log rotation should occur.
+property.time-of-day.syntax.string.pattern.synopsis=24 hour time of day in HHmm format.
diff --git a/opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_ja.properties b/opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_ja.properties
new file mode 100644
index 0000000..14443f7
--- /dev/null
+++ b/opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Fixed Time Log Rotation Policy
+user-friendly-plural-name=Fixed Time Log Rotation Policies
+synopsis=Rotation policy based on a fixed time of day.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Fixed Time Log Rotation Policy implementation.
+property.time-of-day.synopsis=Specifies the time of day at which log rotation should occur.
+property.time-of-day.syntax.string.pattern.synopsis=24 hour time of day in HHmm format.
diff --git a/opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_ko.properties b/opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_ko.properties
new file mode 100644
index 0000000..14443f7
--- /dev/null
+++ b/opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Fixed Time Log Rotation Policy
+user-friendly-plural-name=Fixed Time Log Rotation Policies
+synopsis=Rotation policy based on a fixed time of day.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Fixed Time Log Rotation Policy implementation.
+property.time-of-day.synopsis=Specifies the time of day at which log rotation should occur.
+property.time-of-day.syntax.string.pattern.synopsis=24 hour time of day in HHmm format.
diff --git a/opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_zh_CN.properties b/opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..14443f7
--- /dev/null
+++ b/opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Fixed Time Log Rotation Policy
+user-friendly-plural-name=Fixed Time Log Rotation Policies
+synopsis=Rotation policy based on a fixed time of day.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Fixed Time Log Rotation Policy implementation.
+property.time-of-day.synopsis=Specifies the time of day at which log rotation should occur.
+property.time-of-day.syntax.string.pattern.synopsis=24 hour time of day in HHmm format.
diff --git a/opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_zh_TW.properties b/opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..14443f7
--- /dev/null
+++ b/opends/src/admin/messages/FixedTimeLogRotationPolicyCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Fixed Time Log Rotation Policy
+user-friendly-plural-name=Fixed Time Log Rotation Policies
+synopsis=Rotation policy based on a fixed time of day.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Fixed Time Log Rotation Policy implementation.
+property.time-of-day.synopsis=Specifies the time of day at which log rotation should occur.
+property.time-of-day.syntax.string.pattern.synopsis=24 hour time of day in HHmm format.
diff --git a/opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn.properties b/opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn.properties
new file mode 100644
index 0000000..bdd4540
--- /dev/null
+++ b/opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Free Disk Space Log Retention Policy
+user-friendly-plural-name=Free Disk Space Log Retention Policies
+synopsis=Retention policy based on the free disk space available.
+description=This policy is only available on Java 6.
+property.free-disk-space.synopsis=Specifies the minimum amount of free disk space that should be available on the file system on which the archived log files are stored.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Free Disk Space Log Retention Policy implementation.
diff --git a/opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_de.properties b/opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_de.properties
new file mode 100644
index 0000000..bdd4540
--- /dev/null
+++ b/opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Free Disk Space Log Retention Policy
+user-friendly-plural-name=Free Disk Space Log Retention Policies
+synopsis=Retention policy based on the free disk space available.
+description=This policy is only available on Java 6.
+property.free-disk-space.synopsis=Specifies the minimum amount of free disk space that should be available on the file system on which the archived log files are stored.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Free Disk Space Log Retention Policy implementation.
diff --git a/opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_es.properties b/opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_es.properties
new file mode 100644
index 0000000..bdd4540
--- /dev/null
+++ b/opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Free Disk Space Log Retention Policy
+user-friendly-plural-name=Free Disk Space Log Retention Policies
+synopsis=Retention policy based on the free disk space available.
+description=This policy is only available on Java 6.
+property.free-disk-space.synopsis=Specifies the minimum amount of free disk space that should be available on the file system on which the archived log files are stored.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Free Disk Space Log Retention Policy implementation.
diff --git a/opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_fr.properties b/opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_fr.properties
new file mode 100644
index 0000000..bdd4540
--- /dev/null
+++ b/opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Free Disk Space Log Retention Policy
+user-friendly-plural-name=Free Disk Space Log Retention Policies
+synopsis=Retention policy based on the free disk space available.
+description=This policy is only available on Java 6.
+property.free-disk-space.synopsis=Specifies the minimum amount of free disk space that should be available on the file system on which the archived log files are stored.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Free Disk Space Log Retention Policy implementation.
diff --git a/opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_ja.properties b/opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_ja.properties
new file mode 100644
index 0000000..bdd4540
--- /dev/null
+++ b/opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Free Disk Space Log Retention Policy
+user-friendly-plural-name=Free Disk Space Log Retention Policies
+synopsis=Retention policy based on the free disk space available.
+description=This policy is only available on Java 6.
+property.free-disk-space.synopsis=Specifies the minimum amount of free disk space that should be available on the file system on which the archived log files are stored.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Free Disk Space Log Retention Policy implementation.
diff --git a/opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_ko.properties b/opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_ko.properties
new file mode 100644
index 0000000..bdd4540
--- /dev/null
+++ b/opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Free Disk Space Log Retention Policy
+user-friendly-plural-name=Free Disk Space Log Retention Policies
+synopsis=Retention policy based on the free disk space available.
+description=This policy is only available on Java 6.
+property.free-disk-space.synopsis=Specifies the minimum amount of free disk space that should be available on the file system on which the archived log files are stored.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Free Disk Space Log Retention Policy implementation.
diff --git a/opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_zh_CN.properties b/opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..bdd4540
--- /dev/null
+++ b/opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Free Disk Space Log Retention Policy
+user-friendly-plural-name=Free Disk Space Log Retention Policies
+synopsis=Retention policy based on the free disk space available.
+description=This policy is only available on Java 6.
+property.free-disk-space.synopsis=Specifies the minimum amount of free disk space that should be available on the file system on which the archived log files are stored.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Free Disk Space Log Retention Policy implementation.
diff --git a/opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_zh_TW.properties b/opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..bdd4540
--- /dev/null
+++ b/opends/src/admin/messages/FreeDiskSpaceLogRetentionPolicyCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Free Disk Space Log Retention Policy
+user-friendly-plural-name=Free Disk Space Log Retention Policies
+synopsis=Retention policy based on the free disk space available.
+description=This policy is only available on Java 6.
+property.free-disk-space.synopsis=Specifies the minimum amount of free disk space that should be available on the file system on which the archived log files are stored.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Free Disk Space Log Retention Policy implementation.
diff --git a/opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn.properties b/opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn.properties
new file mode 100644
index 0000000..3727475
--- /dev/null
+++ b/opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn.properties
@@ -0,0 +1,25 @@
+user-friendly-name=GSSAPI SASL Mechanism Handler
+user-friendly-plural-name=GSSAPI SASL Mechanism Handlers
+synopsis=The GSSAPI SASL mechanism performs all processing related to SASL GSSAPI authentication using Kerberos V5.
+description=The GSSAPI SASL mechanism provides the ability for clients to authenticate themselves to the server using existing authentication in a Kerberos environment. This mechanism provides the ability to achieve single sign-on for Kerberos-based clients.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that is to be used with this SASL mechanism handler to match the Kerberos principal included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the GSSAPI SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
+property.kdc-address.synopsis=Specifies the address of the KDC that is to be used for Kerberos processing.
+property.kdc-address.description=If provided, this property must be a fully-qualified DNS-resolvable name. If this property is not provided, then the server attempts to determine it from the system-wide Kerberos configuration.
+property.kdc-address.default-behavior.alias.synopsis=The server attempts to determine the KDC address from the underlying system configuration.
+property.keytab.synopsis=Specifies the path to the keytab file that should be used for Kerberos processing.
+property.keytab.description=If provided, this is either an absolute path or one that is relative to the server instance root.
+property.keytab.default-behavior.alias.synopsis=The server attempts to use the system-wide default keytab.
+property.principal-name.synopsis=Specifies the principal name.
+property.principal-name.description=It can either be a simple user name or a service name such as host/example.com. If this property is not provided, then the server attempts to build the principal name by appending the fully qualified domain name to the string "ldap/".
+property.principal-name.default-behavior.alias.synopsis=The server attempts to determine the principal name from the underlying system configuration.
+property.quality-of-protection.synopsis=The name of a property that specifies the quality of protection the server will support.
+property.quality-of-protection.syntax.enumeration.value.confidentiality.synopsis=Quality of protection equals authentication with integrity and confidentiality protection.
+property.quality-of-protection.syntax.enumeration.value.integrity.synopsis=Quality of protection equals authentication with integrity protection.
+property.quality-of-protection.syntax.enumeration.value.none.synopsis=QOP equals authentication only.
+property.realm.synopsis=Specifies the realm to be used for GSSAPI authentication.
+property.realm.default-behavior.alias.synopsis=The server attempts to determine the realm from the underlying system configuration.
+property.server-fqdn.synopsis=Specifies the DNS-resolvable fully-qualified domain name for the system.
+property.server-fqdn.default-behavior.alias.synopsis=The server attempts to determine the fully-qualified domain name dynamically .
diff --git a/opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_de.properties b/opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..3727475
--- /dev/null
+++ b/opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_de.properties
@@ -0,0 +1,25 @@
+user-friendly-name=GSSAPI SASL Mechanism Handler
+user-friendly-plural-name=GSSAPI SASL Mechanism Handlers
+synopsis=The GSSAPI SASL mechanism performs all processing related to SASL GSSAPI authentication using Kerberos V5.
+description=The GSSAPI SASL mechanism provides the ability for clients to authenticate themselves to the server using existing authentication in a Kerberos environment. This mechanism provides the ability to achieve single sign-on for Kerberos-based clients.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that is to be used with this SASL mechanism handler to match the Kerberos principal included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the GSSAPI SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
+property.kdc-address.synopsis=Specifies the address of the KDC that is to be used for Kerberos processing.
+property.kdc-address.description=If provided, this property must be a fully-qualified DNS-resolvable name. If this property is not provided, then the server attempts to determine it from the system-wide Kerberos configuration.
+property.kdc-address.default-behavior.alias.synopsis=The server attempts to determine the KDC address from the underlying system configuration.
+property.keytab.synopsis=Specifies the path to the keytab file that should be used for Kerberos processing.
+property.keytab.description=If provided, this is either an absolute path or one that is relative to the server instance root.
+property.keytab.default-behavior.alias.synopsis=The server attempts to use the system-wide default keytab.
+property.principal-name.synopsis=Specifies the principal name.
+property.principal-name.description=It can either be a simple user name or a service name such as host/example.com. If this property is not provided, then the server attempts to build the principal name by appending the fully qualified domain name to the string "ldap/".
+property.principal-name.default-behavior.alias.synopsis=The server attempts to determine the principal name from the underlying system configuration.
+property.quality-of-protection.synopsis=The name of a property that specifies the quality of protection the server will support.
+property.quality-of-protection.syntax.enumeration.value.confidentiality.synopsis=Quality of protection equals authentication with integrity and confidentiality protection.
+property.quality-of-protection.syntax.enumeration.value.integrity.synopsis=Quality of protection equals authentication with integrity protection.
+property.quality-of-protection.syntax.enumeration.value.none.synopsis=QOP equals authentication only.
+property.realm.synopsis=Specifies the realm to be used for GSSAPI authentication.
+property.realm.default-behavior.alias.synopsis=The server attempts to determine the realm from the underlying system configuration.
+property.server-fqdn.synopsis=Specifies the DNS-resolvable fully-qualified domain name for the system.
+property.server-fqdn.default-behavior.alias.synopsis=The server attempts to determine the fully-qualified domain name dynamically .
diff --git a/opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_es.properties b/opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..3727475
--- /dev/null
+++ b/opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_es.properties
@@ -0,0 +1,25 @@
+user-friendly-name=GSSAPI SASL Mechanism Handler
+user-friendly-plural-name=GSSAPI SASL Mechanism Handlers
+synopsis=The GSSAPI SASL mechanism performs all processing related to SASL GSSAPI authentication using Kerberos V5.
+description=The GSSAPI SASL mechanism provides the ability for clients to authenticate themselves to the server using existing authentication in a Kerberos environment. This mechanism provides the ability to achieve single sign-on for Kerberos-based clients.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that is to be used with this SASL mechanism handler to match the Kerberos principal included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the GSSAPI SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
+property.kdc-address.synopsis=Specifies the address of the KDC that is to be used for Kerberos processing.
+property.kdc-address.description=If provided, this property must be a fully-qualified DNS-resolvable name. If this property is not provided, then the server attempts to determine it from the system-wide Kerberos configuration.
+property.kdc-address.default-behavior.alias.synopsis=The server attempts to determine the KDC address from the underlying system configuration.
+property.keytab.synopsis=Specifies the path to the keytab file that should be used for Kerberos processing.
+property.keytab.description=If provided, this is either an absolute path or one that is relative to the server instance root.
+property.keytab.default-behavior.alias.synopsis=The server attempts to use the system-wide default keytab.
+property.principal-name.synopsis=Specifies the principal name.
+property.principal-name.description=It can either be a simple user name or a service name such as host/example.com. If this property is not provided, then the server attempts to build the principal name by appending the fully qualified domain name to the string "ldap/".
+property.principal-name.default-behavior.alias.synopsis=The server attempts to determine the principal name from the underlying system configuration.
+property.quality-of-protection.synopsis=The name of a property that specifies the quality of protection the server will support.
+property.quality-of-protection.syntax.enumeration.value.confidentiality.synopsis=Quality of protection equals authentication with integrity and confidentiality protection.
+property.quality-of-protection.syntax.enumeration.value.integrity.synopsis=Quality of protection equals authentication with integrity protection.
+property.quality-of-protection.syntax.enumeration.value.none.synopsis=QOP equals authentication only.
+property.realm.synopsis=Specifies the realm to be used for GSSAPI authentication.
+property.realm.default-behavior.alias.synopsis=The server attempts to determine the realm from the underlying system configuration.
+property.server-fqdn.synopsis=Specifies the DNS-resolvable fully-qualified domain name for the system.
+property.server-fqdn.default-behavior.alias.synopsis=The server attempts to determine the fully-qualified domain name dynamically .
diff --git a/opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_fr.properties b/opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..3727475
--- /dev/null
+++ b/opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_fr.properties
@@ -0,0 +1,25 @@
+user-friendly-name=GSSAPI SASL Mechanism Handler
+user-friendly-plural-name=GSSAPI SASL Mechanism Handlers
+synopsis=The GSSAPI SASL mechanism performs all processing related to SASL GSSAPI authentication using Kerberos V5.
+description=The GSSAPI SASL mechanism provides the ability for clients to authenticate themselves to the server using existing authentication in a Kerberos environment. This mechanism provides the ability to achieve single sign-on for Kerberos-based clients.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that is to be used with this SASL mechanism handler to match the Kerberos principal included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the GSSAPI SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
+property.kdc-address.synopsis=Specifies the address of the KDC that is to be used for Kerberos processing.
+property.kdc-address.description=If provided, this property must be a fully-qualified DNS-resolvable name. If this property is not provided, then the server attempts to determine it from the system-wide Kerberos configuration.
+property.kdc-address.default-behavior.alias.synopsis=The server attempts to determine the KDC address from the underlying system configuration.
+property.keytab.synopsis=Specifies the path to the keytab file that should be used for Kerberos processing.
+property.keytab.description=If provided, this is either an absolute path or one that is relative to the server instance root.
+property.keytab.default-behavior.alias.synopsis=The server attempts to use the system-wide default keytab.
+property.principal-name.synopsis=Specifies the principal name.
+property.principal-name.description=It can either be a simple user name or a service name such as host/example.com. If this property is not provided, then the server attempts to build the principal name by appending the fully qualified domain name to the string "ldap/".
+property.principal-name.default-behavior.alias.synopsis=The server attempts to determine the principal name from the underlying system configuration.
+property.quality-of-protection.synopsis=The name of a property that specifies the quality of protection the server will support.
+property.quality-of-protection.syntax.enumeration.value.confidentiality.synopsis=Quality of protection equals authentication with integrity and confidentiality protection.
+property.quality-of-protection.syntax.enumeration.value.integrity.synopsis=Quality of protection equals authentication with integrity protection.
+property.quality-of-protection.syntax.enumeration.value.none.synopsis=QOP equals authentication only.
+property.realm.synopsis=Specifies the realm to be used for GSSAPI authentication.
+property.realm.default-behavior.alias.synopsis=The server attempts to determine the realm from the underlying system configuration.
+property.server-fqdn.synopsis=Specifies the DNS-resolvable fully-qualified domain name for the system.
+property.server-fqdn.default-behavior.alias.synopsis=The server attempts to determine the fully-qualified domain name dynamically .
diff --git a/opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_ja.properties b/opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..3727475
--- /dev/null
+++ b/opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_ja.properties
@@ -0,0 +1,25 @@
+user-friendly-name=GSSAPI SASL Mechanism Handler
+user-friendly-plural-name=GSSAPI SASL Mechanism Handlers
+synopsis=The GSSAPI SASL mechanism performs all processing related to SASL GSSAPI authentication using Kerberos V5.
+description=The GSSAPI SASL mechanism provides the ability for clients to authenticate themselves to the server using existing authentication in a Kerberos environment. This mechanism provides the ability to achieve single sign-on for Kerberos-based clients.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that is to be used with this SASL mechanism handler to match the Kerberos principal included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the GSSAPI SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
+property.kdc-address.synopsis=Specifies the address of the KDC that is to be used for Kerberos processing.
+property.kdc-address.description=If provided, this property must be a fully-qualified DNS-resolvable name. If this property is not provided, then the server attempts to determine it from the system-wide Kerberos configuration.
+property.kdc-address.default-behavior.alias.synopsis=The server attempts to determine the KDC address from the underlying system configuration.
+property.keytab.synopsis=Specifies the path to the keytab file that should be used for Kerberos processing.
+property.keytab.description=If provided, this is either an absolute path or one that is relative to the server instance root.
+property.keytab.default-behavior.alias.synopsis=The server attempts to use the system-wide default keytab.
+property.principal-name.synopsis=Specifies the principal name.
+property.principal-name.description=It can either be a simple user name or a service name such as host/example.com. If this property is not provided, then the server attempts to build the principal name by appending the fully qualified domain name to the string "ldap/".
+property.principal-name.default-behavior.alias.synopsis=The server attempts to determine the principal name from the underlying system configuration.
+property.quality-of-protection.synopsis=The name of a property that specifies the quality of protection the server will support.
+property.quality-of-protection.syntax.enumeration.value.confidentiality.synopsis=Quality of protection equals authentication with integrity and confidentiality protection.
+property.quality-of-protection.syntax.enumeration.value.integrity.synopsis=Quality of protection equals authentication with integrity protection.
+property.quality-of-protection.syntax.enumeration.value.none.synopsis=QOP equals authentication only.
+property.realm.synopsis=Specifies the realm to be used for GSSAPI authentication.
+property.realm.default-behavior.alias.synopsis=The server attempts to determine the realm from the underlying system configuration.
+property.server-fqdn.synopsis=Specifies the DNS-resolvable fully-qualified domain name for the system.
+property.server-fqdn.default-behavior.alias.synopsis=The server attempts to determine the fully-qualified domain name dynamically .
diff --git a/opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_ko.properties b/opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..3727475
--- /dev/null
+++ b/opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_ko.properties
@@ -0,0 +1,25 @@
+user-friendly-name=GSSAPI SASL Mechanism Handler
+user-friendly-plural-name=GSSAPI SASL Mechanism Handlers
+synopsis=The GSSAPI SASL mechanism performs all processing related to SASL GSSAPI authentication using Kerberos V5.
+description=The GSSAPI SASL mechanism provides the ability for clients to authenticate themselves to the server using existing authentication in a Kerberos environment. This mechanism provides the ability to achieve single sign-on for Kerberos-based clients.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that is to be used with this SASL mechanism handler to match the Kerberos principal included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the GSSAPI SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
+property.kdc-address.synopsis=Specifies the address of the KDC that is to be used for Kerberos processing.
+property.kdc-address.description=If provided, this property must be a fully-qualified DNS-resolvable name. If this property is not provided, then the server attempts to determine it from the system-wide Kerberos configuration.
+property.kdc-address.default-behavior.alias.synopsis=The server attempts to determine the KDC address from the underlying system configuration.
+property.keytab.synopsis=Specifies the path to the keytab file that should be used for Kerberos processing.
+property.keytab.description=If provided, this is either an absolute path or one that is relative to the server instance root.
+property.keytab.default-behavior.alias.synopsis=The server attempts to use the system-wide default keytab.
+property.principal-name.synopsis=Specifies the principal name.
+property.principal-name.description=It can either be a simple user name or a service name such as host/example.com. If this property is not provided, then the server attempts to build the principal name by appending the fully qualified domain name to the string "ldap/".
+property.principal-name.default-behavior.alias.synopsis=The server attempts to determine the principal name from the underlying system configuration.
+property.quality-of-protection.synopsis=The name of a property that specifies the quality of protection the server will support.
+property.quality-of-protection.syntax.enumeration.value.confidentiality.synopsis=Quality of protection equals authentication with integrity and confidentiality protection.
+property.quality-of-protection.syntax.enumeration.value.integrity.synopsis=Quality of protection equals authentication with integrity protection.
+property.quality-of-protection.syntax.enumeration.value.none.synopsis=QOP equals authentication only.
+property.realm.synopsis=Specifies the realm to be used for GSSAPI authentication.
+property.realm.default-behavior.alias.synopsis=The server attempts to determine the realm from the underlying system configuration.
+property.server-fqdn.synopsis=Specifies the DNS-resolvable fully-qualified domain name for the system.
+property.server-fqdn.default-behavior.alias.synopsis=The server attempts to determine the fully-qualified domain name dynamically .
diff --git a/opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..3727475
--- /dev/null
+++ b/opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,25 @@
+user-friendly-name=GSSAPI SASL Mechanism Handler
+user-friendly-plural-name=GSSAPI SASL Mechanism Handlers
+synopsis=The GSSAPI SASL mechanism performs all processing related to SASL GSSAPI authentication using Kerberos V5.
+description=The GSSAPI SASL mechanism provides the ability for clients to authenticate themselves to the server using existing authentication in a Kerberos environment. This mechanism provides the ability to achieve single sign-on for Kerberos-based clients.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that is to be used with this SASL mechanism handler to match the Kerberos principal included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the GSSAPI SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
+property.kdc-address.synopsis=Specifies the address of the KDC that is to be used for Kerberos processing.
+property.kdc-address.description=If provided, this property must be a fully-qualified DNS-resolvable name. If this property is not provided, then the server attempts to determine it from the system-wide Kerberos configuration.
+property.kdc-address.default-behavior.alias.synopsis=The server attempts to determine the KDC address from the underlying system configuration.
+property.keytab.synopsis=Specifies the path to the keytab file that should be used for Kerberos processing.
+property.keytab.description=If provided, this is either an absolute path or one that is relative to the server instance root.
+property.keytab.default-behavior.alias.synopsis=The server attempts to use the system-wide default keytab.
+property.principal-name.synopsis=Specifies the principal name.
+property.principal-name.description=It can either be a simple user name or a service name such as host/example.com. If this property is not provided, then the server attempts to build the principal name by appending the fully qualified domain name to the string "ldap/".
+property.principal-name.default-behavior.alias.synopsis=The server attempts to determine the principal name from the underlying system configuration.
+property.quality-of-protection.synopsis=The name of a property that specifies the quality of protection the server will support.
+property.quality-of-protection.syntax.enumeration.value.confidentiality.synopsis=Quality of protection equals authentication with integrity and confidentiality protection.
+property.quality-of-protection.syntax.enumeration.value.integrity.synopsis=Quality of protection equals authentication with integrity protection.
+property.quality-of-protection.syntax.enumeration.value.none.synopsis=QOP equals authentication only.
+property.realm.synopsis=Specifies the realm to be used for GSSAPI authentication.
+property.realm.default-behavior.alias.synopsis=The server attempts to determine the realm from the underlying system configuration.
+property.server-fqdn.synopsis=Specifies the DNS-resolvable fully-qualified domain name for the system.
+property.server-fqdn.default-behavior.alias.synopsis=The server attempts to determine the fully-qualified domain name dynamically .
diff --git a/opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..3727475
--- /dev/null
+++ b/opends/src/admin/messages/GSSAPISASLMechanismHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,25 @@
+user-friendly-name=GSSAPI SASL Mechanism Handler
+user-friendly-plural-name=GSSAPI SASL Mechanism Handlers
+synopsis=The GSSAPI SASL mechanism performs all processing related to SASL GSSAPI authentication using Kerberos V5.
+description=The GSSAPI SASL mechanism provides the ability for clients to authenticate themselves to the server using existing authentication in a Kerberos environment. This mechanism provides the ability to achieve single sign-on for Kerberos-based clients.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that is to be used with this SASL mechanism handler to match the Kerberos principal included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the GSSAPI SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
+property.kdc-address.synopsis=Specifies the address of the KDC that is to be used for Kerberos processing.
+property.kdc-address.description=If provided, this property must be a fully-qualified DNS-resolvable name. If this property is not provided, then the server attempts to determine it from the system-wide Kerberos configuration.
+property.kdc-address.default-behavior.alias.synopsis=The server attempts to determine the KDC address from the underlying system configuration.
+property.keytab.synopsis=Specifies the path to the keytab file that should be used for Kerberos processing.
+property.keytab.description=If provided, this is either an absolute path or one that is relative to the server instance root.
+property.keytab.default-behavior.alias.synopsis=The server attempts to use the system-wide default keytab.
+property.principal-name.synopsis=Specifies the principal name.
+property.principal-name.description=It can either be a simple user name or a service name such as host/example.com. If this property is not provided, then the server attempts to build the principal name by appending the fully qualified domain name to the string "ldap/".
+property.principal-name.default-behavior.alias.synopsis=The server attempts to determine the principal name from the underlying system configuration.
+property.quality-of-protection.synopsis=The name of a property that specifies the quality of protection the server will support.
+property.quality-of-protection.syntax.enumeration.value.confidentiality.synopsis=Quality of protection equals authentication with integrity and confidentiality protection.
+property.quality-of-protection.syntax.enumeration.value.integrity.synopsis=Quality of protection equals authentication with integrity protection.
+property.quality-of-protection.syntax.enumeration.value.none.synopsis=QOP equals authentication only.
+property.realm.synopsis=Specifies the realm to be used for GSSAPI authentication.
+property.realm.default-behavior.alias.synopsis=The server attempts to determine the realm from the underlying system configuration.
+property.server-fqdn.synopsis=Specifies the DNS-resolvable fully-qualified domain name for the system.
+property.server-fqdn.default-behavior.alias.synopsis=The server attempts to determine the fully-qualified domain name dynamically .
diff --git a/opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn.properties b/opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn.properties
new file mode 100644
index 0000000..7924b28
--- /dev/null
+++ b/opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Get Connection Id Extended Operation Handler
+user-friendly-plural-name=Get Connection Id Extended Operation Handlers
+synopsis=The Get Connection Id Extended Operation Handler provides a mechanism for clients to obtain the internal connection ID that the server uses to reference their client connection.
+property.enabled.synopsis=Indicates whether the Get Connection Id Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Get Connection Id Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_de.properties b/opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..7924b28
--- /dev/null
+++ b/opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_de.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Get Connection Id Extended Operation Handler
+user-friendly-plural-name=Get Connection Id Extended Operation Handlers
+synopsis=The Get Connection Id Extended Operation Handler provides a mechanism for clients to obtain the internal connection ID that the server uses to reference their client connection.
+property.enabled.synopsis=Indicates whether the Get Connection Id Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Get Connection Id Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_es.properties b/opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..7924b28
--- /dev/null
+++ b/opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_es.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Get Connection Id Extended Operation Handler
+user-friendly-plural-name=Get Connection Id Extended Operation Handlers
+synopsis=The Get Connection Id Extended Operation Handler provides a mechanism for clients to obtain the internal connection ID that the server uses to reference their client connection.
+property.enabled.synopsis=Indicates whether the Get Connection Id Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Get Connection Id Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_fr.properties b/opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..7924b28
--- /dev/null
+++ b/opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_fr.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Get Connection Id Extended Operation Handler
+user-friendly-plural-name=Get Connection Id Extended Operation Handlers
+synopsis=The Get Connection Id Extended Operation Handler provides a mechanism for clients to obtain the internal connection ID that the server uses to reference their client connection.
+property.enabled.synopsis=Indicates whether the Get Connection Id Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Get Connection Id Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_ja.properties b/opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..7924b28
--- /dev/null
+++ b/opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_ja.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Get Connection Id Extended Operation Handler
+user-friendly-plural-name=Get Connection Id Extended Operation Handlers
+synopsis=The Get Connection Id Extended Operation Handler provides a mechanism for clients to obtain the internal connection ID that the server uses to reference their client connection.
+property.enabled.synopsis=Indicates whether the Get Connection Id Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Get Connection Id Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_ko.properties b/opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..7924b28
--- /dev/null
+++ b/opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_ko.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Get Connection Id Extended Operation Handler
+user-friendly-plural-name=Get Connection Id Extended Operation Handlers
+synopsis=The Get Connection Id Extended Operation Handler provides a mechanism for clients to obtain the internal connection ID that the server uses to reference their client connection.
+property.enabled.synopsis=Indicates whether the Get Connection Id Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Get Connection Id Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..7924b28
--- /dev/null
+++ b/opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Get Connection Id Extended Operation Handler
+user-friendly-plural-name=Get Connection Id Extended Operation Handlers
+synopsis=The Get Connection Id Extended Operation Handler provides a mechanism for clients to obtain the internal connection ID that the server uses to reference their client connection.
+property.enabled.synopsis=Indicates whether the Get Connection Id Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Get Connection Id Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..7924b28
--- /dev/null
+++ b/opends/src/admin/messages/GetConnectionIdExtendedOperationHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Get Connection Id Extended Operation Handler
+user-friendly-plural-name=Get Connection Id Extended Operation Handlers
+synopsis=The Get Connection Id Extended Operation Handler provides a mechanism for clients to obtain the internal connection ID that the server uses to reference their client connection.
+property.enabled.synopsis=Indicates whether the Get Connection Id Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Get Connection Id Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn.properties b/opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn.properties
new file mode 100644
index 0000000..719783d
--- /dev/null
+++ b/opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Get Symmetric Key Extended Operation Handler
+user-friendly-plural-name=Get Symmetric Key Extended Operation Handlers
+synopsis=The Get Symmetric Key Extended Operation Handler is used by the OpenDS cryptographic framework for creating and obtaining symmetric encryption keys.
+property.enabled.synopsis=Indicates whether the Get Symmetric Key Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Get Symmetric Key Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_de.properties b/opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..719783d
--- /dev/null
+++ b/opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_de.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Get Symmetric Key Extended Operation Handler
+user-friendly-plural-name=Get Symmetric Key Extended Operation Handlers
+synopsis=The Get Symmetric Key Extended Operation Handler is used by the OpenDS cryptographic framework for creating and obtaining symmetric encryption keys.
+property.enabled.synopsis=Indicates whether the Get Symmetric Key Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Get Symmetric Key Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_es.properties b/opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..719783d
--- /dev/null
+++ b/opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_es.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Get Symmetric Key Extended Operation Handler
+user-friendly-plural-name=Get Symmetric Key Extended Operation Handlers
+synopsis=The Get Symmetric Key Extended Operation Handler is used by the OpenDS cryptographic framework for creating and obtaining symmetric encryption keys.
+property.enabled.synopsis=Indicates whether the Get Symmetric Key Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Get Symmetric Key Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_fr.properties b/opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..719783d
--- /dev/null
+++ b/opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_fr.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Get Symmetric Key Extended Operation Handler
+user-friendly-plural-name=Get Symmetric Key Extended Operation Handlers
+synopsis=The Get Symmetric Key Extended Operation Handler is used by the OpenDS cryptographic framework for creating and obtaining symmetric encryption keys.
+property.enabled.synopsis=Indicates whether the Get Symmetric Key Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Get Symmetric Key Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_ja.properties b/opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..719783d
--- /dev/null
+++ b/opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_ja.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Get Symmetric Key Extended Operation Handler
+user-friendly-plural-name=Get Symmetric Key Extended Operation Handlers
+synopsis=The Get Symmetric Key Extended Operation Handler is used by the OpenDS cryptographic framework for creating and obtaining symmetric encryption keys.
+property.enabled.synopsis=Indicates whether the Get Symmetric Key Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Get Symmetric Key Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_ko.properties b/opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..719783d
--- /dev/null
+++ b/opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_ko.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Get Symmetric Key Extended Operation Handler
+user-friendly-plural-name=Get Symmetric Key Extended Operation Handlers
+synopsis=The Get Symmetric Key Extended Operation Handler is used by the OpenDS cryptographic framework for creating and obtaining symmetric encryption keys.
+property.enabled.synopsis=Indicates whether the Get Symmetric Key Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Get Symmetric Key Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..719783d
--- /dev/null
+++ b/opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Get Symmetric Key Extended Operation Handler
+user-friendly-plural-name=Get Symmetric Key Extended Operation Handlers
+synopsis=The Get Symmetric Key Extended Operation Handler is used by the OpenDS cryptographic framework for creating and obtaining symmetric encryption keys.
+property.enabled.synopsis=Indicates whether the Get Symmetric Key Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Get Symmetric Key Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..719783d
--- /dev/null
+++ b/opends/src/admin/messages/GetSymmetricKeyExtendedOperationHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Get Symmetric Key Extended Operation Handler
+user-friendly-plural-name=Get Symmetric Key Extended Operation Handlers
+synopsis=The Get Symmetric Key Extended Operation Handler is used by the OpenDS cryptographic framework for creating and obtaining symmetric encryption keys.
+property.enabled.synopsis=Indicates whether the Get Symmetric Key Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Get Symmetric Key Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/GlobalCfgDefn.properties b/opends/src/admin/messages/GlobalCfgDefn.properties
new file mode 100644
index 0000000..5d32c25
--- /dev/null
+++ b/opends/src/admin/messages/GlobalCfgDefn.properties
@@ -0,0 +1,80 @@
+user-friendly-name=Global Configuration
+user-friendly-plural-name=Global Configurations
+synopsis=The Global Configuration contains properties that affect the overall operation of the OpenDS Directory Server .
+property.add-missing-rdn-attributes.synopsis=Indicates whether the Directory Server should automatically add any attribute values contained in the entry's RDN into that entry when processing an add request.
+property.allow-attribute-name-exceptions.synopsis=Indicates whether the Directory Server should allow underscores in attribute names and allow attribute names to begin with numeric digits (both of which are violations of the LDAP standards).
+property.allowed-task.synopsis=Specifies the fully-qualified name of a Java class that may be invoked in the server.
+property.allowed-task.description=Any attempt to invoke a task not included in the list of allowed tasks is rejected.
+property.allowed-task.default-behavior.alias.synopsis=If no values are defined, then the server does not allow any tasks to be invoked.
+property.bind-with-dn-requires-password.synopsis=Indicates whether the Directory Server should reject any simple bind request that contains a DN but no password.
+property.bind-with-dn-requires-password.description=Although such bind requests are technically allowed by the LDAPv3 specification (and should be treated as anonymous simple authentication), they may introduce security problems in applications that do not verify that the client actually provided a password.
+property.check-schema.synopsis=Indicates whether schema enforcement is active.
+property.check-schema.description=When schema enforcement is activated, the Directory Server ensures that all operations result in entries are valid according to the defined server schema. It is strongly recommended that this option be left enabled to prevent the inadvertent addition of invalid data into the server.
+property.default-password-policy.synopsis=Specifies the name of the password policy that is in effect for users whose entries do not specify an alternate password policy (either via a real or virtual attribute).
+property.disabled-privilege.synopsis=Specifies the name of a privilege that should not be evaluated by the server.
+property.disabled-privilege.description=If a privilege is disabled, then it is assumed that all clients (including unauthenticated clients) have that privilege.
+property.disabled-privilege.default-behavior.alias.synopsis=If no values are defined, then the server enforces all privileges.
+property.disabled-privilege.syntax.enumeration.value.backend-backup.synopsis=Allows the user to request that the server process backup tasks.
+property.disabled-privilege.syntax.enumeration.value.backend-restore.synopsis=Allows the user to request that the server process restore tasks.
+property.disabled-privilege.syntax.enumeration.value.bypass-acl.synopsis=Allows the associated user to bypass access control checks performed by the server.
+property.disabled-privilege.syntax.enumeration.value.cancel-request.synopsis=Allows the user to cancel operations in progress on other client connections.
+property.disabled-privilege.syntax.enumeration.value.config-read.synopsis=Allows the associated user to read the server configuration.
+property.disabled-privilege.syntax.enumeration.value.config-write.synopsis=Allows the associated user to update the server configuration. The config-read privilege is also required.
+property.disabled-privilege.syntax.enumeration.value.data-sync.synopsis=Allows the user to participate in data synchronization.
+property.disabled-privilege.syntax.enumeration.value.disconnect-client.synopsis=Allows the user to terminate other client connections.
+property.disabled-privilege.syntax.enumeration.value.jmx-notify.synopsis=Allows the associated user to subscribe to receive JMX notifications.
+property.disabled-privilege.syntax.enumeration.value.jmx-read.synopsis=Allows the associated user to perform JMX read operations.
+property.disabled-privilege.syntax.enumeration.value.jmx-write.synopsis=Allows the associated user to perform JMX write operations.
+property.disabled-privilege.syntax.enumeration.value.ldif-export.synopsis=Allows the user to request that the server process LDIF export tasks.
+property.disabled-privilege.syntax.enumeration.value.ldif-import.synopsis=Allows the user to request that the server process LDIF import tasks.
+property.disabled-privilege.syntax.enumeration.value.modify-acl.synopsis=Allows the associated user to modify the server's access control configuration.
+property.disabled-privilege.syntax.enumeration.value.password-reset.synopsis=Allows the user to reset user passwords.
+property.disabled-privilege.syntax.enumeration.value.privilege-change.synopsis=Allows the user to make changes to the set of defined root privileges, as well as to grant and revoke privileges for users.
+property.disabled-privilege.syntax.enumeration.value.proxied-auth.synopsis=Allows the user to use the proxied authorization control, or to perform a bind that specifies an alternate authorization identity.
+property.disabled-privilege.syntax.enumeration.value.server-restart.synopsis=Allows the user to request that the server perform an in-core restart.
+property.disabled-privilege.syntax.enumeration.value.server-shutdown.synopsis=Allows the user to request that the server shut down.
+property.disabled-privilege.syntax.enumeration.value.unindexed-search.synopsis=Allows the user to request that the server process a search that cannot be optimized using server indexes.
+property.disabled-privilege.syntax.enumeration.value.update-schema.synopsis=Allows the user to make changes to the server schema.
+property.entry-cache-preload.synopsis=Indicates whether or not to preload the entry cache on startup.
+property.etime-resolution.synopsis=Specifies the resolution to use for operation elapsed processing time (etime) measurements.
+property.etime-resolution.syntax.enumeration.value.milliseconds.synopsis=Use millisecond resolution.
+property.etime-resolution.syntax.enumeration.value.nanoseconds.synopsis=Use nanosecond resolution.
+property.idle-time-limit.synopsis=Specifies the maximum length of time that a client connection may remain established since its last completed operation.
+property.idle-time-limit.description=A value of "0 seconds" indicates that no idle time limit is enforced.
+property.invalid-attribute-syntax-behavior.synopsis=Specifies how the Directory Server should handle operations whenever an attribute value violates the associated attribute syntax.
+property.invalid-attribute-syntax-behavior.syntax.enumeration.value.accept.synopsis=The Directory Server silently accepts attribute values that are invalid according to their associated syntax. Matching operations targeting those values may not behave as expected.
+property.invalid-attribute-syntax-behavior.syntax.enumeration.value.reject.synopsis=The Directory Server rejects attribute values that are invalid according to their associated syntax.
+property.invalid-attribute-syntax-behavior.syntax.enumeration.value.warn.synopsis=The Directory Server accepts attribute values that are invalid according to their associated syntax, but also logs a warning message to the error log. Matching operations targeting those values may not behave as expected.
+property.lookthrough-limit.synopsis=Specifies the maximum number of entries that the Directory Server should "look through" in the course of processing a search request.
+property.lookthrough-limit.description=This includes any entry that the server must examine in the course of processing the request, regardless of whether it actually matches the search criteria. A value of 0 indicates that no lookthrough limit is enforced. Note that this is the default server-wide limit, but it may be overridden on a per-user basis using the ds-rlim-lookthrough-limit operational attribute.
+property.max-allowed-client-connections.synopsis=Specifies the maximum number of client connections that may be established at any given time
+property.max-allowed-client-connections.description=A value of 0 indicates that unlimited client connection is allowed.
+property.notify-abandoned-operations.synopsis=Indicates whether the Directory Server should send a response to any operation that is interrupted via an abandon request.
+property.notify-abandoned-operations.description=The LDAP specification states that abandoned operations should not receive any response, but this may cause problems with client applications that always expect to receive a response to each request.
+property.proxied-authorization-identity-mapper.synopsis=Specifies the name of the identity mapper to map authorization ID values (using the "u:" form) provided in the proxied authorization control to the corresponding user entry.
+property.proxied-authorization-identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled.
+property.reject-unauthenticated-requests.synopsis=Indicates whether the Directory Server should reject any request (other than bind or StartTLS requests) received from a client that has not yet been authenticated, whose last authentication attempt was unsuccessful, or whose last authentication attempt used anonymous authentication.
+property.return-bind-error-messages.synopsis=Indicates whether responses for failed bind operations should include a message string providing the reason for the authentication failure.
+property.return-bind-error-messages.description=Note that these messages may include information that could potentially be used by an attacker. If this option is disabled, then these messages appears only in the server's access log.
+property.save-config-on-successful-startup.synopsis=Indicates whether the Directory Server should save a copy of its configuration whenever the startup process completes successfully.
+property.save-config-on-successful-startup.description=This ensures that the server provides a "last known good" configuration, which can be used as a reference (or copied into the active config) if the server fails to start with the current "active" configuration.
+property.server-error-result-code.synopsis=Specifies the numeric value of the result code when request processing fails due to an internal server error.
+property.single-structural-objectclass-behavior.synopsis=Specifies how the Directory Server should handle operations an entry does not contain a structural object class or contains multiple structural classes.
+property.single-structural-objectclass-behavior.syntax.enumeration.value.accept.synopsis=The Directory Server silently accepts entries that do not contain exactly one structural object class. Certain schema features that depend on the entry's structural class may not behave as expected.
+property.single-structural-objectclass-behavior.syntax.enumeration.value.reject.synopsis=The Directory Server rejects entries that do not contain exactly one structural object class.
+property.single-structural-objectclass-behavior.syntax.enumeration.value.warn.synopsis=The Directory Server accepts entries that do not contain exactly one structural object class, but also logs a warning message to the error log. Certain schema features that depend on the entry's structural class may not behave as expected.
+property.size-limit.synopsis=Specifies the maximum number of entries that the Directory Server should return to the client durin a search operation.
+property.size-limit.description=A value of 0 indicates that no size limit is enforced. Note that this is the default server-wide limit, but it may be overridden on a per-user basis using the ds-rlim-size-limit operational attribute.
+property.smtp-server.synopsis=Specifies the address (and optional port number) for a mail server that can be used to send email messages via SMTP.
+property.smtp-server.description=It may be an IP address or resolvable hostname, optionally followed by a colon and a port number.
+property.smtp-server.default-behavior.alias.synopsis=If no values are defined, then the server cannot send email via SMTP.
+property.smtp-server.syntax.string.pattern.synopsis=A hostname, optionally followed by a ":" followed by a port number.
+property.time-limit.synopsis=Specifies the maximum length of time that the Directory Server should spend processing a search operation.
+property.time-limit.description=A value of 0 seconds indicates that no time limit is enforced. Note that this is the default server-wide time limit, but it may be overridden on a per-user basis using the ds-rlim-time-limit operational attribute.
+property.workflow-configuration-mode.synopsis=Specifies the workflow configuration mode (auto vs. manual).
+property.workflow-configuration-mode.syntax.enumeration.value.auto.synopsis=In the "auto" configuration mode, there is no workflow configuration. The workflows are created automatically based on the backend configuration. There is one workflow per backend base DN.
+property.workflow-configuration-mode.syntax.enumeration.value.manual.synopsis=In the "manual" configuration mode, each workflow is created according to its description in the configuration.
+property.writability-mode.synopsis=Specifies the kinds of write operations the Directory Server can process.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=The Directory Server rejects all write operations that are requested of it, regardless of their origin.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=The Directory Server attempts to process all write operations that are requested of it, regardless of their origin.
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=The Directory Server attempts to process write operations requested as internal operations or through synchronization, but rejects any such operations requested from external clients.
diff --git a/opends/src/admin/messages/GlobalCfgDefn_de.properties b/opends/src/admin/messages/GlobalCfgDefn_de.properties
new file mode 100644
index 0000000..5d32c25
--- /dev/null
+++ b/opends/src/admin/messages/GlobalCfgDefn_de.properties
@@ -0,0 +1,80 @@
+user-friendly-name=Global Configuration
+user-friendly-plural-name=Global Configurations
+synopsis=The Global Configuration contains properties that affect the overall operation of the OpenDS Directory Server .
+property.add-missing-rdn-attributes.synopsis=Indicates whether the Directory Server should automatically add any attribute values contained in the entry's RDN into that entry when processing an add request.
+property.allow-attribute-name-exceptions.synopsis=Indicates whether the Directory Server should allow underscores in attribute names and allow attribute names to begin with numeric digits (both of which are violations of the LDAP standards).
+property.allowed-task.synopsis=Specifies the fully-qualified name of a Java class that may be invoked in the server.
+property.allowed-task.description=Any attempt to invoke a task not included in the list of allowed tasks is rejected.
+property.allowed-task.default-behavior.alias.synopsis=If no values are defined, then the server does not allow any tasks to be invoked.
+property.bind-with-dn-requires-password.synopsis=Indicates whether the Directory Server should reject any simple bind request that contains a DN but no password.
+property.bind-with-dn-requires-password.description=Although such bind requests are technically allowed by the LDAPv3 specification (and should be treated as anonymous simple authentication), they may introduce security problems in applications that do not verify that the client actually provided a password.
+property.check-schema.synopsis=Indicates whether schema enforcement is active.
+property.check-schema.description=When schema enforcement is activated, the Directory Server ensures that all operations result in entries are valid according to the defined server schema. It is strongly recommended that this option be left enabled to prevent the inadvertent addition of invalid data into the server.
+property.default-password-policy.synopsis=Specifies the name of the password policy that is in effect for users whose entries do not specify an alternate password policy (either via a real or virtual attribute).
+property.disabled-privilege.synopsis=Specifies the name of a privilege that should not be evaluated by the server.
+property.disabled-privilege.description=If a privilege is disabled, then it is assumed that all clients (including unauthenticated clients) have that privilege.
+property.disabled-privilege.default-behavior.alias.synopsis=If no values are defined, then the server enforces all privileges.
+property.disabled-privilege.syntax.enumeration.value.backend-backup.synopsis=Allows the user to request that the server process backup tasks.
+property.disabled-privilege.syntax.enumeration.value.backend-restore.synopsis=Allows the user to request that the server process restore tasks.
+property.disabled-privilege.syntax.enumeration.value.bypass-acl.synopsis=Allows the associated user to bypass access control checks performed by the server.
+property.disabled-privilege.syntax.enumeration.value.cancel-request.synopsis=Allows the user to cancel operations in progress on other client connections.
+property.disabled-privilege.syntax.enumeration.value.config-read.synopsis=Allows the associated user to read the server configuration.
+property.disabled-privilege.syntax.enumeration.value.config-write.synopsis=Allows the associated user to update the server configuration. The config-read privilege is also required.
+property.disabled-privilege.syntax.enumeration.value.data-sync.synopsis=Allows the user to participate in data synchronization.
+property.disabled-privilege.syntax.enumeration.value.disconnect-client.synopsis=Allows the user to terminate other client connections.
+property.disabled-privilege.syntax.enumeration.value.jmx-notify.synopsis=Allows the associated user to subscribe to receive JMX notifications.
+property.disabled-privilege.syntax.enumeration.value.jmx-read.synopsis=Allows the associated user to perform JMX read operations.
+property.disabled-privilege.syntax.enumeration.value.jmx-write.synopsis=Allows the associated user to perform JMX write operations.
+property.disabled-privilege.syntax.enumeration.value.ldif-export.synopsis=Allows the user to request that the server process LDIF export tasks.
+property.disabled-privilege.syntax.enumeration.value.ldif-import.synopsis=Allows the user to request that the server process LDIF import tasks.
+property.disabled-privilege.syntax.enumeration.value.modify-acl.synopsis=Allows the associated user to modify the server's access control configuration.
+property.disabled-privilege.syntax.enumeration.value.password-reset.synopsis=Allows the user to reset user passwords.
+property.disabled-privilege.syntax.enumeration.value.privilege-change.synopsis=Allows the user to make changes to the set of defined root privileges, as well as to grant and revoke privileges for users.
+property.disabled-privilege.syntax.enumeration.value.proxied-auth.synopsis=Allows the user to use the proxied authorization control, or to perform a bind that specifies an alternate authorization identity.
+property.disabled-privilege.syntax.enumeration.value.server-restart.synopsis=Allows the user to request that the server perform an in-core restart.
+property.disabled-privilege.syntax.enumeration.value.server-shutdown.synopsis=Allows the user to request that the server shut down.
+property.disabled-privilege.syntax.enumeration.value.unindexed-search.synopsis=Allows the user to request that the server process a search that cannot be optimized using server indexes.
+property.disabled-privilege.syntax.enumeration.value.update-schema.synopsis=Allows the user to make changes to the server schema.
+property.entry-cache-preload.synopsis=Indicates whether or not to preload the entry cache on startup.
+property.etime-resolution.synopsis=Specifies the resolution to use for operation elapsed processing time (etime) measurements.
+property.etime-resolution.syntax.enumeration.value.milliseconds.synopsis=Use millisecond resolution.
+property.etime-resolution.syntax.enumeration.value.nanoseconds.synopsis=Use nanosecond resolution.
+property.idle-time-limit.synopsis=Specifies the maximum length of time that a client connection may remain established since its last completed operation.
+property.idle-time-limit.description=A value of "0 seconds" indicates that no idle time limit is enforced.
+property.invalid-attribute-syntax-behavior.synopsis=Specifies how the Directory Server should handle operations whenever an attribute value violates the associated attribute syntax.
+property.invalid-attribute-syntax-behavior.syntax.enumeration.value.accept.synopsis=The Directory Server silently accepts attribute values that are invalid according to their associated syntax. Matching operations targeting those values may not behave as expected.
+property.invalid-attribute-syntax-behavior.syntax.enumeration.value.reject.synopsis=The Directory Server rejects attribute values that are invalid according to their associated syntax.
+property.invalid-attribute-syntax-behavior.syntax.enumeration.value.warn.synopsis=The Directory Server accepts attribute values that are invalid according to their associated syntax, but also logs a warning message to the error log. Matching operations targeting those values may not behave as expected.
+property.lookthrough-limit.synopsis=Specifies the maximum number of entries that the Directory Server should "look through" in the course of processing a search request.
+property.lookthrough-limit.description=This includes any entry that the server must examine in the course of processing the request, regardless of whether it actually matches the search criteria. A value of 0 indicates that no lookthrough limit is enforced. Note that this is the default server-wide limit, but it may be overridden on a per-user basis using the ds-rlim-lookthrough-limit operational attribute.
+property.max-allowed-client-connections.synopsis=Specifies the maximum number of client connections that may be established at any given time
+property.max-allowed-client-connections.description=A value of 0 indicates that unlimited client connection is allowed.
+property.notify-abandoned-operations.synopsis=Indicates whether the Directory Server should send a response to any operation that is interrupted via an abandon request.
+property.notify-abandoned-operations.description=The LDAP specification states that abandoned operations should not receive any response, but this may cause problems with client applications that always expect to receive a response to each request.
+property.proxied-authorization-identity-mapper.synopsis=Specifies the name of the identity mapper to map authorization ID values (using the "u:" form) provided in the proxied authorization control to the corresponding user entry.
+property.proxied-authorization-identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled.
+property.reject-unauthenticated-requests.synopsis=Indicates whether the Directory Server should reject any request (other than bind or StartTLS requests) received from a client that has not yet been authenticated, whose last authentication attempt was unsuccessful, or whose last authentication attempt used anonymous authentication.
+property.return-bind-error-messages.synopsis=Indicates whether responses for failed bind operations should include a message string providing the reason for the authentication failure.
+property.return-bind-error-messages.description=Note that these messages may include information that could potentially be used by an attacker. If this option is disabled, then these messages appears only in the server's access log.
+property.save-config-on-successful-startup.synopsis=Indicates whether the Directory Server should save a copy of its configuration whenever the startup process completes successfully.
+property.save-config-on-successful-startup.description=This ensures that the server provides a "last known good" configuration, which can be used as a reference (or copied into the active config) if the server fails to start with the current "active" configuration.
+property.server-error-result-code.synopsis=Specifies the numeric value of the result code when request processing fails due to an internal server error.
+property.single-structural-objectclass-behavior.synopsis=Specifies how the Directory Server should handle operations an entry does not contain a structural object class or contains multiple structural classes.
+property.single-structural-objectclass-behavior.syntax.enumeration.value.accept.synopsis=The Directory Server silently accepts entries that do not contain exactly one structural object class. Certain schema features that depend on the entry's structural class may not behave as expected.
+property.single-structural-objectclass-behavior.syntax.enumeration.value.reject.synopsis=The Directory Server rejects entries that do not contain exactly one structural object class.
+property.single-structural-objectclass-behavior.syntax.enumeration.value.warn.synopsis=The Directory Server accepts entries that do not contain exactly one structural object class, but also logs a warning message to the error log. Certain schema features that depend on the entry's structural class may not behave as expected.
+property.size-limit.synopsis=Specifies the maximum number of entries that the Directory Server should return to the client durin a search operation.
+property.size-limit.description=A value of 0 indicates that no size limit is enforced. Note that this is the default server-wide limit, but it may be overridden on a per-user basis using the ds-rlim-size-limit operational attribute.
+property.smtp-server.synopsis=Specifies the address (and optional port number) for a mail server that can be used to send email messages via SMTP.
+property.smtp-server.description=It may be an IP address or resolvable hostname, optionally followed by a colon and a port number.
+property.smtp-server.default-behavior.alias.synopsis=If no values are defined, then the server cannot send email via SMTP.
+property.smtp-server.syntax.string.pattern.synopsis=A hostname, optionally followed by a ":" followed by a port number.
+property.time-limit.synopsis=Specifies the maximum length of time that the Directory Server should spend processing a search operation.
+property.time-limit.description=A value of 0 seconds indicates that no time limit is enforced. Note that this is the default server-wide time limit, but it may be overridden on a per-user basis using the ds-rlim-time-limit operational attribute.
+property.workflow-configuration-mode.synopsis=Specifies the workflow configuration mode (auto vs. manual).
+property.workflow-configuration-mode.syntax.enumeration.value.auto.synopsis=In the "auto" configuration mode, there is no workflow configuration. The workflows are created automatically based on the backend configuration. There is one workflow per backend base DN.
+property.workflow-configuration-mode.syntax.enumeration.value.manual.synopsis=In the "manual" configuration mode, each workflow is created according to its description in the configuration.
+property.writability-mode.synopsis=Specifies the kinds of write operations the Directory Server can process.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=The Directory Server rejects all write operations that are requested of it, regardless of their origin.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=The Directory Server attempts to process all write operations that are requested of it, regardless of their origin.
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=The Directory Server attempts to process write operations requested as internal operations or through synchronization, but rejects any such operations requested from external clients.
diff --git a/opends/src/admin/messages/GlobalCfgDefn_es.properties b/opends/src/admin/messages/GlobalCfgDefn_es.properties
new file mode 100644
index 0000000..5d32c25
--- /dev/null
+++ b/opends/src/admin/messages/GlobalCfgDefn_es.properties
@@ -0,0 +1,80 @@
+user-friendly-name=Global Configuration
+user-friendly-plural-name=Global Configurations
+synopsis=The Global Configuration contains properties that affect the overall operation of the OpenDS Directory Server .
+property.add-missing-rdn-attributes.synopsis=Indicates whether the Directory Server should automatically add any attribute values contained in the entry's RDN into that entry when processing an add request.
+property.allow-attribute-name-exceptions.synopsis=Indicates whether the Directory Server should allow underscores in attribute names and allow attribute names to begin with numeric digits (both of which are violations of the LDAP standards).
+property.allowed-task.synopsis=Specifies the fully-qualified name of a Java class that may be invoked in the server.
+property.allowed-task.description=Any attempt to invoke a task not included in the list of allowed tasks is rejected.
+property.allowed-task.default-behavior.alias.synopsis=If no values are defined, then the server does not allow any tasks to be invoked.
+property.bind-with-dn-requires-password.synopsis=Indicates whether the Directory Server should reject any simple bind request that contains a DN but no password.
+property.bind-with-dn-requires-password.description=Although such bind requests are technically allowed by the LDAPv3 specification (and should be treated as anonymous simple authentication), they may introduce security problems in applications that do not verify that the client actually provided a password.
+property.check-schema.synopsis=Indicates whether schema enforcement is active.
+property.check-schema.description=When schema enforcement is activated, the Directory Server ensures that all operations result in entries are valid according to the defined server schema. It is strongly recommended that this option be left enabled to prevent the inadvertent addition of invalid data into the server.
+property.default-password-policy.synopsis=Specifies the name of the password policy that is in effect for users whose entries do not specify an alternate password policy (either via a real or virtual attribute).
+property.disabled-privilege.synopsis=Specifies the name of a privilege that should not be evaluated by the server.
+property.disabled-privilege.description=If a privilege is disabled, then it is assumed that all clients (including unauthenticated clients) have that privilege.
+property.disabled-privilege.default-behavior.alias.synopsis=If no values are defined, then the server enforces all privileges.
+property.disabled-privilege.syntax.enumeration.value.backend-backup.synopsis=Allows the user to request that the server process backup tasks.
+property.disabled-privilege.syntax.enumeration.value.backend-restore.synopsis=Allows the user to request that the server process restore tasks.
+property.disabled-privilege.syntax.enumeration.value.bypass-acl.synopsis=Allows the associated user to bypass access control checks performed by the server.
+property.disabled-privilege.syntax.enumeration.value.cancel-request.synopsis=Allows the user to cancel operations in progress on other client connections.
+property.disabled-privilege.syntax.enumeration.value.config-read.synopsis=Allows the associated user to read the server configuration.
+property.disabled-privilege.syntax.enumeration.value.config-write.synopsis=Allows the associated user to update the server configuration. The config-read privilege is also required.
+property.disabled-privilege.syntax.enumeration.value.data-sync.synopsis=Allows the user to participate in data synchronization.
+property.disabled-privilege.syntax.enumeration.value.disconnect-client.synopsis=Allows the user to terminate other client connections.
+property.disabled-privilege.syntax.enumeration.value.jmx-notify.synopsis=Allows the associated user to subscribe to receive JMX notifications.
+property.disabled-privilege.syntax.enumeration.value.jmx-read.synopsis=Allows the associated user to perform JMX read operations.
+property.disabled-privilege.syntax.enumeration.value.jmx-write.synopsis=Allows the associated user to perform JMX write operations.
+property.disabled-privilege.syntax.enumeration.value.ldif-export.synopsis=Allows the user to request that the server process LDIF export tasks.
+property.disabled-privilege.syntax.enumeration.value.ldif-import.synopsis=Allows the user to request that the server process LDIF import tasks.
+property.disabled-privilege.syntax.enumeration.value.modify-acl.synopsis=Allows the associated user to modify the server's access control configuration.
+property.disabled-privilege.syntax.enumeration.value.password-reset.synopsis=Allows the user to reset user passwords.
+property.disabled-privilege.syntax.enumeration.value.privilege-change.synopsis=Allows the user to make changes to the set of defined root privileges, as well as to grant and revoke privileges for users.
+property.disabled-privilege.syntax.enumeration.value.proxied-auth.synopsis=Allows the user to use the proxied authorization control, or to perform a bind that specifies an alternate authorization identity.
+property.disabled-privilege.syntax.enumeration.value.server-restart.synopsis=Allows the user to request that the server perform an in-core restart.
+property.disabled-privilege.syntax.enumeration.value.server-shutdown.synopsis=Allows the user to request that the server shut down.
+property.disabled-privilege.syntax.enumeration.value.unindexed-search.synopsis=Allows the user to request that the server process a search that cannot be optimized using server indexes.
+property.disabled-privilege.syntax.enumeration.value.update-schema.synopsis=Allows the user to make changes to the server schema.
+property.entry-cache-preload.synopsis=Indicates whether or not to preload the entry cache on startup.
+property.etime-resolution.synopsis=Specifies the resolution to use for operation elapsed processing time (etime) measurements.
+property.etime-resolution.syntax.enumeration.value.milliseconds.synopsis=Use millisecond resolution.
+property.etime-resolution.syntax.enumeration.value.nanoseconds.synopsis=Use nanosecond resolution.
+property.idle-time-limit.synopsis=Specifies the maximum length of time that a client connection may remain established since its last completed operation.
+property.idle-time-limit.description=A value of "0 seconds" indicates that no idle time limit is enforced.
+property.invalid-attribute-syntax-behavior.synopsis=Specifies how the Directory Server should handle operations whenever an attribute value violates the associated attribute syntax.
+property.invalid-attribute-syntax-behavior.syntax.enumeration.value.accept.synopsis=The Directory Server silently accepts attribute values that are invalid according to their associated syntax. Matching operations targeting those values may not behave as expected.
+property.invalid-attribute-syntax-behavior.syntax.enumeration.value.reject.synopsis=The Directory Server rejects attribute values that are invalid according to their associated syntax.
+property.invalid-attribute-syntax-behavior.syntax.enumeration.value.warn.synopsis=The Directory Server accepts attribute values that are invalid according to their associated syntax, but also logs a warning message to the error log. Matching operations targeting those values may not behave as expected.
+property.lookthrough-limit.synopsis=Specifies the maximum number of entries that the Directory Server should "look through" in the course of processing a search request.
+property.lookthrough-limit.description=This includes any entry that the server must examine in the course of processing the request, regardless of whether it actually matches the search criteria. A value of 0 indicates that no lookthrough limit is enforced. Note that this is the default server-wide limit, but it may be overridden on a per-user basis using the ds-rlim-lookthrough-limit operational attribute.
+property.max-allowed-client-connections.synopsis=Specifies the maximum number of client connections that may be established at any given time
+property.max-allowed-client-connections.description=A value of 0 indicates that unlimited client connection is allowed.
+property.notify-abandoned-operations.synopsis=Indicates whether the Directory Server should send a response to any operation that is interrupted via an abandon request.
+property.notify-abandoned-operations.description=The LDAP specification states that abandoned operations should not receive any response, but this may cause problems with client applications that always expect to receive a response to each request.
+property.proxied-authorization-identity-mapper.synopsis=Specifies the name of the identity mapper to map authorization ID values (using the "u:" form) provided in the proxied authorization control to the corresponding user entry.
+property.proxied-authorization-identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled.
+property.reject-unauthenticated-requests.synopsis=Indicates whether the Directory Server should reject any request (other than bind or StartTLS requests) received from a client that has not yet been authenticated, whose last authentication attempt was unsuccessful, or whose last authentication attempt used anonymous authentication.
+property.return-bind-error-messages.synopsis=Indicates whether responses for failed bind operations should include a message string providing the reason for the authentication failure.
+property.return-bind-error-messages.description=Note that these messages may include information that could potentially be used by an attacker. If this option is disabled, then these messages appears only in the server's access log.
+property.save-config-on-successful-startup.synopsis=Indicates whether the Directory Server should save a copy of its configuration whenever the startup process completes successfully.
+property.save-config-on-successful-startup.description=This ensures that the server provides a "last known good" configuration, which can be used as a reference (or copied into the active config) if the server fails to start with the current "active" configuration.
+property.server-error-result-code.synopsis=Specifies the numeric value of the result code when request processing fails due to an internal server error.
+property.single-structural-objectclass-behavior.synopsis=Specifies how the Directory Server should handle operations an entry does not contain a structural object class or contains multiple structural classes.
+property.single-structural-objectclass-behavior.syntax.enumeration.value.accept.synopsis=The Directory Server silently accepts entries that do not contain exactly one structural object class. Certain schema features that depend on the entry's structural class may not behave as expected.
+property.single-structural-objectclass-behavior.syntax.enumeration.value.reject.synopsis=The Directory Server rejects entries that do not contain exactly one structural object class.
+property.single-structural-objectclass-behavior.syntax.enumeration.value.warn.synopsis=The Directory Server accepts entries that do not contain exactly one structural object class, but also logs a warning message to the error log. Certain schema features that depend on the entry's structural class may not behave as expected.
+property.size-limit.synopsis=Specifies the maximum number of entries that the Directory Server should return to the client durin a search operation.
+property.size-limit.description=A value of 0 indicates that no size limit is enforced. Note that this is the default server-wide limit, but it may be overridden on a per-user basis using the ds-rlim-size-limit operational attribute.
+property.smtp-server.synopsis=Specifies the address (and optional port number) for a mail server that can be used to send email messages via SMTP.
+property.smtp-server.description=It may be an IP address or resolvable hostname, optionally followed by a colon and a port number.
+property.smtp-server.default-behavior.alias.synopsis=If no values are defined, then the server cannot send email via SMTP.
+property.smtp-server.syntax.string.pattern.synopsis=A hostname, optionally followed by a ":" followed by a port number.
+property.time-limit.synopsis=Specifies the maximum length of time that the Directory Server should spend processing a search operation.
+property.time-limit.description=A value of 0 seconds indicates that no time limit is enforced. Note that this is the default server-wide time limit, but it may be overridden on a per-user basis using the ds-rlim-time-limit operational attribute.
+property.workflow-configuration-mode.synopsis=Specifies the workflow configuration mode (auto vs. manual).
+property.workflow-configuration-mode.syntax.enumeration.value.auto.synopsis=In the "auto" configuration mode, there is no workflow configuration. The workflows are created automatically based on the backend configuration. There is one workflow per backend base DN.
+property.workflow-configuration-mode.syntax.enumeration.value.manual.synopsis=In the "manual" configuration mode, each workflow is created according to its description in the configuration.
+property.writability-mode.synopsis=Specifies the kinds of write operations the Directory Server can process.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=The Directory Server rejects all write operations that are requested of it, regardless of their origin.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=The Directory Server attempts to process all write operations that are requested of it, regardless of their origin.
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=The Directory Server attempts to process write operations requested as internal operations or through synchronization, but rejects any such operations requested from external clients.
diff --git a/opends/src/admin/messages/GlobalCfgDefn_fr.properties b/opends/src/admin/messages/GlobalCfgDefn_fr.properties
new file mode 100644
index 0000000..5d32c25
--- /dev/null
+++ b/opends/src/admin/messages/GlobalCfgDefn_fr.properties
@@ -0,0 +1,80 @@
+user-friendly-name=Global Configuration
+user-friendly-plural-name=Global Configurations
+synopsis=The Global Configuration contains properties that affect the overall operation of the OpenDS Directory Server .
+property.add-missing-rdn-attributes.synopsis=Indicates whether the Directory Server should automatically add any attribute values contained in the entry's RDN into that entry when processing an add request.
+property.allow-attribute-name-exceptions.synopsis=Indicates whether the Directory Server should allow underscores in attribute names and allow attribute names to begin with numeric digits (both of which are violations of the LDAP standards).
+property.allowed-task.synopsis=Specifies the fully-qualified name of a Java class that may be invoked in the server.
+property.allowed-task.description=Any attempt to invoke a task not included in the list of allowed tasks is rejected.
+property.allowed-task.default-behavior.alias.synopsis=If no values are defined, then the server does not allow any tasks to be invoked.
+property.bind-with-dn-requires-password.synopsis=Indicates whether the Directory Server should reject any simple bind request that contains a DN but no password.
+property.bind-with-dn-requires-password.description=Although such bind requests are technically allowed by the LDAPv3 specification (and should be treated as anonymous simple authentication), they may introduce security problems in applications that do not verify that the client actually provided a password.
+property.check-schema.synopsis=Indicates whether schema enforcement is active.
+property.check-schema.description=When schema enforcement is activated, the Directory Server ensures that all operations result in entries are valid according to the defined server schema. It is strongly recommended that this option be left enabled to prevent the inadvertent addition of invalid data into the server.
+property.default-password-policy.synopsis=Specifies the name of the password policy that is in effect for users whose entries do not specify an alternate password policy (either via a real or virtual attribute).
+property.disabled-privilege.synopsis=Specifies the name of a privilege that should not be evaluated by the server.
+property.disabled-privilege.description=If a privilege is disabled, then it is assumed that all clients (including unauthenticated clients) have that privilege.
+property.disabled-privilege.default-behavior.alias.synopsis=If no values are defined, then the server enforces all privileges.
+property.disabled-privilege.syntax.enumeration.value.backend-backup.synopsis=Allows the user to request that the server process backup tasks.
+property.disabled-privilege.syntax.enumeration.value.backend-restore.synopsis=Allows the user to request that the server process restore tasks.
+property.disabled-privilege.syntax.enumeration.value.bypass-acl.synopsis=Allows the associated user to bypass access control checks performed by the server.
+property.disabled-privilege.syntax.enumeration.value.cancel-request.synopsis=Allows the user to cancel operations in progress on other client connections.
+property.disabled-privilege.syntax.enumeration.value.config-read.synopsis=Allows the associated user to read the server configuration.
+property.disabled-privilege.syntax.enumeration.value.config-write.synopsis=Allows the associated user to update the server configuration. The config-read privilege is also required.
+property.disabled-privilege.syntax.enumeration.value.data-sync.synopsis=Allows the user to participate in data synchronization.
+property.disabled-privilege.syntax.enumeration.value.disconnect-client.synopsis=Allows the user to terminate other client connections.
+property.disabled-privilege.syntax.enumeration.value.jmx-notify.synopsis=Allows the associated user to subscribe to receive JMX notifications.
+property.disabled-privilege.syntax.enumeration.value.jmx-read.synopsis=Allows the associated user to perform JMX read operations.
+property.disabled-privilege.syntax.enumeration.value.jmx-write.synopsis=Allows the associated user to perform JMX write operations.
+property.disabled-privilege.syntax.enumeration.value.ldif-export.synopsis=Allows the user to request that the server process LDIF export tasks.
+property.disabled-privilege.syntax.enumeration.value.ldif-import.synopsis=Allows the user to request that the server process LDIF import tasks.
+property.disabled-privilege.syntax.enumeration.value.modify-acl.synopsis=Allows the associated user to modify the server's access control configuration.
+property.disabled-privilege.syntax.enumeration.value.password-reset.synopsis=Allows the user to reset user passwords.
+property.disabled-privilege.syntax.enumeration.value.privilege-change.synopsis=Allows the user to make changes to the set of defined root privileges, as well as to grant and revoke privileges for users.
+property.disabled-privilege.syntax.enumeration.value.proxied-auth.synopsis=Allows the user to use the proxied authorization control, or to perform a bind that specifies an alternate authorization identity.
+property.disabled-privilege.syntax.enumeration.value.server-restart.synopsis=Allows the user to request that the server perform an in-core restart.
+property.disabled-privilege.syntax.enumeration.value.server-shutdown.synopsis=Allows the user to request that the server shut down.
+property.disabled-privilege.syntax.enumeration.value.unindexed-search.synopsis=Allows the user to request that the server process a search that cannot be optimized using server indexes.
+property.disabled-privilege.syntax.enumeration.value.update-schema.synopsis=Allows the user to make changes to the server schema.
+property.entry-cache-preload.synopsis=Indicates whether or not to preload the entry cache on startup.
+property.etime-resolution.synopsis=Specifies the resolution to use for operation elapsed processing time (etime) measurements.
+property.etime-resolution.syntax.enumeration.value.milliseconds.synopsis=Use millisecond resolution.
+property.etime-resolution.syntax.enumeration.value.nanoseconds.synopsis=Use nanosecond resolution.
+property.idle-time-limit.synopsis=Specifies the maximum length of time that a client connection may remain established since its last completed operation.
+property.idle-time-limit.description=A value of "0 seconds" indicates that no idle time limit is enforced.
+property.invalid-attribute-syntax-behavior.synopsis=Specifies how the Directory Server should handle operations whenever an attribute value violates the associated attribute syntax.
+property.invalid-attribute-syntax-behavior.syntax.enumeration.value.accept.synopsis=The Directory Server silently accepts attribute values that are invalid according to their associated syntax. Matching operations targeting those values may not behave as expected.
+property.invalid-attribute-syntax-behavior.syntax.enumeration.value.reject.synopsis=The Directory Server rejects attribute values that are invalid according to their associated syntax.
+property.invalid-attribute-syntax-behavior.syntax.enumeration.value.warn.synopsis=The Directory Server accepts attribute values that are invalid according to their associated syntax, but also logs a warning message to the error log. Matching operations targeting those values may not behave as expected.
+property.lookthrough-limit.synopsis=Specifies the maximum number of entries that the Directory Server should "look through" in the course of processing a search request.
+property.lookthrough-limit.description=This includes any entry that the server must examine in the course of processing the request, regardless of whether it actually matches the search criteria. A value of 0 indicates that no lookthrough limit is enforced. Note that this is the default server-wide limit, but it may be overridden on a per-user basis using the ds-rlim-lookthrough-limit operational attribute.
+property.max-allowed-client-connections.synopsis=Specifies the maximum number of client connections that may be established at any given time
+property.max-allowed-client-connections.description=A value of 0 indicates that unlimited client connection is allowed.
+property.notify-abandoned-operations.synopsis=Indicates whether the Directory Server should send a response to any operation that is interrupted via an abandon request.
+property.notify-abandoned-operations.description=The LDAP specification states that abandoned operations should not receive any response, but this may cause problems with client applications that always expect to receive a response to each request.
+property.proxied-authorization-identity-mapper.synopsis=Specifies the name of the identity mapper to map authorization ID values (using the "u:" form) provided in the proxied authorization control to the corresponding user entry.
+property.proxied-authorization-identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled.
+property.reject-unauthenticated-requests.synopsis=Indicates whether the Directory Server should reject any request (other than bind or StartTLS requests) received from a client that has not yet been authenticated, whose last authentication attempt was unsuccessful, or whose last authentication attempt used anonymous authentication.
+property.return-bind-error-messages.synopsis=Indicates whether responses for failed bind operations should include a message string providing the reason for the authentication failure.
+property.return-bind-error-messages.description=Note that these messages may include information that could potentially be used by an attacker. If this option is disabled, then these messages appears only in the server's access log.
+property.save-config-on-successful-startup.synopsis=Indicates whether the Directory Server should save a copy of its configuration whenever the startup process completes successfully.
+property.save-config-on-successful-startup.description=This ensures that the server provides a "last known good" configuration, which can be used as a reference (or copied into the active config) if the server fails to start with the current "active" configuration.
+property.server-error-result-code.synopsis=Specifies the numeric value of the result code when request processing fails due to an internal server error.
+property.single-structural-objectclass-behavior.synopsis=Specifies how the Directory Server should handle operations an entry does not contain a structural object class or contains multiple structural classes.
+property.single-structural-objectclass-behavior.syntax.enumeration.value.accept.synopsis=The Directory Server silently accepts entries that do not contain exactly one structural object class. Certain schema features that depend on the entry's structural class may not behave as expected.
+property.single-structural-objectclass-behavior.syntax.enumeration.value.reject.synopsis=The Directory Server rejects entries that do not contain exactly one structural object class.
+property.single-structural-objectclass-behavior.syntax.enumeration.value.warn.synopsis=The Directory Server accepts entries that do not contain exactly one structural object class, but also logs a warning message to the error log. Certain schema features that depend on the entry's structural class may not behave as expected.
+property.size-limit.synopsis=Specifies the maximum number of entries that the Directory Server should return to the client durin a search operation.
+property.size-limit.description=A value of 0 indicates that no size limit is enforced. Note that this is the default server-wide limit, but it may be overridden on a per-user basis using the ds-rlim-size-limit operational attribute.
+property.smtp-server.synopsis=Specifies the address (and optional port number) for a mail server that can be used to send email messages via SMTP.
+property.smtp-server.description=It may be an IP address or resolvable hostname, optionally followed by a colon and a port number.
+property.smtp-server.default-behavior.alias.synopsis=If no values are defined, then the server cannot send email via SMTP.
+property.smtp-server.syntax.string.pattern.synopsis=A hostname, optionally followed by a ":" followed by a port number.
+property.time-limit.synopsis=Specifies the maximum length of time that the Directory Server should spend processing a search operation.
+property.time-limit.description=A value of 0 seconds indicates that no time limit is enforced. Note that this is the default server-wide time limit, but it may be overridden on a per-user basis using the ds-rlim-time-limit operational attribute.
+property.workflow-configuration-mode.synopsis=Specifies the workflow configuration mode (auto vs. manual).
+property.workflow-configuration-mode.syntax.enumeration.value.auto.synopsis=In the "auto" configuration mode, there is no workflow configuration. The workflows are created automatically based on the backend configuration. There is one workflow per backend base DN.
+property.workflow-configuration-mode.syntax.enumeration.value.manual.synopsis=In the "manual" configuration mode, each workflow is created according to its description in the configuration.
+property.writability-mode.synopsis=Specifies the kinds of write operations the Directory Server can process.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=The Directory Server rejects all write operations that are requested of it, regardless of their origin.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=The Directory Server attempts to process all write operations that are requested of it, regardless of their origin.
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=The Directory Server attempts to process write operations requested as internal operations or through synchronization, but rejects any such operations requested from external clients.
diff --git a/opends/src/admin/messages/GlobalCfgDefn_ja.properties b/opends/src/admin/messages/GlobalCfgDefn_ja.properties
new file mode 100644
index 0000000..5d32c25
--- /dev/null
+++ b/opends/src/admin/messages/GlobalCfgDefn_ja.properties
@@ -0,0 +1,80 @@
+user-friendly-name=Global Configuration
+user-friendly-plural-name=Global Configurations
+synopsis=The Global Configuration contains properties that affect the overall operation of the OpenDS Directory Server .
+property.add-missing-rdn-attributes.synopsis=Indicates whether the Directory Server should automatically add any attribute values contained in the entry's RDN into that entry when processing an add request.
+property.allow-attribute-name-exceptions.synopsis=Indicates whether the Directory Server should allow underscores in attribute names and allow attribute names to begin with numeric digits (both of which are violations of the LDAP standards).
+property.allowed-task.synopsis=Specifies the fully-qualified name of a Java class that may be invoked in the server.
+property.allowed-task.description=Any attempt to invoke a task not included in the list of allowed tasks is rejected.
+property.allowed-task.default-behavior.alias.synopsis=If no values are defined, then the server does not allow any tasks to be invoked.
+property.bind-with-dn-requires-password.synopsis=Indicates whether the Directory Server should reject any simple bind request that contains a DN but no password.
+property.bind-with-dn-requires-password.description=Although such bind requests are technically allowed by the LDAPv3 specification (and should be treated as anonymous simple authentication), they may introduce security problems in applications that do not verify that the client actually provided a password.
+property.check-schema.synopsis=Indicates whether schema enforcement is active.
+property.check-schema.description=When schema enforcement is activated, the Directory Server ensures that all operations result in entries are valid according to the defined server schema. It is strongly recommended that this option be left enabled to prevent the inadvertent addition of invalid data into the server.
+property.default-password-policy.synopsis=Specifies the name of the password policy that is in effect for users whose entries do not specify an alternate password policy (either via a real or virtual attribute).
+property.disabled-privilege.synopsis=Specifies the name of a privilege that should not be evaluated by the server.
+property.disabled-privilege.description=If a privilege is disabled, then it is assumed that all clients (including unauthenticated clients) have that privilege.
+property.disabled-privilege.default-behavior.alias.synopsis=If no values are defined, then the server enforces all privileges.
+property.disabled-privilege.syntax.enumeration.value.backend-backup.synopsis=Allows the user to request that the server process backup tasks.
+property.disabled-privilege.syntax.enumeration.value.backend-restore.synopsis=Allows the user to request that the server process restore tasks.
+property.disabled-privilege.syntax.enumeration.value.bypass-acl.synopsis=Allows the associated user to bypass access control checks performed by the server.
+property.disabled-privilege.syntax.enumeration.value.cancel-request.synopsis=Allows the user to cancel operations in progress on other client connections.
+property.disabled-privilege.syntax.enumeration.value.config-read.synopsis=Allows the associated user to read the server configuration.
+property.disabled-privilege.syntax.enumeration.value.config-write.synopsis=Allows the associated user to update the server configuration. The config-read privilege is also required.
+property.disabled-privilege.syntax.enumeration.value.data-sync.synopsis=Allows the user to participate in data synchronization.
+property.disabled-privilege.syntax.enumeration.value.disconnect-client.synopsis=Allows the user to terminate other client connections.
+property.disabled-privilege.syntax.enumeration.value.jmx-notify.synopsis=Allows the associated user to subscribe to receive JMX notifications.
+property.disabled-privilege.syntax.enumeration.value.jmx-read.synopsis=Allows the associated user to perform JMX read operations.
+property.disabled-privilege.syntax.enumeration.value.jmx-write.synopsis=Allows the associated user to perform JMX write operations.
+property.disabled-privilege.syntax.enumeration.value.ldif-export.synopsis=Allows the user to request that the server process LDIF export tasks.
+property.disabled-privilege.syntax.enumeration.value.ldif-import.synopsis=Allows the user to request that the server process LDIF import tasks.
+property.disabled-privilege.syntax.enumeration.value.modify-acl.synopsis=Allows the associated user to modify the server's access control configuration.
+property.disabled-privilege.syntax.enumeration.value.password-reset.synopsis=Allows the user to reset user passwords.
+property.disabled-privilege.syntax.enumeration.value.privilege-change.synopsis=Allows the user to make changes to the set of defined root privileges, as well as to grant and revoke privileges for users.
+property.disabled-privilege.syntax.enumeration.value.proxied-auth.synopsis=Allows the user to use the proxied authorization control, or to perform a bind that specifies an alternate authorization identity.
+property.disabled-privilege.syntax.enumeration.value.server-restart.synopsis=Allows the user to request that the server perform an in-core restart.
+property.disabled-privilege.syntax.enumeration.value.server-shutdown.synopsis=Allows the user to request that the server shut down.
+property.disabled-privilege.syntax.enumeration.value.unindexed-search.synopsis=Allows the user to request that the server process a search that cannot be optimized using server indexes.
+property.disabled-privilege.syntax.enumeration.value.update-schema.synopsis=Allows the user to make changes to the server schema.
+property.entry-cache-preload.synopsis=Indicates whether or not to preload the entry cache on startup.
+property.etime-resolution.synopsis=Specifies the resolution to use for operation elapsed processing time (etime) measurements.
+property.etime-resolution.syntax.enumeration.value.milliseconds.synopsis=Use millisecond resolution.
+property.etime-resolution.syntax.enumeration.value.nanoseconds.synopsis=Use nanosecond resolution.
+property.idle-time-limit.synopsis=Specifies the maximum length of time that a client connection may remain established since its last completed operation.
+property.idle-time-limit.description=A value of "0 seconds" indicates that no idle time limit is enforced.
+property.invalid-attribute-syntax-behavior.synopsis=Specifies how the Directory Server should handle operations whenever an attribute value violates the associated attribute syntax.
+property.invalid-attribute-syntax-behavior.syntax.enumeration.value.accept.synopsis=The Directory Server silently accepts attribute values that are invalid according to their associated syntax. Matching operations targeting those values may not behave as expected.
+property.invalid-attribute-syntax-behavior.syntax.enumeration.value.reject.synopsis=The Directory Server rejects attribute values that are invalid according to their associated syntax.
+property.invalid-attribute-syntax-behavior.syntax.enumeration.value.warn.synopsis=The Directory Server accepts attribute values that are invalid according to their associated syntax, but also logs a warning message to the error log. Matching operations targeting those values may not behave as expected.
+property.lookthrough-limit.synopsis=Specifies the maximum number of entries that the Directory Server should "look through" in the course of processing a search request.
+property.lookthrough-limit.description=This includes any entry that the server must examine in the course of processing the request, regardless of whether it actually matches the search criteria. A value of 0 indicates that no lookthrough limit is enforced. Note that this is the default server-wide limit, but it may be overridden on a per-user basis using the ds-rlim-lookthrough-limit operational attribute.
+property.max-allowed-client-connections.synopsis=Specifies the maximum number of client connections that may be established at any given time
+property.max-allowed-client-connections.description=A value of 0 indicates that unlimited client connection is allowed.
+property.notify-abandoned-operations.synopsis=Indicates whether the Directory Server should send a response to any operation that is interrupted via an abandon request.
+property.notify-abandoned-operations.description=The LDAP specification states that abandoned operations should not receive any response, but this may cause problems with client applications that always expect to receive a response to each request.
+property.proxied-authorization-identity-mapper.synopsis=Specifies the name of the identity mapper to map authorization ID values (using the "u:" form) provided in the proxied authorization control to the corresponding user entry.
+property.proxied-authorization-identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled.
+property.reject-unauthenticated-requests.synopsis=Indicates whether the Directory Server should reject any request (other than bind or StartTLS requests) received from a client that has not yet been authenticated, whose last authentication attempt was unsuccessful, or whose last authentication attempt used anonymous authentication.
+property.return-bind-error-messages.synopsis=Indicates whether responses for failed bind operations should include a message string providing the reason for the authentication failure.
+property.return-bind-error-messages.description=Note that these messages may include information that could potentially be used by an attacker. If this option is disabled, then these messages appears only in the server's access log.
+property.save-config-on-successful-startup.synopsis=Indicates whether the Directory Server should save a copy of its configuration whenever the startup process completes successfully.
+property.save-config-on-successful-startup.description=This ensures that the server provides a "last known good" configuration, which can be used as a reference (or copied into the active config) if the server fails to start with the current "active" configuration.
+property.server-error-result-code.synopsis=Specifies the numeric value of the result code when request processing fails due to an internal server error.
+property.single-structural-objectclass-behavior.synopsis=Specifies how the Directory Server should handle operations an entry does not contain a structural object class or contains multiple structural classes.
+property.single-structural-objectclass-behavior.syntax.enumeration.value.accept.synopsis=The Directory Server silently accepts entries that do not contain exactly one structural object class. Certain schema features that depend on the entry's structural class may not behave as expected.
+property.single-structural-objectclass-behavior.syntax.enumeration.value.reject.synopsis=The Directory Server rejects entries that do not contain exactly one structural object class.
+property.single-structural-objectclass-behavior.syntax.enumeration.value.warn.synopsis=The Directory Server accepts entries that do not contain exactly one structural object class, but also logs a warning message to the error log. Certain schema features that depend on the entry's structural class may not behave as expected.
+property.size-limit.synopsis=Specifies the maximum number of entries that the Directory Server should return to the client durin a search operation.
+property.size-limit.description=A value of 0 indicates that no size limit is enforced. Note that this is the default server-wide limit, but it may be overridden on a per-user basis using the ds-rlim-size-limit operational attribute.
+property.smtp-server.synopsis=Specifies the address (and optional port number) for a mail server that can be used to send email messages via SMTP.
+property.smtp-server.description=It may be an IP address or resolvable hostname, optionally followed by a colon and a port number.
+property.smtp-server.default-behavior.alias.synopsis=If no values are defined, then the server cannot send email via SMTP.
+property.smtp-server.syntax.string.pattern.synopsis=A hostname, optionally followed by a ":" followed by a port number.
+property.time-limit.synopsis=Specifies the maximum length of time that the Directory Server should spend processing a search operation.
+property.time-limit.description=A value of 0 seconds indicates that no time limit is enforced. Note that this is the default server-wide time limit, but it may be overridden on a per-user basis using the ds-rlim-time-limit operational attribute.
+property.workflow-configuration-mode.synopsis=Specifies the workflow configuration mode (auto vs. manual).
+property.workflow-configuration-mode.syntax.enumeration.value.auto.synopsis=In the "auto" configuration mode, there is no workflow configuration. The workflows are created automatically based on the backend configuration. There is one workflow per backend base DN.
+property.workflow-configuration-mode.syntax.enumeration.value.manual.synopsis=In the "manual" configuration mode, each workflow is created according to its description in the configuration.
+property.writability-mode.synopsis=Specifies the kinds of write operations the Directory Server can process.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=The Directory Server rejects all write operations that are requested of it, regardless of their origin.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=The Directory Server attempts to process all write operations that are requested of it, regardless of their origin.
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=The Directory Server attempts to process write operations requested as internal operations or through synchronization, but rejects any such operations requested from external clients.
diff --git a/opends/src/admin/messages/GlobalCfgDefn_ko.properties b/opends/src/admin/messages/GlobalCfgDefn_ko.properties
new file mode 100644
index 0000000..5d32c25
--- /dev/null
+++ b/opends/src/admin/messages/GlobalCfgDefn_ko.properties
@@ -0,0 +1,80 @@
+user-friendly-name=Global Configuration
+user-friendly-plural-name=Global Configurations
+synopsis=The Global Configuration contains properties that affect the overall operation of the OpenDS Directory Server .
+property.add-missing-rdn-attributes.synopsis=Indicates whether the Directory Server should automatically add any attribute values contained in the entry's RDN into that entry when processing an add request.
+property.allow-attribute-name-exceptions.synopsis=Indicates whether the Directory Server should allow underscores in attribute names and allow attribute names to begin with numeric digits (both of which are violations of the LDAP standards).
+property.allowed-task.synopsis=Specifies the fully-qualified name of a Java class that may be invoked in the server.
+property.allowed-task.description=Any attempt to invoke a task not included in the list of allowed tasks is rejected.
+property.allowed-task.default-behavior.alias.synopsis=If no values are defined, then the server does not allow any tasks to be invoked.
+property.bind-with-dn-requires-password.synopsis=Indicates whether the Directory Server should reject any simple bind request that contains a DN but no password.
+property.bind-with-dn-requires-password.description=Although such bind requests are technically allowed by the LDAPv3 specification (and should be treated as anonymous simple authentication), they may introduce security problems in applications that do not verify that the client actually provided a password.
+property.check-schema.synopsis=Indicates whether schema enforcement is active.
+property.check-schema.description=When schema enforcement is activated, the Directory Server ensures that all operations result in entries are valid according to the defined server schema. It is strongly recommended that this option be left enabled to prevent the inadvertent addition of invalid data into the server.
+property.default-password-policy.synopsis=Specifies the name of the password policy that is in effect for users whose entries do not specify an alternate password policy (either via a real or virtual attribute).
+property.disabled-privilege.synopsis=Specifies the name of a privilege that should not be evaluated by the server.
+property.disabled-privilege.description=If a privilege is disabled, then it is assumed that all clients (including unauthenticated clients) have that privilege.
+property.disabled-privilege.default-behavior.alias.synopsis=If no values are defined, then the server enforces all privileges.
+property.disabled-privilege.syntax.enumeration.value.backend-backup.synopsis=Allows the user to request that the server process backup tasks.
+property.disabled-privilege.syntax.enumeration.value.backend-restore.synopsis=Allows the user to request that the server process restore tasks.
+property.disabled-privilege.syntax.enumeration.value.bypass-acl.synopsis=Allows the associated user to bypass access control checks performed by the server.
+property.disabled-privilege.syntax.enumeration.value.cancel-request.synopsis=Allows the user to cancel operations in progress on other client connections.
+property.disabled-privilege.syntax.enumeration.value.config-read.synopsis=Allows the associated user to read the server configuration.
+property.disabled-privilege.syntax.enumeration.value.config-write.synopsis=Allows the associated user to update the server configuration. The config-read privilege is also required.
+property.disabled-privilege.syntax.enumeration.value.data-sync.synopsis=Allows the user to participate in data synchronization.
+property.disabled-privilege.syntax.enumeration.value.disconnect-client.synopsis=Allows the user to terminate other client connections.
+property.disabled-privilege.syntax.enumeration.value.jmx-notify.synopsis=Allows the associated user to subscribe to receive JMX notifications.
+property.disabled-privilege.syntax.enumeration.value.jmx-read.synopsis=Allows the associated user to perform JMX read operations.
+property.disabled-privilege.syntax.enumeration.value.jmx-write.synopsis=Allows the associated user to perform JMX write operations.
+property.disabled-privilege.syntax.enumeration.value.ldif-export.synopsis=Allows the user to request that the server process LDIF export tasks.
+property.disabled-privilege.syntax.enumeration.value.ldif-import.synopsis=Allows the user to request that the server process LDIF import tasks.
+property.disabled-privilege.syntax.enumeration.value.modify-acl.synopsis=Allows the associated user to modify the server's access control configuration.
+property.disabled-privilege.syntax.enumeration.value.password-reset.synopsis=Allows the user to reset user passwords.
+property.disabled-privilege.syntax.enumeration.value.privilege-change.synopsis=Allows the user to make changes to the set of defined root privileges, as well as to grant and revoke privileges for users.
+property.disabled-privilege.syntax.enumeration.value.proxied-auth.synopsis=Allows the user to use the proxied authorization control, or to perform a bind that specifies an alternate authorization identity.
+property.disabled-privilege.syntax.enumeration.value.server-restart.synopsis=Allows the user to request that the server perform an in-core restart.
+property.disabled-privilege.syntax.enumeration.value.server-shutdown.synopsis=Allows the user to request that the server shut down.
+property.disabled-privilege.syntax.enumeration.value.unindexed-search.synopsis=Allows the user to request that the server process a search that cannot be optimized using server indexes.
+property.disabled-privilege.syntax.enumeration.value.update-schema.synopsis=Allows the user to make changes to the server schema.
+property.entry-cache-preload.synopsis=Indicates whether or not to preload the entry cache on startup.
+property.etime-resolution.synopsis=Specifies the resolution to use for operation elapsed processing time (etime) measurements.
+property.etime-resolution.syntax.enumeration.value.milliseconds.synopsis=Use millisecond resolution.
+property.etime-resolution.syntax.enumeration.value.nanoseconds.synopsis=Use nanosecond resolution.
+property.idle-time-limit.synopsis=Specifies the maximum length of time that a client connection may remain established since its last completed operation.
+property.idle-time-limit.description=A value of "0 seconds" indicates that no idle time limit is enforced.
+property.invalid-attribute-syntax-behavior.synopsis=Specifies how the Directory Server should handle operations whenever an attribute value violates the associated attribute syntax.
+property.invalid-attribute-syntax-behavior.syntax.enumeration.value.accept.synopsis=The Directory Server silently accepts attribute values that are invalid according to their associated syntax. Matching operations targeting those values may not behave as expected.
+property.invalid-attribute-syntax-behavior.syntax.enumeration.value.reject.synopsis=The Directory Server rejects attribute values that are invalid according to their associated syntax.
+property.invalid-attribute-syntax-behavior.syntax.enumeration.value.warn.synopsis=The Directory Server accepts attribute values that are invalid according to their associated syntax, but also logs a warning message to the error log. Matching operations targeting those values may not behave as expected.
+property.lookthrough-limit.synopsis=Specifies the maximum number of entries that the Directory Server should "look through" in the course of processing a search request.
+property.lookthrough-limit.description=This includes any entry that the server must examine in the course of processing the request, regardless of whether it actually matches the search criteria. A value of 0 indicates that no lookthrough limit is enforced. Note that this is the default server-wide limit, but it may be overridden on a per-user basis using the ds-rlim-lookthrough-limit operational attribute.
+property.max-allowed-client-connections.synopsis=Specifies the maximum number of client connections that may be established at any given time
+property.max-allowed-client-connections.description=A value of 0 indicates that unlimited client connection is allowed.
+property.notify-abandoned-operations.synopsis=Indicates whether the Directory Server should send a response to any operation that is interrupted via an abandon request.
+property.notify-abandoned-operations.description=The LDAP specification states that abandoned operations should not receive any response, but this may cause problems with client applications that always expect to receive a response to each request.
+property.proxied-authorization-identity-mapper.synopsis=Specifies the name of the identity mapper to map authorization ID values (using the "u:" form) provided in the proxied authorization control to the corresponding user entry.
+property.proxied-authorization-identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled.
+property.reject-unauthenticated-requests.synopsis=Indicates whether the Directory Server should reject any request (other than bind or StartTLS requests) received from a client that has not yet been authenticated, whose last authentication attempt was unsuccessful, or whose last authentication attempt used anonymous authentication.
+property.return-bind-error-messages.synopsis=Indicates whether responses for failed bind operations should include a message string providing the reason for the authentication failure.
+property.return-bind-error-messages.description=Note that these messages may include information that could potentially be used by an attacker. If this option is disabled, then these messages appears only in the server's access log.
+property.save-config-on-successful-startup.synopsis=Indicates whether the Directory Server should save a copy of its configuration whenever the startup process completes successfully.
+property.save-config-on-successful-startup.description=This ensures that the server provides a "last known good" configuration, which can be used as a reference (or copied into the active config) if the server fails to start with the current "active" configuration.
+property.server-error-result-code.synopsis=Specifies the numeric value of the result code when request processing fails due to an internal server error.
+property.single-structural-objectclass-behavior.synopsis=Specifies how the Directory Server should handle operations an entry does not contain a structural object class or contains multiple structural classes.
+property.single-structural-objectclass-behavior.syntax.enumeration.value.accept.synopsis=The Directory Server silently accepts entries that do not contain exactly one structural object class. Certain schema features that depend on the entry's structural class may not behave as expected.
+property.single-structural-objectclass-behavior.syntax.enumeration.value.reject.synopsis=The Directory Server rejects entries that do not contain exactly one structural object class.
+property.single-structural-objectclass-behavior.syntax.enumeration.value.warn.synopsis=The Directory Server accepts entries that do not contain exactly one structural object class, but also logs a warning message to the error log. Certain schema features that depend on the entry's structural class may not behave as expected.
+property.size-limit.synopsis=Specifies the maximum number of entries that the Directory Server should return to the client durin a search operation.
+property.size-limit.description=A value of 0 indicates that no size limit is enforced. Note that this is the default server-wide limit, but it may be overridden on a per-user basis using the ds-rlim-size-limit operational attribute.
+property.smtp-server.synopsis=Specifies the address (and optional port number) for a mail server that can be used to send email messages via SMTP.
+property.smtp-server.description=It may be an IP address or resolvable hostname, optionally followed by a colon and a port number.
+property.smtp-server.default-behavior.alias.synopsis=If no values are defined, then the server cannot send email via SMTP.
+property.smtp-server.syntax.string.pattern.synopsis=A hostname, optionally followed by a ":" followed by a port number.
+property.time-limit.synopsis=Specifies the maximum length of time that the Directory Server should spend processing a search operation.
+property.time-limit.description=A value of 0 seconds indicates that no time limit is enforced. Note that this is the default server-wide time limit, but it may be overridden on a per-user basis using the ds-rlim-time-limit operational attribute.
+property.workflow-configuration-mode.synopsis=Specifies the workflow configuration mode (auto vs. manual).
+property.workflow-configuration-mode.syntax.enumeration.value.auto.synopsis=In the "auto" configuration mode, there is no workflow configuration. The workflows are created automatically based on the backend configuration. There is one workflow per backend base DN.
+property.workflow-configuration-mode.syntax.enumeration.value.manual.synopsis=In the "manual" configuration mode, each workflow is created according to its description in the configuration.
+property.writability-mode.synopsis=Specifies the kinds of write operations the Directory Server can process.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=The Directory Server rejects all write operations that are requested of it, regardless of their origin.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=The Directory Server attempts to process all write operations that are requested of it, regardless of their origin.
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=The Directory Server attempts to process write operations requested as internal operations or through synchronization, but rejects any such operations requested from external clients.
diff --git a/opends/src/admin/messages/GlobalCfgDefn_zh_CN.properties b/opends/src/admin/messages/GlobalCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..5d32c25
--- /dev/null
+++ b/opends/src/admin/messages/GlobalCfgDefn_zh_CN.properties
@@ -0,0 +1,80 @@
+user-friendly-name=Global Configuration
+user-friendly-plural-name=Global Configurations
+synopsis=The Global Configuration contains properties that affect the overall operation of the OpenDS Directory Server .
+property.add-missing-rdn-attributes.synopsis=Indicates whether the Directory Server should automatically add any attribute values contained in the entry's RDN into that entry when processing an add request.
+property.allow-attribute-name-exceptions.synopsis=Indicates whether the Directory Server should allow underscores in attribute names and allow attribute names to begin with numeric digits (both of which are violations of the LDAP standards).
+property.allowed-task.synopsis=Specifies the fully-qualified name of a Java class that may be invoked in the server.
+property.allowed-task.description=Any attempt to invoke a task not included in the list of allowed tasks is rejected.
+property.allowed-task.default-behavior.alias.synopsis=If no values are defined, then the server does not allow any tasks to be invoked.
+property.bind-with-dn-requires-password.synopsis=Indicates whether the Directory Server should reject any simple bind request that contains a DN but no password.
+property.bind-with-dn-requires-password.description=Although such bind requests are technically allowed by the LDAPv3 specification (and should be treated as anonymous simple authentication), they may introduce security problems in applications that do not verify that the client actually provided a password.
+property.check-schema.synopsis=Indicates whether schema enforcement is active.
+property.check-schema.description=When schema enforcement is activated, the Directory Server ensures that all operations result in entries are valid according to the defined server schema. It is strongly recommended that this option be left enabled to prevent the inadvertent addition of invalid data into the server.
+property.default-password-policy.synopsis=Specifies the name of the password policy that is in effect for users whose entries do not specify an alternate password policy (either via a real or virtual attribute).
+property.disabled-privilege.synopsis=Specifies the name of a privilege that should not be evaluated by the server.
+property.disabled-privilege.description=If a privilege is disabled, then it is assumed that all clients (including unauthenticated clients) have that privilege.
+property.disabled-privilege.default-behavior.alias.synopsis=If no values are defined, then the server enforces all privileges.
+property.disabled-privilege.syntax.enumeration.value.backend-backup.synopsis=Allows the user to request that the server process backup tasks.
+property.disabled-privilege.syntax.enumeration.value.backend-restore.synopsis=Allows the user to request that the server process restore tasks.
+property.disabled-privilege.syntax.enumeration.value.bypass-acl.synopsis=Allows the associated user to bypass access control checks performed by the server.
+property.disabled-privilege.syntax.enumeration.value.cancel-request.synopsis=Allows the user to cancel operations in progress on other client connections.
+property.disabled-privilege.syntax.enumeration.value.config-read.synopsis=Allows the associated user to read the server configuration.
+property.disabled-privilege.syntax.enumeration.value.config-write.synopsis=Allows the associated user to update the server configuration. The config-read privilege is also required.
+property.disabled-privilege.syntax.enumeration.value.data-sync.synopsis=Allows the user to participate in data synchronization.
+property.disabled-privilege.syntax.enumeration.value.disconnect-client.synopsis=Allows the user to terminate other client connections.
+property.disabled-privilege.syntax.enumeration.value.jmx-notify.synopsis=Allows the associated user to subscribe to receive JMX notifications.
+property.disabled-privilege.syntax.enumeration.value.jmx-read.synopsis=Allows the associated user to perform JMX read operations.
+property.disabled-privilege.syntax.enumeration.value.jmx-write.synopsis=Allows the associated user to perform JMX write operations.
+property.disabled-privilege.syntax.enumeration.value.ldif-export.synopsis=Allows the user to request that the server process LDIF export tasks.
+property.disabled-privilege.syntax.enumeration.value.ldif-import.synopsis=Allows the user to request that the server process LDIF import tasks.
+property.disabled-privilege.syntax.enumeration.value.modify-acl.synopsis=Allows the associated user to modify the server's access control configuration.
+property.disabled-privilege.syntax.enumeration.value.password-reset.synopsis=Allows the user to reset user passwords.
+property.disabled-privilege.syntax.enumeration.value.privilege-change.synopsis=Allows the user to make changes to the set of defined root privileges, as well as to grant and revoke privileges for users.
+property.disabled-privilege.syntax.enumeration.value.proxied-auth.synopsis=Allows the user to use the proxied authorization control, or to perform a bind that specifies an alternate authorization identity.
+property.disabled-privilege.syntax.enumeration.value.server-restart.synopsis=Allows the user to request that the server perform an in-core restart.
+property.disabled-privilege.syntax.enumeration.value.server-shutdown.synopsis=Allows the user to request that the server shut down.
+property.disabled-privilege.syntax.enumeration.value.unindexed-search.synopsis=Allows the user to request that the server process a search that cannot be optimized using server indexes.
+property.disabled-privilege.syntax.enumeration.value.update-schema.synopsis=Allows the user to make changes to the server schema.
+property.entry-cache-preload.synopsis=Indicates whether or not to preload the entry cache on startup.
+property.etime-resolution.synopsis=Specifies the resolution to use for operation elapsed processing time (etime) measurements.
+property.etime-resolution.syntax.enumeration.value.milliseconds.synopsis=Use millisecond resolution.
+property.etime-resolution.syntax.enumeration.value.nanoseconds.synopsis=Use nanosecond resolution.
+property.idle-time-limit.synopsis=Specifies the maximum length of time that a client connection may remain established since its last completed operation.
+property.idle-time-limit.description=A value of "0 seconds" indicates that no idle time limit is enforced.
+property.invalid-attribute-syntax-behavior.synopsis=Specifies how the Directory Server should handle operations whenever an attribute value violates the associated attribute syntax.
+property.invalid-attribute-syntax-behavior.syntax.enumeration.value.accept.synopsis=The Directory Server silently accepts attribute values that are invalid according to their associated syntax. Matching operations targeting those values may not behave as expected.
+property.invalid-attribute-syntax-behavior.syntax.enumeration.value.reject.synopsis=The Directory Server rejects attribute values that are invalid according to their associated syntax.
+property.invalid-attribute-syntax-behavior.syntax.enumeration.value.warn.synopsis=The Directory Server accepts attribute values that are invalid according to their associated syntax, but also logs a warning message to the error log. Matching operations targeting those values may not behave as expected.
+property.lookthrough-limit.synopsis=Specifies the maximum number of entries that the Directory Server should "look through" in the course of processing a search request.
+property.lookthrough-limit.description=This includes any entry that the server must examine in the course of processing the request, regardless of whether it actually matches the search criteria. A value of 0 indicates that no lookthrough limit is enforced. Note that this is the default server-wide limit, but it may be overridden on a per-user basis using the ds-rlim-lookthrough-limit operational attribute.
+property.max-allowed-client-connections.synopsis=Specifies the maximum number of client connections that may be established at any given time
+property.max-allowed-client-connections.description=A value of 0 indicates that unlimited client connection is allowed.
+property.notify-abandoned-operations.synopsis=Indicates whether the Directory Server should send a response to any operation that is interrupted via an abandon request.
+property.notify-abandoned-operations.description=The LDAP specification states that abandoned operations should not receive any response, but this may cause problems with client applications that always expect to receive a response to each request.
+property.proxied-authorization-identity-mapper.synopsis=Specifies the name of the identity mapper to map authorization ID values (using the "u:" form) provided in the proxied authorization control to the corresponding user entry.
+property.proxied-authorization-identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled.
+property.reject-unauthenticated-requests.synopsis=Indicates whether the Directory Server should reject any request (other than bind or StartTLS requests) received from a client that has not yet been authenticated, whose last authentication attempt was unsuccessful, or whose last authentication attempt used anonymous authentication.
+property.return-bind-error-messages.synopsis=Indicates whether responses for failed bind operations should include a message string providing the reason for the authentication failure.
+property.return-bind-error-messages.description=Note that these messages may include information that could potentially be used by an attacker. If this option is disabled, then these messages appears only in the server's access log.
+property.save-config-on-successful-startup.synopsis=Indicates whether the Directory Server should save a copy of its configuration whenever the startup process completes successfully.
+property.save-config-on-successful-startup.description=This ensures that the server provides a "last known good" configuration, which can be used as a reference (or copied into the active config) if the server fails to start with the current "active" configuration.
+property.server-error-result-code.synopsis=Specifies the numeric value of the result code when request processing fails due to an internal server error.
+property.single-structural-objectclass-behavior.synopsis=Specifies how the Directory Server should handle operations an entry does not contain a structural object class or contains multiple structural classes.
+property.single-structural-objectclass-behavior.syntax.enumeration.value.accept.synopsis=The Directory Server silently accepts entries that do not contain exactly one structural object class. Certain schema features that depend on the entry's structural class may not behave as expected.
+property.single-structural-objectclass-behavior.syntax.enumeration.value.reject.synopsis=The Directory Server rejects entries that do not contain exactly one structural object class.
+property.single-structural-objectclass-behavior.syntax.enumeration.value.warn.synopsis=The Directory Server accepts entries that do not contain exactly one structural object class, but also logs a warning message to the error log. Certain schema features that depend on the entry's structural class may not behave as expected.
+property.size-limit.synopsis=Specifies the maximum number of entries that the Directory Server should return to the client durin a search operation.
+property.size-limit.description=A value of 0 indicates that no size limit is enforced. Note that this is the default server-wide limit, but it may be overridden on a per-user basis using the ds-rlim-size-limit operational attribute.
+property.smtp-server.synopsis=Specifies the address (and optional port number) for a mail server that can be used to send email messages via SMTP.
+property.smtp-server.description=It may be an IP address or resolvable hostname, optionally followed by a colon and a port number.
+property.smtp-server.default-behavior.alias.synopsis=If no values are defined, then the server cannot send email via SMTP.
+property.smtp-server.syntax.string.pattern.synopsis=A hostname, optionally followed by a ":" followed by a port number.
+property.time-limit.synopsis=Specifies the maximum length of time that the Directory Server should spend processing a search operation.
+property.time-limit.description=A value of 0 seconds indicates that no time limit is enforced. Note that this is the default server-wide time limit, but it may be overridden on a per-user basis using the ds-rlim-time-limit operational attribute.
+property.workflow-configuration-mode.synopsis=Specifies the workflow configuration mode (auto vs. manual).
+property.workflow-configuration-mode.syntax.enumeration.value.auto.synopsis=In the "auto" configuration mode, there is no workflow configuration. The workflows are created automatically based on the backend configuration. There is one workflow per backend base DN.
+property.workflow-configuration-mode.syntax.enumeration.value.manual.synopsis=In the "manual" configuration mode, each workflow is created according to its description in the configuration.
+property.writability-mode.synopsis=Specifies the kinds of write operations the Directory Server can process.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=The Directory Server rejects all write operations that are requested of it, regardless of their origin.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=The Directory Server attempts to process all write operations that are requested of it, regardless of their origin.
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=The Directory Server attempts to process write operations requested as internal operations or through synchronization, but rejects any such operations requested from external clients.
diff --git a/opends/src/admin/messages/GlobalCfgDefn_zh_TW.properties b/opends/src/admin/messages/GlobalCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..5d32c25
--- /dev/null
+++ b/opends/src/admin/messages/GlobalCfgDefn_zh_TW.properties
@@ -0,0 +1,80 @@
+user-friendly-name=Global Configuration
+user-friendly-plural-name=Global Configurations
+synopsis=The Global Configuration contains properties that affect the overall operation of the OpenDS Directory Server .
+property.add-missing-rdn-attributes.synopsis=Indicates whether the Directory Server should automatically add any attribute values contained in the entry's RDN into that entry when processing an add request.
+property.allow-attribute-name-exceptions.synopsis=Indicates whether the Directory Server should allow underscores in attribute names and allow attribute names to begin with numeric digits (both of which are violations of the LDAP standards).
+property.allowed-task.synopsis=Specifies the fully-qualified name of a Java class that may be invoked in the server.
+property.allowed-task.description=Any attempt to invoke a task not included in the list of allowed tasks is rejected.
+property.allowed-task.default-behavior.alias.synopsis=If no values are defined, then the server does not allow any tasks to be invoked.
+property.bind-with-dn-requires-password.synopsis=Indicates whether the Directory Server should reject any simple bind request that contains a DN but no password.
+property.bind-with-dn-requires-password.description=Although such bind requests are technically allowed by the LDAPv3 specification (and should be treated as anonymous simple authentication), they may introduce security problems in applications that do not verify that the client actually provided a password.
+property.check-schema.synopsis=Indicates whether schema enforcement is active.
+property.check-schema.description=When schema enforcement is activated, the Directory Server ensures that all operations result in entries are valid according to the defined server schema. It is strongly recommended that this option be left enabled to prevent the inadvertent addition of invalid data into the server.
+property.default-password-policy.synopsis=Specifies the name of the password policy that is in effect for users whose entries do not specify an alternate password policy (either via a real or virtual attribute).
+property.disabled-privilege.synopsis=Specifies the name of a privilege that should not be evaluated by the server.
+property.disabled-privilege.description=If a privilege is disabled, then it is assumed that all clients (including unauthenticated clients) have that privilege.
+property.disabled-privilege.default-behavior.alias.synopsis=If no values are defined, then the server enforces all privileges.
+property.disabled-privilege.syntax.enumeration.value.backend-backup.synopsis=Allows the user to request that the server process backup tasks.
+property.disabled-privilege.syntax.enumeration.value.backend-restore.synopsis=Allows the user to request that the server process restore tasks.
+property.disabled-privilege.syntax.enumeration.value.bypass-acl.synopsis=Allows the associated user to bypass access control checks performed by the server.
+property.disabled-privilege.syntax.enumeration.value.cancel-request.synopsis=Allows the user to cancel operations in progress on other client connections.
+property.disabled-privilege.syntax.enumeration.value.config-read.synopsis=Allows the associated user to read the server configuration.
+property.disabled-privilege.syntax.enumeration.value.config-write.synopsis=Allows the associated user to update the server configuration. The config-read privilege is also required.
+property.disabled-privilege.syntax.enumeration.value.data-sync.synopsis=Allows the user to participate in data synchronization.
+property.disabled-privilege.syntax.enumeration.value.disconnect-client.synopsis=Allows the user to terminate other client connections.
+property.disabled-privilege.syntax.enumeration.value.jmx-notify.synopsis=Allows the associated user to subscribe to receive JMX notifications.
+property.disabled-privilege.syntax.enumeration.value.jmx-read.synopsis=Allows the associated user to perform JMX read operations.
+property.disabled-privilege.syntax.enumeration.value.jmx-write.synopsis=Allows the associated user to perform JMX write operations.
+property.disabled-privilege.syntax.enumeration.value.ldif-export.synopsis=Allows the user to request that the server process LDIF export tasks.
+property.disabled-privilege.syntax.enumeration.value.ldif-import.synopsis=Allows the user to request that the server process LDIF import tasks.
+property.disabled-privilege.syntax.enumeration.value.modify-acl.synopsis=Allows the associated user to modify the server's access control configuration.
+property.disabled-privilege.syntax.enumeration.value.password-reset.synopsis=Allows the user to reset user passwords.
+property.disabled-privilege.syntax.enumeration.value.privilege-change.synopsis=Allows the user to make changes to the set of defined root privileges, as well as to grant and revoke privileges for users.
+property.disabled-privilege.syntax.enumeration.value.proxied-auth.synopsis=Allows the user to use the proxied authorization control, or to perform a bind that specifies an alternate authorization identity.
+property.disabled-privilege.syntax.enumeration.value.server-restart.synopsis=Allows the user to request that the server perform an in-core restart.
+property.disabled-privilege.syntax.enumeration.value.server-shutdown.synopsis=Allows the user to request that the server shut down.
+property.disabled-privilege.syntax.enumeration.value.unindexed-search.synopsis=Allows the user to request that the server process a search that cannot be optimized using server indexes.
+property.disabled-privilege.syntax.enumeration.value.update-schema.synopsis=Allows the user to make changes to the server schema.
+property.entry-cache-preload.synopsis=Indicates whether or not to preload the entry cache on startup.
+property.etime-resolution.synopsis=Specifies the resolution to use for operation elapsed processing time (etime) measurements.
+property.etime-resolution.syntax.enumeration.value.milliseconds.synopsis=Use millisecond resolution.
+property.etime-resolution.syntax.enumeration.value.nanoseconds.synopsis=Use nanosecond resolution.
+property.idle-time-limit.synopsis=Specifies the maximum length of time that a client connection may remain established since its last completed operation.
+property.idle-time-limit.description=A value of "0 seconds" indicates that no idle time limit is enforced.
+property.invalid-attribute-syntax-behavior.synopsis=Specifies how the Directory Server should handle operations whenever an attribute value violates the associated attribute syntax.
+property.invalid-attribute-syntax-behavior.syntax.enumeration.value.accept.synopsis=The Directory Server silently accepts attribute values that are invalid according to their associated syntax. Matching operations targeting those values may not behave as expected.
+property.invalid-attribute-syntax-behavior.syntax.enumeration.value.reject.synopsis=The Directory Server rejects attribute values that are invalid according to their associated syntax.
+property.invalid-attribute-syntax-behavior.syntax.enumeration.value.warn.synopsis=The Directory Server accepts attribute values that are invalid according to their associated syntax, but also logs a warning message to the error log. Matching operations targeting those values may not behave as expected.
+property.lookthrough-limit.synopsis=Specifies the maximum number of entries that the Directory Server should "look through" in the course of processing a search request.
+property.lookthrough-limit.description=This includes any entry that the server must examine in the course of processing the request, regardless of whether it actually matches the search criteria. A value of 0 indicates that no lookthrough limit is enforced. Note that this is the default server-wide limit, but it may be overridden on a per-user basis using the ds-rlim-lookthrough-limit operational attribute.
+property.max-allowed-client-connections.synopsis=Specifies the maximum number of client connections that may be established at any given time
+property.max-allowed-client-connections.description=A value of 0 indicates that unlimited client connection is allowed.
+property.notify-abandoned-operations.synopsis=Indicates whether the Directory Server should send a response to any operation that is interrupted via an abandon request.
+property.notify-abandoned-operations.description=The LDAP specification states that abandoned operations should not receive any response, but this may cause problems with client applications that always expect to receive a response to each request.
+property.proxied-authorization-identity-mapper.synopsis=Specifies the name of the identity mapper to map authorization ID values (using the "u:" form) provided in the proxied authorization control to the corresponding user entry.
+property.proxied-authorization-identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled.
+property.reject-unauthenticated-requests.synopsis=Indicates whether the Directory Server should reject any request (other than bind or StartTLS requests) received from a client that has not yet been authenticated, whose last authentication attempt was unsuccessful, or whose last authentication attempt used anonymous authentication.
+property.return-bind-error-messages.synopsis=Indicates whether responses for failed bind operations should include a message string providing the reason for the authentication failure.
+property.return-bind-error-messages.description=Note that these messages may include information that could potentially be used by an attacker. If this option is disabled, then these messages appears only in the server's access log.
+property.save-config-on-successful-startup.synopsis=Indicates whether the Directory Server should save a copy of its configuration whenever the startup process completes successfully.
+property.save-config-on-successful-startup.description=This ensures that the server provides a "last known good" configuration, which can be used as a reference (or copied into the active config) if the server fails to start with the current "active" configuration.
+property.server-error-result-code.synopsis=Specifies the numeric value of the result code when request processing fails due to an internal server error.
+property.single-structural-objectclass-behavior.synopsis=Specifies how the Directory Server should handle operations an entry does not contain a structural object class or contains multiple structural classes.
+property.single-structural-objectclass-behavior.syntax.enumeration.value.accept.synopsis=The Directory Server silently accepts entries that do not contain exactly one structural object class. Certain schema features that depend on the entry's structural class may not behave as expected.
+property.single-structural-objectclass-behavior.syntax.enumeration.value.reject.synopsis=The Directory Server rejects entries that do not contain exactly one structural object class.
+property.single-structural-objectclass-behavior.syntax.enumeration.value.warn.synopsis=The Directory Server accepts entries that do not contain exactly one structural object class, but also logs a warning message to the error log. Certain schema features that depend on the entry's structural class may not behave as expected.
+property.size-limit.synopsis=Specifies the maximum number of entries that the Directory Server should return to the client durin a search operation.
+property.size-limit.description=A value of 0 indicates that no size limit is enforced. Note that this is the default server-wide limit, but it may be overridden on a per-user basis using the ds-rlim-size-limit operational attribute.
+property.smtp-server.synopsis=Specifies the address (and optional port number) for a mail server that can be used to send email messages via SMTP.
+property.smtp-server.description=It may be an IP address or resolvable hostname, optionally followed by a colon and a port number.
+property.smtp-server.default-behavior.alias.synopsis=If no values are defined, then the server cannot send email via SMTP.
+property.smtp-server.syntax.string.pattern.synopsis=A hostname, optionally followed by a ":" followed by a port number.
+property.time-limit.synopsis=Specifies the maximum length of time that the Directory Server should spend processing a search operation.
+property.time-limit.description=A value of 0 seconds indicates that no time limit is enforced. Note that this is the default server-wide time limit, but it may be overridden on a per-user basis using the ds-rlim-time-limit operational attribute.
+property.workflow-configuration-mode.synopsis=Specifies the workflow configuration mode (auto vs. manual).
+property.workflow-configuration-mode.syntax.enumeration.value.auto.synopsis=In the "auto" configuration mode, there is no workflow configuration. The workflows are created automatically based on the backend configuration. There is one workflow per backend base DN.
+property.workflow-configuration-mode.syntax.enumeration.value.manual.synopsis=In the "manual" configuration mode, each workflow is created according to its description in the configuration.
+property.writability-mode.synopsis=Specifies the kinds of write operations the Directory Server can process.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=The Directory Server rejects all write operations that are requested of it, regardless of their origin.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=The Directory Server attempts to process all write operations that are requested of it, regardless of their origin.
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=The Directory Server attempts to process write operations requested as internal operations or through synchronization, but rejects any such operations requested from external clients.
diff --git a/opends/src/admin/messages/GroupImplementationCfgDefn.properties b/opends/src/admin/messages/GroupImplementationCfgDefn.properties
new file mode 100644
index 0000000..2fc2e3e
--- /dev/null
+++ b/opends/src/admin/messages/GroupImplementationCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Group Implementation
+user-friendly-plural-name=Group Implementations
+synopsis=Group Implementations define named collections of users.
+description=Different group implementations may have different ways of determining membership. For example, some groups may explicitly list the members, and/or they may dynamically determine membership.
+property.enabled.synopsis=Indicates whether the Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Group Implementation implementation.
diff --git a/opends/src/admin/messages/GroupImplementationCfgDefn_de.properties b/opends/src/admin/messages/GroupImplementationCfgDefn_de.properties
new file mode 100644
index 0000000..2fc2e3e
--- /dev/null
+++ b/opends/src/admin/messages/GroupImplementationCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Group Implementation
+user-friendly-plural-name=Group Implementations
+synopsis=Group Implementations define named collections of users.
+description=Different group implementations may have different ways of determining membership. For example, some groups may explicitly list the members, and/or they may dynamically determine membership.
+property.enabled.synopsis=Indicates whether the Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Group Implementation implementation.
diff --git a/opends/src/admin/messages/GroupImplementationCfgDefn_es.properties b/opends/src/admin/messages/GroupImplementationCfgDefn_es.properties
new file mode 100644
index 0000000..2fc2e3e
--- /dev/null
+++ b/opends/src/admin/messages/GroupImplementationCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Group Implementation
+user-friendly-plural-name=Group Implementations
+synopsis=Group Implementations define named collections of users.
+description=Different group implementations may have different ways of determining membership. For example, some groups may explicitly list the members, and/or they may dynamically determine membership.
+property.enabled.synopsis=Indicates whether the Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Group Implementation implementation.
diff --git a/opends/src/admin/messages/GroupImplementationCfgDefn_fr.properties b/opends/src/admin/messages/GroupImplementationCfgDefn_fr.properties
new file mode 100644
index 0000000..2fc2e3e
--- /dev/null
+++ b/opends/src/admin/messages/GroupImplementationCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Group Implementation
+user-friendly-plural-name=Group Implementations
+synopsis=Group Implementations define named collections of users.
+description=Different group implementations may have different ways of determining membership. For example, some groups may explicitly list the members, and/or they may dynamically determine membership.
+property.enabled.synopsis=Indicates whether the Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Group Implementation implementation.
diff --git a/opends/src/admin/messages/GroupImplementationCfgDefn_ja.properties b/opends/src/admin/messages/GroupImplementationCfgDefn_ja.properties
new file mode 100644
index 0000000..2fc2e3e
--- /dev/null
+++ b/opends/src/admin/messages/GroupImplementationCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Group Implementation
+user-friendly-plural-name=Group Implementations
+synopsis=Group Implementations define named collections of users.
+description=Different group implementations may have different ways of determining membership. For example, some groups may explicitly list the members, and/or they may dynamically determine membership.
+property.enabled.synopsis=Indicates whether the Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Group Implementation implementation.
diff --git a/opends/src/admin/messages/GroupImplementationCfgDefn_ko.properties b/opends/src/admin/messages/GroupImplementationCfgDefn_ko.properties
new file mode 100644
index 0000000..2fc2e3e
--- /dev/null
+++ b/opends/src/admin/messages/GroupImplementationCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Group Implementation
+user-friendly-plural-name=Group Implementations
+synopsis=Group Implementations define named collections of users.
+description=Different group implementations may have different ways of determining membership. For example, some groups may explicitly list the members, and/or they may dynamically determine membership.
+property.enabled.synopsis=Indicates whether the Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Group Implementation implementation.
diff --git a/opends/src/admin/messages/GroupImplementationCfgDefn_zh_CN.properties b/opends/src/admin/messages/GroupImplementationCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..2fc2e3e
--- /dev/null
+++ b/opends/src/admin/messages/GroupImplementationCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Group Implementation
+user-friendly-plural-name=Group Implementations
+synopsis=Group Implementations define named collections of users.
+description=Different group implementations may have different ways of determining membership. For example, some groups may explicitly list the members, and/or they may dynamically determine membership.
+property.enabled.synopsis=Indicates whether the Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Group Implementation implementation.
diff --git a/opends/src/admin/messages/GroupImplementationCfgDefn_zh_TW.properties b/opends/src/admin/messages/GroupImplementationCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..2fc2e3e
--- /dev/null
+++ b/opends/src/admin/messages/GroupImplementationCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Group Implementation
+user-friendly-plural-name=Group Implementations
+synopsis=Group Implementations define named collections of users.
+description=Different group implementations may have different ways of determining membership. For example, some groups may explicitly list the members, and/or they may dynamically determine membership.
+property.enabled.synopsis=Indicates whether the Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Group Implementation implementation.
diff --git a/opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn.properties b/opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn.properties
new file mode 100644
index 0000000..0bf7da8
--- /dev/null
+++ b/opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Has Subordinates Virtual Attribute
+user-friendly-plural-name=Has Subordinates Virtual Attributes
+synopsis=The Has Subordinates Virtual Attribute generates a virtual attribute that indicates whether the entry has any subordinate entries.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Has Subordinates Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_de.properties b/opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_de.properties
new file mode 100644
index 0000000..0bf7da8
--- /dev/null
+++ b/opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_de.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Has Subordinates Virtual Attribute
+user-friendly-plural-name=Has Subordinates Virtual Attributes
+synopsis=The Has Subordinates Virtual Attribute generates a virtual attribute that indicates whether the entry has any subordinate entries.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Has Subordinates Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_es.properties b/opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_es.properties
new file mode 100644
index 0000000..0bf7da8
--- /dev/null
+++ b/opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_es.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Has Subordinates Virtual Attribute
+user-friendly-plural-name=Has Subordinates Virtual Attributes
+synopsis=The Has Subordinates Virtual Attribute generates a virtual attribute that indicates whether the entry has any subordinate entries.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Has Subordinates Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_fr.properties b/opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_fr.properties
new file mode 100644
index 0000000..0bf7da8
--- /dev/null
+++ b/opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_fr.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Has Subordinates Virtual Attribute
+user-friendly-plural-name=Has Subordinates Virtual Attributes
+synopsis=The Has Subordinates Virtual Attribute generates a virtual attribute that indicates whether the entry has any subordinate entries.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Has Subordinates Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_ja.properties b/opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_ja.properties
new file mode 100644
index 0000000..0bf7da8
--- /dev/null
+++ b/opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_ja.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Has Subordinates Virtual Attribute
+user-friendly-plural-name=Has Subordinates Virtual Attributes
+synopsis=The Has Subordinates Virtual Attribute generates a virtual attribute that indicates whether the entry has any subordinate entries.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Has Subordinates Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_ko.properties b/opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_ko.properties
new file mode 100644
index 0000000..0bf7da8
--- /dev/null
+++ b/opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_ko.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Has Subordinates Virtual Attribute
+user-friendly-plural-name=Has Subordinates Virtual Attributes
+synopsis=The Has Subordinates Virtual Attribute generates a virtual attribute that indicates whether the entry has any subordinate entries.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Has Subordinates Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_zh_CN.properties b/opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..0bf7da8
--- /dev/null
+++ b/opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_zh_CN.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Has Subordinates Virtual Attribute
+user-friendly-plural-name=Has Subordinates Virtual Attributes
+synopsis=The Has Subordinates Virtual Attribute generates a virtual attribute that indicates whether the entry has any subordinate entries.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Has Subordinates Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_zh_TW.properties b/opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..0bf7da8
--- /dev/null
+++ b/opends/src/admin/messages/HasSubordinatesVirtualAttributeCfgDefn_zh_TW.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Has Subordinates Virtual Attribute
+user-friendly-plural-name=Has Subordinates Virtual Attributes
+synopsis=The Has Subordinates Virtual Attribute generates a virtual attribute that indicates whether the entry has any subordinate entries.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Has Subordinates Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/IdentityMapperCfgDefn.properties b/opends/src/admin/messages/IdentityMapperCfgDefn.properties
new file mode 100644
index 0000000..d7d663d
--- /dev/null
+++ b/opends/src/admin/messages/IdentityMapperCfgDefn.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Identity Mapper
+user-friendly-plural-name=Identity Mappers
+synopsis=Identity Mappers are responsible for establishing a mapping between an identifier string provided by a client, and the entry for the user that corresponds to that identifier. Identity Mappers are used to process several SASL mechanisms to map an authorization ID (e.g., a Kerberos principal when using GSSAPI) to a directory user. They are also used when processing requests with the proxied authorization control.
+property.enabled.synopsis=Indicates whether the Identity Mapper is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Identity Mapper implementation.
diff --git a/opends/src/admin/messages/IdentityMapperCfgDefn_de.properties b/opends/src/admin/messages/IdentityMapperCfgDefn_de.properties
new file mode 100644
index 0000000..d7d663d
--- /dev/null
+++ b/opends/src/admin/messages/IdentityMapperCfgDefn_de.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Identity Mapper
+user-friendly-plural-name=Identity Mappers
+synopsis=Identity Mappers are responsible for establishing a mapping between an identifier string provided by a client, and the entry for the user that corresponds to that identifier. Identity Mappers are used to process several SASL mechanisms to map an authorization ID (e.g., a Kerberos principal when using GSSAPI) to a directory user. They are also used when processing requests with the proxied authorization control.
+property.enabled.synopsis=Indicates whether the Identity Mapper is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Identity Mapper implementation.
diff --git a/opends/src/admin/messages/IdentityMapperCfgDefn_es.properties b/opends/src/admin/messages/IdentityMapperCfgDefn_es.properties
new file mode 100644
index 0000000..d7d663d
--- /dev/null
+++ b/opends/src/admin/messages/IdentityMapperCfgDefn_es.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Identity Mapper
+user-friendly-plural-name=Identity Mappers
+synopsis=Identity Mappers are responsible for establishing a mapping between an identifier string provided by a client, and the entry for the user that corresponds to that identifier. Identity Mappers are used to process several SASL mechanisms to map an authorization ID (e.g., a Kerberos principal when using GSSAPI) to a directory user. They are also used when processing requests with the proxied authorization control.
+property.enabled.synopsis=Indicates whether the Identity Mapper is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Identity Mapper implementation.
diff --git a/opends/src/admin/messages/IdentityMapperCfgDefn_fr.properties b/opends/src/admin/messages/IdentityMapperCfgDefn_fr.properties
new file mode 100644
index 0000000..d7d663d
--- /dev/null
+++ b/opends/src/admin/messages/IdentityMapperCfgDefn_fr.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Identity Mapper
+user-friendly-plural-name=Identity Mappers
+synopsis=Identity Mappers are responsible for establishing a mapping between an identifier string provided by a client, and the entry for the user that corresponds to that identifier. Identity Mappers are used to process several SASL mechanisms to map an authorization ID (e.g., a Kerberos principal when using GSSAPI) to a directory user. They are also used when processing requests with the proxied authorization control.
+property.enabled.synopsis=Indicates whether the Identity Mapper is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Identity Mapper implementation.
diff --git a/opends/src/admin/messages/IdentityMapperCfgDefn_ja.properties b/opends/src/admin/messages/IdentityMapperCfgDefn_ja.properties
new file mode 100644
index 0000000..d7d663d
--- /dev/null
+++ b/opends/src/admin/messages/IdentityMapperCfgDefn_ja.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Identity Mapper
+user-friendly-plural-name=Identity Mappers
+synopsis=Identity Mappers are responsible for establishing a mapping between an identifier string provided by a client, and the entry for the user that corresponds to that identifier. Identity Mappers are used to process several SASL mechanisms to map an authorization ID (e.g., a Kerberos principal when using GSSAPI) to a directory user. They are also used when processing requests with the proxied authorization control.
+property.enabled.synopsis=Indicates whether the Identity Mapper is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Identity Mapper implementation.
diff --git a/opends/src/admin/messages/IdentityMapperCfgDefn_ko.properties b/opends/src/admin/messages/IdentityMapperCfgDefn_ko.properties
new file mode 100644
index 0000000..d7d663d
--- /dev/null
+++ b/opends/src/admin/messages/IdentityMapperCfgDefn_ko.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Identity Mapper
+user-friendly-plural-name=Identity Mappers
+synopsis=Identity Mappers are responsible for establishing a mapping between an identifier string provided by a client, and the entry for the user that corresponds to that identifier. Identity Mappers are used to process several SASL mechanisms to map an authorization ID (e.g., a Kerberos principal when using GSSAPI) to a directory user. They are also used when processing requests with the proxied authorization control.
+property.enabled.synopsis=Indicates whether the Identity Mapper is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Identity Mapper implementation.
diff --git a/opends/src/admin/messages/IdentityMapperCfgDefn_zh_CN.properties b/opends/src/admin/messages/IdentityMapperCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..d7d663d
--- /dev/null
+++ b/opends/src/admin/messages/IdentityMapperCfgDefn_zh_CN.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Identity Mapper
+user-friendly-plural-name=Identity Mappers
+synopsis=Identity Mappers are responsible for establishing a mapping between an identifier string provided by a client, and the entry for the user that corresponds to that identifier. Identity Mappers are used to process several SASL mechanisms to map an authorization ID (e.g., a Kerberos principal when using GSSAPI) to a directory user. They are also used when processing requests with the proxied authorization control.
+property.enabled.synopsis=Indicates whether the Identity Mapper is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Identity Mapper implementation.
diff --git a/opends/src/admin/messages/IdentityMapperCfgDefn_zh_TW.properties b/opends/src/admin/messages/IdentityMapperCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..d7d663d
--- /dev/null
+++ b/opends/src/admin/messages/IdentityMapperCfgDefn_zh_TW.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Identity Mapper
+user-friendly-plural-name=Identity Mappers
+synopsis=Identity Mappers are responsible for establishing a mapping between an identifier string provided by a client, and the entry for the user that corresponds to that identifier. Identity Mappers are used to process several SASL mechanisms to map an authorization ID (e.g., a Kerberos principal when using GSSAPI) to a directory user. They are also used when processing requests with the proxied authorization control.
+property.enabled.synopsis=Indicates whether the Identity Mapper is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Identity Mapper implementation.
diff --git a/opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn.properties b/opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn.properties
new file mode 100644
index 0000000..392c0d2
--- /dev/null
+++ b/opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Is Member Of Virtual Attribute
+user-friendly-plural-name=Is Member Of Virtual Attributes
+synopsis=The Is Member Of Virtual Attribute generates the isMemberOf operational attribute, which contains the DNs of the groups in which the user is a member.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Is Member Of Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_de.properties b/opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_de.properties
new file mode 100644
index 0000000..392c0d2
--- /dev/null
+++ b/opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_de.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Is Member Of Virtual Attribute
+user-friendly-plural-name=Is Member Of Virtual Attributes
+synopsis=The Is Member Of Virtual Attribute generates the isMemberOf operational attribute, which contains the DNs of the groups in which the user is a member.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Is Member Of Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_es.properties b/opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_es.properties
new file mode 100644
index 0000000..392c0d2
--- /dev/null
+++ b/opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_es.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Is Member Of Virtual Attribute
+user-friendly-plural-name=Is Member Of Virtual Attributes
+synopsis=The Is Member Of Virtual Attribute generates the isMemberOf operational attribute, which contains the DNs of the groups in which the user is a member.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Is Member Of Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_fr.properties b/opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_fr.properties
new file mode 100644
index 0000000..392c0d2
--- /dev/null
+++ b/opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_fr.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Is Member Of Virtual Attribute
+user-friendly-plural-name=Is Member Of Virtual Attributes
+synopsis=The Is Member Of Virtual Attribute generates the isMemberOf operational attribute, which contains the DNs of the groups in which the user is a member.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Is Member Of Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_ja.properties b/opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_ja.properties
new file mode 100644
index 0000000..392c0d2
--- /dev/null
+++ b/opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_ja.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Is Member Of Virtual Attribute
+user-friendly-plural-name=Is Member Of Virtual Attributes
+synopsis=The Is Member Of Virtual Attribute generates the isMemberOf operational attribute, which contains the DNs of the groups in which the user is a member.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Is Member Of Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_ko.properties b/opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_ko.properties
new file mode 100644
index 0000000..392c0d2
--- /dev/null
+++ b/opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_ko.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Is Member Of Virtual Attribute
+user-friendly-plural-name=Is Member Of Virtual Attributes
+synopsis=The Is Member Of Virtual Attribute generates the isMemberOf operational attribute, which contains the DNs of the groups in which the user is a member.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Is Member Of Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_zh_CN.properties b/opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..392c0d2
--- /dev/null
+++ b/opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_zh_CN.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Is Member Of Virtual Attribute
+user-friendly-plural-name=Is Member Of Virtual Attributes
+synopsis=The Is Member Of Virtual Attribute generates the isMemberOf operational attribute, which contains the DNs of the groups in which the user is a member.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Is Member Of Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_zh_TW.properties b/opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..392c0d2
--- /dev/null
+++ b/opends/src/admin/messages/IsMemberOfVirtualAttributeCfgDefn_zh_TW.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Is Member Of Virtual Attribute
+user-friendly-plural-name=Is Member Of Virtual Attributes
+synopsis=The Is Member Of Virtual Attribute generates the isMemberOf operational attribute, which contains the DNs of the groups in which the user is a member.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Is Member Of Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/JMXAlertHandlerCfgDefn.properties b/opends/src/admin/messages/JMXAlertHandlerCfgDefn.properties
new file mode 100644
index 0000000..8cf1191
--- /dev/null
+++ b/opends/src/admin/messages/JMXAlertHandlerCfgDefn.properties
@@ -0,0 +1,11 @@
+user-friendly-name=JMX Alert Handler
+user-friendly-plural-name=JMX Alert Handlers
+synopsis=The JMX Alert Handler is used to generate JMX notifications to alert administrators of significant events that occur within the server.
+property.disabled-alert-type.synopsis=Specifies the names of the alert types that are disabled for this alert handler.
+property.disabled-alert-type.description=If there are any values for this attribute, then no alerts with any of the specified types are allowed. If there are no values for this attribute, then only alerts with a type included in the set of enabled alert types are allowed, or if there are no values for the enabled alert types option, then all alert types are allowed.
+property.disabled-alert-type.default-behavior.alias.synopsis=If there is a set of enabled alert types, then only alerts with one of those types are allowed. Otherwise, all alerts are allowed.
+property.enabled.synopsis=Indicates whether the JMX Alert Handler is enabled.
+property.enabled-alert-type.synopsis=Specifies the names of the alert types that are enabled for this alert handler.
+property.enabled-alert-type.description=If there are any values for this attribute, then only alerts with one of the specified types are allowed (unless they are also included in the disabled alert types). If there are no values for this attribute, then any alert with a type not included in the list of disabled alert types is allowed.
+property.enabled-alert-type.default-behavior.alias.synopsis=All alerts with types not included in the set of disabled alert types are allowed.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the JMX Alert Handler implementation.
diff --git a/opends/src/admin/messages/JMXAlertHandlerCfgDefn_de.properties b/opends/src/admin/messages/JMXAlertHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..8cf1191
--- /dev/null
+++ b/opends/src/admin/messages/JMXAlertHandlerCfgDefn_de.properties
@@ -0,0 +1,11 @@
+user-friendly-name=JMX Alert Handler
+user-friendly-plural-name=JMX Alert Handlers
+synopsis=The JMX Alert Handler is used to generate JMX notifications to alert administrators of significant events that occur within the server.
+property.disabled-alert-type.synopsis=Specifies the names of the alert types that are disabled for this alert handler.
+property.disabled-alert-type.description=If there are any values for this attribute, then no alerts with any of the specified types are allowed. If there are no values for this attribute, then only alerts with a type included in the set of enabled alert types are allowed, or if there are no values for the enabled alert types option, then all alert types are allowed.
+property.disabled-alert-type.default-behavior.alias.synopsis=If there is a set of enabled alert types, then only alerts with one of those types are allowed. Otherwise, all alerts are allowed.
+property.enabled.synopsis=Indicates whether the JMX Alert Handler is enabled.
+property.enabled-alert-type.synopsis=Specifies the names of the alert types that are enabled for this alert handler.
+property.enabled-alert-type.description=If there are any values for this attribute, then only alerts with one of the specified types are allowed (unless they are also included in the disabled alert types). If there are no values for this attribute, then any alert with a type not included in the list of disabled alert types is allowed.
+property.enabled-alert-type.default-behavior.alias.synopsis=All alerts with types not included in the set of disabled alert types are allowed.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the JMX Alert Handler implementation.
diff --git a/opends/src/admin/messages/JMXAlertHandlerCfgDefn_es.properties b/opends/src/admin/messages/JMXAlertHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..8cf1191
--- /dev/null
+++ b/opends/src/admin/messages/JMXAlertHandlerCfgDefn_es.properties
@@ -0,0 +1,11 @@
+user-friendly-name=JMX Alert Handler
+user-friendly-plural-name=JMX Alert Handlers
+synopsis=The JMX Alert Handler is used to generate JMX notifications to alert administrators of significant events that occur within the server.
+property.disabled-alert-type.synopsis=Specifies the names of the alert types that are disabled for this alert handler.
+property.disabled-alert-type.description=If there are any values for this attribute, then no alerts with any of the specified types are allowed. If there are no values for this attribute, then only alerts with a type included in the set of enabled alert types are allowed, or if there are no values for the enabled alert types option, then all alert types are allowed.
+property.disabled-alert-type.default-behavior.alias.synopsis=If there is a set of enabled alert types, then only alerts with one of those types are allowed. Otherwise, all alerts are allowed.
+property.enabled.synopsis=Indicates whether the JMX Alert Handler is enabled.
+property.enabled-alert-type.synopsis=Specifies the names of the alert types that are enabled for this alert handler.
+property.enabled-alert-type.description=If there are any values for this attribute, then only alerts with one of the specified types are allowed (unless they are also included in the disabled alert types). If there are no values for this attribute, then any alert with a type not included in the list of disabled alert types is allowed.
+property.enabled-alert-type.default-behavior.alias.synopsis=All alerts with types not included in the set of disabled alert types are allowed.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the JMX Alert Handler implementation.
diff --git a/opends/src/admin/messages/JMXAlertHandlerCfgDefn_fr.properties b/opends/src/admin/messages/JMXAlertHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..8cf1191
--- /dev/null
+++ b/opends/src/admin/messages/JMXAlertHandlerCfgDefn_fr.properties
@@ -0,0 +1,11 @@
+user-friendly-name=JMX Alert Handler
+user-friendly-plural-name=JMX Alert Handlers
+synopsis=The JMX Alert Handler is used to generate JMX notifications to alert administrators of significant events that occur within the server.
+property.disabled-alert-type.synopsis=Specifies the names of the alert types that are disabled for this alert handler.
+property.disabled-alert-type.description=If there are any values for this attribute, then no alerts with any of the specified types are allowed. If there are no values for this attribute, then only alerts with a type included in the set of enabled alert types are allowed, or if there are no values for the enabled alert types option, then all alert types are allowed.
+property.disabled-alert-type.default-behavior.alias.synopsis=If there is a set of enabled alert types, then only alerts with one of those types are allowed. Otherwise, all alerts are allowed.
+property.enabled.synopsis=Indicates whether the JMX Alert Handler is enabled.
+property.enabled-alert-type.synopsis=Specifies the names of the alert types that are enabled for this alert handler.
+property.enabled-alert-type.description=If there are any values for this attribute, then only alerts with one of the specified types are allowed (unless they are also included in the disabled alert types). If there are no values for this attribute, then any alert with a type not included in the list of disabled alert types is allowed.
+property.enabled-alert-type.default-behavior.alias.synopsis=All alerts with types not included in the set of disabled alert types are allowed.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the JMX Alert Handler implementation.
diff --git a/opends/src/admin/messages/JMXAlertHandlerCfgDefn_ja.properties b/opends/src/admin/messages/JMXAlertHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..8cf1191
--- /dev/null
+++ b/opends/src/admin/messages/JMXAlertHandlerCfgDefn_ja.properties
@@ -0,0 +1,11 @@
+user-friendly-name=JMX Alert Handler
+user-friendly-plural-name=JMX Alert Handlers
+synopsis=The JMX Alert Handler is used to generate JMX notifications to alert administrators of significant events that occur within the server.
+property.disabled-alert-type.synopsis=Specifies the names of the alert types that are disabled for this alert handler.
+property.disabled-alert-type.description=If there are any values for this attribute, then no alerts with any of the specified types are allowed. If there are no values for this attribute, then only alerts with a type included in the set of enabled alert types are allowed, or if there are no values for the enabled alert types option, then all alert types are allowed.
+property.disabled-alert-type.default-behavior.alias.synopsis=If there is a set of enabled alert types, then only alerts with one of those types are allowed. Otherwise, all alerts are allowed.
+property.enabled.synopsis=Indicates whether the JMX Alert Handler is enabled.
+property.enabled-alert-type.synopsis=Specifies the names of the alert types that are enabled for this alert handler.
+property.enabled-alert-type.description=If there are any values for this attribute, then only alerts with one of the specified types are allowed (unless they are also included in the disabled alert types). If there are no values for this attribute, then any alert with a type not included in the list of disabled alert types is allowed.
+property.enabled-alert-type.default-behavior.alias.synopsis=All alerts with types not included in the set of disabled alert types are allowed.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the JMX Alert Handler implementation.
diff --git a/opends/src/admin/messages/JMXAlertHandlerCfgDefn_ko.properties b/opends/src/admin/messages/JMXAlertHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..8cf1191
--- /dev/null
+++ b/opends/src/admin/messages/JMXAlertHandlerCfgDefn_ko.properties
@@ -0,0 +1,11 @@
+user-friendly-name=JMX Alert Handler
+user-friendly-plural-name=JMX Alert Handlers
+synopsis=The JMX Alert Handler is used to generate JMX notifications to alert administrators of significant events that occur within the server.
+property.disabled-alert-type.synopsis=Specifies the names of the alert types that are disabled for this alert handler.
+property.disabled-alert-type.description=If there are any values for this attribute, then no alerts with any of the specified types are allowed. If there are no values for this attribute, then only alerts with a type included in the set of enabled alert types are allowed, or if there are no values for the enabled alert types option, then all alert types are allowed.
+property.disabled-alert-type.default-behavior.alias.synopsis=If there is a set of enabled alert types, then only alerts with one of those types are allowed. Otherwise, all alerts are allowed.
+property.enabled.synopsis=Indicates whether the JMX Alert Handler is enabled.
+property.enabled-alert-type.synopsis=Specifies the names of the alert types that are enabled for this alert handler.
+property.enabled-alert-type.description=If there are any values for this attribute, then only alerts with one of the specified types are allowed (unless they are also included in the disabled alert types). If there are no values for this attribute, then any alert with a type not included in the list of disabled alert types is allowed.
+property.enabled-alert-type.default-behavior.alias.synopsis=All alerts with types not included in the set of disabled alert types are allowed.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the JMX Alert Handler implementation.
diff --git a/opends/src/admin/messages/JMXAlertHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/JMXAlertHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..8cf1191
--- /dev/null
+++ b/opends/src/admin/messages/JMXAlertHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,11 @@
+user-friendly-name=JMX Alert Handler
+user-friendly-plural-name=JMX Alert Handlers
+synopsis=The JMX Alert Handler is used to generate JMX notifications to alert administrators of significant events that occur within the server.
+property.disabled-alert-type.synopsis=Specifies the names of the alert types that are disabled for this alert handler.
+property.disabled-alert-type.description=If there are any values for this attribute, then no alerts with any of the specified types are allowed. If there are no values for this attribute, then only alerts with a type included in the set of enabled alert types are allowed, or if there are no values for the enabled alert types option, then all alert types are allowed.
+property.disabled-alert-type.default-behavior.alias.synopsis=If there is a set of enabled alert types, then only alerts with one of those types are allowed. Otherwise, all alerts are allowed.
+property.enabled.synopsis=Indicates whether the JMX Alert Handler is enabled.
+property.enabled-alert-type.synopsis=Specifies the names of the alert types that are enabled for this alert handler.
+property.enabled-alert-type.description=If there are any values for this attribute, then only alerts with one of the specified types are allowed (unless they are also included in the disabled alert types). If there are no values for this attribute, then any alert with a type not included in the list of disabled alert types is allowed.
+property.enabled-alert-type.default-behavior.alias.synopsis=All alerts with types not included in the set of disabled alert types are allowed.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the JMX Alert Handler implementation.
diff --git a/opends/src/admin/messages/JMXAlertHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/JMXAlertHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..8cf1191
--- /dev/null
+++ b/opends/src/admin/messages/JMXAlertHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,11 @@
+user-friendly-name=JMX Alert Handler
+user-friendly-plural-name=JMX Alert Handlers
+synopsis=The JMX Alert Handler is used to generate JMX notifications to alert administrators of significant events that occur within the server.
+property.disabled-alert-type.synopsis=Specifies the names of the alert types that are disabled for this alert handler.
+property.disabled-alert-type.description=If there are any values for this attribute, then no alerts with any of the specified types are allowed. If there are no values for this attribute, then only alerts with a type included in the set of enabled alert types are allowed, or if there are no values for the enabled alert types option, then all alert types are allowed.
+property.disabled-alert-type.default-behavior.alias.synopsis=If there is a set of enabled alert types, then only alerts with one of those types are allowed. Otherwise, all alerts are allowed.
+property.enabled.synopsis=Indicates whether the JMX Alert Handler is enabled.
+property.enabled-alert-type.synopsis=Specifies the names of the alert types that are enabled for this alert handler.
+property.enabled-alert-type.description=If there are any values for this attribute, then only alerts with one of the specified types are allowed (unless they are also included in the disabled alert types). If there are no values for this attribute, then any alert with a type not included in the list of disabled alert types is allowed.
+property.enabled-alert-type.default-behavior.alias.synopsis=All alerts with types not included in the set of disabled alert types are allowed.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the JMX Alert Handler implementation.
diff --git a/opends/src/admin/messages/JMXConnectionHandlerCfgDefn.properties b/opends/src/admin/messages/JMXConnectionHandlerCfgDefn.properties
new file mode 100644
index 0000000..8985984
--- /dev/null
+++ b/opends/src/admin/messages/JMXConnectionHandlerCfgDefn.properties
@@ -0,0 +1,24 @@
+user-friendly-name=JMX Connection Handler
+user-friendly-plural-name=JMX Connection Handlers
+synopsis=The JMX Connection Handler is used to interact with clients using the Java Management Extensions (JMX) protocol.
+constraint.1.synopsis=A Key Manager Provider must be specified when this JMX Connection Handler is enabled and it is configured to use SSL.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the JMX Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the JMX Connection Handler implementation.
+property.key-manager-provider.synopsis=Specifies the name of the key manager that should be used with this JMX Connection Handler .
+property.key-manager-provider.requires-admin-action.synopsis=Changes to this property take effect immediately, but only for subsequent attempts to access the key manager provider for associated client connections.
+property.key-manager-provider.syntax.aggregation.constraint-synopsis=The referenced key manager provider must be enabled when the JMX Connection Handler is enabled and configured to use SSL.
+property.listen-port.synopsis=Specifies the port number on which the JMX Connection Handler will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the JMX Connection Handler should use when performing SSL communication.
+property.ssl-cert-nickname.description=This is only applicable when the JMX Connection Handler is configured to use SSL.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.use-ssl.synopsis=Indicates whether the JMX Connection Handler should use SSL.
+property.use-ssl.description=If enabled, the JMX Connection Handler will use SSL to encrypt communication with the clients.
diff --git a/opends/src/admin/messages/JMXConnectionHandlerCfgDefn_de.properties b/opends/src/admin/messages/JMXConnectionHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..8985984
--- /dev/null
+++ b/opends/src/admin/messages/JMXConnectionHandlerCfgDefn_de.properties
@@ -0,0 +1,24 @@
+user-friendly-name=JMX Connection Handler
+user-friendly-plural-name=JMX Connection Handlers
+synopsis=The JMX Connection Handler is used to interact with clients using the Java Management Extensions (JMX) protocol.
+constraint.1.synopsis=A Key Manager Provider must be specified when this JMX Connection Handler is enabled and it is configured to use SSL.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the JMX Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the JMX Connection Handler implementation.
+property.key-manager-provider.synopsis=Specifies the name of the key manager that should be used with this JMX Connection Handler .
+property.key-manager-provider.requires-admin-action.synopsis=Changes to this property take effect immediately, but only for subsequent attempts to access the key manager provider for associated client connections.
+property.key-manager-provider.syntax.aggregation.constraint-synopsis=The referenced key manager provider must be enabled when the JMX Connection Handler is enabled and configured to use SSL.
+property.listen-port.synopsis=Specifies the port number on which the JMX Connection Handler will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the JMX Connection Handler should use when performing SSL communication.
+property.ssl-cert-nickname.description=This is only applicable when the JMX Connection Handler is configured to use SSL.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.use-ssl.synopsis=Indicates whether the JMX Connection Handler should use SSL.
+property.use-ssl.description=If enabled, the JMX Connection Handler will use SSL to encrypt communication with the clients.
diff --git a/opends/src/admin/messages/JMXConnectionHandlerCfgDefn_es.properties b/opends/src/admin/messages/JMXConnectionHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..8985984
--- /dev/null
+++ b/opends/src/admin/messages/JMXConnectionHandlerCfgDefn_es.properties
@@ -0,0 +1,24 @@
+user-friendly-name=JMX Connection Handler
+user-friendly-plural-name=JMX Connection Handlers
+synopsis=The JMX Connection Handler is used to interact with clients using the Java Management Extensions (JMX) protocol.
+constraint.1.synopsis=A Key Manager Provider must be specified when this JMX Connection Handler is enabled and it is configured to use SSL.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the JMX Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the JMX Connection Handler implementation.
+property.key-manager-provider.synopsis=Specifies the name of the key manager that should be used with this JMX Connection Handler .
+property.key-manager-provider.requires-admin-action.synopsis=Changes to this property take effect immediately, but only for subsequent attempts to access the key manager provider for associated client connections.
+property.key-manager-provider.syntax.aggregation.constraint-synopsis=The referenced key manager provider must be enabled when the JMX Connection Handler is enabled and configured to use SSL.
+property.listen-port.synopsis=Specifies the port number on which the JMX Connection Handler will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the JMX Connection Handler should use when performing SSL communication.
+property.ssl-cert-nickname.description=This is only applicable when the JMX Connection Handler is configured to use SSL.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.use-ssl.synopsis=Indicates whether the JMX Connection Handler should use SSL.
+property.use-ssl.description=If enabled, the JMX Connection Handler will use SSL to encrypt communication with the clients.
diff --git a/opends/src/admin/messages/JMXConnectionHandlerCfgDefn_fr.properties b/opends/src/admin/messages/JMXConnectionHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..8985984
--- /dev/null
+++ b/opends/src/admin/messages/JMXConnectionHandlerCfgDefn_fr.properties
@@ -0,0 +1,24 @@
+user-friendly-name=JMX Connection Handler
+user-friendly-plural-name=JMX Connection Handlers
+synopsis=The JMX Connection Handler is used to interact with clients using the Java Management Extensions (JMX) protocol.
+constraint.1.synopsis=A Key Manager Provider must be specified when this JMX Connection Handler is enabled and it is configured to use SSL.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the JMX Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the JMX Connection Handler implementation.
+property.key-manager-provider.synopsis=Specifies the name of the key manager that should be used with this JMX Connection Handler .
+property.key-manager-provider.requires-admin-action.synopsis=Changes to this property take effect immediately, but only for subsequent attempts to access the key manager provider for associated client connections.
+property.key-manager-provider.syntax.aggregation.constraint-synopsis=The referenced key manager provider must be enabled when the JMX Connection Handler is enabled and configured to use SSL.
+property.listen-port.synopsis=Specifies the port number on which the JMX Connection Handler will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the JMX Connection Handler should use when performing SSL communication.
+property.ssl-cert-nickname.description=This is only applicable when the JMX Connection Handler is configured to use SSL.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.use-ssl.synopsis=Indicates whether the JMX Connection Handler should use SSL.
+property.use-ssl.description=If enabled, the JMX Connection Handler will use SSL to encrypt communication with the clients.
diff --git a/opends/src/admin/messages/JMXConnectionHandlerCfgDefn_ja.properties b/opends/src/admin/messages/JMXConnectionHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..8985984
--- /dev/null
+++ b/opends/src/admin/messages/JMXConnectionHandlerCfgDefn_ja.properties
@@ -0,0 +1,24 @@
+user-friendly-name=JMX Connection Handler
+user-friendly-plural-name=JMX Connection Handlers
+synopsis=The JMX Connection Handler is used to interact with clients using the Java Management Extensions (JMX) protocol.
+constraint.1.synopsis=A Key Manager Provider must be specified when this JMX Connection Handler is enabled and it is configured to use SSL.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the JMX Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the JMX Connection Handler implementation.
+property.key-manager-provider.synopsis=Specifies the name of the key manager that should be used with this JMX Connection Handler .
+property.key-manager-provider.requires-admin-action.synopsis=Changes to this property take effect immediately, but only for subsequent attempts to access the key manager provider for associated client connections.
+property.key-manager-provider.syntax.aggregation.constraint-synopsis=The referenced key manager provider must be enabled when the JMX Connection Handler is enabled and configured to use SSL.
+property.listen-port.synopsis=Specifies the port number on which the JMX Connection Handler will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the JMX Connection Handler should use when performing SSL communication.
+property.ssl-cert-nickname.description=This is only applicable when the JMX Connection Handler is configured to use SSL.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.use-ssl.synopsis=Indicates whether the JMX Connection Handler should use SSL.
+property.use-ssl.description=If enabled, the JMX Connection Handler will use SSL to encrypt communication with the clients.
diff --git a/opends/src/admin/messages/JMXConnectionHandlerCfgDefn_ko.properties b/opends/src/admin/messages/JMXConnectionHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..8985984
--- /dev/null
+++ b/opends/src/admin/messages/JMXConnectionHandlerCfgDefn_ko.properties
@@ -0,0 +1,24 @@
+user-friendly-name=JMX Connection Handler
+user-friendly-plural-name=JMX Connection Handlers
+synopsis=The JMX Connection Handler is used to interact with clients using the Java Management Extensions (JMX) protocol.
+constraint.1.synopsis=A Key Manager Provider must be specified when this JMX Connection Handler is enabled and it is configured to use SSL.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the JMX Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the JMX Connection Handler implementation.
+property.key-manager-provider.synopsis=Specifies the name of the key manager that should be used with this JMX Connection Handler .
+property.key-manager-provider.requires-admin-action.synopsis=Changes to this property take effect immediately, but only for subsequent attempts to access the key manager provider for associated client connections.
+property.key-manager-provider.syntax.aggregation.constraint-synopsis=The referenced key manager provider must be enabled when the JMX Connection Handler is enabled and configured to use SSL.
+property.listen-port.synopsis=Specifies the port number on which the JMX Connection Handler will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the JMX Connection Handler should use when performing SSL communication.
+property.ssl-cert-nickname.description=This is only applicable when the JMX Connection Handler is configured to use SSL.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.use-ssl.synopsis=Indicates whether the JMX Connection Handler should use SSL.
+property.use-ssl.description=If enabled, the JMX Connection Handler will use SSL to encrypt communication with the clients.
diff --git a/opends/src/admin/messages/JMXConnectionHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/JMXConnectionHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..8985984
--- /dev/null
+++ b/opends/src/admin/messages/JMXConnectionHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,24 @@
+user-friendly-name=JMX Connection Handler
+user-friendly-plural-name=JMX Connection Handlers
+synopsis=The JMX Connection Handler is used to interact with clients using the Java Management Extensions (JMX) protocol.
+constraint.1.synopsis=A Key Manager Provider must be specified when this JMX Connection Handler is enabled and it is configured to use SSL.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the JMX Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the JMX Connection Handler implementation.
+property.key-manager-provider.synopsis=Specifies the name of the key manager that should be used with this JMX Connection Handler .
+property.key-manager-provider.requires-admin-action.synopsis=Changes to this property take effect immediately, but only for subsequent attempts to access the key manager provider for associated client connections.
+property.key-manager-provider.syntax.aggregation.constraint-synopsis=The referenced key manager provider must be enabled when the JMX Connection Handler is enabled and configured to use SSL.
+property.listen-port.synopsis=Specifies the port number on which the JMX Connection Handler will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the JMX Connection Handler should use when performing SSL communication.
+property.ssl-cert-nickname.description=This is only applicable when the JMX Connection Handler is configured to use SSL.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.use-ssl.synopsis=Indicates whether the JMX Connection Handler should use SSL.
+property.use-ssl.description=If enabled, the JMX Connection Handler will use SSL to encrypt communication with the clients.
diff --git a/opends/src/admin/messages/JMXConnectionHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/JMXConnectionHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..8985984
--- /dev/null
+++ b/opends/src/admin/messages/JMXConnectionHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,24 @@
+user-friendly-name=JMX Connection Handler
+user-friendly-plural-name=JMX Connection Handlers
+synopsis=The JMX Connection Handler is used to interact with clients using the Java Management Extensions (JMX) protocol.
+constraint.1.synopsis=A Key Manager Provider must be specified when this JMX Connection Handler is enabled and it is configured to use SSL.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the JMX Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the JMX Connection Handler implementation.
+property.key-manager-provider.synopsis=Specifies the name of the key manager that should be used with this JMX Connection Handler .
+property.key-manager-provider.requires-admin-action.synopsis=Changes to this property take effect immediately, but only for subsequent attempts to access the key manager provider for associated client connections.
+property.key-manager-provider.syntax.aggregation.constraint-synopsis=The referenced key manager provider must be enabled when the JMX Connection Handler is enabled and configured to use SSL.
+property.listen-port.synopsis=Specifies the port number on which the JMX Connection Handler will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the JMX Connection Handler should use when performing SSL communication.
+property.ssl-cert-nickname.description=This is only applicable when the JMX Connection Handler is configured to use SSL.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.use-ssl.synopsis=Indicates whether the JMX Connection Handler should use SSL.
+property.use-ssl.description=If enabled, the JMX Connection Handler will use SSL to encrypt communication with the clients.
diff --git a/opends/src/admin/messages/KeyManagerProviderCfgDefn.properties b/opends/src/admin/messages/KeyManagerProviderCfgDefn.properties
new file mode 100644
index 0000000..a5d864d
--- /dev/null
+++ b/opends/src/admin/messages/KeyManagerProviderCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Key Manager Provider
+user-friendly-plural-name=Key Manager Providers
+synopsis=Key Manager Providers are responsible for managing the key material that is used to authenticate an SSL connection to its peer.
+description=Key Manager Providers essentially provide access to the certificate that is used by the server when performing SSL or StartTLS negotiation.
+property.enabled.synopsis=Indicates whether the Key Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Key Manager Provider implementation.
diff --git a/opends/src/admin/messages/KeyManagerProviderCfgDefn_de.properties b/opends/src/admin/messages/KeyManagerProviderCfgDefn_de.properties
new file mode 100644
index 0000000..a5d864d
--- /dev/null
+++ b/opends/src/admin/messages/KeyManagerProviderCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Key Manager Provider
+user-friendly-plural-name=Key Manager Providers
+synopsis=Key Manager Providers are responsible for managing the key material that is used to authenticate an SSL connection to its peer.
+description=Key Manager Providers essentially provide access to the certificate that is used by the server when performing SSL or StartTLS negotiation.
+property.enabled.synopsis=Indicates whether the Key Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Key Manager Provider implementation.
diff --git a/opends/src/admin/messages/KeyManagerProviderCfgDefn_es.properties b/opends/src/admin/messages/KeyManagerProviderCfgDefn_es.properties
new file mode 100644
index 0000000..a5d864d
--- /dev/null
+++ b/opends/src/admin/messages/KeyManagerProviderCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Key Manager Provider
+user-friendly-plural-name=Key Manager Providers
+synopsis=Key Manager Providers are responsible for managing the key material that is used to authenticate an SSL connection to its peer.
+description=Key Manager Providers essentially provide access to the certificate that is used by the server when performing SSL or StartTLS negotiation.
+property.enabled.synopsis=Indicates whether the Key Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Key Manager Provider implementation.
diff --git a/opends/src/admin/messages/KeyManagerProviderCfgDefn_fr.properties b/opends/src/admin/messages/KeyManagerProviderCfgDefn_fr.properties
new file mode 100644
index 0000000..a5d864d
--- /dev/null
+++ b/opends/src/admin/messages/KeyManagerProviderCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Key Manager Provider
+user-friendly-plural-name=Key Manager Providers
+synopsis=Key Manager Providers are responsible for managing the key material that is used to authenticate an SSL connection to its peer.
+description=Key Manager Providers essentially provide access to the certificate that is used by the server when performing SSL or StartTLS negotiation.
+property.enabled.synopsis=Indicates whether the Key Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Key Manager Provider implementation.
diff --git a/opends/src/admin/messages/KeyManagerProviderCfgDefn_ja.properties b/opends/src/admin/messages/KeyManagerProviderCfgDefn_ja.properties
new file mode 100644
index 0000000..a5d864d
--- /dev/null
+++ b/opends/src/admin/messages/KeyManagerProviderCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Key Manager Provider
+user-friendly-plural-name=Key Manager Providers
+synopsis=Key Manager Providers are responsible for managing the key material that is used to authenticate an SSL connection to its peer.
+description=Key Manager Providers essentially provide access to the certificate that is used by the server when performing SSL or StartTLS negotiation.
+property.enabled.synopsis=Indicates whether the Key Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Key Manager Provider implementation.
diff --git a/opends/src/admin/messages/KeyManagerProviderCfgDefn_ko.properties b/opends/src/admin/messages/KeyManagerProviderCfgDefn_ko.properties
new file mode 100644
index 0000000..a5d864d
--- /dev/null
+++ b/opends/src/admin/messages/KeyManagerProviderCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Key Manager Provider
+user-friendly-plural-name=Key Manager Providers
+synopsis=Key Manager Providers are responsible for managing the key material that is used to authenticate an SSL connection to its peer.
+description=Key Manager Providers essentially provide access to the certificate that is used by the server when performing SSL or StartTLS negotiation.
+property.enabled.synopsis=Indicates whether the Key Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Key Manager Provider implementation.
diff --git a/opends/src/admin/messages/KeyManagerProviderCfgDefn_zh_CN.properties b/opends/src/admin/messages/KeyManagerProviderCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..a5d864d
--- /dev/null
+++ b/opends/src/admin/messages/KeyManagerProviderCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Key Manager Provider
+user-friendly-plural-name=Key Manager Providers
+synopsis=Key Manager Providers are responsible for managing the key material that is used to authenticate an SSL connection to its peer.
+description=Key Manager Providers essentially provide access to the certificate that is used by the server when performing SSL or StartTLS negotiation.
+property.enabled.synopsis=Indicates whether the Key Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Key Manager Provider implementation.
diff --git a/opends/src/admin/messages/KeyManagerProviderCfgDefn_zh_TW.properties b/opends/src/admin/messages/KeyManagerProviderCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..a5d864d
--- /dev/null
+++ b/opends/src/admin/messages/KeyManagerProviderCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Key Manager Provider
+user-friendly-plural-name=Key Manager Providers
+synopsis=Key Manager Providers are responsible for managing the key material that is used to authenticate an SSL connection to its peer.
+description=Key Manager Providers essentially provide access to the certificate that is used by the server when performing SSL or StartTLS negotiation.
+property.enabled.synopsis=Indicates whether the Key Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Key Manager Provider implementation.
diff --git a/opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn.properties b/opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn.properties
new file mode 100644
index 0000000..0146563
--- /dev/null
+++ b/opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn.properties
@@ -0,0 +1,59 @@
+user-friendly-name=LDAP Attribute Description List Plugin
+user-friendly-plural-name=LDAP Attribute Description List Plugins
+synopsis=The LDAP Attribute Description List Plugin provides the ability for clients to include an attribute list in a search request that names object classes instead of (or in addition to) attributes.
+description=For example, if a client wishes to retrieve all of the attributes in the inetOrgPerson object class, then that client can include "@inetOrgPerson" in the attribute list rather than naming all of those attributes individually. This behavior is based on the specification contained in RFC 4529. The implementation for the LDAP attribute description list plugin is contained in the org.opends.server.plugins.LDAPADListPlugin class. It must be configured with the preParseSearch plugin type, but does not have any other custom configuration.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_de.properties b/opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_de.properties
new file mode 100644
index 0000000..0146563
--- /dev/null
+++ b/opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_de.properties
@@ -0,0 +1,59 @@
+user-friendly-name=LDAP Attribute Description List Plugin
+user-friendly-plural-name=LDAP Attribute Description List Plugins
+synopsis=The LDAP Attribute Description List Plugin provides the ability for clients to include an attribute list in a search request that names object classes instead of (or in addition to) attributes.
+description=For example, if a client wishes to retrieve all of the attributes in the inetOrgPerson object class, then that client can include "@inetOrgPerson" in the attribute list rather than naming all of those attributes individually. This behavior is based on the specification contained in RFC 4529. The implementation for the LDAP attribute description list plugin is contained in the org.opends.server.plugins.LDAPADListPlugin class. It must be configured with the preParseSearch plugin type, but does not have any other custom configuration.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_es.properties b/opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_es.properties
new file mode 100644
index 0000000..0146563
--- /dev/null
+++ b/opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_es.properties
@@ -0,0 +1,59 @@
+user-friendly-name=LDAP Attribute Description List Plugin
+user-friendly-plural-name=LDAP Attribute Description List Plugins
+synopsis=The LDAP Attribute Description List Plugin provides the ability for clients to include an attribute list in a search request that names object classes instead of (or in addition to) attributes.
+description=For example, if a client wishes to retrieve all of the attributes in the inetOrgPerson object class, then that client can include "@inetOrgPerson" in the attribute list rather than naming all of those attributes individually. This behavior is based on the specification contained in RFC 4529. The implementation for the LDAP attribute description list plugin is contained in the org.opends.server.plugins.LDAPADListPlugin class. It must be configured with the preParseSearch plugin type, but does not have any other custom configuration.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_fr.properties b/opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_fr.properties
new file mode 100644
index 0000000..0146563
--- /dev/null
+++ b/opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_fr.properties
@@ -0,0 +1,59 @@
+user-friendly-name=LDAP Attribute Description List Plugin
+user-friendly-plural-name=LDAP Attribute Description List Plugins
+synopsis=The LDAP Attribute Description List Plugin provides the ability for clients to include an attribute list in a search request that names object classes instead of (or in addition to) attributes.
+description=For example, if a client wishes to retrieve all of the attributes in the inetOrgPerson object class, then that client can include "@inetOrgPerson" in the attribute list rather than naming all of those attributes individually. This behavior is based on the specification contained in RFC 4529. The implementation for the LDAP attribute description list plugin is contained in the org.opends.server.plugins.LDAPADListPlugin class. It must be configured with the preParseSearch plugin type, but does not have any other custom configuration.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_ja.properties b/opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_ja.properties
new file mode 100644
index 0000000..0146563
--- /dev/null
+++ b/opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_ja.properties
@@ -0,0 +1,59 @@
+user-friendly-name=LDAP Attribute Description List Plugin
+user-friendly-plural-name=LDAP Attribute Description List Plugins
+synopsis=The LDAP Attribute Description List Plugin provides the ability for clients to include an attribute list in a search request that names object classes instead of (or in addition to) attributes.
+description=For example, if a client wishes to retrieve all of the attributes in the inetOrgPerson object class, then that client can include "@inetOrgPerson" in the attribute list rather than naming all of those attributes individually. This behavior is based on the specification contained in RFC 4529. The implementation for the LDAP attribute description list plugin is contained in the org.opends.server.plugins.LDAPADListPlugin class. It must be configured with the preParseSearch plugin type, but does not have any other custom configuration.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_ko.properties b/opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_ko.properties
new file mode 100644
index 0000000..0146563
--- /dev/null
+++ b/opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_ko.properties
@@ -0,0 +1,59 @@
+user-friendly-name=LDAP Attribute Description List Plugin
+user-friendly-plural-name=LDAP Attribute Description List Plugins
+synopsis=The LDAP Attribute Description List Plugin provides the ability for clients to include an attribute list in a search request that names object classes instead of (or in addition to) attributes.
+description=For example, if a client wishes to retrieve all of the attributes in the inetOrgPerson object class, then that client can include "@inetOrgPerson" in the attribute list rather than naming all of those attributes individually. This behavior is based on the specification contained in RFC 4529. The implementation for the LDAP attribute description list plugin is contained in the org.opends.server.plugins.LDAPADListPlugin class. It must be configured with the preParseSearch plugin type, but does not have any other custom configuration.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_zh_CN.properties b/opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..0146563
--- /dev/null
+++ b/opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_zh_CN.properties
@@ -0,0 +1,59 @@
+user-friendly-name=LDAP Attribute Description List Plugin
+user-friendly-plural-name=LDAP Attribute Description List Plugins
+synopsis=The LDAP Attribute Description List Plugin provides the ability for clients to include an attribute list in a search request that names object classes instead of (or in addition to) attributes.
+description=For example, if a client wishes to retrieve all of the attributes in the inetOrgPerson object class, then that client can include "@inetOrgPerson" in the attribute list rather than naming all of those attributes individually. This behavior is based on the specification contained in RFC 4529. The implementation for the LDAP attribute description list plugin is contained in the org.opends.server.plugins.LDAPADListPlugin class. It must be configured with the preParseSearch plugin type, but does not have any other custom configuration.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_zh_TW.properties b/opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..0146563
--- /dev/null
+++ b/opends/src/admin/messages/LDAPAttributeDescriptionListPluginCfgDefn_zh_TW.properties
@@ -0,0 +1,59 @@
+user-friendly-name=LDAP Attribute Description List Plugin
+user-friendly-plural-name=LDAP Attribute Description List Plugins
+synopsis=The LDAP Attribute Description List Plugin provides the ability for clients to include an attribute list in a search request that names object classes instead of (or in addition to) attributes.
+description=For example, if a client wishes to retrieve all of the attributes in the inetOrgPerson object class, then that client can include "@inetOrgPerson" in the attribute list rather than naming all of those attributes individually. This behavior is based on the specification contained in RFC 4529. The implementation for the LDAP attribute description list plugin is contained in the org.opends.server.plugins.LDAPADListPlugin class. It must be configured with the preParseSearch plugin type, but does not have any other custom configuration.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/LDAPConnectionHandlerCfgDefn.properties b/opends/src/admin/messages/LDAPConnectionHandlerCfgDefn.properties
new file mode 100644
index 0000000..cbdadac
--- /dev/null
+++ b/opends/src/admin/messages/LDAPConnectionHandlerCfgDefn.properties
@@ -0,0 +1,65 @@
+user-friendly-name=LDAP Connection Handler
+user-friendly-plural-name=LDAP Connection Handlers
+synopsis=The LDAP Connection Handler is used to interact with clients using LDAP.
+description=It provides full support for LDAPv3 and limited support for LDAPv2.
+constraint.1.synopsis=A Key Manager Provider must be specified when this LDAP Connection Handler is enabled and it is configured to use SSL or StartTLS.
+constraint.2.synopsis=A Trust Manager Provider must be specified when this LDAP Connection Handler is enabled and it is configured to use SSL or StartTLS.
+constraint.3.synopsis=A LDAP Connection Handler cannot be configured to support SSL and StartTLS at the same time. Either SSL or StartTLS must be disabled in order for this LDAP Connection Handler to be used.
+property.accept-backlog.synopsis=Specifies the maximum number of pending connection attempts that are allowed to queue up in the accept backlog before the server starts rejecting new connection attempts.
+property.accept-backlog.description=This is primarily an issue for cases in which a large number of connections are established to the server in a very short period of time (for example, a benchmark utility that creates a large number of client threads that each have their own connection to the server) and the connection handler is unable to keep up with the rate at which the new connections are established.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.allow-ldap-v2.synopsis=Indicates whether connections from LDAPv2 clients are allowed.
+property.allow-ldap-v2.description=If LDAPv2 clients are allowed, then only a minimal degree of special support are provided for them to ensure that LDAPv3-specific protocol elements (for example, Configuration Guide 25 controls, extended response messages, intermediate response messages, referrals) are not sent to an LDAPv2 client.
+property.allow-start-tls.synopsis=Indicates whether clients are allowed to use StartTLS.
+property.allow-start-tls.description=If enabled, the LDAP Connection Handler allows clients to use the StartTLS extended operation to initiate secure communication over an otherwise insecure channel. Note that this is only allowed if the LDAP Connection Handler is not configured to use SSL, and if the server is configured with a valid key manager provider and a valid trust manager provider.
+property.allow-tcp-reuse-address.synopsis=Indicates whether the LDAP Connection Handler should reuse socket descriptors.
+property.allow-tcp-reuse-address.description=If enabled, the SO_REUSEADDR socket option is used on the server listen socket to potentially allow the reuse of socket descriptors for clients in a TIME_WAIT state. This may help the server avoid temporarily running out of socket descriptors in cases in which a very large number of short-lived connections have been established from the same client system.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the LDAP Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the LDAP Connection Handler implementation.
+property.keep-stats.synopsis=Indicates whether the LDAP Connection Handler should keep statistics.
+property.keep-stats.description=If enabled, the LDAP Connection Handler maintains statistics about the number and types of operations requested over LDAP and the amount of data sent and received.
+property.key-manager-provider.synopsis=Specifies the name of the key manager that should be used with this LDAP Connection Handler .
+property.key-manager-provider.requires-admin-action.synopsis=Changes to this property take effect immediately, but only for subsequent attempts to access the key manager provider for associated client connections.
+property.key-manager-provider.syntax.aggregation.constraint-synopsis=The referenced key manager provider must be enabled when the LDAP Connection Handler is enabled and configured to use SSL or StartTLS.
+property.listen-address.synopsis=Specifies the address or set of addresses on which this LDAP Connection Handler should listen for connections from LDAP clients.
+property.listen-address.description=Multiple addresses may be provided as separate values for this attribute. If no values are provided, then the LDAP Connection Handler listens on all interfaces.
+property.listen-port.synopsis=Specifies the port number on which the LDAP Connection Handler will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.max-blocked-write-time-limit.synopsis=Specifies the maximum length of time that attempts to write data to LDAP clients should be allowed to block.
+property.max-blocked-write-time-limit.description=If an attempt to write data to a client takes longer than this length of time, then the client connection is terminated.
+property.max-request-size.synopsis=Specifies the size in bytes of the largest LDAP request message that will be allowed by this LDAP Connection handler.
+property.max-request-size.description=This property is analogous to the maxBERSize configuration attribute of the Sun Java System Directory Server. This can help prevent denial-of-service attacks by clients that indicate they send extremely large requests to the server causing it to attempt to allocate large amounts of memory.
+property.num-request-handlers.synopsis=Specifies the number of request handlers that are used to read requests from clients.
+property.num-request-handlers.description=The LDAP Connection Handler uses one thread to accept new connections from clients, but uses one or more additional threads to read requests from existing client connections. This ensures that new requests are read efficiently and that the connection handler itself does not become a bottleneck when the server is under heavy load from many clients at the same time.
+property.send-rejection-notice.synopsis=Indicates whether the LDAP Connection Handler should send a notice of disconnection extended response message to the client if a new connection is rejected for some reason.
+property.send-rejection-notice.description=The extended response message may provide an explanation indicating the reason that the connection was rejected.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the LDAP Connection Handler should use when performing SSL communication.
+property.ssl-cert-nickname.description=This is only applicable when the LDAP Connection Handler is configured to use SSL.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.ssl-cipher-suite.synopsis=Specifies the names of the SSL cipher suites that are allowed for use in SSL or StartTLS communication.
+property.ssl-cipher-suite.default-behavior.alias.synopsis=Uses the default set of SSL cipher suites provided by the server's JVM.
+property.ssl-cipher-suite.requires-admin-action.synopsis=Changes to this property take effect immediately but will only impact new SSL/TLS-based sessions created after the change.
+property.ssl-client-auth-policy.synopsis=Specifies the policy that the LDAP Connection Handler should use regarding client SSL certificates.
+property.ssl-client-auth-policy.description=This is only applicable if clients are allowed to use SSL.
+property.ssl-client-auth-policy.syntax.enumeration.value.disabled.synopsis=Clients are not required to provide their own certificates when performing SSL negotiation.
+property.ssl-client-auth-policy.syntax.enumeration.value.optional.synopsis=Clients are requested to provide their own certificates when performing SSL negotiation, but still accept the connection even if the client does not provide a certificate.
+property.ssl-client-auth-policy.syntax.enumeration.value.required.synopsis=Clients are required to provide their own certificates when performing SSL negotiation and are refused access if the do not provide a certificate.
+property.ssl-protocol.synopsis=Specifies the names of the SSL protocols that are allowed for use in SSL or StartTLS communication.
+property.ssl-protocol.default-behavior.alias.synopsis=Uses the default set of SSL protocols provided by the server's JVM.
+property.ssl-protocol.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
+property.trust-manager-provider.synopsis=Specifies the name of the trust manager that should be used with the LDAP Connection Handler .
+property.trust-manager-provider.requires-admin-action.synopsis=Changes to this property take effect immediately, but only for subsequent attempts to access the trust manager provider for associated client connections.
+property.trust-manager-provider.syntax.aggregation.constraint-synopsis=The referenced trust manager provider must be enabled when the LDAP Connection Handler is enabled and configured to use SSL or StartTLS.
+property.use-ssl.synopsis=Indicates whether the LDAP Connection Handler should use SSL.
+property.use-ssl.description=If enabled, the LDAP Connection Handler will use SSL to encrypt communication with the clients.
+property.use-tcp-keep-alive.synopsis=Indicates whether the LDAP Connection Handler should use TCP keep-alive.
+property.use-tcp-keep-alive.description=If enabled, the SO_KEEPALIVE socket option is used to indicate that TCP keepalive messages should periodically be sent to the client to verify that the associated connection is still valid. This may also help prevent cases in which intermediate network hardware could silently drop an otherwise idle client connection, provided that the keepalive interval configured in the underlying operating system is smaller than the timeout enforced by the network hardware.
+property.use-tcp-no-delay.synopsis=Indicates whether the LDAP Connection Handler should use TCP no-delay.
+property.use-tcp-no-delay.description=If enabled, the TCP_NODELAY socket option is used to ensure that response messages to the client are sent immediately rather than potentially waiting to determine whether additional response messages can be sent in the same packet. In most cases, using the TCP_NODELAY socket option provides better performance and lower response times, but disabling it may help for some cases in which the server sends a large number of entries to a client in response to a search request.
diff --git a/opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_de.properties b/opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..cbdadac
--- /dev/null
+++ b/opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_de.properties
@@ -0,0 +1,65 @@
+user-friendly-name=LDAP Connection Handler
+user-friendly-plural-name=LDAP Connection Handlers
+synopsis=The LDAP Connection Handler is used to interact with clients using LDAP.
+description=It provides full support for LDAPv3 and limited support for LDAPv2.
+constraint.1.synopsis=A Key Manager Provider must be specified when this LDAP Connection Handler is enabled and it is configured to use SSL or StartTLS.
+constraint.2.synopsis=A Trust Manager Provider must be specified when this LDAP Connection Handler is enabled and it is configured to use SSL or StartTLS.
+constraint.3.synopsis=A LDAP Connection Handler cannot be configured to support SSL and StartTLS at the same time. Either SSL or StartTLS must be disabled in order for this LDAP Connection Handler to be used.
+property.accept-backlog.synopsis=Specifies the maximum number of pending connection attempts that are allowed to queue up in the accept backlog before the server starts rejecting new connection attempts.
+property.accept-backlog.description=This is primarily an issue for cases in which a large number of connections are established to the server in a very short period of time (for example, a benchmark utility that creates a large number of client threads that each have their own connection to the server) and the connection handler is unable to keep up with the rate at which the new connections are established.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.allow-ldap-v2.synopsis=Indicates whether connections from LDAPv2 clients are allowed.
+property.allow-ldap-v2.description=If LDAPv2 clients are allowed, then only a minimal degree of special support are provided for them to ensure that LDAPv3-specific protocol elements (for example, Configuration Guide 25 controls, extended response messages, intermediate response messages, referrals) are not sent to an LDAPv2 client.
+property.allow-start-tls.synopsis=Indicates whether clients are allowed to use StartTLS.
+property.allow-start-tls.description=If enabled, the LDAP Connection Handler allows clients to use the StartTLS extended operation to initiate secure communication over an otherwise insecure channel. Note that this is only allowed if the LDAP Connection Handler is not configured to use SSL, and if the server is configured with a valid key manager provider and a valid trust manager provider.
+property.allow-tcp-reuse-address.synopsis=Indicates whether the LDAP Connection Handler should reuse socket descriptors.
+property.allow-tcp-reuse-address.description=If enabled, the SO_REUSEADDR socket option is used on the server listen socket to potentially allow the reuse of socket descriptors for clients in a TIME_WAIT state. This may help the server avoid temporarily running out of socket descriptors in cases in which a very large number of short-lived connections have been established from the same client system.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the LDAP Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the LDAP Connection Handler implementation.
+property.keep-stats.synopsis=Indicates whether the LDAP Connection Handler should keep statistics.
+property.keep-stats.description=If enabled, the LDAP Connection Handler maintains statistics about the number and types of operations requested over LDAP and the amount of data sent and received.
+property.key-manager-provider.synopsis=Specifies the name of the key manager that should be used with this LDAP Connection Handler .
+property.key-manager-provider.requires-admin-action.synopsis=Changes to this property take effect immediately, but only for subsequent attempts to access the key manager provider for associated client connections.
+property.key-manager-provider.syntax.aggregation.constraint-synopsis=The referenced key manager provider must be enabled when the LDAP Connection Handler is enabled and configured to use SSL or StartTLS.
+property.listen-address.synopsis=Specifies the address or set of addresses on which this LDAP Connection Handler should listen for connections from LDAP clients.
+property.listen-address.description=Multiple addresses may be provided as separate values for this attribute. If no values are provided, then the LDAP Connection Handler listens on all interfaces.
+property.listen-port.synopsis=Specifies the port number on which the LDAP Connection Handler will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.max-blocked-write-time-limit.synopsis=Specifies the maximum length of time that attempts to write data to LDAP clients should be allowed to block.
+property.max-blocked-write-time-limit.description=If an attempt to write data to a client takes longer than this length of time, then the client connection is terminated.
+property.max-request-size.synopsis=Specifies the size in bytes of the largest LDAP request message that will be allowed by this LDAP Connection handler.
+property.max-request-size.description=This property is analogous to the maxBERSize configuration attribute of the Sun Java System Directory Server. This can help prevent denial-of-service attacks by clients that indicate they send extremely large requests to the server causing it to attempt to allocate large amounts of memory.
+property.num-request-handlers.synopsis=Specifies the number of request handlers that are used to read requests from clients.
+property.num-request-handlers.description=The LDAP Connection Handler uses one thread to accept new connections from clients, but uses one or more additional threads to read requests from existing client connections. This ensures that new requests are read efficiently and that the connection handler itself does not become a bottleneck when the server is under heavy load from many clients at the same time.
+property.send-rejection-notice.synopsis=Indicates whether the LDAP Connection Handler should send a notice of disconnection extended response message to the client if a new connection is rejected for some reason.
+property.send-rejection-notice.description=The extended response message may provide an explanation indicating the reason that the connection was rejected.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the LDAP Connection Handler should use when performing SSL communication.
+property.ssl-cert-nickname.description=This is only applicable when the LDAP Connection Handler is configured to use SSL.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.ssl-cipher-suite.synopsis=Specifies the names of the SSL cipher suites that are allowed for use in SSL or StartTLS communication.
+property.ssl-cipher-suite.default-behavior.alias.synopsis=Uses the default set of SSL cipher suites provided by the server's JVM.
+property.ssl-cipher-suite.requires-admin-action.synopsis=Changes to this property take effect immediately but will only impact new SSL/TLS-based sessions created after the change.
+property.ssl-client-auth-policy.synopsis=Specifies the policy that the LDAP Connection Handler should use regarding client SSL certificates.
+property.ssl-client-auth-policy.description=This is only applicable if clients are allowed to use SSL.
+property.ssl-client-auth-policy.syntax.enumeration.value.disabled.synopsis=Clients are not required to provide their own certificates when performing SSL negotiation.
+property.ssl-client-auth-policy.syntax.enumeration.value.optional.synopsis=Clients are requested to provide their own certificates when performing SSL negotiation, but still accept the connection even if the client does not provide a certificate.
+property.ssl-client-auth-policy.syntax.enumeration.value.required.synopsis=Clients are required to provide their own certificates when performing SSL negotiation and are refused access if the do not provide a certificate.
+property.ssl-protocol.synopsis=Specifies the names of the SSL protocols that are allowed for use in SSL or StartTLS communication.
+property.ssl-protocol.default-behavior.alias.synopsis=Uses the default set of SSL protocols provided by the server's JVM.
+property.ssl-protocol.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
+property.trust-manager-provider.synopsis=Specifies the name of the trust manager that should be used with the LDAP Connection Handler .
+property.trust-manager-provider.requires-admin-action.synopsis=Changes to this property take effect immediately, but only for subsequent attempts to access the trust manager provider for associated client connections.
+property.trust-manager-provider.syntax.aggregation.constraint-synopsis=The referenced trust manager provider must be enabled when the LDAP Connection Handler is enabled and configured to use SSL or StartTLS.
+property.use-ssl.synopsis=Indicates whether the LDAP Connection Handler should use SSL.
+property.use-ssl.description=If enabled, the LDAP Connection Handler will use SSL to encrypt communication with the clients.
+property.use-tcp-keep-alive.synopsis=Indicates whether the LDAP Connection Handler should use TCP keep-alive.
+property.use-tcp-keep-alive.description=If enabled, the SO_KEEPALIVE socket option is used to indicate that TCP keepalive messages should periodically be sent to the client to verify that the associated connection is still valid. This may also help prevent cases in which intermediate network hardware could silently drop an otherwise idle client connection, provided that the keepalive interval configured in the underlying operating system is smaller than the timeout enforced by the network hardware.
+property.use-tcp-no-delay.synopsis=Indicates whether the LDAP Connection Handler should use TCP no-delay.
+property.use-tcp-no-delay.description=If enabled, the TCP_NODELAY socket option is used to ensure that response messages to the client are sent immediately rather than potentially waiting to determine whether additional response messages can be sent in the same packet. In most cases, using the TCP_NODELAY socket option provides better performance and lower response times, but disabling it may help for some cases in which the server sends a large number of entries to a client in response to a search request.
diff --git a/opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_es.properties b/opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..cbdadac
--- /dev/null
+++ b/opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_es.properties
@@ -0,0 +1,65 @@
+user-friendly-name=LDAP Connection Handler
+user-friendly-plural-name=LDAP Connection Handlers
+synopsis=The LDAP Connection Handler is used to interact with clients using LDAP.
+description=It provides full support for LDAPv3 and limited support for LDAPv2.
+constraint.1.synopsis=A Key Manager Provider must be specified when this LDAP Connection Handler is enabled and it is configured to use SSL or StartTLS.
+constraint.2.synopsis=A Trust Manager Provider must be specified when this LDAP Connection Handler is enabled and it is configured to use SSL or StartTLS.
+constraint.3.synopsis=A LDAP Connection Handler cannot be configured to support SSL and StartTLS at the same time. Either SSL or StartTLS must be disabled in order for this LDAP Connection Handler to be used.
+property.accept-backlog.synopsis=Specifies the maximum number of pending connection attempts that are allowed to queue up in the accept backlog before the server starts rejecting new connection attempts.
+property.accept-backlog.description=This is primarily an issue for cases in which a large number of connections are established to the server in a very short period of time (for example, a benchmark utility that creates a large number of client threads that each have their own connection to the server) and the connection handler is unable to keep up with the rate at which the new connections are established.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.allow-ldap-v2.synopsis=Indicates whether connections from LDAPv2 clients are allowed.
+property.allow-ldap-v2.description=If LDAPv2 clients are allowed, then only a minimal degree of special support are provided for them to ensure that LDAPv3-specific protocol elements (for example, Configuration Guide 25 controls, extended response messages, intermediate response messages, referrals) are not sent to an LDAPv2 client.
+property.allow-start-tls.synopsis=Indicates whether clients are allowed to use StartTLS.
+property.allow-start-tls.description=If enabled, the LDAP Connection Handler allows clients to use the StartTLS extended operation to initiate secure communication over an otherwise insecure channel. Note that this is only allowed if the LDAP Connection Handler is not configured to use SSL, and if the server is configured with a valid key manager provider and a valid trust manager provider.
+property.allow-tcp-reuse-address.synopsis=Indicates whether the LDAP Connection Handler should reuse socket descriptors.
+property.allow-tcp-reuse-address.description=If enabled, the SO_REUSEADDR socket option is used on the server listen socket to potentially allow the reuse of socket descriptors for clients in a TIME_WAIT state. This may help the server avoid temporarily running out of socket descriptors in cases in which a very large number of short-lived connections have been established from the same client system.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the LDAP Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the LDAP Connection Handler implementation.
+property.keep-stats.synopsis=Indicates whether the LDAP Connection Handler should keep statistics.
+property.keep-stats.description=If enabled, the LDAP Connection Handler maintains statistics about the number and types of operations requested over LDAP and the amount of data sent and received.
+property.key-manager-provider.synopsis=Specifies the name of the key manager that should be used with this LDAP Connection Handler .
+property.key-manager-provider.requires-admin-action.synopsis=Changes to this property take effect immediately, but only for subsequent attempts to access the key manager provider for associated client connections.
+property.key-manager-provider.syntax.aggregation.constraint-synopsis=The referenced key manager provider must be enabled when the LDAP Connection Handler is enabled and configured to use SSL or StartTLS.
+property.listen-address.synopsis=Specifies the address or set of addresses on which this LDAP Connection Handler should listen for connections from LDAP clients.
+property.listen-address.description=Multiple addresses may be provided as separate values for this attribute. If no values are provided, then the LDAP Connection Handler listens on all interfaces.
+property.listen-port.synopsis=Specifies the port number on which the LDAP Connection Handler will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.max-blocked-write-time-limit.synopsis=Specifies the maximum length of time that attempts to write data to LDAP clients should be allowed to block.
+property.max-blocked-write-time-limit.description=If an attempt to write data to a client takes longer than this length of time, then the client connection is terminated.
+property.max-request-size.synopsis=Specifies the size in bytes of the largest LDAP request message that will be allowed by this LDAP Connection handler.
+property.max-request-size.description=This property is analogous to the maxBERSize configuration attribute of the Sun Java System Directory Server. This can help prevent denial-of-service attacks by clients that indicate they send extremely large requests to the server causing it to attempt to allocate large amounts of memory.
+property.num-request-handlers.synopsis=Specifies the number of request handlers that are used to read requests from clients.
+property.num-request-handlers.description=The LDAP Connection Handler uses one thread to accept new connections from clients, but uses one or more additional threads to read requests from existing client connections. This ensures that new requests are read efficiently and that the connection handler itself does not become a bottleneck when the server is under heavy load from many clients at the same time.
+property.send-rejection-notice.synopsis=Indicates whether the LDAP Connection Handler should send a notice of disconnection extended response message to the client if a new connection is rejected for some reason.
+property.send-rejection-notice.description=The extended response message may provide an explanation indicating the reason that the connection was rejected.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the LDAP Connection Handler should use when performing SSL communication.
+property.ssl-cert-nickname.description=This is only applicable when the LDAP Connection Handler is configured to use SSL.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.ssl-cipher-suite.synopsis=Specifies the names of the SSL cipher suites that are allowed for use in SSL or StartTLS communication.
+property.ssl-cipher-suite.default-behavior.alias.synopsis=Uses the default set of SSL cipher suites provided by the server's JVM.
+property.ssl-cipher-suite.requires-admin-action.synopsis=Changes to this property take effect immediately but will only impact new SSL/TLS-based sessions created after the change.
+property.ssl-client-auth-policy.synopsis=Specifies the policy that the LDAP Connection Handler should use regarding client SSL certificates.
+property.ssl-client-auth-policy.description=This is only applicable if clients are allowed to use SSL.
+property.ssl-client-auth-policy.syntax.enumeration.value.disabled.synopsis=Clients are not required to provide their own certificates when performing SSL negotiation.
+property.ssl-client-auth-policy.syntax.enumeration.value.optional.synopsis=Clients are requested to provide their own certificates when performing SSL negotiation, but still accept the connection even if the client does not provide a certificate.
+property.ssl-client-auth-policy.syntax.enumeration.value.required.synopsis=Clients are required to provide their own certificates when performing SSL negotiation and are refused access if the do not provide a certificate.
+property.ssl-protocol.synopsis=Specifies the names of the SSL protocols that are allowed for use in SSL or StartTLS communication.
+property.ssl-protocol.default-behavior.alias.synopsis=Uses the default set of SSL protocols provided by the server's JVM.
+property.ssl-protocol.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
+property.trust-manager-provider.synopsis=Specifies the name of the trust manager that should be used with the LDAP Connection Handler .
+property.trust-manager-provider.requires-admin-action.synopsis=Changes to this property take effect immediately, but only for subsequent attempts to access the trust manager provider for associated client connections.
+property.trust-manager-provider.syntax.aggregation.constraint-synopsis=The referenced trust manager provider must be enabled when the LDAP Connection Handler is enabled and configured to use SSL or StartTLS.
+property.use-ssl.synopsis=Indicates whether the LDAP Connection Handler should use SSL.
+property.use-ssl.description=If enabled, the LDAP Connection Handler will use SSL to encrypt communication with the clients.
+property.use-tcp-keep-alive.synopsis=Indicates whether the LDAP Connection Handler should use TCP keep-alive.
+property.use-tcp-keep-alive.description=If enabled, the SO_KEEPALIVE socket option is used to indicate that TCP keepalive messages should periodically be sent to the client to verify that the associated connection is still valid. This may also help prevent cases in which intermediate network hardware could silently drop an otherwise idle client connection, provided that the keepalive interval configured in the underlying operating system is smaller than the timeout enforced by the network hardware.
+property.use-tcp-no-delay.synopsis=Indicates whether the LDAP Connection Handler should use TCP no-delay.
+property.use-tcp-no-delay.description=If enabled, the TCP_NODELAY socket option is used to ensure that response messages to the client are sent immediately rather than potentially waiting to determine whether additional response messages can be sent in the same packet. In most cases, using the TCP_NODELAY socket option provides better performance and lower response times, but disabling it may help for some cases in which the server sends a large number of entries to a client in response to a search request.
diff --git a/opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_fr.properties b/opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..cbdadac
--- /dev/null
+++ b/opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_fr.properties
@@ -0,0 +1,65 @@
+user-friendly-name=LDAP Connection Handler
+user-friendly-plural-name=LDAP Connection Handlers
+synopsis=The LDAP Connection Handler is used to interact with clients using LDAP.
+description=It provides full support for LDAPv3 and limited support for LDAPv2.
+constraint.1.synopsis=A Key Manager Provider must be specified when this LDAP Connection Handler is enabled and it is configured to use SSL or StartTLS.
+constraint.2.synopsis=A Trust Manager Provider must be specified when this LDAP Connection Handler is enabled and it is configured to use SSL or StartTLS.
+constraint.3.synopsis=A LDAP Connection Handler cannot be configured to support SSL and StartTLS at the same time. Either SSL or StartTLS must be disabled in order for this LDAP Connection Handler to be used.
+property.accept-backlog.synopsis=Specifies the maximum number of pending connection attempts that are allowed to queue up in the accept backlog before the server starts rejecting new connection attempts.
+property.accept-backlog.description=This is primarily an issue for cases in which a large number of connections are established to the server in a very short period of time (for example, a benchmark utility that creates a large number of client threads that each have their own connection to the server) and the connection handler is unable to keep up with the rate at which the new connections are established.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.allow-ldap-v2.synopsis=Indicates whether connections from LDAPv2 clients are allowed.
+property.allow-ldap-v2.description=If LDAPv2 clients are allowed, then only a minimal degree of special support are provided for them to ensure that LDAPv3-specific protocol elements (for example, Configuration Guide 25 controls, extended response messages, intermediate response messages, referrals) are not sent to an LDAPv2 client.
+property.allow-start-tls.synopsis=Indicates whether clients are allowed to use StartTLS.
+property.allow-start-tls.description=If enabled, the LDAP Connection Handler allows clients to use the StartTLS extended operation to initiate secure communication over an otherwise insecure channel. Note that this is only allowed if the LDAP Connection Handler is not configured to use SSL, and if the server is configured with a valid key manager provider and a valid trust manager provider.
+property.allow-tcp-reuse-address.synopsis=Indicates whether the LDAP Connection Handler should reuse socket descriptors.
+property.allow-tcp-reuse-address.description=If enabled, the SO_REUSEADDR socket option is used on the server listen socket to potentially allow the reuse of socket descriptors for clients in a TIME_WAIT state. This may help the server avoid temporarily running out of socket descriptors in cases in which a very large number of short-lived connections have been established from the same client system.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the LDAP Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the LDAP Connection Handler implementation.
+property.keep-stats.synopsis=Indicates whether the LDAP Connection Handler should keep statistics.
+property.keep-stats.description=If enabled, the LDAP Connection Handler maintains statistics about the number and types of operations requested over LDAP and the amount of data sent and received.
+property.key-manager-provider.synopsis=Specifies the name of the key manager that should be used with this LDAP Connection Handler .
+property.key-manager-provider.requires-admin-action.synopsis=Changes to this property take effect immediately, but only for subsequent attempts to access the key manager provider for associated client connections.
+property.key-manager-provider.syntax.aggregation.constraint-synopsis=The referenced key manager provider must be enabled when the LDAP Connection Handler is enabled and configured to use SSL or StartTLS.
+property.listen-address.synopsis=Specifies the address or set of addresses on which this LDAP Connection Handler should listen for connections from LDAP clients.
+property.listen-address.description=Multiple addresses may be provided as separate values for this attribute. If no values are provided, then the LDAP Connection Handler listens on all interfaces.
+property.listen-port.synopsis=Specifies the port number on which the LDAP Connection Handler will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.max-blocked-write-time-limit.synopsis=Specifies the maximum length of time that attempts to write data to LDAP clients should be allowed to block.
+property.max-blocked-write-time-limit.description=If an attempt to write data to a client takes longer than this length of time, then the client connection is terminated.
+property.max-request-size.synopsis=Specifies the size in bytes of the largest LDAP request message that will be allowed by this LDAP Connection handler.
+property.max-request-size.description=This property is analogous to the maxBERSize configuration attribute of the Sun Java System Directory Server. This can help prevent denial-of-service attacks by clients that indicate they send extremely large requests to the server causing it to attempt to allocate large amounts of memory.
+property.num-request-handlers.synopsis=Specifies the number of request handlers that are used to read requests from clients.
+property.num-request-handlers.description=The LDAP Connection Handler uses one thread to accept new connections from clients, but uses one or more additional threads to read requests from existing client connections. This ensures that new requests are read efficiently and that the connection handler itself does not become a bottleneck when the server is under heavy load from many clients at the same time.
+property.send-rejection-notice.synopsis=Indicates whether the LDAP Connection Handler should send a notice of disconnection extended response message to the client if a new connection is rejected for some reason.
+property.send-rejection-notice.description=The extended response message may provide an explanation indicating the reason that the connection was rejected.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the LDAP Connection Handler should use when performing SSL communication.
+property.ssl-cert-nickname.description=This is only applicable when the LDAP Connection Handler is configured to use SSL.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.ssl-cipher-suite.synopsis=Specifies the names of the SSL cipher suites that are allowed for use in SSL or StartTLS communication.
+property.ssl-cipher-suite.default-behavior.alias.synopsis=Uses the default set of SSL cipher suites provided by the server's JVM.
+property.ssl-cipher-suite.requires-admin-action.synopsis=Changes to this property take effect immediately but will only impact new SSL/TLS-based sessions created after the change.
+property.ssl-client-auth-policy.synopsis=Specifies the policy that the LDAP Connection Handler should use regarding client SSL certificates.
+property.ssl-client-auth-policy.description=This is only applicable if clients are allowed to use SSL.
+property.ssl-client-auth-policy.syntax.enumeration.value.disabled.synopsis=Clients are not required to provide their own certificates when performing SSL negotiation.
+property.ssl-client-auth-policy.syntax.enumeration.value.optional.synopsis=Clients are requested to provide their own certificates when performing SSL negotiation, but still accept the connection even if the client does not provide a certificate.
+property.ssl-client-auth-policy.syntax.enumeration.value.required.synopsis=Clients are required to provide their own certificates when performing SSL negotiation and are refused access if the do not provide a certificate.
+property.ssl-protocol.synopsis=Specifies the names of the SSL protocols that are allowed for use in SSL or StartTLS communication.
+property.ssl-protocol.default-behavior.alias.synopsis=Uses the default set of SSL protocols provided by the server's JVM.
+property.ssl-protocol.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
+property.trust-manager-provider.synopsis=Specifies the name of the trust manager that should be used with the LDAP Connection Handler .
+property.trust-manager-provider.requires-admin-action.synopsis=Changes to this property take effect immediately, but only for subsequent attempts to access the trust manager provider for associated client connections.
+property.trust-manager-provider.syntax.aggregation.constraint-synopsis=The referenced trust manager provider must be enabled when the LDAP Connection Handler is enabled and configured to use SSL or StartTLS.
+property.use-ssl.synopsis=Indicates whether the LDAP Connection Handler should use SSL.
+property.use-ssl.description=If enabled, the LDAP Connection Handler will use SSL to encrypt communication with the clients.
+property.use-tcp-keep-alive.synopsis=Indicates whether the LDAP Connection Handler should use TCP keep-alive.
+property.use-tcp-keep-alive.description=If enabled, the SO_KEEPALIVE socket option is used to indicate that TCP keepalive messages should periodically be sent to the client to verify that the associated connection is still valid. This may also help prevent cases in which intermediate network hardware could silently drop an otherwise idle client connection, provided that the keepalive interval configured in the underlying operating system is smaller than the timeout enforced by the network hardware.
+property.use-tcp-no-delay.synopsis=Indicates whether the LDAP Connection Handler should use TCP no-delay.
+property.use-tcp-no-delay.description=If enabled, the TCP_NODELAY socket option is used to ensure that response messages to the client are sent immediately rather than potentially waiting to determine whether additional response messages can be sent in the same packet. In most cases, using the TCP_NODELAY socket option provides better performance and lower response times, but disabling it may help for some cases in which the server sends a large number of entries to a client in response to a search request.
diff --git a/opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_ja.properties b/opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..cbdadac
--- /dev/null
+++ b/opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_ja.properties
@@ -0,0 +1,65 @@
+user-friendly-name=LDAP Connection Handler
+user-friendly-plural-name=LDAP Connection Handlers
+synopsis=The LDAP Connection Handler is used to interact with clients using LDAP.
+description=It provides full support for LDAPv3 and limited support for LDAPv2.
+constraint.1.synopsis=A Key Manager Provider must be specified when this LDAP Connection Handler is enabled and it is configured to use SSL or StartTLS.
+constraint.2.synopsis=A Trust Manager Provider must be specified when this LDAP Connection Handler is enabled and it is configured to use SSL or StartTLS.
+constraint.3.synopsis=A LDAP Connection Handler cannot be configured to support SSL and StartTLS at the same time. Either SSL or StartTLS must be disabled in order for this LDAP Connection Handler to be used.
+property.accept-backlog.synopsis=Specifies the maximum number of pending connection attempts that are allowed to queue up in the accept backlog before the server starts rejecting new connection attempts.
+property.accept-backlog.description=This is primarily an issue for cases in which a large number of connections are established to the server in a very short period of time (for example, a benchmark utility that creates a large number of client threads that each have their own connection to the server) and the connection handler is unable to keep up with the rate at which the new connections are established.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.allow-ldap-v2.synopsis=Indicates whether connections from LDAPv2 clients are allowed.
+property.allow-ldap-v2.description=If LDAPv2 clients are allowed, then only a minimal degree of special support are provided for them to ensure that LDAPv3-specific protocol elements (for example, Configuration Guide 25 controls, extended response messages, intermediate response messages, referrals) are not sent to an LDAPv2 client.
+property.allow-start-tls.synopsis=Indicates whether clients are allowed to use StartTLS.
+property.allow-start-tls.description=If enabled, the LDAP Connection Handler allows clients to use the StartTLS extended operation to initiate secure communication over an otherwise insecure channel. Note that this is only allowed if the LDAP Connection Handler is not configured to use SSL, and if the server is configured with a valid key manager provider and a valid trust manager provider.
+property.allow-tcp-reuse-address.synopsis=Indicates whether the LDAP Connection Handler should reuse socket descriptors.
+property.allow-tcp-reuse-address.description=If enabled, the SO_REUSEADDR socket option is used on the server listen socket to potentially allow the reuse of socket descriptors for clients in a TIME_WAIT state. This may help the server avoid temporarily running out of socket descriptors in cases in which a very large number of short-lived connections have been established from the same client system.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the LDAP Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the LDAP Connection Handler implementation.
+property.keep-stats.synopsis=Indicates whether the LDAP Connection Handler should keep statistics.
+property.keep-stats.description=If enabled, the LDAP Connection Handler maintains statistics about the number and types of operations requested over LDAP and the amount of data sent and received.
+property.key-manager-provider.synopsis=Specifies the name of the key manager that should be used with this LDAP Connection Handler .
+property.key-manager-provider.requires-admin-action.synopsis=Changes to this property take effect immediately, but only for subsequent attempts to access the key manager provider for associated client connections.
+property.key-manager-provider.syntax.aggregation.constraint-synopsis=The referenced key manager provider must be enabled when the LDAP Connection Handler is enabled and configured to use SSL or StartTLS.
+property.listen-address.synopsis=Specifies the address or set of addresses on which this LDAP Connection Handler should listen for connections from LDAP clients.
+property.listen-address.description=Multiple addresses may be provided as separate values for this attribute. If no values are provided, then the LDAP Connection Handler listens on all interfaces.
+property.listen-port.synopsis=Specifies the port number on which the LDAP Connection Handler will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.max-blocked-write-time-limit.synopsis=Specifies the maximum length of time that attempts to write data to LDAP clients should be allowed to block.
+property.max-blocked-write-time-limit.description=If an attempt to write data to a client takes longer than this length of time, then the client connection is terminated.
+property.max-request-size.synopsis=Specifies the size in bytes of the largest LDAP request message that will be allowed by this LDAP Connection handler.
+property.max-request-size.description=This property is analogous to the maxBERSize configuration attribute of the Sun Java System Directory Server. This can help prevent denial-of-service attacks by clients that indicate they send extremely large requests to the server causing it to attempt to allocate large amounts of memory.
+property.num-request-handlers.synopsis=Specifies the number of request handlers that are used to read requests from clients.
+property.num-request-handlers.description=The LDAP Connection Handler uses one thread to accept new connections from clients, but uses one or more additional threads to read requests from existing client connections. This ensures that new requests are read efficiently and that the connection handler itself does not become a bottleneck when the server is under heavy load from many clients at the same time.
+property.send-rejection-notice.synopsis=Indicates whether the LDAP Connection Handler should send a notice of disconnection extended response message to the client if a new connection is rejected for some reason.
+property.send-rejection-notice.description=The extended response message may provide an explanation indicating the reason that the connection was rejected.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the LDAP Connection Handler should use when performing SSL communication.
+property.ssl-cert-nickname.description=This is only applicable when the LDAP Connection Handler is configured to use SSL.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.ssl-cipher-suite.synopsis=Specifies the names of the SSL cipher suites that are allowed for use in SSL or StartTLS communication.
+property.ssl-cipher-suite.default-behavior.alias.synopsis=Uses the default set of SSL cipher suites provided by the server's JVM.
+property.ssl-cipher-suite.requires-admin-action.synopsis=Changes to this property take effect immediately but will only impact new SSL/TLS-based sessions created after the change.
+property.ssl-client-auth-policy.synopsis=Specifies the policy that the LDAP Connection Handler should use regarding client SSL certificates.
+property.ssl-client-auth-policy.description=This is only applicable if clients are allowed to use SSL.
+property.ssl-client-auth-policy.syntax.enumeration.value.disabled.synopsis=Clients are not required to provide their own certificates when performing SSL negotiation.
+property.ssl-client-auth-policy.syntax.enumeration.value.optional.synopsis=Clients are requested to provide their own certificates when performing SSL negotiation, but still accept the connection even if the client does not provide a certificate.
+property.ssl-client-auth-policy.syntax.enumeration.value.required.synopsis=Clients are required to provide their own certificates when performing SSL negotiation and are refused access if the do not provide a certificate.
+property.ssl-protocol.synopsis=Specifies the names of the SSL protocols that are allowed for use in SSL or StartTLS communication.
+property.ssl-protocol.default-behavior.alias.synopsis=Uses the default set of SSL protocols provided by the server's JVM.
+property.ssl-protocol.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
+property.trust-manager-provider.synopsis=Specifies the name of the trust manager that should be used with the LDAP Connection Handler .
+property.trust-manager-provider.requires-admin-action.synopsis=Changes to this property take effect immediately, but only for subsequent attempts to access the trust manager provider for associated client connections.
+property.trust-manager-provider.syntax.aggregation.constraint-synopsis=The referenced trust manager provider must be enabled when the LDAP Connection Handler is enabled and configured to use SSL or StartTLS.
+property.use-ssl.synopsis=Indicates whether the LDAP Connection Handler should use SSL.
+property.use-ssl.description=If enabled, the LDAP Connection Handler will use SSL to encrypt communication with the clients.
+property.use-tcp-keep-alive.synopsis=Indicates whether the LDAP Connection Handler should use TCP keep-alive.
+property.use-tcp-keep-alive.description=If enabled, the SO_KEEPALIVE socket option is used to indicate that TCP keepalive messages should periodically be sent to the client to verify that the associated connection is still valid. This may also help prevent cases in which intermediate network hardware could silently drop an otherwise idle client connection, provided that the keepalive interval configured in the underlying operating system is smaller than the timeout enforced by the network hardware.
+property.use-tcp-no-delay.synopsis=Indicates whether the LDAP Connection Handler should use TCP no-delay.
+property.use-tcp-no-delay.description=If enabled, the TCP_NODELAY socket option is used to ensure that response messages to the client are sent immediately rather than potentially waiting to determine whether additional response messages can be sent in the same packet. In most cases, using the TCP_NODELAY socket option provides better performance and lower response times, but disabling it may help for some cases in which the server sends a large number of entries to a client in response to a search request.
diff --git a/opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_ko.properties b/opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..cbdadac
--- /dev/null
+++ b/opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_ko.properties
@@ -0,0 +1,65 @@
+user-friendly-name=LDAP Connection Handler
+user-friendly-plural-name=LDAP Connection Handlers
+synopsis=The LDAP Connection Handler is used to interact with clients using LDAP.
+description=It provides full support for LDAPv3 and limited support for LDAPv2.
+constraint.1.synopsis=A Key Manager Provider must be specified when this LDAP Connection Handler is enabled and it is configured to use SSL or StartTLS.
+constraint.2.synopsis=A Trust Manager Provider must be specified when this LDAP Connection Handler is enabled and it is configured to use SSL or StartTLS.
+constraint.3.synopsis=A LDAP Connection Handler cannot be configured to support SSL and StartTLS at the same time. Either SSL or StartTLS must be disabled in order for this LDAP Connection Handler to be used.
+property.accept-backlog.synopsis=Specifies the maximum number of pending connection attempts that are allowed to queue up in the accept backlog before the server starts rejecting new connection attempts.
+property.accept-backlog.description=This is primarily an issue for cases in which a large number of connections are established to the server in a very short period of time (for example, a benchmark utility that creates a large number of client threads that each have their own connection to the server) and the connection handler is unable to keep up with the rate at which the new connections are established.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.allow-ldap-v2.synopsis=Indicates whether connections from LDAPv2 clients are allowed.
+property.allow-ldap-v2.description=If LDAPv2 clients are allowed, then only a minimal degree of special support are provided for them to ensure that LDAPv3-specific protocol elements (for example, Configuration Guide 25 controls, extended response messages, intermediate response messages, referrals) are not sent to an LDAPv2 client.
+property.allow-start-tls.synopsis=Indicates whether clients are allowed to use StartTLS.
+property.allow-start-tls.description=If enabled, the LDAP Connection Handler allows clients to use the StartTLS extended operation to initiate secure communication over an otherwise insecure channel. Note that this is only allowed if the LDAP Connection Handler is not configured to use SSL, and if the server is configured with a valid key manager provider and a valid trust manager provider.
+property.allow-tcp-reuse-address.synopsis=Indicates whether the LDAP Connection Handler should reuse socket descriptors.
+property.allow-tcp-reuse-address.description=If enabled, the SO_REUSEADDR socket option is used on the server listen socket to potentially allow the reuse of socket descriptors for clients in a TIME_WAIT state. This may help the server avoid temporarily running out of socket descriptors in cases in which a very large number of short-lived connections have been established from the same client system.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the LDAP Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the LDAP Connection Handler implementation.
+property.keep-stats.synopsis=Indicates whether the LDAP Connection Handler should keep statistics.
+property.keep-stats.description=If enabled, the LDAP Connection Handler maintains statistics about the number and types of operations requested over LDAP and the amount of data sent and received.
+property.key-manager-provider.synopsis=Specifies the name of the key manager that should be used with this LDAP Connection Handler .
+property.key-manager-provider.requires-admin-action.synopsis=Changes to this property take effect immediately, but only for subsequent attempts to access the key manager provider for associated client connections.
+property.key-manager-provider.syntax.aggregation.constraint-synopsis=The referenced key manager provider must be enabled when the LDAP Connection Handler is enabled and configured to use SSL or StartTLS.
+property.listen-address.synopsis=Specifies the address or set of addresses on which this LDAP Connection Handler should listen for connections from LDAP clients.
+property.listen-address.description=Multiple addresses may be provided as separate values for this attribute. If no values are provided, then the LDAP Connection Handler listens on all interfaces.
+property.listen-port.synopsis=Specifies the port number on which the LDAP Connection Handler will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.max-blocked-write-time-limit.synopsis=Specifies the maximum length of time that attempts to write data to LDAP clients should be allowed to block.
+property.max-blocked-write-time-limit.description=If an attempt to write data to a client takes longer than this length of time, then the client connection is terminated.
+property.max-request-size.synopsis=Specifies the size in bytes of the largest LDAP request message that will be allowed by this LDAP Connection handler.
+property.max-request-size.description=This property is analogous to the maxBERSize configuration attribute of the Sun Java System Directory Server. This can help prevent denial-of-service attacks by clients that indicate they send extremely large requests to the server causing it to attempt to allocate large amounts of memory.
+property.num-request-handlers.synopsis=Specifies the number of request handlers that are used to read requests from clients.
+property.num-request-handlers.description=The LDAP Connection Handler uses one thread to accept new connections from clients, but uses one or more additional threads to read requests from existing client connections. This ensures that new requests are read efficiently and that the connection handler itself does not become a bottleneck when the server is under heavy load from many clients at the same time.
+property.send-rejection-notice.synopsis=Indicates whether the LDAP Connection Handler should send a notice of disconnection extended response message to the client if a new connection is rejected for some reason.
+property.send-rejection-notice.description=The extended response message may provide an explanation indicating the reason that the connection was rejected.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the LDAP Connection Handler should use when performing SSL communication.
+property.ssl-cert-nickname.description=This is only applicable when the LDAP Connection Handler is configured to use SSL.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.ssl-cipher-suite.synopsis=Specifies the names of the SSL cipher suites that are allowed for use in SSL or StartTLS communication.
+property.ssl-cipher-suite.default-behavior.alias.synopsis=Uses the default set of SSL cipher suites provided by the server's JVM.
+property.ssl-cipher-suite.requires-admin-action.synopsis=Changes to this property take effect immediately but will only impact new SSL/TLS-based sessions created after the change.
+property.ssl-client-auth-policy.synopsis=Specifies the policy that the LDAP Connection Handler should use regarding client SSL certificates.
+property.ssl-client-auth-policy.description=This is only applicable if clients are allowed to use SSL.
+property.ssl-client-auth-policy.syntax.enumeration.value.disabled.synopsis=Clients are not required to provide their own certificates when performing SSL negotiation.
+property.ssl-client-auth-policy.syntax.enumeration.value.optional.synopsis=Clients are requested to provide their own certificates when performing SSL negotiation, but still accept the connection even if the client does not provide a certificate.
+property.ssl-client-auth-policy.syntax.enumeration.value.required.synopsis=Clients are required to provide their own certificates when performing SSL negotiation and are refused access if the do not provide a certificate.
+property.ssl-protocol.synopsis=Specifies the names of the SSL protocols that are allowed for use in SSL or StartTLS communication.
+property.ssl-protocol.default-behavior.alias.synopsis=Uses the default set of SSL protocols provided by the server's JVM.
+property.ssl-protocol.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
+property.trust-manager-provider.synopsis=Specifies the name of the trust manager that should be used with the LDAP Connection Handler .
+property.trust-manager-provider.requires-admin-action.synopsis=Changes to this property take effect immediately, but only for subsequent attempts to access the trust manager provider for associated client connections.
+property.trust-manager-provider.syntax.aggregation.constraint-synopsis=The referenced trust manager provider must be enabled when the LDAP Connection Handler is enabled and configured to use SSL or StartTLS.
+property.use-ssl.synopsis=Indicates whether the LDAP Connection Handler should use SSL.
+property.use-ssl.description=If enabled, the LDAP Connection Handler will use SSL to encrypt communication with the clients.
+property.use-tcp-keep-alive.synopsis=Indicates whether the LDAP Connection Handler should use TCP keep-alive.
+property.use-tcp-keep-alive.description=If enabled, the SO_KEEPALIVE socket option is used to indicate that TCP keepalive messages should periodically be sent to the client to verify that the associated connection is still valid. This may also help prevent cases in which intermediate network hardware could silently drop an otherwise idle client connection, provided that the keepalive interval configured in the underlying operating system is smaller than the timeout enforced by the network hardware.
+property.use-tcp-no-delay.synopsis=Indicates whether the LDAP Connection Handler should use TCP no-delay.
+property.use-tcp-no-delay.description=If enabled, the TCP_NODELAY socket option is used to ensure that response messages to the client are sent immediately rather than potentially waiting to determine whether additional response messages can be sent in the same packet. In most cases, using the TCP_NODELAY socket option provides better performance and lower response times, but disabling it may help for some cases in which the server sends a large number of entries to a client in response to a search request.
diff --git a/opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..cbdadac
--- /dev/null
+++ b/opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,65 @@
+user-friendly-name=LDAP Connection Handler
+user-friendly-plural-name=LDAP Connection Handlers
+synopsis=The LDAP Connection Handler is used to interact with clients using LDAP.
+description=It provides full support for LDAPv3 and limited support for LDAPv2.
+constraint.1.synopsis=A Key Manager Provider must be specified when this LDAP Connection Handler is enabled and it is configured to use SSL or StartTLS.
+constraint.2.synopsis=A Trust Manager Provider must be specified when this LDAP Connection Handler is enabled and it is configured to use SSL or StartTLS.
+constraint.3.synopsis=A LDAP Connection Handler cannot be configured to support SSL and StartTLS at the same time. Either SSL or StartTLS must be disabled in order for this LDAP Connection Handler to be used.
+property.accept-backlog.synopsis=Specifies the maximum number of pending connection attempts that are allowed to queue up in the accept backlog before the server starts rejecting new connection attempts.
+property.accept-backlog.description=This is primarily an issue for cases in which a large number of connections are established to the server in a very short period of time (for example, a benchmark utility that creates a large number of client threads that each have their own connection to the server) and the connection handler is unable to keep up with the rate at which the new connections are established.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.allow-ldap-v2.synopsis=Indicates whether connections from LDAPv2 clients are allowed.
+property.allow-ldap-v2.description=If LDAPv2 clients are allowed, then only a minimal degree of special support are provided for them to ensure that LDAPv3-specific protocol elements (for example, Configuration Guide 25 controls, extended response messages, intermediate response messages, referrals) are not sent to an LDAPv2 client.
+property.allow-start-tls.synopsis=Indicates whether clients are allowed to use StartTLS.
+property.allow-start-tls.description=If enabled, the LDAP Connection Handler allows clients to use the StartTLS extended operation to initiate secure communication over an otherwise insecure channel. Note that this is only allowed if the LDAP Connection Handler is not configured to use SSL, and if the server is configured with a valid key manager provider and a valid trust manager provider.
+property.allow-tcp-reuse-address.synopsis=Indicates whether the LDAP Connection Handler should reuse socket descriptors.
+property.allow-tcp-reuse-address.description=If enabled, the SO_REUSEADDR socket option is used on the server listen socket to potentially allow the reuse of socket descriptors for clients in a TIME_WAIT state. This may help the server avoid temporarily running out of socket descriptors in cases in which a very large number of short-lived connections have been established from the same client system.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the LDAP Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the LDAP Connection Handler implementation.
+property.keep-stats.synopsis=Indicates whether the LDAP Connection Handler should keep statistics.
+property.keep-stats.description=If enabled, the LDAP Connection Handler maintains statistics about the number and types of operations requested over LDAP and the amount of data sent and received.
+property.key-manager-provider.synopsis=Specifies the name of the key manager that should be used with this LDAP Connection Handler .
+property.key-manager-provider.requires-admin-action.synopsis=Changes to this property take effect immediately, but only for subsequent attempts to access the key manager provider for associated client connections.
+property.key-manager-provider.syntax.aggregation.constraint-synopsis=The referenced key manager provider must be enabled when the LDAP Connection Handler is enabled and configured to use SSL or StartTLS.
+property.listen-address.synopsis=Specifies the address or set of addresses on which this LDAP Connection Handler should listen for connections from LDAP clients.
+property.listen-address.description=Multiple addresses may be provided as separate values for this attribute. If no values are provided, then the LDAP Connection Handler listens on all interfaces.
+property.listen-port.synopsis=Specifies the port number on which the LDAP Connection Handler will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.max-blocked-write-time-limit.synopsis=Specifies the maximum length of time that attempts to write data to LDAP clients should be allowed to block.
+property.max-blocked-write-time-limit.description=If an attempt to write data to a client takes longer than this length of time, then the client connection is terminated.
+property.max-request-size.synopsis=Specifies the size in bytes of the largest LDAP request message that will be allowed by this LDAP Connection handler.
+property.max-request-size.description=This property is analogous to the maxBERSize configuration attribute of the Sun Java System Directory Server. This can help prevent denial-of-service attacks by clients that indicate they send extremely large requests to the server causing it to attempt to allocate large amounts of memory.
+property.num-request-handlers.synopsis=Specifies the number of request handlers that are used to read requests from clients.
+property.num-request-handlers.description=The LDAP Connection Handler uses one thread to accept new connections from clients, but uses one or more additional threads to read requests from existing client connections. This ensures that new requests are read efficiently and that the connection handler itself does not become a bottleneck when the server is under heavy load from many clients at the same time.
+property.send-rejection-notice.synopsis=Indicates whether the LDAP Connection Handler should send a notice of disconnection extended response message to the client if a new connection is rejected for some reason.
+property.send-rejection-notice.description=The extended response message may provide an explanation indicating the reason that the connection was rejected.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the LDAP Connection Handler should use when performing SSL communication.
+property.ssl-cert-nickname.description=This is only applicable when the LDAP Connection Handler is configured to use SSL.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.ssl-cipher-suite.synopsis=Specifies the names of the SSL cipher suites that are allowed for use in SSL or StartTLS communication.
+property.ssl-cipher-suite.default-behavior.alias.synopsis=Uses the default set of SSL cipher suites provided by the server's JVM.
+property.ssl-cipher-suite.requires-admin-action.synopsis=Changes to this property take effect immediately but will only impact new SSL/TLS-based sessions created after the change.
+property.ssl-client-auth-policy.synopsis=Specifies the policy that the LDAP Connection Handler should use regarding client SSL certificates.
+property.ssl-client-auth-policy.description=This is only applicable if clients are allowed to use SSL.
+property.ssl-client-auth-policy.syntax.enumeration.value.disabled.synopsis=Clients are not required to provide their own certificates when performing SSL negotiation.
+property.ssl-client-auth-policy.syntax.enumeration.value.optional.synopsis=Clients are requested to provide their own certificates when performing SSL negotiation, but still accept the connection even if the client does not provide a certificate.
+property.ssl-client-auth-policy.syntax.enumeration.value.required.synopsis=Clients are required to provide their own certificates when performing SSL negotiation and are refused access if the do not provide a certificate.
+property.ssl-protocol.synopsis=Specifies the names of the SSL protocols that are allowed for use in SSL or StartTLS communication.
+property.ssl-protocol.default-behavior.alias.synopsis=Uses the default set of SSL protocols provided by the server's JVM.
+property.ssl-protocol.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
+property.trust-manager-provider.synopsis=Specifies the name of the trust manager that should be used with the LDAP Connection Handler .
+property.trust-manager-provider.requires-admin-action.synopsis=Changes to this property take effect immediately, but only for subsequent attempts to access the trust manager provider for associated client connections.
+property.trust-manager-provider.syntax.aggregation.constraint-synopsis=The referenced trust manager provider must be enabled when the LDAP Connection Handler is enabled and configured to use SSL or StartTLS.
+property.use-ssl.synopsis=Indicates whether the LDAP Connection Handler should use SSL.
+property.use-ssl.description=If enabled, the LDAP Connection Handler will use SSL to encrypt communication with the clients.
+property.use-tcp-keep-alive.synopsis=Indicates whether the LDAP Connection Handler should use TCP keep-alive.
+property.use-tcp-keep-alive.description=If enabled, the SO_KEEPALIVE socket option is used to indicate that TCP keepalive messages should periodically be sent to the client to verify that the associated connection is still valid. This may also help prevent cases in which intermediate network hardware could silently drop an otherwise idle client connection, provided that the keepalive interval configured in the underlying operating system is smaller than the timeout enforced by the network hardware.
+property.use-tcp-no-delay.synopsis=Indicates whether the LDAP Connection Handler should use TCP no-delay.
+property.use-tcp-no-delay.description=If enabled, the TCP_NODELAY socket option is used to ensure that response messages to the client are sent immediately rather than potentially waiting to determine whether additional response messages can be sent in the same packet. In most cases, using the TCP_NODELAY socket option provides better performance and lower response times, but disabling it may help for some cases in which the server sends a large number of entries to a client in response to a search request.
diff --git a/opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..cbdadac
--- /dev/null
+++ b/opends/src/admin/messages/LDAPConnectionHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,65 @@
+user-friendly-name=LDAP Connection Handler
+user-friendly-plural-name=LDAP Connection Handlers
+synopsis=The LDAP Connection Handler is used to interact with clients using LDAP.
+description=It provides full support for LDAPv3 and limited support for LDAPv2.
+constraint.1.synopsis=A Key Manager Provider must be specified when this LDAP Connection Handler is enabled and it is configured to use SSL or StartTLS.
+constraint.2.synopsis=A Trust Manager Provider must be specified when this LDAP Connection Handler is enabled and it is configured to use SSL or StartTLS.
+constraint.3.synopsis=A LDAP Connection Handler cannot be configured to support SSL and StartTLS at the same time. Either SSL or StartTLS must be disabled in order for this LDAP Connection Handler to be used.
+property.accept-backlog.synopsis=Specifies the maximum number of pending connection attempts that are allowed to queue up in the accept backlog before the server starts rejecting new connection attempts.
+property.accept-backlog.description=This is primarily an issue for cases in which a large number of connections are established to the server in a very short period of time (for example, a benchmark utility that creates a large number of client threads that each have their own connection to the server) and the connection handler is unable to keep up with the rate at which the new connections are established.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.allow-ldap-v2.synopsis=Indicates whether connections from LDAPv2 clients are allowed.
+property.allow-ldap-v2.description=If LDAPv2 clients are allowed, then only a minimal degree of special support are provided for them to ensure that LDAPv3-specific protocol elements (for example, Configuration Guide 25 controls, extended response messages, intermediate response messages, referrals) are not sent to an LDAPv2 client.
+property.allow-start-tls.synopsis=Indicates whether clients are allowed to use StartTLS.
+property.allow-start-tls.description=If enabled, the LDAP Connection Handler allows clients to use the StartTLS extended operation to initiate secure communication over an otherwise insecure channel. Note that this is only allowed if the LDAP Connection Handler is not configured to use SSL, and if the server is configured with a valid key manager provider and a valid trust manager provider.
+property.allow-tcp-reuse-address.synopsis=Indicates whether the LDAP Connection Handler should reuse socket descriptors.
+property.allow-tcp-reuse-address.description=If enabled, the SO_REUSEADDR socket option is used on the server listen socket to potentially allow the reuse of socket descriptors for clients in a TIME_WAIT state. This may help the server avoid temporarily running out of socket descriptors in cases in which a very large number of short-lived connections have been established from the same client system.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the LDAP Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the LDAP Connection Handler implementation.
+property.keep-stats.synopsis=Indicates whether the LDAP Connection Handler should keep statistics.
+property.keep-stats.description=If enabled, the LDAP Connection Handler maintains statistics about the number and types of operations requested over LDAP and the amount of data sent and received.
+property.key-manager-provider.synopsis=Specifies the name of the key manager that should be used with this LDAP Connection Handler .
+property.key-manager-provider.requires-admin-action.synopsis=Changes to this property take effect immediately, but only for subsequent attempts to access the key manager provider for associated client connections.
+property.key-manager-provider.syntax.aggregation.constraint-synopsis=The referenced key manager provider must be enabled when the LDAP Connection Handler is enabled and configured to use SSL or StartTLS.
+property.listen-address.synopsis=Specifies the address or set of addresses on which this LDAP Connection Handler should listen for connections from LDAP clients.
+property.listen-address.description=Multiple addresses may be provided as separate values for this attribute. If no values are provided, then the LDAP Connection Handler listens on all interfaces.
+property.listen-port.synopsis=Specifies the port number on which the LDAP Connection Handler will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.max-blocked-write-time-limit.synopsis=Specifies the maximum length of time that attempts to write data to LDAP clients should be allowed to block.
+property.max-blocked-write-time-limit.description=If an attempt to write data to a client takes longer than this length of time, then the client connection is terminated.
+property.max-request-size.synopsis=Specifies the size in bytes of the largest LDAP request message that will be allowed by this LDAP Connection handler.
+property.max-request-size.description=This property is analogous to the maxBERSize configuration attribute of the Sun Java System Directory Server. This can help prevent denial-of-service attacks by clients that indicate they send extremely large requests to the server causing it to attempt to allocate large amounts of memory.
+property.num-request-handlers.synopsis=Specifies the number of request handlers that are used to read requests from clients.
+property.num-request-handlers.description=The LDAP Connection Handler uses one thread to accept new connections from clients, but uses one or more additional threads to read requests from existing client connections. This ensures that new requests are read efficiently and that the connection handler itself does not become a bottleneck when the server is under heavy load from many clients at the same time.
+property.send-rejection-notice.synopsis=Indicates whether the LDAP Connection Handler should send a notice of disconnection extended response message to the client if a new connection is rejected for some reason.
+property.send-rejection-notice.description=The extended response message may provide an explanation indicating the reason that the connection was rejected.
+property.ssl-cert-nickname.synopsis=Specifies the nickname (also called the alias) of the certificate that the LDAP Connection Handler should use when performing SSL communication.
+property.ssl-cert-nickname.description=This is only applicable when the LDAP Connection Handler is configured to use SSL.
+property.ssl-cert-nickname.default-behavior.alias.synopsis=Let the server decide.
+property.ssl-cipher-suite.synopsis=Specifies the names of the SSL cipher suites that are allowed for use in SSL or StartTLS communication.
+property.ssl-cipher-suite.default-behavior.alias.synopsis=Uses the default set of SSL cipher suites provided by the server's JVM.
+property.ssl-cipher-suite.requires-admin-action.synopsis=Changes to this property take effect immediately but will only impact new SSL/TLS-based sessions created after the change.
+property.ssl-client-auth-policy.synopsis=Specifies the policy that the LDAP Connection Handler should use regarding client SSL certificates.
+property.ssl-client-auth-policy.description=This is only applicable if clients are allowed to use SSL.
+property.ssl-client-auth-policy.syntax.enumeration.value.disabled.synopsis=Clients are not required to provide their own certificates when performing SSL negotiation.
+property.ssl-client-auth-policy.syntax.enumeration.value.optional.synopsis=Clients are requested to provide their own certificates when performing SSL negotiation, but still accept the connection even if the client does not provide a certificate.
+property.ssl-client-auth-policy.syntax.enumeration.value.required.synopsis=Clients are required to provide their own certificates when performing SSL negotiation and are refused access if the do not provide a certificate.
+property.ssl-protocol.synopsis=Specifies the names of the SSL protocols that are allowed for use in SSL or StartTLS communication.
+property.ssl-protocol.default-behavior.alias.synopsis=Uses the default set of SSL protocols provided by the server's JVM.
+property.ssl-protocol.requires-admin-action.synopsis=Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
+property.trust-manager-provider.synopsis=Specifies the name of the trust manager that should be used with the LDAP Connection Handler .
+property.trust-manager-provider.requires-admin-action.synopsis=Changes to this property take effect immediately, but only for subsequent attempts to access the trust manager provider for associated client connections.
+property.trust-manager-provider.syntax.aggregation.constraint-synopsis=The referenced trust manager provider must be enabled when the LDAP Connection Handler is enabled and configured to use SSL or StartTLS.
+property.use-ssl.synopsis=Indicates whether the LDAP Connection Handler should use SSL.
+property.use-ssl.description=If enabled, the LDAP Connection Handler will use SSL to encrypt communication with the clients.
+property.use-tcp-keep-alive.synopsis=Indicates whether the LDAP Connection Handler should use TCP keep-alive.
+property.use-tcp-keep-alive.description=If enabled, the SO_KEEPALIVE socket option is used to indicate that TCP keepalive messages should periodically be sent to the client to verify that the associated connection is still valid. This may also help prevent cases in which intermediate network hardware could silently drop an otherwise idle client connection, provided that the keepalive interval configured in the underlying operating system is smaller than the timeout enforced by the network hardware.
+property.use-tcp-no-delay.synopsis=Indicates whether the LDAP Connection Handler should use TCP no-delay.
+property.use-tcp-no-delay.description=If enabled, the TCP_NODELAY socket option is used to ensure that response messages to the client are sent immediately rather than potentially waiting to determine whether additional response messages can be sent in the same packet. In most cases, using the TCP_NODELAY socket option provides better performance and lower response times, but disabling it may help for some cases in which the server sends a large number of entries to a client in response to a search request.
diff --git a/opends/src/admin/messages/LDIFBackendCfgDefn.properties b/opends/src/admin/messages/LDIFBackendCfgDefn.properties
new file mode 100644
index 0000000..56cac9d
--- /dev/null
+++ b/opends/src/admin/messages/LDIFBackendCfgDefn.properties
@@ -0,0 +1,18 @@
+user-friendly-name=LDIF Backend
+user-friendly-plural-name=LDIF Backends
+synopsis=The LDIF Backend provides a mechanism for interacting with data stored in an LDIF file.
+description=All basic LDAP operations are supported in the LDIF backend although it has minimal support for custom controls.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.is-private-backend.synopsis=Indicates whether the backend should be considered a private backend, which indicates that it is used for storing operational data rather than user-defined information.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.ldif-file.synopsis=Specifies the path to the LDIF file containing the data for this backend.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/LDIFBackendCfgDefn_de.properties b/opends/src/admin/messages/LDIFBackendCfgDefn_de.properties
new file mode 100644
index 0000000..56cac9d
--- /dev/null
+++ b/opends/src/admin/messages/LDIFBackendCfgDefn_de.properties
@@ -0,0 +1,18 @@
+user-friendly-name=LDIF Backend
+user-friendly-plural-name=LDIF Backends
+synopsis=The LDIF Backend provides a mechanism for interacting with data stored in an LDIF file.
+description=All basic LDAP operations are supported in the LDIF backend although it has minimal support for custom controls.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.is-private-backend.synopsis=Indicates whether the backend should be considered a private backend, which indicates that it is used for storing operational data rather than user-defined information.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.ldif-file.synopsis=Specifies the path to the LDIF file containing the data for this backend.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/LDIFBackendCfgDefn_es.properties b/opends/src/admin/messages/LDIFBackendCfgDefn_es.properties
new file mode 100644
index 0000000..56cac9d
--- /dev/null
+++ b/opends/src/admin/messages/LDIFBackendCfgDefn_es.properties
@@ -0,0 +1,18 @@
+user-friendly-name=LDIF Backend
+user-friendly-plural-name=LDIF Backends
+synopsis=The LDIF Backend provides a mechanism for interacting with data stored in an LDIF file.
+description=All basic LDAP operations are supported in the LDIF backend although it has minimal support for custom controls.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.is-private-backend.synopsis=Indicates whether the backend should be considered a private backend, which indicates that it is used for storing operational data rather than user-defined information.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.ldif-file.synopsis=Specifies the path to the LDIF file containing the data for this backend.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/LDIFBackendCfgDefn_fr.properties b/opends/src/admin/messages/LDIFBackendCfgDefn_fr.properties
new file mode 100644
index 0000000..56cac9d
--- /dev/null
+++ b/opends/src/admin/messages/LDIFBackendCfgDefn_fr.properties
@@ -0,0 +1,18 @@
+user-friendly-name=LDIF Backend
+user-friendly-plural-name=LDIF Backends
+synopsis=The LDIF Backend provides a mechanism for interacting with data stored in an LDIF file.
+description=All basic LDAP operations are supported in the LDIF backend although it has minimal support for custom controls.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.is-private-backend.synopsis=Indicates whether the backend should be considered a private backend, which indicates that it is used for storing operational data rather than user-defined information.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.ldif-file.synopsis=Specifies the path to the LDIF file containing the data for this backend.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/LDIFBackendCfgDefn_ja.properties b/opends/src/admin/messages/LDIFBackendCfgDefn_ja.properties
new file mode 100644
index 0000000..56cac9d
--- /dev/null
+++ b/opends/src/admin/messages/LDIFBackendCfgDefn_ja.properties
@@ -0,0 +1,18 @@
+user-friendly-name=LDIF Backend
+user-friendly-plural-name=LDIF Backends
+synopsis=The LDIF Backend provides a mechanism for interacting with data stored in an LDIF file.
+description=All basic LDAP operations are supported in the LDIF backend although it has minimal support for custom controls.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.is-private-backend.synopsis=Indicates whether the backend should be considered a private backend, which indicates that it is used for storing operational data rather than user-defined information.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.ldif-file.synopsis=Specifies the path to the LDIF file containing the data for this backend.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/LDIFBackendCfgDefn_ko.properties b/opends/src/admin/messages/LDIFBackendCfgDefn_ko.properties
new file mode 100644
index 0000000..56cac9d
--- /dev/null
+++ b/opends/src/admin/messages/LDIFBackendCfgDefn_ko.properties
@@ -0,0 +1,18 @@
+user-friendly-name=LDIF Backend
+user-friendly-plural-name=LDIF Backends
+synopsis=The LDIF Backend provides a mechanism for interacting with data stored in an LDIF file.
+description=All basic LDAP operations are supported in the LDIF backend although it has minimal support for custom controls.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.is-private-backend.synopsis=Indicates whether the backend should be considered a private backend, which indicates that it is used for storing operational data rather than user-defined information.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.ldif-file.synopsis=Specifies the path to the LDIF file containing the data for this backend.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/LDIFBackendCfgDefn_zh_CN.properties b/opends/src/admin/messages/LDIFBackendCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..56cac9d
--- /dev/null
+++ b/opends/src/admin/messages/LDIFBackendCfgDefn_zh_CN.properties
@@ -0,0 +1,18 @@
+user-friendly-name=LDIF Backend
+user-friendly-plural-name=LDIF Backends
+synopsis=The LDIF Backend provides a mechanism for interacting with data stored in an LDIF file.
+description=All basic LDAP operations are supported in the LDIF backend although it has minimal support for custom controls.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.is-private-backend.synopsis=Indicates whether the backend should be considered a private backend, which indicates that it is used for storing operational data rather than user-defined information.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.ldif-file.synopsis=Specifies the path to the LDIF file containing the data for this backend.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/LDIFBackendCfgDefn_zh_TW.properties b/opends/src/admin/messages/LDIFBackendCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..56cac9d
--- /dev/null
+++ b/opends/src/admin/messages/LDIFBackendCfgDefn_zh_TW.properties
@@ -0,0 +1,18 @@
+user-friendly-name=LDIF Backend
+user-friendly-plural-name=LDIF Backends
+synopsis=The LDIF Backend provides a mechanism for interacting with data stored in an LDIF file.
+description=All basic LDAP operations are supported in the LDIF backend although it has minimal support for custom controls.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.is-private-backend.synopsis=Indicates whether the backend should be considered a private backend, which indicates that it is used for storing operational data rather than user-defined information.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.ldif-file.synopsis=Specifies the path to the LDIF file containing the data for this backend.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/LDIFConnectionHandlerCfgDefn.properties b/opends/src/admin/messages/LDIFConnectionHandlerCfgDefn.properties
new file mode 100644
index 0000000..b7756f6
--- /dev/null
+++ b/opends/src/admin/messages/LDIFConnectionHandlerCfgDefn.properties
@@ -0,0 +1,16 @@
+user-friendly-name=LDIF Connection Handler
+user-friendly-plural-name=LDIF Connection Handlers
+synopsis=The LDIF Connection Handler is used to process changes in the server using internal operations, where the changes to process are read from an LDIF file.
+description=The connection handler periodically looks for the existence of a new file, processes the changes contained in that file as internal operations, and writse the result to an output file with comments indicating the result of the processing. NOTE: By default LDIF Connection Handler operations are not logged because they are internal operations. If you want to log these operations, allow internal logging in the access log publisher.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the LDIF Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the LDIF Connection Handler implementation.
+property.ldif-directory.synopsis=Specifies the path to the directory in which the LDIF files should be placed.
+property.poll-interval.synopsis=Specifies how frequently the LDIF connection handler should check the LDIF directory to determine whether a new LDIF file has been added.
diff --git a/opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_de.properties b/opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..b7756f6
--- /dev/null
+++ b/opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_de.properties
@@ -0,0 +1,16 @@
+user-friendly-name=LDIF Connection Handler
+user-friendly-plural-name=LDIF Connection Handlers
+synopsis=The LDIF Connection Handler is used to process changes in the server using internal operations, where the changes to process are read from an LDIF file.
+description=The connection handler periodically looks for the existence of a new file, processes the changes contained in that file as internal operations, and writse the result to an output file with comments indicating the result of the processing. NOTE: By default LDIF Connection Handler operations are not logged because they are internal operations. If you want to log these operations, allow internal logging in the access log publisher.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the LDIF Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the LDIF Connection Handler implementation.
+property.ldif-directory.synopsis=Specifies the path to the directory in which the LDIF files should be placed.
+property.poll-interval.synopsis=Specifies how frequently the LDIF connection handler should check the LDIF directory to determine whether a new LDIF file has been added.
diff --git a/opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_es.properties b/opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..b7756f6
--- /dev/null
+++ b/opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_es.properties
@@ -0,0 +1,16 @@
+user-friendly-name=LDIF Connection Handler
+user-friendly-plural-name=LDIF Connection Handlers
+synopsis=The LDIF Connection Handler is used to process changes in the server using internal operations, where the changes to process are read from an LDIF file.
+description=The connection handler periodically looks for the existence of a new file, processes the changes contained in that file as internal operations, and writse the result to an output file with comments indicating the result of the processing. NOTE: By default LDIF Connection Handler operations are not logged because they are internal operations. If you want to log these operations, allow internal logging in the access log publisher.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the LDIF Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the LDIF Connection Handler implementation.
+property.ldif-directory.synopsis=Specifies the path to the directory in which the LDIF files should be placed.
+property.poll-interval.synopsis=Specifies how frequently the LDIF connection handler should check the LDIF directory to determine whether a new LDIF file has been added.
diff --git a/opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_fr.properties b/opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..b7756f6
--- /dev/null
+++ b/opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_fr.properties
@@ -0,0 +1,16 @@
+user-friendly-name=LDIF Connection Handler
+user-friendly-plural-name=LDIF Connection Handlers
+synopsis=The LDIF Connection Handler is used to process changes in the server using internal operations, where the changes to process are read from an LDIF file.
+description=The connection handler periodically looks for the existence of a new file, processes the changes contained in that file as internal operations, and writse the result to an output file with comments indicating the result of the processing. NOTE: By default LDIF Connection Handler operations are not logged because they are internal operations. If you want to log these operations, allow internal logging in the access log publisher.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the LDIF Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the LDIF Connection Handler implementation.
+property.ldif-directory.synopsis=Specifies the path to the directory in which the LDIF files should be placed.
+property.poll-interval.synopsis=Specifies how frequently the LDIF connection handler should check the LDIF directory to determine whether a new LDIF file has been added.
diff --git a/opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_ja.properties b/opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..b7756f6
--- /dev/null
+++ b/opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_ja.properties
@@ -0,0 +1,16 @@
+user-friendly-name=LDIF Connection Handler
+user-friendly-plural-name=LDIF Connection Handlers
+synopsis=The LDIF Connection Handler is used to process changes in the server using internal operations, where the changes to process are read from an LDIF file.
+description=The connection handler periodically looks for the existence of a new file, processes the changes contained in that file as internal operations, and writse the result to an output file with comments indicating the result of the processing. NOTE: By default LDIF Connection Handler operations are not logged because they are internal operations. If you want to log these operations, allow internal logging in the access log publisher.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the LDIF Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the LDIF Connection Handler implementation.
+property.ldif-directory.synopsis=Specifies the path to the directory in which the LDIF files should be placed.
+property.poll-interval.synopsis=Specifies how frequently the LDIF connection handler should check the LDIF directory to determine whether a new LDIF file has been added.
diff --git a/opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_ko.properties b/opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..b7756f6
--- /dev/null
+++ b/opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_ko.properties
@@ -0,0 +1,16 @@
+user-friendly-name=LDIF Connection Handler
+user-friendly-plural-name=LDIF Connection Handlers
+synopsis=The LDIF Connection Handler is used to process changes in the server using internal operations, where the changes to process are read from an LDIF file.
+description=The connection handler periodically looks for the existence of a new file, processes the changes contained in that file as internal operations, and writse the result to an output file with comments indicating the result of the processing. NOTE: By default LDIF Connection Handler operations are not logged because they are internal operations. If you want to log these operations, allow internal logging in the access log publisher.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the LDIF Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the LDIF Connection Handler implementation.
+property.ldif-directory.synopsis=Specifies the path to the directory in which the LDIF files should be placed.
+property.poll-interval.synopsis=Specifies how frequently the LDIF connection handler should check the LDIF directory to determine whether a new LDIF file has been added.
diff --git a/opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..b7756f6
--- /dev/null
+++ b/opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,16 @@
+user-friendly-name=LDIF Connection Handler
+user-friendly-plural-name=LDIF Connection Handlers
+synopsis=The LDIF Connection Handler is used to process changes in the server using internal operations, where the changes to process are read from an LDIF file.
+description=The connection handler periodically looks for the existence of a new file, processes the changes contained in that file as internal operations, and writse the result to an output file with comments indicating the result of the processing. NOTE: By default LDIF Connection Handler operations are not logged because they are internal operations. If you want to log these operations, allow internal logging in the access log publisher.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the LDIF Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the LDIF Connection Handler implementation.
+property.ldif-directory.synopsis=Specifies the path to the directory in which the LDIF files should be placed.
+property.poll-interval.synopsis=Specifies how frequently the LDIF connection handler should check the LDIF directory to determine whether a new LDIF file has been added.
diff --git a/opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..b7756f6
--- /dev/null
+++ b/opends/src/admin/messages/LDIFConnectionHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,16 @@
+user-friendly-name=LDIF Connection Handler
+user-friendly-plural-name=LDIF Connection Handlers
+synopsis=The LDIF Connection Handler is used to process changes in the server using internal operations, where the changes to process are read from an LDIF file.
+description=The connection handler periodically looks for the existence of a new file, processes the changes contained in that file as internal operations, and writse the result to an output file with comments indicating the result of the processing. NOTE: By default LDIF Connection Handler operations are not logged because they are internal operations. If you want to log these operations, allow internal logging in the access log publisher.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the LDIF Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the LDIF Connection Handler implementation.
+property.ldif-directory.synopsis=Specifies the path to the directory in which the LDIF files should be placed.
+property.poll-interval.synopsis=Specifies how frequently the LDIF connection handler should check the LDIF directory to determine whether a new LDIF file has been added.
diff --git a/opends/src/admin/messages/LastModPluginCfgDefn.properties b/opends/src/admin/messages/LastModPluginCfgDefn.properties
new file mode 100644
index 0000000..d5dfca2
--- /dev/null
+++ b/opends/src/admin/messages/LastModPluginCfgDefn.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Last Mod Plugin
+user-friendly-plural-name=Last Mod Plugins
+synopsis=The Last Mod Plugin is used to ensure that the creatorsName and createTimestamp attributes are included in an entry whenever it is added to the server and also to ensure that the modifiersName and modifyTimestamp attributes are updated whenever an entry is modified or renamed.
+description=This behavior is described in RFC 4512. The implementation for the LastMod plugin is contained in the org.opends.server.plugins.LastModPlugin class. It must be configured with the preOperationAdd, preOperationModify, and preOperationModifyDN plugin types, but it does not have any other custom configuration.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/LastModPluginCfgDefn_de.properties b/opends/src/admin/messages/LastModPluginCfgDefn_de.properties
new file mode 100644
index 0000000..d5dfca2
--- /dev/null
+++ b/opends/src/admin/messages/LastModPluginCfgDefn_de.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Last Mod Plugin
+user-friendly-plural-name=Last Mod Plugins
+synopsis=The Last Mod Plugin is used to ensure that the creatorsName and createTimestamp attributes are included in an entry whenever it is added to the server and also to ensure that the modifiersName and modifyTimestamp attributes are updated whenever an entry is modified or renamed.
+description=This behavior is described in RFC 4512. The implementation for the LastMod plugin is contained in the org.opends.server.plugins.LastModPlugin class. It must be configured with the preOperationAdd, preOperationModify, and preOperationModifyDN plugin types, but it does not have any other custom configuration.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/LastModPluginCfgDefn_es.properties b/opends/src/admin/messages/LastModPluginCfgDefn_es.properties
new file mode 100644
index 0000000..d5dfca2
--- /dev/null
+++ b/opends/src/admin/messages/LastModPluginCfgDefn_es.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Last Mod Plugin
+user-friendly-plural-name=Last Mod Plugins
+synopsis=The Last Mod Plugin is used to ensure that the creatorsName and createTimestamp attributes are included in an entry whenever it is added to the server and also to ensure that the modifiersName and modifyTimestamp attributes are updated whenever an entry is modified or renamed.
+description=This behavior is described in RFC 4512. The implementation for the LastMod plugin is contained in the org.opends.server.plugins.LastModPlugin class. It must be configured with the preOperationAdd, preOperationModify, and preOperationModifyDN plugin types, but it does not have any other custom configuration.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/LastModPluginCfgDefn_fr.properties b/opends/src/admin/messages/LastModPluginCfgDefn_fr.properties
new file mode 100644
index 0000000..d5dfca2
--- /dev/null
+++ b/opends/src/admin/messages/LastModPluginCfgDefn_fr.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Last Mod Plugin
+user-friendly-plural-name=Last Mod Plugins
+synopsis=The Last Mod Plugin is used to ensure that the creatorsName and createTimestamp attributes are included in an entry whenever it is added to the server and also to ensure that the modifiersName and modifyTimestamp attributes are updated whenever an entry is modified or renamed.
+description=This behavior is described in RFC 4512. The implementation for the LastMod plugin is contained in the org.opends.server.plugins.LastModPlugin class. It must be configured with the preOperationAdd, preOperationModify, and preOperationModifyDN plugin types, but it does not have any other custom configuration.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/LastModPluginCfgDefn_ja.properties b/opends/src/admin/messages/LastModPluginCfgDefn_ja.properties
new file mode 100644
index 0000000..d5dfca2
--- /dev/null
+++ b/opends/src/admin/messages/LastModPluginCfgDefn_ja.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Last Mod Plugin
+user-friendly-plural-name=Last Mod Plugins
+synopsis=The Last Mod Plugin is used to ensure that the creatorsName and createTimestamp attributes are included in an entry whenever it is added to the server and also to ensure that the modifiersName and modifyTimestamp attributes are updated whenever an entry is modified or renamed.
+description=This behavior is described in RFC 4512. The implementation for the LastMod plugin is contained in the org.opends.server.plugins.LastModPlugin class. It must be configured with the preOperationAdd, preOperationModify, and preOperationModifyDN plugin types, but it does not have any other custom configuration.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/LastModPluginCfgDefn_ko.properties b/opends/src/admin/messages/LastModPluginCfgDefn_ko.properties
new file mode 100644
index 0000000..d5dfca2
--- /dev/null
+++ b/opends/src/admin/messages/LastModPluginCfgDefn_ko.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Last Mod Plugin
+user-friendly-plural-name=Last Mod Plugins
+synopsis=The Last Mod Plugin is used to ensure that the creatorsName and createTimestamp attributes are included in an entry whenever it is added to the server and also to ensure that the modifiersName and modifyTimestamp attributes are updated whenever an entry is modified or renamed.
+description=This behavior is described in RFC 4512. The implementation for the LastMod plugin is contained in the org.opends.server.plugins.LastModPlugin class. It must be configured with the preOperationAdd, preOperationModify, and preOperationModifyDN plugin types, but it does not have any other custom configuration.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/LastModPluginCfgDefn_zh_CN.properties b/opends/src/admin/messages/LastModPluginCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..d5dfca2
--- /dev/null
+++ b/opends/src/admin/messages/LastModPluginCfgDefn_zh_CN.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Last Mod Plugin
+user-friendly-plural-name=Last Mod Plugins
+synopsis=The Last Mod Plugin is used to ensure that the creatorsName and createTimestamp attributes are included in an entry whenever it is added to the server and also to ensure that the modifiersName and modifyTimestamp attributes are updated whenever an entry is modified or renamed.
+description=This behavior is described in RFC 4512. The implementation for the LastMod plugin is contained in the org.opends.server.plugins.LastModPlugin class. It must be configured with the preOperationAdd, preOperationModify, and preOperationModifyDN plugin types, but it does not have any other custom configuration.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/LastModPluginCfgDefn_zh_TW.properties b/opends/src/admin/messages/LastModPluginCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..d5dfca2
--- /dev/null
+++ b/opends/src/admin/messages/LastModPluginCfgDefn_zh_TW.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Last Mod Plugin
+user-friendly-plural-name=Last Mod Plugins
+synopsis=The Last Mod Plugin is used to ensure that the creatorsName and createTimestamp attributes are included in an entry whenever it is added to the server and also to ensure that the modifiersName and modifyTimestamp attributes are updated whenever an entry is modified or renamed.
+description=This behavior is described in RFC 4512. The implementation for the LastMod plugin is contained in the org.opends.server.plugins.LastModPlugin class. It must be configured with the preOperationAdd, preOperationModify, and preOperationModifyDN plugin types, but it does not have any other custom configuration.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn.properties b/opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn.properties
new file mode 100644
index 0000000..b5a8e68
--- /dev/null
+++ b/opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Length Based Password Validator
+user-friendly-plural-name=Length Based Password Validators
+synopsis=The Length Based Password Validator is used to determine whether a proposed password is acceptable based on whether the number of characters it contains falls within an acceptable range of values.
+description=Both upper and lower bounds may be defined.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.max-password-length.synopsis=Specifies the maximum number of characters that can be included in a proposed password.
+property.max-password-length.description=A value of zero indicates that there will be no upper bound enforced. If both minimum and maximum lengths are defined, then the minimum length must be less than or equal to the maximum length.
+property.min-password-length.synopsis=Specifies the minimum number of characters that must be included in a proposed password.
+property.min-password-length.description=A value of zero indicates that there will be no lower bound enforced. If both minimum and maximum lengths are defined, then the minimum length must be less than or equal to the maximum length.
diff --git a/opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_de.properties b/opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_de.properties
new file mode 100644
index 0000000..b5a8e68
--- /dev/null
+++ b/opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_de.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Length Based Password Validator
+user-friendly-plural-name=Length Based Password Validators
+synopsis=The Length Based Password Validator is used to determine whether a proposed password is acceptable based on whether the number of characters it contains falls within an acceptable range of values.
+description=Both upper and lower bounds may be defined.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.max-password-length.synopsis=Specifies the maximum number of characters that can be included in a proposed password.
+property.max-password-length.description=A value of zero indicates that there will be no upper bound enforced. If both minimum and maximum lengths are defined, then the minimum length must be less than or equal to the maximum length.
+property.min-password-length.synopsis=Specifies the minimum number of characters that must be included in a proposed password.
+property.min-password-length.description=A value of zero indicates that there will be no lower bound enforced. If both minimum and maximum lengths are defined, then the minimum length must be less than or equal to the maximum length.
diff --git a/opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_es.properties b/opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_es.properties
new file mode 100644
index 0000000..b5a8e68
--- /dev/null
+++ b/opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_es.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Length Based Password Validator
+user-friendly-plural-name=Length Based Password Validators
+synopsis=The Length Based Password Validator is used to determine whether a proposed password is acceptable based on whether the number of characters it contains falls within an acceptable range of values.
+description=Both upper and lower bounds may be defined.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.max-password-length.synopsis=Specifies the maximum number of characters that can be included in a proposed password.
+property.max-password-length.description=A value of zero indicates that there will be no upper bound enforced. If both minimum and maximum lengths are defined, then the minimum length must be less than or equal to the maximum length.
+property.min-password-length.synopsis=Specifies the minimum number of characters that must be included in a proposed password.
+property.min-password-length.description=A value of zero indicates that there will be no lower bound enforced. If both minimum and maximum lengths are defined, then the minimum length must be less than or equal to the maximum length.
diff --git a/opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_fr.properties b/opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_fr.properties
new file mode 100644
index 0000000..b5a8e68
--- /dev/null
+++ b/opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_fr.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Length Based Password Validator
+user-friendly-plural-name=Length Based Password Validators
+synopsis=The Length Based Password Validator is used to determine whether a proposed password is acceptable based on whether the number of characters it contains falls within an acceptable range of values.
+description=Both upper and lower bounds may be defined.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.max-password-length.synopsis=Specifies the maximum number of characters that can be included in a proposed password.
+property.max-password-length.description=A value of zero indicates that there will be no upper bound enforced. If both minimum and maximum lengths are defined, then the minimum length must be less than or equal to the maximum length.
+property.min-password-length.synopsis=Specifies the minimum number of characters that must be included in a proposed password.
+property.min-password-length.description=A value of zero indicates that there will be no lower bound enforced. If both minimum and maximum lengths are defined, then the minimum length must be less than or equal to the maximum length.
diff --git a/opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_ja.properties b/opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_ja.properties
new file mode 100644
index 0000000..b5a8e68
--- /dev/null
+++ b/opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_ja.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Length Based Password Validator
+user-friendly-plural-name=Length Based Password Validators
+synopsis=The Length Based Password Validator is used to determine whether a proposed password is acceptable based on whether the number of characters it contains falls within an acceptable range of values.
+description=Both upper and lower bounds may be defined.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.max-password-length.synopsis=Specifies the maximum number of characters that can be included in a proposed password.
+property.max-password-length.description=A value of zero indicates that there will be no upper bound enforced. If both minimum and maximum lengths are defined, then the minimum length must be less than or equal to the maximum length.
+property.min-password-length.synopsis=Specifies the minimum number of characters that must be included in a proposed password.
+property.min-password-length.description=A value of zero indicates that there will be no lower bound enforced. If both minimum and maximum lengths are defined, then the minimum length must be less than or equal to the maximum length.
diff --git a/opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_ko.properties b/opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_ko.properties
new file mode 100644
index 0000000..b5a8e68
--- /dev/null
+++ b/opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_ko.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Length Based Password Validator
+user-friendly-plural-name=Length Based Password Validators
+synopsis=The Length Based Password Validator is used to determine whether a proposed password is acceptable based on whether the number of characters it contains falls within an acceptable range of values.
+description=Both upper and lower bounds may be defined.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.max-password-length.synopsis=Specifies the maximum number of characters that can be included in a proposed password.
+property.max-password-length.description=A value of zero indicates that there will be no upper bound enforced. If both minimum and maximum lengths are defined, then the minimum length must be less than or equal to the maximum length.
+property.min-password-length.synopsis=Specifies the minimum number of characters that must be included in a proposed password.
+property.min-password-length.description=A value of zero indicates that there will be no lower bound enforced. If both minimum and maximum lengths are defined, then the minimum length must be less than or equal to the maximum length.
diff --git a/opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_zh_CN.properties b/opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..b5a8e68
--- /dev/null
+++ b/opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_zh_CN.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Length Based Password Validator
+user-friendly-plural-name=Length Based Password Validators
+synopsis=The Length Based Password Validator is used to determine whether a proposed password is acceptable based on whether the number of characters it contains falls within an acceptable range of values.
+description=Both upper and lower bounds may be defined.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.max-password-length.synopsis=Specifies the maximum number of characters that can be included in a proposed password.
+property.max-password-length.description=A value of zero indicates that there will be no upper bound enforced. If both minimum and maximum lengths are defined, then the minimum length must be less than or equal to the maximum length.
+property.min-password-length.synopsis=Specifies the minimum number of characters that must be included in a proposed password.
+property.min-password-length.description=A value of zero indicates that there will be no lower bound enforced. If both minimum and maximum lengths are defined, then the minimum length must be less than or equal to the maximum length.
diff --git a/opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_zh_TW.properties b/opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..b5a8e68
--- /dev/null
+++ b/opends/src/admin/messages/LengthBasedPasswordValidatorCfgDefn_zh_TW.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Length Based Password Validator
+user-friendly-plural-name=Length Based Password Validators
+synopsis=The Length Based Password Validator is used to determine whether a proposed password is acceptable based on whether the number of characters it contains falls within an acceptable range of values.
+description=Both upper and lower bounds may be defined.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.max-password-length.synopsis=Specifies the maximum number of characters that can be included in a proposed password.
+property.max-password-length.description=A value of zero indicates that there will be no upper bound enforced. If both minimum and maximum lengths are defined, then the minimum length must be less than or equal to the maximum length.
+property.min-password-length.synopsis=Specifies the minimum number of characters that must be included in a proposed password.
+property.min-password-length.description=A value of zero indicates that there will be no lower bound enforced. If both minimum and maximum lengths are defined, then the minimum length must be less than or equal to the maximum length.
diff --git a/opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn.properties b/opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn.properties
new file mode 100644
index 0000000..4f138fc
--- /dev/null
+++ b/opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Local Backend Workflow Element
+user-friendly-plural-name=Local Backend Workflow Elements
+synopsis=The Local Backend Workflow Element provides access to a backend.
+property.backend.synopsis=Identifies the backend accessed by the workflow element.
+property.backend.syntax.aggregation.constraint-synopsis=The referenced backend must be enabled.
+property.enabled.synopsis=Indicates whether the Local Backend Workflow Element is enabled for use in the server.
+property.enabled.description=If a Local Backend Workflow Element is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Local Backend Workflow Element implementation.
+property.workflow-element-id.synopsis=Provides a name that identifies the associated Local Backend Workflow Element .
+property.workflow-element-id.description=The name must be unique among all Local Backend Workflow Elements in the server.
diff --git a/opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_de.properties b/opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_de.properties
new file mode 100644
index 0000000..4f138fc
--- /dev/null
+++ b/opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_de.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Local Backend Workflow Element
+user-friendly-plural-name=Local Backend Workflow Elements
+synopsis=The Local Backend Workflow Element provides access to a backend.
+property.backend.synopsis=Identifies the backend accessed by the workflow element.
+property.backend.syntax.aggregation.constraint-synopsis=The referenced backend must be enabled.
+property.enabled.synopsis=Indicates whether the Local Backend Workflow Element is enabled for use in the server.
+property.enabled.description=If a Local Backend Workflow Element is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Local Backend Workflow Element implementation.
+property.workflow-element-id.synopsis=Provides a name that identifies the associated Local Backend Workflow Element .
+property.workflow-element-id.description=The name must be unique among all Local Backend Workflow Elements in the server.
diff --git a/opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_es.properties b/opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_es.properties
new file mode 100644
index 0000000..4f138fc
--- /dev/null
+++ b/opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_es.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Local Backend Workflow Element
+user-friendly-plural-name=Local Backend Workflow Elements
+synopsis=The Local Backend Workflow Element provides access to a backend.
+property.backend.synopsis=Identifies the backend accessed by the workflow element.
+property.backend.syntax.aggregation.constraint-synopsis=The referenced backend must be enabled.
+property.enabled.synopsis=Indicates whether the Local Backend Workflow Element is enabled for use in the server.
+property.enabled.description=If a Local Backend Workflow Element is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Local Backend Workflow Element implementation.
+property.workflow-element-id.synopsis=Provides a name that identifies the associated Local Backend Workflow Element .
+property.workflow-element-id.description=The name must be unique among all Local Backend Workflow Elements in the server.
diff --git a/opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_fr.properties b/opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_fr.properties
new file mode 100644
index 0000000..4f138fc
--- /dev/null
+++ b/opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_fr.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Local Backend Workflow Element
+user-friendly-plural-name=Local Backend Workflow Elements
+synopsis=The Local Backend Workflow Element provides access to a backend.
+property.backend.synopsis=Identifies the backend accessed by the workflow element.
+property.backend.syntax.aggregation.constraint-synopsis=The referenced backend must be enabled.
+property.enabled.synopsis=Indicates whether the Local Backend Workflow Element is enabled for use in the server.
+property.enabled.description=If a Local Backend Workflow Element is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Local Backend Workflow Element implementation.
+property.workflow-element-id.synopsis=Provides a name that identifies the associated Local Backend Workflow Element .
+property.workflow-element-id.description=The name must be unique among all Local Backend Workflow Elements in the server.
diff --git a/opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_ja.properties b/opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_ja.properties
new file mode 100644
index 0000000..4f138fc
--- /dev/null
+++ b/opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_ja.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Local Backend Workflow Element
+user-friendly-plural-name=Local Backend Workflow Elements
+synopsis=The Local Backend Workflow Element provides access to a backend.
+property.backend.synopsis=Identifies the backend accessed by the workflow element.
+property.backend.syntax.aggregation.constraint-synopsis=The referenced backend must be enabled.
+property.enabled.synopsis=Indicates whether the Local Backend Workflow Element is enabled for use in the server.
+property.enabled.description=If a Local Backend Workflow Element is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Local Backend Workflow Element implementation.
+property.workflow-element-id.synopsis=Provides a name that identifies the associated Local Backend Workflow Element .
+property.workflow-element-id.description=The name must be unique among all Local Backend Workflow Elements in the server.
diff --git a/opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_ko.properties b/opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_ko.properties
new file mode 100644
index 0000000..4f138fc
--- /dev/null
+++ b/opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_ko.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Local Backend Workflow Element
+user-friendly-plural-name=Local Backend Workflow Elements
+synopsis=The Local Backend Workflow Element provides access to a backend.
+property.backend.synopsis=Identifies the backend accessed by the workflow element.
+property.backend.syntax.aggregation.constraint-synopsis=The referenced backend must be enabled.
+property.enabled.synopsis=Indicates whether the Local Backend Workflow Element is enabled for use in the server.
+property.enabled.description=If a Local Backend Workflow Element is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Local Backend Workflow Element implementation.
+property.workflow-element-id.synopsis=Provides a name that identifies the associated Local Backend Workflow Element .
+property.workflow-element-id.description=The name must be unique among all Local Backend Workflow Elements in the server.
diff --git a/opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_zh_CN.properties b/opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..4f138fc
--- /dev/null
+++ b/opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_zh_CN.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Local Backend Workflow Element
+user-friendly-plural-name=Local Backend Workflow Elements
+synopsis=The Local Backend Workflow Element provides access to a backend.
+property.backend.synopsis=Identifies the backend accessed by the workflow element.
+property.backend.syntax.aggregation.constraint-synopsis=The referenced backend must be enabled.
+property.enabled.synopsis=Indicates whether the Local Backend Workflow Element is enabled for use in the server.
+property.enabled.description=If a Local Backend Workflow Element is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Local Backend Workflow Element implementation.
+property.workflow-element-id.synopsis=Provides a name that identifies the associated Local Backend Workflow Element .
+property.workflow-element-id.description=The name must be unique among all Local Backend Workflow Elements in the server.
diff --git a/opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_zh_TW.properties b/opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..4f138fc
--- /dev/null
+++ b/opends/src/admin/messages/LocalBackendWorkflowElementCfgDefn_zh_TW.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Local Backend Workflow Element
+user-friendly-plural-name=Local Backend Workflow Elements
+synopsis=The Local Backend Workflow Element provides access to a backend.
+property.backend.synopsis=Identifies the backend accessed by the workflow element.
+property.backend.syntax.aggregation.constraint-synopsis=The referenced backend must be enabled.
+property.enabled.synopsis=Indicates whether the Local Backend Workflow Element is enabled for use in the server.
+property.enabled.description=If a Local Backend Workflow Element is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Local Backend Workflow Element implementation.
+property.workflow-element-id.synopsis=Provides a name that identifies the associated Local Backend Workflow Element .
+property.workflow-element-id.description=The name must be unique among all Local Backend Workflow Elements in the server.
diff --git a/opends/src/admin/messages/LocalDBBackendCfgDefn.properties b/opends/src/admin/messages/LocalDBBackendCfgDefn.properties
new file mode 100644
index 0000000..2075bdf
--- /dev/null
+++ b/opends/src/admin/messages/LocalDBBackendCfgDefn.properties
@@ -0,0 +1,76 @@
+user-friendly-name=Local DB Backend
+user-friendly-plural-name=Local DB Backends
+synopsis=The Local DB Backend uses the Berkeley DB Java Edition to store user-provided data in a local repository.
+description=It is the traditional "directory server" backend and is similar to the backends provided by the Sun Java System Directory Server. The Local DB Backend stores the entries in an encoded form and also provides indexes that can be used to quickly locate target entries based on different kinds of criteria.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.compact-encoding.synopsis=Indicates whether the backend should use a compact form when encoding entries by compressing the attribute descriptions and object class sets.
+property.compact-encoding.description=Note that this property applies only to the entries themselves and does not impact the index data.
+property.compact-encoding.requires-admin-action.synopsis=Changes to this setting take effect only for writes that occur after the change is made. It is not retroactively applied to existing data.
+property.db-cache-percent.synopsis=Specifies the percentage of JVM memory to allocate to the database cache.
+property.db-cache-percent.description=Specifies the percentage of memory available to the JVM that should be used for caching database contents. Note that this is only used if the value of the db-cache-size property is set to "0 MB". Otherwise, the value of that property is used instead to control the cache size configuration.
+property.db-cache-size.synopsis=The amount of JVM memory to allocate to the database cache.
+property.db-cache-size.description=Specifies the amount of memory that should be used for caching database contents. A value of "0 MB" indicates that the db-cache-percent property should be used instead to specify the cache size.
+property.db-checkpointer-bytes-interval.synopsis=Specifies the maximum number of bytes that may be written to the database before it is forced to perform a checkpoint.
+property.db-checkpointer-bytes-interval.description=This can be used to bound the recovery time that may be required if the database environment is opened without having been properly closed. If this property is set to a non-zero value, the checkpointer wakeup interval is not used. To use time-based checkpointing, set this property to zero.
+property.db-checkpointer-wakeup-interval.synopsis=Specifies the maximum length of time that may pass between checkpoints.
+property.db-checkpointer-wakeup-interval.description=Note that this is only used if the value of the checkpointer bytes interval is zero.
+property.db-cleaner-min-utilization.synopsis=Specifies the minimum percentage of "live" data that the database cleaner attempts to keep in database log files.
+property.db-cleaner-min-utilization.description=If the amount of live data in any database log file drops below this percentage, then the cleaner moves the remaining live data in that file to the end of the database and deletes the original file in order to keep the database relatively compact.
+property.db-directory.synopsis=Specifies the path to the filesystem directory that is used to hold the Berkeley DB Java Edition database files containing the data for this backend.
+property.db-directory.description=The path may be either an absolute path or a path relative to the directory containing the base of the OpenDS Directory Server installation. The path may be any valid directory path in which the server has appropriate permissions to read and write files and has sufficient space to hold the database contents.
+property.db-directory-permissions.synopsis=Specifies the permissions that should be applied to the directory containing the server database files.
+property.db-directory-permissions.description=They should be expressed as three-digit octal values, which is the traditional representation for UNIX file permissions. The three digits represent the permissions that are available for the directory's owner, group members, and other users (in that order), and each digit is the octal representation of the read, write, and execute bits. Note that this only impacts permissions on the database directory and not on the files written into that directory. On UNIX systems, the user's umask controls permissions given to the database files.
+property.db-directory-permissions.syntax.string.pattern.synopsis=Any octal value between 700 and 777 (the owner must always have read, write, and execute permissions on the directory).
+property.db-evictor-lru-only.synopsis=Indicates whether the database should evict existing data from the cache based on an LRU policy (where the least recently used information will be evicted first).
+property.db-evictor-lru-only.description=If set to "false", then the eviction keeps internal nodes of the underlying Btree in the cache over leaf notes, even if the leaf nodes have been accessed more recently. This may be a better configuration for databases in which only a very small portion of the data is cached.
+property.db-evictor-nodes-per-scan.synopsis=Specifies the number of Btree nodes that should be evicted from the cache in a single pass if it is determined that it is necessary to free existing data in order to make room for new information.
+property.db-evictor-nodes-per-scan.description=Changes to this property do not take effect until the backend is restarted. It is recommended that you also change this property when you set db-evictor-lru-only to false. This setting controls the number of Btree nodes that are considered, or sampled, each time a node is evicted. A setting of 100 often produces good results, but this may vary from application to application. The larger the nodes per scan, the more accurate the algorithm. However, setting it too high is detrimental; the need to consider larger numbers of nodes for each eviction may delay the completion of a given database operation, which will impact the response time of the application thread.
+property.db-log-file-max.synopsis=Specifies the maximum size for a database log file.
+property.db-logging-file-handler-on.synopsis=Indicates whether the database should maintain a je.info file in the same directory as the database log directory.
+property.db-logging-file-handler-on.description=This file contains information about the internal processing performed by the underlying database.
+property.db-logging-level.synopsis=Specifies the log level that should be used by the database when it is writing information into the je.info file.
+property.db-logging-level.description=The database trace logging level is (in increasing order of verbosity) chosen from: OFF, SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST, ALL.
+property.db-num-cleaner-threads.synopsis=Specifies the number of threads that the backend should maintain to keep the database log files at or near the desired utilization.
+property.db-num-cleaner-threads.description=In environments with high write throughput, multiple cleaner threads may be required to maintain the desired utilization.
+property.db-num-lock-tables.synopsis=Specifies the number of lock tables that are used by the underlying database.
+property.db-num-lock-tables.description=This can be particularly important to help improve scalability by avoiding contention on systems with large numbers of CPUs. The value of this configuration property should be set to a prime number that is less than or equal to the number of worker threads configured for use in the server.
+property.db-run-cleaner.synopsis=Indicates whether the database cleaner threads should be enabled.
+property.db-run-cleaner.description=The cleaner threads are used to periodically compact the database by identifying database files with a low (that is, less than the amount specified by the db-cleaner-min-utilization property) percentage of live data, moving the remaining live data to the end of the log and deleting that file.
+property.db-txn-no-sync.synopsis=Indicates whether database writes should be primarily written to an internal buffer but not immediately written to disk.
+property.db-txn-no-sync.description=Setting the value of this configuration attribute to "true" may improve write performance but could cause the most recent changes to be lost if the OpenDS Directory Server or the underlying JVM exits abnormally, or if an OS or hardware failure occurs (a behavior similar to running with transaction durability disabled in the Sun Java System Directory Server).
+property.db-txn-write-no-sync.synopsis=Indicates whether the database should synchronously flush data as it is written to disk.
+property.db-txn-write-no-sync.description=If this value is set to "false", then all data written to disk is synchronously flushed to persistent storage and thereby providing full durability. If it is set to "true", then data may be cached for a period of time by the underlying operating system before actually being written to disk. This may improve performance, but could cause the most recent changes to be lost in the event of an underlying OS or hardware failure (but not in the case that the OpenDS Directory Server or the JVM exits abnormally).
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.entries-compressed.synopsis=Indicates whether the backend should attempt to compress entries before storing them in the database.
+property.entries-compressed.description=Note that this property applies only to the entries themselves and does not impact the index data. Further, the effectiveness of the compression is based on the type of data contained in the entry.
+property.entries-compressed.requires-admin-action.synopsis=Changes to this setting take effect only for writes that occur after the change is made. It is not retroactively applied to existing data.
+property.import-queue-size.synopsis=Specifies the size (in number of entries) of the queue that is used to hold the entries read during an LDIF import.
+property.import-queue-size.requires-admin-action.synopsis=Changes do not take effect for any import that may already be in progress.
+property.import-thread-count.synopsis=Specifies the number of threads that is used for concurrent processing during an LDIF import.
+property.import-thread-count.description=This should generally be a small multiple (for example, 2x) of the number of CPUs in the system for a traditional system, or equal to the number of CPU strands for a CMT system.
+property.import-thread-count.requires-admin-action.synopsis=Changes do not take effect for any import that may already be in progress.
+property.index-entry-limit.synopsis=Specifies the maximum number of entries that is allowed to match a given index key before that particular index key is no longer maintained.
+property.index-entry-limit.description=This property is analogous to the ALL IDs threshold in the Sun Java System Directory Server. Note that this is the default limit for the backend, and it may be overridden on a per-attribute basis.A value of 0 means there is no limit.
+property.index-entry-limit.requires-admin-action.synopsis=If any index keys have already reached this limit, indexes need to be rebuilt before they are allowed to use the new limit.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.je-property.synopsis=Specifies the database and environment properties for the Berkeley DB Java Edition database serving the data for this backend.
+property.je-property.description=Any Berkeley DB Java Edition property can be specified using the following form: property-name=property-value. Refer to OpenDS documentation for further information on related properties, their implications, and range values. The definitive identification of all the property parameters is available in the example.properties file of Berkeley DB Java Edition distribution.
+property.preload-time-limit.synopsis=Specifies the length of time that the backend is allowed to spend "pre-loading" data when it is initialized.
+property.preload-time-limit.description=The pre-load process is used to pre-populate the database cache, so that it can be more quickly available when the server is processing requests. A duration of zero means there is no pre-load.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
+relation.local-db-index.user-friendly-name=Local DB Index
+relation.local-db-index.user-friendly-plural-name=Local DB Indexes
+relation.local-db-index.synopsis=Local DB Indexes are used to store information that makes it possible to locate entries very quickly when processing search operations.
+relation.local-db-index.description=Indexing is performed on a per-attribute level and different types of indexing may be performed for different kinds of attributes, based on how they are expected to be accessed during search operations.
+relation.local-db-vlv-index.user-friendly-name=Local DB VLV Index
+relation.local-db-vlv-index.user-friendly-plural-name=Local DB VLV Indexes
+relation.local-db-vlv-index.synopsis=Local DB VLV Indexes are used to store information about a specific search request that makes it possible to efficiently process them using the VLV control.
+relation.local-db-vlv-index.description=A VLV index effectively notifies the server that a virtual list view, with specific query and sort parameters, will be performed. This index also allows the server to collect and maintain the information required to make using the virtual list view faster.
diff --git a/opends/src/admin/messages/LocalDBBackendCfgDefn_de.properties b/opends/src/admin/messages/LocalDBBackendCfgDefn_de.properties
new file mode 100644
index 0000000..2075bdf
--- /dev/null
+++ b/opends/src/admin/messages/LocalDBBackendCfgDefn_de.properties
@@ -0,0 +1,76 @@
+user-friendly-name=Local DB Backend
+user-friendly-plural-name=Local DB Backends
+synopsis=The Local DB Backend uses the Berkeley DB Java Edition to store user-provided data in a local repository.
+description=It is the traditional "directory server" backend and is similar to the backends provided by the Sun Java System Directory Server. The Local DB Backend stores the entries in an encoded form and also provides indexes that can be used to quickly locate target entries based on different kinds of criteria.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.compact-encoding.synopsis=Indicates whether the backend should use a compact form when encoding entries by compressing the attribute descriptions and object class sets.
+property.compact-encoding.description=Note that this property applies only to the entries themselves and does not impact the index data.
+property.compact-encoding.requires-admin-action.synopsis=Changes to this setting take effect only for writes that occur after the change is made. It is not retroactively applied to existing data.
+property.db-cache-percent.synopsis=Specifies the percentage of JVM memory to allocate to the database cache.
+property.db-cache-percent.description=Specifies the percentage of memory available to the JVM that should be used for caching database contents. Note that this is only used if the value of the db-cache-size property is set to "0 MB". Otherwise, the value of that property is used instead to control the cache size configuration.
+property.db-cache-size.synopsis=The amount of JVM memory to allocate to the database cache.
+property.db-cache-size.description=Specifies the amount of memory that should be used for caching database contents. A value of "0 MB" indicates that the db-cache-percent property should be used instead to specify the cache size.
+property.db-checkpointer-bytes-interval.synopsis=Specifies the maximum number of bytes that may be written to the database before it is forced to perform a checkpoint.
+property.db-checkpointer-bytes-interval.description=This can be used to bound the recovery time that may be required if the database environment is opened without having been properly closed. If this property is set to a non-zero value, the checkpointer wakeup interval is not used. To use time-based checkpointing, set this property to zero.
+property.db-checkpointer-wakeup-interval.synopsis=Specifies the maximum length of time that may pass between checkpoints.
+property.db-checkpointer-wakeup-interval.description=Note that this is only used if the value of the checkpointer bytes interval is zero.
+property.db-cleaner-min-utilization.synopsis=Specifies the minimum percentage of "live" data that the database cleaner attempts to keep in database log files.
+property.db-cleaner-min-utilization.description=If the amount of live data in any database log file drops below this percentage, then the cleaner moves the remaining live data in that file to the end of the database and deletes the original file in order to keep the database relatively compact.
+property.db-directory.synopsis=Specifies the path to the filesystem directory that is used to hold the Berkeley DB Java Edition database files containing the data for this backend.
+property.db-directory.description=The path may be either an absolute path or a path relative to the directory containing the base of the OpenDS Directory Server installation. The path may be any valid directory path in which the server has appropriate permissions to read and write files and has sufficient space to hold the database contents.
+property.db-directory-permissions.synopsis=Specifies the permissions that should be applied to the directory containing the server database files.
+property.db-directory-permissions.description=They should be expressed as three-digit octal values, which is the traditional representation for UNIX file permissions. The three digits represent the permissions that are available for the directory's owner, group members, and other users (in that order), and each digit is the octal representation of the read, write, and execute bits. Note that this only impacts permissions on the database directory and not on the files written into that directory. On UNIX systems, the user's umask controls permissions given to the database files.
+property.db-directory-permissions.syntax.string.pattern.synopsis=Any octal value between 700 and 777 (the owner must always have read, write, and execute permissions on the directory).
+property.db-evictor-lru-only.synopsis=Indicates whether the database should evict existing data from the cache based on an LRU policy (where the least recently used information will be evicted first).
+property.db-evictor-lru-only.description=If set to "false", then the eviction keeps internal nodes of the underlying Btree in the cache over leaf notes, even if the leaf nodes have been accessed more recently. This may be a better configuration for databases in which only a very small portion of the data is cached.
+property.db-evictor-nodes-per-scan.synopsis=Specifies the number of Btree nodes that should be evicted from the cache in a single pass if it is determined that it is necessary to free existing data in order to make room for new information.
+property.db-evictor-nodes-per-scan.description=Changes to this property do not take effect until the backend is restarted. It is recommended that you also change this property when you set db-evictor-lru-only to false. This setting controls the number of Btree nodes that are considered, or sampled, each time a node is evicted. A setting of 100 often produces good results, but this may vary from application to application. The larger the nodes per scan, the more accurate the algorithm. However, setting it too high is detrimental; the need to consider larger numbers of nodes for each eviction may delay the completion of a given database operation, which will impact the response time of the application thread.
+property.db-log-file-max.synopsis=Specifies the maximum size for a database log file.
+property.db-logging-file-handler-on.synopsis=Indicates whether the database should maintain a je.info file in the same directory as the database log directory.
+property.db-logging-file-handler-on.description=This file contains information about the internal processing performed by the underlying database.
+property.db-logging-level.synopsis=Specifies the log level that should be used by the database when it is writing information into the je.info file.
+property.db-logging-level.description=The database trace logging level is (in increasing order of verbosity) chosen from: OFF, SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST, ALL.
+property.db-num-cleaner-threads.synopsis=Specifies the number of threads that the backend should maintain to keep the database log files at or near the desired utilization.
+property.db-num-cleaner-threads.description=In environments with high write throughput, multiple cleaner threads may be required to maintain the desired utilization.
+property.db-num-lock-tables.synopsis=Specifies the number of lock tables that are used by the underlying database.
+property.db-num-lock-tables.description=This can be particularly important to help improve scalability by avoiding contention on systems with large numbers of CPUs. The value of this configuration property should be set to a prime number that is less than or equal to the number of worker threads configured for use in the server.
+property.db-run-cleaner.synopsis=Indicates whether the database cleaner threads should be enabled.
+property.db-run-cleaner.description=The cleaner threads are used to periodically compact the database by identifying database files with a low (that is, less than the amount specified by the db-cleaner-min-utilization property) percentage of live data, moving the remaining live data to the end of the log and deleting that file.
+property.db-txn-no-sync.synopsis=Indicates whether database writes should be primarily written to an internal buffer but not immediately written to disk.
+property.db-txn-no-sync.description=Setting the value of this configuration attribute to "true" may improve write performance but could cause the most recent changes to be lost if the OpenDS Directory Server or the underlying JVM exits abnormally, or if an OS or hardware failure occurs (a behavior similar to running with transaction durability disabled in the Sun Java System Directory Server).
+property.db-txn-write-no-sync.synopsis=Indicates whether the database should synchronously flush data as it is written to disk.
+property.db-txn-write-no-sync.description=If this value is set to "false", then all data written to disk is synchronously flushed to persistent storage and thereby providing full durability. If it is set to "true", then data may be cached for a period of time by the underlying operating system before actually being written to disk. This may improve performance, but could cause the most recent changes to be lost in the event of an underlying OS or hardware failure (but not in the case that the OpenDS Directory Server or the JVM exits abnormally).
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.entries-compressed.synopsis=Indicates whether the backend should attempt to compress entries before storing them in the database.
+property.entries-compressed.description=Note that this property applies only to the entries themselves and does not impact the index data. Further, the effectiveness of the compression is based on the type of data contained in the entry.
+property.entries-compressed.requires-admin-action.synopsis=Changes to this setting take effect only for writes that occur after the change is made. It is not retroactively applied to existing data.
+property.import-queue-size.synopsis=Specifies the size (in number of entries) of the queue that is used to hold the entries read during an LDIF import.
+property.import-queue-size.requires-admin-action.synopsis=Changes do not take effect for any import that may already be in progress.
+property.import-thread-count.synopsis=Specifies the number of threads that is used for concurrent processing during an LDIF import.
+property.import-thread-count.description=This should generally be a small multiple (for example, 2x) of the number of CPUs in the system for a traditional system, or equal to the number of CPU strands for a CMT system.
+property.import-thread-count.requires-admin-action.synopsis=Changes do not take effect for any import that may already be in progress.
+property.index-entry-limit.synopsis=Specifies the maximum number of entries that is allowed to match a given index key before that particular index key is no longer maintained.
+property.index-entry-limit.description=This property is analogous to the ALL IDs threshold in the Sun Java System Directory Server. Note that this is the default limit for the backend, and it may be overridden on a per-attribute basis.A value of 0 means there is no limit.
+property.index-entry-limit.requires-admin-action.synopsis=If any index keys have already reached this limit, indexes need to be rebuilt before they are allowed to use the new limit.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.je-property.synopsis=Specifies the database and environment properties for the Berkeley DB Java Edition database serving the data for this backend.
+property.je-property.description=Any Berkeley DB Java Edition property can be specified using the following form: property-name=property-value. Refer to OpenDS documentation for further information on related properties, their implications, and range values. The definitive identification of all the property parameters is available in the example.properties file of Berkeley DB Java Edition distribution.
+property.preload-time-limit.synopsis=Specifies the length of time that the backend is allowed to spend "pre-loading" data when it is initialized.
+property.preload-time-limit.description=The pre-load process is used to pre-populate the database cache, so that it can be more quickly available when the server is processing requests. A duration of zero means there is no pre-load.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
+relation.local-db-index.user-friendly-name=Local DB Index
+relation.local-db-index.user-friendly-plural-name=Local DB Indexes
+relation.local-db-index.synopsis=Local DB Indexes are used to store information that makes it possible to locate entries very quickly when processing search operations.
+relation.local-db-index.description=Indexing is performed on a per-attribute level and different types of indexing may be performed for different kinds of attributes, based on how they are expected to be accessed during search operations.
+relation.local-db-vlv-index.user-friendly-name=Local DB VLV Index
+relation.local-db-vlv-index.user-friendly-plural-name=Local DB VLV Indexes
+relation.local-db-vlv-index.synopsis=Local DB VLV Indexes are used to store information about a specific search request that makes it possible to efficiently process them using the VLV control.
+relation.local-db-vlv-index.description=A VLV index effectively notifies the server that a virtual list view, with specific query and sort parameters, will be performed. This index also allows the server to collect and maintain the information required to make using the virtual list view faster.
diff --git a/opends/src/admin/messages/LocalDBBackendCfgDefn_es.properties b/opends/src/admin/messages/LocalDBBackendCfgDefn_es.properties
new file mode 100644
index 0000000..2075bdf
--- /dev/null
+++ b/opends/src/admin/messages/LocalDBBackendCfgDefn_es.properties
@@ -0,0 +1,76 @@
+user-friendly-name=Local DB Backend
+user-friendly-plural-name=Local DB Backends
+synopsis=The Local DB Backend uses the Berkeley DB Java Edition to store user-provided data in a local repository.
+description=It is the traditional "directory server" backend and is similar to the backends provided by the Sun Java System Directory Server. The Local DB Backend stores the entries in an encoded form and also provides indexes that can be used to quickly locate target entries based on different kinds of criteria.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.compact-encoding.synopsis=Indicates whether the backend should use a compact form when encoding entries by compressing the attribute descriptions and object class sets.
+property.compact-encoding.description=Note that this property applies only to the entries themselves and does not impact the index data.
+property.compact-encoding.requires-admin-action.synopsis=Changes to this setting take effect only for writes that occur after the change is made. It is not retroactively applied to existing data.
+property.db-cache-percent.synopsis=Specifies the percentage of JVM memory to allocate to the database cache.
+property.db-cache-percent.description=Specifies the percentage of memory available to the JVM that should be used for caching database contents. Note that this is only used if the value of the db-cache-size property is set to "0 MB". Otherwise, the value of that property is used instead to control the cache size configuration.
+property.db-cache-size.synopsis=The amount of JVM memory to allocate to the database cache.
+property.db-cache-size.description=Specifies the amount of memory that should be used for caching database contents. A value of "0 MB" indicates that the db-cache-percent property should be used instead to specify the cache size.
+property.db-checkpointer-bytes-interval.synopsis=Specifies the maximum number of bytes that may be written to the database before it is forced to perform a checkpoint.
+property.db-checkpointer-bytes-interval.description=This can be used to bound the recovery time that may be required if the database environment is opened without having been properly closed. If this property is set to a non-zero value, the checkpointer wakeup interval is not used. To use time-based checkpointing, set this property to zero.
+property.db-checkpointer-wakeup-interval.synopsis=Specifies the maximum length of time that may pass between checkpoints.
+property.db-checkpointer-wakeup-interval.description=Note that this is only used if the value of the checkpointer bytes interval is zero.
+property.db-cleaner-min-utilization.synopsis=Specifies the minimum percentage of "live" data that the database cleaner attempts to keep in database log files.
+property.db-cleaner-min-utilization.description=If the amount of live data in any database log file drops below this percentage, then the cleaner moves the remaining live data in that file to the end of the database and deletes the original file in order to keep the database relatively compact.
+property.db-directory.synopsis=Specifies the path to the filesystem directory that is used to hold the Berkeley DB Java Edition database files containing the data for this backend.
+property.db-directory.description=The path may be either an absolute path or a path relative to the directory containing the base of the OpenDS Directory Server installation. The path may be any valid directory path in which the server has appropriate permissions to read and write files and has sufficient space to hold the database contents.
+property.db-directory-permissions.synopsis=Specifies the permissions that should be applied to the directory containing the server database files.
+property.db-directory-permissions.description=They should be expressed as three-digit octal values, which is the traditional representation for UNIX file permissions. The three digits represent the permissions that are available for the directory's owner, group members, and other users (in that order), and each digit is the octal representation of the read, write, and execute bits. Note that this only impacts permissions on the database directory and not on the files written into that directory. On UNIX systems, the user's umask controls permissions given to the database files.
+property.db-directory-permissions.syntax.string.pattern.synopsis=Any octal value between 700 and 777 (the owner must always have read, write, and execute permissions on the directory).
+property.db-evictor-lru-only.synopsis=Indicates whether the database should evict existing data from the cache based on an LRU policy (where the least recently used information will be evicted first).
+property.db-evictor-lru-only.description=If set to "false", then the eviction keeps internal nodes of the underlying Btree in the cache over leaf notes, even if the leaf nodes have been accessed more recently. This may be a better configuration for databases in which only a very small portion of the data is cached.
+property.db-evictor-nodes-per-scan.synopsis=Specifies the number of Btree nodes that should be evicted from the cache in a single pass if it is determined that it is necessary to free existing data in order to make room for new information.
+property.db-evictor-nodes-per-scan.description=Changes to this property do not take effect until the backend is restarted. It is recommended that you also change this property when you set db-evictor-lru-only to false. This setting controls the number of Btree nodes that are considered, or sampled, each time a node is evicted. A setting of 100 often produces good results, but this may vary from application to application. The larger the nodes per scan, the more accurate the algorithm. However, setting it too high is detrimental; the need to consider larger numbers of nodes for each eviction may delay the completion of a given database operation, which will impact the response time of the application thread.
+property.db-log-file-max.synopsis=Specifies the maximum size for a database log file.
+property.db-logging-file-handler-on.synopsis=Indicates whether the database should maintain a je.info file in the same directory as the database log directory.
+property.db-logging-file-handler-on.description=This file contains information about the internal processing performed by the underlying database.
+property.db-logging-level.synopsis=Specifies the log level that should be used by the database when it is writing information into the je.info file.
+property.db-logging-level.description=The database trace logging level is (in increasing order of verbosity) chosen from: OFF, SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST, ALL.
+property.db-num-cleaner-threads.synopsis=Specifies the number of threads that the backend should maintain to keep the database log files at or near the desired utilization.
+property.db-num-cleaner-threads.description=In environments with high write throughput, multiple cleaner threads may be required to maintain the desired utilization.
+property.db-num-lock-tables.synopsis=Specifies the number of lock tables that are used by the underlying database.
+property.db-num-lock-tables.description=This can be particularly important to help improve scalability by avoiding contention on systems with large numbers of CPUs. The value of this configuration property should be set to a prime number that is less than or equal to the number of worker threads configured for use in the server.
+property.db-run-cleaner.synopsis=Indicates whether the database cleaner threads should be enabled.
+property.db-run-cleaner.description=The cleaner threads are used to periodically compact the database by identifying database files with a low (that is, less than the amount specified by the db-cleaner-min-utilization property) percentage of live data, moving the remaining live data to the end of the log and deleting that file.
+property.db-txn-no-sync.synopsis=Indicates whether database writes should be primarily written to an internal buffer but not immediately written to disk.
+property.db-txn-no-sync.description=Setting the value of this configuration attribute to "true" may improve write performance but could cause the most recent changes to be lost if the OpenDS Directory Server or the underlying JVM exits abnormally, or if an OS or hardware failure occurs (a behavior similar to running with transaction durability disabled in the Sun Java System Directory Server).
+property.db-txn-write-no-sync.synopsis=Indicates whether the database should synchronously flush data as it is written to disk.
+property.db-txn-write-no-sync.description=If this value is set to "false", then all data written to disk is synchronously flushed to persistent storage and thereby providing full durability. If it is set to "true", then data may be cached for a period of time by the underlying operating system before actually being written to disk. This may improve performance, but could cause the most recent changes to be lost in the event of an underlying OS or hardware failure (but not in the case that the OpenDS Directory Server or the JVM exits abnormally).
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.entries-compressed.synopsis=Indicates whether the backend should attempt to compress entries before storing them in the database.
+property.entries-compressed.description=Note that this property applies only to the entries themselves and does not impact the index data. Further, the effectiveness of the compression is based on the type of data contained in the entry.
+property.entries-compressed.requires-admin-action.synopsis=Changes to this setting take effect only for writes that occur after the change is made. It is not retroactively applied to existing data.
+property.import-queue-size.synopsis=Specifies the size (in number of entries) of the queue that is used to hold the entries read during an LDIF import.
+property.import-queue-size.requires-admin-action.synopsis=Changes do not take effect for any import that may already be in progress.
+property.import-thread-count.synopsis=Specifies the number of threads that is used for concurrent processing during an LDIF import.
+property.import-thread-count.description=This should generally be a small multiple (for example, 2x) of the number of CPUs in the system for a traditional system, or equal to the number of CPU strands for a CMT system.
+property.import-thread-count.requires-admin-action.synopsis=Changes do not take effect for any import that may already be in progress.
+property.index-entry-limit.synopsis=Specifies the maximum number of entries that is allowed to match a given index key before that particular index key is no longer maintained.
+property.index-entry-limit.description=This property is analogous to the ALL IDs threshold in the Sun Java System Directory Server. Note that this is the default limit for the backend, and it may be overridden on a per-attribute basis.A value of 0 means there is no limit.
+property.index-entry-limit.requires-admin-action.synopsis=If any index keys have already reached this limit, indexes need to be rebuilt before they are allowed to use the new limit.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.je-property.synopsis=Specifies the database and environment properties for the Berkeley DB Java Edition database serving the data for this backend.
+property.je-property.description=Any Berkeley DB Java Edition property can be specified using the following form: property-name=property-value. Refer to OpenDS documentation for further information on related properties, their implications, and range values. The definitive identification of all the property parameters is available in the example.properties file of Berkeley DB Java Edition distribution.
+property.preload-time-limit.synopsis=Specifies the length of time that the backend is allowed to spend "pre-loading" data when it is initialized.
+property.preload-time-limit.description=The pre-load process is used to pre-populate the database cache, so that it can be more quickly available when the server is processing requests. A duration of zero means there is no pre-load.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
+relation.local-db-index.user-friendly-name=Local DB Index
+relation.local-db-index.user-friendly-plural-name=Local DB Indexes
+relation.local-db-index.synopsis=Local DB Indexes are used to store information that makes it possible to locate entries very quickly when processing search operations.
+relation.local-db-index.description=Indexing is performed on a per-attribute level and different types of indexing may be performed for different kinds of attributes, based on how they are expected to be accessed during search operations.
+relation.local-db-vlv-index.user-friendly-name=Local DB VLV Index
+relation.local-db-vlv-index.user-friendly-plural-name=Local DB VLV Indexes
+relation.local-db-vlv-index.synopsis=Local DB VLV Indexes are used to store information about a specific search request that makes it possible to efficiently process them using the VLV control.
+relation.local-db-vlv-index.description=A VLV index effectively notifies the server that a virtual list view, with specific query and sort parameters, will be performed. This index also allows the server to collect and maintain the information required to make using the virtual list view faster.
diff --git a/opends/src/admin/messages/LocalDBBackendCfgDefn_fr.properties b/opends/src/admin/messages/LocalDBBackendCfgDefn_fr.properties
new file mode 100644
index 0000000..2075bdf
--- /dev/null
+++ b/opends/src/admin/messages/LocalDBBackendCfgDefn_fr.properties
@@ -0,0 +1,76 @@
+user-friendly-name=Local DB Backend
+user-friendly-plural-name=Local DB Backends
+synopsis=The Local DB Backend uses the Berkeley DB Java Edition to store user-provided data in a local repository.
+description=It is the traditional "directory server" backend and is similar to the backends provided by the Sun Java System Directory Server. The Local DB Backend stores the entries in an encoded form and also provides indexes that can be used to quickly locate target entries based on different kinds of criteria.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.compact-encoding.synopsis=Indicates whether the backend should use a compact form when encoding entries by compressing the attribute descriptions and object class sets.
+property.compact-encoding.description=Note that this property applies only to the entries themselves and does not impact the index data.
+property.compact-encoding.requires-admin-action.synopsis=Changes to this setting take effect only for writes that occur after the change is made. It is not retroactively applied to existing data.
+property.db-cache-percent.synopsis=Specifies the percentage of JVM memory to allocate to the database cache.
+property.db-cache-percent.description=Specifies the percentage of memory available to the JVM that should be used for caching database contents. Note that this is only used if the value of the db-cache-size property is set to "0 MB". Otherwise, the value of that property is used instead to control the cache size configuration.
+property.db-cache-size.synopsis=The amount of JVM memory to allocate to the database cache.
+property.db-cache-size.description=Specifies the amount of memory that should be used for caching database contents. A value of "0 MB" indicates that the db-cache-percent property should be used instead to specify the cache size.
+property.db-checkpointer-bytes-interval.synopsis=Specifies the maximum number of bytes that may be written to the database before it is forced to perform a checkpoint.
+property.db-checkpointer-bytes-interval.description=This can be used to bound the recovery time that may be required if the database environment is opened without having been properly closed. If this property is set to a non-zero value, the checkpointer wakeup interval is not used. To use time-based checkpointing, set this property to zero.
+property.db-checkpointer-wakeup-interval.synopsis=Specifies the maximum length of time that may pass between checkpoints.
+property.db-checkpointer-wakeup-interval.description=Note that this is only used if the value of the checkpointer bytes interval is zero.
+property.db-cleaner-min-utilization.synopsis=Specifies the minimum percentage of "live" data that the database cleaner attempts to keep in database log files.
+property.db-cleaner-min-utilization.description=If the amount of live data in any database log file drops below this percentage, then the cleaner moves the remaining live data in that file to the end of the database and deletes the original file in order to keep the database relatively compact.
+property.db-directory.synopsis=Specifies the path to the filesystem directory that is used to hold the Berkeley DB Java Edition database files containing the data for this backend.
+property.db-directory.description=The path may be either an absolute path or a path relative to the directory containing the base of the OpenDS Directory Server installation. The path may be any valid directory path in which the server has appropriate permissions to read and write files and has sufficient space to hold the database contents.
+property.db-directory-permissions.synopsis=Specifies the permissions that should be applied to the directory containing the server database files.
+property.db-directory-permissions.description=They should be expressed as three-digit octal values, which is the traditional representation for UNIX file permissions. The three digits represent the permissions that are available for the directory's owner, group members, and other users (in that order), and each digit is the octal representation of the read, write, and execute bits. Note that this only impacts permissions on the database directory and not on the files written into that directory. On UNIX systems, the user's umask controls permissions given to the database files.
+property.db-directory-permissions.syntax.string.pattern.synopsis=Any octal value between 700 and 777 (the owner must always have read, write, and execute permissions on the directory).
+property.db-evictor-lru-only.synopsis=Indicates whether the database should evict existing data from the cache based on an LRU policy (where the least recently used information will be evicted first).
+property.db-evictor-lru-only.description=If set to "false", then the eviction keeps internal nodes of the underlying Btree in the cache over leaf notes, even if the leaf nodes have been accessed more recently. This may be a better configuration for databases in which only a very small portion of the data is cached.
+property.db-evictor-nodes-per-scan.synopsis=Specifies the number of Btree nodes that should be evicted from the cache in a single pass if it is determined that it is necessary to free existing data in order to make room for new information.
+property.db-evictor-nodes-per-scan.description=Changes to this property do not take effect until the backend is restarted. It is recommended that you also change this property when you set db-evictor-lru-only to false. This setting controls the number of Btree nodes that are considered, or sampled, each time a node is evicted. A setting of 100 often produces good results, but this may vary from application to application. The larger the nodes per scan, the more accurate the algorithm. However, setting it too high is detrimental; the need to consider larger numbers of nodes for each eviction may delay the completion of a given database operation, which will impact the response time of the application thread.
+property.db-log-file-max.synopsis=Specifies the maximum size for a database log file.
+property.db-logging-file-handler-on.synopsis=Indicates whether the database should maintain a je.info file in the same directory as the database log directory.
+property.db-logging-file-handler-on.description=This file contains information about the internal processing performed by the underlying database.
+property.db-logging-level.synopsis=Specifies the log level that should be used by the database when it is writing information into the je.info file.
+property.db-logging-level.description=The database trace logging level is (in increasing order of verbosity) chosen from: OFF, SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST, ALL.
+property.db-num-cleaner-threads.synopsis=Specifies the number of threads that the backend should maintain to keep the database log files at or near the desired utilization.
+property.db-num-cleaner-threads.description=In environments with high write throughput, multiple cleaner threads may be required to maintain the desired utilization.
+property.db-num-lock-tables.synopsis=Specifies the number of lock tables that are used by the underlying database.
+property.db-num-lock-tables.description=This can be particularly important to help improve scalability by avoiding contention on systems with large numbers of CPUs. The value of this configuration property should be set to a prime number that is less than or equal to the number of worker threads configured for use in the server.
+property.db-run-cleaner.synopsis=Indicates whether the database cleaner threads should be enabled.
+property.db-run-cleaner.description=The cleaner threads are used to periodically compact the database by identifying database files with a low (that is, less than the amount specified by the db-cleaner-min-utilization property) percentage of live data, moving the remaining live data to the end of the log and deleting that file.
+property.db-txn-no-sync.synopsis=Indicates whether database writes should be primarily written to an internal buffer but not immediately written to disk.
+property.db-txn-no-sync.description=Setting the value of this configuration attribute to "true" may improve write performance but could cause the most recent changes to be lost if the OpenDS Directory Server or the underlying JVM exits abnormally, or if an OS or hardware failure occurs (a behavior similar to running with transaction durability disabled in the Sun Java System Directory Server).
+property.db-txn-write-no-sync.synopsis=Indicates whether the database should synchronously flush data as it is written to disk.
+property.db-txn-write-no-sync.description=If this value is set to "false", then all data written to disk is synchronously flushed to persistent storage and thereby providing full durability. If it is set to "true", then data may be cached for a period of time by the underlying operating system before actually being written to disk. This may improve performance, but could cause the most recent changes to be lost in the event of an underlying OS or hardware failure (but not in the case that the OpenDS Directory Server or the JVM exits abnormally).
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.entries-compressed.synopsis=Indicates whether the backend should attempt to compress entries before storing them in the database.
+property.entries-compressed.description=Note that this property applies only to the entries themselves and does not impact the index data. Further, the effectiveness of the compression is based on the type of data contained in the entry.
+property.entries-compressed.requires-admin-action.synopsis=Changes to this setting take effect only for writes that occur after the change is made. It is not retroactively applied to existing data.
+property.import-queue-size.synopsis=Specifies the size (in number of entries) of the queue that is used to hold the entries read during an LDIF import.
+property.import-queue-size.requires-admin-action.synopsis=Changes do not take effect for any import that may already be in progress.
+property.import-thread-count.synopsis=Specifies the number of threads that is used for concurrent processing during an LDIF import.
+property.import-thread-count.description=This should generally be a small multiple (for example, 2x) of the number of CPUs in the system for a traditional system, or equal to the number of CPU strands for a CMT system.
+property.import-thread-count.requires-admin-action.synopsis=Changes do not take effect for any import that may already be in progress.
+property.index-entry-limit.synopsis=Specifies the maximum number of entries that is allowed to match a given index key before that particular index key is no longer maintained.
+property.index-entry-limit.description=This property is analogous to the ALL IDs threshold in the Sun Java System Directory Server. Note that this is the default limit for the backend, and it may be overridden on a per-attribute basis.A value of 0 means there is no limit.
+property.index-entry-limit.requires-admin-action.synopsis=If any index keys have already reached this limit, indexes need to be rebuilt before they are allowed to use the new limit.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.je-property.synopsis=Specifies the database and environment properties for the Berkeley DB Java Edition database serving the data for this backend.
+property.je-property.description=Any Berkeley DB Java Edition property can be specified using the following form: property-name=property-value. Refer to OpenDS documentation for further information on related properties, their implications, and range values. The definitive identification of all the property parameters is available in the example.properties file of Berkeley DB Java Edition distribution.
+property.preload-time-limit.synopsis=Specifies the length of time that the backend is allowed to spend "pre-loading" data when it is initialized.
+property.preload-time-limit.description=The pre-load process is used to pre-populate the database cache, so that it can be more quickly available when the server is processing requests. A duration of zero means there is no pre-load.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
+relation.local-db-index.user-friendly-name=Local DB Index
+relation.local-db-index.user-friendly-plural-name=Local DB Indexes
+relation.local-db-index.synopsis=Local DB Indexes are used to store information that makes it possible to locate entries very quickly when processing search operations.
+relation.local-db-index.description=Indexing is performed on a per-attribute level and different types of indexing may be performed for different kinds of attributes, based on how they are expected to be accessed during search operations.
+relation.local-db-vlv-index.user-friendly-name=Local DB VLV Index
+relation.local-db-vlv-index.user-friendly-plural-name=Local DB VLV Indexes
+relation.local-db-vlv-index.synopsis=Local DB VLV Indexes are used to store information about a specific search request that makes it possible to efficiently process them using the VLV control.
+relation.local-db-vlv-index.description=A VLV index effectively notifies the server that a virtual list view, with specific query and sort parameters, will be performed. This index also allows the server to collect and maintain the information required to make using the virtual list view faster.
diff --git a/opends/src/admin/messages/LocalDBBackendCfgDefn_ja.properties b/opends/src/admin/messages/LocalDBBackendCfgDefn_ja.properties
new file mode 100644
index 0000000..2075bdf
--- /dev/null
+++ b/opends/src/admin/messages/LocalDBBackendCfgDefn_ja.properties
@@ -0,0 +1,76 @@
+user-friendly-name=Local DB Backend
+user-friendly-plural-name=Local DB Backends
+synopsis=The Local DB Backend uses the Berkeley DB Java Edition to store user-provided data in a local repository.
+description=It is the traditional "directory server" backend and is similar to the backends provided by the Sun Java System Directory Server. The Local DB Backend stores the entries in an encoded form and also provides indexes that can be used to quickly locate target entries based on different kinds of criteria.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.compact-encoding.synopsis=Indicates whether the backend should use a compact form when encoding entries by compressing the attribute descriptions and object class sets.
+property.compact-encoding.description=Note that this property applies only to the entries themselves and does not impact the index data.
+property.compact-encoding.requires-admin-action.synopsis=Changes to this setting take effect only for writes that occur after the change is made. It is not retroactively applied to existing data.
+property.db-cache-percent.synopsis=Specifies the percentage of JVM memory to allocate to the database cache.
+property.db-cache-percent.description=Specifies the percentage of memory available to the JVM that should be used for caching database contents. Note that this is only used if the value of the db-cache-size property is set to "0 MB". Otherwise, the value of that property is used instead to control the cache size configuration.
+property.db-cache-size.synopsis=The amount of JVM memory to allocate to the database cache.
+property.db-cache-size.description=Specifies the amount of memory that should be used for caching database contents. A value of "0 MB" indicates that the db-cache-percent property should be used instead to specify the cache size.
+property.db-checkpointer-bytes-interval.synopsis=Specifies the maximum number of bytes that may be written to the database before it is forced to perform a checkpoint.
+property.db-checkpointer-bytes-interval.description=This can be used to bound the recovery time that may be required if the database environment is opened without having been properly closed. If this property is set to a non-zero value, the checkpointer wakeup interval is not used. To use time-based checkpointing, set this property to zero.
+property.db-checkpointer-wakeup-interval.synopsis=Specifies the maximum length of time that may pass between checkpoints.
+property.db-checkpointer-wakeup-interval.description=Note that this is only used if the value of the checkpointer bytes interval is zero.
+property.db-cleaner-min-utilization.synopsis=Specifies the minimum percentage of "live" data that the database cleaner attempts to keep in database log files.
+property.db-cleaner-min-utilization.description=If the amount of live data in any database log file drops below this percentage, then the cleaner moves the remaining live data in that file to the end of the database and deletes the original file in order to keep the database relatively compact.
+property.db-directory.synopsis=Specifies the path to the filesystem directory that is used to hold the Berkeley DB Java Edition database files containing the data for this backend.
+property.db-directory.description=The path may be either an absolute path or a path relative to the directory containing the base of the OpenDS Directory Server installation. The path may be any valid directory path in which the server has appropriate permissions to read and write files and has sufficient space to hold the database contents.
+property.db-directory-permissions.synopsis=Specifies the permissions that should be applied to the directory containing the server database files.
+property.db-directory-permissions.description=They should be expressed as three-digit octal values, which is the traditional representation for UNIX file permissions. The three digits represent the permissions that are available for the directory's owner, group members, and other users (in that order), and each digit is the octal representation of the read, write, and execute bits. Note that this only impacts permissions on the database directory and not on the files written into that directory. On UNIX systems, the user's umask controls permissions given to the database files.
+property.db-directory-permissions.syntax.string.pattern.synopsis=Any octal value between 700 and 777 (the owner must always have read, write, and execute permissions on the directory).
+property.db-evictor-lru-only.synopsis=Indicates whether the database should evict existing data from the cache based on an LRU policy (where the least recently used information will be evicted first).
+property.db-evictor-lru-only.description=If set to "false", then the eviction keeps internal nodes of the underlying Btree in the cache over leaf notes, even if the leaf nodes have been accessed more recently. This may be a better configuration for databases in which only a very small portion of the data is cached.
+property.db-evictor-nodes-per-scan.synopsis=Specifies the number of Btree nodes that should be evicted from the cache in a single pass if it is determined that it is necessary to free existing data in order to make room for new information.
+property.db-evictor-nodes-per-scan.description=Changes to this property do not take effect until the backend is restarted. It is recommended that you also change this property when you set db-evictor-lru-only to false. This setting controls the number of Btree nodes that are considered, or sampled, each time a node is evicted. A setting of 100 often produces good results, but this may vary from application to application. The larger the nodes per scan, the more accurate the algorithm. However, setting it too high is detrimental; the need to consider larger numbers of nodes for each eviction may delay the completion of a given database operation, which will impact the response time of the application thread.
+property.db-log-file-max.synopsis=Specifies the maximum size for a database log file.
+property.db-logging-file-handler-on.synopsis=Indicates whether the database should maintain a je.info file in the same directory as the database log directory.
+property.db-logging-file-handler-on.description=This file contains information about the internal processing performed by the underlying database.
+property.db-logging-level.synopsis=Specifies the log level that should be used by the database when it is writing information into the je.info file.
+property.db-logging-level.description=The database trace logging level is (in increasing order of verbosity) chosen from: OFF, SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST, ALL.
+property.db-num-cleaner-threads.synopsis=Specifies the number of threads that the backend should maintain to keep the database log files at or near the desired utilization.
+property.db-num-cleaner-threads.description=In environments with high write throughput, multiple cleaner threads may be required to maintain the desired utilization.
+property.db-num-lock-tables.synopsis=Specifies the number of lock tables that are used by the underlying database.
+property.db-num-lock-tables.description=This can be particularly important to help improve scalability by avoiding contention on systems with large numbers of CPUs. The value of this configuration property should be set to a prime number that is less than or equal to the number of worker threads configured for use in the server.
+property.db-run-cleaner.synopsis=Indicates whether the database cleaner threads should be enabled.
+property.db-run-cleaner.description=The cleaner threads are used to periodically compact the database by identifying database files with a low (that is, less than the amount specified by the db-cleaner-min-utilization property) percentage of live data, moving the remaining live data to the end of the log and deleting that file.
+property.db-txn-no-sync.synopsis=Indicates whether database writes should be primarily written to an internal buffer but not immediately written to disk.
+property.db-txn-no-sync.description=Setting the value of this configuration attribute to "true" may improve write performance but could cause the most recent changes to be lost if the OpenDS Directory Server or the underlying JVM exits abnormally, or if an OS or hardware failure occurs (a behavior similar to running with transaction durability disabled in the Sun Java System Directory Server).
+property.db-txn-write-no-sync.synopsis=Indicates whether the database should synchronously flush data as it is written to disk.
+property.db-txn-write-no-sync.description=If this value is set to "false", then all data written to disk is synchronously flushed to persistent storage and thereby providing full durability. If it is set to "true", then data may be cached for a period of time by the underlying operating system before actually being written to disk. This may improve performance, but could cause the most recent changes to be lost in the event of an underlying OS or hardware failure (but not in the case that the OpenDS Directory Server or the JVM exits abnormally).
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.entries-compressed.synopsis=Indicates whether the backend should attempt to compress entries before storing them in the database.
+property.entries-compressed.description=Note that this property applies only to the entries themselves and does not impact the index data. Further, the effectiveness of the compression is based on the type of data contained in the entry.
+property.entries-compressed.requires-admin-action.synopsis=Changes to this setting take effect only for writes that occur after the change is made. It is not retroactively applied to existing data.
+property.import-queue-size.synopsis=Specifies the size (in number of entries) of the queue that is used to hold the entries read during an LDIF import.
+property.import-queue-size.requires-admin-action.synopsis=Changes do not take effect for any import that may already be in progress.
+property.import-thread-count.synopsis=Specifies the number of threads that is used for concurrent processing during an LDIF import.
+property.import-thread-count.description=This should generally be a small multiple (for example, 2x) of the number of CPUs in the system for a traditional system, or equal to the number of CPU strands for a CMT system.
+property.import-thread-count.requires-admin-action.synopsis=Changes do not take effect for any import that may already be in progress.
+property.index-entry-limit.synopsis=Specifies the maximum number of entries that is allowed to match a given index key before that particular index key is no longer maintained.
+property.index-entry-limit.description=This property is analogous to the ALL IDs threshold in the Sun Java System Directory Server. Note that this is the default limit for the backend, and it may be overridden on a per-attribute basis.A value of 0 means there is no limit.
+property.index-entry-limit.requires-admin-action.synopsis=If any index keys have already reached this limit, indexes need to be rebuilt before they are allowed to use the new limit.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.je-property.synopsis=Specifies the database and environment properties for the Berkeley DB Java Edition database serving the data for this backend.
+property.je-property.description=Any Berkeley DB Java Edition property can be specified using the following form: property-name=property-value. Refer to OpenDS documentation for further information on related properties, their implications, and range values. The definitive identification of all the property parameters is available in the example.properties file of Berkeley DB Java Edition distribution.
+property.preload-time-limit.synopsis=Specifies the length of time that the backend is allowed to spend "pre-loading" data when it is initialized.
+property.preload-time-limit.description=The pre-load process is used to pre-populate the database cache, so that it can be more quickly available when the server is processing requests. A duration of zero means there is no pre-load.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
+relation.local-db-index.user-friendly-name=Local DB Index
+relation.local-db-index.user-friendly-plural-name=Local DB Indexes
+relation.local-db-index.synopsis=Local DB Indexes are used to store information that makes it possible to locate entries very quickly when processing search operations.
+relation.local-db-index.description=Indexing is performed on a per-attribute level and different types of indexing may be performed for different kinds of attributes, based on how they are expected to be accessed during search operations.
+relation.local-db-vlv-index.user-friendly-name=Local DB VLV Index
+relation.local-db-vlv-index.user-friendly-plural-name=Local DB VLV Indexes
+relation.local-db-vlv-index.synopsis=Local DB VLV Indexes are used to store information about a specific search request that makes it possible to efficiently process them using the VLV control.
+relation.local-db-vlv-index.description=A VLV index effectively notifies the server that a virtual list view, with specific query and sort parameters, will be performed. This index also allows the server to collect and maintain the information required to make using the virtual list view faster.
diff --git a/opends/src/admin/messages/LocalDBBackendCfgDefn_ko.properties b/opends/src/admin/messages/LocalDBBackendCfgDefn_ko.properties
new file mode 100644
index 0000000..2075bdf
--- /dev/null
+++ b/opends/src/admin/messages/LocalDBBackendCfgDefn_ko.properties
@@ -0,0 +1,76 @@
+user-friendly-name=Local DB Backend
+user-friendly-plural-name=Local DB Backends
+synopsis=The Local DB Backend uses the Berkeley DB Java Edition to store user-provided data in a local repository.
+description=It is the traditional "directory server" backend and is similar to the backends provided by the Sun Java System Directory Server. The Local DB Backend stores the entries in an encoded form and also provides indexes that can be used to quickly locate target entries based on different kinds of criteria.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.compact-encoding.synopsis=Indicates whether the backend should use a compact form when encoding entries by compressing the attribute descriptions and object class sets.
+property.compact-encoding.description=Note that this property applies only to the entries themselves and does not impact the index data.
+property.compact-encoding.requires-admin-action.synopsis=Changes to this setting take effect only for writes that occur after the change is made. It is not retroactively applied to existing data.
+property.db-cache-percent.synopsis=Specifies the percentage of JVM memory to allocate to the database cache.
+property.db-cache-percent.description=Specifies the percentage of memory available to the JVM that should be used for caching database contents. Note that this is only used if the value of the db-cache-size property is set to "0 MB". Otherwise, the value of that property is used instead to control the cache size configuration.
+property.db-cache-size.synopsis=The amount of JVM memory to allocate to the database cache.
+property.db-cache-size.description=Specifies the amount of memory that should be used for caching database contents. A value of "0 MB" indicates that the db-cache-percent property should be used instead to specify the cache size.
+property.db-checkpointer-bytes-interval.synopsis=Specifies the maximum number of bytes that may be written to the database before it is forced to perform a checkpoint.
+property.db-checkpointer-bytes-interval.description=This can be used to bound the recovery time that may be required if the database environment is opened without having been properly closed. If this property is set to a non-zero value, the checkpointer wakeup interval is not used. To use time-based checkpointing, set this property to zero.
+property.db-checkpointer-wakeup-interval.synopsis=Specifies the maximum length of time that may pass between checkpoints.
+property.db-checkpointer-wakeup-interval.description=Note that this is only used if the value of the checkpointer bytes interval is zero.
+property.db-cleaner-min-utilization.synopsis=Specifies the minimum percentage of "live" data that the database cleaner attempts to keep in database log files.
+property.db-cleaner-min-utilization.description=If the amount of live data in any database log file drops below this percentage, then the cleaner moves the remaining live data in that file to the end of the database and deletes the original file in order to keep the database relatively compact.
+property.db-directory.synopsis=Specifies the path to the filesystem directory that is used to hold the Berkeley DB Java Edition database files containing the data for this backend.
+property.db-directory.description=The path may be either an absolute path or a path relative to the directory containing the base of the OpenDS Directory Server installation. The path may be any valid directory path in which the server has appropriate permissions to read and write files and has sufficient space to hold the database contents.
+property.db-directory-permissions.synopsis=Specifies the permissions that should be applied to the directory containing the server database files.
+property.db-directory-permissions.description=They should be expressed as three-digit octal values, which is the traditional representation for UNIX file permissions. The three digits represent the permissions that are available for the directory's owner, group members, and other users (in that order), and each digit is the octal representation of the read, write, and execute bits. Note that this only impacts permissions on the database directory and not on the files written into that directory. On UNIX systems, the user's umask controls permissions given to the database files.
+property.db-directory-permissions.syntax.string.pattern.synopsis=Any octal value between 700 and 777 (the owner must always have read, write, and execute permissions on the directory).
+property.db-evictor-lru-only.synopsis=Indicates whether the database should evict existing data from the cache based on an LRU policy (where the least recently used information will be evicted first).
+property.db-evictor-lru-only.description=If set to "false", then the eviction keeps internal nodes of the underlying Btree in the cache over leaf notes, even if the leaf nodes have been accessed more recently. This may be a better configuration for databases in which only a very small portion of the data is cached.
+property.db-evictor-nodes-per-scan.synopsis=Specifies the number of Btree nodes that should be evicted from the cache in a single pass if it is determined that it is necessary to free existing data in order to make room for new information.
+property.db-evictor-nodes-per-scan.description=Changes to this property do not take effect until the backend is restarted. It is recommended that you also change this property when you set db-evictor-lru-only to false. This setting controls the number of Btree nodes that are considered, or sampled, each time a node is evicted. A setting of 100 often produces good results, but this may vary from application to application. The larger the nodes per scan, the more accurate the algorithm. However, setting it too high is detrimental; the need to consider larger numbers of nodes for each eviction may delay the completion of a given database operation, which will impact the response time of the application thread.
+property.db-log-file-max.synopsis=Specifies the maximum size for a database log file.
+property.db-logging-file-handler-on.synopsis=Indicates whether the database should maintain a je.info file in the same directory as the database log directory.
+property.db-logging-file-handler-on.description=This file contains information about the internal processing performed by the underlying database.
+property.db-logging-level.synopsis=Specifies the log level that should be used by the database when it is writing information into the je.info file.
+property.db-logging-level.description=The database trace logging level is (in increasing order of verbosity) chosen from: OFF, SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST, ALL.
+property.db-num-cleaner-threads.synopsis=Specifies the number of threads that the backend should maintain to keep the database log files at or near the desired utilization.
+property.db-num-cleaner-threads.description=In environments with high write throughput, multiple cleaner threads may be required to maintain the desired utilization.
+property.db-num-lock-tables.synopsis=Specifies the number of lock tables that are used by the underlying database.
+property.db-num-lock-tables.description=This can be particularly important to help improve scalability by avoiding contention on systems with large numbers of CPUs. The value of this configuration property should be set to a prime number that is less than or equal to the number of worker threads configured for use in the server.
+property.db-run-cleaner.synopsis=Indicates whether the database cleaner threads should be enabled.
+property.db-run-cleaner.description=The cleaner threads are used to periodically compact the database by identifying database files with a low (that is, less than the amount specified by the db-cleaner-min-utilization property) percentage of live data, moving the remaining live data to the end of the log and deleting that file.
+property.db-txn-no-sync.synopsis=Indicates whether database writes should be primarily written to an internal buffer but not immediately written to disk.
+property.db-txn-no-sync.description=Setting the value of this configuration attribute to "true" may improve write performance but could cause the most recent changes to be lost if the OpenDS Directory Server or the underlying JVM exits abnormally, or if an OS or hardware failure occurs (a behavior similar to running with transaction durability disabled in the Sun Java System Directory Server).
+property.db-txn-write-no-sync.synopsis=Indicates whether the database should synchronously flush data as it is written to disk.
+property.db-txn-write-no-sync.description=If this value is set to "false", then all data written to disk is synchronously flushed to persistent storage and thereby providing full durability. If it is set to "true", then data may be cached for a period of time by the underlying operating system before actually being written to disk. This may improve performance, but could cause the most recent changes to be lost in the event of an underlying OS or hardware failure (but not in the case that the OpenDS Directory Server or the JVM exits abnormally).
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.entries-compressed.synopsis=Indicates whether the backend should attempt to compress entries before storing them in the database.
+property.entries-compressed.description=Note that this property applies only to the entries themselves and does not impact the index data. Further, the effectiveness of the compression is based on the type of data contained in the entry.
+property.entries-compressed.requires-admin-action.synopsis=Changes to this setting take effect only for writes that occur after the change is made. It is not retroactively applied to existing data.
+property.import-queue-size.synopsis=Specifies the size (in number of entries) of the queue that is used to hold the entries read during an LDIF import.
+property.import-queue-size.requires-admin-action.synopsis=Changes do not take effect for any import that may already be in progress.
+property.import-thread-count.synopsis=Specifies the number of threads that is used for concurrent processing during an LDIF import.
+property.import-thread-count.description=This should generally be a small multiple (for example, 2x) of the number of CPUs in the system for a traditional system, or equal to the number of CPU strands for a CMT system.
+property.import-thread-count.requires-admin-action.synopsis=Changes do not take effect for any import that may already be in progress.
+property.index-entry-limit.synopsis=Specifies the maximum number of entries that is allowed to match a given index key before that particular index key is no longer maintained.
+property.index-entry-limit.description=This property is analogous to the ALL IDs threshold in the Sun Java System Directory Server. Note that this is the default limit for the backend, and it may be overridden on a per-attribute basis.A value of 0 means there is no limit.
+property.index-entry-limit.requires-admin-action.synopsis=If any index keys have already reached this limit, indexes need to be rebuilt before they are allowed to use the new limit.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.je-property.synopsis=Specifies the database and environment properties for the Berkeley DB Java Edition database serving the data for this backend.
+property.je-property.description=Any Berkeley DB Java Edition property can be specified using the following form: property-name=property-value. Refer to OpenDS documentation for further information on related properties, their implications, and range values. The definitive identification of all the property parameters is available in the example.properties file of Berkeley DB Java Edition distribution.
+property.preload-time-limit.synopsis=Specifies the length of time that the backend is allowed to spend "pre-loading" data when it is initialized.
+property.preload-time-limit.description=The pre-load process is used to pre-populate the database cache, so that it can be more quickly available when the server is processing requests. A duration of zero means there is no pre-load.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
+relation.local-db-index.user-friendly-name=Local DB Index
+relation.local-db-index.user-friendly-plural-name=Local DB Indexes
+relation.local-db-index.synopsis=Local DB Indexes are used to store information that makes it possible to locate entries very quickly when processing search operations.
+relation.local-db-index.description=Indexing is performed on a per-attribute level and different types of indexing may be performed for different kinds of attributes, based on how they are expected to be accessed during search operations.
+relation.local-db-vlv-index.user-friendly-name=Local DB VLV Index
+relation.local-db-vlv-index.user-friendly-plural-name=Local DB VLV Indexes
+relation.local-db-vlv-index.synopsis=Local DB VLV Indexes are used to store information about a specific search request that makes it possible to efficiently process them using the VLV control.
+relation.local-db-vlv-index.description=A VLV index effectively notifies the server that a virtual list view, with specific query and sort parameters, will be performed. This index also allows the server to collect and maintain the information required to make using the virtual list view faster.
diff --git a/opends/src/admin/messages/LocalDBBackendCfgDefn_zh_CN.properties b/opends/src/admin/messages/LocalDBBackendCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..2075bdf
--- /dev/null
+++ b/opends/src/admin/messages/LocalDBBackendCfgDefn_zh_CN.properties
@@ -0,0 +1,76 @@
+user-friendly-name=Local DB Backend
+user-friendly-plural-name=Local DB Backends
+synopsis=The Local DB Backend uses the Berkeley DB Java Edition to store user-provided data in a local repository.
+description=It is the traditional "directory server" backend and is similar to the backends provided by the Sun Java System Directory Server. The Local DB Backend stores the entries in an encoded form and also provides indexes that can be used to quickly locate target entries based on different kinds of criteria.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.compact-encoding.synopsis=Indicates whether the backend should use a compact form when encoding entries by compressing the attribute descriptions and object class sets.
+property.compact-encoding.description=Note that this property applies only to the entries themselves and does not impact the index data.
+property.compact-encoding.requires-admin-action.synopsis=Changes to this setting take effect only for writes that occur after the change is made. It is not retroactively applied to existing data.
+property.db-cache-percent.synopsis=Specifies the percentage of JVM memory to allocate to the database cache.
+property.db-cache-percent.description=Specifies the percentage of memory available to the JVM that should be used for caching database contents. Note that this is only used if the value of the db-cache-size property is set to "0 MB". Otherwise, the value of that property is used instead to control the cache size configuration.
+property.db-cache-size.synopsis=The amount of JVM memory to allocate to the database cache.
+property.db-cache-size.description=Specifies the amount of memory that should be used for caching database contents. A value of "0 MB" indicates that the db-cache-percent property should be used instead to specify the cache size.
+property.db-checkpointer-bytes-interval.synopsis=Specifies the maximum number of bytes that may be written to the database before it is forced to perform a checkpoint.
+property.db-checkpointer-bytes-interval.description=This can be used to bound the recovery time that may be required if the database environment is opened without having been properly closed. If this property is set to a non-zero value, the checkpointer wakeup interval is not used. To use time-based checkpointing, set this property to zero.
+property.db-checkpointer-wakeup-interval.synopsis=Specifies the maximum length of time that may pass between checkpoints.
+property.db-checkpointer-wakeup-interval.description=Note that this is only used if the value of the checkpointer bytes interval is zero.
+property.db-cleaner-min-utilization.synopsis=Specifies the minimum percentage of "live" data that the database cleaner attempts to keep in database log files.
+property.db-cleaner-min-utilization.description=If the amount of live data in any database log file drops below this percentage, then the cleaner moves the remaining live data in that file to the end of the database and deletes the original file in order to keep the database relatively compact.
+property.db-directory.synopsis=Specifies the path to the filesystem directory that is used to hold the Berkeley DB Java Edition database files containing the data for this backend.
+property.db-directory.description=The path may be either an absolute path or a path relative to the directory containing the base of the OpenDS Directory Server installation. The path may be any valid directory path in which the server has appropriate permissions to read and write files and has sufficient space to hold the database contents.
+property.db-directory-permissions.synopsis=Specifies the permissions that should be applied to the directory containing the server database files.
+property.db-directory-permissions.description=They should be expressed as three-digit octal values, which is the traditional representation for UNIX file permissions. The three digits represent the permissions that are available for the directory's owner, group members, and other users (in that order), and each digit is the octal representation of the read, write, and execute bits. Note that this only impacts permissions on the database directory and not on the files written into that directory. On UNIX systems, the user's umask controls permissions given to the database files.
+property.db-directory-permissions.syntax.string.pattern.synopsis=Any octal value between 700 and 777 (the owner must always have read, write, and execute permissions on the directory).
+property.db-evictor-lru-only.synopsis=Indicates whether the database should evict existing data from the cache based on an LRU policy (where the least recently used information will be evicted first).
+property.db-evictor-lru-only.description=If set to "false", then the eviction keeps internal nodes of the underlying Btree in the cache over leaf notes, even if the leaf nodes have been accessed more recently. This may be a better configuration for databases in which only a very small portion of the data is cached.
+property.db-evictor-nodes-per-scan.synopsis=Specifies the number of Btree nodes that should be evicted from the cache in a single pass if it is determined that it is necessary to free existing data in order to make room for new information.
+property.db-evictor-nodes-per-scan.description=Changes to this property do not take effect until the backend is restarted. It is recommended that you also change this property when you set db-evictor-lru-only to false. This setting controls the number of Btree nodes that are considered, or sampled, each time a node is evicted. A setting of 100 often produces good results, but this may vary from application to application. The larger the nodes per scan, the more accurate the algorithm. However, setting it too high is detrimental; the need to consider larger numbers of nodes for each eviction may delay the completion of a given database operation, which will impact the response time of the application thread.
+property.db-log-file-max.synopsis=Specifies the maximum size for a database log file.
+property.db-logging-file-handler-on.synopsis=Indicates whether the database should maintain a je.info file in the same directory as the database log directory.
+property.db-logging-file-handler-on.description=This file contains information about the internal processing performed by the underlying database.
+property.db-logging-level.synopsis=Specifies the log level that should be used by the database when it is writing information into the je.info file.
+property.db-logging-level.description=The database trace logging level is (in increasing order of verbosity) chosen from: OFF, SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST, ALL.
+property.db-num-cleaner-threads.synopsis=Specifies the number of threads that the backend should maintain to keep the database log files at or near the desired utilization.
+property.db-num-cleaner-threads.description=In environments with high write throughput, multiple cleaner threads may be required to maintain the desired utilization.
+property.db-num-lock-tables.synopsis=Specifies the number of lock tables that are used by the underlying database.
+property.db-num-lock-tables.description=This can be particularly important to help improve scalability by avoiding contention on systems with large numbers of CPUs. The value of this configuration property should be set to a prime number that is less than or equal to the number of worker threads configured for use in the server.
+property.db-run-cleaner.synopsis=Indicates whether the database cleaner threads should be enabled.
+property.db-run-cleaner.description=The cleaner threads are used to periodically compact the database by identifying database files with a low (that is, less than the amount specified by the db-cleaner-min-utilization property) percentage of live data, moving the remaining live data to the end of the log and deleting that file.
+property.db-txn-no-sync.synopsis=Indicates whether database writes should be primarily written to an internal buffer but not immediately written to disk.
+property.db-txn-no-sync.description=Setting the value of this configuration attribute to "true" may improve write performance but could cause the most recent changes to be lost if the OpenDS Directory Server or the underlying JVM exits abnormally, or if an OS or hardware failure occurs (a behavior similar to running with transaction durability disabled in the Sun Java System Directory Server).
+property.db-txn-write-no-sync.synopsis=Indicates whether the database should synchronously flush data as it is written to disk.
+property.db-txn-write-no-sync.description=If this value is set to "false", then all data written to disk is synchronously flushed to persistent storage and thereby providing full durability. If it is set to "true", then data may be cached for a period of time by the underlying operating system before actually being written to disk. This may improve performance, but could cause the most recent changes to be lost in the event of an underlying OS or hardware failure (but not in the case that the OpenDS Directory Server or the JVM exits abnormally).
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.entries-compressed.synopsis=Indicates whether the backend should attempt to compress entries before storing them in the database.
+property.entries-compressed.description=Note that this property applies only to the entries themselves and does not impact the index data. Further, the effectiveness of the compression is based on the type of data contained in the entry.
+property.entries-compressed.requires-admin-action.synopsis=Changes to this setting take effect only for writes that occur after the change is made. It is not retroactively applied to existing data.
+property.import-queue-size.synopsis=Specifies the size (in number of entries) of the queue that is used to hold the entries read during an LDIF import.
+property.import-queue-size.requires-admin-action.synopsis=Changes do not take effect for any import that may already be in progress.
+property.import-thread-count.synopsis=Specifies the number of threads that is used for concurrent processing during an LDIF import.
+property.import-thread-count.description=This should generally be a small multiple (for example, 2x) of the number of CPUs in the system for a traditional system, or equal to the number of CPU strands for a CMT system.
+property.import-thread-count.requires-admin-action.synopsis=Changes do not take effect for any import that may already be in progress.
+property.index-entry-limit.synopsis=Specifies the maximum number of entries that is allowed to match a given index key before that particular index key is no longer maintained.
+property.index-entry-limit.description=This property is analogous to the ALL IDs threshold in the Sun Java System Directory Server. Note that this is the default limit for the backend, and it may be overridden on a per-attribute basis.A value of 0 means there is no limit.
+property.index-entry-limit.requires-admin-action.synopsis=If any index keys have already reached this limit, indexes need to be rebuilt before they are allowed to use the new limit.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.je-property.synopsis=Specifies the database and environment properties for the Berkeley DB Java Edition database serving the data for this backend.
+property.je-property.description=Any Berkeley DB Java Edition property can be specified using the following form: property-name=property-value. Refer to OpenDS documentation for further information on related properties, their implications, and range values. The definitive identification of all the property parameters is available in the example.properties file of Berkeley DB Java Edition distribution.
+property.preload-time-limit.synopsis=Specifies the length of time that the backend is allowed to spend "pre-loading" data when it is initialized.
+property.preload-time-limit.description=The pre-load process is used to pre-populate the database cache, so that it can be more quickly available when the server is processing requests. A duration of zero means there is no pre-load.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
+relation.local-db-index.user-friendly-name=Local DB Index
+relation.local-db-index.user-friendly-plural-name=Local DB Indexes
+relation.local-db-index.synopsis=Local DB Indexes are used to store information that makes it possible to locate entries very quickly when processing search operations.
+relation.local-db-index.description=Indexing is performed on a per-attribute level and different types of indexing may be performed for different kinds of attributes, based on how they are expected to be accessed during search operations.
+relation.local-db-vlv-index.user-friendly-name=Local DB VLV Index
+relation.local-db-vlv-index.user-friendly-plural-name=Local DB VLV Indexes
+relation.local-db-vlv-index.synopsis=Local DB VLV Indexes are used to store information about a specific search request that makes it possible to efficiently process them using the VLV control.
+relation.local-db-vlv-index.description=A VLV index effectively notifies the server that a virtual list view, with specific query and sort parameters, will be performed. This index also allows the server to collect and maintain the information required to make using the virtual list view faster.
diff --git a/opends/src/admin/messages/LocalDBBackendCfgDefn_zh_TW.properties b/opends/src/admin/messages/LocalDBBackendCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..2075bdf
--- /dev/null
+++ b/opends/src/admin/messages/LocalDBBackendCfgDefn_zh_TW.properties
@@ -0,0 +1,76 @@
+user-friendly-name=Local DB Backend
+user-friendly-plural-name=Local DB Backends
+synopsis=The Local DB Backend uses the Berkeley DB Java Edition to store user-provided data in a local repository.
+description=It is the traditional "directory server" backend and is similar to the backends provided by the Sun Java System Directory Server. The Local DB Backend stores the entries in an encoded form and also provides indexes that can be used to quickly locate target entries based on different kinds of criteria.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.compact-encoding.synopsis=Indicates whether the backend should use a compact form when encoding entries by compressing the attribute descriptions and object class sets.
+property.compact-encoding.description=Note that this property applies only to the entries themselves and does not impact the index data.
+property.compact-encoding.requires-admin-action.synopsis=Changes to this setting take effect only for writes that occur after the change is made. It is not retroactively applied to existing data.
+property.db-cache-percent.synopsis=Specifies the percentage of JVM memory to allocate to the database cache.
+property.db-cache-percent.description=Specifies the percentage of memory available to the JVM that should be used for caching database contents. Note that this is only used if the value of the db-cache-size property is set to "0 MB". Otherwise, the value of that property is used instead to control the cache size configuration.
+property.db-cache-size.synopsis=The amount of JVM memory to allocate to the database cache.
+property.db-cache-size.description=Specifies the amount of memory that should be used for caching database contents. A value of "0 MB" indicates that the db-cache-percent property should be used instead to specify the cache size.
+property.db-checkpointer-bytes-interval.synopsis=Specifies the maximum number of bytes that may be written to the database before it is forced to perform a checkpoint.
+property.db-checkpointer-bytes-interval.description=This can be used to bound the recovery time that may be required if the database environment is opened without having been properly closed. If this property is set to a non-zero value, the checkpointer wakeup interval is not used. To use time-based checkpointing, set this property to zero.
+property.db-checkpointer-wakeup-interval.synopsis=Specifies the maximum length of time that may pass between checkpoints.
+property.db-checkpointer-wakeup-interval.description=Note that this is only used if the value of the checkpointer bytes interval is zero.
+property.db-cleaner-min-utilization.synopsis=Specifies the minimum percentage of "live" data that the database cleaner attempts to keep in database log files.
+property.db-cleaner-min-utilization.description=If the amount of live data in any database log file drops below this percentage, then the cleaner moves the remaining live data in that file to the end of the database and deletes the original file in order to keep the database relatively compact.
+property.db-directory.synopsis=Specifies the path to the filesystem directory that is used to hold the Berkeley DB Java Edition database files containing the data for this backend.
+property.db-directory.description=The path may be either an absolute path or a path relative to the directory containing the base of the OpenDS Directory Server installation. The path may be any valid directory path in which the server has appropriate permissions to read and write files and has sufficient space to hold the database contents.
+property.db-directory-permissions.synopsis=Specifies the permissions that should be applied to the directory containing the server database files.
+property.db-directory-permissions.description=They should be expressed as three-digit octal values, which is the traditional representation for UNIX file permissions. The three digits represent the permissions that are available for the directory's owner, group members, and other users (in that order), and each digit is the octal representation of the read, write, and execute bits. Note that this only impacts permissions on the database directory and not on the files written into that directory. On UNIX systems, the user's umask controls permissions given to the database files.
+property.db-directory-permissions.syntax.string.pattern.synopsis=Any octal value between 700 and 777 (the owner must always have read, write, and execute permissions on the directory).
+property.db-evictor-lru-only.synopsis=Indicates whether the database should evict existing data from the cache based on an LRU policy (where the least recently used information will be evicted first).
+property.db-evictor-lru-only.description=If set to "false", then the eviction keeps internal nodes of the underlying Btree in the cache over leaf notes, even if the leaf nodes have been accessed more recently. This may be a better configuration for databases in which only a very small portion of the data is cached.
+property.db-evictor-nodes-per-scan.synopsis=Specifies the number of Btree nodes that should be evicted from the cache in a single pass if it is determined that it is necessary to free existing data in order to make room for new information.
+property.db-evictor-nodes-per-scan.description=Changes to this property do not take effect until the backend is restarted. It is recommended that you also change this property when you set db-evictor-lru-only to false. This setting controls the number of Btree nodes that are considered, or sampled, each time a node is evicted. A setting of 100 often produces good results, but this may vary from application to application. The larger the nodes per scan, the more accurate the algorithm. However, setting it too high is detrimental; the need to consider larger numbers of nodes for each eviction may delay the completion of a given database operation, which will impact the response time of the application thread.
+property.db-log-file-max.synopsis=Specifies the maximum size for a database log file.
+property.db-logging-file-handler-on.synopsis=Indicates whether the database should maintain a je.info file in the same directory as the database log directory.
+property.db-logging-file-handler-on.description=This file contains information about the internal processing performed by the underlying database.
+property.db-logging-level.synopsis=Specifies the log level that should be used by the database when it is writing information into the je.info file.
+property.db-logging-level.description=The database trace logging level is (in increasing order of verbosity) chosen from: OFF, SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST, ALL.
+property.db-num-cleaner-threads.synopsis=Specifies the number of threads that the backend should maintain to keep the database log files at or near the desired utilization.
+property.db-num-cleaner-threads.description=In environments with high write throughput, multiple cleaner threads may be required to maintain the desired utilization.
+property.db-num-lock-tables.synopsis=Specifies the number of lock tables that are used by the underlying database.
+property.db-num-lock-tables.description=This can be particularly important to help improve scalability by avoiding contention on systems with large numbers of CPUs. The value of this configuration property should be set to a prime number that is less than or equal to the number of worker threads configured for use in the server.
+property.db-run-cleaner.synopsis=Indicates whether the database cleaner threads should be enabled.
+property.db-run-cleaner.description=The cleaner threads are used to periodically compact the database by identifying database files with a low (that is, less than the amount specified by the db-cleaner-min-utilization property) percentage of live data, moving the remaining live data to the end of the log and deleting that file.
+property.db-txn-no-sync.synopsis=Indicates whether database writes should be primarily written to an internal buffer but not immediately written to disk.
+property.db-txn-no-sync.description=Setting the value of this configuration attribute to "true" may improve write performance but could cause the most recent changes to be lost if the OpenDS Directory Server or the underlying JVM exits abnormally, or if an OS or hardware failure occurs (a behavior similar to running with transaction durability disabled in the Sun Java System Directory Server).
+property.db-txn-write-no-sync.synopsis=Indicates whether the database should synchronously flush data as it is written to disk.
+property.db-txn-write-no-sync.description=If this value is set to "false", then all data written to disk is synchronously flushed to persistent storage and thereby providing full durability. If it is set to "true", then data may be cached for a period of time by the underlying operating system before actually being written to disk. This may improve performance, but could cause the most recent changes to be lost in the event of an underlying OS or hardware failure (but not in the case that the OpenDS Directory Server or the JVM exits abnormally).
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.entries-compressed.synopsis=Indicates whether the backend should attempt to compress entries before storing them in the database.
+property.entries-compressed.description=Note that this property applies only to the entries themselves and does not impact the index data. Further, the effectiveness of the compression is based on the type of data contained in the entry.
+property.entries-compressed.requires-admin-action.synopsis=Changes to this setting take effect only for writes that occur after the change is made. It is not retroactively applied to existing data.
+property.import-queue-size.synopsis=Specifies the size (in number of entries) of the queue that is used to hold the entries read during an LDIF import.
+property.import-queue-size.requires-admin-action.synopsis=Changes do not take effect for any import that may already be in progress.
+property.import-thread-count.synopsis=Specifies the number of threads that is used for concurrent processing during an LDIF import.
+property.import-thread-count.description=This should generally be a small multiple (for example, 2x) of the number of CPUs in the system for a traditional system, or equal to the number of CPU strands for a CMT system.
+property.import-thread-count.requires-admin-action.synopsis=Changes do not take effect for any import that may already be in progress.
+property.index-entry-limit.synopsis=Specifies the maximum number of entries that is allowed to match a given index key before that particular index key is no longer maintained.
+property.index-entry-limit.description=This property is analogous to the ALL IDs threshold in the Sun Java System Directory Server. Note that this is the default limit for the backend, and it may be overridden on a per-attribute basis.A value of 0 means there is no limit.
+property.index-entry-limit.requires-admin-action.synopsis=If any index keys have already reached this limit, indexes need to be rebuilt before they are allowed to use the new limit.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.je-property.synopsis=Specifies the database and environment properties for the Berkeley DB Java Edition database serving the data for this backend.
+property.je-property.description=Any Berkeley DB Java Edition property can be specified using the following form: property-name=property-value. Refer to OpenDS documentation for further information on related properties, their implications, and range values. The definitive identification of all the property parameters is available in the example.properties file of Berkeley DB Java Edition distribution.
+property.preload-time-limit.synopsis=Specifies the length of time that the backend is allowed to spend "pre-loading" data when it is initialized.
+property.preload-time-limit.description=The pre-load process is used to pre-populate the database cache, so that it can be more quickly available when the server is processing requests. A duration of zero means there is no pre-load.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
+relation.local-db-index.user-friendly-name=Local DB Index
+relation.local-db-index.user-friendly-plural-name=Local DB Indexes
+relation.local-db-index.synopsis=Local DB Indexes are used to store information that makes it possible to locate entries very quickly when processing search operations.
+relation.local-db-index.description=Indexing is performed on a per-attribute level and different types of indexing may be performed for different kinds of attributes, based on how they are expected to be accessed during search operations.
+relation.local-db-vlv-index.user-friendly-name=Local DB VLV Index
+relation.local-db-vlv-index.user-friendly-plural-name=Local DB VLV Indexes
+relation.local-db-vlv-index.synopsis=Local DB VLV Indexes are used to store information about a specific search request that makes it possible to efficiently process them using the VLV control.
+relation.local-db-vlv-index.description=A VLV index effectively notifies the server that a virtual list view, with specific query and sort parameters, will be performed. This index also allows the server to collect and maintain the information required to make using the virtual list view faster.
diff --git a/opends/src/admin/messages/LocalDBIndexCfgDefn.properties b/opends/src/admin/messages/LocalDBIndexCfgDefn.properties
new file mode 100644
index 0000000..376b363
--- /dev/null
+++ b/opends/src/admin/messages/LocalDBIndexCfgDefn.properties
@@ -0,0 +1,18 @@
+user-friendly-name=Local DB Index
+user-friendly-plural-name=Local DB Indexes
+synopsis=Local DB Indexes are used to store information that makes it possible to locate entries very quickly when processing search operations.
+description=Indexing is performed on a per-attribute level and different types of indexing may be performed for different kinds of attributes, based on how they are expected to be accessed during search operations.
+property.attribute.synopsis=Specifies the name of the attribute for which the index is to be maintained.
+property.index-entry-limit.synopsis=Specifies the maximum number of entries that are allowed to match a given index key before that particular index key is no longer maintained.
+property.index-entry-limit.description=This is analogous to the ALL IDs threshold in the Sun Java System Directory Server. If this is specified, its value overrides the JE backend-wide configuration. For no limit, use 0 for the value.
+property.index-entry-limit.requires-admin-action.synopsis=If any index keys have already reached this limit, indexes must be rebuilt before they will be allowed to use the new limit.
+property.index-type.synopsis=Specifies the type(s) of indexing that should be performed for the associated attribute.
+property.index-type.description=For equality, presence, and substring index types, the associated attribute type must have a corresponding matching rule.
+property.index-type.requires-admin-action.synopsis=If any new index types are added for an attribute, and values for that attribute already exist in the database, the index must be rebuilt before it will be accurate.
+property.index-type.syntax.enumeration.value.approximate.synopsis=This index type is used to improve the efficiency of searches using approximate matching search filters.
+property.index-type.syntax.enumeration.value.equality.synopsis=This index type is used to improve the efficiency of searches using equality search filters.
+property.index-type.syntax.enumeration.value.ordering.synopsis=This index type is used to improve the efficiency of searches using "greater than or equal to" or "less then or equal to" search filters.
+property.index-type.syntax.enumeration.value.presence.synopsis=This index type is used to improve the efficiency of searches using the presence search filters.
+property.index-type.syntax.enumeration.value.substring.synopsis=This index type is used to improve the efficiency of searches using substring search filters.
+property.substring-length.synopsis=The length of substrings in a substring index.
+property.substring-length.requires-admin-action.synopsis=The index must be rebuilt before it will reflect the new value.
diff --git a/opends/src/admin/messages/LocalDBIndexCfgDefn_de.properties b/opends/src/admin/messages/LocalDBIndexCfgDefn_de.properties
new file mode 100644
index 0000000..376b363
--- /dev/null
+++ b/opends/src/admin/messages/LocalDBIndexCfgDefn_de.properties
@@ -0,0 +1,18 @@
+user-friendly-name=Local DB Index
+user-friendly-plural-name=Local DB Indexes
+synopsis=Local DB Indexes are used to store information that makes it possible to locate entries very quickly when processing search operations.
+description=Indexing is performed on a per-attribute level and different types of indexing may be performed for different kinds of attributes, based on how they are expected to be accessed during search operations.
+property.attribute.synopsis=Specifies the name of the attribute for which the index is to be maintained.
+property.index-entry-limit.synopsis=Specifies the maximum number of entries that are allowed to match a given index key before that particular index key is no longer maintained.
+property.index-entry-limit.description=This is analogous to the ALL IDs threshold in the Sun Java System Directory Server. If this is specified, its value overrides the JE backend-wide configuration. For no limit, use 0 for the value.
+property.index-entry-limit.requires-admin-action.synopsis=If any index keys have already reached this limit, indexes must be rebuilt before they will be allowed to use the new limit.
+property.index-type.synopsis=Specifies the type(s) of indexing that should be performed for the associated attribute.
+property.index-type.description=For equality, presence, and substring index types, the associated attribute type must have a corresponding matching rule.
+property.index-type.requires-admin-action.synopsis=If any new index types are added for an attribute, and values for that attribute already exist in the database, the index must be rebuilt before it will be accurate.
+property.index-type.syntax.enumeration.value.approximate.synopsis=This index type is used to improve the efficiency of searches using approximate matching search filters.
+property.index-type.syntax.enumeration.value.equality.synopsis=This index type is used to improve the efficiency of searches using equality search filters.
+property.index-type.syntax.enumeration.value.ordering.synopsis=This index type is used to improve the efficiency of searches using "greater than or equal to" or "less then or equal to" search filters.
+property.index-type.syntax.enumeration.value.presence.synopsis=This index type is used to improve the efficiency of searches using the presence search filters.
+property.index-type.syntax.enumeration.value.substring.synopsis=This index type is used to improve the efficiency of searches using substring search filters.
+property.substring-length.synopsis=The length of substrings in a substring index.
+property.substring-length.requires-admin-action.synopsis=The index must be rebuilt before it will reflect the new value.
diff --git a/opends/src/admin/messages/LocalDBIndexCfgDefn_es.properties b/opends/src/admin/messages/LocalDBIndexCfgDefn_es.properties
new file mode 100644
index 0000000..376b363
--- /dev/null
+++ b/opends/src/admin/messages/LocalDBIndexCfgDefn_es.properties
@@ -0,0 +1,18 @@
+user-friendly-name=Local DB Index
+user-friendly-plural-name=Local DB Indexes
+synopsis=Local DB Indexes are used to store information that makes it possible to locate entries very quickly when processing search operations.
+description=Indexing is performed on a per-attribute level and different types of indexing may be performed for different kinds of attributes, based on how they are expected to be accessed during search operations.
+property.attribute.synopsis=Specifies the name of the attribute for which the index is to be maintained.
+property.index-entry-limit.synopsis=Specifies the maximum number of entries that are allowed to match a given index key before that particular index key is no longer maintained.
+property.index-entry-limit.description=This is analogous to the ALL IDs threshold in the Sun Java System Directory Server. If this is specified, its value overrides the JE backend-wide configuration. For no limit, use 0 for the value.
+property.index-entry-limit.requires-admin-action.synopsis=If any index keys have already reached this limit, indexes must be rebuilt before they will be allowed to use the new limit.
+property.index-type.synopsis=Specifies the type(s) of indexing that should be performed for the associated attribute.
+property.index-type.description=For equality, presence, and substring index types, the associated attribute type must have a corresponding matching rule.
+property.index-type.requires-admin-action.synopsis=If any new index types are added for an attribute, and values for that attribute already exist in the database, the index must be rebuilt before it will be accurate.
+property.index-type.syntax.enumeration.value.approximate.synopsis=This index type is used to improve the efficiency of searches using approximate matching search filters.
+property.index-type.syntax.enumeration.value.equality.synopsis=This index type is used to improve the efficiency of searches using equality search filters.
+property.index-type.syntax.enumeration.value.ordering.synopsis=This index type is used to improve the efficiency of searches using "greater than or equal to" or "less then or equal to" search filters.
+property.index-type.syntax.enumeration.value.presence.synopsis=This index type is used to improve the efficiency of searches using the presence search filters.
+property.index-type.syntax.enumeration.value.substring.synopsis=This index type is used to improve the efficiency of searches using substring search filters.
+property.substring-length.synopsis=The length of substrings in a substring index.
+property.substring-length.requires-admin-action.synopsis=The index must be rebuilt before it will reflect the new value.
diff --git a/opends/src/admin/messages/LocalDBIndexCfgDefn_fr.properties b/opends/src/admin/messages/LocalDBIndexCfgDefn_fr.properties
new file mode 100644
index 0000000..376b363
--- /dev/null
+++ b/opends/src/admin/messages/LocalDBIndexCfgDefn_fr.properties
@@ -0,0 +1,18 @@
+user-friendly-name=Local DB Index
+user-friendly-plural-name=Local DB Indexes
+synopsis=Local DB Indexes are used to store information that makes it possible to locate entries very quickly when processing search operations.
+description=Indexing is performed on a per-attribute level and different types of indexing may be performed for different kinds of attributes, based on how they are expected to be accessed during search operations.
+property.attribute.synopsis=Specifies the name of the attribute for which the index is to be maintained.
+property.index-entry-limit.synopsis=Specifies the maximum number of entries that are allowed to match a given index key before that particular index key is no longer maintained.
+property.index-entry-limit.description=This is analogous to the ALL IDs threshold in the Sun Java System Directory Server. If this is specified, its value overrides the JE backend-wide configuration. For no limit, use 0 for the value.
+property.index-entry-limit.requires-admin-action.synopsis=If any index keys have already reached this limit, indexes must be rebuilt before they will be allowed to use the new limit.
+property.index-type.synopsis=Specifies the type(s) of indexing that should be performed for the associated attribute.
+property.index-type.description=For equality, presence, and substring index types, the associated attribute type must have a corresponding matching rule.
+property.index-type.requires-admin-action.synopsis=If any new index types are added for an attribute, and values for that attribute already exist in the database, the index must be rebuilt before it will be accurate.
+property.index-type.syntax.enumeration.value.approximate.synopsis=This index type is used to improve the efficiency of searches using approximate matching search filters.
+property.index-type.syntax.enumeration.value.equality.synopsis=This index type is used to improve the efficiency of searches using equality search filters.
+property.index-type.syntax.enumeration.value.ordering.synopsis=This index type is used to improve the efficiency of searches using "greater than or equal to" or "less then or equal to" search filters.
+property.index-type.syntax.enumeration.value.presence.synopsis=This index type is used to improve the efficiency of searches using the presence search filters.
+property.index-type.syntax.enumeration.value.substring.synopsis=This index type is used to improve the efficiency of searches using substring search filters.
+property.substring-length.synopsis=The length of substrings in a substring index.
+property.substring-length.requires-admin-action.synopsis=The index must be rebuilt before it will reflect the new value.
diff --git a/opends/src/admin/messages/LocalDBIndexCfgDefn_ja.properties b/opends/src/admin/messages/LocalDBIndexCfgDefn_ja.properties
new file mode 100644
index 0000000..376b363
--- /dev/null
+++ b/opends/src/admin/messages/LocalDBIndexCfgDefn_ja.properties
@@ -0,0 +1,18 @@
+user-friendly-name=Local DB Index
+user-friendly-plural-name=Local DB Indexes
+synopsis=Local DB Indexes are used to store information that makes it possible to locate entries very quickly when processing search operations.
+description=Indexing is performed on a per-attribute level and different types of indexing may be performed for different kinds of attributes, based on how they are expected to be accessed during search operations.
+property.attribute.synopsis=Specifies the name of the attribute for which the index is to be maintained.
+property.index-entry-limit.synopsis=Specifies the maximum number of entries that are allowed to match a given index key before that particular index key is no longer maintained.
+property.index-entry-limit.description=This is analogous to the ALL IDs threshold in the Sun Java System Directory Server. If this is specified, its value overrides the JE backend-wide configuration. For no limit, use 0 for the value.
+property.index-entry-limit.requires-admin-action.synopsis=If any index keys have already reached this limit, indexes must be rebuilt before they will be allowed to use the new limit.
+property.index-type.synopsis=Specifies the type(s) of indexing that should be performed for the associated attribute.
+property.index-type.description=For equality, presence, and substring index types, the associated attribute type must have a corresponding matching rule.
+property.index-type.requires-admin-action.synopsis=If any new index types are added for an attribute, and values for that attribute already exist in the database, the index must be rebuilt before it will be accurate.
+property.index-type.syntax.enumeration.value.approximate.synopsis=This index type is used to improve the efficiency of searches using approximate matching search filters.
+property.index-type.syntax.enumeration.value.equality.synopsis=This index type is used to improve the efficiency of searches using equality search filters.
+property.index-type.syntax.enumeration.value.ordering.synopsis=This index type is used to improve the efficiency of searches using "greater than or equal to" or "less then or equal to" search filters.
+property.index-type.syntax.enumeration.value.presence.synopsis=This index type is used to improve the efficiency of searches using the presence search filters.
+property.index-type.syntax.enumeration.value.substring.synopsis=This index type is used to improve the efficiency of searches using substring search filters.
+property.substring-length.synopsis=The length of substrings in a substring index.
+property.substring-length.requires-admin-action.synopsis=The index must be rebuilt before it will reflect the new value.
diff --git a/opends/src/admin/messages/LocalDBIndexCfgDefn_ko.properties b/opends/src/admin/messages/LocalDBIndexCfgDefn_ko.properties
new file mode 100644
index 0000000..376b363
--- /dev/null
+++ b/opends/src/admin/messages/LocalDBIndexCfgDefn_ko.properties
@@ -0,0 +1,18 @@
+user-friendly-name=Local DB Index
+user-friendly-plural-name=Local DB Indexes
+synopsis=Local DB Indexes are used to store information that makes it possible to locate entries very quickly when processing search operations.
+description=Indexing is performed on a per-attribute level and different types of indexing may be performed for different kinds of attributes, based on how they are expected to be accessed during search operations.
+property.attribute.synopsis=Specifies the name of the attribute for which the index is to be maintained.
+property.index-entry-limit.synopsis=Specifies the maximum number of entries that are allowed to match a given index key before that particular index key is no longer maintained.
+property.index-entry-limit.description=This is analogous to the ALL IDs threshold in the Sun Java System Directory Server. If this is specified, its value overrides the JE backend-wide configuration. For no limit, use 0 for the value.
+property.index-entry-limit.requires-admin-action.synopsis=If any index keys have already reached this limit, indexes must be rebuilt before they will be allowed to use the new limit.
+property.index-type.synopsis=Specifies the type(s) of indexing that should be performed for the associated attribute.
+property.index-type.description=For equality, presence, and substring index types, the associated attribute type must have a corresponding matching rule.
+property.index-type.requires-admin-action.synopsis=If any new index types are added for an attribute, and values for that attribute already exist in the database, the index must be rebuilt before it will be accurate.
+property.index-type.syntax.enumeration.value.approximate.synopsis=This index type is used to improve the efficiency of searches using approximate matching search filters.
+property.index-type.syntax.enumeration.value.equality.synopsis=This index type is used to improve the efficiency of searches using equality search filters.
+property.index-type.syntax.enumeration.value.ordering.synopsis=This index type is used to improve the efficiency of searches using "greater than or equal to" or "less then or equal to" search filters.
+property.index-type.syntax.enumeration.value.presence.synopsis=This index type is used to improve the efficiency of searches using the presence search filters.
+property.index-type.syntax.enumeration.value.substring.synopsis=This index type is used to improve the efficiency of searches using substring search filters.
+property.substring-length.synopsis=The length of substrings in a substring index.
+property.substring-length.requires-admin-action.synopsis=The index must be rebuilt before it will reflect the new value.
diff --git a/opends/src/admin/messages/LocalDBIndexCfgDefn_zh_CN.properties b/opends/src/admin/messages/LocalDBIndexCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..376b363
--- /dev/null
+++ b/opends/src/admin/messages/LocalDBIndexCfgDefn_zh_CN.properties
@@ -0,0 +1,18 @@
+user-friendly-name=Local DB Index
+user-friendly-plural-name=Local DB Indexes
+synopsis=Local DB Indexes are used to store information that makes it possible to locate entries very quickly when processing search operations.
+description=Indexing is performed on a per-attribute level and different types of indexing may be performed for different kinds of attributes, based on how they are expected to be accessed during search operations.
+property.attribute.synopsis=Specifies the name of the attribute for which the index is to be maintained.
+property.index-entry-limit.synopsis=Specifies the maximum number of entries that are allowed to match a given index key before that particular index key is no longer maintained.
+property.index-entry-limit.description=This is analogous to the ALL IDs threshold in the Sun Java System Directory Server. If this is specified, its value overrides the JE backend-wide configuration. For no limit, use 0 for the value.
+property.index-entry-limit.requires-admin-action.synopsis=If any index keys have already reached this limit, indexes must be rebuilt before they will be allowed to use the new limit.
+property.index-type.synopsis=Specifies the type(s) of indexing that should be performed for the associated attribute.
+property.index-type.description=For equality, presence, and substring index types, the associated attribute type must have a corresponding matching rule.
+property.index-type.requires-admin-action.synopsis=If any new index types are added for an attribute, and values for that attribute already exist in the database, the index must be rebuilt before it will be accurate.
+property.index-type.syntax.enumeration.value.approximate.synopsis=This index type is used to improve the efficiency of searches using approximate matching search filters.
+property.index-type.syntax.enumeration.value.equality.synopsis=This index type is used to improve the efficiency of searches using equality search filters.
+property.index-type.syntax.enumeration.value.ordering.synopsis=This index type is used to improve the efficiency of searches using "greater than or equal to" or "less then or equal to" search filters.
+property.index-type.syntax.enumeration.value.presence.synopsis=This index type is used to improve the efficiency of searches using the presence search filters.
+property.index-type.syntax.enumeration.value.substring.synopsis=This index type is used to improve the efficiency of searches using substring search filters.
+property.substring-length.synopsis=The length of substrings in a substring index.
+property.substring-length.requires-admin-action.synopsis=The index must be rebuilt before it will reflect the new value.
diff --git a/opends/src/admin/messages/LocalDBIndexCfgDefn_zh_TW.properties b/opends/src/admin/messages/LocalDBIndexCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..376b363
--- /dev/null
+++ b/opends/src/admin/messages/LocalDBIndexCfgDefn_zh_TW.properties
@@ -0,0 +1,18 @@
+user-friendly-name=Local DB Index
+user-friendly-plural-name=Local DB Indexes
+synopsis=Local DB Indexes are used to store information that makes it possible to locate entries very quickly when processing search operations.
+description=Indexing is performed on a per-attribute level and different types of indexing may be performed for different kinds of attributes, based on how they are expected to be accessed during search operations.
+property.attribute.synopsis=Specifies the name of the attribute for which the index is to be maintained.
+property.index-entry-limit.synopsis=Specifies the maximum number of entries that are allowed to match a given index key before that particular index key is no longer maintained.
+property.index-entry-limit.description=This is analogous to the ALL IDs threshold in the Sun Java System Directory Server. If this is specified, its value overrides the JE backend-wide configuration. For no limit, use 0 for the value.
+property.index-entry-limit.requires-admin-action.synopsis=If any index keys have already reached this limit, indexes must be rebuilt before they will be allowed to use the new limit.
+property.index-type.synopsis=Specifies the type(s) of indexing that should be performed for the associated attribute.
+property.index-type.description=For equality, presence, and substring index types, the associated attribute type must have a corresponding matching rule.
+property.index-type.requires-admin-action.synopsis=If any new index types are added for an attribute, and values for that attribute already exist in the database, the index must be rebuilt before it will be accurate.
+property.index-type.syntax.enumeration.value.approximate.synopsis=This index type is used to improve the efficiency of searches using approximate matching search filters.
+property.index-type.syntax.enumeration.value.equality.synopsis=This index type is used to improve the efficiency of searches using equality search filters.
+property.index-type.syntax.enumeration.value.ordering.synopsis=This index type is used to improve the efficiency of searches using "greater than or equal to" or "less then or equal to" search filters.
+property.index-type.syntax.enumeration.value.presence.synopsis=This index type is used to improve the efficiency of searches using the presence search filters.
+property.index-type.syntax.enumeration.value.substring.synopsis=This index type is used to improve the efficiency of searches using substring search filters.
+property.substring-length.synopsis=The length of substrings in a substring index.
+property.substring-length.requires-admin-action.synopsis=The index must be rebuilt before it will reflect the new value.
diff --git a/opends/src/admin/messages/LocalDBVLVIndexCfgDefn.properties b/opends/src/admin/messages/LocalDBVLVIndexCfgDefn.properties
new file mode 100644
index 0000000..f18fa6e
--- /dev/null
+++ b/opends/src/admin/messages/LocalDBVLVIndexCfgDefn.properties
@@ -0,0 +1,23 @@
+user-friendly-name=Local DB VLV Index
+user-friendly-plural-name=Local DB VLV Indexes
+synopsis=Local DB VLV Indexes are used to store information about a specific search request that makes it possible to efficiently process them using the VLV control.
+description=A VLV index effectively notifies the server that a virtual list view, with specific query and sort parameters, will be performed. This index also allows the server to collect and maintain the information required to make using the virtual list view faster.
+property.base-dn.synopsis=Specifies the base DN used in the search query that is being indexed.
+property.base-dn.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.filter.synopsis=Specifies the LDAP filter used in the query that is being indexed.
+property.filter.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.filter.syntax.string.pattern.synopsis=A valid LDAP search filter.
+property.max-block-size.synopsis=Specifies the number of entry IDs to store in a single sorted set before it must be split.
+property.max-block-size.requires-admin-action.synopsis=The blocks are resized lazily the next time the index is modified.
+property.name.synopsis=Specifies a unique name for this VLV index.
+property.name.requires-admin-action.synopsis=The VLV index name cannot be altered after the index is created.
+property.scope.synopsis=Specifies the LDAP scope of the query that is being indexed.
+property.scope.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.scope.syntax.enumeration.value.base-object.synopsis=Search the base object only.
+property.scope.syntax.enumeration.value.single-level.synopsis=Search the immediate children of the base object but do not include any of their descendants or the base object itself.
+property.scope.syntax.enumeration.value.subordinate-subtree.synopsis=Search the entire subtree below the base object but do not include the base object itself.
+property.scope.syntax.enumeration.value.whole-subtree.synopsis=Search the base object and the entire subtree below the base object.
+property.sort-order.synopsis=Specifies the names of the attributes that are used to sort the entries for the query being indexed.
+property.sort-order.description=Multiple attributes can be used to determine the sort order by listing the attribute names from highest to lowest precedence. Optionally, + or - can be prefixed to the attribute name to sort the attribute in ascending order or descending order respectively.
+property.sort-order.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.sort-order.syntax.string.pattern.synopsis=Valid attribute types defined in the schema, separated by a space and optionally prefixed by + or -.
diff --git a/opends/src/admin/messages/LocalDBVLVIndexCfgDefn_de.properties b/opends/src/admin/messages/LocalDBVLVIndexCfgDefn_de.properties
new file mode 100644
index 0000000..f18fa6e
--- /dev/null
+++ b/opends/src/admin/messages/LocalDBVLVIndexCfgDefn_de.properties
@@ -0,0 +1,23 @@
+user-friendly-name=Local DB VLV Index
+user-friendly-plural-name=Local DB VLV Indexes
+synopsis=Local DB VLV Indexes are used to store information about a specific search request that makes it possible to efficiently process them using the VLV control.
+description=A VLV index effectively notifies the server that a virtual list view, with specific query and sort parameters, will be performed. This index also allows the server to collect and maintain the information required to make using the virtual list view faster.
+property.base-dn.synopsis=Specifies the base DN used in the search query that is being indexed.
+property.base-dn.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.filter.synopsis=Specifies the LDAP filter used in the query that is being indexed.
+property.filter.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.filter.syntax.string.pattern.synopsis=A valid LDAP search filter.
+property.max-block-size.synopsis=Specifies the number of entry IDs to store in a single sorted set before it must be split.
+property.max-block-size.requires-admin-action.synopsis=The blocks are resized lazily the next time the index is modified.
+property.name.synopsis=Specifies a unique name for this VLV index.
+property.name.requires-admin-action.synopsis=The VLV index name cannot be altered after the index is created.
+property.scope.synopsis=Specifies the LDAP scope of the query that is being indexed.
+property.scope.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.scope.syntax.enumeration.value.base-object.synopsis=Search the base object only.
+property.scope.syntax.enumeration.value.single-level.synopsis=Search the immediate children of the base object but do not include any of their descendants or the base object itself.
+property.scope.syntax.enumeration.value.subordinate-subtree.synopsis=Search the entire subtree below the base object but do not include the base object itself.
+property.scope.syntax.enumeration.value.whole-subtree.synopsis=Search the base object and the entire subtree below the base object.
+property.sort-order.synopsis=Specifies the names of the attributes that are used to sort the entries for the query being indexed.
+property.sort-order.description=Multiple attributes can be used to determine the sort order by listing the attribute names from highest to lowest precedence. Optionally, + or - can be prefixed to the attribute name to sort the attribute in ascending order or descending order respectively.
+property.sort-order.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.sort-order.syntax.string.pattern.synopsis=Valid attribute types defined in the schema, separated by a space and optionally prefixed by + or -.
diff --git a/opends/src/admin/messages/LocalDBVLVIndexCfgDefn_es.properties b/opends/src/admin/messages/LocalDBVLVIndexCfgDefn_es.properties
new file mode 100644
index 0000000..f18fa6e
--- /dev/null
+++ b/opends/src/admin/messages/LocalDBVLVIndexCfgDefn_es.properties
@@ -0,0 +1,23 @@
+user-friendly-name=Local DB VLV Index
+user-friendly-plural-name=Local DB VLV Indexes
+synopsis=Local DB VLV Indexes are used to store information about a specific search request that makes it possible to efficiently process them using the VLV control.
+description=A VLV index effectively notifies the server that a virtual list view, with specific query and sort parameters, will be performed. This index also allows the server to collect and maintain the information required to make using the virtual list view faster.
+property.base-dn.synopsis=Specifies the base DN used in the search query that is being indexed.
+property.base-dn.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.filter.synopsis=Specifies the LDAP filter used in the query that is being indexed.
+property.filter.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.filter.syntax.string.pattern.synopsis=A valid LDAP search filter.
+property.max-block-size.synopsis=Specifies the number of entry IDs to store in a single sorted set before it must be split.
+property.max-block-size.requires-admin-action.synopsis=The blocks are resized lazily the next time the index is modified.
+property.name.synopsis=Specifies a unique name for this VLV index.
+property.name.requires-admin-action.synopsis=The VLV index name cannot be altered after the index is created.
+property.scope.synopsis=Specifies the LDAP scope of the query that is being indexed.
+property.scope.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.scope.syntax.enumeration.value.base-object.synopsis=Search the base object only.
+property.scope.syntax.enumeration.value.single-level.synopsis=Search the immediate children of the base object but do not include any of their descendants or the base object itself.
+property.scope.syntax.enumeration.value.subordinate-subtree.synopsis=Search the entire subtree below the base object but do not include the base object itself.
+property.scope.syntax.enumeration.value.whole-subtree.synopsis=Search the base object and the entire subtree below the base object.
+property.sort-order.synopsis=Specifies the names of the attributes that are used to sort the entries for the query being indexed.
+property.sort-order.description=Multiple attributes can be used to determine the sort order by listing the attribute names from highest to lowest precedence. Optionally, + or - can be prefixed to the attribute name to sort the attribute in ascending order or descending order respectively.
+property.sort-order.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.sort-order.syntax.string.pattern.synopsis=Valid attribute types defined in the schema, separated by a space and optionally prefixed by + or -.
diff --git a/opends/src/admin/messages/LocalDBVLVIndexCfgDefn_fr.properties b/opends/src/admin/messages/LocalDBVLVIndexCfgDefn_fr.properties
new file mode 100644
index 0000000..f18fa6e
--- /dev/null
+++ b/opends/src/admin/messages/LocalDBVLVIndexCfgDefn_fr.properties
@@ -0,0 +1,23 @@
+user-friendly-name=Local DB VLV Index
+user-friendly-plural-name=Local DB VLV Indexes
+synopsis=Local DB VLV Indexes are used to store information about a specific search request that makes it possible to efficiently process them using the VLV control.
+description=A VLV index effectively notifies the server that a virtual list view, with specific query and sort parameters, will be performed. This index also allows the server to collect and maintain the information required to make using the virtual list view faster.
+property.base-dn.synopsis=Specifies the base DN used in the search query that is being indexed.
+property.base-dn.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.filter.synopsis=Specifies the LDAP filter used in the query that is being indexed.
+property.filter.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.filter.syntax.string.pattern.synopsis=A valid LDAP search filter.
+property.max-block-size.synopsis=Specifies the number of entry IDs to store in a single sorted set before it must be split.
+property.max-block-size.requires-admin-action.synopsis=The blocks are resized lazily the next time the index is modified.
+property.name.synopsis=Specifies a unique name for this VLV index.
+property.name.requires-admin-action.synopsis=The VLV index name cannot be altered after the index is created.
+property.scope.synopsis=Specifies the LDAP scope of the query that is being indexed.
+property.scope.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.scope.syntax.enumeration.value.base-object.synopsis=Search the base object only.
+property.scope.syntax.enumeration.value.single-level.synopsis=Search the immediate children of the base object but do not include any of their descendants or the base object itself.
+property.scope.syntax.enumeration.value.subordinate-subtree.synopsis=Search the entire subtree below the base object but do not include the base object itself.
+property.scope.syntax.enumeration.value.whole-subtree.synopsis=Search the base object and the entire subtree below the base object.
+property.sort-order.synopsis=Specifies the names of the attributes that are used to sort the entries for the query being indexed.
+property.sort-order.description=Multiple attributes can be used to determine the sort order by listing the attribute names from highest to lowest precedence. Optionally, + or - can be prefixed to the attribute name to sort the attribute in ascending order or descending order respectively.
+property.sort-order.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.sort-order.syntax.string.pattern.synopsis=Valid attribute types defined in the schema, separated by a space and optionally prefixed by + or -.
diff --git a/opends/src/admin/messages/LocalDBVLVIndexCfgDefn_ja.properties b/opends/src/admin/messages/LocalDBVLVIndexCfgDefn_ja.properties
new file mode 100644
index 0000000..f18fa6e
--- /dev/null
+++ b/opends/src/admin/messages/LocalDBVLVIndexCfgDefn_ja.properties
@@ -0,0 +1,23 @@
+user-friendly-name=Local DB VLV Index
+user-friendly-plural-name=Local DB VLV Indexes
+synopsis=Local DB VLV Indexes are used to store information about a specific search request that makes it possible to efficiently process them using the VLV control.
+description=A VLV index effectively notifies the server that a virtual list view, with specific query and sort parameters, will be performed. This index also allows the server to collect and maintain the information required to make using the virtual list view faster.
+property.base-dn.synopsis=Specifies the base DN used in the search query that is being indexed.
+property.base-dn.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.filter.synopsis=Specifies the LDAP filter used in the query that is being indexed.
+property.filter.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.filter.syntax.string.pattern.synopsis=A valid LDAP search filter.
+property.max-block-size.synopsis=Specifies the number of entry IDs to store in a single sorted set before it must be split.
+property.max-block-size.requires-admin-action.synopsis=The blocks are resized lazily the next time the index is modified.
+property.name.synopsis=Specifies a unique name for this VLV index.
+property.name.requires-admin-action.synopsis=The VLV index name cannot be altered after the index is created.
+property.scope.synopsis=Specifies the LDAP scope of the query that is being indexed.
+property.scope.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.scope.syntax.enumeration.value.base-object.synopsis=Search the base object only.
+property.scope.syntax.enumeration.value.single-level.synopsis=Search the immediate children of the base object but do not include any of their descendants or the base object itself.
+property.scope.syntax.enumeration.value.subordinate-subtree.synopsis=Search the entire subtree below the base object but do not include the base object itself.
+property.scope.syntax.enumeration.value.whole-subtree.synopsis=Search the base object and the entire subtree below the base object.
+property.sort-order.synopsis=Specifies the names of the attributes that are used to sort the entries for the query being indexed.
+property.sort-order.description=Multiple attributes can be used to determine the sort order by listing the attribute names from highest to lowest precedence. Optionally, + or - can be prefixed to the attribute name to sort the attribute in ascending order or descending order respectively.
+property.sort-order.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.sort-order.syntax.string.pattern.synopsis=Valid attribute types defined in the schema, separated by a space and optionally prefixed by + or -.
diff --git a/opends/src/admin/messages/LocalDBVLVIndexCfgDefn_ko.properties b/opends/src/admin/messages/LocalDBVLVIndexCfgDefn_ko.properties
new file mode 100644
index 0000000..f18fa6e
--- /dev/null
+++ b/opends/src/admin/messages/LocalDBVLVIndexCfgDefn_ko.properties
@@ -0,0 +1,23 @@
+user-friendly-name=Local DB VLV Index
+user-friendly-plural-name=Local DB VLV Indexes
+synopsis=Local DB VLV Indexes are used to store information about a specific search request that makes it possible to efficiently process them using the VLV control.
+description=A VLV index effectively notifies the server that a virtual list view, with specific query and sort parameters, will be performed. This index also allows the server to collect and maintain the information required to make using the virtual list view faster.
+property.base-dn.synopsis=Specifies the base DN used in the search query that is being indexed.
+property.base-dn.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.filter.synopsis=Specifies the LDAP filter used in the query that is being indexed.
+property.filter.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.filter.syntax.string.pattern.synopsis=A valid LDAP search filter.
+property.max-block-size.synopsis=Specifies the number of entry IDs to store in a single sorted set before it must be split.
+property.max-block-size.requires-admin-action.synopsis=The blocks are resized lazily the next time the index is modified.
+property.name.synopsis=Specifies a unique name for this VLV index.
+property.name.requires-admin-action.synopsis=The VLV index name cannot be altered after the index is created.
+property.scope.synopsis=Specifies the LDAP scope of the query that is being indexed.
+property.scope.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.scope.syntax.enumeration.value.base-object.synopsis=Search the base object only.
+property.scope.syntax.enumeration.value.single-level.synopsis=Search the immediate children of the base object but do not include any of their descendants or the base object itself.
+property.scope.syntax.enumeration.value.subordinate-subtree.synopsis=Search the entire subtree below the base object but do not include the base object itself.
+property.scope.syntax.enumeration.value.whole-subtree.synopsis=Search the base object and the entire subtree below the base object.
+property.sort-order.synopsis=Specifies the names of the attributes that are used to sort the entries for the query being indexed.
+property.sort-order.description=Multiple attributes can be used to determine the sort order by listing the attribute names from highest to lowest precedence. Optionally, + or - can be prefixed to the attribute name to sort the attribute in ascending order or descending order respectively.
+property.sort-order.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.sort-order.syntax.string.pattern.synopsis=Valid attribute types defined in the schema, separated by a space and optionally prefixed by + or -.
diff --git a/opends/src/admin/messages/LocalDBVLVIndexCfgDefn_zh_CN.properties b/opends/src/admin/messages/LocalDBVLVIndexCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..f18fa6e
--- /dev/null
+++ b/opends/src/admin/messages/LocalDBVLVIndexCfgDefn_zh_CN.properties
@@ -0,0 +1,23 @@
+user-friendly-name=Local DB VLV Index
+user-friendly-plural-name=Local DB VLV Indexes
+synopsis=Local DB VLV Indexes are used to store information about a specific search request that makes it possible to efficiently process them using the VLV control.
+description=A VLV index effectively notifies the server that a virtual list view, with specific query and sort parameters, will be performed. This index also allows the server to collect and maintain the information required to make using the virtual list view faster.
+property.base-dn.synopsis=Specifies the base DN used in the search query that is being indexed.
+property.base-dn.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.filter.synopsis=Specifies the LDAP filter used in the query that is being indexed.
+property.filter.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.filter.syntax.string.pattern.synopsis=A valid LDAP search filter.
+property.max-block-size.synopsis=Specifies the number of entry IDs to store in a single sorted set before it must be split.
+property.max-block-size.requires-admin-action.synopsis=The blocks are resized lazily the next time the index is modified.
+property.name.synopsis=Specifies a unique name for this VLV index.
+property.name.requires-admin-action.synopsis=The VLV index name cannot be altered after the index is created.
+property.scope.synopsis=Specifies the LDAP scope of the query that is being indexed.
+property.scope.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.scope.syntax.enumeration.value.base-object.synopsis=Search the base object only.
+property.scope.syntax.enumeration.value.single-level.synopsis=Search the immediate children of the base object but do not include any of their descendants or the base object itself.
+property.scope.syntax.enumeration.value.subordinate-subtree.synopsis=Search the entire subtree below the base object but do not include the base object itself.
+property.scope.syntax.enumeration.value.whole-subtree.synopsis=Search the base object and the entire subtree below the base object.
+property.sort-order.synopsis=Specifies the names of the attributes that are used to sort the entries for the query being indexed.
+property.sort-order.description=Multiple attributes can be used to determine the sort order by listing the attribute names from highest to lowest precedence. Optionally, + or - can be prefixed to the attribute name to sort the attribute in ascending order or descending order respectively.
+property.sort-order.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.sort-order.syntax.string.pattern.synopsis=Valid attribute types defined in the schema, separated by a space and optionally prefixed by + or -.
diff --git a/opends/src/admin/messages/LocalDBVLVIndexCfgDefn_zh_TW.properties b/opends/src/admin/messages/LocalDBVLVIndexCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..f18fa6e
--- /dev/null
+++ b/opends/src/admin/messages/LocalDBVLVIndexCfgDefn_zh_TW.properties
@@ -0,0 +1,23 @@
+user-friendly-name=Local DB VLV Index
+user-friendly-plural-name=Local DB VLV Indexes
+synopsis=Local DB VLV Indexes are used to store information about a specific search request that makes it possible to efficiently process them using the VLV control.
+description=A VLV index effectively notifies the server that a virtual list view, with specific query and sort parameters, will be performed. This index also allows the server to collect and maintain the information required to make using the virtual list view faster.
+property.base-dn.synopsis=Specifies the base DN used in the search query that is being indexed.
+property.base-dn.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.filter.synopsis=Specifies the LDAP filter used in the query that is being indexed.
+property.filter.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.filter.syntax.string.pattern.synopsis=A valid LDAP search filter.
+property.max-block-size.synopsis=Specifies the number of entry IDs to store in a single sorted set before it must be split.
+property.max-block-size.requires-admin-action.synopsis=The blocks are resized lazily the next time the index is modified.
+property.name.synopsis=Specifies a unique name for this VLV index.
+property.name.requires-admin-action.synopsis=The VLV index name cannot be altered after the index is created.
+property.scope.synopsis=Specifies the LDAP scope of the query that is being indexed.
+property.scope.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.scope.syntax.enumeration.value.base-object.synopsis=Search the base object only.
+property.scope.syntax.enumeration.value.single-level.synopsis=Search the immediate children of the base object but do not include any of their descendants or the base object itself.
+property.scope.syntax.enumeration.value.subordinate-subtree.synopsis=Search the entire subtree below the base object but do not include the base object itself.
+property.scope.syntax.enumeration.value.whole-subtree.synopsis=Search the base object and the entire subtree below the base object.
+property.sort-order.synopsis=Specifies the names of the attributes that are used to sort the entries for the query being indexed.
+property.sort-order.description=Multiple attributes can be used to determine the sort order by listing the attribute names from highest to lowest precedence. Optionally, + or - can be prefixed to the attribute name to sort the attribute in ascending order or descending order respectively.
+property.sort-order.requires-admin-action.synopsis=The index must be rebuilt after modifying this property.
+property.sort-order.syntax.string.pattern.synopsis=Valid attribute types defined in the schema, separated by a space and optionally prefixed by + or -.
diff --git a/opends/src/admin/messages/LogPublisherCfgDefn.properties b/opends/src/admin/messages/LogPublisherCfgDefn.properties
new file mode 100644
index 0000000..0ad75c9
--- /dev/null
+++ b/opends/src/admin/messages/LogPublisherCfgDefn.properties
@@ -0,0 +1,4 @@
+user-friendly-name=Log Publisher
+user-friendly-plural-name=Log Publishers
+synopsis=Log Publishers are responsible for distributing log messages from different loggers to a destination.
+property.enabled.synopsis=Indicates whether the Log Publisher is enabled for use.
diff --git a/opends/src/admin/messages/LogPublisherCfgDefn_de.properties b/opends/src/admin/messages/LogPublisherCfgDefn_de.properties
new file mode 100644
index 0000000..0ad75c9
--- /dev/null
+++ b/opends/src/admin/messages/LogPublisherCfgDefn_de.properties
@@ -0,0 +1,4 @@
+user-friendly-name=Log Publisher
+user-friendly-plural-name=Log Publishers
+synopsis=Log Publishers are responsible for distributing log messages from different loggers to a destination.
+property.enabled.synopsis=Indicates whether the Log Publisher is enabled for use.
diff --git a/opends/src/admin/messages/LogPublisherCfgDefn_es.properties b/opends/src/admin/messages/LogPublisherCfgDefn_es.properties
new file mode 100644
index 0000000..0ad75c9
--- /dev/null
+++ b/opends/src/admin/messages/LogPublisherCfgDefn_es.properties
@@ -0,0 +1,4 @@
+user-friendly-name=Log Publisher
+user-friendly-plural-name=Log Publishers
+synopsis=Log Publishers are responsible for distributing log messages from different loggers to a destination.
+property.enabled.synopsis=Indicates whether the Log Publisher is enabled for use.
diff --git a/opends/src/admin/messages/LogPublisherCfgDefn_fr.properties b/opends/src/admin/messages/LogPublisherCfgDefn_fr.properties
new file mode 100644
index 0000000..0ad75c9
--- /dev/null
+++ b/opends/src/admin/messages/LogPublisherCfgDefn_fr.properties
@@ -0,0 +1,4 @@
+user-friendly-name=Log Publisher
+user-friendly-plural-name=Log Publishers
+synopsis=Log Publishers are responsible for distributing log messages from different loggers to a destination.
+property.enabled.synopsis=Indicates whether the Log Publisher is enabled for use.
diff --git a/opends/src/admin/messages/LogPublisherCfgDefn_ja.properties b/opends/src/admin/messages/LogPublisherCfgDefn_ja.properties
new file mode 100644
index 0000000..0ad75c9
--- /dev/null
+++ b/opends/src/admin/messages/LogPublisherCfgDefn_ja.properties
@@ -0,0 +1,4 @@
+user-friendly-name=Log Publisher
+user-friendly-plural-name=Log Publishers
+synopsis=Log Publishers are responsible for distributing log messages from different loggers to a destination.
+property.enabled.synopsis=Indicates whether the Log Publisher is enabled for use.
diff --git a/opends/src/admin/messages/LogPublisherCfgDefn_ko.properties b/opends/src/admin/messages/LogPublisherCfgDefn_ko.properties
new file mode 100644
index 0000000..0ad75c9
--- /dev/null
+++ b/opends/src/admin/messages/LogPublisherCfgDefn_ko.properties
@@ -0,0 +1,4 @@
+user-friendly-name=Log Publisher
+user-friendly-plural-name=Log Publishers
+synopsis=Log Publishers are responsible for distributing log messages from different loggers to a destination.
+property.enabled.synopsis=Indicates whether the Log Publisher is enabled for use.
diff --git a/opends/src/admin/messages/LogPublisherCfgDefn_zh_CN.properties b/opends/src/admin/messages/LogPublisherCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..0ad75c9
--- /dev/null
+++ b/opends/src/admin/messages/LogPublisherCfgDefn_zh_CN.properties
@@ -0,0 +1,4 @@
+user-friendly-name=Log Publisher
+user-friendly-plural-name=Log Publishers
+synopsis=Log Publishers are responsible for distributing log messages from different loggers to a destination.
+property.enabled.synopsis=Indicates whether the Log Publisher is enabled for use.
diff --git a/opends/src/admin/messages/LogPublisherCfgDefn_zh_TW.properties b/opends/src/admin/messages/LogPublisherCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..0ad75c9
--- /dev/null
+++ b/opends/src/admin/messages/LogPublisherCfgDefn_zh_TW.properties
@@ -0,0 +1,4 @@
+user-friendly-name=Log Publisher
+user-friendly-plural-name=Log Publishers
+synopsis=Log Publishers are responsible for distributing log messages from different loggers to a destination.
+property.enabled.synopsis=Indicates whether the Log Publisher is enabled for use.
diff --git a/opends/src/admin/messages/LogRetentionPolicyCfgDefn.properties b/opends/src/admin/messages/LogRetentionPolicyCfgDefn.properties
new file mode 100644
index 0000000..bbfbee4
--- /dev/null
+++ b/opends/src/admin/messages/LogRetentionPolicyCfgDefn.properties
@@ -0,0 +1,4 @@
+user-friendly-name=Log Retention Policy
+user-friendly-plural-name=Log Retention Policies
+synopsis=Log Retention Policies are used to specify when log files should be cleaned.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Log Retention Policy implementation.
diff --git a/opends/src/admin/messages/LogRetentionPolicyCfgDefn_de.properties b/opends/src/admin/messages/LogRetentionPolicyCfgDefn_de.properties
new file mode 100644
index 0000000..bbfbee4
--- /dev/null
+++ b/opends/src/admin/messages/LogRetentionPolicyCfgDefn_de.properties
@@ -0,0 +1,4 @@
+user-friendly-name=Log Retention Policy
+user-friendly-plural-name=Log Retention Policies
+synopsis=Log Retention Policies are used to specify when log files should be cleaned.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Log Retention Policy implementation.
diff --git a/opends/src/admin/messages/LogRetentionPolicyCfgDefn_es.properties b/opends/src/admin/messages/LogRetentionPolicyCfgDefn_es.properties
new file mode 100644
index 0000000..bbfbee4
--- /dev/null
+++ b/opends/src/admin/messages/LogRetentionPolicyCfgDefn_es.properties
@@ -0,0 +1,4 @@
+user-friendly-name=Log Retention Policy
+user-friendly-plural-name=Log Retention Policies
+synopsis=Log Retention Policies are used to specify when log files should be cleaned.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Log Retention Policy implementation.
diff --git a/opends/src/admin/messages/LogRetentionPolicyCfgDefn_fr.properties b/opends/src/admin/messages/LogRetentionPolicyCfgDefn_fr.properties
new file mode 100644
index 0000000..bbfbee4
--- /dev/null
+++ b/opends/src/admin/messages/LogRetentionPolicyCfgDefn_fr.properties
@@ -0,0 +1,4 @@
+user-friendly-name=Log Retention Policy
+user-friendly-plural-name=Log Retention Policies
+synopsis=Log Retention Policies are used to specify when log files should be cleaned.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Log Retention Policy implementation.
diff --git a/opends/src/admin/messages/LogRetentionPolicyCfgDefn_ja.properties b/opends/src/admin/messages/LogRetentionPolicyCfgDefn_ja.properties
new file mode 100644
index 0000000..bbfbee4
--- /dev/null
+++ b/opends/src/admin/messages/LogRetentionPolicyCfgDefn_ja.properties
@@ -0,0 +1,4 @@
+user-friendly-name=Log Retention Policy
+user-friendly-plural-name=Log Retention Policies
+synopsis=Log Retention Policies are used to specify when log files should be cleaned.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Log Retention Policy implementation.
diff --git a/opends/src/admin/messages/LogRetentionPolicyCfgDefn_ko.properties b/opends/src/admin/messages/LogRetentionPolicyCfgDefn_ko.properties
new file mode 100644
index 0000000..bbfbee4
--- /dev/null
+++ b/opends/src/admin/messages/LogRetentionPolicyCfgDefn_ko.properties
@@ -0,0 +1,4 @@
+user-friendly-name=Log Retention Policy
+user-friendly-plural-name=Log Retention Policies
+synopsis=Log Retention Policies are used to specify when log files should be cleaned.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Log Retention Policy implementation.
diff --git a/opends/src/admin/messages/LogRetentionPolicyCfgDefn_zh_CN.properties b/opends/src/admin/messages/LogRetentionPolicyCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..bbfbee4
--- /dev/null
+++ b/opends/src/admin/messages/LogRetentionPolicyCfgDefn_zh_CN.properties
@@ -0,0 +1,4 @@
+user-friendly-name=Log Retention Policy
+user-friendly-plural-name=Log Retention Policies
+synopsis=Log Retention Policies are used to specify when log files should be cleaned.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Log Retention Policy implementation.
diff --git a/opends/src/admin/messages/LogRetentionPolicyCfgDefn_zh_TW.properties b/opends/src/admin/messages/LogRetentionPolicyCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..bbfbee4
--- /dev/null
+++ b/opends/src/admin/messages/LogRetentionPolicyCfgDefn_zh_TW.properties
@@ -0,0 +1,4 @@
+user-friendly-name=Log Retention Policy
+user-friendly-plural-name=Log Retention Policies
+synopsis=Log Retention Policies are used to specify when log files should be cleaned.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Log Retention Policy implementation.
diff --git a/opends/src/admin/messages/LogRotationPolicyCfgDefn.properties b/opends/src/admin/messages/LogRotationPolicyCfgDefn.properties
new file mode 100644
index 0000000..d3c6d24
--- /dev/null
+++ b/opends/src/admin/messages/LogRotationPolicyCfgDefn.properties
@@ -0,0 +1,4 @@
+user-friendly-name=Log Rotation Policy
+user-friendly-plural-name=Log Rotation Policies
+synopsis=Log Rotation Policies are used to specify when log files should be rotated.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Log Rotation Policy implementation.
diff --git a/opends/src/admin/messages/LogRotationPolicyCfgDefn_de.properties b/opends/src/admin/messages/LogRotationPolicyCfgDefn_de.properties
new file mode 100644
index 0000000..d3c6d24
--- /dev/null
+++ b/opends/src/admin/messages/LogRotationPolicyCfgDefn_de.properties
@@ -0,0 +1,4 @@
+user-friendly-name=Log Rotation Policy
+user-friendly-plural-name=Log Rotation Policies
+synopsis=Log Rotation Policies are used to specify when log files should be rotated.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Log Rotation Policy implementation.
diff --git a/opends/src/admin/messages/LogRotationPolicyCfgDefn_es.properties b/opends/src/admin/messages/LogRotationPolicyCfgDefn_es.properties
new file mode 100644
index 0000000..d3c6d24
--- /dev/null
+++ b/opends/src/admin/messages/LogRotationPolicyCfgDefn_es.properties
@@ -0,0 +1,4 @@
+user-friendly-name=Log Rotation Policy
+user-friendly-plural-name=Log Rotation Policies
+synopsis=Log Rotation Policies are used to specify when log files should be rotated.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Log Rotation Policy implementation.
diff --git a/opends/src/admin/messages/LogRotationPolicyCfgDefn_fr.properties b/opends/src/admin/messages/LogRotationPolicyCfgDefn_fr.properties
new file mode 100644
index 0000000..d3c6d24
--- /dev/null
+++ b/opends/src/admin/messages/LogRotationPolicyCfgDefn_fr.properties
@@ -0,0 +1,4 @@
+user-friendly-name=Log Rotation Policy
+user-friendly-plural-name=Log Rotation Policies
+synopsis=Log Rotation Policies are used to specify when log files should be rotated.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Log Rotation Policy implementation.
diff --git a/opends/src/admin/messages/LogRotationPolicyCfgDefn_ja.properties b/opends/src/admin/messages/LogRotationPolicyCfgDefn_ja.properties
new file mode 100644
index 0000000..d3c6d24
--- /dev/null
+++ b/opends/src/admin/messages/LogRotationPolicyCfgDefn_ja.properties
@@ -0,0 +1,4 @@
+user-friendly-name=Log Rotation Policy
+user-friendly-plural-name=Log Rotation Policies
+synopsis=Log Rotation Policies are used to specify when log files should be rotated.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Log Rotation Policy implementation.
diff --git a/opends/src/admin/messages/LogRotationPolicyCfgDefn_ko.properties b/opends/src/admin/messages/LogRotationPolicyCfgDefn_ko.properties
new file mode 100644
index 0000000..d3c6d24
--- /dev/null
+++ b/opends/src/admin/messages/LogRotationPolicyCfgDefn_ko.properties
@@ -0,0 +1,4 @@
+user-friendly-name=Log Rotation Policy
+user-friendly-plural-name=Log Rotation Policies
+synopsis=Log Rotation Policies are used to specify when log files should be rotated.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Log Rotation Policy implementation.
diff --git a/opends/src/admin/messages/LogRotationPolicyCfgDefn_zh_CN.properties b/opends/src/admin/messages/LogRotationPolicyCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..d3c6d24
--- /dev/null
+++ b/opends/src/admin/messages/LogRotationPolicyCfgDefn_zh_CN.properties
@@ -0,0 +1,4 @@
+user-friendly-name=Log Rotation Policy
+user-friendly-plural-name=Log Rotation Policies
+synopsis=Log Rotation Policies are used to specify when log files should be rotated.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Log Rotation Policy implementation.
diff --git a/opends/src/admin/messages/LogRotationPolicyCfgDefn_zh_TW.properties b/opends/src/admin/messages/LogRotationPolicyCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..d3c6d24
--- /dev/null
+++ b/opends/src/admin/messages/LogRotationPolicyCfgDefn_zh_TW.properties
@@ -0,0 +1,4 @@
+user-friendly-name=Log Rotation Policy
+user-friendly-plural-name=Log Rotation Policies
+synopsis=Log Rotation Policies are used to specify when log files should be rotated.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Log Rotation Policy implementation.
diff --git a/opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn.properties b/opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn.properties
new file mode 100644
index 0000000..894e737
--- /dev/null
+++ b/opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=MD5 Password Storage Scheme
+user-friendly-plural-name=MD5 Password Storage Schemes
+synopsis=The MD5 Password Storage Scheme provides a mechanism for encoding user passwords using an unsalted form of the MD5 message digest algorithm. Because the implementation does not use any kind of salting mechanism, a given password always has the same encoded form.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "MD5". Although the MD5 digest algorithm is relatively secure, recent cryptanalysis work has identified mechanisms for generating MD5 collisions. This does not impact the security of this algorithm as it is used in OpenDS, but it is recommended that the MD5 password storage scheme only be used if client applications require it for compatibility purposes, and that a stronger digest like SSHA or SSHA256 be used for environments in which MD5 support is not required.
+property.enabled.synopsis=Indicates whether the MD5 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the MD5 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_de.properties b/opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_de.properties
new file mode 100644
index 0000000..894e737
--- /dev/null
+++ b/opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=MD5 Password Storage Scheme
+user-friendly-plural-name=MD5 Password Storage Schemes
+synopsis=The MD5 Password Storage Scheme provides a mechanism for encoding user passwords using an unsalted form of the MD5 message digest algorithm. Because the implementation does not use any kind of salting mechanism, a given password always has the same encoded form.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "MD5". Although the MD5 digest algorithm is relatively secure, recent cryptanalysis work has identified mechanisms for generating MD5 collisions. This does not impact the security of this algorithm as it is used in OpenDS, but it is recommended that the MD5 password storage scheme only be used if client applications require it for compatibility purposes, and that a stronger digest like SSHA or SSHA256 be used for environments in which MD5 support is not required.
+property.enabled.synopsis=Indicates whether the MD5 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the MD5 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_es.properties b/opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_es.properties
new file mode 100644
index 0000000..894e737
--- /dev/null
+++ b/opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=MD5 Password Storage Scheme
+user-friendly-plural-name=MD5 Password Storage Schemes
+synopsis=The MD5 Password Storage Scheme provides a mechanism for encoding user passwords using an unsalted form of the MD5 message digest algorithm. Because the implementation does not use any kind of salting mechanism, a given password always has the same encoded form.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "MD5". Although the MD5 digest algorithm is relatively secure, recent cryptanalysis work has identified mechanisms for generating MD5 collisions. This does not impact the security of this algorithm as it is used in OpenDS, but it is recommended that the MD5 password storage scheme only be used if client applications require it for compatibility purposes, and that a stronger digest like SSHA or SSHA256 be used for environments in which MD5 support is not required.
+property.enabled.synopsis=Indicates whether the MD5 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the MD5 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_fr.properties b/opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_fr.properties
new file mode 100644
index 0000000..894e737
--- /dev/null
+++ b/opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=MD5 Password Storage Scheme
+user-friendly-plural-name=MD5 Password Storage Schemes
+synopsis=The MD5 Password Storage Scheme provides a mechanism for encoding user passwords using an unsalted form of the MD5 message digest algorithm. Because the implementation does not use any kind of salting mechanism, a given password always has the same encoded form.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "MD5". Although the MD5 digest algorithm is relatively secure, recent cryptanalysis work has identified mechanisms for generating MD5 collisions. This does not impact the security of this algorithm as it is used in OpenDS, but it is recommended that the MD5 password storage scheme only be used if client applications require it for compatibility purposes, and that a stronger digest like SSHA or SSHA256 be used for environments in which MD5 support is not required.
+property.enabled.synopsis=Indicates whether the MD5 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the MD5 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_ja.properties b/opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_ja.properties
new file mode 100644
index 0000000..894e737
--- /dev/null
+++ b/opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=MD5 Password Storage Scheme
+user-friendly-plural-name=MD5 Password Storage Schemes
+synopsis=The MD5 Password Storage Scheme provides a mechanism for encoding user passwords using an unsalted form of the MD5 message digest algorithm. Because the implementation does not use any kind of salting mechanism, a given password always has the same encoded form.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "MD5". Although the MD5 digest algorithm is relatively secure, recent cryptanalysis work has identified mechanisms for generating MD5 collisions. This does not impact the security of this algorithm as it is used in OpenDS, but it is recommended that the MD5 password storage scheme only be used if client applications require it for compatibility purposes, and that a stronger digest like SSHA or SSHA256 be used for environments in which MD5 support is not required.
+property.enabled.synopsis=Indicates whether the MD5 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the MD5 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_ko.properties b/opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_ko.properties
new file mode 100644
index 0000000..894e737
--- /dev/null
+++ b/opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=MD5 Password Storage Scheme
+user-friendly-plural-name=MD5 Password Storage Schemes
+synopsis=The MD5 Password Storage Scheme provides a mechanism for encoding user passwords using an unsalted form of the MD5 message digest algorithm. Because the implementation does not use any kind of salting mechanism, a given password always has the same encoded form.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "MD5". Although the MD5 digest algorithm is relatively secure, recent cryptanalysis work has identified mechanisms for generating MD5 collisions. This does not impact the security of this algorithm as it is used in OpenDS, but it is recommended that the MD5 password storage scheme only be used if client applications require it for compatibility purposes, and that a stronger digest like SSHA or SSHA256 be used for environments in which MD5 support is not required.
+property.enabled.synopsis=Indicates whether the MD5 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the MD5 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_zh_CN.properties b/opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..894e737
--- /dev/null
+++ b/opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=MD5 Password Storage Scheme
+user-friendly-plural-name=MD5 Password Storage Schemes
+synopsis=The MD5 Password Storage Scheme provides a mechanism for encoding user passwords using an unsalted form of the MD5 message digest algorithm. Because the implementation does not use any kind of salting mechanism, a given password always has the same encoded form.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "MD5". Although the MD5 digest algorithm is relatively secure, recent cryptanalysis work has identified mechanisms for generating MD5 collisions. This does not impact the security of this algorithm as it is used in OpenDS, but it is recommended that the MD5 password storage scheme only be used if client applications require it for compatibility purposes, and that a stronger digest like SSHA or SSHA256 be used for environments in which MD5 support is not required.
+property.enabled.synopsis=Indicates whether the MD5 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the MD5 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_zh_TW.properties b/opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..894e737
--- /dev/null
+++ b/opends/src/admin/messages/MD5PasswordStorageSchemeCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=MD5 Password Storage Scheme
+user-friendly-plural-name=MD5 Password Storage Schemes
+synopsis=The MD5 Password Storage Scheme provides a mechanism for encoding user passwords using an unsalted form of the MD5 message digest algorithm. Because the implementation does not use any kind of salting mechanism, a given password always has the same encoded form.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "MD5". Although the MD5 digest algorithm is relatively secure, recent cryptanalysis work has identified mechanisms for generating MD5 collisions. This does not impact the security of this algorithm as it is used in OpenDS, but it is recommended that the MD5 password storage scheme only be used if client applications require it for compatibility purposes, and that a stronger digest like SSHA or SSHA256 be used for environments in which MD5 support is not required.
+property.enabled.synopsis=Indicates whether the MD5 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the MD5 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/MatchingRuleCfgDefn.properties b/opends/src/admin/messages/MatchingRuleCfgDefn.properties
new file mode 100644
index 0000000..4c9dbb4
--- /dev/null
+++ b/opends/src/admin/messages/MatchingRuleCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Matching Rule
+user-friendly-plural-name=Matching Rules
+synopsis=Matching Rules define a set of rules for performing matching operations against assertion values.
+description=Matching rules are frequently associated with an attribute syntax and are used to compare values according to that syntax. For example, the distinguishedNameEqualityMatch matching rule can be used to determine whether two DNs are equal and can ignore unnecessary spaces around commas and equal signs, differences in capitalization in attribute names, an so on.
+property.enabled.synopsis=Indicates whether the Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Matching Rule implementation.
diff --git a/opends/src/admin/messages/MatchingRuleCfgDefn_de.properties b/opends/src/admin/messages/MatchingRuleCfgDefn_de.properties
new file mode 100644
index 0000000..4c9dbb4
--- /dev/null
+++ b/opends/src/admin/messages/MatchingRuleCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Matching Rule
+user-friendly-plural-name=Matching Rules
+synopsis=Matching Rules define a set of rules for performing matching operations against assertion values.
+description=Matching rules are frequently associated with an attribute syntax and are used to compare values according to that syntax. For example, the distinguishedNameEqualityMatch matching rule can be used to determine whether two DNs are equal and can ignore unnecessary spaces around commas and equal signs, differences in capitalization in attribute names, an so on.
+property.enabled.synopsis=Indicates whether the Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Matching Rule implementation.
diff --git a/opends/src/admin/messages/MatchingRuleCfgDefn_es.properties b/opends/src/admin/messages/MatchingRuleCfgDefn_es.properties
new file mode 100644
index 0000000..4c9dbb4
--- /dev/null
+++ b/opends/src/admin/messages/MatchingRuleCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Matching Rule
+user-friendly-plural-name=Matching Rules
+synopsis=Matching Rules define a set of rules for performing matching operations against assertion values.
+description=Matching rules are frequently associated with an attribute syntax and are used to compare values according to that syntax. For example, the distinguishedNameEqualityMatch matching rule can be used to determine whether two DNs are equal and can ignore unnecessary spaces around commas and equal signs, differences in capitalization in attribute names, an so on.
+property.enabled.synopsis=Indicates whether the Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Matching Rule implementation.
diff --git a/opends/src/admin/messages/MatchingRuleCfgDefn_fr.properties b/opends/src/admin/messages/MatchingRuleCfgDefn_fr.properties
new file mode 100644
index 0000000..4c9dbb4
--- /dev/null
+++ b/opends/src/admin/messages/MatchingRuleCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Matching Rule
+user-friendly-plural-name=Matching Rules
+synopsis=Matching Rules define a set of rules for performing matching operations against assertion values.
+description=Matching rules are frequently associated with an attribute syntax and are used to compare values according to that syntax. For example, the distinguishedNameEqualityMatch matching rule can be used to determine whether two DNs are equal and can ignore unnecessary spaces around commas and equal signs, differences in capitalization in attribute names, an so on.
+property.enabled.synopsis=Indicates whether the Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Matching Rule implementation.
diff --git a/opends/src/admin/messages/MatchingRuleCfgDefn_ja.properties b/opends/src/admin/messages/MatchingRuleCfgDefn_ja.properties
new file mode 100644
index 0000000..4c9dbb4
--- /dev/null
+++ b/opends/src/admin/messages/MatchingRuleCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Matching Rule
+user-friendly-plural-name=Matching Rules
+synopsis=Matching Rules define a set of rules for performing matching operations against assertion values.
+description=Matching rules are frequently associated with an attribute syntax and are used to compare values according to that syntax. For example, the distinguishedNameEqualityMatch matching rule can be used to determine whether two DNs are equal and can ignore unnecessary spaces around commas and equal signs, differences in capitalization in attribute names, an so on.
+property.enabled.synopsis=Indicates whether the Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Matching Rule implementation.
diff --git a/opends/src/admin/messages/MatchingRuleCfgDefn_ko.properties b/opends/src/admin/messages/MatchingRuleCfgDefn_ko.properties
new file mode 100644
index 0000000..4c9dbb4
--- /dev/null
+++ b/opends/src/admin/messages/MatchingRuleCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Matching Rule
+user-friendly-plural-name=Matching Rules
+synopsis=Matching Rules define a set of rules for performing matching operations against assertion values.
+description=Matching rules are frequently associated with an attribute syntax and are used to compare values according to that syntax. For example, the distinguishedNameEqualityMatch matching rule can be used to determine whether two DNs are equal and can ignore unnecessary spaces around commas and equal signs, differences in capitalization in attribute names, an so on.
+property.enabled.synopsis=Indicates whether the Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Matching Rule implementation.
diff --git a/opends/src/admin/messages/MatchingRuleCfgDefn_zh_CN.properties b/opends/src/admin/messages/MatchingRuleCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..4c9dbb4
--- /dev/null
+++ b/opends/src/admin/messages/MatchingRuleCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Matching Rule
+user-friendly-plural-name=Matching Rules
+synopsis=Matching Rules define a set of rules for performing matching operations against assertion values.
+description=Matching rules are frequently associated with an attribute syntax and are used to compare values according to that syntax. For example, the distinguishedNameEqualityMatch matching rule can be used to determine whether two DNs are equal and can ignore unnecessary spaces around commas and equal signs, differences in capitalization in attribute names, an so on.
+property.enabled.synopsis=Indicates whether the Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Matching Rule implementation.
diff --git a/opends/src/admin/messages/MatchingRuleCfgDefn_zh_TW.properties b/opends/src/admin/messages/MatchingRuleCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..4c9dbb4
--- /dev/null
+++ b/opends/src/admin/messages/MatchingRuleCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Matching Rule
+user-friendly-plural-name=Matching Rules
+synopsis=Matching Rules define a set of rules for performing matching operations against assertion values.
+description=Matching rules are frequently associated with an attribute syntax and are used to compare values according to that syntax. For example, the distinguishedNameEqualityMatch matching rule can be used to determine whether two DNs are equal and can ignore unnecessary spaces around commas and equal signs, differences in capitalization in attribute names, an so on.
+property.enabled.synopsis=Indicates whether the Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Matching Rule implementation.
diff --git a/opends/src/admin/messages/MemberVirtualAttributeCfgDefn.properties b/opends/src/admin/messages/MemberVirtualAttributeCfgDefn.properties
new file mode 100644
index 0000000..f6585f4
--- /dev/null
+++ b/opends/src/admin/messages/MemberVirtualAttributeCfgDefn.properties
@@ -0,0 +1,22 @@
+user-friendly-name=Member Virtual Attribute
+user-friendly-plural-name=User Defined Virtual Attributes
+synopsis=The Member Virtual Attribute generates a member or uniqueMember attribute whose values are the DNs of the members of a specified virtual static group.
+description=This component is used to implement virtual static group functionality, in which it is possible to create an entry that looks like a static group but obtains all of its membership from a dynamic group (or some other type of group, including another static group). This implementation is most efficient when attempting to determine whether a given user is a member of a group (for example, with a filter like "(uniqueMember=uid=john.doe,ou=People,dc=example,dc=com)") when the search does not actually return the membership attribute. Although it works to generate the entire set of values for the member or uniqueMember attribute, this can be an expensive operation for a large group.
+property.allow-retrieving-membership.synopsis=Indicates whether to handle requests that request all values for the virtual attribute.
+property.allow-retrieving-membership.description=This operation can be very expensive in some cases and is not consistent with the primary function of virtual static groups, which is to make it possible to use static group idioms to determine whether a given user is a member. If this attribute is set to false, attempts to retrieve the entire set of values receive an empty set, and only attempts to determine whether the attribute has a specific value or set of values (which is the primary anticipated use for virtual static groups) are handled properly.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Member Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/MemberVirtualAttributeCfgDefn_de.properties b/opends/src/admin/messages/MemberVirtualAttributeCfgDefn_de.properties
new file mode 100644
index 0000000..f6585f4
--- /dev/null
+++ b/opends/src/admin/messages/MemberVirtualAttributeCfgDefn_de.properties
@@ -0,0 +1,22 @@
+user-friendly-name=Member Virtual Attribute
+user-friendly-plural-name=User Defined Virtual Attributes
+synopsis=The Member Virtual Attribute generates a member or uniqueMember attribute whose values are the DNs of the members of a specified virtual static group.
+description=This component is used to implement virtual static group functionality, in which it is possible to create an entry that looks like a static group but obtains all of its membership from a dynamic group (or some other type of group, including another static group). This implementation is most efficient when attempting to determine whether a given user is a member of a group (for example, with a filter like "(uniqueMember=uid=john.doe,ou=People,dc=example,dc=com)") when the search does not actually return the membership attribute. Although it works to generate the entire set of values for the member or uniqueMember attribute, this can be an expensive operation for a large group.
+property.allow-retrieving-membership.synopsis=Indicates whether to handle requests that request all values for the virtual attribute.
+property.allow-retrieving-membership.description=This operation can be very expensive in some cases and is not consistent with the primary function of virtual static groups, which is to make it possible to use static group idioms to determine whether a given user is a member. If this attribute is set to false, attempts to retrieve the entire set of values receive an empty set, and only attempts to determine whether the attribute has a specific value or set of values (which is the primary anticipated use for virtual static groups) are handled properly.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Member Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/MemberVirtualAttributeCfgDefn_es.properties b/opends/src/admin/messages/MemberVirtualAttributeCfgDefn_es.properties
new file mode 100644
index 0000000..f6585f4
--- /dev/null
+++ b/opends/src/admin/messages/MemberVirtualAttributeCfgDefn_es.properties
@@ -0,0 +1,22 @@
+user-friendly-name=Member Virtual Attribute
+user-friendly-plural-name=User Defined Virtual Attributes
+synopsis=The Member Virtual Attribute generates a member or uniqueMember attribute whose values are the DNs of the members of a specified virtual static group.
+description=This component is used to implement virtual static group functionality, in which it is possible to create an entry that looks like a static group but obtains all of its membership from a dynamic group (or some other type of group, including another static group). This implementation is most efficient when attempting to determine whether a given user is a member of a group (for example, with a filter like "(uniqueMember=uid=john.doe,ou=People,dc=example,dc=com)") when the search does not actually return the membership attribute. Although it works to generate the entire set of values for the member or uniqueMember attribute, this can be an expensive operation for a large group.
+property.allow-retrieving-membership.synopsis=Indicates whether to handle requests that request all values for the virtual attribute.
+property.allow-retrieving-membership.description=This operation can be very expensive in some cases and is not consistent with the primary function of virtual static groups, which is to make it possible to use static group idioms to determine whether a given user is a member. If this attribute is set to false, attempts to retrieve the entire set of values receive an empty set, and only attempts to determine whether the attribute has a specific value or set of values (which is the primary anticipated use for virtual static groups) are handled properly.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Member Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/MemberVirtualAttributeCfgDefn_fr.properties b/opends/src/admin/messages/MemberVirtualAttributeCfgDefn_fr.properties
new file mode 100644
index 0000000..f6585f4
--- /dev/null
+++ b/opends/src/admin/messages/MemberVirtualAttributeCfgDefn_fr.properties
@@ -0,0 +1,22 @@
+user-friendly-name=Member Virtual Attribute
+user-friendly-plural-name=User Defined Virtual Attributes
+synopsis=The Member Virtual Attribute generates a member or uniqueMember attribute whose values are the DNs of the members of a specified virtual static group.
+description=This component is used to implement virtual static group functionality, in which it is possible to create an entry that looks like a static group but obtains all of its membership from a dynamic group (or some other type of group, including another static group). This implementation is most efficient when attempting to determine whether a given user is a member of a group (for example, with a filter like "(uniqueMember=uid=john.doe,ou=People,dc=example,dc=com)") when the search does not actually return the membership attribute. Although it works to generate the entire set of values for the member or uniqueMember attribute, this can be an expensive operation for a large group.
+property.allow-retrieving-membership.synopsis=Indicates whether to handle requests that request all values for the virtual attribute.
+property.allow-retrieving-membership.description=This operation can be very expensive in some cases and is not consistent with the primary function of virtual static groups, which is to make it possible to use static group idioms to determine whether a given user is a member. If this attribute is set to false, attempts to retrieve the entire set of values receive an empty set, and only attempts to determine whether the attribute has a specific value or set of values (which is the primary anticipated use for virtual static groups) are handled properly.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Member Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/MemberVirtualAttributeCfgDefn_ja.properties b/opends/src/admin/messages/MemberVirtualAttributeCfgDefn_ja.properties
new file mode 100644
index 0000000..f6585f4
--- /dev/null
+++ b/opends/src/admin/messages/MemberVirtualAttributeCfgDefn_ja.properties
@@ -0,0 +1,22 @@
+user-friendly-name=Member Virtual Attribute
+user-friendly-plural-name=User Defined Virtual Attributes
+synopsis=The Member Virtual Attribute generates a member or uniqueMember attribute whose values are the DNs of the members of a specified virtual static group.
+description=This component is used to implement virtual static group functionality, in which it is possible to create an entry that looks like a static group but obtains all of its membership from a dynamic group (or some other type of group, including another static group). This implementation is most efficient when attempting to determine whether a given user is a member of a group (for example, with a filter like "(uniqueMember=uid=john.doe,ou=People,dc=example,dc=com)") when the search does not actually return the membership attribute. Although it works to generate the entire set of values for the member or uniqueMember attribute, this can be an expensive operation for a large group.
+property.allow-retrieving-membership.synopsis=Indicates whether to handle requests that request all values for the virtual attribute.
+property.allow-retrieving-membership.description=This operation can be very expensive in some cases and is not consistent with the primary function of virtual static groups, which is to make it possible to use static group idioms to determine whether a given user is a member. If this attribute is set to false, attempts to retrieve the entire set of values receive an empty set, and only attempts to determine whether the attribute has a specific value or set of values (which is the primary anticipated use for virtual static groups) are handled properly.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Member Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/MemberVirtualAttributeCfgDefn_ko.properties b/opends/src/admin/messages/MemberVirtualAttributeCfgDefn_ko.properties
new file mode 100644
index 0000000..f6585f4
--- /dev/null
+++ b/opends/src/admin/messages/MemberVirtualAttributeCfgDefn_ko.properties
@@ -0,0 +1,22 @@
+user-friendly-name=Member Virtual Attribute
+user-friendly-plural-name=User Defined Virtual Attributes
+synopsis=The Member Virtual Attribute generates a member or uniqueMember attribute whose values are the DNs of the members of a specified virtual static group.
+description=This component is used to implement virtual static group functionality, in which it is possible to create an entry that looks like a static group but obtains all of its membership from a dynamic group (or some other type of group, including another static group). This implementation is most efficient when attempting to determine whether a given user is a member of a group (for example, with a filter like "(uniqueMember=uid=john.doe,ou=People,dc=example,dc=com)") when the search does not actually return the membership attribute. Although it works to generate the entire set of values for the member or uniqueMember attribute, this can be an expensive operation for a large group.
+property.allow-retrieving-membership.synopsis=Indicates whether to handle requests that request all values for the virtual attribute.
+property.allow-retrieving-membership.description=This operation can be very expensive in some cases and is not consistent with the primary function of virtual static groups, which is to make it possible to use static group idioms to determine whether a given user is a member. If this attribute is set to false, attempts to retrieve the entire set of values receive an empty set, and only attempts to determine whether the attribute has a specific value or set of values (which is the primary anticipated use for virtual static groups) are handled properly.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Member Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/MemberVirtualAttributeCfgDefn_zh_CN.properties b/opends/src/admin/messages/MemberVirtualAttributeCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..f6585f4
--- /dev/null
+++ b/opends/src/admin/messages/MemberVirtualAttributeCfgDefn_zh_CN.properties
@@ -0,0 +1,22 @@
+user-friendly-name=Member Virtual Attribute
+user-friendly-plural-name=User Defined Virtual Attributes
+synopsis=The Member Virtual Attribute generates a member or uniqueMember attribute whose values are the DNs of the members of a specified virtual static group.
+description=This component is used to implement virtual static group functionality, in which it is possible to create an entry that looks like a static group but obtains all of its membership from a dynamic group (or some other type of group, including another static group). This implementation is most efficient when attempting to determine whether a given user is a member of a group (for example, with a filter like "(uniqueMember=uid=john.doe,ou=People,dc=example,dc=com)") when the search does not actually return the membership attribute. Although it works to generate the entire set of values for the member or uniqueMember attribute, this can be an expensive operation for a large group.
+property.allow-retrieving-membership.synopsis=Indicates whether to handle requests that request all values for the virtual attribute.
+property.allow-retrieving-membership.description=This operation can be very expensive in some cases and is not consistent with the primary function of virtual static groups, which is to make it possible to use static group idioms to determine whether a given user is a member. If this attribute is set to false, attempts to retrieve the entire set of values receive an empty set, and only attempts to determine whether the attribute has a specific value or set of values (which is the primary anticipated use for virtual static groups) are handled properly.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Member Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/MemberVirtualAttributeCfgDefn_zh_TW.properties b/opends/src/admin/messages/MemberVirtualAttributeCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..f6585f4
--- /dev/null
+++ b/opends/src/admin/messages/MemberVirtualAttributeCfgDefn_zh_TW.properties
@@ -0,0 +1,22 @@
+user-friendly-name=Member Virtual Attribute
+user-friendly-plural-name=User Defined Virtual Attributes
+synopsis=The Member Virtual Attribute generates a member or uniqueMember attribute whose values are the DNs of the members of a specified virtual static group.
+description=This component is used to implement virtual static group functionality, in which it is possible to create an entry that looks like a static group but obtains all of its membership from a dynamic group (or some other type of group, including another static group). This implementation is most efficient when attempting to determine whether a given user is a member of a group (for example, with a filter like "(uniqueMember=uid=john.doe,ou=People,dc=example,dc=com)") when the search does not actually return the membership attribute. Although it works to generate the entire set of values for the member or uniqueMember attribute, this can be an expensive operation for a large group.
+property.allow-retrieving-membership.synopsis=Indicates whether to handle requests that request all values for the virtual attribute.
+property.allow-retrieving-membership.description=This operation can be very expensive in some cases and is not consistent with the primary function of virtual static groups, which is to make it possible to use static group idioms to determine whether a given user is a member. If this attribute is set to false, attempts to retrieve the entire set of values receive an empty set, and only attempts to determine whether the attribute has a specific value or set of values (which is the primary anticipated use for virtual static groups) are handled properly.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Member Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/MemoryBackendCfgDefn.properties b/opends/src/admin/messages/MemoryBackendCfgDefn.properties
new file mode 100644
index 0000000..c4ab102
--- /dev/null
+++ b/opends/src/admin/messages/MemoryBackendCfgDefn.properties
@@ -0,0 +1,16 @@
+user-friendly-name=Memory Backend
+user-friendly-plural-name=Memory Backends
+synopsis=The Memory Backend provides a Directory Server backend implementation that stores entries in memory.
+description=There is no persistence of any kind, and the backend contents are cleared whenever the backend is brought online or offline and when the server is restarted.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/MemoryBackendCfgDefn_de.properties b/opends/src/admin/messages/MemoryBackendCfgDefn_de.properties
new file mode 100644
index 0000000..c4ab102
--- /dev/null
+++ b/opends/src/admin/messages/MemoryBackendCfgDefn_de.properties
@@ -0,0 +1,16 @@
+user-friendly-name=Memory Backend
+user-friendly-plural-name=Memory Backends
+synopsis=The Memory Backend provides a Directory Server backend implementation that stores entries in memory.
+description=There is no persistence of any kind, and the backend contents are cleared whenever the backend is brought online or offline and when the server is restarted.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/MemoryBackendCfgDefn_es.properties b/opends/src/admin/messages/MemoryBackendCfgDefn_es.properties
new file mode 100644
index 0000000..c4ab102
--- /dev/null
+++ b/opends/src/admin/messages/MemoryBackendCfgDefn_es.properties
@@ -0,0 +1,16 @@
+user-friendly-name=Memory Backend
+user-friendly-plural-name=Memory Backends
+synopsis=The Memory Backend provides a Directory Server backend implementation that stores entries in memory.
+description=There is no persistence of any kind, and the backend contents are cleared whenever the backend is brought online or offline and when the server is restarted.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/MemoryBackendCfgDefn_fr.properties b/opends/src/admin/messages/MemoryBackendCfgDefn_fr.properties
new file mode 100644
index 0000000..c4ab102
--- /dev/null
+++ b/opends/src/admin/messages/MemoryBackendCfgDefn_fr.properties
@@ -0,0 +1,16 @@
+user-friendly-name=Memory Backend
+user-friendly-plural-name=Memory Backends
+synopsis=The Memory Backend provides a Directory Server backend implementation that stores entries in memory.
+description=There is no persistence of any kind, and the backend contents are cleared whenever the backend is brought online or offline and when the server is restarted.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/MemoryBackendCfgDefn_ja.properties b/opends/src/admin/messages/MemoryBackendCfgDefn_ja.properties
new file mode 100644
index 0000000..c4ab102
--- /dev/null
+++ b/opends/src/admin/messages/MemoryBackendCfgDefn_ja.properties
@@ -0,0 +1,16 @@
+user-friendly-name=Memory Backend
+user-friendly-plural-name=Memory Backends
+synopsis=The Memory Backend provides a Directory Server backend implementation that stores entries in memory.
+description=There is no persistence of any kind, and the backend contents are cleared whenever the backend is brought online or offline and when the server is restarted.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/MemoryBackendCfgDefn_ko.properties b/opends/src/admin/messages/MemoryBackendCfgDefn_ko.properties
new file mode 100644
index 0000000..c4ab102
--- /dev/null
+++ b/opends/src/admin/messages/MemoryBackendCfgDefn_ko.properties
@@ -0,0 +1,16 @@
+user-friendly-name=Memory Backend
+user-friendly-plural-name=Memory Backends
+synopsis=The Memory Backend provides a Directory Server backend implementation that stores entries in memory.
+description=There is no persistence of any kind, and the backend contents are cleared whenever the backend is brought online or offline and when the server is restarted.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/MemoryBackendCfgDefn_zh_CN.properties b/opends/src/admin/messages/MemoryBackendCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..c4ab102
--- /dev/null
+++ b/opends/src/admin/messages/MemoryBackendCfgDefn_zh_CN.properties
@@ -0,0 +1,16 @@
+user-friendly-name=Memory Backend
+user-friendly-plural-name=Memory Backends
+synopsis=The Memory Backend provides a Directory Server backend implementation that stores entries in memory.
+description=There is no persistence of any kind, and the backend contents are cleared whenever the backend is brought online or offline and when the server is restarted.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/MemoryBackendCfgDefn_zh_TW.properties b/opends/src/admin/messages/MemoryBackendCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..c4ab102
--- /dev/null
+++ b/opends/src/admin/messages/MemoryBackendCfgDefn_zh_TW.properties
@@ -0,0 +1,16 @@
+user-friendly-name=Memory Backend
+user-friendly-plural-name=Memory Backends
+synopsis=The Memory Backend provides a Directory Server backend implementation that stores entries in memory.
+description=There is no persistence of any kind, and the backend contents are cleared whenever the backend is brought online or offline and when the server is restarted.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn.properties b/opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn.properties
new file mode 100644
index 0000000..a54b712
--- /dev/null
+++ b/opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Memory Usage Monitor Provider
+user-friendly-plural-name=Memory Usage Monitor Providers
+synopsis=The Memory Usage Monitor Provider can be used to publish information about memory consumption and garbage collection activity in the JVM.
+property.enabled.synopsis=Indicates whether the Memory Usage Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Memory Usage Monitor Provider implementation.
diff --git a/opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_de.properties b/opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_de.properties
new file mode 100644
index 0000000..a54b712
--- /dev/null
+++ b/opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_de.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Memory Usage Monitor Provider
+user-friendly-plural-name=Memory Usage Monitor Providers
+synopsis=The Memory Usage Monitor Provider can be used to publish information about memory consumption and garbage collection activity in the JVM.
+property.enabled.synopsis=Indicates whether the Memory Usage Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Memory Usage Monitor Provider implementation.
diff --git a/opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_es.properties b/opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_es.properties
new file mode 100644
index 0000000..a54b712
--- /dev/null
+++ b/opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_es.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Memory Usage Monitor Provider
+user-friendly-plural-name=Memory Usage Monitor Providers
+synopsis=The Memory Usage Monitor Provider can be used to publish information about memory consumption and garbage collection activity in the JVM.
+property.enabled.synopsis=Indicates whether the Memory Usage Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Memory Usage Monitor Provider implementation.
diff --git a/opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_fr.properties b/opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_fr.properties
new file mode 100644
index 0000000..a54b712
--- /dev/null
+++ b/opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_fr.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Memory Usage Monitor Provider
+user-friendly-plural-name=Memory Usage Monitor Providers
+synopsis=The Memory Usage Monitor Provider can be used to publish information about memory consumption and garbage collection activity in the JVM.
+property.enabled.synopsis=Indicates whether the Memory Usage Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Memory Usage Monitor Provider implementation.
diff --git a/opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_ja.properties b/opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_ja.properties
new file mode 100644
index 0000000..a54b712
--- /dev/null
+++ b/opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_ja.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Memory Usage Monitor Provider
+user-friendly-plural-name=Memory Usage Monitor Providers
+synopsis=The Memory Usage Monitor Provider can be used to publish information about memory consumption and garbage collection activity in the JVM.
+property.enabled.synopsis=Indicates whether the Memory Usage Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Memory Usage Monitor Provider implementation.
diff --git a/opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_ko.properties b/opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_ko.properties
new file mode 100644
index 0000000..a54b712
--- /dev/null
+++ b/opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_ko.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Memory Usage Monitor Provider
+user-friendly-plural-name=Memory Usage Monitor Providers
+synopsis=The Memory Usage Monitor Provider can be used to publish information about memory consumption and garbage collection activity in the JVM.
+property.enabled.synopsis=Indicates whether the Memory Usage Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Memory Usage Monitor Provider implementation.
diff --git a/opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_zh_CN.properties b/opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..a54b712
--- /dev/null
+++ b/opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_zh_CN.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Memory Usage Monitor Provider
+user-friendly-plural-name=Memory Usage Monitor Providers
+synopsis=The Memory Usage Monitor Provider can be used to publish information about memory consumption and garbage collection activity in the JVM.
+property.enabled.synopsis=Indicates whether the Memory Usage Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Memory Usage Monitor Provider implementation.
diff --git a/opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_zh_TW.properties b/opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..a54b712
--- /dev/null
+++ b/opends/src/admin/messages/MemoryUsageMonitorProviderCfgDefn_zh_TW.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Memory Usage Monitor Provider
+user-friendly-plural-name=Memory Usage Monitor Providers
+synopsis=The Memory Usage Monitor Provider can be used to publish information about memory consumption and garbage collection activity in the JVM.
+property.enabled.synopsis=Indicates whether the Memory Usage Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Memory Usage Monitor Provider implementation.
diff --git a/opends/src/admin/messages/MonitorBackendCfgDefn.properties b/opends/src/admin/messages/MonitorBackendCfgDefn.properties
new file mode 100644
index 0000000..6f5bc9c
--- /dev/null
+++ b/opends/src/admin/messages/MonitorBackendCfgDefn.properties
@@ -0,0 +1,15 @@
+user-friendly-name=Monitor Backend
+user-friendly-plural-name=Monitor Backends
+synopsis=The Monitor Backend allows clients to access the information made available by Directory Server monitor providers.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/MonitorBackendCfgDefn_de.properties b/opends/src/admin/messages/MonitorBackendCfgDefn_de.properties
new file mode 100644
index 0000000..6f5bc9c
--- /dev/null
+++ b/opends/src/admin/messages/MonitorBackendCfgDefn_de.properties
@@ -0,0 +1,15 @@
+user-friendly-name=Monitor Backend
+user-friendly-plural-name=Monitor Backends
+synopsis=The Monitor Backend allows clients to access the information made available by Directory Server monitor providers.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/MonitorBackendCfgDefn_es.properties b/opends/src/admin/messages/MonitorBackendCfgDefn_es.properties
new file mode 100644
index 0000000..6f5bc9c
--- /dev/null
+++ b/opends/src/admin/messages/MonitorBackendCfgDefn_es.properties
@@ -0,0 +1,15 @@
+user-friendly-name=Monitor Backend
+user-friendly-plural-name=Monitor Backends
+synopsis=The Monitor Backend allows clients to access the information made available by Directory Server monitor providers.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/MonitorBackendCfgDefn_fr.properties b/opends/src/admin/messages/MonitorBackendCfgDefn_fr.properties
new file mode 100644
index 0000000..6f5bc9c
--- /dev/null
+++ b/opends/src/admin/messages/MonitorBackendCfgDefn_fr.properties
@@ -0,0 +1,15 @@
+user-friendly-name=Monitor Backend
+user-friendly-plural-name=Monitor Backends
+synopsis=The Monitor Backend allows clients to access the information made available by Directory Server monitor providers.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/MonitorBackendCfgDefn_ja.properties b/opends/src/admin/messages/MonitorBackendCfgDefn_ja.properties
new file mode 100644
index 0000000..6f5bc9c
--- /dev/null
+++ b/opends/src/admin/messages/MonitorBackendCfgDefn_ja.properties
@@ -0,0 +1,15 @@
+user-friendly-name=Monitor Backend
+user-friendly-plural-name=Monitor Backends
+synopsis=The Monitor Backend allows clients to access the information made available by Directory Server monitor providers.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/MonitorBackendCfgDefn_ko.properties b/opends/src/admin/messages/MonitorBackendCfgDefn_ko.properties
new file mode 100644
index 0000000..6f5bc9c
--- /dev/null
+++ b/opends/src/admin/messages/MonitorBackendCfgDefn_ko.properties
@@ -0,0 +1,15 @@
+user-friendly-name=Monitor Backend
+user-friendly-plural-name=Monitor Backends
+synopsis=The Monitor Backend allows clients to access the information made available by Directory Server monitor providers.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/MonitorBackendCfgDefn_zh_CN.properties b/opends/src/admin/messages/MonitorBackendCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..6f5bc9c
--- /dev/null
+++ b/opends/src/admin/messages/MonitorBackendCfgDefn_zh_CN.properties
@@ -0,0 +1,15 @@
+user-friendly-name=Monitor Backend
+user-friendly-plural-name=Monitor Backends
+synopsis=The Monitor Backend allows clients to access the information made available by Directory Server monitor providers.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/MonitorBackendCfgDefn_zh_TW.properties b/opends/src/admin/messages/MonitorBackendCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..6f5bc9c
--- /dev/null
+++ b/opends/src/admin/messages/MonitorBackendCfgDefn_zh_TW.properties
@@ -0,0 +1,15 @@
+user-friendly-name=Monitor Backend
+user-friendly-plural-name=Monitor Backends
+synopsis=The Monitor Backend allows clients to access the information made available by Directory Server monitor providers.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/MonitorProviderCfgDefn.properties b/opends/src/admin/messages/MonitorProviderCfgDefn.properties
new file mode 100644
index 0000000..13b7e18
--- /dev/null
+++ b/opends/src/admin/messages/MonitorProviderCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Monitor Provider
+user-friendly-plural-name=Monitor Providers
+synopsis=Monitor Providers can be used to provide information about the state of the server or one of its components.
+description=This information is useful for monitoring or troubleshooting.
+property.enabled.synopsis=Indicates whether the Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Monitor Provider implementation.
diff --git a/opends/src/admin/messages/MonitorProviderCfgDefn_de.properties b/opends/src/admin/messages/MonitorProviderCfgDefn_de.properties
new file mode 100644
index 0000000..13b7e18
--- /dev/null
+++ b/opends/src/admin/messages/MonitorProviderCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Monitor Provider
+user-friendly-plural-name=Monitor Providers
+synopsis=Monitor Providers can be used to provide information about the state of the server or one of its components.
+description=This information is useful for monitoring or troubleshooting.
+property.enabled.synopsis=Indicates whether the Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Monitor Provider implementation.
diff --git a/opends/src/admin/messages/MonitorProviderCfgDefn_es.properties b/opends/src/admin/messages/MonitorProviderCfgDefn_es.properties
new file mode 100644
index 0000000..13b7e18
--- /dev/null
+++ b/opends/src/admin/messages/MonitorProviderCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Monitor Provider
+user-friendly-plural-name=Monitor Providers
+synopsis=Monitor Providers can be used to provide information about the state of the server or one of its components.
+description=This information is useful for monitoring or troubleshooting.
+property.enabled.synopsis=Indicates whether the Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Monitor Provider implementation.
diff --git a/opends/src/admin/messages/MonitorProviderCfgDefn_fr.properties b/opends/src/admin/messages/MonitorProviderCfgDefn_fr.properties
new file mode 100644
index 0000000..13b7e18
--- /dev/null
+++ b/opends/src/admin/messages/MonitorProviderCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Monitor Provider
+user-friendly-plural-name=Monitor Providers
+synopsis=Monitor Providers can be used to provide information about the state of the server or one of its components.
+description=This information is useful for monitoring or troubleshooting.
+property.enabled.synopsis=Indicates whether the Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Monitor Provider implementation.
diff --git a/opends/src/admin/messages/MonitorProviderCfgDefn_ja.properties b/opends/src/admin/messages/MonitorProviderCfgDefn_ja.properties
new file mode 100644
index 0000000..13b7e18
--- /dev/null
+++ b/opends/src/admin/messages/MonitorProviderCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Monitor Provider
+user-friendly-plural-name=Monitor Providers
+synopsis=Monitor Providers can be used to provide information about the state of the server or one of its components.
+description=This information is useful for monitoring or troubleshooting.
+property.enabled.synopsis=Indicates whether the Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Monitor Provider implementation.
diff --git a/opends/src/admin/messages/MonitorProviderCfgDefn_ko.properties b/opends/src/admin/messages/MonitorProviderCfgDefn_ko.properties
new file mode 100644
index 0000000..13b7e18
--- /dev/null
+++ b/opends/src/admin/messages/MonitorProviderCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Monitor Provider
+user-friendly-plural-name=Monitor Providers
+synopsis=Monitor Providers can be used to provide information about the state of the server or one of its components.
+description=This information is useful for monitoring or troubleshooting.
+property.enabled.synopsis=Indicates whether the Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Monitor Provider implementation.
diff --git a/opends/src/admin/messages/MonitorProviderCfgDefn_zh_CN.properties b/opends/src/admin/messages/MonitorProviderCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..13b7e18
--- /dev/null
+++ b/opends/src/admin/messages/MonitorProviderCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Monitor Provider
+user-friendly-plural-name=Monitor Providers
+synopsis=Monitor Providers can be used to provide information about the state of the server or one of its components.
+description=This information is useful for monitoring or troubleshooting.
+property.enabled.synopsis=Indicates whether the Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Monitor Provider implementation.
diff --git a/opends/src/admin/messages/MonitorProviderCfgDefn_zh_TW.properties b/opends/src/admin/messages/MonitorProviderCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..13b7e18
--- /dev/null
+++ b/opends/src/admin/messages/MonitorProviderCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Monitor Provider
+user-friendly-plural-name=Monitor Providers
+synopsis=Monitor Providers can be used to provide information about the state of the server or one of its components.
+description=This information is useful for monitoring or troubleshooting.
+property.enabled.synopsis=Indicates whether the Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Monitor Provider implementation.
diff --git a/opends/src/admin/messages/NetworkGroupCfgDefn.properties b/opends/src/admin/messages/NetworkGroupCfgDefn.properties
new file mode 100644
index 0000000..b2371ec
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupCfgDefn.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Network Group
+user-friendly-plural-name=Network Groups
+synopsis=The Network Group is used to classify incoming connections and route requests to workflows.
+property.enabled.synopsis=Indicates whether the Network Group is enabled for use in the server.
+property.enabled.description=If a network group is not enabled, its workflows will not be accessible when processing operations.
+property.network-group-id.synopsis=Specifies the name that is used to identify the associated Network Group .
+property.network-group-id.description=The name must be unique among all the Network Groups in the server.
+property.priority.synopsis=Specifies the order in which the network groups are evaluated.
+property.priority.description=A client connection is first compared against network group with priority 1. If the client connection does not match the network group criteria, the client connection is compared against network group with priority 2 etc...
+property.workflow.synopsis=Identifies the workflows in the network group.
+property.workflow.syntax.aggregation.constraint-synopsis=The referenced workflows must be enabled.
+relation.network-group-criteria.user-friendly-name=Network Group Criteria
+relation.network-group-criteria.synopsis=Specifies the set of criteria associated to this network group.
+relation.network-group-criteria.description=A client connection can belong to a Network Group Criteria only if it matches all the criteria defined for this Network Group Criteria.
+relation.network-group-request-filtering-policy.user-friendly-name=Network Group Request Filtering Policy
+relation.network-group-request-filtering-policy.synopsis=Specifies the request filtering policy enforced by this Network Group Request Filtering Policy.
+relation.network-group-request-filtering-policy.description=All client connections belonging to a Network Group Request Filtering Policy must comply with the request filtering policy.
+relation.network-group-resource-limits.user-friendly-name=Network Group Resource Limits
+relation.network-group-resource-limits.synopsis=Specifies the set of resource limits enforced by this Network Group Resource Limits.
+relation.network-group-resource-limits.description=All client connections belonging to a Network Group Resource Limits must comply with the resource limits policy.
diff --git a/opends/src/admin/messages/NetworkGroupCfgDefn_de.properties b/opends/src/admin/messages/NetworkGroupCfgDefn_de.properties
new file mode 100644
index 0000000..b2371ec
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupCfgDefn_de.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Network Group
+user-friendly-plural-name=Network Groups
+synopsis=The Network Group is used to classify incoming connections and route requests to workflows.
+property.enabled.synopsis=Indicates whether the Network Group is enabled for use in the server.
+property.enabled.description=If a network group is not enabled, its workflows will not be accessible when processing operations.
+property.network-group-id.synopsis=Specifies the name that is used to identify the associated Network Group .
+property.network-group-id.description=The name must be unique among all the Network Groups in the server.
+property.priority.synopsis=Specifies the order in which the network groups are evaluated.
+property.priority.description=A client connection is first compared against network group with priority 1. If the client connection does not match the network group criteria, the client connection is compared against network group with priority 2 etc...
+property.workflow.synopsis=Identifies the workflows in the network group.
+property.workflow.syntax.aggregation.constraint-synopsis=The referenced workflows must be enabled.
+relation.network-group-criteria.user-friendly-name=Network Group Criteria
+relation.network-group-criteria.synopsis=Specifies the set of criteria associated to this network group.
+relation.network-group-criteria.description=A client connection can belong to a Network Group Criteria only if it matches all the criteria defined for this Network Group Criteria.
+relation.network-group-request-filtering-policy.user-friendly-name=Network Group Request Filtering Policy
+relation.network-group-request-filtering-policy.synopsis=Specifies the request filtering policy enforced by this Network Group Request Filtering Policy.
+relation.network-group-request-filtering-policy.description=All client connections belonging to a Network Group Request Filtering Policy must comply with the request filtering policy.
+relation.network-group-resource-limits.user-friendly-name=Network Group Resource Limits
+relation.network-group-resource-limits.synopsis=Specifies the set of resource limits enforced by this Network Group Resource Limits.
+relation.network-group-resource-limits.description=All client connections belonging to a Network Group Resource Limits must comply with the resource limits policy.
diff --git a/opends/src/admin/messages/NetworkGroupCfgDefn_es.properties b/opends/src/admin/messages/NetworkGroupCfgDefn_es.properties
new file mode 100644
index 0000000..b2371ec
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupCfgDefn_es.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Network Group
+user-friendly-plural-name=Network Groups
+synopsis=The Network Group is used to classify incoming connections and route requests to workflows.
+property.enabled.synopsis=Indicates whether the Network Group is enabled for use in the server.
+property.enabled.description=If a network group is not enabled, its workflows will not be accessible when processing operations.
+property.network-group-id.synopsis=Specifies the name that is used to identify the associated Network Group .
+property.network-group-id.description=The name must be unique among all the Network Groups in the server.
+property.priority.synopsis=Specifies the order in which the network groups are evaluated.
+property.priority.description=A client connection is first compared against network group with priority 1. If the client connection does not match the network group criteria, the client connection is compared against network group with priority 2 etc...
+property.workflow.synopsis=Identifies the workflows in the network group.
+property.workflow.syntax.aggregation.constraint-synopsis=The referenced workflows must be enabled.
+relation.network-group-criteria.user-friendly-name=Network Group Criteria
+relation.network-group-criteria.synopsis=Specifies the set of criteria associated to this network group.
+relation.network-group-criteria.description=A client connection can belong to a Network Group Criteria only if it matches all the criteria defined for this Network Group Criteria.
+relation.network-group-request-filtering-policy.user-friendly-name=Network Group Request Filtering Policy
+relation.network-group-request-filtering-policy.synopsis=Specifies the request filtering policy enforced by this Network Group Request Filtering Policy.
+relation.network-group-request-filtering-policy.description=All client connections belonging to a Network Group Request Filtering Policy must comply with the request filtering policy.
+relation.network-group-resource-limits.user-friendly-name=Network Group Resource Limits
+relation.network-group-resource-limits.synopsis=Specifies the set of resource limits enforced by this Network Group Resource Limits.
+relation.network-group-resource-limits.description=All client connections belonging to a Network Group Resource Limits must comply with the resource limits policy.
diff --git a/opends/src/admin/messages/NetworkGroupCfgDefn_fr.properties b/opends/src/admin/messages/NetworkGroupCfgDefn_fr.properties
new file mode 100644
index 0000000..b2371ec
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupCfgDefn_fr.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Network Group
+user-friendly-plural-name=Network Groups
+synopsis=The Network Group is used to classify incoming connections and route requests to workflows.
+property.enabled.synopsis=Indicates whether the Network Group is enabled for use in the server.
+property.enabled.description=If a network group is not enabled, its workflows will not be accessible when processing operations.
+property.network-group-id.synopsis=Specifies the name that is used to identify the associated Network Group .
+property.network-group-id.description=The name must be unique among all the Network Groups in the server.
+property.priority.synopsis=Specifies the order in which the network groups are evaluated.
+property.priority.description=A client connection is first compared against network group with priority 1. If the client connection does not match the network group criteria, the client connection is compared against network group with priority 2 etc...
+property.workflow.synopsis=Identifies the workflows in the network group.
+property.workflow.syntax.aggregation.constraint-synopsis=The referenced workflows must be enabled.
+relation.network-group-criteria.user-friendly-name=Network Group Criteria
+relation.network-group-criteria.synopsis=Specifies the set of criteria associated to this network group.
+relation.network-group-criteria.description=A client connection can belong to a Network Group Criteria only if it matches all the criteria defined for this Network Group Criteria.
+relation.network-group-request-filtering-policy.user-friendly-name=Network Group Request Filtering Policy
+relation.network-group-request-filtering-policy.synopsis=Specifies the request filtering policy enforced by this Network Group Request Filtering Policy.
+relation.network-group-request-filtering-policy.description=All client connections belonging to a Network Group Request Filtering Policy must comply with the request filtering policy.
+relation.network-group-resource-limits.user-friendly-name=Network Group Resource Limits
+relation.network-group-resource-limits.synopsis=Specifies the set of resource limits enforced by this Network Group Resource Limits.
+relation.network-group-resource-limits.description=All client connections belonging to a Network Group Resource Limits must comply with the resource limits policy.
diff --git a/opends/src/admin/messages/NetworkGroupCfgDefn_ja.properties b/opends/src/admin/messages/NetworkGroupCfgDefn_ja.properties
new file mode 100644
index 0000000..b2371ec
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupCfgDefn_ja.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Network Group
+user-friendly-plural-name=Network Groups
+synopsis=The Network Group is used to classify incoming connections and route requests to workflows.
+property.enabled.synopsis=Indicates whether the Network Group is enabled for use in the server.
+property.enabled.description=If a network group is not enabled, its workflows will not be accessible when processing operations.
+property.network-group-id.synopsis=Specifies the name that is used to identify the associated Network Group .
+property.network-group-id.description=The name must be unique among all the Network Groups in the server.
+property.priority.synopsis=Specifies the order in which the network groups are evaluated.
+property.priority.description=A client connection is first compared against network group with priority 1. If the client connection does not match the network group criteria, the client connection is compared against network group with priority 2 etc...
+property.workflow.synopsis=Identifies the workflows in the network group.
+property.workflow.syntax.aggregation.constraint-synopsis=The referenced workflows must be enabled.
+relation.network-group-criteria.user-friendly-name=Network Group Criteria
+relation.network-group-criteria.synopsis=Specifies the set of criteria associated to this network group.
+relation.network-group-criteria.description=A client connection can belong to a Network Group Criteria only if it matches all the criteria defined for this Network Group Criteria.
+relation.network-group-request-filtering-policy.user-friendly-name=Network Group Request Filtering Policy
+relation.network-group-request-filtering-policy.synopsis=Specifies the request filtering policy enforced by this Network Group Request Filtering Policy.
+relation.network-group-request-filtering-policy.description=All client connections belonging to a Network Group Request Filtering Policy must comply with the request filtering policy.
+relation.network-group-resource-limits.user-friendly-name=Network Group Resource Limits
+relation.network-group-resource-limits.synopsis=Specifies the set of resource limits enforced by this Network Group Resource Limits.
+relation.network-group-resource-limits.description=All client connections belonging to a Network Group Resource Limits must comply with the resource limits policy.
diff --git a/opends/src/admin/messages/NetworkGroupCfgDefn_ko.properties b/opends/src/admin/messages/NetworkGroupCfgDefn_ko.properties
new file mode 100644
index 0000000..b2371ec
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupCfgDefn_ko.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Network Group
+user-friendly-plural-name=Network Groups
+synopsis=The Network Group is used to classify incoming connections and route requests to workflows.
+property.enabled.synopsis=Indicates whether the Network Group is enabled for use in the server.
+property.enabled.description=If a network group is not enabled, its workflows will not be accessible when processing operations.
+property.network-group-id.synopsis=Specifies the name that is used to identify the associated Network Group .
+property.network-group-id.description=The name must be unique among all the Network Groups in the server.
+property.priority.synopsis=Specifies the order in which the network groups are evaluated.
+property.priority.description=A client connection is first compared against network group with priority 1. If the client connection does not match the network group criteria, the client connection is compared against network group with priority 2 etc...
+property.workflow.synopsis=Identifies the workflows in the network group.
+property.workflow.syntax.aggregation.constraint-synopsis=The referenced workflows must be enabled.
+relation.network-group-criteria.user-friendly-name=Network Group Criteria
+relation.network-group-criteria.synopsis=Specifies the set of criteria associated to this network group.
+relation.network-group-criteria.description=A client connection can belong to a Network Group Criteria only if it matches all the criteria defined for this Network Group Criteria.
+relation.network-group-request-filtering-policy.user-friendly-name=Network Group Request Filtering Policy
+relation.network-group-request-filtering-policy.synopsis=Specifies the request filtering policy enforced by this Network Group Request Filtering Policy.
+relation.network-group-request-filtering-policy.description=All client connections belonging to a Network Group Request Filtering Policy must comply with the request filtering policy.
+relation.network-group-resource-limits.user-friendly-name=Network Group Resource Limits
+relation.network-group-resource-limits.synopsis=Specifies the set of resource limits enforced by this Network Group Resource Limits.
+relation.network-group-resource-limits.description=All client connections belonging to a Network Group Resource Limits must comply with the resource limits policy.
diff --git a/opends/src/admin/messages/NetworkGroupCfgDefn_zh_CN.properties b/opends/src/admin/messages/NetworkGroupCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..b2371ec
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupCfgDefn_zh_CN.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Network Group
+user-friendly-plural-name=Network Groups
+synopsis=The Network Group is used to classify incoming connections and route requests to workflows.
+property.enabled.synopsis=Indicates whether the Network Group is enabled for use in the server.
+property.enabled.description=If a network group is not enabled, its workflows will not be accessible when processing operations.
+property.network-group-id.synopsis=Specifies the name that is used to identify the associated Network Group .
+property.network-group-id.description=The name must be unique among all the Network Groups in the server.
+property.priority.synopsis=Specifies the order in which the network groups are evaluated.
+property.priority.description=A client connection is first compared against network group with priority 1. If the client connection does not match the network group criteria, the client connection is compared against network group with priority 2 etc...
+property.workflow.synopsis=Identifies the workflows in the network group.
+property.workflow.syntax.aggregation.constraint-synopsis=The referenced workflows must be enabled.
+relation.network-group-criteria.user-friendly-name=Network Group Criteria
+relation.network-group-criteria.synopsis=Specifies the set of criteria associated to this network group.
+relation.network-group-criteria.description=A client connection can belong to a Network Group Criteria only if it matches all the criteria defined for this Network Group Criteria.
+relation.network-group-request-filtering-policy.user-friendly-name=Network Group Request Filtering Policy
+relation.network-group-request-filtering-policy.synopsis=Specifies the request filtering policy enforced by this Network Group Request Filtering Policy.
+relation.network-group-request-filtering-policy.description=All client connections belonging to a Network Group Request Filtering Policy must comply with the request filtering policy.
+relation.network-group-resource-limits.user-friendly-name=Network Group Resource Limits
+relation.network-group-resource-limits.synopsis=Specifies the set of resource limits enforced by this Network Group Resource Limits.
+relation.network-group-resource-limits.description=All client connections belonging to a Network Group Resource Limits must comply with the resource limits policy.
diff --git a/opends/src/admin/messages/NetworkGroupCfgDefn_zh_TW.properties b/opends/src/admin/messages/NetworkGroupCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..b2371ec
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupCfgDefn_zh_TW.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Network Group
+user-friendly-plural-name=Network Groups
+synopsis=The Network Group is used to classify incoming connections and route requests to workflows.
+property.enabled.synopsis=Indicates whether the Network Group is enabled for use in the server.
+property.enabled.description=If a network group is not enabled, its workflows will not be accessible when processing operations.
+property.network-group-id.synopsis=Specifies the name that is used to identify the associated Network Group .
+property.network-group-id.description=The name must be unique among all the Network Groups in the server.
+property.priority.synopsis=Specifies the order in which the network groups are evaluated.
+property.priority.description=A client connection is first compared against network group with priority 1. If the client connection does not match the network group criteria, the client connection is compared against network group with priority 2 etc...
+property.workflow.synopsis=Identifies the workflows in the network group.
+property.workflow.syntax.aggregation.constraint-synopsis=The referenced workflows must be enabled.
+relation.network-group-criteria.user-friendly-name=Network Group Criteria
+relation.network-group-criteria.synopsis=Specifies the set of criteria associated to this network group.
+relation.network-group-criteria.description=A client connection can belong to a Network Group Criteria only if it matches all the criteria defined for this Network Group Criteria.
+relation.network-group-request-filtering-policy.user-friendly-name=Network Group Request Filtering Policy
+relation.network-group-request-filtering-policy.synopsis=Specifies the request filtering policy enforced by this Network Group Request Filtering Policy.
+relation.network-group-request-filtering-policy.description=All client connections belonging to a Network Group Request Filtering Policy must comply with the request filtering policy.
+relation.network-group-resource-limits.user-friendly-name=Network Group Resource Limits
+relation.network-group-resource-limits.synopsis=Specifies the set of resource limits enforced by this Network Group Resource Limits.
+relation.network-group-resource-limits.description=All client connections belonging to a Network Group Resource Limits must comply with the resource limits policy.
diff --git a/opends/src/admin/messages/NetworkGroupCriteriaCfgDefn.properties b/opends/src/admin/messages/NetworkGroupCriteriaCfgDefn.properties
new file mode 100644
index 0000000..c5f4825
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupCriteriaCfgDefn.properties
@@ -0,0 +1,16 @@
+user-friendly-name=Network Group Criteria
+user-friendly-plural-name=Network Group Criteria
+synopsis=The Network Group Criteria is used to classify incoming connections.
+property.allowed-auth-method.synopsis=Specifies the allowed authorization methods for a client connection to match the Network Group Criteria.
+property.allowed-auth-method.syntax.enumeration.value.anonymous.synopsis=Anonymous connections.
+property.allowed-auth-method.syntax.enumeration.value.sasl.synopsis=SASL/external connections, with a certificate containing the user authentication.
+property.allowed-auth-method.syntax.enumeration.value.simple.synopsis=Simple bind connections, with bind DN and password.
+property.allowed-ldap-port.synopsis=Specifies the allowed LDAP ports for the client connection to match the Network Group Criteria.
+property.allowed-ldap-port.syntax.enumeration.value.ldap.synopsis=Connection over ldap port.
+property.allowed-ldap-port.syntax.enumeration.value.ldaps.synopsis=Connection over ldaps port.
+property.bind-dn-filter.synopsis=Specifies a bind DN filter for the client connection to match the Network Group Criteria.
+property.bind-dn-filter.description=A valid bind DN filter is a string composed of zero or more wildcards. A double wildcard ** replaces one or more RDN components (as in uid=dmiller,**,dc=example,dc=com). A simple wildcard * replaces either a whole RDN, or a whole type, or a value substring (as in uid=bj*,ou=people,dc=example,dc=com).
+property.ip-address-filter.synopsis=Specifies an IP address filter for the Network Group Criteria.
+property.ip-address-filter.description=A valid IP address mask can be one of the followings: 129.34.55.67 129.*.78.55 .sun.com foo.sun.com foo.*.sun.* 128.*.*.* 129.45.23.67/22 128.33.21.21/32 *.*.*.* 129.45.67.34/0 foo.com foo 2001:fecd:ba23:cd1f:dcb1:1010:9234:4088/124 2001:fecd:ba23:cd1f:dcb1:1010:9234:4088 [2001:fecd:ba23:cd1f:dcb1:1010:9234:4088]/45 ::/128 ::1/128 ::
+property.is-security-mandatory.synopsis=Specifies whether security is mandatory for the Network Group Criteria.
+property.user-entry-filter.synopsis=Specifies a search filter that the entry of a bound client must match.
diff --git a/opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_de.properties b/opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_de.properties
new file mode 100644
index 0000000..c5f4825
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_de.properties
@@ -0,0 +1,16 @@
+user-friendly-name=Network Group Criteria
+user-friendly-plural-name=Network Group Criteria
+synopsis=The Network Group Criteria is used to classify incoming connections.
+property.allowed-auth-method.synopsis=Specifies the allowed authorization methods for a client connection to match the Network Group Criteria.
+property.allowed-auth-method.syntax.enumeration.value.anonymous.synopsis=Anonymous connections.
+property.allowed-auth-method.syntax.enumeration.value.sasl.synopsis=SASL/external connections, with a certificate containing the user authentication.
+property.allowed-auth-method.syntax.enumeration.value.simple.synopsis=Simple bind connections, with bind DN and password.
+property.allowed-ldap-port.synopsis=Specifies the allowed LDAP ports for the client connection to match the Network Group Criteria.
+property.allowed-ldap-port.syntax.enumeration.value.ldap.synopsis=Connection over ldap port.
+property.allowed-ldap-port.syntax.enumeration.value.ldaps.synopsis=Connection over ldaps port.
+property.bind-dn-filter.synopsis=Specifies a bind DN filter for the client connection to match the Network Group Criteria.
+property.bind-dn-filter.description=A valid bind DN filter is a string composed of zero or more wildcards. A double wildcard ** replaces one or more RDN components (as in uid=dmiller,**,dc=example,dc=com). A simple wildcard * replaces either a whole RDN, or a whole type, or a value substring (as in uid=bj*,ou=people,dc=example,dc=com).
+property.ip-address-filter.synopsis=Specifies an IP address filter for the Network Group Criteria.
+property.ip-address-filter.description=A valid IP address mask can be one of the followings: 129.34.55.67 129.*.78.55 .sun.com foo.sun.com foo.*.sun.* 128.*.*.* 129.45.23.67/22 128.33.21.21/32 *.*.*.* 129.45.67.34/0 foo.com foo 2001:fecd:ba23:cd1f:dcb1:1010:9234:4088/124 2001:fecd:ba23:cd1f:dcb1:1010:9234:4088 [2001:fecd:ba23:cd1f:dcb1:1010:9234:4088]/45 ::/128 ::1/128 ::
+property.is-security-mandatory.synopsis=Specifies whether security is mandatory for the Network Group Criteria.
+property.user-entry-filter.synopsis=Specifies a search filter that the entry of a bound client must match.
diff --git a/opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_es.properties b/opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_es.properties
new file mode 100644
index 0000000..c5f4825
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_es.properties
@@ -0,0 +1,16 @@
+user-friendly-name=Network Group Criteria
+user-friendly-plural-name=Network Group Criteria
+synopsis=The Network Group Criteria is used to classify incoming connections.
+property.allowed-auth-method.synopsis=Specifies the allowed authorization methods for a client connection to match the Network Group Criteria.
+property.allowed-auth-method.syntax.enumeration.value.anonymous.synopsis=Anonymous connections.
+property.allowed-auth-method.syntax.enumeration.value.sasl.synopsis=SASL/external connections, with a certificate containing the user authentication.
+property.allowed-auth-method.syntax.enumeration.value.simple.synopsis=Simple bind connections, with bind DN and password.
+property.allowed-ldap-port.synopsis=Specifies the allowed LDAP ports for the client connection to match the Network Group Criteria.
+property.allowed-ldap-port.syntax.enumeration.value.ldap.synopsis=Connection over ldap port.
+property.allowed-ldap-port.syntax.enumeration.value.ldaps.synopsis=Connection over ldaps port.
+property.bind-dn-filter.synopsis=Specifies a bind DN filter for the client connection to match the Network Group Criteria.
+property.bind-dn-filter.description=A valid bind DN filter is a string composed of zero or more wildcards. A double wildcard ** replaces one or more RDN components (as in uid=dmiller,**,dc=example,dc=com). A simple wildcard * replaces either a whole RDN, or a whole type, or a value substring (as in uid=bj*,ou=people,dc=example,dc=com).
+property.ip-address-filter.synopsis=Specifies an IP address filter for the Network Group Criteria.
+property.ip-address-filter.description=A valid IP address mask can be one of the followings: 129.34.55.67 129.*.78.55 .sun.com foo.sun.com foo.*.sun.* 128.*.*.* 129.45.23.67/22 128.33.21.21/32 *.*.*.* 129.45.67.34/0 foo.com foo 2001:fecd:ba23:cd1f:dcb1:1010:9234:4088/124 2001:fecd:ba23:cd1f:dcb1:1010:9234:4088 [2001:fecd:ba23:cd1f:dcb1:1010:9234:4088]/45 ::/128 ::1/128 ::
+property.is-security-mandatory.synopsis=Specifies whether security is mandatory for the Network Group Criteria.
+property.user-entry-filter.synopsis=Specifies a search filter that the entry of a bound client must match.
diff --git a/opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_fr.properties b/opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_fr.properties
new file mode 100644
index 0000000..c5f4825
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_fr.properties
@@ -0,0 +1,16 @@
+user-friendly-name=Network Group Criteria
+user-friendly-plural-name=Network Group Criteria
+synopsis=The Network Group Criteria is used to classify incoming connections.
+property.allowed-auth-method.synopsis=Specifies the allowed authorization methods for a client connection to match the Network Group Criteria.
+property.allowed-auth-method.syntax.enumeration.value.anonymous.synopsis=Anonymous connections.
+property.allowed-auth-method.syntax.enumeration.value.sasl.synopsis=SASL/external connections, with a certificate containing the user authentication.
+property.allowed-auth-method.syntax.enumeration.value.simple.synopsis=Simple bind connections, with bind DN and password.
+property.allowed-ldap-port.synopsis=Specifies the allowed LDAP ports for the client connection to match the Network Group Criteria.
+property.allowed-ldap-port.syntax.enumeration.value.ldap.synopsis=Connection over ldap port.
+property.allowed-ldap-port.syntax.enumeration.value.ldaps.synopsis=Connection over ldaps port.
+property.bind-dn-filter.synopsis=Specifies a bind DN filter for the client connection to match the Network Group Criteria.
+property.bind-dn-filter.description=A valid bind DN filter is a string composed of zero or more wildcards. A double wildcard ** replaces one or more RDN components (as in uid=dmiller,**,dc=example,dc=com). A simple wildcard * replaces either a whole RDN, or a whole type, or a value substring (as in uid=bj*,ou=people,dc=example,dc=com).
+property.ip-address-filter.synopsis=Specifies an IP address filter for the Network Group Criteria.
+property.ip-address-filter.description=A valid IP address mask can be one of the followings: 129.34.55.67 129.*.78.55 .sun.com foo.sun.com foo.*.sun.* 128.*.*.* 129.45.23.67/22 128.33.21.21/32 *.*.*.* 129.45.67.34/0 foo.com foo 2001:fecd:ba23:cd1f:dcb1:1010:9234:4088/124 2001:fecd:ba23:cd1f:dcb1:1010:9234:4088 [2001:fecd:ba23:cd1f:dcb1:1010:9234:4088]/45 ::/128 ::1/128 ::
+property.is-security-mandatory.synopsis=Specifies whether security is mandatory for the Network Group Criteria.
+property.user-entry-filter.synopsis=Specifies a search filter that the entry of a bound client must match.
diff --git a/opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_ja.properties b/opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_ja.properties
new file mode 100644
index 0000000..c5f4825
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_ja.properties
@@ -0,0 +1,16 @@
+user-friendly-name=Network Group Criteria
+user-friendly-plural-name=Network Group Criteria
+synopsis=The Network Group Criteria is used to classify incoming connections.
+property.allowed-auth-method.synopsis=Specifies the allowed authorization methods for a client connection to match the Network Group Criteria.
+property.allowed-auth-method.syntax.enumeration.value.anonymous.synopsis=Anonymous connections.
+property.allowed-auth-method.syntax.enumeration.value.sasl.synopsis=SASL/external connections, with a certificate containing the user authentication.
+property.allowed-auth-method.syntax.enumeration.value.simple.synopsis=Simple bind connections, with bind DN and password.
+property.allowed-ldap-port.synopsis=Specifies the allowed LDAP ports for the client connection to match the Network Group Criteria.
+property.allowed-ldap-port.syntax.enumeration.value.ldap.synopsis=Connection over ldap port.
+property.allowed-ldap-port.syntax.enumeration.value.ldaps.synopsis=Connection over ldaps port.
+property.bind-dn-filter.synopsis=Specifies a bind DN filter for the client connection to match the Network Group Criteria.
+property.bind-dn-filter.description=A valid bind DN filter is a string composed of zero or more wildcards. A double wildcard ** replaces one or more RDN components (as in uid=dmiller,**,dc=example,dc=com). A simple wildcard * replaces either a whole RDN, or a whole type, or a value substring (as in uid=bj*,ou=people,dc=example,dc=com).
+property.ip-address-filter.synopsis=Specifies an IP address filter for the Network Group Criteria.
+property.ip-address-filter.description=A valid IP address mask can be one of the followings: 129.34.55.67 129.*.78.55 .sun.com foo.sun.com foo.*.sun.* 128.*.*.* 129.45.23.67/22 128.33.21.21/32 *.*.*.* 129.45.67.34/0 foo.com foo 2001:fecd:ba23:cd1f:dcb1:1010:9234:4088/124 2001:fecd:ba23:cd1f:dcb1:1010:9234:4088 [2001:fecd:ba23:cd1f:dcb1:1010:9234:4088]/45 ::/128 ::1/128 ::
+property.is-security-mandatory.synopsis=Specifies whether security is mandatory for the Network Group Criteria.
+property.user-entry-filter.synopsis=Specifies a search filter that the entry of a bound client must match.
diff --git a/opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_ko.properties b/opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_ko.properties
new file mode 100644
index 0000000..c5f4825
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_ko.properties
@@ -0,0 +1,16 @@
+user-friendly-name=Network Group Criteria
+user-friendly-plural-name=Network Group Criteria
+synopsis=The Network Group Criteria is used to classify incoming connections.
+property.allowed-auth-method.synopsis=Specifies the allowed authorization methods for a client connection to match the Network Group Criteria.
+property.allowed-auth-method.syntax.enumeration.value.anonymous.synopsis=Anonymous connections.
+property.allowed-auth-method.syntax.enumeration.value.sasl.synopsis=SASL/external connections, with a certificate containing the user authentication.
+property.allowed-auth-method.syntax.enumeration.value.simple.synopsis=Simple bind connections, with bind DN and password.
+property.allowed-ldap-port.synopsis=Specifies the allowed LDAP ports for the client connection to match the Network Group Criteria.
+property.allowed-ldap-port.syntax.enumeration.value.ldap.synopsis=Connection over ldap port.
+property.allowed-ldap-port.syntax.enumeration.value.ldaps.synopsis=Connection over ldaps port.
+property.bind-dn-filter.synopsis=Specifies a bind DN filter for the client connection to match the Network Group Criteria.
+property.bind-dn-filter.description=A valid bind DN filter is a string composed of zero or more wildcards. A double wildcard ** replaces one or more RDN components (as in uid=dmiller,**,dc=example,dc=com). A simple wildcard * replaces either a whole RDN, or a whole type, or a value substring (as in uid=bj*,ou=people,dc=example,dc=com).
+property.ip-address-filter.synopsis=Specifies an IP address filter for the Network Group Criteria.
+property.ip-address-filter.description=A valid IP address mask can be one of the followings: 129.34.55.67 129.*.78.55 .sun.com foo.sun.com foo.*.sun.* 128.*.*.* 129.45.23.67/22 128.33.21.21/32 *.*.*.* 129.45.67.34/0 foo.com foo 2001:fecd:ba23:cd1f:dcb1:1010:9234:4088/124 2001:fecd:ba23:cd1f:dcb1:1010:9234:4088 [2001:fecd:ba23:cd1f:dcb1:1010:9234:4088]/45 ::/128 ::1/128 ::
+property.is-security-mandatory.synopsis=Specifies whether security is mandatory for the Network Group Criteria.
+property.user-entry-filter.synopsis=Specifies a search filter that the entry of a bound client must match.
diff --git a/opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_zh_CN.properties b/opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..c5f4825
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_zh_CN.properties
@@ -0,0 +1,16 @@
+user-friendly-name=Network Group Criteria
+user-friendly-plural-name=Network Group Criteria
+synopsis=The Network Group Criteria is used to classify incoming connections.
+property.allowed-auth-method.synopsis=Specifies the allowed authorization methods for a client connection to match the Network Group Criteria.
+property.allowed-auth-method.syntax.enumeration.value.anonymous.synopsis=Anonymous connections.
+property.allowed-auth-method.syntax.enumeration.value.sasl.synopsis=SASL/external connections, with a certificate containing the user authentication.
+property.allowed-auth-method.syntax.enumeration.value.simple.synopsis=Simple bind connections, with bind DN and password.
+property.allowed-ldap-port.synopsis=Specifies the allowed LDAP ports for the client connection to match the Network Group Criteria.
+property.allowed-ldap-port.syntax.enumeration.value.ldap.synopsis=Connection over ldap port.
+property.allowed-ldap-port.syntax.enumeration.value.ldaps.synopsis=Connection over ldaps port.
+property.bind-dn-filter.synopsis=Specifies a bind DN filter for the client connection to match the Network Group Criteria.
+property.bind-dn-filter.description=A valid bind DN filter is a string composed of zero or more wildcards. A double wildcard ** replaces one or more RDN components (as in uid=dmiller,**,dc=example,dc=com). A simple wildcard * replaces either a whole RDN, or a whole type, or a value substring (as in uid=bj*,ou=people,dc=example,dc=com).
+property.ip-address-filter.synopsis=Specifies an IP address filter for the Network Group Criteria.
+property.ip-address-filter.description=A valid IP address mask can be one of the followings: 129.34.55.67 129.*.78.55 .sun.com foo.sun.com foo.*.sun.* 128.*.*.* 129.45.23.67/22 128.33.21.21/32 *.*.*.* 129.45.67.34/0 foo.com foo 2001:fecd:ba23:cd1f:dcb1:1010:9234:4088/124 2001:fecd:ba23:cd1f:dcb1:1010:9234:4088 [2001:fecd:ba23:cd1f:dcb1:1010:9234:4088]/45 ::/128 ::1/128 ::
+property.is-security-mandatory.synopsis=Specifies whether security is mandatory for the Network Group Criteria.
+property.user-entry-filter.synopsis=Specifies a search filter that the entry of a bound client must match.
diff --git a/opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_zh_TW.properties b/opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..c5f4825
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupCriteriaCfgDefn_zh_TW.properties
@@ -0,0 +1,16 @@
+user-friendly-name=Network Group Criteria
+user-friendly-plural-name=Network Group Criteria
+synopsis=The Network Group Criteria is used to classify incoming connections.
+property.allowed-auth-method.synopsis=Specifies the allowed authorization methods for a client connection to match the Network Group Criteria.
+property.allowed-auth-method.syntax.enumeration.value.anonymous.synopsis=Anonymous connections.
+property.allowed-auth-method.syntax.enumeration.value.sasl.synopsis=SASL/external connections, with a certificate containing the user authentication.
+property.allowed-auth-method.syntax.enumeration.value.simple.synopsis=Simple bind connections, with bind DN and password.
+property.allowed-ldap-port.synopsis=Specifies the allowed LDAP ports for the client connection to match the Network Group Criteria.
+property.allowed-ldap-port.syntax.enumeration.value.ldap.synopsis=Connection over ldap port.
+property.allowed-ldap-port.syntax.enumeration.value.ldaps.synopsis=Connection over ldaps port.
+property.bind-dn-filter.synopsis=Specifies a bind DN filter for the client connection to match the Network Group Criteria.
+property.bind-dn-filter.description=A valid bind DN filter is a string composed of zero or more wildcards. A double wildcard ** replaces one or more RDN components (as in uid=dmiller,**,dc=example,dc=com). A simple wildcard * replaces either a whole RDN, or a whole type, or a value substring (as in uid=bj*,ou=people,dc=example,dc=com).
+property.ip-address-filter.synopsis=Specifies an IP address filter for the Network Group Criteria.
+property.ip-address-filter.description=A valid IP address mask can be one of the followings: 129.34.55.67 129.*.78.55 .sun.com foo.sun.com foo.*.sun.* 128.*.*.* 129.45.23.67/22 128.33.21.21/32 *.*.*.* 129.45.67.34/0 foo.com foo 2001:fecd:ba23:cd1f:dcb1:1010:9234:4088/124 2001:fecd:ba23:cd1f:dcb1:1010:9234:4088 [2001:fecd:ba23:cd1f:dcb1:1010:9234:4088]/45 ::/128 ::1/128 ::
+property.is-security-mandatory.synopsis=Specifies whether security is mandatory for the Network Group Criteria.
+property.user-entry-filter.synopsis=Specifies a search filter that the entry of a bound client must match.
diff --git a/opends/src/admin/messages/NetworkGroupPluginCfgDefn.properties b/opends/src/admin/messages/NetworkGroupPluginCfgDefn.properties
new file mode 100644
index 0000000..a2433e2
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupPluginCfgDefn.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Network Group Plugin
+user-friendly-plural-name=Network Group Plugins
+synopsis=The Network Group Plugin allows to group connections into different network groups and enforce specific resource limit policies for each network group.
+description=The Network Group Plugin creates network groups based on client connection criteria. Each network group defines resource limit policies applied to all its connections.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/NetworkGroupPluginCfgDefn_de.properties b/opends/src/admin/messages/NetworkGroupPluginCfgDefn_de.properties
new file mode 100644
index 0000000..a2433e2
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupPluginCfgDefn_de.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Network Group Plugin
+user-friendly-plural-name=Network Group Plugins
+synopsis=The Network Group Plugin allows to group connections into different network groups and enforce specific resource limit policies for each network group.
+description=The Network Group Plugin creates network groups based on client connection criteria. Each network group defines resource limit policies applied to all its connections.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/NetworkGroupPluginCfgDefn_es.properties b/opends/src/admin/messages/NetworkGroupPluginCfgDefn_es.properties
new file mode 100644
index 0000000..a2433e2
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupPluginCfgDefn_es.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Network Group Plugin
+user-friendly-plural-name=Network Group Plugins
+synopsis=The Network Group Plugin allows to group connections into different network groups and enforce specific resource limit policies for each network group.
+description=The Network Group Plugin creates network groups based on client connection criteria. Each network group defines resource limit policies applied to all its connections.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/NetworkGroupPluginCfgDefn_fr.properties b/opends/src/admin/messages/NetworkGroupPluginCfgDefn_fr.properties
new file mode 100644
index 0000000..a2433e2
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupPluginCfgDefn_fr.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Network Group Plugin
+user-friendly-plural-name=Network Group Plugins
+synopsis=The Network Group Plugin allows to group connections into different network groups and enforce specific resource limit policies for each network group.
+description=The Network Group Plugin creates network groups based on client connection criteria. Each network group defines resource limit policies applied to all its connections.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/NetworkGroupPluginCfgDefn_ja.properties b/opends/src/admin/messages/NetworkGroupPluginCfgDefn_ja.properties
new file mode 100644
index 0000000..a2433e2
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupPluginCfgDefn_ja.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Network Group Plugin
+user-friendly-plural-name=Network Group Plugins
+synopsis=The Network Group Plugin allows to group connections into different network groups and enforce specific resource limit policies for each network group.
+description=The Network Group Plugin creates network groups based on client connection criteria. Each network group defines resource limit policies applied to all its connections.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/NetworkGroupPluginCfgDefn_ko.properties b/opends/src/admin/messages/NetworkGroupPluginCfgDefn_ko.properties
new file mode 100644
index 0000000..a2433e2
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupPluginCfgDefn_ko.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Network Group Plugin
+user-friendly-plural-name=Network Group Plugins
+synopsis=The Network Group Plugin allows to group connections into different network groups and enforce specific resource limit policies for each network group.
+description=The Network Group Plugin creates network groups based on client connection criteria. Each network group defines resource limit policies applied to all its connections.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/NetworkGroupPluginCfgDefn_zh_CN.properties b/opends/src/admin/messages/NetworkGroupPluginCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..a2433e2
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupPluginCfgDefn_zh_CN.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Network Group Plugin
+user-friendly-plural-name=Network Group Plugins
+synopsis=The Network Group Plugin allows to group connections into different network groups and enforce specific resource limit policies for each network group.
+description=The Network Group Plugin creates network groups based on client connection criteria. Each network group defines resource limit policies applied to all its connections.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/NetworkGroupPluginCfgDefn_zh_TW.properties b/opends/src/admin/messages/NetworkGroupPluginCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..a2433e2
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupPluginCfgDefn_zh_TW.properties
@@ -0,0 +1,59 @@
+user-friendly-name=Network Group Plugin
+user-friendly-plural-name=Network Group Plugins
+synopsis=The Network Group Plugin allows to group connections into different network groups and enforce specific resource limit policies for each network group.
+description=The Network Group Plugin creates network groups based on client connection criteria. Each network group defines resource limit policies applied to all its connections.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn.properties b/opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn.properties
new file mode 100644
index 0000000..ff4fddb
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn.properties
@@ -0,0 +1,28 @@
+user-friendly-name=Network Group Request Filtering Policy
+user-friendly-plural-name=Network Group Request Filtering Policies
+synopsis=The Network Group Request Filtering Policy is used to define the type of requests allowed in the network group.
+property.allowed-attributes.synopsis=Specifies which attributes are allowed in search and compare operations.
+property.allowed-attributes.description=When this attribute is specified, only the listed attributes are allowed in search and compare operations. If it is not set, all the attributes are allowed, except those listed in ds-cfg-prohibited-attributes.
+property.allowed-operations.synopsis=Specifies which operations are allowed in the network group.
+property.allowed-operations.description=When this attribute is specified, only the listed operations are allowed in the network group. If the attribute is not defined, all the operations are allowed.
+property.allowed-operations.syntax.enumeration.value.add.synopsis=Add operations.
+property.allowed-operations.syntax.enumeration.value.bind.synopsis=Bind operations.
+property.allowed-operations.syntax.enumeration.value.compare.synopsis=Compare operations
+property.allowed-operations.syntax.enumeration.value.delete.synopsis=Delete operations
+property.allowed-operations.syntax.enumeration.value.extended.synopsis=Extended operations
+property.allowed-operations.syntax.enumeration.value.inequality-search.synopsis=Inequality Search operations
+property.allowed-operations.syntax.enumeration.value.modify.synopsis=Modify operations
+property.allowed-operations.syntax.enumeration.value.rename.synopsis=Rename operations
+property.allowed-operations.syntax.enumeration.value.search.synopsis=Search operations
+property.allowed-search-scopes.synopsis=Specifies which search scopes are allowed in the network group.
+property.allowed-search-scopes.description=When this attribute is specified, only the listed scopes are allowed in the network group. If it is not set, all search scopes are allowed.
+property.allowed-search-scopes.syntax.enumeration.value.base.synopsis=Base-object search.
+property.allowed-search-scopes.syntax.enumeration.value.children.synopsis=Subordinate subtree search
+property.allowed-search-scopes.syntax.enumeration.value.one.synopsis=One-level search.
+property.allowed-search-scopes.syntax.enumeration.value.sub.synopsis=Whole subtree search
+property.allowed-subtrees.synopsis=Specifies which subtrees are exposed to clients.
+property.allowed-subtrees.description=When this attribute is specified, only the listed subtrees are exposed. If it is not set, all the substrees are exposed. Note that ds-cfg-prohibited-subtrees restricts the list of exposed subtrees.
+property.prohibited-attributes.synopsis=Specifies which attributes are not allowed in search and compare operations.
+property.prohibited-attributes.description=When this attribute is specified, all the listed attributes are prohibited in search and compare operations. It should not be used in conjunction with ds-cfg-allowed-attributes.
+property.prohibited-subtrees.synopsis=Specifies which subtrees are not exposed to clients. Each prohibited subtree must be subordinate to an allowed subtree.
+property.prohibited-subtrees.description=When this attribute is specified, all the listed subtrees cannot be accessed.
diff --git a/opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_de.properties b/opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_de.properties
new file mode 100644
index 0000000..ff4fddb
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_de.properties
@@ -0,0 +1,28 @@
+user-friendly-name=Network Group Request Filtering Policy
+user-friendly-plural-name=Network Group Request Filtering Policies
+synopsis=The Network Group Request Filtering Policy is used to define the type of requests allowed in the network group.
+property.allowed-attributes.synopsis=Specifies which attributes are allowed in search and compare operations.
+property.allowed-attributes.description=When this attribute is specified, only the listed attributes are allowed in search and compare operations. If it is not set, all the attributes are allowed, except those listed in ds-cfg-prohibited-attributes.
+property.allowed-operations.synopsis=Specifies which operations are allowed in the network group.
+property.allowed-operations.description=When this attribute is specified, only the listed operations are allowed in the network group. If the attribute is not defined, all the operations are allowed.
+property.allowed-operations.syntax.enumeration.value.add.synopsis=Add operations.
+property.allowed-operations.syntax.enumeration.value.bind.synopsis=Bind operations.
+property.allowed-operations.syntax.enumeration.value.compare.synopsis=Compare operations
+property.allowed-operations.syntax.enumeration.value.delete.synopsis=Delete operations
+property.allowed-operations.syntax.enumeration.value.extended.synopsis=Extended operations
+property.allowed-operations.syntax.enumeration.value.inequality-search.synopsis=Inequality Search operations
+property.allowed-operations.syntax.enumeration.value.modify.synopsis=Modify operations
+property.allowed-operations.syntax.enumeration.value.rename.synopsis=Rename operations
+property.allowed-operations.syntax.enumeration.value.search.synopsis=Search operations
+property.allowed-search-scopes.synopsis=Specifies which search scopes are allowed in the network group.
+property.allowed-search-scopes.description=When this attribute is specified, only the listed scopes are allowed in the network group. If it is not set, all search scopes are allowed.
+property.allowed-search-scopes.syntax.enumeration.value.base.synopsis=Base-object search.
+property.allowed-search-scopes.syntax.enumeration.value.children.synopsis=Subordinate subtree search
+property.allowed-search-scopes.syntax.enumeration.value.one.synopsis=One-level search.
+property.allowed-search-scopes.syntax.enumeration.value.sub.synopsis=Whole subtree search
+property.allowed-subtrees.synopsis=Specifies which subtrees are exposed to clients.
+property.allowed-subtrees.description=When this attribute is specified, only the listed subtrees are exposed. If it is not set, all the substrees are exposed. Note that ds-cfg-prohibited-subtrees restricts the list of exposed subtrees.
+property.prohibited-attributes.synopsis=Specifies which attributes are not allowed in search and compare operations.
+property.prohibited-attributes.description=When this attribute is specified, all the listed attributes are prohibited in search and compare operations. It should not be used in conjunction with ds-cfg-allowed-attributes.
+property.prohibited-subtrees.synopsis=Specifies which subtrees are not exposed to clients. Each prohibited subtree must be subordinate to an allowed subtree.
+property.prohibited-subtrees.description=When this attribute is specified, all the listed subtrees cannot be accessed.
diff --git a/opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_es.properties b/opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_es.properties
new file mode 100644
index 0000000..ff4fddb
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_es.properties
@@ -0,0 +1,28 @@
+user-friendly-name=Network Group Request Filtering Policy
+user-friendly-plural-name=Network Group Request Filtering Policies
+synopsis=The Network Group Request Filtering Policy is used to define the type of requests allowed in the network group.
+property.allowed-attributes.synopsis=Specifies which attributes are allowed in search and compare operations.
+property.allowed-attributes.description=When this attribute is specified, only the listed attributes are allowed in search and compare operations. If it is not set, all the attributes are allowed, except those listed in ds-cfg-prohibited-attributes.
+property.allowed-operations.synopsis=Specifies which operations are allowed in the network group.
+property.allowed-operations.description=When this attribute is specified, only the listed operations are allowed in the network group. If the attribute is not defined, all the operations are allowed.
+property.allowed-operations.syntax.enumeration.value.add.synopsis=Add operations.
+property.allowed-operations.syntax.enumeration.value.bind.synopsis=Bind operations.
+property.allowed-operations.syntax.enumeration.value.compare.synopsis=Compare operations
+property.allowed-operations.syntax.enumeration.value.delete.synopsis=Delete operations
+property.allowed-operations.syntax.enumeration.value.extended.synopsis=Extended operations
+property.allowed-operations.syntax.enumeration.value.inequality-search.synopsis=Inequality Search operations
+property.allowed-operations.syntax.enumeration.value.modify.synopsis=Modify operations
+property.allowed-operations.syntax.enumeration.value.rename.synopsis=Rename operations
+property.allowed-operations.syntax.enumeration.value.search.synopsis=Search operations
+property.allowed-search-scopes.synopsis=Specifies which search scopes are allowed in the network group.
+property.allowed-search-scopes.description=When this attribute is specified, only the listed scopes are allowed in the network group. If it is not set, all search scopes are allowed.
+property.allowed-search-scopes.syntax.enumeration.value.base.synopsis=Base-object search.
+property.allowed-search-scopes.syntax.enumeration.value.children.synopsis=Subordinate subtree search
+property.allowed-search-scopes.syntax.enumeration.value.one.synopsis=One-level search.
+property.allowed-search-scopes.syntax.enumeration.value.sub.synopsis=Whole subtree search
+property.allowed-subtrees.synopsis=Specifies which subtrees are exposed to clients.
+property.allowed-subtrees.description=When this attribute is specified, only the listed subtrees are exposed. If it is not set, all the substrees are exposed. Note that ds-cfg-prohibited-subtrees restricts the list of exposed subtrees.
+property.prohibited-attributes.synopsis=Specifies which attributes are not allowed in search and compare operations.
+property.prohibited-attributes.description=When this attribute is specified, all the listed attributes are prohibited in search and compare operations. It should not be used in conjunction with ds-cfg-allowed-attributes.
+property.prohibited-subtrees.synopsis=Specifies which subtrees are not exposed to clients. Each prohibited subtree must be subordinate to an allowed subtree.
+property.prohibited-subtrees.description=When this attribute is specified, all the listed subtrees cannot be accessed.
diff --git a/opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_fr.properties b/opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_fr.properties
new file mode 100644
index 0000000..ff4fddb
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_fr.properties
@@ -0,0 +1,28 @@
+user-friendly-name=Network Group Request Filtering Policy
+user-friendly-plural-name=Network Group Request Filtering Policies
+synopsis=The Network Group Request Filtering Policy is used to define the type of requests allowed in the network group.
+property.allowed-attributes.synopsis=Specifies which attributes are allowed in search and compare operations.
+property.allowed-attributes.description=When this attribute is specified, only the listed attributes are allowed in search and compare operations. If it is not set, all the attributes are allowed, except those listed in ds-cfg-prohibited-attributes.
+property.allowed-operations.synopsis=Specifies which operations are allowed in the network group.
+property.allowed-operations.description=When this attribute is specified, only the listed operations are allowed in the network group. If the attribute is not defined, all the operations are allowed.
+property.allowed-operations.syntax.enumeration.value.add.synopsis=Add operations.
+property.allowed-operations.syntax.enumeration.value.bind.synopsis=Bind operations.
+property.allowed-operations.syntax.enumeration.value.compare.synopsis=Compare operations
+property.allowed-operations.syntax.enumeration.value.delete.synopsis=Delete operations
+property.allowed-operations.syntax.enumeration.value.extended.synopsis=Extended operations
+property.allowed-operations.syntax.enumeration.value.inequality-search.synopsis=Inequality Search operations
+property.allowed-operations.syntax.enumeration.value.modify.synopsis=Modify operations
+property.allowed-operations.syntax.enumeration.value.rename.synopsis=Rename operations
+property.allowed-operations.syntax.enumeration.value.search.synopsis=Search operations
+property.allowed-search-scopes.synopsis=Specifies which search scopes are allowed in the network group.
+property.allowed-search-scopes.description=When this attribute is specified, only the listed scopes are allowed in the network group. If it is not set, all search scopes are allowed.
+property.allowed-search-scopes.syntax.enumeration.value.base.synopsis=Base-object search.
+property.allowed-search-scopes.syntax.enumeration.value.children.synopsis=Subordinate subtree search
+property.allowed-search-scopes.syntax.enumeration.value.one.synopsis=One-level search.
+property.allowed-search-scopes.syntax.enumeration.value.sub.synopsis=Whole subtree search
+property.allowed-subtrees.synopsis=Specifies which subtrees are exposed to clients.
+property.allowed-subtrees.description=When this attribute is specified, only the listed subtrees are exposed. If it is not set, all the substrees are exposed. Note that ds-cfg-prohibited-subtrees restricts the list of exposed subtrees.
+property.prohibited-attributes.synopsis=Specifies which attributes are not allowed in search and compare operations.
+property.prohibited-attributes.description=When this attribute is specified, all the listed attributes are prohibited in search and compare operations. It should not be used in conjunction with ds-cfg-allowed-attributes.
+property.prohibited-subtrees.synopsis=Specifies which subtrees are not exposed to clients. Each prohibited subtree must be subordinate to an allowed subtree.
+property.prohibited-subtrees.description=When this attribute is specified, all the listed subtrees cannot be accessed.
diff --git a/opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_ja.properties b/opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_ja.properties
new file mode 100644
index 0000000..ff4fddb
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_ja.properties
@@ -0,0 +1,28 @@
+user-friendly-name=Network Group Request Filtering Policy
+user-friendly-plural-name=Network Group Request Filtering Policies
+synopsis=The Network Group Request Filtering Policy is used to define the type of requests allowed in the network group.
+property.allowed-attributes.synopsis=Specifies which attributes are allowed in search and compare operations.
+property.allowed-attributes.description=When this attribute is specified, only the listed attributes are allowed in search and compare operations. If it is not set, all the attributes are allowed, except those listed in ds-cfg-prohibited-attributes.
+property.allowed-operations.synopsis=Specifies which operations are allowed in the network group.
+property.allowed-operations.description=When this attribute is specified, only the listed operations are allowed in the network group. If the attribute is not defined, all the operations are allowed.
+property.allowed-operations.syntax.enumeration.value.add.synopsis=Add operations.
+property.allowed-operations.syntax.enumeration.value.bind.synopsis=Bind operations.
+property.allowed-operations.syntax.enumeration.value.compare.synopsis=Compare operations
+property.allowed-operations.syntax.enumeration.value.delete.synopsis=Delete operations
+property.allowed-operations.syntax.enumeration.value.extended.synopsis=Extended operations
+property.allowed-operations.syntax.enumeration.value.inequality-search.synopsis=Inequality Search operations
+property.allowed-operations.syntax.enumeration.value.modify.synopsis=Modify operations
+property.allowed-operations.syntax.enumeration.value.rename.synopsis=Rename operations
+property.allowed-operations.syntax.enumeration.value.search.synopsis=Search operations
+property.allowed-search-scopes.synopsis=Specifies which search scopes are allowed in the network group.
+property.allowed-search-scopes.description=When this attribute is specified, only the listed scopes are allowed in the network group. If it is not set, all search scopes are allowed.
+property.allowed-search-scopes.syntax.enumeration.value.base.synopsis=Base-object search.
+property.allowed-search-scopes.syntax.enumeration.value.children.synopsis=Subordinate subtree search
+property.allowed-search-scopes.syntax.enumeration.value.one.synopsis=One-level search.
+property.allowed-search-scopes.syntax.enumeration.value.sub.synopsis=Whole subtree search
+property.allowed-subtrees.synopsis=Specifies which subtrees are exposed to clients.
+property.allowed-subtrees.description=When this attribute is specified, only the listed subtrees are exposed. If it is not set, all the substrees are exposed. Note that ds-cfg-prohibited-subtrees restricts the list of exposed subtrees.
+property.prohibited-attributes.synopsis=Specifies which attributes are not allowed in search and compare operations.
+property.prohibited-attributes.description=When this attribute is specified, all the listed attributes are prohibited in search and compare operations. It should not be used in conjunction with ds-cfg-allowed-attributes.
+property.prohibited-subtrees.synopsis=Specifies which subtrees are not exposed to clients. Each prohibited subtree must be subordinate to an allowed subtree.
+property.prohibited-subtrees.description=When this attribute is specified, all the listed subtrees cannot be accessed.
diff --git a/opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_ko.properties b/opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_ko.properties
new file mode 100644
index 0000000..ff4fddb
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_ko.properties
@@ -0,0 +1,28 @@
+user-friendly-name=Network Group Request Filtering Policy
+user-friendly-plural-name=Network Group Request Filtering Policies
+synopsis=The Network Group Request Filtering Policy is used to define the type of requests allowed in the network group.
+property.allowed-attributes.synopsis=Specifies which attributes are allowed in search and compare operations.
+property.allowed-attributes.description=When this attribute is specified, only the listed attributes are allowed in search and compare operations. If it is not set, all the attributes are allowed, except those listed in ds-cfg-prohibited-attributes.
+property.allowed-operations.synopsis=Specifies which operations are allowed in the network group.
+property.allowed-operations.description=When this attribute is specified, only the listed operations are allowed in the network group. If the attribute is not defined, all the operations are allowed.
+property.allowed-operations.syntax.enumeration.value.add.synopsis=Add operations.
+property.allowed-operations.syntax.enumeration.value.bind.synopsis=Bind operations.
+property.allowed-operations.syntax.enumeration.value.compare.synopsis=Compare operations
+property.allowed-operations.syntax.enumeration.value.delete.synopsis=Delete operations
+property.allowed-operations.syntax.enumeration.value.extended.synopsis=Extended operations
+property.allowed-operations.syntax.enumeration.value.inequality-search.synopsis=Inequality Search operations
+property.allowed-operations.syntax.enumeration.value.modify.synopsis=Modify operations
+property.allowed-operations.syntax.enumeration.value.rename.synopsis=Rename operations
+property.allowed-operations.syntax.enumeration.value.search.synopsis=Search operations
+property.allowed-search-scopes.synopsis=Specifies which search scopes are allowed in the network group.
+property.allowed-search-scopes.description=When this attribute is specified, only the listed scopes are allowed in the network group. If it is not set, all search scopes are allowed.
+property.allowed-search-scopes.syntax.enumeration.value.base.synopsis=Base-object search.
+property.allowed-search-scopes.syntax.enumeration.value.children.synopsis=Subordinate subtree search
+property.allowed-search-scopes.syntax.enumeration.value.one.synopsis=One-level search.
+property.allowed-search-scopes.syntax.enumeration.value.sub.synopsis=Whole subtree search
+property.allowed-subtrees.synopsis=Specifies which subtrees are exposed to clients.
+property.allowed-subtrees.description=When this attribute is specified, only the listed subtrees are exposed. If it is not set, all the substrees are exposed. Note that ds-cfg-prohibited-subtrees restricts the list of exposed subtrees.
+property.prohibited-attributes.synopsis=Specifies which attributes are not allowed in search and compare operations.
+property.prohibited-attributes.description=When this attribute is specified, all the listed attributes are prohibited in search and compare operations. It should not be used in conjunction with ds-cfg-allowed-attributes.
+property.prohibited-subtrees.synopsis=Specifies which subtrees are not exposed to clients. Each prohibited subtree must be subordinate to an allowed subtree.
+property.prohibited-subtrees.description=When this attribute is specified, all the listed subtrees cannot be accessed.
diff --git a/opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_zh_CN.properties b/opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..ff4fddb
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_zh_CN.properties
@@ -0,0 +1,28 @@
+user-friendly-name=Network Group Request Filtering Policy
+user-friendly-plural-name=Network Group Request Filtering Policies
+synopsis=The Network Group Request Filtering Policy is used to define the type of requests allowed in the network group.
+property.allowed-attributes.synopsis=Specifies which attributes are allowed in search and compare operations.
+property.allowed-attributes.description=When this attribute is specified, only the listed attributes are allowed in search and compare operations. If it is not set, all the attributes are allowed, except those listed in ds-cfg-prohibited-attributes.
+property.allowed-operations.synopsis=Specifies which operations are allowed in the network group.
+property.allowed-operations.description=When this attribute is specified, only the listed operations are allowed in the network group. If the attribute is not defined, all the operations are allowed.
+property.allowed-operations.syntax.enumeration.value.add.synopsis=Add operations.
+property.allowed-operations.syntax.enumeration.value.bind.synopsis=Bind operations.
+property.allowed-operations.syntax.enumeration.value.compare.synopsis=Compare operations
+property.allowed-operations.syntax.enumeration.value.delete.synopsis=Delete operations
+property.allowed-operations.syntax.enumeration.value.extended.synopsis=Extended operations
+property.allowed-operations.syntax.enumeration.value.inequality-search.synopsis=Inequality Search operations
+property.allowed-operations.syntax.enumeration.value.modify.synopsis=Modify operations
+property.allowed-operations.syntax.enumeration.value.rename.synopsis=Rename operations
+property.allowed-operations.syntax.enumeration.value.search.synopsis=Search operations
+property.allowed-search-scopes.synopsis=Specifies which search scopes are allowed in the network group.
+property.allowed-search-scopes.description=When this attribute is specified, only the listed scopes are allowed in the network group. If it is not set, all search scopes are allowed.
+property.allowed-search-scopes.syntax.enumeration.value.base.synopsis=Base-object search.
+property.allowed-search-scopes.syntax.enumeration.value.children.synopsis=Subordinate subtree search
+property.allowed-search-scopes.syntax.enumeration.value.one.synopsis=One-level search.
+property.allowed-search-scopes.syntax.enumeration.value.sub.synopsis=Whole subtree search
+property.allowed-subtrees.synopsis=Specifies which subtrees are exposed to clients.
+property.allowed-subtrees.description=When this attribute is specified, only the listed subtrees are exposed. If it is not set, all the substrees are exposed. Note that ds-cfg-prohibited-subtrees restricts the list of exposed subtrees.
+property.prohibited-attributes.synopsis=Specifies which attributes are not allowed in search and compare operations.
+property.prohibited-attributes.description=When this attribute is specified, all the listed attributes are prohibited in search and compare operations. It should not be used in conjunction with ds-cfg-allowed-attributes.
+property.prohibited-subtrees.synopsis=Specifies which subtrees are not exposed to clients. Each prohibited subtree must be subordinate to an allowed subtree.
+property.prohibited-subtrees.description=When this attribute is specified, all the listed subtrees cannot be accessed.
diff --git a/opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_zh_TW.properties b/opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..ff4fddb
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupRequestFilteringPolicyCfgDefn_zh_TW.properties
@@ -0,0 +1,28 @@
+user-friendly-name=Network Group Request Filtering Policy
+user-friendly-plural-name=Network Group Request Filtering Policies
+synopsis=The Network Group Request Filtering Policy is used to define the type of requests allowed in the network group.
+property.allowed-attributes.synopsis=Specifies which attributes are allowed in search and compare operations.
+property.allowed-attributes.description=When this attribute is specified, only the listed attributes are allowed in search and compare operations. If it is not set, all the attributes are allowed, except those listed in ds-cfg-prohibited-attributes.
+property.allowed-operations.synopsis=Specifies which operations are allowed in the network group.
+property.allowed-operations.description=When this attribute is specified, only the listed operations are allowed in the network group. If the attribute is not defined, all the operations are allowed.
+property.allowed-operations.syntax.enumeration.value.add.synopsis=Add operations.
+property.allowed-operations.syntax.enumeration.value.bind.synopsis=Bind operations.
+property.allowed-operations.syntax.enumeration.value.compare.synopsis=Compare operations
+property.allowed-operations.syntax.enumeration.value.delete.synopsis=Delete operations
+property.allowed-operations.syntax.enumeration.value.extended.synopsis=Extended operations
+property.allowed-operations.syntax.enumeration.value.inequality-search.synopsis=Inequality Search operations
+property.allowed-operations.syntax.enumeration.value.modify.synopsis=Modify operations
+property.allowed-operations.syntax.enumeration.value.rename.synopsis=Rename operations
+property.allowed-operations.syntax.enumeration.value.search.synopsis=Search operations
+property.allowed-search-scopes.synopsis=Specifies which search scopes are allowed in the network group.
+property.allowed-search-scopes.description=When this attribute is specified, only the listed scopes are allowed in the network group. If it is not set, all search scopes are allowed.
+property.allowed-search-scopes.syntax.enumeration.value.base.synopsis=Base-object search.
+property.allowed-search-scopes.syntax.enumeration.value.children.synopsis=Subordinate subtree search
+property.allowed-search-scopes.syntax.enumeration.value.one.synopsis=One-level search.
+property.allowed-search-scopes.syntax.enumeration.value.sub.synopsis=Whole subtree search
+property.allowed-subtrees.synopsis=Specifies which subtrees are exposed to clients.
+property.allowed-subtrees.description=When this attribute is specified, only the listed subtrees are exposed. If it is not set, all the substrees are exposed. Note that ds-cfg-prohibited-subtrees restricts the list of exposed subtrees.
+property.prohibited-attributes.synopsis=Specifies which attributes are not allowed in search and compare operations.
+property.prohibited-attributes.description=When this attribute is specified, all the listed attributes are prohibited in search and compare operations. It should not be used in conjunction with ds-cfg-allowed-attributes.
+property.prohibited-subtrees.synopsis=Specifies which subtrees are not exposed to clients. Each prohibited subtree must be subordinate to an allowed subtree.
+property.prohibited-subtrees.description=When this attribute is specified, all the listed subtrees cannot be accessed.
diff --git a/opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn.properties b/opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn.properties
new file mode 100644
index 0000000..40871fb
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn.properties
@@ -0,0 +1,30 @@
+user-friendly-name=Network Group Resource Limits
+user-friendly-plural-name=Network Group Resource Limits
+synopsis=The Network Group Resource Limits are used to define resource limits enforced by the network group.
+property.max-concurrent-ops-per-connection.synopsis=Specifies the maximum number of concurrent operations per connection.
+property.max-concurrent-ops-per-connection.description=A value of 0 means that no limit is enforced.
+property.max-connections.synopsis=Specifies the maximum number of connections in the network group.
+property.max-connections.description=A value of 0 means that no limit is enforced.
+property.max-connections-from-same-ip.synopsis=Specifies the maximum number of connections from the same client (identified by its IP address).
+property.max-connections-from-same-ip.description=A value of 0 means that no limit is enforced.
+property.max-ops-per-connection.synopsis=Specifies the maximum number of operations per connection.
+property.max-ops-per-connection.description=A value of 0 means that no limit is enforced.
+property.min-substring-length.synopsis=Specifies the minimum length for a search substring.
+property.min-substring-length.description=Search operations with short search substring are likely to match a high number of entries and might degrade performances. A value of 0 indicates that no limit is enforced.
+property.referral-bind-policy.synopsis=Specifies the referral bind policy.
+property.referral-bind-policy.description=The referral bind policy is used only when the referral policy is set to "follow". It specifies whether the referral is followed with the client bind DN and password or anonymously.
+property.referral-bind-policy.syntax.enumeration.value.anonymous.synopsis=Follow referrals anonymously.
+property.referral-bind-policy.syntax.enumeration.value.use-password.synopsis=Follow referrals with the client bind DN and password.
+property.referral-hop-limit.synopsis=Specifies the maximum number of hops when following referrals.
+property.referral-hop-limit.description=A value of 0 means that no limit is enforced.
+property.referral-policy.synopsis=Specifies the referral policy.
+property.referral-policy.description=The referral policy defines the behavior when a referral is received. The server can either discard the referral, forward the referral to the client or follow the referral.
+property.referral-policy.syntax.enumeration.value.discard.synopsis=Discard referrals.
+property.referral-policy.syntax.enumeration.value.follow.synopsis=Follow referrals
+property.referral-policy.syntax.enumeration.value.forward.synopsis=Forward referrals.
+property.search-size-limit.synopsis=Specifies the maximum number of entries that the Directory Server should return to the client during a search operation.
+property.search-size-limit.description=A value of 0 indicates that no size limit is enforced. Note that this is the network-group limit, but it may be overridden on a per-user basis.
+property.search-size-limit.default-behavior.alias.synopsis=Use the global default size limit.
+property.search-time-limit.synopsis=Specifies the maximum length of time that the Directory Server should spend processing a search operation.
+property.search-time-limit.description=A value of 0 seconds indicates that no time limit is enforced. Note that this is the network group time limit, but it may be overridden on a per-user basis.
+property.search-time-limit.default-behavior.alias.synopsis=Use the global default time limit.
diff --git a/opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_de.properties b/opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_de.properties
new file mode 100644
index 0000000..40871fb
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_de.properties
@@ -0,0 +1,30 @@
+user-friendly-name=Network Group Resource Limits
+user-friendly-plural-name=Network Group Resource Limits
+synopsis=The Network Group Resource Limits are used to define resource limits enforced by the network group.
+property.max-concurrent-ops-per-connection.synopsis=Specifies the maximum number of concurrent operations per connection.
+property.max-concurrent-ops-per-connection.description=A value of 0 means that no limit is enforced.
+property.max-connections.synopsis=Specifies the maximum number of connections in the network group.
+property.max-connections.description=A value of 0 means that no limit is enforced.
+property.max-connections-from-same-ip.synopsis=Specifies the maximum number of connections from the same client (identified by its IP address).
+property.max-connections-from-same-ip.description=A value of 0 means that no limit is enforced.
+property.max-ops-per-connection.synopsis=Specifies the maximum number of operations per connection.
+property.max-ops-per-connection.description=A value of 0 means that no limit is enforced.
+property.min-substring-length.synopsis=Specifies the minimum length for a search substring.
+property.min-substring-length.description=Search operations with short search substring are likely to match a high number of entries and might degrade performances. A value of 0 indicates that no limit is enforced.
+property.referral-bind-policy.synopsis=Specifies the referral bind policy.
+property.referral-bind-policy.description=The referral bind policy is used only when the referral policy is set to "follow". It specifies whether the referral is followed with the client bind DN and password or anonymously.
+property.referral-bind-policy.syntax.enumeration.value.anonymous.synopsis=Follow referrals anonymously.
+property.referral-bind-policy.syntax.enumeration.value.use-password.synopsis=Follow referrals with the client bind DN and password.
+property.referral-hop-limit.synopsis=Specifies the maximum number of hops when following referrals.
+property.referral-hop-limit.description=A value of 0 means that no limit is enforced.
+property.referral-policy.synopsis=Specifies the referral policy.
+property.referral-policy.description=The referral policy defines the behavior when a referral is received. The server can either discard the referral, forward the referral to the client or follow the referral.
+property.referral-policy.syntax.enumeration.value.discard.synopsis=Discard referrals.
+property.referral-policy.syntax.enumeration.value.follow.synopsis=Follow referrals
+property.referral-policy.syntax.enumeration.value.forward.synopsis=Forward referrals.
+property.search-size-limit.synopsis=Specifies the maximum number of entries that the Directory Server should return to the client during a search operation.
+property.search-size-limit.description=A value of 0 indicates that no size limit is enforced. Note that this is the network-group limit, but it may be overridden on a per-user basis.
+property.search-size-limit.default-behavior.alias.synopsis=Use the global default size limit.
+property.search-time-limit.synopsis=Specifies the maximum length of time that the Directory Server should spend processing a search operation.
+property.search-time-limit.description=A value of 0 seconds indicates that no time limit is enforced. Note that this is the network group time limit, but it may be overridden on a per-user basis.
+property.search-time-limit.default-behavior.alias.synopsis=Use the global default time limit.
diff --git a/opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_es.properties b/opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_es.properties
new file mode 100644
index 0000000..40871fb
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_es.properties
@@ -0,0 +1,30 @@
+user-friendly-name=Network Group Resource Limits
+user-friendly-plural-name=Network Group Resource Limits
+synopsis=The Network Group Resource Limits are used to define resource limits enforced by the network group.
+property.max-concurrent-ops-per-connection.synopsis=Specifies the maximum number of concurrent operations per connection.
+property.max-concurrent-ops-per-connection.description=A value of 0 means that no limit is enforced.
+property.max-connections.synopsis=Specifies the maximum number of connections in the network group.
+property.max-connections.description=A value of 0 means that no limit is enforced.
+property.max-connections-from-same-ip.synopsis=Specifies the maximum number of connections from the same client (identified by its IP address).
+property.max-connections-from-same-ip.description=A value of 0 means that no limit is enforced.
+property.max-ops-per-connection.synopsis=Specifies the maximum number of operations per connection.
+property.max-ops-per-connection.description=A value of 0 means that no limit is enforced.
+property.min-substring-length.synopsis=Specifies the minimum length for a search substring.
+property.min-substring-length.description=Search operations with short search substring are likely to match a high number of entries and might degrade performances. A value of 0 indicates that no limit is enforced.
+property.referral-bind-policy.synopsis=Specifies the referral bind policy.
+property.referral-bind-policy.description=The referral bind policy is used only when the referral policy is set to "follow". It specifies whether the referral is followed with the client bind DN and password or anonymously.
+property.referral-bind-policy.syntax.enumeration.value.anonymous.synopsis=Follow referrals anonymously.
+property.referral-bind-policy.syntax.enumeration.value.use-password.synopsis=Follow referrals with the client bind DN and password.
+property.referral-hop-limit.synopsis=Specifies the maximum number of hops when following referrals.
+property.referral-hop-limit.description=A value of 0 means that no limit is enforced.
+property.referral-policy.synopsis=Specifies the referral policy.
+property.referral-policy.description=The referral policy defines the behavior when a referral is received. The server can either discard the referral, forward the referral to the client or follow the referral.
+property.referral-policy.syntax.enumeration.value.discard.synopsis=Discard referrals.
+property.referral-policy.syntax.enumeration.value.follow.synopsis=Follow referrals
+property.referral-policy.syntax.enumeration.value.forward.synopsis=Forward referrals.
+property.search-size-limit.synopsis=Specifies the maximum number of entries that the Directory Server should return to the client during a search operation.
+property.search-size-limit.description=A value of 0 indicates that no size limit is enforced. Note that this is the network-group limit, but it may be overridden on a per-user basis.
+property.search-size-limit.default-behavior.alias.synopsis=Use the global default size limit.
+property.search-time-limit.synopsis=Specifies the maximum length of time that the Directory Server should spend processing a search operation.
+property.search-time-limit.description=A value of 0 seconds indicates that no time limit is enforced. Note that this is the network group time limit, but it may be overridden on a per-user basis.
+property.search-time-limit.default-behavior.alias.synopsis=Use the global default time limit.
diff --git a/opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_fr.properties b/opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_fr.properties
new file mode 100644
index 0000000..40871fb
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_fr.properties
@@ -0,0 +1,30 @@
+user-friendly-name=Network Group Resource Limits
+user-friendly-plural-name=Network Group Resource Limits
+synopsis=The Network Group Resource Limits are used to define resource limits enforced by the network group.
+property.max-concurrent-ops-per-connection.synopsis=Specifies the maximum number of concurrent operations per connection.
+property.max-concurrent-ops-per-connection.description=A value of 0 means that no limit is enforced.
+property.max-connections.synopsis=Specifies the maximum number of connections in the network group.
+property.max-connections.description=A value of 0 means that no limit is enforced.
+property.max-connections-from-same-ip.synopsis=Specifies the maximum number of connections from the same client (identified by its IP address).
+property.max-connections-from-same-ip.description=A value of 0 means that no limit is enforced.
+property.max-ops-per-connection.synopsis=Specifies the maximum number of operations per connection.
+property.max-ops-per-connection.description=A value of 0 means that no limit is enforced.
+property.min-substring-length.synopsis=Specifies the minimum length for a search substring.
+property.min-substring-length.description=Search operations with short search substring are likely to match a high number of entries and might degrade performances. A value of 0 indicates that no limit is enforced.
+property.referral-bind-policy.synopsis=Specifies the referral bind policy.
+property.referral-bind-policy.description=The referral bind policy is used only when the referral policy is set to "follow". It specifies whether the referral is followed with the client bind DN and password or anonymously.
+property.referral-bind-policy.syntax.enumeration.value.anonymous.synopsis=Follow referrals anonymously.
+property.referral-bind-policy.syntax.enumeration.value.use-password.synopsis=Follow referrals with the client bind DN and password.
+property.referral-hop-limit.synopsis=Specifies the maximum number of hops when following referrals.
+property.referral-hop-limit.description=A value of 0 means that no limit is enforced.
+property.referral-policy.synopsis=Specifies the referral policy.
+property.referral-policy.description=The referral policy defines the behavior when a referral is received. The server can either discard the referral, forward the referral to the client or follow the referral.
+property.referral-policy.syntax.enumeration.value.discard.synopsis=Discard referrals.
+property.referral-policy.syntax.enumeration.value.follow.synopsis=Follow referrals
+property.referral-policy.syntax.enumeration.value.forward.synopsis=Forward referrals.
+property.search-size-limit.synopsis=Specifies the maximum number of entries that the Directory Server should return to the client during a search operation.
+property.search-size-limit.description=A value of 0 indicates that no size limit is enforced. Note that this is the network-group limit, but it may be overridden on a per-user basis.
+property.search-size-limit.default-behavior.alias.synopsis=Use the global default size limit.
+property.search-time-limit.synopsis=Specifies the maximum length of time that the Directory Server should spend processing a search operation.
+property.search-time-limit.description=A value of 0 seconds indicates that no time limit is enforced. Note that this is the network group time limit, but it may be overridden on a per-user basis.
+property.search-time-limit.default-behavior.alias.synopsis=Use the global default time limit.
diff --git a/opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_ja.properties b/opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_ja.properties
new file mode 100644
index 0000000..40871fb
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_ja.properties
@@ -0,0 +1,30 @@
+user-friendly-name=Network Group Resource Limits
+user-friendly-plural-name=Network Group Resource Limits
+synopsis=The Network Group Resource Limits are used to define resource limits enforced by the network group.
+property.max-concurrent-ops-per-connection.synopsis=Specifies the maximum number of concurrent operations per connection.
+property.max-concurrent-ops-per-connection.description=A value of 0 means that no limit is enforced.
+property.max-connections.synopsis=Specifies the maximum number of connections in the network group.
+property.max-connections.description=A value of 0 means that no limit is enforced.
+property.max-connections-from-same-ip.synopsis=Specifies the maximum number of connections from the same client (identified by its IP address).
+property.max-connections-from-same-ip.description=A value of 0 means that no limit is enforced.
+property.max-ops-per-connection.synopsis=Specifies the maximum number of operations per connection.
+property.max-ops-per-connection.description=A value of 0 means that no limit is enforced.
+property.min-substring-length.synopsis=Specifies the minimum length for a search substring.
+property.min-substring-length.description=Search operations with short search substring are likely to match a high number of entries and might degrade performances. A value of 0 indicates that no limit is enforced.
+property.referral-bind-policy.synopsis=Specifies the referral bind policy.
+property.referral-bind-policy.description=The referral bind policy is used only when the referral policy is set to "follow". It specifies whether the referral is followed with the client bind DN and password or anonymously.
+property.referral-bind-policy.syntax.enumeration.value.anonymous.synopsis=Follow referrals anonymously.
+property.referral-bind-policy.syntax.enumeration.value.use-password.synopsis=Follow referrals with the client bind DN and password.
+property.referral-hop-limit.synopsis=Specifies the maximum number of hops when following referrals.
+property.referral-hop-limit.description=A value of 0 means that no limit is enforced.
+property.referral-policy.synopsis=Specifies the referral policy.
+property.referral-policy.description=The referral policy defines the behavior when a referral is received. The server can either discard the referral, forward the referral to the client or follow the referral.
+property.referral-policy.syntax.enumeration.value.discard.synopsis=Discard referrals.
+property.referral-policy.syntax.enumeration.value.follow.synopsis=Follow referrals
+property.referral-policy.syntax.enumeration.value.forward.synopsis=Forward referrals.
+property.search-size-limit.synopsis=Specifies the maximum number of entries that the Directory Server should return to the client during a search operation.
+property.search-size-limit.description=A value of 0 indicates that no size limit is enforced. Note that this is the network-group limit, but it may be overridden on a per-user basis.
+property.search-size-limit.default-behavior.alias.synopsis=Use the global default size limit.
+property.search-time-limit.synopsis=Specifies the maximum length of time that the Directory Server should spend processing a search operation.
+property.search-time-limit.description=A value of 0 seconds indicates that no time limit is enforced. Note that this is the network group time limit, but it may be overridden on a per-user basis.
+property.search-time-limit.default-behavior.alias.synopsis=Use the global default time limit.
diff --git a/opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_ko.properties b/opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_ko.properties
new file mode 100644
index 0000000..40871fb
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_ko.properties
@@ -0,0 +1,30 @@
+user-friendly-name=Network Group Resource Limits
+user-friendly-plural-name=Network Group Resource Limits
+synopsis=The Network Group Resource Limits are used to define resource limits enforced by the network group.
+property.max-concurrent-ops-per-connection.synopsis=Specifies the maximum number of concurrent operations per connection.
+property.max-concurrent-ops-per-connection.description=A value of 0 means that no limit is enforced.
+property.max-connections.synopsis=Specifies the maximum number of connections in the network group.
+property.max-connections.description=A value of 0 means that no limit is enforced.
+property.max-connections-from-same-ip.synopsis=Specifies the maximum number of connections from the same client (identified by its IP address).
+property.max-connections-from-same-ip.description=A value of 0 means that no limit is enforced.
+property.max-ops-per-connection.synopsis=Specifies the maximum number of operations per connection.
+property.max-ops-per-connection.description=A value of 0 means that no limit is enforced.
+property.min-substring-length.synopsis=Specifies the minimum length for a search substring.
+property.min-substring-length.description=Search operations with short search substring are likely to match a high number of entries and might degrade performances. A value of 0 indicates that no limit is enforced.
+property.referral-bind-policy.synopsis=Specifies the referral bind policy.
+property.referral-bind-policy.description=The referral bind policy is used only when the referral policy is set to "follow". It specifies whether the referral is followed with the client bind DN and password or anonymously.
+property.referral-bind-policy.syntax.enumeration.value.anonymous.synopsis=Follow referrals anonymously.
+property.referral-bind-policy.syntax.enumeration.value.use-password.synopsis=Follow referrals with the client bind DN and password.
+property.referral-hop-limit.synopsis=Specifies the maximum number of hops when following referrals.
+property.referral-hop-limit.description=A value of 0 means that no limit is enforced.
+property.referral-policy.synopsis=Specifies the referral policy.
+property.referral-policy.description=The referral policy defines the behavior when a referral is received. The server can either discard the referral, forward the referral to the client or follow the referral.
+property.referral-policy.syntax.enumeration.value.discard.synopsis=Discard referrals.
+property.referral-policy.syntax.enumeration.value.follow.synopsis=Follow referrals
+property.referral-policy.syntax.enumeration.value.forward.synopsis=Forward referrals.
+property.search-size-limit.synopsis=Specifies the maximum number of entries that the Directory Server should return to the client during a search operation.
+property.search-size-limit.description=A value of 0 indicates that no size limit is enforced. Note that this is the network-group limit, but it may be overridden on a per-user basis.
+property.search-size-limit.default-behavior.alias.synopsis=Use the global default size limit.
+property.search-time-limit.synopsis=Specifies the maximum length of time that the Directory Server should spend processing a search operation.
+property.search-time-limit.description=A value of 0 seconds indicates that no time limit is enforced. Note that this is the network group time limit, but it may be overridden on a per-user basis.
+property.search-time-limit.default-behavior.alias.synopsis=Use the global default time limit.
diff --git a/opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_zh_CN.properties b/opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..40871fb
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_zh_CN.properties
@@ -0,0 +1,30 @@
+user-friendly-name=Network Group Resource Limits
+user-friendly-plural-name=Network Group Resource Limits
+synopsis=The Network Group Resource Limits are used to define resource limits enforced by the network group.
+property.max-concurrent-ops-per-connection.synopsis=Specifies the maximum number of concurrent operations per connection.
+property.max-concurrent-ops-per-connection.description=A value of 0 means that no limit is enforced.
+property.max-connections.synopsis=Specifies the maximum number of connections in the network group.
+property.max-connections.description=A value of 0 means that no limit is enforced.
+property.max-connections-from-same-ip.synopsis=Specifies the maximum number of connections from the same client (identified by its IP address).
+property.max-connections-from-same-ip.description=A value of 0 means that no limit is enforced.
+property.max-ops-per-connection.synopsis=Specifies the maximum number of operations per connection.
+property.max-ops-per-connection.description=A value of 0 means that no limit is enforced.
+property.min-substring-length.synopsis=Specifies the minimum length for a search substring.
+property.min-substring-length.description=Search operations with short search substring are likely to match a high number of entries and might degrade performances. A value of 0 indicates that no limit is enforced.
+property.referral-bind-policy.synopsis=Specifies the referral bind policy.
+property.referral-bind-policy.description=The referral bind policy is used only when the referral policy is set to "follow". It specifies whether the referral is followed with the client bind DN and password or anonymously.
+property.referral-bind-policy.syntax.enumeration.value.anonymous.synopsis=Follow referrals anonymously.
+property.referral-bind-policy.syntax.enumeration.value.use-password.synopsis=Follow referrals with the client bind DN and password.
+property.referral-hop-limit.synopsis=Specifies the maximum number of hops when following referrals.
+property.referral-hop-limit.description=A value of 0 means that no limit is enforced.
+property.referral-policy.synopsis=Specifies the referral policy.
+property.referral-policy.description=The referral policy defines the behavior when a referral is received. The server can either discard the referral, forward the referral to the client or follow the referral.
+property.referral-policy.syntax.enumeration.value.discard.synopsis=Discard referrals.
+property.referral-policy.syntax.enumeration.value.follow.synopsis=Follow referrals
+property.referral-policy.syntax.enumeration.value.forward.synopsis=Forward referrals.
+property.search-size-limit.synopsis=Specifies the maximum number of entries that the Directory Server should return to the client during a search operation.
+property.search-size-limit.description=A value of 0 indicates that no size limit is enforced. Note that this is the network-group limit, but it may be overridden on a per-user basis.
+property.search-size-limit.default-behavior.alias.synopsis=Use the global default size limit.
+property.search-time-limit.synopsis=Specifies the maximum length of time that the Directory Server should spend processing a search operation.
+property.search-time-limit.description=A value of 0 seconds indicates that no time limit is enforced. Note that this is the network group time limit, but it may be overridden on a per-user basis.
+property.search-time-limit.default-behavior.alias.synopsis=Use the global default time limit.
diff --git a/opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_zh_TW.properties b/opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..40871fb
--- /dev/null
+++ b/opends/src/admin/messages/NetworkGroupResourceLimitsCfgDefn_zh_TW.properties
@@ -0,0 +1,30 @@
+user-friendly-name=Network Group Resource Limits
+user-friendly-plural-name=Network Group Resource Limits
+synopsis=The Network Group Resource Limits are used to define resource limits enforced by the network group.
+property.max-concurrent-ops-per-connection.synopsis=Specifies the maximum number of concurrent operations per connection.
+property.max-concurrent-ops-per-connection.description=A value of 0 means that no limit is enforced.
+property.max-connections.synopsis=Specifies the maximum number of connections in the network group.
+property.max-connections.description=A value of 0 means that no limit is enforced.
+property.max-connections-from-same-ip.synopsis=Specifies the maximum number of connections from the same client (identified by its IP address).
+property.max-connections-from-same-ip.description=A value of 0 means that no limit is enforced.
+property.max-ops-per-connection.synopsis=Specifies the maximum number of operations per connection.
+property.max-ops-per-connection.description=A value of 0 means that no limit is enforced.
+property.min-substring-length.synopsis=Specifies the minimum length for a search substring.
+property.min-substring-length.description=Search operations with short search substring are likely to match a high number of entries and might degrade performances. A value of 0 indicates that no limit is enforced.
+property.referral-bind-policy.synopsis=Specifies the referral bind policy.
+property.referral-bind-policy.description=The referral bind policy is used only when the referral policy is set to "follow". It specifies whether the referral is followed with the client bind DN and password or anonymously.
+property.referral-bind-policy.syntax.enumeration.value.anonymous.synopsis=Follow referrals anonymously.
+property.referral-bind-policy.syntax.enumeration.value.use-password.synopsis=Follow referrals with the client bind DN and password.
+property.referral-hop-limit.synopsis=Specifies the maximum number of hops when following referrals.
+property.referral-hop-limit.description=A value of 0 means that no limit is enforced.
+property.referral-policy.synopsis=Specifies the referral policy.
+property.referral-policy.description=The referral policy defines the behavior when a referral is received. The server can either discard the referral, forward the referral to the client or follow the referral.
+property.referral-policy.syntax.enumeration.value.discard.synopsis=Discard referrals.
+property.referral-policy.syntax.enumeration.value.follow.synopsis=Follow referrals
+property.referral-policy.syntax.enumeration.value.forward.synopsis=Forward referrals.
+property.search-size-limit.synopsis=Specifies the maximum number of entries that the Directory Server should return to the client during a search operation.
+property.search-size-limit.description=A value of 0 indicates that no size limit is enforced. Note that this is the network-group limit, but it may be overridden on a per-user basis.
+property.search-size-limit.default-behavior.alias.synopsis=Use the global default size limit.
+property.search-time-limit.synopsis=Specifies the maximum length of time that the Directory Server should spend processing a search operation.
+property.search-time-limit.description=A value of 0 seconds indicates that no time limit is enforced. Note that this is the network group time limit, but it may be overridden on a per-user basis.
+property.search-time-limit.default-behavior.alias.synopsis=Use the global default time limit.
diff --git a/opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn.properties b/opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn.properties
new file mode 100644
index 0000000..3edbb9b
--- /dev/null
+++ b/opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Num Subordinates Virtual Attribute
+user-friendly-plural-name=Num Subordinates Virtual Attributes
+synopsis=The Num Subordinates Virtual Attribute generates a virtual attribute that specifies the number of immediate child entries that exist below the entry.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Num Subordinates Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_de.properties b/opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_de.properties
new file mode 100644
index 0000000..3edbb9b
--- /dev/null
+++ b/opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_de.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Num Subordinates Virtual Attribute
+user-friendly-plural-name=Num Subordinates Virtual Attributes
+synopsis=The Num Subordinates Virtual Attribute generates a virtual attribute that specifies the number of immediate child entries that exist below the entry.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Num Subordinates Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_es.properties b/opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_es.properties
new file mode 100644
index 0000000..3edbb9b
--- /dev/null
+++ b/opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_es.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Num Subordinates Virtual Attribute
+user-friendly-plural-name=Num Subordinates Virtual Attributes
+synopsis=The Num Subordinates Virtual Attribute generates a virtual attribute that specifies the number of immediate child entries that exist below the entry.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Num Subordinates Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_fr.properties b/opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_fr.properties
new file mode 100644
index 0000000..3edbb9b
--- /dev/null
+++ b/opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_fr.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Num Subordinates Virtual Attribute
+user-friendly-plural-name=Num Subordinates Virtual Attributes
+synopsis=The Num Subordinates Virtual Attribute generates a virtual attribute that specifies the number of immediate child entries that exist below the entry.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Num Subordinates Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_ja.properties b/opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_ja.properties
new file mode 100644
index 0000000..3edbb9b
--- /dev/null
+++ b/opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_ja.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Num Subordinates Virtual Attribute
+user-friendly-plural-name=Num Subordinates Virtual Attributes
+synopsis=The Num Subordinates Virtual Attribute generates a virtual attribute that specifies the number of immediate child entries that exist below the entry.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Num Subordinates Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_ko.properties b/opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_ko.properties
new file mode 100644
index 0000000..3edbb9b
--- /dev/null
+++ b/opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_ko.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Num Subordinates Virtual Attribute
+user-friendly-plural-name=Num Subordinates Virtual Attributes
+synopsis=The Num Subordinates Virtual Attribute generates a virtual attribute that specifies the number of immediate child entries that exist below the entry.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Num Subordinates Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_zh_CN.properties b/opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..3edbb9b
--- /dev/null
+++ b/opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_zh_CN.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Num Subordinates Virtual Attribute
+user-friendly-plural-name=Num Subordinates Virtual Attributes
+synopsis=The Num Subordinates Virtual Attribute generates a virtual attribute that specifies the number of immediate child entries that exist below the entry.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Num Subordinates Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_zh_TW.properties b/opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..3edbb9b
--- /dev/null
+++ b/opends/src/admin/messages/NumSubordinatesVirtualAttributeCfgDefn_zh_TW.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Num Subordinates Virtual Attribute
+user-friendly-plural-name=Num Subordinates Virtual Attributes
+synopsis=The Num Subordinates Virtual Attribute generates a virtual attribute that specifies the number of immediate child entries that exist below the entry.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Num Subordinates Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/OrderingMatchingRuleCfgDefn.properties b/opends/src/admin/messages/OrderingMatchingRuleCfgDefn.properties
new file mode 100644
index 0000000..6411eb8
--- /dev/null
+++ b/opends/src/admin/messages/OrderingMatchingRuleCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Ordering Matching Rule
+user-friendly-plural-name=Ordering Matching Rules
+synopsis=Ordering Matching Rules define a set of rules for performing ordering matching operations against assertion values.
+description=These matching rules are used for greater-than-or-equal and less-than-or-equal comparisons, as well as for sorting.
+property.enabled.synopsis=Indicates whether the Ordering Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Ordering Matching Rule implementation.
diff --git a/opends/src/admin/messages/OrderingMatchingRuleCfgDefn_de.properties b/opends/src/admin/messages/OrderingMatchingRuleCfgDefn_de.properties
new file mode 100644
index 0000000..6411eb8
--- /dev/null
+++ b/opends/src/admin/messages/OrderingMatchingRuleCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Ordering Matching Rule
+user-friendly-plural-name=Ordering Matching Rules
+synopsis=Ordering Matching Rules define a set of rules for performing ordering matching operations against assertion values.
+description=These matching rules are used for greater-than-or-equal and less-than-or-equal comparisons, as well as for sorting.
+property.enabled.synopsis=Indicates whether the Ordering Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Ordering Matching Rule implementation.
diff --git a/opends/src/admin/messages/OrderingMatchingRuleCfgDefn_es.properties b/opends/src/admin/messages/OrderingMatchingRuleCfgDefn_es.properties
new file mode 100644
index 0000000..6411eb8
--- /dev/null
+++ b/opends/src/admin/messages/OrderingMatchingRuleCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Ordering Matching Rule
+user-friendly-plural-name=Ordering Matching Rules
+synopsis=Ordering Matching Rules define a set of rules for performing ordering matching operations against assertion values.
+description=These matching rules are used for greater-than-or-equal and less-than-or-equal comparisons, as well as for sorting.
+property.enabled.synopsis=Indicates whether the Ordering Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Ordering Matching Rule implementation.
diff --git a/opends/src/admin/messages/OrderingMatchingRuleCfgDefn_fr.properties b/opends/src/admin/messages/OrderingMatchingRuleCfgDefn_fr.properties
new file mode 100644
index 0000000..6411eb8
--- /dev/null
+++ b/opends/src/admin/messages/OrderingMatchingRuleCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Ordering Matching Rule
+user-friendly-plural-name=Ordering Matching Rules
+synopsis=Ordering Matching Rules define a set of rules for performing ordering matching operations against assertion values.
+description=These matching rules are used for greater-than-or-equal and less-than-or-equal comparisons, as well as for sorting.
+property.enabled.synopsis=Indicates whether the Ordering Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Ordering Matching Rule implementation.
diff --git a/opends/src/admin/messages/OrderingMatchingRuleCfgDefn_ja.properties b/opends/src/admin/messages/OrderingMatchingRuleCfgDefn_ja.properties
new file mode 100644
index 0000000..6411eb8
--- /dev/null
+++ b/opends/src/admin/messages/OrderingMatchingRuleCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Ordering Matching Rule
+user-friendly-plural-name=Ordering Matching Rules
+synopsis=Ordering Matching Rules define a set of rules for performing ordering matching operations against assertion values.
+description=These matching rules are used for greater-than-or-equal and less-than-or-equal comparisons, as well as for sorting.
+property.enabled.synopsis=Indicates whether the Ordering Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Ordering Matching Rule implementation.
diff --git a/opends/src/admin/messages/OrderingMatchingRuleCfgDefn_ko.properties b/opends/src/admin/messages/OrderingMatchingRuleCfgDefn_ko.properties
new file mode 100644
index 0000000..6411eb8
--- /dev/null
+++ b/opends/src/admin/messages/OrderingMatchingRuleCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Ordering Matching Rule
+user-friendly-plural-name=Ordering Matching Rules
+synopsis=Ordering Matching Rules define a set of rules for performing ordering matching operations against assertion values.
+description=These matching rules are used for greater-than-or-equal and less-than-or-equal comparisons, as well as for sorting.
+property.enabled.synopsis=Indicates whether the Ordering Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Ordering Matching Rule implementation.
diff --git a/opends/src/admin/messages/OrderingMatchingRuleCfgDefn_zh_CN.properties b/opends/src/admin/messages/OrderingMatchingRuleCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..6411eb8
--- /dev/null
+++ b/opends/src/admin/messages/OrderingMatchingRuleCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Ordering Matching Rule
+user-friendly-plural-name=Ordering Matching Rules
+synopsis=Ordering Matching Rules define a set of rules for performing ordering matching operations against assertion values.
+description=These matching rules are used for greater-than-or-equal and less-than-or-equal comparisons, as well as for sorting.
+property.enabled.synopsis=Indicates whether the Ordering Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Ordering Matching Rule implementation.
diff --git a/opends/src/admin/messages/OrderingMatchingRuleCfgDefn_zh_TW.properties b/opends/src/admin/messages/OrderingMatchingRuleCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..6411eb8
--- /dev/null
+++ b/opends/src/admin/messages/OrderingMatchingRuleCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Ordering Matching Rule
+user-friendly-plural-name=Ordering Matching Rules
+synopsis=Ordering Matching Rules define a set of rules for performing ordering matching operations against assertion values.
+description=These matching rules are used for greater-than-or-equal and less-than-or-equal comparisons, as well as for sorting.
+property.enabled.synopsis=Indicates whether the Ordering Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Ordering Matching Rule implementation.
diff --git a/opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn.properties b/opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn.properties
new file mode 100644
index 0000000..2cf098a
--- /dev/null
+++ b/opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn.properties
@@ -0,0 +1,18 @@
+user-friendly-name=PKCS11 Key Manager Provider
+user-friendly-plural-name=PKCS11 Key Manager Providers
+synopsis=The PKCS11 Key Manager Provider enables the server to access the private key information through the PKCS11 interface.
+description=This standard interface is used by cryptographic accelerators and hardware security modules.
+constraint.1.synopsis=The key store pin must be specified using one of the key-store-pin properties when the PKCS11 Key Manager Provider is enabled.
+property.enabled.synopsis=Indicates whether the PKCS11 Key Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the PKCS11 Key Manager Provider implementation.
+property.key-store-pin.synopsis=Specifies the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.syntax.string.pattern.synopsis=The name of a defined environment variable that contains the clear-text PIN required to access the contents of the key store.
+property.key-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.key-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-property.syntax.string.pattern.synopsis=The name of a defined Java property.
diff --git a/opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_de.properties b/opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_de.properties
new file mode 100644
index 0000000..2cf098a
--- /dev/null
+++ b/opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_de.properties
@@ -0,0 +1,18 @@
+user-friendly-name=PKCS11 Key Manager Provider
+user-friendly-plural-name=PKCS11 Key Manager Providers
+synopsis=The PKCS11 Key Manager Provider enables the server to access the private key information through the PKCS11 interface.
+description=This standard interface is used by cryptographic accelerators and hardware security modules.
+constraint.1.synopsis=The key store pin must be specified using one of the key-store-pin properties when the PKCS11 Key Manager Provider is enabled.
+property.enabled.synopsis=Indicates whether the PKCS11 Key Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the PKCS11 Key Manager Provider implementation.
+property.key-store-pin.synopsis=Specifies the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.syntax.string.pattern.synopsis=The name of a defined environment variable that contains the clear-text PIN required to access the contents of the key store.
+property.key-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.key-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-property.syntax.string.pattern.synopsis=The name of a defined Java property.
diff --git a/opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_es.properties b/opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_es.properties
new file mode 100644
index 0000000..2cf098a
--- /dev/null
+++ b/opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_es.properties
@@ -0,0 +1,18 @@
+user-friendly-name=PKCS11 Key Manager Provider
+user-friendly-plural-name=PKCS11 Key Manager Providers
+synopsis=The PKCS11 Key Manager Provider enables the server to access the private key information through the PKCS11 interface.
+description=This standard interface is used by cryptographic accelerators and hardware security modules.
+constraint.1.synopsis=The key store pin must be specified using one of the key-store-pin properties when the PKCS11 Key Manager Provider is enabled.
+property.enabled.synopsis=Indicates whether the PKCS11 Key Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the PKCS11 Key Manager Provider implementation.
+property.key-store-pin.synopsis=Specifies the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.syntax.string.pattern.synopsis=The name of a defined environment variable that contains the clear-text PIN required to access the contents of the key store.
+property.key-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.key-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-property.syntax.string.pattern.synopsis=The name of a defined Java property.
diff --git a/opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_fr.properties b/opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_fr.properties
new file mode 100644
index 0000000..2cf098a
--- /dev/null
+++ b/opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_fr.properties
@@ -0,0 +1,18 @@
+user-friendly-name=PKCS11 Key Manager Provider
+user-friendly-plural-name=PKCS11 Key Manager Providers
+synopsis=The PKCS11 Key Manager Provider enables the server to access the private key information through the PKCS11 interface.
+description=This standard interface is used by cryptographic accelerators and hardware security modules.
+constraint.1.synopsis=The key store pin must be specified using one of the key-store-pin properties when the PKCS11 Key Manager Provider is enabled.
+property.enabled.synopsis=Indicates whether the PKCS11 Key Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the PKCS11 Key Manager Provider implementation.
+property.key-store-pin.synopsis=Specifies the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.syntax.string.pattern.synopsis=The name of a defined environment variable that contains the clear-text PIN required to access the contents of the key store.
+property.key-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.key-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-property.syntax.string.pattern.synopsis=The name of a defined Java property.
diff --git a/opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_ja.properties b/opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_ja.properties
new file mode 100644
index 0000000..2cf098a
--- /dev/null
+++ b/opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_ja.properties
@@ -0,0 +1,18 @@
+user-friendly-name=PKCS11 Key Manager Provider
+user-friendly-plural-name=PKCS11 Key Manager Providers
+synopsis=The PKCS11 Key Manager Provider enables the server to access the private key information through the PKCS11 interface.
+description=This standard interface is used by cryptographic accelerators and hardware security modules.
+constraint.1.synopsis=The key store pin must be specified using one of the key-store-pin properties when the PKCS11 Key Manager Provider is enabled.
+property.enabled.synopsis=Indicates whether the PKCS11 Key Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the PKCS11 Key Manager Provider implementation.
+property.key-store-pin.synopsis=Specifies the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.syntax.string.pattern.synopsis=The name of a defined environment variable that contains the clear-text PIN required to access the contents of the key store.
+property.key-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.key-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-property.syntax.string.pattern.synopsis=The name of a defined Java property.
diff --git a/opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_ko.properties b/opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_ko.properties
new file mode 100644
index 0000000..2cf098a
--- /dev/null
+++ b/opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_ko.properties
@@ -0,0 +1,18 @@
+user-friendly-name=PKCS11 Key Manager Provider
+user-friendly-plural-name=PKCS11 Key Manager Providers
+synopsis=The PKCS11 Key Manager Provider enables the server to access the private key information through the PKCS11 interface.
+description=This standard interface is used by cryptographic accelerators and hardware security modules.
+constraint.1.synopsis=The key store pin must be specified using one of the key-store-pin properties when the PKCS11 Key Manager Provider is enabled.
+property.enabled.synopsis=Indicates whether the PKCS11 Key Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the PKCS11 Key Manager Provider implementation.
+property.key-store-pin.synopsis=Specifies the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.syntax.string.pattern.synopsis=The name of a defined environment variable that contains the clear-text PIN required to access the contents of the key store.
+property.key-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.key-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-property.syntax.string.pattern.synopsis=The name of a defined Java property.
diff --git a/opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_zh_CN.properties b/opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..2cf098a
--- /dev/null
+++ b/opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_zh_CN.properties
@@ -0,0 +1,18 @@
+user-friendly-name=PKCS11 Key Manager Provider
+user-friendly-plural-name=PKCS11 Key Manager Providers
+synopsis=The PKCS11 Key Manager Provider enables the server to access the private key information through the PKCS11 interface.
+description=This standard interface is used by cryptographic accelerators and hardware security modules.
+constraint.1.synopsis=The key store pin must be specified using one of the key-store-pin properties when the PKCS11 Key Manager Provider is enabled.
+property.enabled.synopsis=Indicates whether the PKCS11 Key Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the PKCS11 Key Manager Provider implementation.
+property.key-store-pin.synopsis=Specifies the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.syntax.string.pattern.synopsis=The name of a defined environment variable that contains the clear-text PIN required to access the contents of the key store.
+property.key-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.key-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-property.syntax.string.pattern.synopsis=The name of a defined Java property.
diff --git a/opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_zh_TW.properties b/opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..2cf098a
--- /dev/null
+++ b/opends/src/admin/messages/PKCS11KeyManagerProviderCfgDefn_zh_TW.properties
@@ -0,0 +1,18 @@
+user-friendly-name=PKCS11 Key Manager Provider
+user-friendly-plural-name=PKCS11 Key Manager Providers
+synopsis=The PKCS11 Key Manager Provider enables the server to access the private key information through the PKCS11 interface.
+description=This standard interface is used by cryptographic accelerators and hardware security modules.
+constraint.1.synopsis=The key store pin must be specified using one of the key-store-pin properties when the PKCS11 Key Manager Provider is enabled.
+property.enabled.synopsis=Indicates whether the PKCS11 Key Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the PKCS11 Key Manager Provider implementation.
+property.key-store-pin.synopsis=Specifies the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-environment-variable.syntax.string.pattern.synopsis=The name of a defined environment variable that contains the clear-text PIN required to access the contents of the key store.
+property.key-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.key-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the PKCS11 Key Manager Provider .
+property.key-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the PKCS11 Key Manager Provider is accessed.
+property.key-store-pin-property.syntax.string.pattern.synopsis=The name of a defined Java property.
diff --git a/opends/src/admin/messages/PasswordGeneratorCfgDefn.properties b/opends/src/admin/messages/PasswordGeneratorCfgDefn.properties
new file mode 100644
index 0000000..9ca9033
--- /dev/null
+++ b/opends/src/admin/messages/PasswordGeneratorCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Password Generator
+user-friendly-plural-name=Password Generators
+synopsis=Password Generators are used by the password modify extended operation to construct a new password for the user.
+description=The server allows any number of password validators to be defined. This can impose any kinds of restrictions on the characteristics of valid passwords. Therefore, it is not feasible for the server to attempt to generate a password on its own that will meet all the requirements of all the validators. The password generator makes it possible to provide custom logic for creating a new password.
+property.enabled.synopsis=Indicates whether the Password Generator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Generator implementation.
diff --git a/opends/src/admin/messages/PasswordGeneratorCfgDefn_de.properties b/opends/src/admin/messages/PasswordGeneratorCfgDefn_de.properties
new file mode 100644
index 0000000..9ca9033
--- /dev/null
+++ b/opends/src/admin/messages/PasswordGeneratorCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Password Generator
+user-friendly-plural-name=Password Generators
+synopsis=Password Generators are used by the password modify extended operation to construct a new password for the user.
+description=The server allows any number of password validators to be defined. This can impose any kinds of restrictions on the characteristics of valid passwords. Therefore, it is not feasible for the server to attempt to generate a password on its own that will meet all the requirements of all the validators. The password generator makes it possible to provide custom logic for creating a new password.
+property.enabled.synopsis=Indicates whether the Password Generator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Generator implementation.
diff --git a/opends/src/admin/messages/PasswordGeneratorCfgDefn_es.properties b/opends/src/admin/messages/PasswordGeneratorCfgDefn_es.properties
new file mode 100644
index 0000000..9ca9033
--- /dev/null
+++ b/opends/src/admin/messages/PasswordGeneratorCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Password Generator
+user-friendly-plural-name=Password Generators
+synopsis=Password Generators are used by the password modify extended operation to construct a new password for the user.
+description=The server allows any number of password validators to be defined. This can impose any kinds of restrictions on the characteristics of valid passwords. Therefore, it is not feasible for the server to attempt to generate a password on its own that will meet all the requirements of all the validators. The password generator makes it possible to provide custom logic for creating a new password.
+property.enabled.synopsis=Indicates whether the Password Generator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Generator implementation.
diff --git a/opends/src/admin/messages/PasswordGeneratorCfgDefn_fr.properties b/opends/src/admin/messages/PasswordGeneratorCfgDefn_fr.properties
new file mode 100644
index 0000000..9ca9033
--- /dev/null
+++ b/opends/src/admin/messages/PasswordGeneratorCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Password Generator
+user-friendly-plural-name=Password Generators
+synopsis=Password Generators are used by the password modify extended operation to construct a new password for the user.
+description=The server allows any number of password validators to be defined. This can impose any kinds of restrictions on the characteristics of valid passwords. Therefore, it is not feasible for the server to attempt to generate a password on its own that will meet all the requirements of all the validators. The password generator makes it possible to provide custom logic for creating a new password.
+property.enabled.synopsis=Indicates whether the Password Generator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Generator implementation.
diff --git a/opends/src/admin/messages/PasswordGeneratorCfgDefn_ja.properties b/opends/src/admin/messages/PasswordGeneratorCfgDefn_ja.properties
new file mode 100644
index 0000000..9ca9033
--- /dev/null
+++ b/opends/src/admin/messages/PasswordGeneratorCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Password Generator
+user-friendly-plural-name=Password Generators
+synopsis=Password Generators are used by the password modify extended operation to construct a new password for the user.
+description=The server allows any number of password validators to be defined. This can impose any kinds of restrictions on the characteristics of valid passwords. Therefore, it is not feasible for the server to attempt to generate a password on its own that will meet all the requirements of all the validators. The password generator makes it possible to provide custom logic for creating a new password.
+property.enabled.synopsis=Indicates whether the Password Generator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Generator implementation.
diff --git a/opends/src/admin/messages/PasswordGeneratorCfgDefn_ko.properties b/opends/src/admin/messages/PasswordGeneratorCfgDefn_ko.properties
new file mode 100644
index 0000000..9ca9033
--- /dev/null
+++ b/opends/src/admin/messages/PasswordGeneratorCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Password Generator
+user-friendly-plural-name=Password Generators
+synopsis=Password Generators are used by the password modify extended operation to construct a new password for the user.
+description=The server allows any number of password validators to be defined. This can impose any kinds of restrictions on the characteristics of valid passwords. Therefore, it is not feasible for the server to attempt to generate a password on its own that will meet all the requirements of all the validators. The password generator makes it possible to provide custom logic for creating a new password.
+property.enabled.synopsis=Indicates whether the Password Generator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Generator implementation.
diff --git a/opends/src/admin/messages/PasswordGeneratorCfgDefn_zh_CN.properties b/opends/src/admin/messages/PasswordGeneratorCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..9ca9033
--- /dev/null
+++ b/opends/src/admin/messages/PasswordGeneratorCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Password Generator
+user-friendly-plural-name=Password Generators
+synopsis=Password Generators are used by the password modify extended operation to construct a new password for the user.
+description=The server allows any number of password validators to be defined. This can impose any kinds of restrictions on the characteristics of valid passwords. Therefore, it is not feasible for the server to attempt to generate a password on its own that will meet all the requirements of all the validators. The password generator makes it possible to provide custom logic for creating a new password.
+property.enabled.synopsis=Indicates whether the Password Generator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Generator implementation.
diff --git a/opends/src/admin/messages/PasswordGeneratorCfgDefn_zh_TW.properties b/opends/src/admin/messages/PasswordGeneratorCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..9ca9033
--- /dev/null
+++ b/opends/src/admin/messages/PasswordGeneratorCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Password Generator
+user-friendly-plural-name=Password Generators
+synopsis=Password Generators are used by the password modify extended operation to construct a new password for the user.
+description=The server allows any number of password validators to be defined. This can impose any kinds of restrictions on the characteristics of valid passwords. Therefore, it is not feasible for the server to attempt to generate a password on its own that will meet all the requirements of all the validators. The password generator makes it possible to provide custom logic for creating a new password.
+property.enabled.synopsis=Indicates whether the Password Generator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Generator implementation.
diff --git a/opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn.properties b/opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn.properties
new file mode 100644
index 0000000..3d22f8b
--- /dev/null
+++ b/opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Password Modify Extended Operation Handler
+user-friendly-plural-name=Password Modify Extended Operation Handlers
+synopsis=The Password Modify Extended Operation Handler allows end users to change their own passwords, or administrators to reset user passwords.
+description=The password modify extended operation is defined in RFC 3062. It includes the ability for users to provide their current password for further confirmation of their identity when changing the password, and it also includes the ability to generate a new password if the user does not provide one.
+property.enabled.synopsis=Indicates whether the Password Modify Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that should be used in conjunction with the password modify extended operation.
+property.identity-mapper.description=This property is used to identify a user based on an authorization ID in the 'u:' form. Changes to this property take effect immediately.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Password Modify Extended Operation Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Modify Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_de.properties b/opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..3d22f8b
--- /dev/null
+++ b/opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_de.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Password Modify Extended Operation Handler
+user-friendly-plural-name=Password Modify Extended Operation Handlers
+synopsis=The Password Modify Extended Operation Handler allows end users to change their own passwords, or administrators to reset user passwords.
+description=The password modify extended operation is defined in RFC 3062. It includes the ability for users to provide their current password for further confirmation of their identity when changing the password, and it also includes the ability to generate a new password if the user does not provide one.
+property.enabled.synopsis=Indicates whether the Password Modify Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that should be used in conjunction with the password modify extended operation.
+property.identity-mapper.description=This property is used to identify a user based on an authorization ID in the 'u:' form. Changes to this property take effect immediately.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Password Modify Extended Operation Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Modify Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_es.properties b/opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..3d22f8b
--- /dev/null
+++ b/opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_es.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Password Modify Extended Operation Handler
+user-friendly-plural-name=Password Modify Extended Operation Handlers
+synopsis=The Password Modify Extended Operation Handler allows end users to change their own passwords, or administrators to reset user passwords.
+description=The password modify extended operation is defined in RFC 3062. It includes the ability for users to provide their current password for further confirmation of their identity when changing the password, and it also includes the ability to generate a new password if the user does not provide one.
+property.enabled.synopsis=Indicates whether the Password Modify Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that should be used in conjunction with the password modify extended operation.
+property.identity-mapper.description=This property is used to identify a user based on an authorization ID in the 'u:' form. Changes to this property take effect immediately.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Password Modify Extended Operation Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Modify Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_fr.properties b/opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..3d22f8b
--- /dev/null
+++ b/opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_fr.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Password Modify Extended Operation Handler
+user-friendly-plural-name=Password Modify Extended Operation Handlers
+synopsis=The Password Modify Extended Operation Handler allows end users to change their own passwords, or administrators to reset user passwords.
+description=The password modify extended operation is defined in RFC 3062. It includes the ability for users to provide their current password for further confirmation of their identity when changing the password, and it also includes the ability to generate a new password if the user does not provide one.
+property.enabled.synopsis=Indicates whether the Password Modify Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that should be used in conjunction with the password modify extended operation.
+property.identity-mapper.description=This property is used to identify a user based on an authorization ID in the 'u:' form. Changes to this property take effect immediately.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Password Modify Extended Operation Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Modify Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_ja.properties b/opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..3d22f8b
--- /dev/null
+++ b/opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_ja.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Password Modify Extended Operation Handler
+user-friendly-plural-name=Password Modify Extended Operation Handlers
+synopsis=The Password Modify Extended Operation Handler allows end users to change their own passwords, or administrators to reset user passwords.
+description=The password modify extended operation is defined in RFC 3062. It includes the ability for users to provide their current password for further confirmation of their identity when changing the password, and it also includes the ability to generate a new password if the user does not provide one.
+property.enabled.synopsis=Indicates whether the Password Modify Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that should be used in conjunction with the password modify extended operation.
+property.identity-mapper.description=This property is used to identify a user based on an authorization ID in the 'u:' form. Changes to this property take effect immediately.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Password Modify Extended Operation Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Modify Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_ko.properties b/opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..3d22f8b
--- /dev/null
+++ b/opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_ko.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Password Modify Extended Operation Handler
+user-friendly-plural-name=Password Modify Extended Operation Handlers
+synopsis=The Password Modify Extended Operation Handler allows end users to change their own passwords, or administrators to reset user passwords.
+description=The password modify extended operation is defined in RFC 3062. It includes the ability for users to provide their current password for further confirmation of their identity when changing the password, and it also includes the ability to generate a new password if the user does not provide one.
+property.enabled.synopsis=Indicates whether the Password Modify Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that should be used in conjunction with the password modify extended operation.
+property.identity-mapper.description=This property is used to identify a user based on an authorization ID in the 'u:' form. Changes to this property take effect immediately.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Password Modify Extended Operation Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Modify Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..3d22f8b
--- /dev/null
+++ b/opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Password Modify Extended Operation Handler
+user-friendly-plural-name=Password Modify Extended Operation Handlers
+synopsis=The Password Modify Extended Operation Handler allows end users to change their own passwords, or administrators to reset user passwords.
+description=The password modify extended operation is defined in RFC 3062. It includes the ability for users to provide their current password for further confirmation of their identity when changing the password, and it also includes the ability to generate a new password if the user does not provide one.
+property.enabled.synopsis=Indicates whether the Password Modify Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that should be used in conjunction with the password modify extended operation.
+property.identity-mapper.description=This property is used to identify a user based on an authorization ID in the 'u:' form. Changes to this property take effect immediately.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Password Modify Extended Operation Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Modify Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..3d22f8b
--- /dev/null
+++ b/opends/src/admin/messages/PasswordModifyExtendedOperationHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Password Modify Extended Operation Handler
+user-friendly-plural-name=Password Modify Extended Operation Handlers
+synopsis=The Password Modify Extended Operation Handler allows end users to change their own passwords, or administrators to reset user passwords.
+description=The password modify extended operation is defined in RFC 3062. It includes the ability for users to provide their current password for further confirmation of their identity when changing the password, and it also includes the ability to generate a new password if the user does not provide one.
+property.enabled.synopsis=Indicates whether the Password Modify Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that should be used in conjunction with the password modify extended operation.
+property.identity-mapper.description=This property is used to identify a user based on an authorization ID in the 'u:' form. Changes to this property take effect immediately.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Password Modify Extended Operation Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Modify Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/PasswordPolicyCfgDefn.properties b/opends/src/admin/messages/PasswordPolicyCfgDefn.properties
new file mode 100644
index 0000000..c21c32d
--- /dev/null
+++ b/opends/src/admin/messages/PasswordPolicyCfgDefn.properties
@@ -0,0 +1,73 @@
+user-friendly-name=Password Policy
+user-friendly-plural-name=Password Policies
+synopsis=Password Policies define a number of password management rules, as well as requirements for authentication processing.
+property.account-status-notification-handler.synopsis=Specifies the names of the account status notification handlers that are used with the associated password storage scheme.
+property.account-status-notification-handler.syntax.aggregation.constraint-synopsis=The referenced account status notification handlers must be enabled.
+property.allow-expired-password-changes.synopsis=Indicates whether a user whose password is expired is still allowed to change that password using the password modify extended operation.
+property.allow-multiple-password-values.synopsis=Indicates whether user entries can have multiple distinct values for the password attribute.
+property.allow-multiple-password-values.description=This is potentially dangerous because many mechanisms used to change the password do not work well with such a configuration. If multiple password values are allowed, then any of them can be used to authenticate, and they are all subject to the same policy constraints.
+property.allow-pre-encoded-passwords.synopsis=Indicates whether users can change their passwords by providing a pre-encoded value.
+property.allow-pre-encoded-passwords.description=This can cause a security risk because the clear-text version of the password is not known and therefore validation checks cannot be applied to it.
+property.allow-user-password-changes.synopsis=Indicates whether users can change their own passwords.
+property.allow-user-password-changes.description=This check is made in addition to access control evaluation. Both must allow the password change for it to occur.
+property.default-password-storage-scheme.synopsis=Specifies the names of the password storage schemes that are used to encode clear-text passwords for this password policy.
+property.default-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled.
+property.deprecated-password-storage-scheme.synopsis=Specifies the names of the password storage schemes that are considered deprecated for this password policy.
+property.deprecated-password-storage-scheme.description=If a user with this password policy authenticates to the server and his/her password is encoded with a deprecated scheme, those values are removed and replaced with values encoded using the default password storage scheme(s).
+property.deprecated-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled.
+property.expire-passwords-without-warning.synopsis=Indicates whether the Directory Server allows a user's password to expire even if that user has never seen an expiration warning notification.
+property.expire-passwords-without-warning.description=If this property is true, accounts always expire when the expiration time arrives. If this property is false disabled, the user always receives at least one warning notification, and the password expiration is set to the warning time plus the warning interval.
+property.force-change-on-add.synopsis=Indicates whether users are forced to change their passwords upon first authenticating to the Directory Server after their account has been created.
+property.force-change-on-reset.synopsis=Indicates whether users are forced to change their passwords if they are reset by an administrator.
+property.force-change-on-reset.description=For this purpose, anyone with permission to change a given user's password other than that user is considered an administrator.
+property.grace-login-count.synopsis=Specifies the number of grace logins that a user is allowed after the account has expired to allow that user to choose a new password.
+property.grace-login-count.description=A value of 0 indicates that no grace logins are allowed.
+property.idle-lockout-interval.synopsis=Specifies the maximum length of time that an account may remain idle (that is, the associated user does not authenticate to the server) before that user is locked out.
+property.idle-lockout-interval.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds indicates that idle accounts are not automatically locked out. This feature is available only if the last login time is maintained.
+property.last-login-time-attribute.synopsis=Specifies the name or OID of the attribute type that is used to hold the last login time for users with the associated password policy.
+property.last-login-time-attribute.description=This attribute type must be defined in the Directory Server schema and must either be defined as an operational attribute or must be allowed by the set of objectClasses for all users with the associated password policy.
+property.last-login-time-format.synopsis=Specifies the format string that is used to generate the last login time value for users with the associated password policy.
+property.last-login-time-format.description=This format string conforms to the syntax described in the API documentation for the java.text.SimpleDateFormat class.
+property.last-login-time-format.syntax.string.pattern.synopsis=Any valid format string that can be used with the java.text.SimpleDateFormat class.
+property.lockout-duration.synopsis=Specifies the length of time that an account is locked after too many authentication failures.
+property.lockout-duration.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds indicates that the account must remain locked until an administrator resets the password.
+property.lockout-failure-count.synopsis=Specifies the maximum number of authentication failures that a user is allowed before the account is locked out.
+property.lockout-failure-count.description=A value of 0 indicates that accounts are never locked out due to failed attempts.
+property.lockout-failure-expiration-interval.synopsis=Specifies the length of time before an authentication failure is no longer counted against a user for the purposes of account lockout.
+property.lockout-failure-expiration-interval.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds indicates that the authentication failures must never expire. The failure count is always cleared upon a successful authentication.
+property.max-password-age.synopsis=Specifies the maximum length of time that a user can continue using the same password before it must be changed (that is, the password expiration interval).
+property.max-password-age.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds disables password expiration.
+property.max-password-reset-age.synopsis=Specifies the maximum length of time that users have to change passwords after they have been reset by an administrator before they become locked.
+property.max-password-reset-age.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds disables this feature.
+property.min-password-age.synopsis=Specifies the minimum length of time after a password change before the user is allowed to change the password again.
+property.min-password-age.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. This setting can be used to prevent users from changing their passwords repeatedly over a short period of time to flush an old password from the history so that it can be re-used.
+property.password-attribute.synopsis=Specifies the attribute type used to hold user passwords.
+property.password-attribute.description=This attribute type must be defined in the server schema, and it must have either the user password or auth password syntax.
+property.password-change-requires-current-password.synopsis=Indicates whether user password changes must use the password modify extended operation and must include the user's current password before the change is allowed.
+property.password-expiration-warning-interval.synopsis=Specifies the maximum length of time before a user's password actually expires that the server begins to include warning notifications in bind responses for that user.
+property.password-expiration-warning-interval.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds disables the warning interval.
+property.password-generator.synopsis=Specifies the name of the password generator that is used with the associated password policy.
+property.password-generator.description=This is used in conjunction with the password modify extended operation to generate a new password for a user when none was provided in the request.
+property.password-generator.syntax.aggregation.constraint-synopsis=The referenced password generator must be enabled.
+property.password-history-count.synopsis=Specifies the maximum number of former passwords to maintain in the password history.
+property.password-history-count.description=When choosing a new password, the proposed password is checked to ensure that it does not match the current password, nor any other password in the history list. A value of zero indicates that either no password history is to be maintained (if the password history duration has a value of zero seconds), or that there is no maximum number of passwords to maintain in the history (if the password history duration has a value greater than zero seconds).
+property.password-history-duration.synopsis=Specifies the maximum length of time that passwords remain in the password history.
+property.password-history-duration.description=When choosing a new password, the proposed password is checked to ensure that it does not match the current password, nor any other password in the history list. A value of zero seconds indicates that either no password history is to be maintained (if the password history count has a value of zero), or that there is no maximum duration for passwords in the history (if the password history count has a value greater than zero).
+property.password-validator.synopsis=Specifies the names of the password validators that are used with the associated password storage scheme.
+property.password-validator.description=The password validators are invoked when a user attempts to provide a new password, to determine whether the new password is acceptable.
+property.password-validator.syntax.aggregation.constraint-synopsis=The referenced password validators must be enabled.
+property.previous-last-login-time-format.synopsis=Specifies the format string(s) that might have been used with the last login time at any point in the past for users associated with the password policy.
+property.previous-last-login-time-format.description=These values are used to make it possible to parse previous values, but are not used to set new values. The format strings conform to the syntax described in the API documentation for the java.text.SimpleDateFormat class.
+property.previous-last-login-time-format.syntax.string.pattern.synopsis=Any valid format string that can be used with the java.text.SimpleDateFormat class.
+property.require-change-by-time.synopsis=Specifies the time by which all users with the associated password policy must change their passwords.
+property.require-change-by-time.description=The value is expressed in a generalized time format. If this time is equal to the current time or is in the past, then all users are required to change their passwords immediately. The behavior of the server in this mode is identical to the behavior observed when users are forced to change their passwords after an administrative reset.
+property.require-change-by-time.syntax.string.pattern.synopsis=A valid timestamp in generalized time form (for example, a value of "20070409185811Z" indicates a value of April 9, 2007 at 6:58:11 pm GMT).
+property.require-secure-authentication.synopsis=Indicates whether users with the associated password policy are required to authenticate in a secure manner.
+property.require-secure-authentication.description=This might mean either using a secure communication channel between the client and the server, or using a SASL mechanism that does not expose the credentials.
+property.require-secure-password-changes.synopsis=Indicates whether users with the associated password policy are required to change their password in a secure manner that does not expose the credentials.
+property.skip-validation-for-administrators.synopsis=Indicates whether passwords set by administrators are allowed to bypass the password validation process that is required for user password changes.
+property.state-update-failure-policy.synopsis=Specifies how the server deals with the inability to update password policy state information during an authentication attempt.
+property.state-update-failure-policy.description=In particular, this property can be used to control whether an otherwise successful bind operation fails if a failure occurs while attempting to update password policy state information (for example, to clear a record of previous authentication failures or to update the last login time). It can also be used to control whether to reject a bind request if it is known ahead of time that it will not be possible to update the authentication failure times in the event of an unsuccessful bind attempt (for example, if the backend writability mode is disabled).
+property.state-update-failure-policy.syntax.enumeration.value.ignore.synopsis=If a bind attempt would otherwise be successful, then do not reject it if a problem occurs while attempting to update the password policy state information for the user.
+property.state-update-failure-policy.syntax.enumeration.value.proactive.synopsis=Proactively reject any bind attempt if it is known ahead of time that it would not be possible to update the user's password policy state information.
+property.state-update-failure-policy.syntax.enumeration.value.reactive.synopsis=Even if a bind attempt would otherwise be successful, reject it if a problem occurs while attempting to update the password policy state information for the user.
diff --git a/opends/src/admin/messages/PasswordPolicyCfgDefn_de.properties b/opends/src/admin/messages/PasswordPolicyCfgDefn_de.properties
new file mode 100644
index 0000000..c21c32d
--- /dev/null
+++ b/opends/src/admin/messages/PasswordPolicyCfgDefn_de.properties
@@ -0,0 +1,73 @@
+user-friendly-name=Password Policy
+user-friendly-plural-name=Password Policies
+synopsis=Password Policies define a number of password management rules, as well as requirements for authentication processing.
+property.account-status-notification-handler.synopsis=Specifies the names of the account status notification handlers that are used with the associated password storage scheme.
+property.account-status-notification-handler.syntax.aggregation.constraint-synopsis=The referenced account status notification handlers must be enabled.
+property.allow-expired-password-changes.synopsis=Indicates whether a user whose password is expired is still allowed to change that password using the password modify extended operation.
+property.allow-multiple-password-values.synopsis=Indicates whether user entries can have multiple distinct values for the password attribute.
+property.allow-multiple-password-values.description=This is potentially dangerous because many mechanisms used to change the password do not work well with such a configuration. If multiple password values are allowed, then any of them can be used to authenticate, and they are all subject to the same policy constraints.
+property.allow-pre-encoded-passwords.synopsis=Indicates whether users can change their passwords by providing a pre-encoded value.
+property.allow-pre-encoded-passwords.description=This can cause a security risk because the clear-text version of the password is not known and therefore validation checks cannot be applied to it.
+property.allow-user-password-changes.synopsis=Indicates whether users can change their own passwords.
+property.allow-user-password-changes.description=This check is made in addition to access control evaluation. Both must allow the password change for it to occur.
+property.default-password-storage-scheme.synopsis=Specifies the names of the password storage schemes that are used to encode clear-text passwords for this password policy.
+property.default-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled.
+property.deprecated-password-storage-scheme.synopsis=Specifies the names of the password storage schemes that are considered deprecated for this password policy.
+property.deprecated-password-storage-scheme.description=If a user with this password policy authenticates to the server and his/her password is encoded with a deprecated scheme, those values are removed and replaced with values encoded using the default password storage scheme(s).
+property.deprecated-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled.
+property.expire-passwords-without-warning.synopsis=Indicates whether the Directory Server allows a user's password to expire even if that user has never seen an expiration warning notification.
+property.expire-passwords-without-warning.description=If this property is true, accounts always expire when the expiration time arrives. If this property is false disabled, the user always receives at least one warning notification, and the password expiration is set to the warning time plus the warning interval.
+property.force-change-on-add.synopsis=Indicates whether users are forced to change their passwords upon first authenticating to the Directory Server after their account has been created.
+property.force-change-on-reset.synopsis=Indicates whether users are forced to change their passwords if they are reset by an administrator.
+property.force-change-on-reset.description=For this purpose, anyone with permission to change a given user's password other than that user is considered an administrator.
+property.grace-login-count.synopsis=Specifies the number of grace logins that a user is allowed after the account has expired to allow that user to choose a new password.
+property.grace-login-count.description=A value of 0 indicates that no grace logins are allowed.
+property.idle-lockout-interval.synopsis=Specifies the maximum length of time that an account may remain idle (that is, the associated user does not authenticate to the server) before that user is locked out.
+property.idle-lockout-interval.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds indicates that idle accounts are not automatically locked out. This feature is available only if the last login time is maintained.
+property.last-login-time-attribute.synopsis=Specifies the name or OID of the attribute type that is used to hold the last login time for users with the associated password policy.
+property.last-login-time-attribute.description=This attribute type must be defined in the Directory Server schema and must either be defined as an operational attribute or must be allowed by the set of objectClasses for all users with the associated password policy.
+property.last-login-time-format.synopsis=Specifies the format string that is used to generate the last login time value for users with the associated password policy.
+property.last-login-time-format.description=This format string conforms to the syntax described in the API documentation for the java.text.SimpleDateFormat class.
+property.last-login-time-format.syntax.string.pattern.synopsis=Any valid format string that can be used with the java.text.SimpleDateFormat class.
+property.lockout-duration.synopsis=Specifies the length of time that an account is locked after too many authentication failures.
+property.lockout-duration.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds indicates that the account must remain locked until an administrator resets the password.
+property.lockout-failure-count.synopsis=Specifies the maximum number of authentication failures that a user is allowed before the account is locked out.
+property.lockout-failure-count.description=A value of 0 indicates that accounts are never locked out due to failed attempts.
+property.lockout-failure-expiration-interval.synopsis=Specifies the length of time before an authentication failure is no longer counted against a user for the purposes of account lockout.
+property.lockout-failure-expiration-interval.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds indicates that the authentication failures must never expire. The failure count is always cleared upon a successful authentication.
+property.max-password-age.synopsis=Specifies the maximum length of time that a user can continue using the same password before it must be changed (that is, the password expiration interval).
+property.max-password-age.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds disables password expiration.
+property.max-password-reset-age.synopsis=Specifies the maximum length of time that users have to change passwords after they have been reset by an administrator before they become locked.
+property.max-password-reset-age.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds disables this feature.
+property.min-password-age.synopsis=Specifies the minimum length of time after a password change before the user is allowed to change the password again.
+property.min-password-age.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. This setting can be used to prevent users from changing their passwords repeatedly over a short period of time to flush an old password from the history so that it can be re-used.
+property.password-attribute.synopsis=Specifies the attribute type used to hold user passwords.
+property.password-attribute.description=This attribute type must be defined in the server schema, and it must have either the user password or auth password syntax.
+property.password-change-requires-current-password.synopsis=Indicates whether user password changes must use the password modify extended operation and must include the user's current password before the change is allowed.
+property.password-expiration-warning-interval.synopsis=Specifies the maximum length of time before a user's password actually expires that the server begins to include warning notifications in bind responses for that user.
+property.password-expiration-warning-interval.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds disables the warning interval.
+property.password-generator.synopsis=Specifies the name of the password generator that is used with the associated password policy.
+property.password-generator.description=This is used in conjunction with the password modify extended operation to generate a new password for a user when none was provided in the request.
+property.password-generator.syntax.aggregation.constraint-synopsis=The referenced password generator must be enabled.
+property.password-history-count.synopsis=Specifies the maximum number of former passwords to maintain in the password history.
+property.password-history-count.description=When choosing a new password, the proposed password is checked to ensure that it does not match the current password, nor any other password in the history list. A value of zero indicates that either no password history is to be maintained (if the password history duration has a value of zero seconds), or that there is no maximum number of passwords to maintain in the history (if the password history duration has a value greater than zero seconds).
+property.password-history-duration.synopsis=Specifies the maximum length of time that passwords remain in the password history.
+property.password-history-duration.description=When choosing a new password, the proposed password is checked to ensure that it does not match the current password, nor any other password in the history list. A value of zero seconds indicates that either no password history is to be maintained (if the password history count has a value of zero), or that there is no maximum duration for passwords in the history (if the password history count has a value greater than zero).
+property.password-validator.synopsis=Specifies the names of the password validators that are used with the associated password storage scheme.
+property.password-validator.description=The password validators are invoked when a user attempts to provide a new password, to determine whether the new password is acceptable.
+property.password-validator.syntax.aggregation.constraint-synopsis=The referenced password validators must be enabled.
+property.previous-last-login-time-format.synopsis=Specifies the format string(s) that might have been used with the last login time at any point in the past for users associated with the password policy.
+property.previous-last-login-time-format.description=These values are used to make it possible to parse previous values, but are not used to set new values. The format strings conform to the syntax described in the API documentation for the java.text.SimpleDateFormat class.
+property.previous-last-login-time-format.syntax.string.pattern.synopsis=Any valid format string that can be used with the java.text.SimpleDateFormat class.
+property.require-change-by-time.synopsis=Specifies the time by which all users with the associated password policy must change their passwords.
+property.require-change-by-time.description=The value is expressed in a generalized time format. If this time is equal to the current time or is in the past, then all users are required to change their passwords immediately. The behavior of the server in this mode is identical to the behavior observed when users are forced to change their passwords after an administrative reset.
+property.require-change-by-time.syntax.string.pattern.synopsis=A valid timestamp in generalized time form (for example, a value of "20070409185811Z" indicates a value of April 9, 2007 at 6:58:11 pm GMT).
+property.require-secure-authentication.synopsis=Indicates whether users with the associated password policy are required to authenticate in a secure manner.
+property.require-secure-authentication.description=This might mean either using a secure communication channel between the client and the server, or using a SASL mechanism that does not expose the credentials.
+property.require-secure-password-changes.synopsis=Indicates whether users with the associated password policy are required to change their password in a secure manner that does not expose the credentials.
+property.skip-validation-for-administrators.synopsis=Indicates whether passwords set by administrators are allowed to bypass the password validation process that is required for user password changes.
+property.state-update-failure-policy.synopsis=Specifies how the server deals with the inability to update password policy state information during an authentication attempt.
+property.state-update-failure-policy.description=In particular, this property can be used to control whether an otherwise successful bind operation fails if a failure occurs while attempting to update password policy state information (for example, to clear a record of previous authentication failures or to update the last login time). It can also be used to control whether to reject a bind request if it is known ahead of time that it will not be possible to update the authentication failure times in the event of an unsuccessful bind attempt (for example, if the backend writability mode is disabled).
+property.state-update-failure-policy.syntax.enumeration.value.ignore.synopsis=If a bind attempt would otherwise be successful, then do not reject it if a problem occurs while attempting to update the password policy state information for the user.
+property.state-update-failure-policy.syntax.enumeration.value.proactive.synopsis=Proactively reject any bind attempt if it is known ahead of time that it would not be possible to update the user's password policy state information.
+property.state-update-failure-policy.syntax.enumeration.value.reactive.synopsis=Even if a bind attempt would otherwise be successful, reject it if a problem occurs while attempting to update the password policy state information for the user.
diff --git a/opends/src/admin/messages/PasswordPolicyCfgDefn_es.properties b/opends/src/admin/messages/PasswordPolicyCfgDefn_es.properties
new file mode 100644
index 0000000..c21c32d
--- /dev/null
+++ b/opends/src/admin/messages/PasswordPolicyCfgDefn_es.properties
@@ -0,0 +1,73 @@
+user-friendly-name=Password Policy
+user-friendly-plural-name=Password Policies
+synopsis=Password Policies define a number of password management rules, as well as requirements for authentication processing.
+property.account-status-notification-handler.synopsis=Specifies the names of the account status notification handlers that are used with the associated password storage scheme.
+property.account-status-notification-handler.syntax.aggregation.constraint-synopsis=The referenced account status notification handlers must be enabled.
+property.allow-expired-password-changes.synopsis=Indicates whether a user whose password is expired is still allowed to change that password using the password modify extended operation.
+property.allow-multiple-password-values.synopsis=Indicates whether user entries can have multiple distinct values for the password attribute.
+property.allow-multiple-password-values.description=This is potentially dangerous because many mechanisms used to change the password do not work well with such a configuration. If multiple password values are allowed, then any of them can be used to authenticate, and they are all subject to the same policy constraints.
+property.allow-pre-encoded-passwords.synopsis=Indicates whether users can change their passwords by providing a pre-encoded value.
+property.allow-pre-encoded-passwords.description=This can cause a security risk because the clear-text version of the password is not known and therefore validation checks cannot be applied to it.
+property.allow-user-password-changes.synopsis=Indicates whether users can change their own passwords.
+property.allow-user-password-changes.description=This check is made in addition to access control evaluation. Both must allow the password change for it to occur.
+property.default-password-storage-scheme.synopsis=Specifies the names of the password storage schemes that are used to encode clear-text passwords for this password policy.
+property.default-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled.
+property.deprecated-password-storage-scheme.synopsis=Specifies the names of the password storage schemes that are considered deprecated for this password policy.
+property.deprecated-password-storage-scheme.description=If a user with this password policy authenticates to the server and his/her password is encoded with a deprecated scheme, those values are removed and replaced with values encoded using the default password storage scheme(s).
+property.deprecated-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled.
+property.expire-passwords-without-warning.synopsis=Indicates whether the Directory Server allows a user's password to expire even if that user has never seen an expiration warning notification.
+property.expire-passwords-without-warning.description=If this property is true, accounts always expire when the expiration time arrives. If this property is false disabled, the user always receives at least one warning notification, and the password expiration is set to the warning time plus the warning interval.
+property.force-change-on-add.synopsis=Indicates whether users are forced to change their passwords upon first authenticating to the Directory Server after their account has been created.
+property.force-change-on-reset.synopsis=Indicates whether users are forced to change their passwords if they are reset by an administrator.
+property.force-change-on-reset.description=For this purpose, anyone with permission to change a given user's password other than that user is considered an administrator.
+property.grace-login-count.synopsis=Specifies the number of grace logins that a user is allowed after the account has expired to allow that user to choose a new password.
+property.grace-login-count.description=A value of 0 indicates that no grace logins are allowed.
+property.idle-lockout-interval.synopsis=Specifies the maximum length of time that an account may remain idle (that is, the associated user does not authenticate to the server) before that user is locked out.
+property.idle-lockout-interval.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds indicates that idle accounts are not automatically locked out. This feature is available only if the last login time is maintained.
+property.last-login-time-attribute.synopsis=Specifies the name or OID of the attribute type that is used to hold the last login time for users with the associated password policy.
+property.last-login-time-attribute.description=This attribute type must be defined in the Directory Server schema and must either be defined as an operational attribute or must be allowed by the set of objectClasses for all users with the associated password policy.
+property.last-login-time-format.synopsis=Specifies the format string that is used to generate the last login time value for users with the associated password policy.
+property.last-login-time-format.description=This format string conforms to the syntax described in the API documentation for the java.text.SimpleDateFormat class.
+property.last-login-time-format.syntax.string.pattern.synopsis=Any valid format string that can be used with the java.text.SimpleDateFormat class.
+property.lockout-duration.synopsis=Specifies the length of time that an account is locked after too many authentication failures.
+property.lockout-duration.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds indicates that the account must remain locked until an administrator resets the password.
+property.lockout-failure-count.synopsis=Specifies the maximum number of authentication failures that a user is allowed before the account is locked out.
+property.lockout-failure-count.description=A value of 0 indicates that accounts are never locked out due to failed attempts.
+property.lockout-failure-expiration-interval.synopsis=Specifies the length of time before an authentication failure is no longer counted against a user for the purposes of account lockout.
+property.lockout-failure-expiration-interval.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds indicates that the authentication failures must never expire. The failure count is always cleared upon a successful authentication.
+property.max-password-age.synopsis=Specifies the maximum length of time that a user can continue using the same password before it must be changed (that is, the password expiration interval).
+property.max-password-age.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds disables password expiration.
+property.max-password-reset-age.synopsis=Specifies the maximum length of time that users have to change passwords after they have been reset by an administrator before they become locked.
+property.max-password-reset-age.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds disables this feature.
+property.min-password-age.synopsis=Specifies the minimum length of time after a password change before the user is allowed to change the password again.
+property.min-password-age.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. This setting can be used to prevent users from changing their passwords repeatedly over a short period of time to flush an old password from the history so that it can be re-used.
+property.password-attribute.synopsis=Specifies the attribute type used to hold user passwords.
+property.password-attribute.description=This attribute type must be defined in the server schema, and it must have either the user password or auth password syntax.
+property.password-change-requires-current-password.synopsis=Indicates whether user password changes must use the password modify extended operation and must include the user's current password before the change is allowed.
+property.password-expiration-warning-interval.synopsis=Specifies the maximum length of time before a user's password actually expires that the server begins to include warning notifications in bind responses for that user.
+property.password-expiration-warning-interval.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds disables the warning interval.
+property.password-generator.synopsis=Specifies the name of the password generator that is used with the associated password policy.
+property.password-generator.description=This is used in conjunction with the password modify extended operation to generate a new password for a user when none was provided in the request.
+property.password-generator.syntax.aggregation.constraint-synopsis=The referenced password generator must be enabled.
+property.password-history-count.synopsis=Specifies the maximum number of former passwords to maintain in the password history.
+property.password-history-count.description=When choosing a new password, the proposed password is checked to ensure that it does not match the current password, nor any other password in the history list. A value of zero indicates that either no password history is to be maintained (if the password history duration has a value of zero seconds), or that there is no maximum number of passwords to maintain in the history (if the password history duration has a value greater than zero seconds).
+property.password-history-duration.synopsis=Specifies the maximum length of time that passwords remain in the password history.
+property.password-history-duration.description=When choosing a new password, the proposed password is checked to ensure that it does not match the current password, nor any other password in the history list. A value of zero seconds indicates that either no password history is to be maintained (if the password history count has a value of zero), or that there is no maximum duration for passwords in the history (if the password history count has a value greater than zero).
+property.password-validator.synopsis=Specifies the names of the password validators that are used with the associated password storage scheme.
+property.password-validator.description=The password validators are invoked when a user attempts to provide a new password, to determine whether the new password is acceptable.
+property.password-validator.syntax.aggregation.constraint-synopsis=The referenced password validators must be enabled.
+property.previous-last-login-time-format.synopsis=Specifies the format string(s) that might have been used with the last login time at any point in the past for users associated with the password policy.
+property.previous-last-login-time-format.description=These values are used to make it possible to parse previous values, but are not used to set new values. The format strings conform to the syntax described in the API documentation for the java.text.SimpleDateFormat class.
+property.previous-last-login-time-format.syntax.string.pattern.synopsis=Any valid format string that can be used with the java.text.SimpleDateFormat class.
+property.require-change-by-time.synopsis=Specifies the time by which all users with the associated password policy must change their passwords.
+property.require-change-by-time.description=The value is expressed in a generalized time format. If this time is equal to the current time or is in the past, then all users are required to change their passwords immediately. The behavior of the server in this mode is identical to the behavior observed when users are forced to change their passwords after an administrative reset.
+property.require-change-by-time.syntax.string.pattern.synopsis=A valid timestamp in generalized time form (for example, a value of "20070409185811Z" indicates a value of April 9, 2007 at 6:58:11 pm GMT).
+property.require-secure-authentication.synopsis=Indicates whether users with the associated password policy are required to authenticate in a secure manner.
+property.require-secure-authentication.description=This might mean either using a secure communication channel between the client and the server, or using a SASL mechanism that does not expose the credentials.
+property.require-secure-password-changes.synopsis=Indicates whether users with the associated password policy are required to change their password in a secure manner that does not expose the credentials.
+property.skip-validation-for-administrators.synopsis=Indicates whether passwords set by administrators are allowed to bypass the password validation process that is required for user password changes.
+property.state-update-failure-policy.synopsis=Specifies how the server deals with the inability to update password policy state information during an authentication attempt.
+property.state-update-failure-policy.description=In particular, this property can be used to control whether an otherwise successful bind operation fails if a failure occurs while attempting to update password policy state information (for example, to clear a record of previous authentication failures or to update the last login time). It can also be used to control whether to reject a bind request if it is known ahead of time that it will not be possible to update the authentication failure times in the event of an unsuccessful bind attempt (for example, if the backend writability mode is disabled).
+property.state-update-failure-policy.syntax.enumeration.value.ignore.synopsis=If a bind attempt would otherwise be successful, then do not reject it if a problem occurs while attempting to update the password policy state information for the user.
+property.state-update-failure-policy.syntax.enumeration.value.proactive.synopsis=Proactively reject any bind attempt if it is known ahead of time that it would not be possible to update the user's password policy state information.
+property.state-update-failure-policy.syntax.enumeration.value.reactive.synopsis=Even if a bind attempt would otherwise be successful, reject it if a problem occurs while attempting to update the password policy state information for the user.
diff --git a/opends/src/admin/messages/PasswordPolicyCfgDefn_fr.properties b/opends/src/admin/messages/PasswordPolicyCfgDefn_fr.properties
new file mode 100644
index 0000000..c21c32d
--- /dev/null
+++ b/opends/src/admin/messages/PasswordPolicyCfgDefn_fr.properties
@@ -0,0 +1,73 @@
+user-friendly-name=Password Policy
+user-friendly-plural-name=Password Policies
+synopsis=Password Policies define a number of password management rules, as well as requirements for authentication processing.
+property.account-status-notification-handler.synopsis=Specifies the names of the account status notification handlers that are used with the associated password storage scheme.
+property.account-status-notification-handler.syntax.aggregation.constraint-synopsis=The referenced account status notification handlers must be enabled.
+property.allow-expired-password-changes.synopsis=Indicates whether a user whose password is expired is still allowed to change that password using the password modify extended operation.
+property.allow-multiple-password-values.synopsis=Indicates whether user entries can have multiple distinct values for the password attribute.
+property.allow-multiple-password-values.description=This is potentially dangerous because many mechanisms used to change the password do not work well with such a configuration. If multiple password values are allowed, then any of them can be used to authenticate, and they are all subject to the same policy constraints.
+property.allow-pre-encoded-passwords.synopsis=Indicates whether users can change their passwords by providing a pre-encoded value.
+property.allow-pre-encoded-passwords.description=This can cause a security risk because the clear-text version of the password is not known and therefore validation checks cannot be applied to it.
+property.allow-user-password-changes.synopsis=Indicates whether users can change their own passwords.
+property.allow-user-password-changes.description=This check is made in addition to access control evaluation. Both must allow the password change for it to occur.
+property.default-password-storage-scheme.synopsis=Specifies the names of the password storage schemes that are used to encode clear-text passwords for this password policy.
+property.default-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled.
+property.deprecated-password-storage-scheme.synopsis=Specifies the names of the password storage schemes that are considered deprecated for this password policy.
+property.deprecated-password-storage-scheme.description=If a user with this password policy authenticates to the server and his/her password is encoded with a deprecated scheme, those values are removed and replaced with values encoded using the default password storage scheme(s).
+property.deprecated-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled.
+property.expire-passwords-without-warning.synopsis=Indicates whether the Directory Server allows a user's password to expire even if that user has never seen an expiration warning notification.
+property.expire-passwords-without-warning.description=If this property is true, accounts always expire when the expiration time arrives. If this property is false disabled, the user always receives at least one warning notification, and the password expiration is set to the warning time plus the warning interval.
+property.force-change-on-add.synopsis=Indicates whether users are forced to change their passwords upon first authenticating to the Directory Server after their account has been created.
+property.force-change-on-reset.synopsis=Indicates whether users are forced to change their passwords if they are reset by an administrator.
+property.force-change-on-reset.description=For this purpose, anyone with permission to change a given user's password other than that user is considered an administrator.
+property.grace-login-count.synopsis=Specifies the number of grace logins that a user is allowed after the account has expired to allow that user to choose a new password.
+property.grace-login-count.description=A value of 0 indicates that no grace logins are allowed.
+property.idle-lockout-interval.synopsis=Specifies the maximum length of time that an account may remain idle (that is, the associated user does not authenticate to the server) before that user is locked out.
+property.idle-lockout-interval.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds indicates that idle accounts are not automatically locked out. This feature is available only if the last login time is maintained.
+property.last-login-time-attribute.synopsis=Specifies the name or OID of the attribute type that is used to hold the last login time for users with the associated password policy.
+property.last-login-time-attribute.description=This attribute type must be defined in the Directory Server schema and must either be defined as an operational attribute or must be allowed by the set of objectClasses for all users with the associated password policy.
+property.last-login-time-format.synopsis=Specifies the format string that is used to generate the last login time value for users with the associated password policy.
+property.last-login-time-format.description=This format string conforms to the syntax described in the API documentation for the java.text.SimpleDateFormat class.
+property.last-login-time-format.syntax.string.pattern.synopsis=Any valid format string that can be used with the java.text.SimpleDateFormat class.
+property.lockout-duration.synopsis=Specifies the length of time that an account is locked after too many authentication failures.
+property.lockout-duration.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds indicates that the account must remain locked until an administrator resets the password.
+property.lockout-failure-count.synopsis=Specifies the maximum number of authentication failures that a user is allowed before the account is locked out.
+property.lockout-failure-count.description=A value of 0 indicates that accounts are never locked out due to failed attempts.
+property.lockout-failure-expiration-interval.synopsis=Specifies the length of time before an authentication failure is no longer counted against a user for the purposes of account lockout.
+property.lockout-failure-expiration-interval.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds indicates that the authentication failures must never expire. The failure count is always cleared upon a successful authentication.
+property.max-password-age.synopsis=Specifies the maximum length of time that a user can continue using the same password before it must be changed (that is, the password expiration interval).
+property.max-password-age.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds disables password expiration.
+property.max-password-reset-age.synopsis=Specifies the maximum length of time that users have to change passwords after they have been reset by an administrator before they become locked.
+property.max-password-reset-age.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds disables this feature.
+property.min-password-age.synopsis=Specifies the minimum length of time after a password change before the user is allowed to change the password again.
+property.min-password-age.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. This setting can be used to prevent users from changing their passwords repeatedly over a short period of time to flush an old password from the history so that it can be re-used.
+property.password-attribute.synopsis=Specifies the attribute type used to hold user passwords.
+property.password-attribute.description=This attribute type must be defined in the server schema, and it must have either the user password or auth password syntax.
+property.password-change-requires-current-password.synopsis=Indicates whether user password changes must use the password modify extended operation and must include the user's current password before the change is allowed.
+property.password-expiration-warning-interval.synopsis=Specifies the maximum length of time before a user's password actually expires that the server begins to include warning notifications in bind responses for that user.
+property.password-expiration-warning-interval.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds disables the warning interval.
+property.password-generator.synopsis=Specifies the name of the password generator that is used with the associated password policy.
+property.password-generator.description=This is used in conjunction with the password modify extended operation to generate a new password for a user when none was provided in the request.
+property.password-generator.syntax.aggregation.constraint-synopsis=The referenced password generator must be enabled.
+property.password-history-count.synopsis=Specifies the maximum number of former passwords to maintain in the password history.
+property.password-history-count.description=When choosing a new password, the proposed password is checked to ensure that it does not match the current password, nor any other password in the history list. A value of zero indicates that either no password history is to be maintained (if the password history duration has a value of zero seconds), or that there is no maximum number of passwords to maintain in the history (if the password history duration has a value greater than zero seconds).
+property.password-history-duration.synopsis=Specifies the maximum length of time that passwords remain in the password history.
+property.password-history-duration.description=When choosing a new password, the proposed password is checked to ensure that it does not match the current password, nor any other password in the history list. A value of zero seconds indicates that either no password history is to be maintained (if the password history count has a value of zero), or that there is no maximum duration for passwords in the history (if the password history count has a value greater than zero).
+property.password-validator.synopsis=Specifies the names of the password validators that are used with the associated password storage scheme.
+property.password-validator.description=The password validators are invoked when a user attempts to provide a new password, to determine whether the new password is acceptable.
+property.password-validator.syntax.aggregation.constraint-synopsis=The referenced password validators must be enabled.
+property.previous-last-login-time-format.synopsis=Specifies the format string(s) that might have been used with the last login time at any point in the past for users associated with the password policy.
+property.previous-last-login-time-format.description=These values are used to make it possible to parse previous values, but are not used to set new values. The format strings conform to the syntax described in the API documentation for the java.text.SimpleDateFormat class.
+property.previous-last-login-time-format.syntax.string.pattern.synopsis=Any valid format string that can be used with the java.text.SimpleDateFormat class.
+property.require-change-by-time.synopsis=Specifies the time by which all users with the associated password policy must change their passwords.
+property.require-change-by-time.description=The value is expressed in a generalized time format. If this time is equal to the current time or is in the past, then all users are required to change their passwords immediately. The behavior of the server in this mode is identical to the behavior observed when users are forced to change their passwords after an administrative reset.
+property.require-change-by-time.syntax.string.pattern.synopsis=A valid timestamp in generalized time form (for example, a value of "20070409185811Z" indicates a value of April 9, 2007 at 6:58:11 pm GMT).
+property.require-secure-authentication.synopsis=Indicates whether users with the associated password policy are required to authenticate in a secure manner.
+property.require-secure-authentication.description=This might mean either using a secure communication channel between the client and the server, or using a SASL mechanism that does not expose the credentials.
+property.require-secure-password-changes.synopsis=Indicates whether users with the associated password policy are required to change their password in a secure manner that does not expose the credentials.
+property.skip-validation-for-administrators.synopsis=Indicates whether passwords set by administrators are allowed to bypass the password validation process that is required for user password changes.
+property.state-update-failure-policy.synopsis=Specifies how the server deals with the inability to update password policy state information during an authentication attempt.
+property.state-update-failure-policy.description=In particular, this property can be used to control whether an otherwise successful bind operation fails if a failure occurs while attempting to update password policy state information (for example, to clear a record of previous authentication failures or to update the last login time). It can also be used to control whether to reject a bind request if it is known ahead of time that it will not be possible to update the authentication failure times in the event of an unsuccessful bind attempt (for example, if the backend writability mode is disabled).
+property.state-update-failure-policy.syntax.enumeration.value.ignore.synopsis=If a bind attempt would otherwise be successful, then do not reject it if a problem occurs while attempting to update the password policy state information for the user.
+property.state-update-failure-policy.syntax.enumeration.value.proactive.synopsis=Proactively reject any bind attempt if it is known ahead of time that it would not be possible to update the user's password policy state information.
+property.state-update-failure-policy.syntax.enumeration.value.reactive.synopsis=Even if a bind attempt would otherwise be successful, reject it if a problem occurs while attempting to update the password policy state information for the user.
diff --git a/opends/src/admin/messages/PasswordPolicyCfgDefn_ja.properties b/opends/src/admin/messages/PasswordPolicyCfgDefn_ja.properties
new file mode 100644
index 0000000..c21c32d
--- /dev/null
+++ b/opends/src/admin/messages/PasswordPolicyCfgDefn_ja.properties
@@ -0,0 +1,73 @@
+user-friendly-name=Password Policy
+user-friendly-plural-name=Password Policies
+synopsis=Password Policies define a number of password management rules, as well as requirements for authentication processing.
+property.account-status-notification-handler.synopsis=Specifies the names of the account status notification handlers that are used with the associated password storage scheme.
+property.account-status-notification-handler.syntax.aggregation.constraint-synopsis=The referenced account status notification handlers must be enabled.
+property.allow-expired-password-changes.synopsis=Indicates whether a user whose password is expired is still allowed to change that password using the password modify extended operation.
+property.allow-multiple-password-values.synopsis=Indicates whether user entries can have multiple distinct values for the password attribute.
+property.allow-multiple-password-values.description=This is potentially dangerous because many mechanisms used to change the password do not work well with such a configuration. If multiple password values are allowed, then any of them can be used to authenticate, and they are all subject to the same policy constraints.
+property.allow-pre-encoded-passwords.synopsis=Indicates whether users can change their passwords by providing a pre-encoded value.
+property.allow-pre-encoded-passwords.description=This can cause a security risk because the clear-text version of the password is not known and therefore validation checks cannot be applied to it.
+property.allow-user-password-changes.synopsis=Indicates whether users can change their own passwords.
+property.allow-user-password-changes.description=This check is made in addition to access control evaluation. Both must allow the password change for it to occur.
+property.default-password-storage-scheme.synopsis=Specifies the names of the password storage schemes that are used to encode clear-text passwords for this password policy.
+property.default-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled.
+property.deprecated-password-storage-scheme.synopsis=Specifies the names of the password storage schemes that are considered deprecated for this password policy.
+property.deprecated-password-storage-scheme.description=If a user with this password policy authenticates to the server and his/her password is encoded with a deprecated scheme, those values are removed and replaced with values encoded using the default password storage scheme(s).
+property.deprecated-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled.
+property.expire-passwords-without-warning.synopsis=Indicates whether the Directory Server allows a user's password to expire even if that user has never seen an expiration warning notification.
+property.expire-passwords-without-warning.description=If this property is true, accounts always expire when the expiration time arrives. If this property is false disabled, the user always receives at least one warning notification, and the password expiration is set to the warning time plus the warning interval.
+property.force-change-on-add.synopsis=Indicates whether users are forced to change their passwords upon first authenticating to the Directory Server after their account has been created.
+property.force-change-on-reset.synopsis=Indicates whether users are forced to change their passwords if they are reset by an administrator.
+property.force-change-on-reset.description=For this purpose, anyone with permission to change a given user's password other than that user is considered an administrator.
+property.grace-login-count.synopsis=Specifies the number of grace logins that a user is allowed after the account has expired to allow that user to choose a new password.
+property.grace-login-count.description=A value of 0 indicates that no grace logins are allowed.
+property.idle-lockout-interval.synopsis=Specifies the maximum length of time that an account may remain idle (that is, the associated user does not authenticate to the server) before that user is locked out.
+property.idle-lockout-interval.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds indicates that idle accounts are not automatically locked out. This feature is available only if the last login time is maintained.
+property.last-login-time-attribute.synopsis=Specifies the name or OID of the attribute type that is used to hold the last login time for users with the associated password policy.
+property.last-login-time-attribute.description=This attribute type must be defined in the Directory Server schema and must either be defined as an operational attribute or must be allowed by the set of objectClasses for all users with the associated password policy.
+property.last-login-time-format.synopsis=Specifies the format string that is used to generate the last login time value for users with the associated password policy.
+property.last-login-time-format.description=This format string conforms to the syntax described in the API documentation for the java.text.SimpleDateFormat class.
+property.last-login-time-format.syntax.string.pattern.synopsis=Any valid format string that can be used with the java.text.SimpleDateFormat class.
+property.lockout-duration.synopsis=Specifies the length of time that an account is locked after too many authentication failures.
+property.lockout-duration.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds indicates that the account must remain locked until an administrator resets the password.
+property.lockout-failure-count.synopsis=Specifies the maximum number of authentication failures that a user is allowed before the account is locked out.
+property.lockout-failure-count.description=A value of 0 indicates that accounts are never locked out due to failed attempts.
+property.lockout-failure-expiration-interval.synopsis=Specifies the length of time before an authentication failure is no longer counted against a user for the purposes of account lockout.
+property.lockout-failure-expiration-interval.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds indicates that the authentication failures must never expire. The failure count is always cleared upon a successful authentication.
+property.max-password-age.synopsis=Specifies the maximum length of time that a user can continue using the same password before it must be changed (that is, the password expiration interval).
+property.max-password-age.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds disables password expiration.
+property.max-password-reset-age.synopsis=Specifies the maximum length of time that users have to change passwords after they have been reset by an administrator before they become locked.
+property.max-password-reset-age.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds disables this feature.
+property.min-password-age.synopsis=Specifies the minimum length of time after a password change before the user is allowed to change the password again.
+property.min-password-age.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. This setting can be used to prevent users from changing their passwords repeatedly over a short period of time to flush an old password from the history so that it can be re-used.
+property.password-attribute.synopsis=Specifies the attribute type used to hold user passwords.
+property.password-attribute.description=This attribute type must be defined in the server schema, and it must have either the user password or auth password syntax.
+property.password-change-requires-current-password.synopsis=Indicates whether user password changes must use the password modify extended operation and must include the user's current password before the change is allowed.
+property.password-expiration-warning-interval.synopsis=Specifies the maximum length of time before a user's password actually expires that the server begins to include warning notifications in bind responses for that user.
+property.password-expiration-warning-interval.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds disables the warning interval.
+property.password-generator.synopsis=Specifies the name of the password generator that is used with the associated password policy.
+property.password-generator.description=This is used in conjunction with the password modify extended operation to generate a new password for a user when none was provided in the request.
+property.password-generator.syntax.aggregation.constraint-synopsis=The referenced password generator must be enabled.
+property.password-history-count.synopsis=Specifies the maximum number of former passwords to maintain in the password history.
+property.password-history-count.description=When choosing a new password, the proposed password is checked to ensure that it does not match the current password, nor any other password in the history list. A value of zero indicates that either no password history is to be maintained (if the password history duration has a value of zero seconds), or that there is no maximum number of passwords to maintain in the history (if the password history duration has a value greater than zero seconds).
+property.password-history-duration.synopsis=Specifies the maximum length of time that passwords remain in the password history.
+property.password-history-duration.description=When choosing a new password, the proposed password is checked to ensure that it does not match the current password, nor any other password in the history list. A value of zero seconds indicates that either no password history is to be maintained (if the password history count has a value of zero), or that there is no maximum duration for passwords in the history (if the password history count has a value greater than zero).
+property.password-validator.synopsis=Specifies the names of the password validators that are used with the associated password storage scheme.
+property.password-validator.description=The password validators are invoked when a user attempts to provide a new password, to determine whether the new password is acceptable.
+property.password-validator.syntax.aggregation.constraint-synopsis=The referenced password validators must be enabled.
+property.previous-last-login-time-format.synopsis=Specifies the format string(s) that might have been used with the last login time at any point in the past for users associated with the password policy.
+property.previous-last-login-time-format.description=These values are used to make it possible to parse previous values, but are not used to set new values. The format strings conform to the syntax described in the API documentation for the java.text.SimpleDateFormat class.
+property.previous-last-login-time-format.syntax.string.pattern.synopsis=Any valid format string that can be used with the java.text.SimpleDateFormat class.
+property.require-change-by-time.synopsis=Specifies the time by which all users with the associated password policy must change their passwords.
+property.require-change-by-time.description=The value is expressed in a generalized time format. If this time is equal to the current time or is in the past, then all users are required to change their passwords immediately. The behavior of the server in this mode is identical to the behavior observed when users are forced to change their passwords after an administrative reset.
+property.require-change-by-time.syntax.string.pattern.synopsis=A valid timestamp in generalized time form (for example, a value of "20070409185811Z" indicates a value of April 9, 2007 at 6:58:11 pm GMT).
+property.require-secure-authentication.synopsis=Indicates whether users with the associated password policy are required to authenticate in a secure manner.
+property.require-secure-authentication.description=This might mean either using a secure communication channel between the client and the server, or using a SASL mechanism that does not expose the credentials.
+property.require-secure-password-changes.synopsis=Indicates whether users with the associated password policy are required to change their password in a secure manner that does not expose the credentials.
+property.skip-validation-for-administrators.synopsis=Indicates whether passwords set by administrators are allowed to bypass the password validation process that is required for user password changes.
+property.state-update-failure-policy.synopsis=Specifies how the server deals with the inability to update password policy state information during an authentication attempt.
+property.state-update-failure-policy.description=In particular, this property can be used to control whether an otherwise successful bind operation fails if a failure occurs while attempting to update password policy state information (for example, to clear a record of previous authentication failures or to update the last login time). It can also be used to control whether to reject a bind request if it is known ahead of time that it will not be possible to update the authentication failure times in the event of an unsuccessful bind attempt (for example, if the backend writability mode is disabled).
+property.state-update-failure-policy.syntax.enumeration.value.ignore.synopsis=If a bind attempt would otherwise be successful, then do not reject it if a problem occurs while attempting to update the password policy state information for the user.
+property.state-update-failure-policy.syntax.enumeration.value.proactive.synopsis=Proactively reject any bind attempt if it is known ahead of time that it would not be possible to update the user's password policy state information.
+property.state-update-failure-policy.syntax.enumeration.value.reactive.synopsis=Even if a bind attempt would otherwise be successful, reject it if a problem occurs while attempting to update the password policy state information for the user.
diff --git a/opends/src/admin/messages/PasswordPolicyCfgDefn_ko.properties b/opends/src/admin/messages/PasswordPolicyCfgDefn_ko.properties
new file mode 100644
index 0000000..c21c32d
--- /dev/null
+++ b/opends/src/admin/messages/PasswordPolicyCfgDefn_ko.properties
@@ -0,0 +1,73 @@
+user-friendly-name=Password Policy
+user-friendly-plural-name=Password Policies
+synopsis=Password Policies define a number of password management rules, as well as requirements for authentication processing.
+property.account-status-notification-handler.synopsis=Specifies the names of the account status notification handlers that are used with the associated password storage scheme.
+property.account-status-notification-handler.syntax.aggregation.constraint-synopsis=The referenced account status notification handlers must be enabled.
+property.allow-expired-password-changes.synopsis=Indicates whether a user whose password is expired is still allowed to change that password using the password modify extended operation.
+property.allow-multiple-password-values.synopsis=Indicates whether user entries can have multiple distinct values for the password attribute.
+property.allow-multiple-password-values.description=This is potentially dangerous because many mechanisms used to change the password do not work well with such a configuration. If multiple password values are allowed, then any of them can be used to authenticate, and they are all subject to the same policy constraints.
+property.allow-pre-encoded-passwords.synopsis=Indicates whether users can change their passwords by providing a pre-encoded value.
+property.allow-pre-encoded-passwords.description=This can cause a security risk because the clear-text version of the password is not known and therefore validation checks cannot be applied to it.
+property.allow-user-password-changes.synopsis=Indicates whether users can change their own passwords.
+property.allow-user-password-changes.description=This check is made in addition to access control evaluation. Both must allow the password change for it to occur.
+property.default-password-storage-scheme.synopsis=Specifies the names of the password storage schemes that are used to encode clear-text passwords for this password policy.
+property.default-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled.
+property.deprecated-password-storage-scheme.synopsis=Specifies the names of the password storage schemes that are considered deprecated for this password policy.
+property.deprecated-password-storage-scheme.description=If a user with this password policy authenticates to the server and his/her password is encoded with a deprecated scheme, those values are removed and replaced with values encoded using the default password storage scheme(s).
+property.deprecated-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled.
+property.expire-passwords-without-warning.synopsis=Indicates whether the Directory Server allows a user's password to expire even if that user has never seen an expiration warning notification.
+property.expire-passwords-without-warning.description=If this property is true, accounts always expire when the expiration time arrives. If this property is false disabled, the user always receives at least one warning notification, and the password expiration is set to the warning time plus the warning interval.
+property.force-change-on-add.synopsis=Indicates whether users are forced to change their passwords upon first authenticating to the Directory Server after their account has been created.
+property.force-change-on-reset.synopsis=Indicates whether users are forced to change their passwords if they are reset by an administrator.
+property.force-change-on-reset.description=For this purpose, anyone with permission to change a given user's password other than that user is considered an administrator.
+property.grace-login-count.synopsis=Specifies the number of grace logins that a user is allowed after the account has expired to allow that user to choose a new password.
+property.grace-login-count.description=A value of 0 indicates that no grace logins are allowed.
+property.idle-lockout-interval.synopsis=Specifies the maximum length of time that an account may remain idle (that is, the associated user does not authenticate to the server) before that user is locked out.
+property.idle-lockout-interval.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds indicates that idle accounts are not automatically locked out. This feature is available only if the last login time is maintained.
+property.last-login-time-attribute.synopsis=Specifies the name or OID of the attribute type that is used to hold the last login time for users with the associated password policy.
+property.last-login-time-attribute.description=This attribute type must be defined in the Directory Server schema and must either be defined as an operational attribute or must be allowed by the set of objectClasses for all users with the associated password policy.
+property.last-login-time-format.synopsis=Specifies the format string that is used to generate the last login time value for users with the associated password policy.
+property.last-login-time-format.description=This format string conforms to the syntax described in the API documentation for the java.text.SimpleDateFormat class.
+property.last-login-time-format.syntax.string.pattern.synopsis=Any valid format string that can be used with the java.text.SimpleDateFormat class.
+property.lockout-duration.synopsis=Specifies the length of time that an account is locked after too many authentication failures.
+property.lockout-duration.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds indicates that the account must remain locked until an administrator resets the password.
+property.lockout-failure-count.synopsis=Specifies the maximum number of authentication failures that a user is allowed before the account is locked out.
+property.lockout-failure-count.description=A value of 0 indicates that accounts are never locked out due to failed attempts.
+property.lockout-failure-expiration-interval.synopsis=Specifies the length of time before an authentication failure is no longer counted against a user for the purposes of account lockout.
+property.lockout-failure-expiration-interval.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds indicates that the authentication failures must never expire. The failure count is always cleared upon a successful authentication.
+property.max-password-age.synopsis=Specifies the maximum length of time that a user can continue using the same password before it must be changed (that is, the password expiration interval).
+property.max-password-age.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds disables password expiration.
+property.max-password-reset-age.synopsis=Specifies the maximum length of time that users have to change passwords after they have been reset by an administrator before they become locked.
+property.max-password-reset-age.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds disables this feature.
+property.min-password-age.synopsis=Specifies the minimum length of time after a password change before the user is allowed to change the password again.
+property.min-password-age.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. This setting can be used to prevent users from changing their passwords repeatedly over a short period of time to flush an old password from the history so that it can be re-used.
+property.password-attribute.synopsis=Specifies the attribute type used to hold user passwords.
+property.password-attribute.description=This attribute type must be defined in the server schema, and it must have either the user password or auth password syntax.
+property.password-change-requires-current-password.synopsis=Indicates whether user password changes must use the password modify extended operation and must include the user's current password before the change is allowed.
+property.password-expiration-warning-interval.synopsis=Specifies the maximum length of time before a user's password actually expires that the server begins to include warning notifications in bind responses for that user.
+property.password-expiration-warning-interval.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds disables the warning interval.
+property.password-generator.synopsis=Specifies the name of the password generator that is used with the associated password policy.
+property.password-generator.description=This is used in conjunction with the password modify extended operation to generate a new password for a user when none was provided in the request.
+property.password-generator.syntax.aggregation.constraint-synopsis=The referenced password generator must be enabled.
+property.password-history-count.synopsis=Specifies the maximum number of former passwords to maintain in the password history.
+property.password-history-count.description=When choosing a new password, the proposed password is checked to ensure that it does not match the current password, nor any other password in the history list. A value of zero indicates that either no password history is to be maintained (if the password history duration has a value of zero seconds), or that there is no maximum number of passwords to maintain in the history (if the password history duration has a value greater than zero seconds).
+property.password-history-duration.synopsis=Specifies the maximum length of time that passwords remain in the password history.
+property.password-history-duration.description=When choosing a new password, the proposed password is checked to ensure that it does not match the current password, nor any other password in the history list. A value of zero seconds indicates that either no password history is to be maintained (if the password history count has a value of zero), or that there is no maximum duration for passwords in the history (if the password history count has a value greater than zero).
+property.password-validator.synopsis=Specifies the names of the password validators that are used with the associated password storage scheme.
+property.password-validator.description=The password validators are invoked when a user attempts to provide a new password, to determine whether the new password is acceptable.
+property.password-validator.syntax.aggregation.constraint-synopsis=The referenced password validators must be enabled.
+property.previous-last-login-time-format.synopsis=Specifies the format string(s) that might have been used with the last login time at any point in the past for users associated with the password policy.
+property.previous-last-login-time-format.description=These values are used to make it possible to parse previous values, but are not used to set new values. The format strings conform to the syntax described in the API documentation for the java.text.SimpleDateFormat class.
+property.previous-last-login-time-format.syntax.string.pattern.synopsis=Any valid format string that can be used with the java.text.SimpleDateFormat class.
+property.require-change-by-time.synopsis=Specifies the time by which all users with the associated password policy must change their passwords.
+property.require-change-by-time.description=The value is expressed in a generalized time format. If this time is equal to the current time or is in the past, then all users are required to change their passwords immediately. The behavior of the server in this mode is identical to the behavior observed when users are forced to change their passwords after an administrative reset.
+property.require-change-by-time.syntax.string.pattern.synopsis=A valid timestamp in generalized time form (for example, a value of "20070409185811Z" indicates a value of April 9, 2007 at 6:58:11 pm GMT).
+property.require-secure-authentication.synopsis=Indicates whether users with the associated password policy are required to authenticate in a secure manner.
+property.require-secure-authentication.description=This might mean either using a secure communication channel between the client and the server, or using a SASL mechanism that does not expose the credentials.
+property.require-secure-password-changes.synopsis=Indicates whether users with the associated password policy are required to change their password in a secure manner that does not expose the credentials.
+property.skip-validation-for-administrators.synopsis=Indicates whether passwords set by administrators are allowed to bypass the password validation process that is required for user password changes.
+property.state-update-failure-policy.synopsis=Specifies how the server deals with the inability to update password policy state information during an authentication attempt.
+property.state-update-failure-policy.description=In particular, this property can be used to control whether an otherwise successful bind operation fails if a failure occurs while attempting to update password policy state information (for example, to clear a record of previous authentication failures or to update the last login time). It can also be used to control whether to reject a bind request if it is known ahead of time that it will not be possible to update the authentication failure times in the event of an unsuccessful bind attempt (for example, if the backend writability mode is disabled).
+property.state-update-failure-policy.syntax.enumeration.value.ignore.synopsis=If a bind attempt would otherwise be successful, then do not reject it if a problem occurs while attempting to update the password policy state information for the user.
+property.state-update-failure-policy.syntax.enumeration.value.proactive.synopsis=Proactively reject any bind attempt if it is known ahead of time that it would not be possible to update the user's password policy state information.
+property.state-update-failure-policy.syntax.enumeration.value.reactive.synopsis=Even if a bind attempt would otherwise be successful, reject it if a problem occurs while attempting to update the password policy state information for the user.
diff --git a/opends/src/admin/messages/PasswordPolicyCfgDefn_zh_CN.properties b/opends/src/admin/messages/PasswordPolicyCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..c21c32d
--- /dev/null
+++ b/opends/src/admin/messages/PasswordPolicyCfgDefn_zh_CN.properties
@@ -0,0 +1,73 @@
+user-friendly-name=Password Policy
+user-friendly-plural-name=Password Policies
+synopsis=Password Policies define a number of password management rules, as well as requirements for authentication processing.
+property.account-status-notification-handler.synopsis=Specifies the names of the account status notification handlers that are used with the associated password storage scheme.
+property.account-status-notification-handler.syntax.aggregation.constraint-synopsis=The referenced account status notification handlers must be enabled.
+property.allow-expired-password-changes.synopsis=Indicates whether a user whose password is expired is still allowed to change that password using the password modify extended operation.
+property.allow-multiple-password-values.synopsis=Indicates whether user entries can have multiple distinct values for the password attribute.
+property.allow-multiple-password-values.description=This is potentially dangerous because many mechanisms used to change the password do not work well with such a configuration. If multiple password values are allowed, then any of them can be used to authenticate, and they are all subject to the same policy constraints.
+property.allow-pre-encoded-passwords.synopsis=Indicates whether users can change their passwords by providing a pre-encoded value.
+property.allow-pre-encoded-passwords.description=This can cause a security risk because the clear-text version of the password is not known and therefore validation checks cannot be applied to it.
+property.allow-user-password-changes.synopsis=Indicates whether users can change their own passwords.
+property.allow-user-password-changes.description=This check is made in addition to access control evaluation. Both must allow the password change for it to occur.
+property.default-password-storage-scheme.synopsis=Specifies the names of the password storage schemes that are used to encode clear-text passwords for this password policy.
+property.default-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled.
+property.deprecated-password-storage-scheme.synopsis=Specifies the names of the password storage schemes that are considered deprecated for this password policy.
+property.deprecated-password-storage-scheme.description=If a user with this password policy authenticates to the server and his/her password is encoded with a deprecated scheme, those values are removed and replaced with values encoded using the default password storage scheme(s).
+property.deprecated-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled.
+property.expire-passwords-without-warning.synopsis=Indicates whether the Directory Server allows a user's password to expire even if that user has never seen an expiration warning notification.
+property.expire-passwords-without-warning.description=If this property is true, accounts always expire when the expiration time arrives. If this property is false disabled, the user always receives at least one warning notification, and the password expiration is set to the warning time plus the warning interval.
+property.force-change-on-add.synopsis=Indicates whether users are forced to change their passwords upon first authenticating to the Directory Server after their account has been created.
+property.force-change-on-reset.synopsis=Indicates whether users are forced to change their passwords if they are reset by an administrator.
+property.force-change-on-reset.description=For this purpose, anyone with permission to change a given user's password other than that user is considered an administrator.
+property.grace-login-count.synopsis=Specifies the number of grace logins that a user is allowed after the account has expired to allow that user to choose a new password.
+property.grace-login-count.description=A value of 0 indicates that no grace logins are allowed.
+property.idle-lockout-interval.synopsis=Specifies the maximum length of time that an account may remain idle (that is, the associated user does not authenticate to the server) before that user is locked out.
+property.idle-lockout-interval.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds indicates that idle accounts are not automatically locked out. This feature is available only if the last login time is maintained.
+property.last-login-time-attribute.synopsis=Specifies the name or OID of the attribute type that is used to hold the last login time for users with the associated password policy.
+property.last-login-time-attribute.description=This attribute type must be defined in the Directory Server schema and must either be defined as an operational attribute or must be allowed by the set of objectClasses for all users with the associated password policy.
+property.last-login-time-format.synopsis=Specifies the format string that is used to generate the last login time value for users with the associated password policy.
+property.last-login-time-format.description=This format string conforms to the syntax described in the API documentation for the java.text.SimpleDateFormat class.
+property.last-login-time-format.syntax.string.pattern.synopsis=Any valid format string that can be used with the java.text.SimpleDateFormat class.
+property.lockout-duration.synopsis=Specifies the length of time that an account is locked after too many authentication failures.
+property.lockout-duration.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds indicates that the account must remain locked until an administrator resets the password.
+property.lockout-failure-count.synopsis=Specifies the maximum number of authentication failures that a user is allowed before the account is locked out.
+property.lockout-failure-count.description=A value of 0 indicates that accounts are never locked out due to failed attempts.
+property.lockout-failure-expiration-interval.synopsis=Specifies the length of time before an authentication failure is no longer counted against a user for the purposes of account lockout.
+property.lockout-failure-expiration-interval.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds indicates that the authentication failures must never expire. The failure count is always cleared upon a successful authentication.
+property.max-password-age.synopsis=Specifies the maximum length of time that a user can continue using the same password before it must be changed (that is, the password expiration interval).
+property.max-password-age.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds disables password expiration.
+property.max-password-reset-age.synopsis=Specifies the maximum length of time that users have to change passwords after they have been reset by an administrator before they become locked.
+property.max-password-reset-age.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds disables this feature.
+property.min-password-age.synopsis=Specifies the minimum length of time after a password change before the user is allowed to change the password again.
+property.min-password-age.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. This setting can be used to prevent users from changing their passwords repeatedly over a short period of time to flush an old password from the history so that it can be re-used.
+property.password-attribute.synopsis=Specifies the attribute type used to hold user passwords.
+property.password-attribute.description=This attribute type must be defined in the server schema, and it must have either the user password or auth password syntax.
+property.password-change-requires-current-password.synopsis=Indicates whether user password changes must use the password modify extended operation and must include the user's current password before the change is allowed.
+property.password-expiration-warning-interval.synopsis=Specifies the maximum length of time before a user's password actually expires that the server begins to include warning notifications in bind responses for that user.
+property.password-expiration-warning-interval.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds disables the warning interval.
+property.password-generator.synopsis=Specifies the name of the password generator that is used with the associated password policy.
+property.password-generator.description=This is used in conjunction with the password modify extended operation to generate a new password for a user when none was provided in the request.
+property.password-generator.syntax.aggregation.constraint-synopsis=The referenced password generator must be enabled.
+property.password-history-count.synopsis=Specifies the maximum number of former passwords to maintain in the password history.
+property.password-history-count.description=When choosing a new password, the proposed password is checked to ensure that it does not match the current password, nor any other password in the history list. A value of zero indicates that either no password history is to be maintained (if the password history duration has a value of zero seconds), or that there is no maximum number of passwords to maintain in the history (if the password history duration has a value greater than zero seconds).
+property.password-history-duration.synopsis=Specifies the maximum length of time that passwords remain in the password history.
+property.password-history-duration.description=When choosing a new password, the proposed password is checked to ensure that it does not match the current password, nor any other password in the history list. A value of zero seconds indicates that either no password history is to be maintained (if the password history count has a value of zero), or that there is no maximum duration for passwords in the history (if the password history count has a value greater than zero).
+property.password-validator.synopsis=Specifies the names of the password validators that are used with the associated password storage scheme.
+property.password-validator.description=The password validators are invoked when a user attempts to provide a new password, to determine whether the new password is acceptable.
+property.password-validator.syntax.aggregation.constraint-synopsis=The referenced password validators must be enabled.
+property.previous-last-login-time-format.synopsis=Specifies the format string(s) that might have been used with the last login time at any point in the past for users associated with the password policy.
+property.previous-last-login-time-format.description=These values are used to make it possible to parse previous values, but are not used to set new values. The format strings conform to the syntax described in the API documentation for the java.text.SimpleDateFormat class.
+property.previous-last-login-time-format.syntax.string.pattern.synopsis=Any valid format string that can be used with the java.text.SimpleDateFormat class.
+property.require-change-by-time.synopsis=Specifies the time by which all users with the associated password policy must change their passwords.
+property.require-change-by-time.description=The value is expressed in a generalized time format. If this time is equal to the current time or is in the past, then all users are required to change their passwords immediately. The behavior of the server in this mode is identical to the behavior observed when users are forced to change their passwords after an administrative reset.
+property.require-change-by-time.syntax.string.pattern.synopsis=A valid timestamp in generalized time form (for example, a value of "20070409185811Z" indicates a value of April 9, 2007 at 6:58:11 pm GMT).
+property.require-secure-authentication.synopsis=Indicates whether users with the associated password policy are required to authenticate in a secure manner.
+property.require-secure-authentication.description=This might mean either using a secure communication channel between the client and the server, or using a SASL mechanism that does not expose the credentials.
+property.require-secure-password-changes.synopsis=Indicates whether users with the associated password policy are required to change their password in a secure manner that does not expose the credentials.
+property.skip-validation-for-administrators.synopsis=Indicates whether passwords set by administrators are allowed to bypass the password validation process that is required for user password changes.
+property.state-update-failure-policy.synopsis=Specifies how the server deals with the inability to update password policy state information during an authentication attempt.
+property.state-update-failure-policy.description=In particular, this property can be used to control whether an otherwise successful bind operation fails if a failure occurs while attempting to update password policy state information (for example, to clear a record of previous authentication failures or to update the last login time). It can also be used to control whether to reject a bind request if it is known ahead of time that it will not be possible to update the authentication failure times in the event of an unsuccessful bind attempt (for example, if the backend writability mode is disabled).
+property.state-update-failure-policy.syntax.enumeration.value.ignore.synopsis=If a bind attempt would otherwise be successful, then do not reject it if a problem occurs while attempting to update the password policy state information for the user.
+property.state-update-failure-policy.syntax.enumeration.value.proactive.synopsis=Proactively reject any bind attempt if it is known ahead of time that it would not be possible to update the user's password policy state information.
+property.state-update-failure-policy.syntax.enumeration.value.reactive.synopsis=Even if a bind attempt would otherwise be successful, reject it if a problem occurs while attempting to update the password policy state information for the user.
diff --git a/opends/src/admin/messages/PasswordPolicyCfgDefn_zh_TW.properties b/opends/src/admin/messages/PasswordPolicyCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..c21c32d
--- /dev/null
+++ b/opends/src/admin/messages/PasswordPolicyCfgDefn_zh_TW.properties
@@ -0,0 +1,73 @@
+user-friendly-name=Password Policy
+user-friendly-plural-name=Password Policies
+synopsis=Password Policies define a number of password management rules, as well as requirements for authentication processing.
+property.account-status-notification-handler.synopsis=Specifies the names of the account status notification handlers that are used with the associated password storage scheme.
+property.account-status-notification-handler.syntax.aggregation.constraint-synopsis=The referenced account status notification handlers must be enabled.
+property.allow-expired-password-changes.synopsis=Indicates whether a user whose password is expired is still allowed to change that password using the password modify extended operation.
+property.allow-multiple-password-values.synopsis=Indicates whether user entries can have multiple distinct values for the password attribute.
+property.allow-multiple-password-values.description=This is potentially dangerous because many mechanisms used to change the password do not work well with such a configuration. If multiple password values are allowed, then any of them can be used to authenticate, and they are all subject to the same policy constraints.
+property.allow-pre-encoded-passwords.synopsis=Indicates whether users can change their passwords by providing a pre-encoded value.
+property.allow-pre-encoded-passwords.description=This can cause a security risk because the clear-text version of the password is not known and therefore validation checks cannot be applied to it.
+property.allow-user-password-changes.synopsis=Indicates whether users can change their own passwords.
+property.allow-user-password-changes.description=This check is made in addition to access control evaluation. Both must allow the password change for it to occur.
+property.default-password-storage-scheme.synopsis=Specifies the names of the password storage schemes that are used to encode clear-text passwords for this password policy.
+property.default-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled.
+property.deprecated-password-storage-scheme.synopsis=Specifies the names of the password storage schemes that are considered deprecated for this password policy.
+property.deprecated-password-storage-scheme.description=If a user with this password policy authenticates to the server and his/her password is encoded with a deprecated scheme, those values are removed and replaced with values encoded using the default password storage scheme(s).
+property.deprecated-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled.
+property.expire-passwords-without-warning.synopsis=Indicates whether the Directory Server allows a user's password to expire even if that user has never seen an expiration warning notification.
+property.expire-passwords-without-warning.description=If this property is true, accounts always expire when the expiration time arrives. If this property is false disabled, the user always receives at least one warning notification, and the password expiration is set to the warning time plus the warning interval.
+property.force-change-on-add.synopsis=Indicates whether users are forced to change their passwords upon first authenticating to the Directory Server after their account has been created.
+property.force-change-on-reset.synopsis=Indicates whether users are forced to change their passwords if they are reset by an administrator.
+property.force-change-on-reset.description=For this purpose, anyone with permission to change a given user's password other than that user is considered an administrator.
+property.grace-login-count.synopsis=Specifies the number of grace logins that a user is allowed after the account has expired to allow that user to choose a new password.
+property.grace-login-count.description=A value of 0 indicates that no grace logins are allowed.
+property.idle-lockout-interval.synopsis=Specifies the maximum length of time that an account may remain idle (that is, the associated user does not authenticate to the server) before that user is locked out.
+property.idle-lockout-interval.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds indicates that idle accounts are not automatically locked out. This feature is available only if the last login time is maintained.
+property.last-login-time-attribute.synopsis=Specifies the name or OID of the attribute type that is used to hold the last login time for users with the associated password policy.
+property.last-login-time-attribute.description=This attribute type must be defined in the Directory Server schema and must either be defined as an operational attribute or must be allowed by the set of objectClasses for all users with the associated password policy.
+property.last-login-time-format.synopsis=Specifies the format string that is used to generate the last login time value for users with the associated password policy.
+property.last-login-time-format.description=This format string conforms to the syntax described in the API documentation for the java.text.SimpleDateFormat class.
+property.last-login-time-format.syntax.string.pattern.synopsis=Any valid format string that can be used with the java.text.SimpleDateFormat class.
+property.lockout-duration.synopsis=Specifies the length of time that an account is locked after too many authentication failures.
+property.lockout-duration.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds indicates that the account must remain locked until an administrator resets the password.
+property.lockout-failure-count.synopsis=Specifies the maximum number of authentication failures that a user is allowed before the account is locked out.
+property.lockout-failure-count.description=A value of 0 indicates that accounts are never locked out due to failed attempts.
+property.lockout-failure-expiration-interval.synopsis=Specifies the length of time before an authentication failure is no longer counted against a user for the purposes of account lockout.
+property.lockout-failure-expiration-interval.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds indicates that the authentication failures must never expire. The failure count is always cleared upon a successful authentication.
+property.max-password-age.synopsis=Specifies the maximum length of time that a user can continue using the same password before it must be changed (that is, the password expiration interval).
+property.max-password-age.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds disables password expiration.
+property.max-password-reset-age.synopsis=Specifies the maximum length of time that users have to change passwords after they have been reset by an administrator before they become locked.
+property.max-password-reset-age.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds disables this feature.
+property.min-password-age.synopsis=Specifies the minimum length of time after a password change before the user is allowed to change the password again.
+property.min-password-age.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. This setting can be used to prevent users from changing their passwords repeatedly over a short period of time to flush an old password from the history so that it can be re-used.
+property.password-attribute.synopsis=Specifies the attribute type used to hold user passwords.
+property.password-attribute.description=This attribute type must be defined in the server schema, and it must have either the user password or auth password syntax.
+property.password-change-requires-current-password.synopsis=Indicates whether user password changes must use the password modify extended operation and must include the user's current password before the change is allowed.
+property.password-expiration-warning-interval.synopsis=Specifies the maximum length of time before a user's password actually expires that the server begins to include warning notifications in bind responses for that user.
+property.password-expiration-warning-interval.description=The value of this attribute is an integer followed by a unit of seconds, minutes, hours, days, or weeks. A value of 0 seconds disables the warning interval.
+property.password-generator.synopsis=Specifies the name of the password generator that is used with the associated password policy.
+property.password-generator.description=This is used in conjunction with the password modify extended operation to generate a new password for a user when none was provided in the request.
+property.password-generator.syntax.aggregation.constraint-synopsis=The referenced password generator must be enabled.
+property.password-history-count.synopsis=Specifies the maximum number of former passwords to maintain in the password history.
+property.password-history-count.description=When choosing a new password, the proposed password is checked to ensure that it does not match the current password, nor any other password in the history list. A value of zero indicates that either no password history is to be maintained (if the password history duration has a value of zero seconds), or that there is no maximum number of passwords to maintain in the history (if the password history duration has a value greater than zero seconds).
+property.password-history-duration.synopsis=Specifies the maximum length of time that passwords remain in the password history.
+property.password-history-duration.description=When choosing a new password, the proposed password is checked to ensure that it does not match the current password, nor any other password in the history list. A value of zero seconds indicates that either no password history is to be maintained (if the password history count has a value of zero), or that there is no maximum duration for passwords in the history (if the password history count has a value greater than zero).
+property.password-validator.synopsis=Specifies the names of the password validators that are used with the associated password storage scheme.
+property.password-validator.description=The password validators are invoked when a user attempts to provide a new password, to determine whether the new password is acceptable.
+property.password-validator.syntax.aggregation.constraint-synopsis=The referenced password validators must be enabled.
+property.previous-last-login-time-format.synopsis=Specifies the format string(s) that might have been used with the last login time at any point in the past for users associated with the password policy.
+property.previous-last-login-time-format.description=These values are used to make it possible to parse previous values, but are not used to set new values. The format strings conform to the syntax described in the API documentation for the java.text.SimpleDateFormat class.
+property.previous-last-login-time-format.syntax.string.pattern.synopsis=Any valid format string that can be used with the java.text.SimpleDateFormat class.
+property.require-change-by-time.synopsis=Specifies the time by which all users with the associated password policy must change their passwords.
+property.require-change-by-time.description=The value is expressed in a generalized time format. If this time is equal to the current time or is in the past, then all users are required to change their passwords immediately. The behavior of the server in this mode is identical to the behavior observed when users are forced to change their passwords after an administrative reset.
+property.require-change-by-time.syntax.string.pattern.synopsis=A valid timestamp in generalized time form (for example, a value of "20070409185811Z" indicates a value of April 9, 2007 at 6:58:11 pm GMT).
+property.require-secure-authentication.synopsis=Indicates whether users with the associated password policy are required to authenticate in a secure manner.
+property.require-secure-authentication.description=This might mean either using a secure communication channel between the client and the server, or using a SASL mechanism that does not expose the credentials.
+property.require-secure-password-changes.synopsis=Indicates whether users with the associated password policy are required to change their password in a secure manner that does not expose the credentials.
+property.skip-validation-for-administrators.synopsis=Indicates whether passwords set by administrators are allowed to bypass the password validation process that is required for user password changes.
+property.state-update-failure-policy.synopsis=Specifies how the server deals with the inability to update password policy state information during an authentication attempt.
+property.state-update-failure-policy.description=In particular, this property can be used to control whether an otherwise successful bind operation fails if a failure occurs while attempting to update password policy state information (for example, to clear a record of previous authentication failures or to update the last login time). It can also be used to control whether to reject a bind request if it is known ahead of time that it will not be possible to update the authentication failure times in the event of an unsuccessful bind attempt (for example, if the backend writability mode is disabled).
+property.state-update-failure-policy.syntax.enumeration.value.ignore.synopsis=If a bind attempt would otherwise be successful, then do not reject it if a problem occurs while attempting to update the password policy state information for the user.
+property.state-update-failure-policy.syntax.enumeration.value.proactive.synopsis=Proactively reject any bind attempt if it is known ahead of time that it would not be possible to update the user's password policy state information.
+property.state-update-failure-policy.syntax.enumeration.value.reactive.synopsis=Even if a bind attempt would otherwise be successful, reject it if a problem occurs while attempting to update the password policy state information for the user.
diff --git a/opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn.properties b/opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn.properties
new file mode 100644
index 0000000..40915e8
--- /dev/null
+++ b/opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn.properties
@@ -0,0 +1,64 @@
+user-friendly-name=Password Policy Import Plugin
+user-friendly-plural-name=Password Policy Import Plugins
+synopsis=The Password Policy Import Plugin ensures that clear-text passwords contained in LDIF entries are properly encoded before they are stored in the appropriate Directory Server backend.
+property.default-auth-password-storage-scheme.synopsis=Specifies the names of password storage schemes that to be used for encoding passwords contained in attributes with the auth password syntax for entries that do not include the ds-pwp-password-policy-dn attribute specifying which password policy should be used to govern them.
+property.default-auth-password-storage-scheme.default-behavior.alias.synopsis=If the default password policy uses an attribute with the auth password syntax, then the server uses the default password storage schemes for that password policy. Otherwise, it encodes auth password values using the "SHA1" scheme.
+property.default-auth-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled when the Password Policy Import plug-in is enabled.
+property.default-user-password-storage-scheme.synopsis=Specifies the names of the password storage schemes to be used for encoding passwords contained in attributes with the user password syntax for entries that do not include the ds-pwp-password-policy-dn attribute specifying which password policy is to be used to govern them.
+property.default-user-password-storage-scheme.default-behavior.alias.synopsis=If the default password policy uses the attribute with the user password syntax, then the server uses the default password storage schemes for that password policy. Otherwise, it encodes user password values using the "SSHA" scheme.
+property.default-user-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled when the Password Policy Import Plugin is enabled.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_de.properties b/opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_de.properties
new file mode 100644
index 0000000..40915e8
--- /dev/null
+++ b/opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_de.properties
@@ -0,0 +1,64 @@
+user-friendly-name=Password Policy Import Plugin
+user-friendly-plural-name=Password Policy Import Plugins
+synopsis=The Password Policy Import Plugin ensures that clear-text passwords contained in LDIF entries are properly encoded before they are stored in the appropriate Directory Server backend.
+property.default-auth-password-storage-scheme.synopsis=Specifies the names of password storage schemes that to be used for encoding passwords contained in attributes with the auth password syntax for entries that do not include the ds-pwp-password-policy-dn attribute specifying which password policy should be used to govern them.
+property.default-auth-password-storage-scheme.default-behavior.alias.synopsis=If the default password policy uses an attribute with the auth password syntax, then the server uses the default password storage schemes for that password policy. Otherwise, it encodes auth password values using the "SHA1" scheme.
+property.default-auth-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled when the Password Policy Import plug-in is enabled.
+property.default-user-password-storage-scheme.synopsis=Specifies the names of the password storage schemes to be used for encoding passwords contained in attributes with the user password syntax for entries that do not include the ds-pwp-password-policy-dn attribute specifying which password policy is to be used to govern them.
+property.default-user-password-storage-scheme.default-behavior.alias.synopsis=If the default password policy uses the attribute with the user password syntax, then the server uses the default password storage schemes for that password policy. Otherwise, it encodes user password values using the "SSHA" scheme.
+property.default-user-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled when the Password Policy Import Plugin is enabled.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_es.properties b/opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_es.properties
new file mode 100644
index 0000000..40915e8
--- /dev/null
+++ b/opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_es.properties
@@ -0,0 +1,64 @@
+user-friendly-name=Password Policy Import Plugin
+user-friendly-plural-name=Password Policy Import Plugins
+synopsis=The Password Policy Import Plugin ensures that clear-text passwords contained in LDIF entries are properly encoded before they are stored in the appropriate Directory Server backend.
+property.default-auth-password-storage-scheme.synopsis=Specifies the names of password storage schemes that to be used for encoding passwords contained in attributes with the auth password syntax for entries that do not include the ds-pwp-password-policy-dn attribute specifying which password policy should be used to govern them.
+property.default-auth-password-storage-scheme.default-behavior.alias.synopsis=If the default password policy uses an attribute with the auth password syntax, then the server uses the default password storage schemes for that password policy. Otherwise, it encodes auth password values using the "SHA1" scheme.
+property.default-auth-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled when the Password Policy Import plug-in is enabled.
+property.default-user-password-storage-scheme.synopsis=Specifies the names of the password storage schemes to be used for encoding passwords contained in attributes with the user password syntax for entries that do not include the ds-pwp-password-policy-dn attribute specifying which password policy is to be used to govern them.
+property.default-user-password-storage-scheme.default-behavior.alias.synopsis=If the default password policy uses the attribute with the user password syntax, then the server uses the default password storage schemes for that password policy. Otherwise, it encodes user password values using the "SSHA" scheme.
+property.default-user-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled when the Password Policy Import Plugin is enabled.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_fr.properties b/opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_fr.properties
new file mode 100644
index 0000000..40915e8
--- /dev/null
+++ b/opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_fr.properties
@@ -0,0 +1,64 @@
+user-friendly-name=Password Policy Import Plugin
+user-friendly-plural-name=Password Policy Import Plugins
+synopsis=The Password Policy Import Plugin ensures that clear-text passwords contained in LDIF entries are properly encoded before they are stored in the appropriate Directory Server backend.
+property.default-auth-password-storage-scheme.synopsis=Specifies the names of password storage schemes that to be used for encoding passwords contained in attributes with the auth password syntax for entries that do not include the ds-pwp-password-policy-dn attribute specifying which password policy should be used to govern them.
+property.default-auth-password-storage-scheme.default-behavior.alias.synopsis=If the default password policy uses an attribute with the auth password syntax, then the server uses the default password storage schemes for that password policy. Otherwise, it encodes auth password values using the "SHA1" scheme.
+property.default-auth-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled when the Password Policy Import plug-in is enabled.
+property.default-user-password-storage-scheme.synopsis=Specifies the names of the password storage schemes to be used for encoding passwords contained in attributes with the user password syntax for entries that do not include the ds-pwp-password-policy-dn attribute specifying which password policy is to be used to govern them.
+property.default-user-password-storage-scheme.default-behavior.alias.synopsis=If the default password policy uses the attribute with the user password syntax, then the server uses the default password storage schemes for that password policy. Otherwise, it encodes user password values using the "SSHA" scheme.
+property.default-user-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled when the Password Policy Import Plugin is enabled.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_ja.properties b/opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_ja.properties
new file mode 100644
index 0000000..40915e8
--- /dev/null
+++ b/opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_ja.properties
@@ -0,0 +1,64 @@
+user-friendly-name=Password Policy Import Plugin
+user-friendly-plural-name=Password Policy Import Plugins
+synopsis=The Password Policy Import Plugin ensures that clear-text passwords contained in LDIF entries are properly encoded before they are stored in the appropriate Directory Server backend.
+property.default-auth-password-storage-scheme.synopsis=Specifies the names of password storage schemes that to be used for encoding passwords contained in attributes with the auth password syntax for entries that do not include the ds-pwp-password-policy-dn attribute specifying which password policy should be used to govern them.
+property.default-auth-password-storage-scheme.default-behavior.alias.synopsis=If the default password policy uses an attribute with the auth password syntax, then the server uses the default password storage schemes for that password policy. Otherwise, it encodes auth password values using the "SHA1" scheme.
+property.default-auth-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled when the Password Policy Import plug-in is enabled.
+property.default-user-password-storage-scheme.synopsis=Specifies the names of the password storage schemes to be used for encoding passwords contained in attributes with the user password syntax for entries that do not include the ds-pwp-password-policy-dn attribute specifying which password policy is to be used to govern them.
+property.default-user-password-storage-scheme.default-behavior.alias.synopsis=If the default password policy uses the attribute with the user password syntax, then the server uses the default password storage schemes for that password policy. Otherwise, it encodes user password values using the "SSHA" scheme.
+property.default-user-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled when the Password Policy Import Plugin is enabled.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_ko.properties b/opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_ko.properties
new file mode 100644
index 0000000..40915e8
--- /dev/null
+++ b/opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_ko.properties
@@ -0,0 +1,64 @@
+user-friendly-name=Password Policy Import Plugin
+user-friendly-plural-name=Password Policy Import Plugins
+synopsis=The Password Policy Import Plugin ensures that clear-text passwords contained in LDIF entries are properly encoded before they are stored in the appropriate Directory Server backend.
+property.default-auth-password-storage-scheme.synopsis=Specifies the names of password storage schemes that to be used for encoding passwords contained in attributes with the auth password syntax for entries that do not include the ds-pwp-password-policy-dn attribute specifying which password policy should be used to govern them.
+property.default-auth-password-storage-scheme.default-behavior.alias.synopsis=If the default password policy uses an attribute with the auth password syntax, then the server uses the default password storage schemes for that password policy. Otherwise, it encodes auth password values using the "SHA1" scheme.
+property.default-auth-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled when the Password Policy Import plug-in is enabled.
+property.default-user-password-storage-scheme.synopsis=Specifies the names of the password storage schemes to be used for encoding passwords contained in attributes with the user password syntax for entries that do not include the ds-pwp-password-policy-dn attribute specifying which password policy is to be used to govern them.
+property.default-user-password-storage-scheme.default-behavior.alias.synopsis=If the default password policy uses the attribute with the user password syntax, then the server uses the default password storage schemes for that password policy. Otherwise, it encodes user password values using the "SSHA" scheme.
+property.default-user-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled when the Password Policy Import Plugin is enabled.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_zh_CN.properties b/opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..40915e8
--- /dev/null
+++ b/opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_zh_CN.properties
@@ -0,0 +1,64 @@
+user-friendly-name=Password Policy Import Plugin
+user-friendly-plural-name=Password Policy Import Plugins
+synopsis=The Password Policy Import Plugin ensures that clear-text passwords contained in LDIF entries are properly encoded before they are stored in the appropriate Directory Server backend.
+property.default-auth-password-storage-scheme.synopsis=Specifies the names of password storage schemes that to be used for encoding passwords contained in attributes with the auth password syntax for entries that do not include the ds-pwp-password-policy-dn attribute specifying which password policy should be used to govern them.
+property.default-auth-password-storage-scheme.default-behavior.alias.synopsis=If the default password policy uses an attribute with the auth password syntax, then the server uses the default password storage schemes for that password policy. Otherwise, it encodes auth password values using the "SHA1" scheme.
+property.default-auth-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled when the Password Policy Import plug-in is enabled.
+property.default-user-password-storage-scheme.synopsis=Specifies the names of the password storage schemes to be used for encoding passwords contained in attributes with the user password syntax for entries that do not include the ds-pwp-password-policy-dn attribute specifying which password policy is to be used to govern them.
+property.default-user-password-storage-scheme.default-behavior.alias.synopsis=If the default password policy uses the attribute with the user password syntax, then the server uses the default password storage schemes for that password policy. Otherwise, it encodes user password values using the "SSHA" scheme.
+property.default-user-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled when the Password Policy Import Plugin is enabled.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_zh_TW.properties b/opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..40915e8
--- /dev/null
+++ b/opends/src/admin/messages/PasswordPolicyImportPluginCfgDefn_zh_TW.properties
@@ -0,0 +1,64 @@
+user-friendly-name=Password Policy Import Plugin
+user-friendly-plural-name=Password Policy Import Plugins
+synopsis=The Password Policy Import Plugin ensures that clear-text passwords contained in LDIF entries are properly encoded before they are stored in the appropriate Directory Server backend.
+property.default-auth-password-storage-scheme.synopsis=Specifies the names of password storage schemes that to be used for encoding passwords contained in attributes with the auth password syntax for entries that do not include the ds-pwp-password-policy-dn attribute specifying which password policy should be used to govern them.
+property.default-auth-password-storage-scheme.default-behavior.alias.synopsis=If the default password policy uses an attribute with the auth password syntax, then the server uses the default password storage schemes for that password policy. Otherwise, it encodes auth password values using the "SHA1" scheme.
+property.default-auth-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled when the Password Policy Import plug-in is enabled.
+property.default-user-password-storage-scheme.synopsis=Specifies the names of the password storage schemes to be used for encoding passwords contained in attributes with the user password syntax for entries that do not include the ds-pwp-password-policy-dn attribute specifying which password policy is to be used to govern them.
+property.default-user-password-storage-scheme.default-behavior.alias.synopsis=If the default password policy uses the attribute with the user password syntax, then the server uses the default password storage schemes for that password policy. Otherwise, it encodes user password values using the "SSHA" scheme.
+property.default-user-password-storage-scheme.syntax.aggregation.constraint-synopsis=The referenced password storage schemes must be enabled when the Password Policy Import Plugin is enabled.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn.properties b/opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn.properties
new file mode 100644
index 0000000..2504e39
--- /dev/null
+++ b/opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Password Policy State Extended Operation Handler
+user-friendly-plural-name=Password Policy State Extended Operation Handlers
+synopsis=The Password Policy State Extended Operation Handler provides the ability for administrators to request and optionally alter password policy state information for a specified user.
+property.enabled.synopsis=Indicates whether the Password Policy State Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Policy State Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_de.properties b/opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..2504e39
--- /dev/null
+++ b/opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_de.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Password Policy State Extended Operation Handler
+user-friendly-plural-name=Password Policy State Extended Operation Handlers
+synopsis=The Password Policy State Extended Operation Handler provides the ability for administrators to request and optionally alter password policy state information for a specified user.
+property.enabled.synopsis=Indicates whether the Password Policy State Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Policy State Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_es.properties b/opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..2504e39
--- /dev/null
+++ b/opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_es.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Password Policy State Extended Operation Handler
+user-friendly-plural-name=Password Policy State Extended Operation Handlers
+synopsis=The Password Policy State Extended Operation Handler provides the ability for administrators to request and optionally alter password policy state information for a specified user.
+property.enabled.synopsis=Indicates whether the Password Policy State Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Policy State Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_fr.properties b/opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..2504e39
--- /dev/null
+++ b/opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_fr.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Password Policy State Extended Operation Handler
+user-friendly-plural-name=Password Policy State Extended Operation Handlers
+synopsis=The Password Policy State Extended Operation Handler provides the ability for administrators to request and optionally alter password policy state information for a specified user.
+property.enabled.synopsis=Indicates whether the Password Policy State Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Policy State Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_ja.properties b/opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..2504e39
--- /dev/null
+++ b/opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_ja.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Password Policy State Extended Operation Handler
+user-friendly-plural-name=Password Policy State Extended Operation Handlers
+synopsis=The Password Policy State Extended Operation Handler provides the ability for administrators to request and optionally alter password policy state information for a specified user.
+property.enabled.synopsis=Indicates whether the Password Policy State Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Policy State Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_ko.properties b/opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..2504e39
--- /dev/null
+++ b/opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_ko.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Password Policy State Extended Operation Handler
+user-friendly-plural-name=Password Policy State Extended Operation Handlers
+synopsis=The Password Policy State Extended Operation Handler provides the ability for administrators to request and optionally alter password policy state information for a specified user.
+property.enabled.synopsis=Indicates whether the Password Policy State Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Policy State Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..2504e39
--- /dev/null
+++ b/opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Password Policy State Extended Operation Handler
+user-friendly-plural-name=Password Policy State Extended Operation Handlers
+synopsis=The Password Policy State Extended Operation Handler provides the ability for administrators to request and optionally alter password policy state information for a specified user.
+property.enabled.synopsis=Indicates whether the Password Policy State Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Policy State Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..2504e39
--- /dev/null
+++ b/opends/src/admin/messages/PasswordPolicyStateExtendedOperationHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Password Policy State Extended Operation Handler
+user-friendly-plural-name=Password Policy State Extended Operation Handlers
+synopsis=The Password Policy State Extended Operation Handler provides the ability for administrators to request and optionally alter password policy state information for a specified user.
+property.enabled.synopsis=Indicates whether the Password Policy State Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Policy State Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/PasswordStorageSchemeCfgDefn.properties b/opends/src/admin/messages/PasswordStorageSchemeCfgDefn.properties
new file mode 100644
index 0000000..547ddee
--- /dev/null
+++ b/opends/src/admin/messages/PasswordStorageSchemeCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Password Storage Scheme
+user-friendly-plural-name=Password Storage Schemes
+synopsis=Password Storage Schemes encode new passwords provided by users so that they are stored in an encoded manner. This makes it difficult or impossible for someone to determine the clear-text passwords from the encoded values.
+description=Password Storage Schemes also determine whether a clear-text password provided by a client matches the encoded value stored in the server.
+property.enabled.synopsis=Indicates whether the Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/PasswordStorageSchemeCfgDefn_de.properties b/opends/src/admin/messages/PasswordStorageSchemeCfgDefn_de.properties
new file mode 100644
index 0000000..547ddee
--- /dev/null
+++ b/opends/src/admin/messages/PasswordStorageSchemeCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Password Storage Scheme
+user-friendly-plural-name=Password Storage Schemes
+synopsis=Password Storage Schemes encode new passwords provided by users so that they are stored in an encoded manner. This makes it difficult or impossible for someone to determine the clear-text passwords from the encoded values.
+description=Password Storage Schemes also determine whether a clear-text password provided by a client matches the encoded value stored in the server.
+property.enabled.synopsis=Indicates whether the Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/PasswordStorageSchemeCfgDefn_es.properties b/opends/src/admin/messages/PasswordStorageSchemeCfgDefn_es.properties
new file mode 100644
index 0000000..547ddee
--- /dev/null
+++ b/opends/src/admin/messages/PasswordStorageSchemeCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Password Storage Scheme
+user-friendly-plural-name=Password Storage Schemes
+synopsis=Password Storage Schemes encode new passwords provided by users so that they are stored in an encoded manner. This makes it difficult or impossible for someone to determine the clear-text passwords from the encoded values.
+description=Password Storage Schemes also determine whether a clear-text password provided by a client matches the encoded value stored in the server.
+property.enabled.synopsis=Indicates whether the Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/PasswordStorageSchemeCfgDefn_fr.properties b/opends/src/admin/messages/PasswordStorageSchemeCfgDefn_fr.properties
new file mode 100644
index 0000000..547ddee
--- /dev/null
+++ b/opends/src/admin/messages/PasswordStorageSchemeCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Password Storage Scheme
+user-friendly-plural-name=Password Storage Schemes
+synopsis=Password Storage Schemes encode new passwords provided by users so that they are stored in an encoded manner. This makes it difficult or impossible for someone to determine the clear-text passwords from the encoded values.
+description=Password Storage Schemes also determine whether a clear-text password provided by a client matches the encoded value stored in the server.
+property.enabled.synopsis=Indicates whether the Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/PasswordStorageSchemeCfgDefn_ja.properties b/opends/src/admin/messages/PasswordStorageSchemeCfgDefn_ja.properties
new file mode 100644
index 0000000..547ddee
--- /dev/null
+++ b/opends/src/admin/messages/PasswordStorageSchemeCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Password Storage Scheme
+user-friendly-plural-name=Password Storage Schemes
+synopsis=Password Storage Schemes encode new passwords provided by users so that they are stored in an encoded manner. This makes it difficult or impossible for someone to determine the clear-text passwords from the encoded values.
+description=Password Storage Schemes also determine whether a clear-text password provided by a client matches the encoded value stored in the server.
+property.enabled.synopsis=Indicates whether the Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/PasswordStorageSchemeCfgDefn_ko.properties b/opends/src/admin/messages/PasswordStorageSchemeCfgDefn_ko.properties
new file mode 100644
index 0000000..547ddee
--- /dev/null
+++ b/opends/src/admin/messages/PasswordStorageSchemeCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Password Storage Scheme
+user-friendly-plural-name=Password Storage Schemes
+synopsis=Password Storage Schemes encode new passwords provided by users so that they are stored in an encoded manner. This makes it difficult or impossible for someone to determine the clear-text passwords from the encoded values.
+description=Password Storage Schemes also determine whether a clear-text password provided by a client matches the encoded value stored in the server.
+property.enabled.synopsis=Indicates whether the Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/PasswordStorageSchemeCfgDefn_zh_CN.properties b/opends/src/admin/messages/PasswordStorageSchemeCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..547ddee
--- /dev/null
+++ b/opends/src/admin/messages/PasswordStorageSchemeCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Password Storage Scheme
+user-friendly-plural-name=Password Storage Schemes
+synopsis=Password Storage Schemes encode new passwords provided by users so that they are stored in an encoded manner. This makes it difficult or impossible for someone to determine the clear-text passwords from the encoded values.
+description=Password Storage Schemes also determine whether a clear-text password provided by a client matches the encoded value stored in the server.
+property.enabled.synopsis=Indicates whether the Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/PasswordStorageSchemeCfgDefn_zh_TW.properties b/opends/src/admin/messages/PasswordStorageSchemeCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..547ddee
--- /dev/null
+++ b/opends/src/admin/messages/PasswordStorageSchemeCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Password Storage Scheme
+user-friendly-plural-name=Password Storage Schemes
+synopsis=Password Storage Schemes encode new passwords provided by users so that they are stored in an encoded manner. This makes it difficult or impossible for someone to determine the clear-text passwords from the encoded values.
+description=Password Storage Schemes also determine whether a clear-text password provided by a client matches the encoded value stored in the server.
+property.enabled.synopsis=Indicates whether the Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/PasswordValidatorCfgDefn.properties b/opends/src/admin/messages/PasswordValidatorCfgDefn.properties
new file mode 100644
index 0000000..c9c9254
--- /dev/null
+++ b/opends/src/admin/messages/PasswordValidatorCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Password Validator
+user-friendly-plural-name=Password Validators
+synopsis=Password Validators are responsible for determining whether a proposed password is acceptable for use and could include checks like ensuring it meets minimum length requirements, that it has an appropriate range of characters, or that it is not in the history.
+description=The password policy for a user specifies the set of password validators that should be used whenever that user provides a new password. In order to activate a password validator, the corresponding configuration entry must be enabled, and the DN of that entry should be included in the password-validator attribute of the password policy in which you want that validator active. All password validator configuration entries must contain the password-validator structural objectclass.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
diff --git a/opends/src/admin/messages/PasswordValidatorCfgDefn_de.properties b/opends/src/admin/messages/PasswordValidatorCfgDefn_de.properties
new file mode 100644
index 0000000..c9c9254
--- /dev/null
+++ b/opends/src/admin/messages/PasswordValidatorCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Password Validator
+user-friendly-plural-name=Password Validators
+synopsis=Password Validators are responsible for determining whether a proposed password is acceptable for use and could include checks like ensuring it meets minimum length requirements, that it has an appropriate range of characters, or that it is not in the history.
+description=The password policy for a user specifies the set of password validators that should be used whenever that user provides a new password. In order to activate a password validator, the corresponding configuration entry must be enabled, and the DN of that entry should be included in the password-validator attribute of the password policy in which you want that validator active. All password validator configuration entries must contain the password-validator structural objectclass.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
diff --git a/opends/src/admin/messages/PasswordValidatorCfgDefn_es.properties b/opends/src/admin/messages/PasswordValidatorCfgDefn_es.properties
new file mode 100644
index 0000000..c9c9254
--- /dev/null
+++ b/opends/src/admin/messages/PasswordValidatorCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Password Validator
+user-friendly-plural-name=Password Validators
+synopsis=Password Validators are responsible for determining whether a proposed password is acceptable for use and could include checks like ensuring it meets minimum length requirements, that it has an appropriate range of characters, or that it is not in the history.
+description=The password policy for a user specifies the set of password validators that should be used whenever that user provides a new password. In order to activate a password validator, the corresponding configuration entry must be enabled, and the DN of that entry should be included in the password-validator attribute of the password policy in which you want that validator active. All password validator configuration entries must contain the password-validator structural objectclass.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
diff --git a/opends/src/admin/messages/PasswordValidatorCfgDefn_fr.properties b/opends/src/admin/messages/PasswordValidatorCfgDefn_fr.properties
new file mode 100644
index 0000000..c9c9254
--- /dev/null
+++ b/opends/src/admin/messages/PasswordValidatorCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Password Validator
+user-friendly-plural-name=Password Validators
+synopsis=Password Validators are responsible for determining whether a proposed password is acceptable for use and could include checks like ensuring it meets minimum length requirements, that it has an appropriate range of characters, or that it is not in the history.
+description=The password policy for a user specifies the set of password validators that should be used whenever that user provides a new password. In order to activate a password validator, the corresponding configuration entry must be enabled, and the DN of that entry should be included in the password-validator attribute of the password policy in which you want that validator active. All password validator configuration entries must contain the password-validator structural objectclass.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
diff --git a/opends/src/admin/messages/PasswordValidatorCfgDefn_ja.properties b/opends/src/admin/messages/PasswordValidatorCfgDefn_ja.properties
new file mode 100644
index 0000000..c9c9254
--- /dev/null
+++ b/opends/src/admin/messages/PasswordValidatorCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Password Validator
+user-friendly-plural-name=Password Validators
+synopsis=Password Validators are responsible for determining whether a proposed password is acceptable for use and could include checks like ensuring it meets minimum length requirements, that it has an appropriate range of characters, or that it is not in the history.
+description=The password policy for a user specifies the set of password validators that should be used whenever that user provides a new password. In order to activate a password validator, the corresponding configuration entry must be enabled, and the DN of that entry should be included in the password-validator attribute of the password policy in which you want that validator active. All password validator configuration entries must contain the password-validator structural objectclass.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
diff --git a/opends/src/admin/messages/PasswordValidatorCfgDefn_ko.properties b/opends/src/admin/messages/PasswordValidatorCfgDefn_ko.properties
new file mode 100644
index 0000000..c9c9254
--- /dev/null
+++ b/opends/src/admin/messages/PasswordValidatorCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Password Validator
+user-friendly-plural-name=Password Validators
+synopsis=Password Validators are responsible for determining whether a proposed password is acceptable for use and could include checks like ensuring it meets minimum length requirements, that it has an appropriate range of characters, or that it is not in the history.
+description=The password policy for a user specifies the set of password validators that should be used whenever that user provides a new password. In order to activate a password validator, the corresponding configuration entry must be enabled, and the DN of that entry should be included in the password-validator attribute of the password policy in which you want that validator active. All password validator configuration entries must contain the password-validator structural objectclass.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
diff --git a/opends/src/admin/messages/PasswordValidatorCfgDefn_zh_CN.properties b/opends/src/admin/messages/PasswordValidatorCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..c9c9254
--- /dev/null
+++ b/opends/src/admin/messages/PasswordValidatorCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Password Validator
+user-friendly-plural-name=Password Validators
+synopsis=Password Validators are responsible for determining whether a proposed password is acceptable for use and could include checks like ensuring it meets minimum length requirements, that it has an appropriate range of characters, or that it is not in the history.
+description=The password policy for a user specifies the set of password validators that should be used whenever that user provides a new password. In order to activate a password validator, the corresponding configuration entry must be enabled, and the DN of that entry should be included in the password-validator attribute of the password policy in which you want that validator active. All password validator configuration entries must contain the password-validator structural objectclass.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
diff --git a/opends/src/admin/messages/PasswordValidatorCfgDefn_zh_TW.properties b/opends/src/admin/messages/PasswordValidatorCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..c9c9254
--- /dev/null
+++ b/opends/src/admin/messages/PasswordValidatorCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Password Validator
+user-friendly-plural-name=Password Validators
+synopsis=Password Validators are responsible for determining whether a proposed password is acceptable for use and could include checks like ensuring it meets minimum length requirements, that it has an appropriate range of characters, or that it is not in the history.
+description=The password policy for a user specifies the set of password validators that should be used whenever that user provides a new password. In order to activate a password validator, the corresponding configuration entry must be enabled, and the DN of that entry should be included in the password-validator attribute of the password policy in which you want that validator active. All password validator configuration entries must contain the password-validator structural objectclass.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
diff --git a/opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn.properties b/opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn.properties
new file mode 100644
index 0000000..21a961e
--- /dev/null
+++ b/opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Plain SASL Mechanism Handler
+user-friendly-plural-name=Plain SASL Mechanism Handlers
+synopsis=The Plain SASL Mechanism Handler performs all processing related to SASL PLAIN authentication.
+description=The PLAIN SASL mechanism provides the ability for clients to authenticate using a username and password. This authentication is very similar to standard LDAP simple authentication, with the exception that it can authenticate based on an authentication ID (for example, a username) rather than requiring a full DN, and it can also include an authorization ID in addition to the authentication ID. Note that the SASL PLAIN mechanism does not make any attempt to protect the password.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that is to be used with this SASL mechanism handler to match the authentication or authorization ID included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Plain SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_de.properties b/opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..21a961e
--- /dev/null
+++ b/opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_de.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Plain SASL Mechanism Handler
+user-friendly-plural-name=Plain SASL Mechanism Handlers
+synopsis=The Plain SASL Mechanism Handler performs all processing related to SASL PLAIN authentication.
+description=The PLAIN SASL mechanism provides the ability for clients to authenticate using a username and password. This authentication is very similar to standard LDAP simple authentication, with the exception that it can authenticate based on an authentication ID (for example, a username) rather than requiring a full DN, and it can also include an authorization ID in addition to the authentication ID. Note that the SASL PLAIN mechanism does not make any attempt to protect the password.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that is to be used with this SASL mechanism handler to match the authentication or authorization ID included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Plain SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_es.properties b/opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..21a961e
--- /dev/null
+++ b/opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_es.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Plain SASL Mechanism Handler
+user-friendly-plural-name=Plain SASL Mechanism Handlers
+synopsis=The Plain SASL Mechanism Handler performs all processing related to SASL PLAIN authentication.
+description=The PLAIN SASL mechanism provides the ability for clients to authenticate using a username and password. This authentication is very similar to standard LDAP simple authentication, with the exception that it can authenticate based on an authentication ID (for example, a username) rather than requiring a full DN, and it can also include an authorization ID in addition to the authentication ID. Note that the SASL PLAIN mechanism does not make any attempt to protect the password.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that is to be used with this SASL mechanism handler to match the authentication or authorization ID included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Plain SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_fr.properties b/opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..21a961e
--- /dev/null
+++ b/opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_fr.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Plain SASL Mechanism Handler
+user-friendly-plural-name=Plain SASL Mechanism Handlers
+synopsis=The Plain SASL Mechanism Handler performs all processing related to SASL PLAIN authentication.
+description=The PLAIN SASL mechanism provides the ability for clients to authenticate using a username and password. This authentication is very similar to standard LDAP simple authentication, with the exception that it can authenticate based on an authentication ID (for example, a username) rather than requiring a full DN, and it can also include an authorization ID in addition to the authentication ID. Note that the SASL PLAIN mechanism does not make any attempt to protect the password.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that is to be used with this SASL mechanism handler to match the authentication or authorization ID included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Plain SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_ja.properties b/opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..21a961e
--- /dev/null
+++ b/opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_ja.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Plain SASL Mechanism Handler
+user-friendly-plural-name=Plain SASL Mechanism Handlers
+synopsis=The Plain SASL Mechanism Handler performs all processing related to SASL PLAIN authentication.
+description=The PLAIN SASL mechanism provides the ability for clients to authenticate using a username and password. This authentication is very similar to standard LDAP simple authentication, with the exception that it can authenticate based on an authentication ID (for example, a username) rather than requiring a full DN, and it can also include an authorization ID in addition to the authentication ID. Note that the SASL PLAIN mechanism does not make any attempt to protect the password.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that is to be used with this SASL mechanism handler to match the authentication or authorization ID included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Plain SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_ko.properties b/opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..21a961e
--- /dev/null
+++ b/opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_ko.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Plain SASL Mechanism Handler
+user-friendly-plural-name=Plain SASL Mechanism Handlers
+synopsis=The Plain SASL Mechanism Handler performs all processing related to SASL PLAIN authentication.
+description=The PLAIN SASL mechanism provides the ability for clients to authenticate using a username and password. This authentication is very similar to standard LDAP simple authentication, with the exception that it can authenticate based on an authentication ID (for example, a username) rather than requiring a full DN, and it can also include an authorization ID in addition to the authentication ID. Note that the SASL PLAIN mechanism does not make any attempt to protect the password.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that is to be used with this SASL mechanism handler to match the authentication or authorization ID included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Plain SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..21a961e
--- /dev/null
+++ b/opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Plain SASL Mechanism Handler
+user-friendly-plural-name=Plain SASL Mechanism Handlers
+synopsis=The Plain SASL Mechanism Handler performs all processing related to SASL PLAIN authentication.
+description=The PLAIN SASL mechanism provides the ability for clients to authenticate using a username and password. This authentication is very similar to standard LDAP simple authentication, with the exception that it can authenticate based on an authentication ID (for example, a username) rather than requiring a full DN, and it can also include an authorization ID in addition to the authentication ID. Note that the SASL PLAIN mechanism does not make any attempt to protect the password.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that is to be used with this SASL mechanism handler to match the authentication or authorization ID included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Plain SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..21a961e
--- /dev/null
+++ b/opends/src/admin/messages/PlainSASLMechanismHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Plain SASL Mechanism Handler
+user-friendly-plural-name=Plain SASL Mechanism Handlers
+synopsis=The Plain SASL Mechanism Handler performs all processing related to SASL PLAIN authentication.
+description=The PLAIN SASL mechanism provides the ability for clients to authenticate using a username and password. This authentication is very similar to standard LDAP simple authentication, with the exception that it can authenticate based on an authentication ID (for example, a username) rather than requiring a full DN, and it can also include an authorization ID in addition to the authentication ID. Note that the SASL PLAIN mechanism does not make any attempt to protect the password.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.identity-mapper.synopsis=Specifies the name of the identity mapper that is to be used with this SASL mechanism handler to match the authentication or authorization ID included in the SASL bind request to the corresponding user in the directory.
+property.identity-mapper.syntax.aggregation.constraint-synopsis=The referenced identity mapper must be enabled when the Plain SASL Mechanism Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/PluginCfgDefn.properties b/opends/src/admin/messages/PluginCfgDefn.properties
new file mode 100644
index 0000000..f69ef4c
--- /dev/null
+++ b/opends/src/admin/messages/PluginCfgDefn.properties
@@ -0,0 +1,58 @@
+user-friendly-name=Plugin
+user-friendly-plural-name=Plugins
+synopsis=Plugins provide a mechanism for executing custom code at specified points in operation processing and in the course of other events like connection establishment and termination, server startup and shutdown, and LDIF import and export.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/PluginCfgDefn_de.properties b/opends/src/admin/messages/PluginCfgDefn_de.properties
new file mode 100644
index 0000000..f69ef4c
--- /dev/null
+++ b/opends/src/admin/messages/PluginCfgDefn_de.properties
@@ -0,0 +1,58 @@
+user-friendly-name=Plugin
+user-friendly-plural-name=Plugins
+synopsis=Plugins provide a mechanism for executing custom code at specified points in operation processing and in the course of other events like connection establishment and termination, server startup and shutdown, and LDIF import and export.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/PluginCfgDefn_es.properties b/opends/src/admin/messages/PluginCfgDefn_es.properties
new file mode 100644
index 0000000..f69ef4c
--- /dev/null
+++ b/opends/src/admin/messages/PluginCfgDefn_es.properties
@@ -0,0 +1,58 @@
+user-friendly-name=Plugin
+user-friendly-plural-name=Plugins
+synopsis=Plugins provide a mechanism for executing custom code at specified points in operation processing and in the course of other events like connection establishment and termination, server startup and shutdown, and LDIF import and export.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/PluginCfgDefn_fr.properties b/opends/src/admin/messages/PluginCfgDefn_fr.properties
new file mode 100644
index 0000000..f69ef4c
--- /dev/null
+++ b/opends/src/admin/messages/PluginCfgDefn_fr.properties
@@ -0,0 +1,58 @@
+user-friendly-name=Plugin
+user-friendly-plural-name=Plugins
+synopsis=Plugins provide a mechanism for executing custom code at specified points in operation processing and in the course of other events like connection establishment and termination, server startup and shutdown, and LDIF import and export.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/PluginCfgDefn_ja.properties b/opends/src/admin/messages/PluginCfgDefn_ja.properties
new file mode 100644
index 0000000..f69ef4c
--- /dev/null
+++ b/opends/src/admin/messages/PluginCfgDefn_ja.properties
@@ -0,0 +1,58 @@
+user-friendly-name=Plugin
+user-friendly-plural-name=Plugins
+synopsis=Plugins provide a mechanism for executing custom code at specified points in operation processing and in the course of other events like connection establishment and termination, server startup and shutdown, and LDIF import and export.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/PluginCfgDefn_ko.properties b/opends/src/admin/messages/PluginCfgDefn_ko.properties
new file mode 100644
index 0000000..f69ef4c
--- /dev/null
+++ b/opends/src/admin/messages/PluginCfgDefn_ko.properties
@@ -0,0 +1,58 @@
+user-friendly-name=Plugin
+user-friendly-plural-name=Plugins
+synopsis=Plugins provide a mechanism for executing custom code at specified points in operation processing and in the course of other events like connection establishment and termination, server startup and shutdown, and LDIF import and export.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/PluginCfgDefn_zh_CN.properties b/opends/src/admin/messages/PluginCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..f69ef4c
--- /dev/null
+++ b/opends/src/admin/messages/PluginCfgDefn_zh_CN.properties
@@ -0,0 +1,58 @@
+user-friendly-name=Plugin
+user-friendly-plural-name=Plugins
+synopsis=Plugins provide a mechanism for executing custom code at specified points in operation processing and in the course of other events like connection establishment and termination, server startup and shutdown, and LDIF import and export.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/PluginCfgDefn_zh_TW.properties b/opends/src/admin/messages/PluginCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..f69ef4c
--- /dev/null
+++ b/opends/src/admin/messages/PluginCfgDefn_zh_TW.properties
@@ -0,0 +1,58 @@
+user-friendly-name=Plugin
+user-friendly-plural-name=Plugins
+synopsis=Plugins provide a mechanism for executing custom code at specified points in operation processing and in the course of other events like connection establishment and termination, server startup and shutdown, and LDIF import and export.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/PluginRootCfgDefn.properties b/opends/src/admin/messages/PluginRootCfgDefn.properties
new file mode 100644
index 0000000..d15ac52
--- /dev/null
+++ b/opends/src/admin/messages/PluginRootCfgDefn.properties
@@ -0,0 +1,157 @@
+user-friendly-name=Plugin Root
+user-friendly-plural-name=Plugin Roots
+synopsis=The Plugin Root defines the parent entry for all plug-ins defined in the server.
+description=It can also include configuration attributes that define the order in which those plug-ins are to be loaded and invoked.
+property.plugin-order-intermediate-response.synopsis=Specifies the order in which intermediate response plug-ins are to be loaded and invoked.
+property.plugin-order-intermediate-response.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-intermediate-response.default-behavior.alias.synopsis=The order in which intermediate response plug-ins are loaded and invoked is undefined.
+property.plugin-order-ldif-export.synopsis=Specifies the order in which LDIF export plug-ins are to be loaded and invoked.
+property.plugin-order-ldif-export.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-ldif-export.default-behavior.alias.synopsis=The order in which LDIF export plug-ins are loaded and invoked is undefined.
+property.plugin-order-ldif-import.synopsis=Specifies the order in which LDIF import plug-ins are to be loaded and invoked.
+property.plugin-order-ldif-import.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-ldif-import.default-behavior.alias.synopsis=The order in which LDIF import plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-connect.synopsis=Specifies the order in which post-connect plug-ins are to be loaded and invoked.
+property.plugin-order-post-connect.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-connect.default-behavior.alias.synopsis=The order in which post-connect plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-disconnect.synopsis=Specifies the order in which post-disconnect plug-ins are to be loaded and invoked.
+property.plugin-order-post-disconnect.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-disconnect.default-behavior.alias.synopsis=The order in which post-disconnect plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-abandon.synopsis=Specifies the order in which post-operation abandon plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-abandon.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-abandon.default-behavior.alias.synopsis=The order in which post-operation abandon plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-add.synopsis=Specifies the order in which post-operation add plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-add.default-behavior.alias.synopsis=The order in which post-operation add plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-bind.synopsis=Specifies the order in which post-operation bind plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-bind.default-behavior.alias.synopsis=The order in which post-operation bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-compare.synopsis=Specifies the order in which post-operation compare plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-compare.default-behavior.alias.synopsis=The order in which post-operation compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-delete.synopsis=Specifies the order in which post-operation delete plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-delete.default-behavior.alias.synopsis=The order in which post-operation delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-extended.synopsis=Specifies the order in which post-operation extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-extended.default-behavior.alias.synopsis=The order in which post-operation extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-modify.synopsis=Specifies the order in which post-operation modify plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-modify.default-behavior.alias.synopsis=The order in which post-operation modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-modify-dn.synopsis=Specifies the order in which post-operation modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-modify-dn.default-behavior.alias.synopsis=The order in which post-operation modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-search.synopsis=Specifies the order in which post-operation search plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-search.default-behavior.alias.synopsis=The order in which post-operation search plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-unbind.synopsis=Specifies the order in which post-operation unbind plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-unbind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-unbind.default-behavior.alias.synopsis=The order in which post-operation unbind plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-add.synopsis=Specifies the order in which post-response add plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-add.default-behavior.alias.synopsis=The order in which post-response add plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-bind.synopsis=Specifies the order in which post-response bind plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-bind.default-behavior.alias.synopsis=The order in which post-response bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-compare.synopsis=Specifies the order in which post-response compare plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-compare.default-behavior.alias.synopsis=The order in which post-response compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-delete.synopsis=Specifies the order in which post-response delete plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-delete.default-behavior.alias.synopsis=The order in which post-response delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-extended.synopsis=Specifies the order in which post-response extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-extended.default-behavior.alias.synopsis=The order in which post-response extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-modify.synopsis=Specifies the order in which post-response modify plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-modify.default-behavior.alias.synopsis=The order in which post-response modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-modify-dn.synopsis=Specifies the order in which post-response modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-modify-dn.default-behavior.alias.synopsis=The order in which post-response modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-search.synopsis=Specifies the order in which post-response search plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-search.default-behavior.alias.synopsis=The order in which post-response search plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-add.synopsis=Specifies the order in which post-synchronization add plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-add.default-behavior.alias.synopsis=The order in which post-synchronization add plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-delete.synopsis=Specifies the order in which post-synchronization delete plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-delete.default-behavior.alias.synopsis=The order in which post-synchronization delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-modify.synopsis=Specifies the order in which post-synchronization modify plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-modify.default-behavior.alias.synopsis=The order in which post-synchronization modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-modify-dn.synopsis=Specifies the order in which post-synchronization modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-modify-dn.default-behavior.alias.synopsis=The order in which post-synchronization modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-add.synopsis=Specifies the order in which pre-operation add plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-add.default-behavior.alias.synopsis=The order in which pre-operation add plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-bind.synopsis=Specifies the order in which pre-operation bind plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-bind.default-behavior.alias.synopsis=The order in which pre-operation bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-compare.synopsis=Specifies the order in which pre-operation compare plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-compare.default-behavior.alias.synopsis=The order in which pre-operation compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-delete.synopsis=Specifies the order in which pre-operation delete plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-delete.default-behavior.alias.synopsis=The order in which pre-operation delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-extended.synopsis=Specifies the order in which pre-operation extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-extended.default-behavior.alias.synopsis=The order in which pre-operation extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-modify.synopsis=Specifies the order in which pre-operation modify plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-modify.default-behavior.alias.synopsis=The order in which pre-operation modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-modify-dn.synopsis=Specifies the order in which pre-operation modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-modify-dn.default-behavior.alias.synopsis=The order in which pre-operation modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-search.synopsis=Specifies the order in which pre-operation search plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-search.default-behavior.alias.synopsis=The order in which pre-operation searc plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-abandon.synopsis=Specifies the order in which pre-parse abandon plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-abandon.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-abandon.default-behavior.alias.synopsis=The order in which pre-parse abandon plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-add.synopsis=Specifies the order in which pre-parse add plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-add.default-behavior.alias.synopsis=The order in which pre-parse add plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-bind.synopsis=Specifies the order in which pre-parse bind plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-bind.default-behavior.alias.synopsis=The order in which pre-parse bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-compare.synopsis=Specifies the order in which pre-parse compare plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-compare.default-behavior.alias.synopsis=The order in which pre-parse compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-delete.synopsis=Specifies the order in which pre-parse delete plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-delete.default-behavior.alias.synopsis=The order in which pre-parse delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-extended.synopsis=Specifies the order in which pre-parse extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-extended.default-behavior.alias.synopsis=The order in which pre-parse extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-modify.synopsis=Specifies the order in which pre-parse modify plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-modify.default-behavior.alias.synopsis=The order in which pre-parse modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-modify-dn.synopsis=Specifies the order in which pre-parse modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-modify-dn.default-behavior.alias.synopsis=The order in which pre-parse modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-search.synopsis=Specifies the order in which pre-parse search plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-search.default-behavior.alias.synopsis=The order in which pre-parse search plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-unbind.synopsis=Specifies the order in which pre-parse unbind plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-unbind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-unbind.default-behavior.alias.synopsis=The order in which pre-parse unbind plug-ins are loaded and invoked is undefined.
+property.plugin-order-search-result-entry.synopsis=Specifies the order in which search result entry plug-ins are to be loaded and invoked.
+property.plugin-order-search-result-entry.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-search-result-entry.default-behavior.alias.synopsis=The order in which search result entry plug-ins are loaded and invoked is undefined.
+property.plugin-order-search-result-reference.synopsis=Specifies the order in which search result reference plug-ins are to be loaded and invoked.
+property.plugin-order-search-result-reference.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-search-result-reference.default-behavior.alias.synopsis=The order in which search result reference plug-ins are loaded and invoked is undefined.
+property.plugin-order-shutdown.synopsis=Specifies the order in which shutdown plug-ins are to be loaded and invoked.
+property.plugin-order-shutdown.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-shutdown.default-behavior.alias.synopsis=The order in which shutdown plug-ins are loaded and invoked is undefined.
+property.plugin-order-startup.synopsis=Specifies the order in which startup plug-ins are to be loaded and invoked.
+property.plugin-order-startup.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-startup.default-behavior.alias.synopsis=The order in which startup plug-ins are loaded and invoked is undefined.
+property.plugin-order-subordinate-modify-dn.synopsis=Specifies the order in which subordinate modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-subordinate-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-subordinate-modify-dn.default-behavior.alias.synopsis=The order in which subordinate modify DN plug-ins are loaded and invoked is undefined.
+relation.plugin.user-friendly-name=Plugin
+relation.plugin.user-friendly-plural-name=Plugins
+relation.plugin.synopsis=Plugins provide a mechanism for executing custom code at specified points in operation processing and in the course of other events like connection establishment and termination, server startup and shutdown, and LDIF import and export.
diff --git a/opends/src/admin/messages/PluginRootCfgDefn_de.properties b/opends/src/admin/messages/PluginRootCfgDefn_de.properties
new file mode 100644
index 0000000..d15ac52
--- /dev/null
+++ b/opends/src/admin/messages/PluginRootCfgDefn_de.properties
@@ -0,0 +1,157 @@
+user-friendly-name=Plugin Root
+user-friendly-plural-name=Plugin Roots
+synopsis=The Plugin Root defines the parent entry for all plug-ins defined in the server.
+description=It can also include configuration attributes that define the order in which those plug-ins are to be loaded and invoked.
+property.plugin-order-intermediate-response.synopsis=Specifies the order in which intermediate response plug-ins are to be loaded and invoked.
+property.plugin-order-intermediate-response.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-intermediate-response.default-behavior.alias.synopsis=The order in which intermediate response plug-ins are loaded and invoked is undefined.
+property.plugin-order-ldif-export.synopsis=Specifies the order in which LDIF export plug-ins are to be loaded and invoked.
+property.plugin-order-ldif-export.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-ldif-export.default-behavior.alias.synopsis=The order in which LDIF export plug-ins are loaded and invoked is undefined.
+property.plugin-order-ldif-import.synopsis=Specifies the order in which LDIF import plug-ins are to be loaded and invoked.
+property.plugin-order-ldif-import.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-ldif-import.default-behavior.alias.synopsis=The order in which LDIF import plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-connect.synopsis=Specifies the order in which post-connect plug-ins are to be loaded and invoked.
+property.plugin-order-post-connect.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-connect.default-behavior.alias.synopsis=The order in which post-connect plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-disconnect.synopsis=Specifies the order in which post-disconnect plug-ins are to be loaded and invoked.
+property.plugin-order-post-disconnect.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-disconnect.default-behavior.alias.synopsis=The order in which post-disconnect plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-abandon.synopsis=Specifies the order in which post-operation abandon plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-abandon.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-abandon.default-behavior.alias.synopsis=The order in which post-operation abandon plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-add.synopsis=Specifies the order in which post-operation add plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-add.default-behavior.alias.synopsis=The order in which post-operation add plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-bind.synopsis=Specifies the order in which post-operation bind plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-bind.default-behavior.alias.synopsis=The order in which post-operation bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-compare.synopsis=Specifies the order in which post-operation compare plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-compare.default-behavior.alias.synopsis=The order in which post-operation compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-delete.synopsis=Specifies the order in which post-operation delete plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-delete.default-behavior.alias.synopsis=The order in which post-operation delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-extended.synopsis=Specifies the order in which post-operation extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-extended.default-behavior.alias.synopsis=The order in which post-operation extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-modify.synopsis=Specifies the order in which post-operation modify plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-modify.default-behavior.alias.synopsis=The order in which post-operation modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-modify-dn.synopsis=Specifies the order in which post-operation modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-modify-dn.default-behavior.alias.synopsis=The order in which post-operation modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-search.synopsis=Specifies the order in which post-operation search plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-search.default-behavior.alias.synopsis=The order in which post-operation search plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-unbind.synopsis=Specifies the order in which post-operation unbind plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-unbind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-unbind.default-behavior.alias.synopsis=The order in which post-operation unbind plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-add.synopsis=Specifies the order in which post-response add plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-add.default-behavior.alias.synopsis=The order in which post-response add plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-bind.synopsis=Specifies the order in which post-response bind plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-bind.default-behavior.alias.synopsis=The order in which post-response bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-compare.synopsis=Specifies the order in which post-response compare plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-compare.default-behavior.alias.synopsis=The order in which post-response compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-delete.synopsis=Specifies the order in which post-response delete plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-delete.default-behavior.alias.synopsis=The order in which post-response delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-extended.synopsis=Specifies the order in which post-response extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-extended.default-behavior.alias.synopsis=The order in which post-response extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-modify.synopsis=Specifies the order in which post-response modify plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-modify.default-behavior.alias.synopsis=The order in which post-response modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-modify-dn.synopsis=Specifies the order in which post-response modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-modify-dn.default-behavior.alias.synopsis=The order in which post-response modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-search.synopsis=Specifies the order in which post-response search plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-search.default-behavior.alias.synopsis=The order in which post-response search plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-add.synopsis=Specifies the order in which post-synchronization add plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-add.default-behavior.alias.synopsis=The order in which post-synchronization add plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-delete.synopsis=Specifies the order in which post-synchronization delete plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-delete.default-behavior.alias.synopsis=The order in which post-synchronization delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-modify.synopsis=Specifies the order in which post-synchronization modify plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-modify.default-behavior.alias.synopsis=The order in which post-synchronization modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-modify-dn.synopsis=Specifies the order in which post-synchronization modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-modify-dn.default-behavior.alias.synopsis=The order in which post-synchronization modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-add.synopsis=Specifies the order in which pre-operation add plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-add.default-behavior.alias.synopsis=The order in which pre-operation add plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-bind.synopsis=Specifies the order in which pre-operation bind plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-bind.default-behavior.alias.synopsis=The order in which pre-operation bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-compare.synopsis=Specifies the order in which pre-operation compare plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-compare.default-behavior.alias.synopsis=The order in which pre-operation compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-delete.synopsis=Specifies the order in which pre-operation delete plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-delete.default-behavior.alias.synopsis=The order in which pre-operation delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-extended.synopsis=Specifies the order in which pre-operation extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-extended.default-behavior.alias.synopsis=The order in which pre-operation extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-modify.synopsis=Specifies the order in which pre-operation modify plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-modify.default-behavior.alias.synopsis=The order in which pre-operation modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-modify-dn.synopsis=Specifies the order in which pre-operation modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-modify-dn.default-behavior.alias.synopsis=The order in which pre-operation modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-search.synopsis=Specifies the order in which pre-operation search plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-search.default-behavior.alias.synopsis=The order in which pre-operation searc plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-abandon.synopsis=Specifies the order in which pre-parse abandon plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-abandon.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-abandon.default-behavior.alias.synopsis=The order in which pre-parse abandon plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-add.synopsis=Specifies the order in which pre-parse add plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-add.default-behavior.alias.synopsis=The order in which pre-parse add plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-bind.synopsis=Specifies the order in which pre-parse bind plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-bind.default-behavior.alias.synopsis=The order in which pre-parse bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-compare.synopsis=Specifies the order in which pre-parse compare plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-compare.default-behavior.alias.synopsis=The order in which pre-parse compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-delete.synopsis=Specifies the order in which pre-parse delete plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-delete.default-behavior.alias.synopsis=The order in which pre-parse delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-extended.synopsis=Specifies the order in which pre-parse extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-extended.default-behavior.alias.synopsis=The order in which pre-parse extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-modify.synopsis=Specifies the order in which pre-parse modify plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-modify.default-behavior.alias.synopsis=The order in which pre-parse modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-modify-dn.synopsis=Specifies the order in which pre-parse modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-modify-dn.default-behavior.alias.synopsis=The order in which pre-parse modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-search.synopsis=Specifies the order in which pre-parse search plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-search.default-behavior.alias.synopsis=The order in which pre-parse search plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-unbind.synopsis=Specifies the order in which pre-parse unbind plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-unbind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-unbind.default-behavior.alias.synopsis=The order in which pre-parse unbind plug-ins are loaded and invoked is undefined.
+property.plugin-order-search-result-entry.synopsis=Specifies the order in which search result entry plug-ins are to be loaded and invoked.
+property.plugin-order-search-result-entry.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-search-result-entry.default-behavior.alias.synopsis=The order in which search result entry plug-ins are loaded and invoked is undefined.
+property.plugin-order-search-result-reference.synopsis=Specifies the order in which search result reference plug-ins are to be loaded and invoked.
+property.plugin-order-search-result-reference.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-search-result-reference.default-behavior.alias.synopsis=The order in which search result reference plug-ins are loaded and invoked is undefined.
+property.plugin-order-shutdown.synopsis=Specifies the order in which shutdown plug-ins are to be loaded and invoked.
+property.plugin-order-shutdown.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-shutdown.default-behavior.alias.synopsis=The order in which shutdown plug-ins are loaded and invoked is undefined.
+property.plugin-order-startup.synopsis=Specifies the order in which startup plug-ins are to be loaded and invoked.
+property.plugin-order-startup.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-startup.default-behavior.alias.synopsis=The order in which startup plug-ins are loaded and invoked is undefined.
+property.plugin-order-subordinate-modify-dn.synopsis=Specifies the order in which subordinate modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-subordinate-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-subordinate-modify-dn.default-behavior.alias.synopsis=The order in which subordinate modify DN plug-ins are loaded and invoked is undefined.
+relation.plugin.user-friendly-name=Plugin
+relation.plugin.user-friendly-plural-name=Plugins
+relation.plugin.synopsis=Plugins provide a mechanism for executing custom code at specified points in operation processing and in the course of other events like connection establishment and termination, server startup and shutdown, and LDIF import and export.
diff --git a/opends/src/admin/messages/PluginRootCfgDefn_es.properties b/opends/src/admin/messages/PluginRootCfgDefn_es.properties
new file mode 100644
index 0000000..d15ac52
--- /dev/null
+++ b/opends/src/admin/messages/PluginRootCfgDefn_es.properties
@@ -0,0 +1,157 @@
+user-friendly-name=Plugin Root
+user-friendly-plural-name=Plugin Roots
+synopsis=The Plugin Root defines the parent entry for all plug-ins defined in the server.
+description=It can also include configuration attributes that define the order in which those plug-ins are to be loaded and invoked.
+property.plugin-order-intermediate-response.synopsis=Specifies the order in which intermediate response plug-ins are to be loaded and invoked.
+property.plugin-order-intermediate-response.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-intermediate-response.default-behavior.alias.synopsis=The order in which intermediate response plug-ins are loaded and invoked is undefined.
+property.plugin-order-ldif-export.synopsis=Specifies the order in which LDIF export plug-ins are to be loaded and invoked.
+property.plugin-order-ldif-export.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-ldif-export.default-behavior.alias.synopsis=The order in which LDIF export plug-ins are loaded and invoked is undefined.
+property.plugin-order-ldif-import.synopsis=Specifies the order in which LDIF import plug-ins are to be loaded and invoked.
+property.plugin-order-ldif-import.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-ldif-import.default-behavior.alias.synopsis=The order in which LDIF import plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-connect.synopsis=Specifies the order in which post-connect plug-ins are to be loaded and invoked.
+property.plugin-order-post-connect.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-connect.default-behavior.alias.synopsis=The order in which post-connect plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-disconnect.synopsis=Specifies the order in which post-disconnect plug-ins are to be loaded and invoked.
+property.plugin-order-post-disconnect.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-disconnect.default-behavior.alias.synopsis=The order in which post-disconnect plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-abandon.synopsis=Specifies the order in which post-operation abandon plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-abandon.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-abandon.default-behavior.alias.synopsis=The order in which post-operation abandon plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-add.synopsis=Specifies the order in which post-operation add plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-add.default-behavior.alias.synopsis=The order in which post-operation add plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-bind.synopsis=Specifies the order in which post-operation bind plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-bind.default-behavior.alias.synopsis=The order in which post-operation bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-compare.synopsis=Specifies the order in which post-operation compare plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-compare.default-behavior.alias.synopsis=The order in which post-operation compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-delete.synopsis=Specifies the order in which post-operation delete plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-delete.default-behavior.alias.synopsis=The order in which post-operation delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-extended.synopsis=Specifies the order in which post-operation extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-extended.default-behavior.alias.synopsis=The order in which post-operation extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-modify.synopsis=Specifies the order in which post-operation modify plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-modify.default-behavior.alias.synopsis=The order in which post-operation modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-modify-dn.synopsis=Specifies the order in which post-operation modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-modify-dn.default-behavior.alias.synopsis=The order in which post-operation modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-search.synopsis=Specifies the order in which post-operation search plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-search.default-behavior.alias.synopsis=The order in which post-operation search plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-unbind.synopsis=Specifies the order in which post-operation unbind plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-unbind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-unbind.default-behavior.alias.synopsis=The order in which post-operation unbind plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-add.synopsis=Specifies the order in which post-response add plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-add.default-behavior.alias.synopsis=The order in which post-response add plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-bind.synopsis=Specifies the order in which post-response bind plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-bind.default-behavior.alias.synopsis=The order in which post-response bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-compare.synopsis=Specifies the order in which post-response compare plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-compare.default-behavior.alias.synopsis=The order in which post-response compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-delete.synopsis=Specifies the order in which post-response delete plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-delete.default-behavior.alias.synopsis=The order in which post-response delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-extended.synopsis=Specifies the order in which post-response extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-extended.default-behavior.alias.synopsis=The order in which post-response extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-modify.synopsis=Specifies the order in which post-response modify plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-modify.default-behavior.alias.synopsis=The order in which post-response modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-modify-dn.synopsis=Specifies the order in which post-response modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-modify-dn.default-behavior.alias.synopsis=The order in which post-response modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-search.synopsis=Specifies the order in which post-response search plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-search.default-behavior.alias.synopsis=The order in which post-response search plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-add.synopsis=Specifies the order in which post-synchronization add plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-add.default-behavior.alias.synopsis=The order in which post-synchronization add plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-delete.synopsis=Specifies the order in which post-synchronization delete plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-delete.default-behavior.alias.synopsis=The order in which post-synchronization delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-modify.synopsis=Specifies the order in which post-synchronization modify plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-modify.default-behavior.alias.synopsis=The order in which post-synchronization modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-modify-dn.synopsis=Specifies the order in which post-synchronization modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-modify-dn.default-behavior.alias.synopsis=The order in which post-synchronization modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-add.synopsis=Specifies the order in which pre-operation add plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-add.default-behavior.alias.synopsis=The order in which pre-operation add plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-bind.synopsis=Specifies the order in which pre-operation bind plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-bind.default-behavior.alias.synopsis=The order in which pre-operation bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-compare.synopsis=Specifies the order in which pre-operation compare plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-compare.default-behavior.alias.synopsis=The order in which pre-operation compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-delete.synopsis=Specifies the order in which pre-operation delete plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-delete.default-behavior.alias.synopsis=The order in which pre-operation delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-extended.synopsis=Specifies the order in which pre-operation extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-extended.default-behavior.alias.synopsis=The order in which pre-operation extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-modify.synopsis=Specifies the order in which pre-operation modify plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-modify.default-behavior.alias.synopsis=The order in which pre-operation modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-modify-dn.synopsis=Specifies the order in which pre-operation modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-modify-dn.default-behavior.alias.synopsis=The order in which pre-operation modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-search.synopsis=Specifies the order in which pre-operation search plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-search.default-behavior.alias.synopsis=The order in which pre-operation searc plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-abandon.synopsis=Specifies the order in which pre-parse abandon plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-abandon.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-abandon.default-behavior.alias.synopsis=The order in which pre-parse abandon plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-add.synopsis=Specifies the order in which pre-parse add plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-add.default-behavior.alias.synopsis=The order in which pre-parse add plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-bind.synopsis=Specifies the order in which pre-parse bind plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-bind.default-behavior.alias.synopsis=The order in which pre-parse bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-compare.synopsis=Specifies the order in which pre-parse compare plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-compare.default-behavior.alias.synopsis=The order in which pre-parse compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-delete.synopsis=Specifies the order in which pre-parse delete plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-delete.default-behavior.alias.synopsis=The order in which pre-parse delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-extended.synopsis=Specifies the order in which pre-parse extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-extended.default-behavior.alias.synopsis=The order in which pre-parse extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-modify.synopsis=Specifies the order in which pre-parse modify plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-modify.default-behavior.alias.synopsis=The order in which pre-parse modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-modify-dn.synopsis=Specifies the order in which pre-parse modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-modify-dn.default-behavior.alias.synopsis=The order in which pre-parse modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-search.synopsis=Specifies the order in which pre-parse search plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-search.default-behavior.alias.synopsis=The order in which pre-parse search plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-unbind.synopsis=Specifies the order in which pre-parse unbind plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-unbind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-unbind.default-behavior.alias.synopsis=The order in which pre-parse unbind plug-ins are loaded and invoked is undefined.
+property.plugin-order-search-result-entry.synopsis=Specifies the order in which search result entry plug-ins are to be loaded and invoked.
+property.plugin-order-search-result-entry.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-search-result-entry.default-behavior.alias.synopsis=The order in which search result entry plug-ins are loaded and invoked is undefined.
+property.plugin-order-search-result-reference.synopsis=Specifies the order in which search result reference plug-ins are to be loaded and invoked.
+property.plugin-order-search-result-reference.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-search-result-reference.default-behavior.alias.synopsis=The order in which search result reference plug-ins are loaded and invoked is undefined.
+property.plugin-order-shutdown.synopsis=Specifies the order in which shutdown plug-ins are to be loaded and invoked.
+property.plugin-order-shutdown.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-shutdown.default-behavior.alias.synopsis=The order in which shutdown plug-ins are loaded and invoked is undefined.
+property.plugin-order-startup.synopsis=Specifies the order in which startup plug-ins are to be loaded and invoked.
+property.plugin-order-startup.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-startup.default-behavior.alias.synopsis=The order in which startup plug-ins are loaded and invoked is undefined.
+property.plugin-order-subordinate-modify-dn.synopsis=Specifies the order in which subordinate modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-subordinate-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-subordinate-modify-dn.default-behavior.alias.synopsis=The order in which subordinate modify DN plug-ins are loaded and invoked is undefined.
+relation.plugin.user-friendly-name=Plugin
+relation.plugin.user-friendly-plural-name=Plugins
+relation.plugin.synopsis=Plugins provide a mechanism for executing custom code at specified points in operation processing and in the course of other events like connection establishment and termination, server startup and shutdown, and LDIF import and export.
diff --git a/opends/src/admin/messages/PluginRootCfgDefn_fr.properties b/opends/src/admin/messages/PluginRootCfgDefn_fr.properties
new file mode 100644
index 0000000..d15ac52
--- /dev/null
+++ b/opends/src/admin/messages/PluginRootCfgDefn_fr.properties
@@ -0,0 +1,157 @@
+user-friendly-name=Plugin Root
+user-friendly-plural-name=Plugin Roots
+synopsis=The Plugin Root defines the parent entry for all plug-ins defined in the server.
+description=It can also include configuration attributes that define the order in which those plug-ins are to be loaded and invoked.
+property.plugin-order-intermediate-response.synopsis=Specifies the order in which intermediate response plug-ins are to be loaded and invoked.
+property.plugin-order-intermediate-response.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-intermediate-response.default-behavior.alias.synopsis=The order in which intermediate response plug-ins are loaded and invoked is undefined.
+property.plugin-order-ldif-export.synopsis=Specifies the order in which LDIF export plug-ins are to be loaded and invoked.
+property.plugin-order-ldif-export.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-ldif-export.default-behavior.alias.synopsis=The order in which LDIF export plug-ins are loaded and invoked is undefined.
+property.plugin-order-ldif-import.synopsis=Specifies the order in which LDIF import plug-ins are to be loaded and invoked.
+property.plugin-order-ldif-import.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-ldif-import.default-behavior.alias.synopsis=The order in which LDIF import plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-connect.synopsis=Specifies the order in which post-connect plug-ins are to be loaded and invoked.
+property.plugin-order-post-connect.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-connect.default-behavior.alias.synopsis=The order in which post-connect plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-disconnect.synopsis=Specifies the order in which post-disconnect plug-ins are to be loaded and invoked.
+property.plugin-order-post-disconnect.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-disconnect.default-behavior.alias.synopsis=The order in which post-disconnect plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-abandon.synopsis=Specifies the order in which post-operation abandon plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-abandon.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-abandon.default-behavior.alias.synopsis=The order in which post-operation abandon plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-add.synopsis=Specifies the order in which post-operation add plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-add.default-behavior.alias.synopsis=The order in which post-operation add plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-bind.synopsis=Specifies the order in which post-operation bind plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-bind.default-behavior.alias.synopsis=The order in which post-operation bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-compare.synopsis=Specifies the order in which post-operation compare plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-compare.default-behavior.alias.synopsis=The order in which post-operation compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-delete.synopsis=Specifies the order in which post-operation delete plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-delete.default-behavior.alias.synopsis=The order in which post-operation delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-extended.synopsis=Specifies the order in which post-operation extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-extended.default-behavior.alias.synopsis=The order in which post-operation extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-modify.synopsis=Specifies the order in which post-operation modify plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-modify.default-behavior.alias.synopsis=The order in which post-operation modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-modify-dn.synopsis=Specifies the order in which post-operation modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-modify-dn.default-behavior.alias.synopsis=The order in which post-operation modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-search.synopsis=Specifies the order in which post-operation search plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-search.default-behavior.alias.synopsis=The order in which post-operation search plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-unbind.synopsis=Specifies the order in which post-operation unbind plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-unbind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-unbind.default-behavior.alias.synopsis=The order in which post-operation unbind plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-add.synopsis=Specifies the order in which post-response add plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-add.default-behavior.alias.synopsis=The order in which post-response add plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-bind.synopsis=Specifies the order in which post-response bind plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-bind.default-behavior.alias.synopsis=The order in which post-response bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-compare.synopsis=Specifies the order in which post-response compare plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-compare.default-behavior.alias.synopsis=The order in which post-response compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-delete.synopsis=Specifies the order in which post-response delete plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-delete.default-behavior.alias.synopsis=The order in which post-response delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-extended.synopsis=Specifies the order in which post-response extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-extended.default-behavior.alias.synopsis=The order in which post-response extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-modify.synopsis=Specifies the order in which post-response modify plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-modify.default-behavior.alias.synopsis=The order in which post-response modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-modify-dn.synopsis=Specifies the order in which post-response modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-modify-dn.default-behavior.alias.synopsis=The order in which post-response modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-search.synopsis=Specifies the order in which post-response search plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-search.default-behavior.alias.synopsis=The order in which post-response search plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-add.synopsis=Specifies the order in which post-synchronization add plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-add.default-behavior.alias.synopsis=The order in which post-synchronization add plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-delete.synopsis=Specifies the order in which post-synchronization delete plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-delete.default-behavior.alias.synopsis=The order in which post-synchronization delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-modify.synopsis=Specifies the order in which post-synchronization modify plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-modify.default-behavior.alias.synopsis=The order in which post-synchronization modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-modify-dn.synopsis=Specifies the order in which post-synchronization modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-modify-dn.default-behavior.alias.synopsis=The order in which post-synchronization modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-add.synopsis=Specifies the order in which pre-operation add plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-add.default-behavior.alias.synopsis=The order in which pre-operation add plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-bind.synopsis=Specifies the order in which pre-operation bind plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-bind.default-behavior.alias.synopsis=The order in which pre-operation bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-compare.synopsis=Specifies the order in which pre-operation compare plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-compare.default-behavior.alias.synopsis=The order in which pre-operation compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-delete.synopsis=Specifies the order in which pre-operation delete plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-delete.default-behavior.alias.synopsis=The order in which pre-operation delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-extended.synopsis=Specifies the order in which pre-operation extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-extended.default-behavior.alias.synopsis=The order in which pre-operation extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-modify.synopsis=Specifies the order in which pre-operation modify plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-modify.default-behavior.alias.synopsis=The order in which pre-operation modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-modify-dn.synopsis=Specifies the order in which pre-operation modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-modify-dn.default-behavior.alias.synopsis=The order in which pre-operation modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-search.synopsis=Specifies the order in which pre-operation search plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-search.default-behavior.alias.synopsis=The order in which pre-operation searc plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-abandon.synopsis=Specifies the order in which pre-parse abandon plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-abandon.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-abandon.default-behavior.alias.synopsis=The order in which pre-parse abandon plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-add.synopsis=Specifies the order in which pre-parse add plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-add.default-behavior.alias.synopsis=The order in which pre-parse add plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-bind.synopsis=Specifies the order in which pre-parse bind plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-bind.default-behavior.alias.synopsis=The order in which pre-parse bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-compare.synopsis=Specifies the order in which pre-parse compare plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-compare.default-behavior.alias.synopsis=The order in which pre-parse compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-delete.synopsis=Specifies the order in which pre-parse delete plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-delete.default-behavior.alias.synopsis=The order in which pre-parse delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-extended.synopsis=Specifies the order in which pre-parse extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-extended.default-behavior.alias.synopsis=The order in which pre-parse extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-modify.synopsis=Specifies the order in which pre-parse modify plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-modify.default-behavior.alias.synopsis=The order in which pre-parse modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-modify-dn.synopsis=Specifies the order in which pre-parse modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-modify-dn.default-behavior.alias.synopsis=The order in which pre-parse modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-search.synopsis=Specifies the order in which pre-parse search plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-search.default-behavior.alias.synopsis=The order in which pre-parse search plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-unbind.synopsis=Specifies the order in which pre-parse unbind plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-unbind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-unbind.default-behavior.alias.synopsis=The order in which pre-parse unbind plug-ins are loaded and invoked is undefined.
+property.plugin-order-search-result-entry.synopsis=Specifies the order in which search result entry plug-ins are to be loaded and invoked.
+property.plugin-order-search-result-entry.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-search-result-entry.default-behavior.alias.synopsis=The order in which search result entry plug-ins are loaded and invoked is undefined.
+property.plugin-order-search-result-reference.synopsis=Specifies the order in which search result reference plug-ins are to be loaded and invoked.
+property.plugin-order-search-result-reference.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-search-result-reference.default-behavior.alias.synopsis=The order in which search result reference plug-ins are loaded and invoked is undefined.
+property.plugin-order-shutdown.synopsis=Specifies the order in which shutdown plug-ins are to be loaded and invoked.
+property.plugin-order-shutdown.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-shutdown.default-behavior.alias.synopsis=The order in which shutdown plug-ins are loaded and invoked is undefined.
+property.plugin-order-startup.synopsis=Specifies the order in which startup plug-ins are to be loaded and invoked.
+property.plugin-order-startup.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-startup.default-behavior.alias.synopsis=The order in which startup plug-ins are loaded and invoked is undefined.
+property.plugin-order-subordinate-modify-dn.synopsis=Specifies the order in which subordinate modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-subordinate-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-subordinate-modify-dn.default-behavior.alias.synopsis=The order in which subordinate modify DN plug-ins are loaded and invoked is undefined.
+relation.plugin.user-friendly-name=Plugin
+relation.plugin.user-friendly-plural-name=Plugins
+relation.plugin.synopsis=Plugins provide a mechanism for executing custom code at specified points in operation processing and in the course of other events like connection establishment and termination, server startup and shutdown, and LDIF import and export.
diff --git a/opends/src/admin/messages/PluginRootCfgDefn_ja.properties b/opends/src/admin/messages/PluginRootCfgDefn_ja.properties
new file mode 100644
index 0000000..d15ac52
--- /dev/null
+++ b/opends/src/admin/messages/PluginRootCfgDefn_ja.properties
@@ -0,0 +1,157 @@
+user-friendly-name=Plugin Root
+user-friendly-plural-name=Plugin Roots
+synopsis=The Plugin Root defines the parent entry for all plug-ins defined in the server.
+description=It can also include configuration attributes that define the order in which those plug-ins are to be loaded and invoked.
+property.plugin-order-intermediate-response.synopsis=Specifies the order in which intermediate response plug-ins are to be loaded and invoked.
+property.plugin-order-intermediate-response.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-intermediate-response.default-behavior.alias.synopsis=The order in which intermediate response plug-ins are loaded and invoked is undefined.
+property.plugin-order-ldif-export.synopsis=Specifies the order in which LDIF export plug-ins are to be loaded and invoked.
+property.plugin-order-ldif-export.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-ldif-export.default-behavior.alias.synopsis=The order in which LDIF export plug-ins are loaded and invoked is undefined.
+property.plugin-order-ldif-import.synopsis=Specifies the order in which LDIF import plug-ins are to be loaded and invoked.
+property.plugin-order-ldif-import.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-ldif-import.default-behavior.alias.synopsis=The order in which LDIF import plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-connect.synopsis=Specifies the order in which post-connect plug-ins are to be loaded and invoked.
+property.plugin-order-post-connect.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-connect.default-behavior.alias.synopsis=The order in which post-connect plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-disconnect.synopsis=Specifies the order in which post-disconnect plug-ins are to be loaded and invoked.
+property.plugin-order-post-disconnect.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-disconnect.default-behavior.alias.synopsis=The order in which post-disconnect plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-abandon.synopsis=Specifies the order in which post-operation abandon plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-abandon.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-abandon.default-behavior.alias.synopsis=The order in which post-operation abandon plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-add.synopsis=Specifies the order in which post-operation add plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-add.default-behavior.alias.synopsis=The order in which post-operation add plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-bind.synopsis=Specifies the order in which post-operation bind plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-bind.default-behavior.alias.synopsis=The order in which post-operation bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-compare.synopsis=Specifies the order in which post-operation compare plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-compare.default-behavior.alias.synopsis=The order in which post-operation compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-delete.synopsis=Specifies the order in which post-operation delete plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-delete.default-behavior.alias.synopsis=The order in which post-operation delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-extended.synopsis=Specifies the order in which post-operation extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-extended.default-behavior.alias.synopsis=The order in which post-operation extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-modify.synopsis=Specifies the order in which post-operation modify plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-modify.default-behavior.alias.synopsis=The order in which post-operation modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-modify-dn.synopsis=Specifies the order in which post-operation modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-modify-dn.default-behavior.alias.synopsis=The order in which post-operation modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-search.synopsis=Specifies the order in which post-operation search plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-search.default-behavior.alias.synopsis=The order in which post-operation search plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-unbind.synopsis=Specifies the order in which post-operation unbind plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-unbind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-unbind.default-behavior.alias.synopsis=The order in which post-operation unbind plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-add.synopsis=Specifies the order in which post-response add plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-add.default-behavior.alias.synopsis=The order in which post-response add plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-bind.synopsis=Specifies the order in which post-response bind plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-bind.default-behavior.alias.synopsis=The order in which post-response bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-compare.synopsis=Specifies the order in which post-response compare plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-compare.default-behavior.alias.synopsis=The order in which post-response compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-delete.synopsis=Specifies the order in which post-response delete plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-delete.default-behavior.alias.synopsis=The order in which post-response delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-extended.synopsis=Specifies the order in which post-response extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-extended.default-behavior.alias.synopsis=The order in which post-response extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-modify.synopsis=Specifies the order in which post-response modify plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-modify.default-behavior.alias.synopsis=The order in which post-response modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-modify-dn.synopsis=Specifies the order in which post-response modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-modify-dn.default-behavior.alias.synopsis=The order in which post-response modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-search.synopsis=Specifies the order in which post-response search plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-search.default-behavior.alias.synopsis=The order in which post-response search plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-add.synopsis=Specifies the order in which post-synchronization add plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-add.default-behavior.alias.synopsis=The order in which post-synchronization add plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-delete.synopsis=Specifies the order in which post-synchronization delete plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-delete.default-behavior.alias.synopsis=The order in which post-synchronization delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-modify.synopsis=Specifies the order in which post-synchronization modify plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-modify.default-behavior.alias.synopsis=The order in which post-synchronization modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-modify-dn.synopsis=Specifies the order in which post-synchronization modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-modify-dn.default-behavior.alias.synopsis=The order in which post-synchronization modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-add.synopsis=Specifies the order in which pre-operation add plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-add.default-behavior.alias.synopsis=The order in which pre-operation add plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-bind.synopsis=Specifies the order in which pre-operation bind plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-bind.default-behavior.alias.synopsis=The order in which pre-operation bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-compare.synopsis=Specifies the order in which pre-operation compare plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-compare.default-behavior.alias.synopsis=The order in which pre-operation compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-delete.synopsis=Specifies the order in which pre-operation delete plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-delete.default-behavior.alias.synopsis=The order in which pre-operation delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-extended.synopsis=Specifies the order in which pre-operation extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-extended.default-behavior.alias.synopsis=The order in which pre-operation extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-modify.synopsis=Specifies the order in which pre-operation modify plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-modify.default-behavior.alias.synopsis=The order in which pre-operation modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-modify-dn.synopsis=Specifies the order in which pre-operation modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-modify-dn.default-behavior.alias.synopsis=The order in which pre-operation modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-search.synopsis=Specifies the order in which pre-operation search plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-search.default-behavior.alias.synopsis=The order in which pre-operation searc plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-abandon.synopsis=Specifies the order in which pre-parse abandon plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-abandon.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-abandon.default-behavior.alias.synopsis=The order in which pre-parse abandon plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-add.synopsis=Specifies the order in which pre-parse add plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-add.default-behavior.alias.synopsis=The order in which pre-parse add plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-bind.synopsis=Specifies the order in which pre-parse bind plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-bind.default-behavior.alias.synopsis=The order in which pre-parse bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-compare.synopsis=Specifies the order in which pre-parse compare plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-compare.default-behavior.alias.synopsis=The order in which pre-parse compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-delete.synopsis=Specifies the order in which pre-parse delete plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-delete.default-behavior.alias.synopsis=The order in which pre-parse delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-extended.synopsis=Specifies the order in which pre-parse extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-extended.default-behavior.alias.synopsis=The order in which pre-parse extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-modify.synopsis=Specifies the order in which pre-parse modify plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-modify.default-behavior.alias.synopsis=The order in which pre-parse modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-modify-dn.synopsis=Specifies the order in which pre-parse modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-modify-dn.default-behavior.alias.synopsis=The order in which pre-parse modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-search.synopsis=Specifies the order in which pre-parse search plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-search.default-behavior.alias.synopsis=The order in which pre-parse search plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-unbind.synopsis=Specifies the order in which pre-parse unbind plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-unbind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-unbind.default-behavior.alias.synopsis=The order in which pre-parse unbind plug-ins are loaded and invoked is undefined.
+property.plugin-order-search-result-entry.synopsis=Specifies the order in which search result entry plug-ins are to be loaded and invoked.
+property.plugin-order-search-result-entry.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-search-result-entry.default-behavior.alias.synopsis=The order in which search result entry plug-ins are loaded and invoked is undefined.
+property.plugin-order-search-result-reference.synopsis=Specifies the order in which search result reference plug-ins are to be loaded and invoked.
+property.plugin-order-search-result-reference.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-search-result-reference.default-behavior.alias.synopsis=The order in which search result reference plug-ins are loaded and invoked is undefined.
+property.plugin-order-shutdown.synopsis=Specifies the order in which shutdown plug-ins are to be loaded and invoked.
+property.plugin-order-shutdown.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-shutdown.default-behavior.alias.synopsis=The order in which shutdown plug-ins are loaded and invoked is undefined.
+property.plugin-order-startup.synopsis=Specifies the order in which startup plug-ins are to be loaded and invoked.
+property.plugin-order-startup.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-startup.default-behavior.alias.synopsis=The order in which startup plug-ins are loaded and invoked is undefined.
+property.plugin-order-subordinate-modify-dn.synopsis=Specifies the order in which subordinate modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-subordinate-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-subordinate-modify-dn.default-behavior.alias.synopsis=The order in which subordinate modify DN plug-ins are loaded and invoked is undefined.
+relation.plugin.user-friendly-name=Plugin
+relation.plugin.user-friendly-plural-name=Plugins
+relation.plugin.synopsis=Plugins provide a mechanism for executing custom code at specified points in operation processing and in the course of other events like connection establishment and termination, server startup and shutdown, and LDIF import and export.
diff --git a/opends/src/admin/messages/PluginRootCfgDefn_ko.properties b/opends/src/admin/messages/PluginRootCfgDefn_ko.properties
new file mode 100644
index 0000000..d15ac52
--- /dev/null
+++ b/opends/src/admin/messages/PluginRootCfgDefn_ko.properties
@@ -0,0 +1,157 @@
+user-friendly-name=Plugin Root
+user-friendly-plural-name=Plugin Roots
+synopsis=The Plugin Root defines the parent entry for all plug-ins defined in the server.
+description=It can also include configuration attributes that define the order in which those plug-ins are to be loaded and invoked.
+property.plugin-order-intermediate-response.synopsis=Specifies the order in which intermediate response plug-ins are to be loaded and invoked.
+property.plugin-order-intermediate-response.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-intermediate-response.default-behavior.alias.synopsis=The order in which intermediate response plug-ins are loaded and invoked is undefined.
+property.plugin-order-ldif-export.synopsis=Specifies the order in which LDIF export plug-ins are to be loaded and invoked.
+property.plugin-order-ldif-export.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-ldif-export.default-behavior.alias.synopsis=The order in which LDIF export plug-ins are loaded and invoked is undefined.
+property.plugin-order-ldif-import.synopsis=Specifies the order in which LDIF import plug-ins are to be loaded and invoked.
+property.plugin-order-ldif-import.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-ldif-import.default-behavior.alias.synopsis=The order in which LDIF import plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-connect.synopsis=Specifies the order in which post-connect plug-ins are to be loaded and invoked.
+property.plugin-order-post-connect.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-connect.default-behavior.alias.synopsis=The order in which post-connect plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-disconnect.synopsis=Specifies the order in which post-disconnect plug-ins are to be loaded and invoked.
+property.plugin-order-post-disconnect.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-disconnect.default-behavior.alias.synopsis=The order in which post-disconnect plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-abandon.synopsis=Specifies the order in which post-operation abandon plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-abandon.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-abandon.default-behavior.alias.synopsis=The order in which post-operation abandon plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-add.synopsis=Specifies the order in which post-operation add plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-add.default-behavior.alias.synopsis=The order in which post-operation add plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-bind.synopsis=Specifies the order in which post-operation bind plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-bind.default-behavior.alias.synopsis=The order in which post-operation bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-compare.synopsis=Specifies the order in which post-operation compare plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-compare.default-behavior.alias.synopsis=The order in which post-operation compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-delete.synopsis=Specifies the order in which post-operation delete plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-delete.default-behavior.alias.synopsis=The order in which post-operation delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-extended.synopsis=Specifies the order in which post-operation extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-extended.default-behavior.alias.synopsis=The order in which post-operation extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-modify.synopsis=Specifies the order in which post-operation modify plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-modify.default-behavior.alias.synopsis=The order in which post-operation modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-modify-dn.synopsis=Specifies the order in which post-operation modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-modify-dn.default-behavior.alias.synopsis=The order in which post-operation modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-search.synopsis=Specifies the order in which post-operation search plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-search.default-behavior.alias.synopsis=The order in which post-operation search plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-unbind.synopsis=Specifies the order in which post-operation unbind plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-unbind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-unbind.default-behavior.alias.synopsis=The order in which post-operation unbind plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-add.synopsis=Specifies the order in which post-response add plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-add.default-behavior.alias.synopsis=The order in which post-response add plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-bind.synopsis=Specifies the order in which post-response bind plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-bind.default-behavior.alias.synopsis=The order in which post-response bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-compare.synopsis=Specifies the order in which post-response compare plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-compare.default-behavior.alias.synopsis=The order in which post-response compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-delete.synopsis=Specifies the order in which post-response delete plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-delete.default-behavior.alias.synopsis=The order in which post-response delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-extended.synopsis=Specifies the order in which post-response extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-extended.default-behavior.alias.synopsis=The order in which post-response extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-modify.synopsis=Specifies the order in which post-response modify plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-modify.default-behavior.alias.synopsis=The order in which post-response modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-modify-dn.synopsis=Specifies the order in which post-response modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-modify-dn.default-behavior.alias.synopsis=The order in which post-response modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-search.synopsis=Specifies the order in which post-response search plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-search.default-behavior.alias.synopsis=The order in which post-response search plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-add.synopsis=Specifies the order in which post-synchronization add plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-add.default-behavior.alias.synopsis=The order in which post-synchronization add plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-delete.synopsis=Specifies the order in which post-synchronization delete plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-delete.default-behavior.alias.synopsis=The order in which post-synchronization delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-modify.synopsis=Specifies the order in which post-synchronization modify plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-modify.default-behavior.alias.synopsis=The order in which post-synchronization modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-modify-dn.synopsis=Specifies the order in which post-synchronization modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-modify-dn.default-behavior.alias.synopsis=The order in which post-synchronization modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-add.synopsis=Specifies the order in which pre-operation add plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-add.default-behavior.alias.synopsis=The order in which pre-operation add plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-bind.synopsis=Specifies the order in which pre-operation bind plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-bind.default-behavior.alias.synopsis=The order in which pre-operation bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-compare.synopsis=Specifies the order in which pre-operation compare plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-compare.default-behavior.alias.synopsis=The order in which pre-operation compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-delete.synopsis=Specifies the order in which pre-operation delete plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-delete.default-behavior.alias.synopsis=The order in which pre-operation delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-extended.synopsis=Specifies the order in which pre-operation extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-extended.default-behavior.alias.synopsis=The order in which pre-operation extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-modify.synopsis=Specifies the order in which pre-operation modify plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-modify.default-behavior.alias.synopsis=The order in which pre-operation modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-modify-dn.synopsis=Specifies the order in which pre-operation modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-modify-dn.default-behavior.alias.synopsis=The order in which pre-operation modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-search.synopsis=Specifies the order in which pre-operation search plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-search.default-behavior.alias.synopsis=The order in which pre-operation searc plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-abandon.synopsis=Specifies the order in which pre-parse abandon plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-abandon.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-abandon.default-behavior.alias.synopsis=The order in which pre-parse abandon plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-add.synopsis=Specifies the order in which pre-parse add plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-add.default-behavior.alias.synopsis=The order in which pre-parse add plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-bind.synopsis=Specifies the order in which pre-parse bind plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-bind.default-behavior.alias.synopsis=The order in which pre-parse bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-compare.synopsis=Specifies the order in which pre-parse compare plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-compare.default-behavior.alias.synopsis=The order in which pre-parse compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-delete.synopsis=Specifies the order in which pre-parse delete plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-delete.default-behavior.alias.synopsis=The order in which pre-parse delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-extended.synopsis=Specifies the order in which pre-parse extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-extended.default-behavior.alias.synopsis=The order in which pre-parse extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-modify.synopsis=Specifies the order in which pre-parse modify plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-modify.default-behavior.alias.synopsis=The order in which pre-parse modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-modify-dn.synopsis=Specifies the order in which pre-parse modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-modify-dn.default-behavior.alias.synopsis=The order in which pre-parse modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-search.synopsis=Specifies the order in which pre-parse search plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-search.default-behavior.alias.synopsis=The order in which pre-parse search plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-unbind.synopsis=Specifies the order in which pre-parse unbind plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-unbind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-unbind.default-behavior.alias.synopsis=The order in which pre-parse unbind plug-ins are loaded and invoked is undefined.
+property.plugin-order-search-result-entry.synopsis=Specifies the order in which search result entry plug-ins are to be loaded and invoked.
+property.plugin-order-search-result-entry.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-search-result-entry.default-behavior.alias.synopsis=The order in which search result entry plug-ins are loaded and invoked is undefined.
+property.plugin-order-search-result-reference.synopsis=Specifies the order in which search result reference plug-ins are to be loaded and invoked.
+property.plugin-order-search-result-reference.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-search-result-reference.default-behavior.alias.synopsis=The order in which search result reference plug-ins are loaded and invoked is undefined.
+property.plugin-order-shutdown.synopsis=Specifies the order in which shutdown plug-ins are to be loaded and invoked.
+property.plugin-order-shutdown.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-shutdown.default-behavior.alias.synopsis=The order in which shutdown plug-ins are loaded and invoked is undefined.
+property.plugin-order-startup.synopsis=Specifies the order in which startup plug-ins are to be loaded and invoked.
+property.plugin-order-startup.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-startup.default-behavior.alias.synopsis=The order in which startup plug-ins are loaded and invoked is undefined.
+property.plugin-order-subordinate-modify-dn.synopsis=Specifies the order in which subordinate modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-subordinate-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-subordinate-modify-dn.default-behavior.alias.synopsis=The order in which subordinate modify DN plug-ins are loaded and invoked is undefined.
+relation.plugin.user-friendly-name=Plugin
+relation.plugin.user-friendly-plural-name=Plugins
+relation.plugin.synopsis=Plugins provide a mechanism for executing custom code at specified points in operation processing and in the course of other events like connection establishment and termination, server startup and shutdown, and LDIF import and export.
diff --git a/opends/src/admin/messages/PluginRootCfgDefn_zh_CN.properties b/opends/src/admin/messages/PluginRootCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..d15ac52
--- /dev/null
+++ b/opends/src/admin/messages/PluginRootCfgDefn_zh_CN.properties
@@ -0,0 +1,157 @@
+user-friendly-name=Plugin Root
+user-friendly-plural-name=Plugin Roots
+synopsis=The Plugin Root defines the parent entry for all plug-ins defined in the server.
+description=It can also include configuration attributes that define the order in which those plug-ins are to be loaded and invoked.
+property.plugin-order-intermediate-response.synopsis=Specifies the order in which intermediate response plug-ins are to be loaded and invoked.
+property.plugin-order-intermediate-response.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-intermediate-response.default-behavior.alias.synopsis=The order in which intermediate response plug-ins are loaded and invoked is undefined.
+property.plugin-order-ldif-export.synopsis=Specifies the order in which LDIF export plug-ins are to be loaded and invoked.
+property.plugin-order-ldif-export.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-ldif-export.default-behavior.alias.synopsis=The order in which LDIF export plug-ins are loaded and invoked is undefined.
+property.plugin-order-ldif-import.synopsis=Specifies the order in which LDIF import plug-ins are to be loaded and invoked.
+property.plugin-order-ldif-import.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-ldif-import.default-behavior.alias.synopsis=The order in which LDIF import plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-connect.synopsis=Specifies the order in which post-connect plug-ins are to be loaded and invoked.
+property.plugin-order-post-connect.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-connect.default-behavior.alias.synopsis=The order in which post-connect plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-disconnect.synopsis=Specifies the order in which post-disconnect plug-ins are to be loaded and invoked.
+property.plugin-order-post-disconnect.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-disconnect.default-behavior.alias.synopsis=The order in which post-disconnect plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-abandon.synopsis=Specifies the order in which post-operation abandon plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-abandon.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-abandon.default-behavior.alias.synopsis=The order in which post-operation abandon plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-add.synopsis=Specifies the order in which post-operation add plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-add.default-behavior.alias.synopsis=The order in which post-operation add plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-bind.synopsis=Specifies the order in which post-operation bind plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-bind.default-behavior.alias.synopsis=The order in which post-operation bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-compare.synopsis=Specifies the order in which post-operation compare plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-compare.default-behavior.alias.synopsis=The order in which post-operation compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-delete.synopsis=Specifies the order in which post-operation delete plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-delete.default-behavior.alias.synopsis=The order in which post-operation delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-extended.synopsis=Specifies the order in which post-operation extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-extended.default-behavior.alias.synopsis=The order in which post-operation extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-modify.synopsis=Specifies the order in which post-operation modify plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-modify.default-behavior.alias.synopsis=The order in which post-operation modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-modify-dn.synopsis=Specifies the order in which post-operation modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-modify-dn.default-behavior.alias.synopsis=The order in which post-operation modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-search.synopsis=Specifies the order in which post-operation search plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-search.default-behavior.alias.synopsis=The order in which post-operation search plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-unbind.synopsis=Specifies the order in which post-operation unbind plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-unbind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-unbind.default-behavior.alias.synopsis=The order in which post-operation unbind plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-add.synopsis=Specifies the order in which post-response add plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-add.default-behavior.alias.synopsis=The order in which post-response add plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-bind.synopsis=Specifies the order in which post-response bind plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-bind.default-behavior.alias.synopsis=The order in which post-response bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-compare.synopsis=Specifies the order in which post-response compare plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-compare.default-behavior.alias.synopsis=The order in which post-response compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-delete.synopsis=Specifies the order in which post-response delete plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-delete.default-behavior.alias.synopsis=The order in which post-response delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-extended.synopsis=Specifies the order in which post-response extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-extended.default-behavior.alias.synopsis=The order in which post-response extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-modify.synopsis=Specifies the order in which post-response modify plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-modify.default-behavior.alias.synopsis=The order in which post-response modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-modify-dn.synopsis=Specifies the order in which post-response modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-modify-dn.default-behavior.alias.synopsis=The order in which post-response modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-search.synopsis=Specifies the order in which post-response search plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-search.default-behavior.alias.synopsis=The order in which post-response search plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-add.synopsis=Specifies the order in which post-synchronization add plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-add.default-behavior.alias.synopsis=The order in which post-synchronization add plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-delete.synopsis=Specifies the order in which post-synchronization delete plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-delete.default-behavior.alias.synopsis=The order in which post-synchronization delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-modify.synopsis=Specifies the order in which post-synchronization modify plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-modify.default-behavior.alias.synopsis=The order in which post-synchronization modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-modify-dn.synopsis=Specifies the order in which post-synchronization modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-modify-dn.default-behavior.alias.synopsis=The order in which post-synchronization modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-add.synopsis=Specifies the order in which pre-operation add plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-add.default-behavior.alias.synopsis=The order in which pre-operation add plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-bind.synopsis=Specifies the order in which pre-operation bind plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-bind.default-behavior.alias.synopsis=The order in which pre-operation bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-compare.synopsis=Specifies the order in which pre-operation compare plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-compare.default-behavior.alias.synopsis=The order in which pre-operation compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-delete.synopsis=Specifies the order in which pre-operation delete plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-delete.default-behavior.alias.synopsis=The order in which pre-operation delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-extended.synopsis=Specifies the order in which pre-operation extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-extended.default-behavior.alias.synopsis=The order in which pre-operation extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-modify.synopsis=Specifies the order in which pre-operation modify plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-modify.default-behavior.alias.synopsis=The order in which pre-operation modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-modify-dn.synopsis=Specifies the order in which pre-operation modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-modify-dn.default-behavior.alias.synopsis=The order in which pre-operation modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-search.synopsis=Specifies the order in which pre-operation search plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-search.default-behavior.alias.synopsis=The order in which pre-operation searc plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-abandon.synopsis=Specifies the order in which pre-parse abandon plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-abandon.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-abandon.default-behavior.alias.synopsis=The order in which pre-parse abandon plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-add.synopsis=Specifies the order in which pre-parse add plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-add.default-behavior.alias.synopsis=The order in which pre-parse add plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-bind.synopsis=Specifies the order in which pre-parse bind plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-bind.default-behavior.alias.synopsis=The order in which pre-parse bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-compare.synopsis=Specifies the order in which pre-parse compare plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-compare.default-behavior.alias.synopsis=The order in which pre-parse compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-delete.synopsis=Specifies the order in which pre-parse delete plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-delete.default-behavior.alias.synopsis=The order in which pre-parse delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-extended.synopsis=Specifies the order in which pre-parse extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-extended.default-behavior.alias.synopsis=The order in which pre-parse extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-modify.synopsis=Specifies the order in which pre-parse modify plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-modify.default-behavior.alias.synopsis=The order in which pre-parse modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-modify-dn.synopsis=Specifies the order in which pre-parse modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-modify-dn.default-behavior.alias.synopsis=The order in which pre-parse modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-search.synopsis=Specifies the order in which pre-parse search plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-search.default-behavior.alias.synopsis=The order in which pre-parse search plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-unbind.synopsis=Specifies the order in which pre-parse unbind plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-unbind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-unbind.default-behavior.alias.synopsis=The order in which pre-parse unbind plug-ins are loaded and invoked is undefined.
+property.plugin-order-search-result-entry.synopsis=Specifies the order in which search result entry plug-ins are to be loaded and invoked.
+property.plugin-order-search-result-entry.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-search-result-entry.default-behavior.alias.synopsis=The order in which search result entry plug-ins are loaded and invoked is undefined.
+property.plugin-order-search-result-reference.synopsis=Specifies the order in which search result reference plug-ins are to be loaded and invoked.
+property.plugin-order-search-result-reference.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-search-result-reference.default-behavior.alias.synopsis=The order in which search result reference plug-ins are loaded and invoked is undefined.
+property.plugin-order-shutdown.synopsis=Specifies the order in which shutdown plug-ins are to be loaded and invoked.
+property.plugin-order-shutdown.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-shutdown.default-behavior.alias.synopsis=The order in which shutdown plug-ins are loaded and invoked is undefined.
+property.plugin-order-startup.synopsis=Specifies the order in which startup plug-ins are to be loaded and invoked.
+property.plugin-order-startup.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-startup.default-behavior.alias.synopsis=The order in which startup plug-ins are loaded and invoked is undefined.
+property.plugin-order-subordinate-modify-dn.synopsis=Specifies the order in which subordinate modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-subordinate-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-subordinate-modify-dn.default-behavior.alias.synopsis=The order in which subordinate modify DN plug-ins are loaded and invoked is undefined.
+relation.plugin.user-friendly-name=Plugin
+relation.plugin.user-friendly-plural-name=Plugins
+relation.plugin.synopsis=Plugins provide a mechanism for executing custom code at specified points in operation processing and in the course of other events like connection establishment and termination, server startup and shutdown, and LDIF import and export.
diff --git a/opends/src/admin/messages/PluginRootCfgDefn_zh_TW.properties b/opends/src/admin/messages/PluginRootCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..d15ac52
--- /dev/null
+++ b/opends/src/admin/messages/PluginRootCfgDefn_zh_TW.properties
@@ -0,0 +1,157 @@
+user-friendly-name=Plugin Root
+user-friendly-plural-name=Plugin Roots
+synopsis=The Plugin Root defines the parent entry for all plug-ins defined in the server.
+description=It can also include configuration attributes that define the order in which those plug-ins are to be loaded and invoked.
+property.plugin-order-intermediate-response.synopsis=Specifies the order in which intermediate response plug-ins are to be loaded and invoked.
+property.plugin-order-intermediate-response.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-intermediate-response.default-behavior.alias.synopsis=The order in which intermediate response plug-ins are loaded and invoked is undefined.
+property.plugin-order-ldif-export.synopsis=Specifies the order in which LDIF export plug-ins are to be loaded and invoked.
+property.plugin-order-ldif-export.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-ldif-export.default-behavior.alias.synopsis=The order in which LDIF export plug-ins are loaded and invoked is undefined.
+property.plugin-order-ldif-import.synopsis=Specifies the order in which LDIF import plug-ins are to be loaded and invoked.
+property.plugin-order-ldif-import.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-ldif-import.default-behavior.alias.synopsis=The order in which LDIF import plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-connect.synopsis=Specifies the order in which post-connect plug-ins are to be loaded and invoked.
+property.plugin-order-post-connect.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-connect.default-behavior.alias.synopsis=The order in which post-connect plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-disconnect.synopsis=Specifies the order in which post-disconnect plug-ins are to be loaded and invoked.
+property.plugin-order-post-disconnect.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-disconnect.default-behavior.alias.synopsis=The order in which post-disconnect plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-abandon.synopsis=Specifies the order in which post-operation abandon plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-abandon.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-abandon.default-behavior.alias.synopsis=The order in which post-operation abandon plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-add.synopsis=Specifies the order in which post-operation add plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-add.default-behavior.alias.synopsis=The order in which post-operation add plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-bind.synopsis=Specifies the order in which post-operation bind plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-bind.default-behavior.alias.synopsis=The order in which post-operation bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-compare.synopsis=Specifies the order in which post-operation compare plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-compare.default-behavior.alias.synopsis=The order in which post-operation compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-delete.synopsis=Specifies the order in which post-operation delete plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-delete.default-behavior.alias.synopsis=The order in which post-operation delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-extended.synopsis=Specifies the order in which post-operation extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-extended.default-behavior.alias.synopsis=The order in which post-operation extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-modify.synopsis=Specifies the order in which post-operation modify plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-modify.default-behavior.alias.synopsis=The order in which post-operation modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-modify-dn.synopsis=Specifies the order in which post-operation modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-modify-dn.default-behavior.alias.synopsis=The order in which post-operation modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-search.synopsis=Specifies the order in which post-operation search plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-search.default-behavior.alias.synopsis=The order in which post-operation search plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-operation-unbind.synopsis=Specifies the order in which post-operation unbind plug-ins are to be loaded and invoked.
+property.plugin-order-post-operation-unbind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-operation-unbind.default-behavior.alias.synopsis=The order in which post-operation unbind plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-add.synopsis=Specifies the order in which post-response add plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-add.default-behavior.alias.synopsis=The order in which post-response add plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-bind.synopsis=Specifies the order in which post-response bind plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-bind.default-behavior.alias.synopsis=The order in which post-response bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-compare.synopsis=Specifies the order in which post-response compare plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-compare.default-behavior.alias.synopsis=The order in which post-response compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-delete.synopsis=Specifies the order in which post-response delete plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-delete.default-behavior.alias.synopsis=The order in which post-response delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-extended.synopsis=Specifies the order in which post-response extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-extended.default-behavior.alias.synopsis=The order in which post-response extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-modify.synopsis=Specifies the order in which post-response modify plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-modify.default-behavior.alias.synopsis=The order in which post-response modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-modify-dn.synopsis=Specifies the order in which post-response modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-modify-dn.default-behavior.alias.synopsis=The order in which post-response modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-response-search.synopsis=Specifies the order in which post-response search plug-ins are to be loaded and invoked.
+property.plugin-order-post-response-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-response-search.default-behavior.alias.synopsis=The order in which post-response search plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-add.synopsis=Specifies the order in which post-synchronization add plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-add.default-behavior.alias.synopsis=The order in which post-synchronization add plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-delete.synopsis=Specifies the order in which post-synchronization delete plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-delete.default-behavior.alias.synopsis=The order in which post-synchronization delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-modify.synopsis=Specifies the order in which post-synchronization modify plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-modify.default-behavior.alias.synopsis=The order in which post-synchronization modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-post-synchronization-modify-dn.synopsis=Specifies the order in which post-synchronization modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-post-synchronization-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-post-synchronization-modify-dn.default-behavior.alias.synopsis=The order in which post-synchronization modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-add.synopsis=Specifies the order in which pre-operation add plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-add.default-behavior.alias.synopsis=The order in which pre-operation add plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-bind.synopsis=Specifies the order in which pre-operation bind plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-bind.default-behavior.alias.synopsis=The order in which pre-operation bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-compare.synopsis=Specifies the order in which pre-operation compare plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-compare.default-behavior.alias.synopsis=The order in which pre-operation compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-delete.synopsis=Specifies the order in which pre-operation delete plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-delete.default-behavior.alias.synopsis=The order in which pre-operation delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-extended.synopsis=Specifies the order in which pre-operation extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-extended.default-behavior.alias.synopsis=The order in which pre-operation extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-modify.synopsis=Specifies the order in which pre-operation modify plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-modify.default-behavior.alias.synopsis=The order in which pre-operation modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-modify-dn.synopsis=Specifies the order in which pre-operation modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-modify-dn.default-behavior.alias.synopsis=The order in which pre-operation modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-operation-search.synopsis=Specifies the order in which pre-operation search plug-ins are to be loaded and invoked.
+property.plugin-order-pre-operation-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-operation-search.default-behavior.alias.synopsis=The order in which pre-operation searc plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-abandon.synopsis=Specifies the order in which pre-parse abandon plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-abandon.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-abandon.default-behavior.alias.synopsis=The order in which pre-parse abandon plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-add.synopsis=Specifies the order in which pre-parse add plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-add.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-add.default-behavior.alias.synopsis=The order in which pre-parse add plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-bind.synopsis=Specifies the order in which pre-parse bind plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-bind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-bind.default-behavior.alias.synopsis=The order in which pre-parse bind plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-compare.synopsis=Specifies the order in which pre-parse compare plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-compare.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-compare.default-behavior.alias.synopsis=The order in which pre-parse compare plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-delete.synopsis=Specifies the order in which pre-parse delete plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-delete.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-delete.default-behavior.alias.synopsis=The order in which pre-parse delete plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-extended.synopsis=Specifies the order in which pre-parse extended operation plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-extended.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-extended.default-behavior.alias.synopsis=The order in which pre-parse extended operation plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-modify.synopsis=Specifies the order in which pre-parse modify plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-modify.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-modify.default-behavior.alias.synopsis=The order in which pre-parse modify plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-modify-dn.synopsis=Specifies the order in which pre-parse modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-modify-dn.default-behavior.alias.synopsis=The order in which pre-parse modify DN plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-search.synopsis=Specifies the order in which pre-parse search plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-search.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-search.default-behavior.alias.synopsis=The order in which pre-parse search plug-ins are loaded and invoked is undefined.
+property.plugin-order-pre-parse-unbind.synopsis=Specifies the order in which pre-parse unbind plug-ins are to be loaded and invoked.
+property.plugin-order-pre-parse-unbind.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-pre-parse-unbind.default-behavior.alias.synopsis=The order in which pre-parse unbind plug-ins are loaded and invoked is undefined.
+property.plugin-order-search-result-entry.synopsis=Specifies the order in which search result entry plug-ins are to be loaded and invoked.
+property.plugin-order-search-result-entry.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-search-result-entry.default-behavior.alias.synopsis=The order in which search result entry plug-ins are loaded and invoked is undefined.
+property.plugin-order-search-result-reference.synopsis=Specifies the order in which search result reference plug-ins are to be loaded and invoked.
+property.plugin-order-search-result-reference.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-search-result-reference.default-behavior.alias.synopsis=The order in which search result reference plug-ins are loaded and invoked is undefined.
+property.plugin-order-shutdown.synopsis=Specifies the order in which shutdown plug-ins are to be loaded and invoked.
+property.plugin-order-shutdown.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-shutdown.default-behavior.alias.synopsis=The order in which shutdown plug-ins are loaded and invoked is undefined.
+property.plugin-order-startup.synopsis=Specifies the order in which startup plug-ins are to be loaded and invoked.
+property.plugin-order-startup.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-startup.default-behavior.alias.synopsis=The order in which startup plug-ins are loaded and invoked is undefined.
+property.plugin-order-subordinate-modify-dn.synopsis=Specifies the order in which subordinate modify DN plug-ins are to be loaded and invoked.
+property.plugin-order-subordinate-modify-dn.description=The value is a comma-delimited list of plug-in names (where the plug-in name is the RDN value from the plug-in configuration entry DN). The list can include at most one asterisk to indicate the position of any unspecified plug-in (and the relative order of those unspecified plug-ins is undefined).
+property.plugin-order-subordinate-modify-dn.default-behavior.alias.synopsis=The order in which subordinate modify DN plug-ins are loaded and invoked is undefined.
+relation.plugin.user-friendly-name=Plugin
+relation.plugin.user-friendly-plural-name=Plugins
+relation.plugin.synopsis=Plugins provide a mechanism for executing custom code at specified points in operation processing and in the course of other events like connection establishment and termination, server startup and shutdown, and LDIF import and export.
diff --git a/opends/src/admin/messages/ProfilerPluginCfgDefn.properties b/opends/src/admin/messages/ProfilerPluginCfgDefn.properties
new file mode 100644
index 0000000..08406af
--- /dev/null
+++ b/opends/src/admin/messages/ProfilerPluginCfgDefn.properties
@@ -0,0 +1,72 @@
+user-friendly-name=Profiler Plugin
+user-friendly-plural-name=Profiler Plugins
+synopsis=The Profiler plug-in captures profiling information about operations performed inside the JVM while the Directory Server is running.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.enable-profiling-on-startup.synopsis=Indicates whether the profiler plug-in is to start collecting data automatically when the Directory Server is started.
+property.enable-profiling-on-startup.description=This property is read only when the server is started, and any changes take effect on the next restart. This property is typically set to "false" unless startup profiling is required, because otherwise the volume of data that can be collected can cause the server to run out of memory if it is not turned off in a timely manner.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
+property.profile-action.synopsis=Specifies the action that should be taken by the profiler.
+property.profile-action.description=A value of "start" causes the profiler thread to start collecting data if it is not already active. A value of "stop" causes the profiler thread to stop collecting data and write it to disk, and a value of "cancel" causes the profiler thread to stop collecting data and discard anything that has been captured. These operations occur immediately.
+property.profile-action.syntax.enumeration.value.cancel.synopsis=Stop collecting profile data and discard what has been captured.
+property.profile-action.syntax.enumeration.value.none.synopsis=Do not take any action.
+property.profile-action.syntax.enumeration.value.start.synopsis=Start collecting profile data.
+property.profile-action.syntax.enumeration.value.stop.synopsis=Stop collecting profile data and write what has been captured to a file in the profile directory.
+property.profile-directory.synopsis=Specifies the path to the directory where profile information is to be written. This path may be either an absolute path or a path that is relative to the root of the OpenDS Directory Server instance.
+property.profile-directory.description=The directory must exist and the Directory Server must have permission to create new files in it.
+property.profile-directory.syntax.string.pattern.synopsis=The path to any directory that exists on the filesystem and that can be read and written by the server user.
+property.profile-sample-interval.synopsis=Specifies the sample interval in milliseconds to be used when capturing profiling information in the server.
+property.profile-sample-interval.description=When capturing data, the profiler thread sleeps for this length of time between calls to obtain traces for all threads running in the JVM.
+property.profile-sample-interval.requires-admin-action.synopsis=Changes to this configuration attribute take effect the next time the profiler is started.
diff --git a/opends/src/admin/messages/ProfilerPluginCfgDefn_de.properties b/opends/src/admin/messages/ProfilerPluginCfgDefn_de.properties
new file mode 100644
index 0000000..08406af
--- /dev/null
+++ b/opends/src/admin/messages/ProfilerPluginCfgDefn_de.properties
@@ -0,0 +1,72 @@
+user-friendly-name=Profiler Plugin
+user-friendly-plural-name=Profiler Plugins
+synopsis=The Profiler plug-in captures profiling information about operations performed inside the JVM while the Directory Server is running.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.enable-profiling-on-startup.synopsis=Indicates whether the profiler plug-in is to start collecting data automatically when the Directory Server is started.
+property.enable-profiling-on-startup.description=This property is read only when the server is started, and any changes take effect on the next restart. This property is typically set to "false" unless startup profiling is required, because otherwise the volume of data that can be collected can cause the server to run out of memory if it is not turned off in a timely manner.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
+property.profile-action.synopsis=Specifies the action that should be taken by the profiler.
+property.profile-action.description=A value of "start" causes the profiler thread to start collecting data if it is not already active. A value of "stop" causes the profiler thread to stop collecting data and write it to disk, and a value of "cancel" causes the profiler thread to stop collecting data and discard anything that has been captured. These operations occur immediately.
+property.profile-action.syntax.enumeration.value.cancel.synopsis=Stop collecting profile data and discard what has been captured.
+property.profile-action.syntax.enumeration.value.none.synopsis=Do not take any action.
+property.profile-action.syntax.enumeration.value.start.synopsis=Start collecting profile data.
+property.profile-action.syntax.enumeration.value.stop.synopsis=Stop collecting profile data and write what has been captured to a file in the profile directory.
+property.profile-directory.synopsis=Specifies the path to the directory where profile information is to be written. This path may be either an absolute path or a path that is relative to the root of the OpenDS Directory Server instance.
+property.profile-directory.description=The directory must exist and the Directory Server must have permission to create new files in it.
+property.profile-directory.syntax.string.pattern.synopsis=The path to any directory that exists on the filesystem and that can be read and written by the server user.
+property.profile-sample-interval.synopsis=Specifies the sample interval in milliseconds to be used when capturing profiling information in the server.
+property.profile-sample-interval.description=When capturing data, the profiler thread sleeps for this length of time between calls to obtain traces for all threads running in the JVM.
+property.profile-sample-interval.requires-admin-action.synopsis=Changes to this configuration attribute take effect the next time the profiler is started.
diff --git a/opends/src/admin/messages/ProfilerPluginCfgDefn_es.properties b/opends/src/admin/messages/ProfilerPluginCfgDefn_es.properties
new file mode 100644
index 0000000..08406af
--- /dev/null
+++ b/opends/src/admin/messages/ProfilerPluginCfgDefn_es.properties
@@ -0,0 +1,72 @@
+user-friendly-name=Profiler Plugin
+user-friendly-plural-name=Profiler Plugins
+synopsis=The Profiler plug-in captures profiling information about operations performed inside the JVM while the Directory Server is running.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.enable-profiling-on-startup.synopsis=Indicates whether the profiler plug-in is to start collecting data automatically when the Directory Server is started.
+property.enable-profiling-on-startup.description=This property is read only when the server is started, and any changes take effect on the next restart. This property is typically set to "false" unless startup profiling is required, because otherwise the volume of data that can be collected can cause the server to run out of memory if it is not turned off in a timely manner.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
+property.profile-action.synopsis=Specifies the action that should be taken by the profiler.
+property.profile-action.description=A value of "start" causes the profiler thread to start collecting data if it is not already active. A value of "stop" causes the profiler thread to stop collecting data and write it to disk, and a value of "cancel" causes the profiler thread to stop collecting data and discard anything that has been captured. These operations occur immediately.
+property.profile-action.syntax.enumeration.value.cancel.synopsis=Stop collecting profile data and discard what has been captured.
+property.profile-action.syntax.enumeration.value.none.synopsis=Do not take any action.
+property.profile-action.syntax.enumeration.value.start.synopsis=Start collecting profile data.
+property.profile-action.syntax.enumeration.value.stop.synopsis=Stop collecting profile data and write what has been captured to a file in the profile directory.
+property.profile-directory.synopsis=Specifies the path to the directory where profile information is to be written. This path may be either an absolute path or a path that is relative to the root of the OpenDS Directory Server instance.
+property.profile-directory.description=The directory must exist and the Directory Server must have permission to create new files in it.
+property.profile-directory.syntax.string.pattern.synopsis=The path to any directory that exists on the filesystem and that can be read and written by the server user.
+property.profile-sample-interval.synopsis=Specifies the sample interval in milliseconds to be used when capturing profiling information in the server.
+property.profile-sample-interval.description=When capturing data, the profiler thread sleeps for this length of time between calls to obtain traces for all threads running in the JVM.
+property.profile-sample-interval.requires-admin-action.synopsis=Changes to this configuration attribute take effect the next time the profiler is started.
diff --git a/opends/src/admin/messages/ProfilerPluginCfgDefn_fr.properties b/opends/src/admin/messages/ProfilerPluginCfgDefn_fr.properties
new file mode 100644
index 0000000..08406af
--- /dev/null
+++ b/opends/src/admin/messages/ProfilerPluginCfgDefn_fr.properties
@@ -0,0 +1,72 @@
+user-friendly-name=Profiler Plugin
+user-friendly-plural-name=Profiler Plugins
+synopsis=The Profiler plug-in captures profiling information about operations performed inside the JVM while the Directory Server is running.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.enable-profiling-on-startup.synopsis=Indicates whether the profiler plug-in is to start collecting data automatically when the Directory Server is started.
+property.enable-profiling-on-startup.description=This property is read only when the server is started, and any changes take effect on the next restart. This property is typically set to "false" unless startup profiling is required, because otherwise the volume of data that can be collected can cause the server to run out of memory if it is not turned off in a timely manner.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
+property.profile-action.synopsis=Specifies the action that should be taken by the profiler.
+property.profile-action.description=A value of "start" causes the profiler thread to start collecting data if it is not already active. A value of "stop" causes the profiler thread to stop collecting data and write it to disk, and a value of "cancel" causes the profiler thread to stop collecting data and discard anything that has been captured. These operations occur immediately.
+property.profile-action.syntax.enumeration.value.cancel.synopsis=Stop collecting profile data and discard what has been captured.
+property.profile-action.syntax.enumeration.value.none.synopsis=Do not take any action.
+property.profile-action.syntax.enumeration.value.start.synopsis=Start collecting profile data.
+property.profile-action.syntax.enumeration.value.stop.synopsis=Stop collecting profile data and write what has been captured to a file in the profile directory.
+property.profile-directory.synopsis=Specifies the path to the directory where profile information is to be written. This path may be either an absolute path or a path that is relative to the root of the OpenDS Directory Server instance.
+property.profile-directory.description=The directory must exist and the Directory Server must have permission to create new files in it.
+property.profile-directory.syntax.string.pattern.synopsis=The path to any directory that exists on the filesystem and that can be read and written by the server user.
+property.profile-sample-interval.synopsis=Specifies the sample interval in milliseconds to be used when capturing profiling information in the server.
+property.profile-sample-interval.description=When capturing data, the profiler thread sleeps for this length of time between calls to obtain traces for all threads running in the JVM.
+property.profile-sample-interval.requires-admin-action.synopsis=Changes to this configuration attribute take effect the next time the profiler is started.
diff --git a/opends/src/admin/messages/ProfilerPluginCfgDefn_ja.properties b/opends/src/admin/messages/ProfilerPluginCfgDefn_ja.properties
new file mode 100644
index 0000000..08406af
--- /dev/null
+++ b/opends/src/admin/messages/ProfilerPluginCfgDefn_ja.properties
@@ -0,0 +1,72 @@
+user-friendly-name=Profiler Plugin
+user-friendly-plural-name=Profiler Plugins
+synopsis=The Profiler plug-in captures profiling information about operations performed inside the JVM while the Directory Server is running.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.enable-profiling-on-startup.synopsis=Indicates whether the profiler plug-in is to start collecting data automatically when the Directory Server is started.
+property.enable-profiling-on-startup.description=This property is read only when the server is started, and any changes take effect on the next restart. This property is typically set to "false" unless startup profiling is required, because otherwise the volume of data that can be collected can cause the server to run out of memory if it is not turned off in a timely manner.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
+property.profile-action.synopsis=Specifies the action that should be taken by the profiler.
+property.profile-action.description=A value of "start" causes the profiler thread to start collecting data if it is not already active. A value of "stop" causes the profiler thread to stop collecting data and write it to disk, and a value of "cancel" causes the profiler thread to stop collecting data and discard anything that has been captured. These operations occur immediately.
+property.profile-action.syntax.enumeration.value.cancel.synopsis=Stop collecting profile data and discard what has been captured.
+property.profile-action.syntax.enumeration.value.none.synopsis=Do not take any action.
+property.profile-action.syntax.enumeration.value.start.synopsis=Start collecting profile data.
+property.profile-action.syntax.enumeration.value.stop.synopsis=Stop collecting profile data and write what has been captured to a file in the profile directory.
+property.profile-directory.synopsis=Specifies the path to the directory where profile information is to be written. This path may be either an absolute path or a path that is relative to the root of the OpenDS Directory Server instance.
+property.profile-directory.description=The directory must exist and the Directory Server must have permission to create new files in it.
+property.profile-directory.syntax.string.pattern.synopsis=The path to any directory that exists on the filesystem and that can be read and written by the server user.
+property.profile-sample-interval.synopsis=Specifies the sample interval in milliseconds to be used when capturing profiling information in the server.
+property.profile-sample-interval.description=When capturing data, the profiler thread sleeps for this length of time between calls to obtain traces for all threads running in the JVM.
+property.profile-sample-interval.requires-admin-action.synopsis=Changes to this configuration attribute take effect the next time the profiler is started.
diff --git a/opends/src/admin/messages/ProfilerPluginCfgDefn_ko.properties b/opends/src/admin/messages/ProfilerPluginCfgDefn_ko.properties
new file mode 100644
index 0000000..08406af
--- /dev/null
+++ b/opends/src/admin/messages/ProfilerPluginCfgDefn_ko.properties
@@ -0,0 +1,72 @@
+user-friendly-name=Profiler Plugin
+user-friendly-plural-name=Profiler Plugins
+synopsis=The Profiler plug-in captures profiling information about operations performed inside the JVM while the Directory Server is running.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.enable-profiling-on-startup.synopsis=Indicates whether the profiler plug-in is to start collecting data automatically when the Directory Server is started.
+property.enable-profiling-on-startup.description=This property is read only when the server is started, and any changes take effect on the next restart. This property is typically set to "false" unless startup profiling is required, because otherwise the volume of data that can be collected can cause the server to run out of memory if it is not turned off in a timely manner.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
+property.profile-action.synopsis=Specifies the action that should be taken by the profiler.
+property.profile-action.description=A value of "start" causes the profiler thread to start collecting data if it is not already active. A value of "stop" causes the profiler thread to stop collecting data and write it to disk, and a value of "cancel" causes the profiler thread to stop collecting data and discard anything that has been captured. These operations occur immediately.
+property.profile-action.syntax.enumeration.value.cancel.synopsis=Stop collecting profile data and discard what has been captured.
+property.profile-action.syntax.enumeration.value.none.synopsis=Do not take any action.
+property.profile-action.syntax.enumeration.value.start.synopsis=Start collecting profile data.
+property.profile-action.syntax.enumeration.value.stop.synopsis=Stop collecting profile data and write what has been captured to a file in the profile directory.
+property.profile-directory.synopsis=Specifies the path to the directory where profile information is to be written. This path may be either an absolute path or a path that is relative to the root of the OpenDS Directory Server instance.
+property.profile-directory.description=The directory must exist and the Directory Server must have permission to create new files in it.
+property.profile-directory.syntax.string.pattern.synopsis=The path to any directory that exists on the filesystem and that can be read and written by the server user.
+property.profile-sample-interval.synopsis=Specifies the sample interval in milliseconds to be used when capturing profiling information in the server.
+property.profile-sample-interval.description=When capturing data, the profiler thread sleeps for this length of time between calls to obtain traces for all threads running in the JVM.
+property.profile-sample-interval.requires-admin-action.synopsis=Changes to this configuration attribute take effect the next time the profiler is started.
diff --git a/opends/src/admin/messages/ProfilerPluginCfgDefn_zh_CN.properties b/opends/src/admin/messages/ProfilerPluginCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..08406af
--- /dev/null
+++ b/opends/src/admin/messages/ProfilerPluginCfgDefn_zh_CN.properties
@@ -0,0 +1,72 @@
+user-friendly-name=Profiler Plugin
+user-friendly-plural-name=Profiler Plugins
+synopsis=The Profiler plug-in captures profiling information about operations performed inside the JVM while the Directory Server is running.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.enable-profiling-on-startup.synopsis=Indicates whether the profiler plug-in is to start collecting data automatically when the Directory Server is started.
+property.enable-profiling-on-startup.description=This property is read only when the server is started, and any changes take effect on the next restart. This property is typically set to "false" unless startup profiling is required, because otherwise the volume of data that can be collected can cause the server to run out of memory if it is not turned off in a timely manner.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
+property.profile-action.synopsis=Specifies the action that should be taken by the profiler.
+property.profile-action.description=A value of "start" causes the profiler thread to start collecting data if it is not already active. A value of "stop" causes the profiler thread to stop collecting data and write it to disk, and a value of "cancel" causes the profiler thread to stop collecting data and discard anything that has been captured. These operations occur immediately.
+property.profile-action.syntax.enumeration.value.cancel.synopsis=Stop collecting profile data and discard what has been captured.
+property.profile-action.syntax.enumeration.value.none.synopsis=Do not take any action.
+property.profile-action.syntax.enumeration.value.start.synopsis=Start collecting profile data.
+property.profile-action.syntax.enumeration.value.stop.synopsis=Stop collecting profile data and write what has been captured to a file in the profile directory.
+property.profile-directory.synopsis=Specifies the path to the directory where profile information is to be written. This path may be either an absolute path or a path that is relative to the root of the OpenDS Directory Server instance.
+property.profile-directory.description=The directory must exist and the Directory Server must have permission to create new files in it.
+property.profile-directory.syntax.string.pattern.synopsis=The path to any directory that exists on the filesystem and that can be read and written by the server user.
+property.profile-sample-interval.synopsis=Specifies the sample interval in milliseconds to be used when capturing profiling information in the server.
+property.profile-sample-interval.description=When capturing data, the profiler thread sleeps for this length of time between calls to obtain traces for all threads running in the JVM.
+property.profile-sample-interval.requires-admin-action.synopsis=Changes to this configuration attribute take effect the next time the profiler is started.
diff --git a/opends/src/admin/messages/ProfilerPluginCfgDefn_zh_TW.properties b/opends/src/admin/messages/ProfilerPluginCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..08406af
--- /dev/null
+++ b/opends/src/admin/messages/ProfilerPluginCfgDefn_zh_TW.properties
@@ -0,0 +1,72 @@
+user-friendly-name=Profiler Plugin
+user-friendly-plural-name=Profiler Plugins
+synopsis=The Profiler plug-in captures profiling information about operations performed inside the JVM while the Directory Server is running.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.enable-profiling-on-startup.synopsis=Indicates whether the profiler plug-in is to start collecting data automatically when the Directory Server is started.
+property.enable-profiling-on-startup.description=This property is read only when the server is started, and any changes take effect on the next restart. This property is typically set to "false" unless startup profiling is required, because otherwise the volume of data that can be collected can cause the server to run out of memory if it is not turned off in a timely manner.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
+property.profile-action.synopsis=Specifies the action that should be taken by the profiler.
+property.profile-action.description=A value of "start" causes the profiler thread to start collecting data if it is not already active. A value of "stop" causes the profiler thread to stop collecting data and write it to disk, and a value of "cancel" causes the profiler thread to stop collecting data and discard anything that has been captured. These operations occur immediately.
+property.profile-action.syntax.enumeration.value.cancel.synopsis=Stop collecting profile data and discard what has been captured.
+property.profile-action.syntax.enumeration.value.none.synopsis=Do not take any action.
+property.profile-action.syntax.enumeration.value.start.synopsis=Start collecting profile data.
+property.profile-action.syntax.enumeration.value.stop.synopsis=Stop collecting profile data and write what has been captured to a file in the profile directory.
+property.profile-directory.synopsis=Specifies the path to the directory where profile information is to be written. This path may be either an absolute path or a path that is relative to the root of the OpenDS Directory Server instance.
+property.profile-directory.description=The directory must exist and the Directory Server must have permission to create new files in it.
+property.profile-directory.syntax.string.pattern.synopsis=The path to any directory that exists on the filesystem and that can be read and written by the server user.
+property.profile-sample-interval.synopsis=Specifies the sample interval in milliseconds to be used when capturing profiling information in the server.
+property.profile-sample-interval.description=When capturing data, the profiler thread sleeps for this length of time between calls to obtain traces for all threads running in the JVM.
+property.profile-sample-interval.requires-admin-action.synopsis=Changes to this configuration attribute take effect the next time the profiler is started.
diff --git a/opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn.properties b/opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn.properties
new file mode 100644
index 0000000..ca43678
--- /dev/null
+++ b/opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=RC4 Password Storage Scheme
+user-friendly-plural-name=RC4 Password Storage Schemes
+synopsis=The RC4 Password Storage Scheme provides a mechanism for encoding user passwords using the RC4 reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "RC4".
+property.enabled.synopsis=Indicates whether the RC4 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the RC4 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_de.properties b/opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_de.properties
new file mode 100644
index 0000000..ca43678
--- /dev/null
+++ b/opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=RC4 Password Storage Scheme
+user-friendly-plural-name=RC4 Password Storage Schemes
+synopsis=The RC4 Password Storage Scheme provides a mechanism for encoding user passwords using the RC4 reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "RC4".
+property.enabled.synopsis=Indicates whether the RC4 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the RC4 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_es.properties b/opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_es.properties
new file mode 100644
index 0000000..ca43678
--- /dev/null
+++ b/opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=RC4 Password Storage Scheme
+user-friendly-plural-name=RC4 Password Storage Schemes
+synopsis=The RC4 Password Storage Scheme provides a mechanism for encoding user passwords using the RC4 reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "RC4".
+property.enabled.synopsis=Indicates whether the RC4 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the RC4 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_fr.properties b/opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_fr.properties
new file mode 100644
index 0000000..ca43678
--- /dev/null
+++ b/opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=RC4 Password Storage Scheme
+user-friendly-plural-name=RC4 Password Storage Schemes
+synopsis=The RC4 Password Storage Scheme provides a mechanism for encoding user passwords using the RC4 reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "RC4".
+property.enabled.synopsis=Indicates whether the RC4 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the RC4 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_ja.properties b/opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_ja.properties
new file mode 100644
index 0000000..ca43678
--- /dev/null
+++ b/opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=RC4 Password Storage Scheme
+user-friendly-plural-name=RC4 Password Storage Schemes
+synopsis=The RC4 Password Storage Scheme provides a mechanism for encoding user passwords using the RC4 reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "RC4".
+property.enabled.synopsis=Indicates whether the RC4 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the RC4 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_ko.properties b/opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_ko.properties
new file mode 100644
index 0000000..ca43678
--- /dev/null
+++ b/opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=RC4 Password Storage Scheme
+user-friendly-plural-name=RC4 Password Storage Schemes
+synopsis=The RC4 Password Storage Scheme provides a mechanism for encoding user passwords using the RC4 reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "RC4".
+property.enabled.synopsis=Indicates whether the RC4 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the RC4 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_zh_CN.properties b/opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..ca43678
--- /dev/null
+++ b/opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=RC4 Password Storage Scheme
+user-friendly-plural-name=RC4 Password Storage Schemes
+synopsis=The RC4 Password Storage Scheme provides a mechanism for encoding user passwords using the RC4 reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "RC4".
+property.enabled.synopsis=Indicates whether the RC4 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the RC4 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_zh_TW.properties b/opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..ca43678
--- /dev/null
+++ b/opends/src/admin/messages/RC4PasswordStorageSchemeCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=RC4 Password Storage Scheme
+user-friendly-plural-name=RC4 Password Storage Schemes
+synopsis=The RC4 Password Storage Scheme provides a mechanism for encoding user passwords using the RC4 reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "RC4".
+property.enabled.synopsis=Indicates whether the RC4 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the RC4 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/RandomPasswordGeneratorCfgDefn.properties b/opends/src/admin/messages/RandomPasswordGeneratorCfgDefn.properties
new file mode 100644
index 0000000..89331c9
--- /dev/null
+++ b/opends/src/admin/messages/RandomPasswordGeneratorCfgDefn.properties
@@ -0,0 +1,11 @@
+user-friendly-name=Random Password Generator
+user-friendly-plural-name=Random Password Generators
+synopsis=The Random Password Generator creates random passwords based on fixed-length strings built from one or more character sets.
+property.enabled.synopsis=Indicates whether the Random Password Generator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Random Password Generator implementation.
+property.password-character-set.synopsis=Specifies one or more named character sets.
+property.password-character-set.description=This is a multi-valued property, with each value defining a different character set. The format of the character set is the name of the set followed by a colon and the characters that are in that set. For example, the value "alpha:abcdefghijklmnopqrstuvwxyz" defines a character set named "alpha" containing all of the lower-case ASCII alphabetic characters.
+property.password-character-set.syntax.string.pattern.synopsis=A character set name (consisting of ASCII letters) followed by a colon and the set of characters that are included in that character set.
+property.password-format.synopsis=Specifies the format to use for the generated password.
+property.password-format.description=The value is a comma-delimited list of elements in which each of those elements is comprised of the name of a character set defined in the password-character-set property, a colon, and the number of characters to include from that set. For example, a value of "alpha:3,numeric:2,alpha:3" generates an 8-character password in which the first three characters are from the "alpha" set, the next two are from the "numeric" set, and the final three are from the "alpha" set.
+property.password-format.syntax.string.pattern.synopsis=A comma-delimited list whose elements comprise a valid character set name, a colon, and a positive integer indicating the number of characters from that set to be included.
diff --git a/opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_de.properties b/opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_de.properties
new file mode 100644
index 0000000..89331c9
--- /dev/null
+++ b/opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_de.properties
@@ -0,0 +1,11 @@
+user-friendly-name=Random Password Generator
+user-friendly-plural-name=Random Password Generators
+synopsis=The Random Password Generator creates random passwords based on fixed-length strings built from one or more character sets.
+property.enabled.synopsis=Indicates whether the Random Password Generator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Random Password Generator implementation.
+property.password-character-set.synopsis=Specifies one or more named character sets.
+property.password-character-set.description=This is a multi-valued property, with each value defining a different character set. The format of the character set is the name of the set followed by a colon and the characters that are in that set. For example, the value "alpha:abcdefghijklmnopqrstuvwxyz" defines a character set named "alpha" containing all of the lower-case ASCII alphabetic characters.
+property.password-character-set.syntax.string.pattern.synopsis=A character set name (consisting of ASCII letters) followed by a colon and the set of characters that are included in that character set.
+property.password-format.synopsis=Specifies the format to use for the generated password.
+property.password-format.description=The value is a comma-delimited list of elements in which each of those elements is comprised of the name of a character set defined in the password-character-set property, a colon, and the number of characters to include from that set. For example, a value of "alpha:3,numeric:2,alpha:3" generates an 8-character password in which the first three characters are from the "alpha" set, the next two are from the "numeric" set, and the final three are from the "alpha" set.
+property.password-format.syntax.string.pattern.synopsis=A comma-delimited list whose elements comprise a valid character set name, a colon, and a positive integer indicating the number of characters from that set to be included.
diff --git a/opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_es.properties b/opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_es.properties
new file mode 100644
index 0000000..89331c9
--- /dev/null
+++ b/opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_es.properties
@@ -0,0 +1,11 @@
+user-friendly-name=Random Password Generator
+user-friendly-plural-name=Random Password Generators
+synopsis=The Random Password Generator creates random passwords based on fixed-length strings built from one or more character sets.
+property.enabled.synopsis=Indicates whether the Random Password Generator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Random Password Generator implementation.
+property.password-character-set.synopsis=Specifies one or more named character sets.
+property.password-character-set.description=This is a multi-valued property, with each value defining a different character set. The format of the character set is the name of the set followed by a colon and the characters that are in that set. For example, the value "alpha:abcdefghijklmnopqrstuvwxyz" defines a character set named "alpha" containing all of the lower-case ASCII alphabetic characters.
+property.password-character-set.syntax.string.pattern.synopsis=A character set name (consisting of ASCII letters) followed by a colon and the set of characters that are included in that character set.
+property.password-format.synopsis=Specifies the format to use for the generated password.
+property.password-format.description=The value is a comma-delimited list of elements in which each of those elements is comprised of the name of a character set defined in the password-character-set property, a colon, and the number of characters to include from that set. For example, a value of "alpha:3,numeric:2,alpha:3" generates an 8-character password in which the first three characters are from the "alpha" set, the next two are from the "numeric" set, and the final three are from the "alpha" set.
+property.password-format.syntax.string.pattern.synopsis=A comma-delimited list whose elements comprise a valid character set name, a colon, and a positive integer indicating the number of characters from that set to be included.
diff --git a/opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_fr.properties b/opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_fr.properties
new file mode 100644
index 0000000..89331c9
--- /dev/null
+++ b/opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_fr.properties
@@ -0,0 +1,11 @@
+user-friendly-name=Random Password Generator
+user-friendly-plural-name=Random Password Generators
+synopsis=The Random Password Generator creates random passwords based on fixed-length strings built from one or more character sets.
+property.enabled.synopsis=Indicates whether the Random Password Generator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Random Password Generator implementation.
+property.password-character-set.synopsis=Specifies one or more named character sets.
+property.password-character-set.description=This is a multi-valued property, with each value defining a different character set. The format of the character set is the name of the set followed by a colon and the characters that are in that set. For example, the value "alpha:abcdefghijklmnopqrstuvwxyz" defines a character set named "alpha" containing all of the lower-case ASCII alphabetic characters.
+property.password-character-set.syntax.string.pattern.synopsis=A character set name (consisting of ASCII letters) followed by a colon and the set of characters that are included in that character set.
+property.password-format.synopsis=Specifies the format to use for the generated password.
+property.password-format.description=The value is a comma-delimited list of elements in which each of those elements is comprised of the name of a character set defined in the password-character-set property, a colon, and the number of characters to include from that set. For example, a value of "alpha:3,numeric:2,alpha:3" generates an 8-character password in which the first three characters are from the "alpha" set, the next two are from the "numeric" set, and the final three are from the "alpha" set.
+property.password-format.syntax.string.pattern.synopsis=A comma-delimited list whose elements comprise a valid character set name, a colon, and a positive integer indicating the number of characters from that set to be included.
diff --git a/opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_ja.properties b/opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_ja.properties
new file mode 100644
index 0000000..89331c9
--- /dev/null
+++ b/opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_ja.properties
@@ -0,0 +1,11 @@
+user-friendly-name=Random Password Generator
+user-friendly-plural-name=Random Password Generators
+synopsis=The Random Password Generator creates random passwords based on fixed-length strings built from one or more character sets.
+property.enabled.synopsis=Indicates whether the Random Password Generator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Random Password Generator implementation.
+property.password-character-set.synopsis=Specifies one or more named character sets.
+property.password-character-set.description=This is a multi-valued property, with each value defining a different character set. The format of the character set is the name of the set followed by a colon and the characters that are in that set. For example, the value "alpha:abcdefghijklmnopqrstuvwxyz" defines a character set named "alpha" containing all of the lower-case ASCII alphabetic characters.
+property.password-character-set.syntax.string.pattern.synopsis=A character set name (consisting of ASCII letters) followed by a colon and the set of characters that are included in that character set.
+property.password-format.synopsis=Specifies the format to use for the generated password.
+property.password-format.description=The value is a comma-delimited list of elements in which each of those elements is comprised of the name of a character set defined in the password-character-set property, a colon, and the number of characters to include from that set. For example, a value of "alpha:3,numeric:2,alpha:3" generates an 8-character password in which the first three characters are from the "alpha" set, the next two are from the "numeric" set, and the final three are from the "alpha" set.
+property.password-format.syntax.string.pattern.synopsis=A comma-delimited list whose elements comprise a valid character set name, a colon, and a positive integer indicating the number of characters from that set to be included.
diff --git a/opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_ko.properties b/opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_ko.properties
new file mode 100644
index 0000000..89331c9
--- /dev/null
+++ b/opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_ko.properties
@@ -0,0 +1,11 @@
+user-friendly-name=Random Password Generator
+user-friendly-plural-name=Random Password Generators
+synopsis=The Random Password Generator creates random passwords based on fixed-length strings built from one or more character sets.
+property.enabled.synopsis=Indicates whether the Random Password Generator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Random Password Generator implementation.
+property.password-character-set.synopsis=Specifies one or more named character sets.
+property.password-character-set.description=This is a multi-valued property, with each value defining a different character set. The format of the character set is the name of the set followed by a colon and the characters that are in that set. For example, the value "alpha:abcdefghijklmnopqrstuvwxyz" defines a character set named "alpha" containing all of the lower-case ASCII alphabetic characters.
+property.password-character-set.syntax.string.pattern.synopsis=A character set name (consisting of ASCII letters) followed by a colon and the set of characters that are included in that character set.
+property.password-format.synopsis=Specifies the format to use for the generated password.
+property.password-format.description=The value is a comma-delimited list of elements in which each of those elements is comprised of the name of a character set defined in the password-character-set property, a colon, and the number of characters to include from that set. For example, a value of "alpha:3,numeric:2,alpha:3" generates an 8-character password in which the first three characters are from the "alpha" set, the next two are from the "numeric" set, and the final three are from the "alpha" set.
+property.password-format.syntax.string.pattern.synopsis=A comma-delimited list whose elements comprise a valid character set name, a colon, and a positive integer indicating the number of characters from that set to be included.
diff --git a/opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_zh_CN.properties b/opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..89331c9
--- /dev/null
+++ b/opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_zh_CN.properties
@@ -0,0 +1,11 @@
+user-friendly-name=Random Password Generator
+user-friendly-plural-name=Random Password Generators
+synopsis=The Random Password Generator creates random passwords based on fixed-length strings built from one or more character sets.
+property.enabled.synopsis=Indicates whether the Random Password Generator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Random Password Generator implementation.
+property.password-character-set.synopsis=Specifies one or more named character sets.
+property.password-character-set.description=This is a multi-valued property, with each value defining a different character set. The format of the character set is the name of the set followed by a colon and the characters that are in that set. For example, the value "alpha:abcdefghijklmnopqrstuvwxyz" defines a character set named "alpha" containing all of the lower-case ASCII alphabetic characters.
+property.password-character-set.syntax.string.pattern.synopsis=A character set name (consisting of ASCII letters) followed by a colon and the set of characters that are included in that character set.
+property.password-format.synopsis=Specifies the format to use for the generated password.
+property.password-format.description=The value is a comma-delimited list of elements in which each of those elements is comprised of the name of a character set defined in the password-character-set property, a colon, and the number of characters to include from that set. For example, a value of "alpha:3,numeric:2,alpha:3" generates an 8-character password in which the first three characters are from the "alpha" set, the next two are from the "numeric" set, and the final three are from the "alpha" set.
+property.password-format.syntax.string.pattern.synopsis=A comma-delimited list whose elements comprise a valid character set name, a colon, and a positive integer indicating the number of characters from that set to be included.
diff --git a/opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_zh_TW.properties b/opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..89331c9
--- /dev/null
+++ b/opends/src/admin/messages/RandomPasswordGeneratorCfgDefn_zh_TW.properties
@@ -0,0 +1,11 @@
+user-friendly-name=Random Password Generator
+user-friendly-plural-name=Random Password Generators
+synopsis=The Random Password Generator creates random passwords based on fixed-length strings built from one or more character sets.
+property.enabled.synopsis=Indicates whether the Random Password Generator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Random Password Generator implementation.
+property.password-character-set.synopsis=Specifies one or more named character sets.
+property.password-character-set.description=This is a multi-valued property, with each value defining a different character set. The format of the character set is the name of the set followed by a colon and the characters that are in that set. For example, the value "alpha:abcdefghijklmnopqrstuvwxyz" defines a character set named "alpha" containing all of the lower-case ASCII alphabetic characters.
+property.password-character-set.syntax.string.pattern.synopsis=A character set name (consisting of ASCII letters) followed by a colon and the set of characters that are included in that character set.
+property.password-format.synopsis=Specifies the format to use for the generated password.
+property.password-format.description=The value is a comma-delimited list of elements in which each of those elements is comprised of the name of a character set defined in the password-character-set property, a colon, and the number of characters to include from that set. For example, a value of "alpha:3,numeric:2,alpha:3" generates an 8-character password in which the first three characters are from the "alpha" set, the next two are from the "numeric" set, and the final three are from the "alpha" set.
+property.password-format.syntax.string.pattern.synopsis=A comma-delimited list whose elements comprise a valid character set name, a colon, and a positive integer indicating the number of characters from that set to be included.
diff --git a/opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn.properties b/opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn.properties
new file mode 100644
index 0000000..a9ad4c0
--- /dev/null
+++ b/opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn.properties
@@ -0,0 +1,68 @@
+user-friendly-name=Referential Integrity Plugin
+user-friendly-plural-name=Referential Integrity Plugins
+synopsis=The Referential Integrity Plugin maintains referential integrity for DN valued attributes.
+description=The values of these attributes can reference entries that have been deleted by a delete operation or renamed by a modify DN operation. The referential integrity plug-in either removes stale references to deleted entries or updates references to renamed entries. The plug-in allows the scope of this referential check to be limited to a set of base DNs if desired. The plug-in also can be configured to perform the referential checking in the background mode specified intervals.
+property.attribute-type.synopsis=Specifies the attribute types for which referential integrity is to be maintained.
+property.attribute-type.description=At least one attribute type must be specified, and the syntax of any attributes must be either a distinguished name (1.3.6.1.4.1.1466.115.121.1.12) or name and optional UID (1.3.6.1.4.1.1466.115.121.1.34).
+property.base-dn.synopsis=Specifies the base DN that limits the scope within which referential integrity is maintained.
+property.base-dn.default-behavior.alias.synopsis=Referential integrity is maintained in all public naming contexts.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.log-file.synopsis=Specifies the log file location where the update records are written when the plug-in is in background-mode processing.
+property.log-file.description=The default location is the logs directory of the server instance, using the file name "referint".
+property.log-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
+property.update-interval.synopsis=Specifies the interval in seconds when referential integrity updates are made.
+property.update-interval.description=If this value is 0, then the updates are made synchronously in the foreground.
diff --git a/opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_de.properties b/opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_de.properties
new file mode 100644
index 0000000..a9ad4c0
--- /dev/null
+++ b/opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_de.properties
@@ -0,0 +1,68 @@
+user-friendly-name=Referential Integrity Plugin
+user-friendly-plural-name=Referential Integrity Plugins
+synopsis=The Referential Integrity Plugin maintains referential integrity for DN valued attributes.
+description=The values of these attributes can reference entries that have been deleted by a delete operation or renamed by a modify DN operation. The referential integrity plug-in either removes stale references to deleted entries or updates references to renamed entries. The plug-in allows the scope of this referential check to be limited to a set of base DNs if desired. The plug-in also can be configured to perform the referential checking in the background mode specified intervals.
+property.attribute-type.synopsis=Specifies the attribute types for which referential integrity is to be maintained.
+property.attribute-type.description=At least one attribute type must be specified, and the syntax of any attributes must be either a distinguished name (1.3.6.1.4.1.1466.115.121.1.12) or name and optional UID (1.3.6.1.4.1.1466.115.121.1.34).
+property.base-dn.synopsis=Specifies the base DN that limits the scope within which referential integrity is maintained.
+property.base-dn.default-behavior.alias.synopsis=Referential integrity is maintained in all public naming contexts.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.log-file.synopsis=Specifies the log file location where the update records are written when the plug-in is in background-mode processing.
+property.log-file.description=The default location is the logs directory of the server instance, using the file name "referint".
+property.log-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
+property.update-interval.synopsis=Specifies the interval in seconds when referential integrity updates are made.
+property.update-interval.description=If this value is 0, then the updates are made synchronously in the foreground.
diff --git a/opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_es.properties b/opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_es.properties
new file mode 100644
index 0000000..a9ad4c0
--- /dev/null
+++ b/opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_es.properties
@@ -0,0 +1,68 @@
+user-friendly-name=Referential Integrity Plugin
+user-friendly-plural-name=Referential Integrity Plugins
+synopsis=The Referential Integrity Plugin maintains referential integrity for DN valued attributes.
+description=The values of these attributes can reference entries that have been deleted by a delete operation or renamed by a modify DN operation. The referential integrity plug-in either removes stale references to deleted entries or updates references to renamed entries. The plug-in allows the scope of this referential check to be limited to a set of base DNs if desired. The plug-in also can be configured to perform the referential checking in the background mode specified intervals.
+property.attribute-type.synopsis=Specifies the attribute types for which referential integrity is to be maintained.
+property.attribute-type.description=At least one attribute type must be specified, and the syntax of any attributes must be either a distinguished name (1.3.6.1.4.1.1466.115.121.1.12) or name and optional UID (1.3.6.1.4.1.1466.115.121.1.34).
+property.base-dn.synopsis=Specifies the base DN that limits the scope within which referential integrity is maintained.
+property.base-dn.default-behavior.alias.synopsis=Referential integrity is maintained in all public naming contexts.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.log-file.synopsis=Specifies the log file location where the update records are written when the plug-in is in background-mode processing.
+property.log-file.description=The default location is the logs directory of the server instance, using the file name "referint".
+property.log-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
+property.update-interval.synopsis=Specifies the interval in seconds when referential integrity updates are made.
+property.update-interval.description=If this value is 0, then the updates are made synchronously in the foreground.
diff --git a/opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_fr.properties b/opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_fr.properties
new file mode 100644
index 0000000..a9ad4c0
--- /dev/null
+++ b/opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_fr.properties
@@ -0,0 +1,68 @@
+user-friendly-name=Referential Integrity Plugin
+user-friendly-plural-name=Referential Integrity Plugins
+synopsis=The Referential Integrity Plugin maintains referential integrity for DN valued attributes.
+description=The values of these attributes can reference entries that have been deleted by a delete operation or renamed by a modify DN operation. The referential integrity plug-in either removes stale references to deleted entries or updates references to renamed entries. The plug-in allows the scope of this referential check to be limited to a set of base DNs if desired. The plug-in also can be configured to perform the referential checking in the background mode specified intervals.
+property.attribute-type.synopsis=Specifies the attribute types for which referential integrity is to be maintained.
+property.attribute-type.description=At least one attribute type must be specified, and the syntax of any attributes must be either a distinguished name (1.3.6.1.4.1.1466.115.121.1.12) or name and optional UID (1.3.6.1.4.1.1466.115.121.1.34).
+property.base-dn.synopsis=Specifies the base DN that limits the scope within which referential integrity is maintained.
+property.base-dn.default-behavior.alias.synopsis=Referential integrity is maintained in all public naming contexts.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.log-file.synopsis=Specifies the log file location where the update records are written when the plug-in is in background-mode processing.
+property.log-file.description=The default location is the logs directory of the server instance, using the file name "referint".
+property.log-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
+property.update-interval.synopsis=Specifies the interval in seconds when referential integrity updates are made.
+property.update-interval.description=If this value is 0, then the updates are made synchronously in the foreground.
diff --git a/opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_ja.properties b/opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_ja.properties
new file mode 100644
index 0000000..a9ad4c0
--- /dev/null
+++ b/opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_ja.properties
@@ -0,0 +1,68 @@
+user-friendly-name=Referential Integrity Plugin
+user-friendly-plural-name=Referential Integrity Plugins
+synopsis=The Referential Integrity Plugin maintains referential integrity for DN valued attributes.
+description=The values of these attributes can reference entries that have been deleted by a delete operation or renamed by a modify DN operation. The referential integrity plug-in either removes stale references to deleted entries or updates references to renamed entries. The plug-in allows the scope of this referential check to be limited to a set of base DNs if desired. The plug-in also can be configured to perform the referential checking in the background mode specified intervals.
+property.attribute-type.synopsis=Specifies the attribute types for which referential integrity is to be maintained.
+property.attribute-type.description=At least one attribute type must be specified, and the syntax of any attributes must be either a distinguished name (1.3.6.1.4.1.1466.115.121.1.12) or name and optional UID (1.3.6.1.4.1.1466.115.121.1.34).
+property.base-dn.synopsis=Specifies the base DN that limits the scope within which referential integrity is maintained.
+property.base-dn.default-behavior.alias.synopsis=Referential integrity is maintained in all public naming contexts.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.log-file.synopsis=Specifies the log file location where the update records are written when the plug-in is in background-mode processing.
+property.log-file.description=The default location is the logs directory of the server instance, using the file name "referint".
+property.log-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
+property.update-interval.synopsis=Specifies the interval in seconds when referential integrity updates are made.
+property.update-interval.description=If this value is 0, then the updates are made synchronously in the foreground.
diff --git a/opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_ko.properties b/opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_ko.properties
new file mode 100644
index 0000000..a9ad4c0
--- /dev/null
+++ b/opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_ko.properties
@@ -0,0 +1,68 @@
+user-friendly-name=Referential Integrity Plugin
+user-friendly-plural-name=Referential Integrity Plugins
+synopsis=The Referential Integrity Plugin maintains referential integrity for DN valued attributes.
+description=The values of these attributes can reference entries that have been deleted by a delete operation or renamed by a modify DN operation. The referential integrity plug-in either removes stale references to deleted entries or updates references to renamed entries. The plug-in allows the scope of this referential check to be limited to a set of base DNs if desired. The plug-in also can be configured to perform the referential checking in the background mode specified intervals.
+property.attribute-type.synopsis=Specifies the attribute types for which referential integrity is to be maintained.
+property.attribute-type.description=At least one attribute type must be specified, and the syntax of any attributes must be either a distinguished name (1.3.6.1.4.1.1466.115.121.1.12) or name and optional UID (1.3.6.1.4.1.1466.115.121.1.34).
+property.base-dn.synopsis=Specifies the base DN that limits the scope within which referential integrity is maintained.
+property.base-dn.default-behavior.alias.synopsis=Referential integrity is maintained in all public naming contexts.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.log-file.synopsis=Specifies the log file location where the update records are written when the plug-in is in background-mode processing.
+property.log-file.description=The default location is the logs directory of the server instance, using the file name "referint".
+property.log-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
+property.update-interval.synopsis=Specifies the interval in seconds when referential integrity updates are made.
+property.update-interval.description=If this value is 0, then the updates are made synchronously in the foreground.
diff --git a/opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_zh_CN.properties b/opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..a9ad4c0
--- /dev/null
+++ b/opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_zh_CN.properties
@@ -0,0 +1,68 @@
+user-friendly-name=Referential Integrity Plugin
+user-friendly-plural-name=Referential Integrity Plugins
+synopsis=The Referential Integrity Plugin maintains referential integrity for DN valued attributes.
+description=The values of these attributes can reference entries that have been deleted by a delete operation or renamed by a modify DN operation. The referential integrity plug-in either removes stale references to deleted entries or updates references to renamed entries. The plug-in allows the scope of this referential check to be limited to a set of base DNs if desired. The plug-in also can be configured to perform the referential checking in the background mode specified intervals.
+property.attribute-type.synopsis=Specifies the attribute types for which referential integrity is to be maintained.
+property.attribute-type.description=At least one attribute type must be specified, and the syntax of any attributes must be either a distinguished name (1.3.6.1.4.1.1466.115.121.1.12) or name and optional UID (1.3.6.1.4.1.1466.115.121.1.34).
+property.base-dn.synopsis=Specifies the base DN that limits the scope within which referential integrity is maintained.
+property.base-dn.default-behavior.alias.synopsis=Referential integrity is maintained in all public naming contexts.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.log-file.synopsis=Specifies the log file location where the update records are written when the plug-in is in background-mode processing.
+property.log-file.description=The default location is the logs directory of the server instance, using the file name "referint".
+property.log-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
+property.update-interval.synopsis=Specifies the interval in seconds when referential integrity updates are made.
+property.update-interval.description=If this value is 0, then the updates are made synchronously in the foreground.
diff --git a/opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_zh_TW.properties b/opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..a9ad4c0
--- /dev/null
+++ b/opends/src/admin/messages/ReferentialIntegrityPluginCfgDefn_zh_TW.properties
@@ -0,0 +1,68 @@
+user-friendly-name=Referential Integrity Plugin
+user-friendly-plural-name=Referential Integrity Plugins
+synopsis=The Referential Integrity Plugin maintains referential integrity for DN valued attributes.
+description=The values of these attributes can reference entries that have been deleted by a delete operation or renamed by a modify DN operation. The referential integrity plug-in either removes stale references to deleted entries or updates references to renamed entries. The plug-in allows the scope of this referential check to be limited to a set of base DNs if desired. The plug-in also can be configured to perform the referential checking in the background mode specified intervals.
+property.attribute-type.synopsis=Specifies the attribute types for which referential integrity is to be maintained.
+property.attribute-type.description=At least one attribute type must be specified, and the syntax of any attributes must be either a distinguished name (1.3.6.1.4.1.1466.115.121.1.12) or name and optional UID (1.3.6.1.4.1.1466.115.121.1.34).
+property.base-dn.synopsis=Specifies the base DN that limits the scope within which referential integrity is maintained.
+property.base-dn.default-behavior.alias.synopsis=Referential integrity is maintained in all public naming contexts.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.log-file.synopsis=Specifies the log file location where the update records are written when the plug-in is in background-mode processing.
+property.log-file.description=The default location is the logs directory of the server instance, using the file name "referint".
+property.log-file.syntax.string.pattern.synopsis=A path to an existing file that is readable by the server.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
+property.update-interval.synopsis=Specifies the interval in seconds when referential integrity updates are made.
+property.update-interval.description=If this value is 0, then the updates are made synchronously in the foreground.
diff --git a/opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn.properties b/opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn.properties
new file mode 100644
index 0000000..ce478d9
--- /dev/null
+++ b/opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn.properties
@@ -0,0 +1,17 @@
+user-friendly-name=Regular Expression Identity Mapper
+user-friendly-plural-name=Regular Expression Identity Mappers
+synopsis=The Regular Expression Identity Mapper provides a way to use a regular expression to translate the provided identifier when searching for the appropriate user entry.
+description=This may be used, for example, if the provided identifier is expected to be an e-mail address or Kerberos principal, but only the username portion (the part before the "@" symbol) should be used in the mapping process. Note that a replacement will be made only if all or part of the provided ID string matches the given match pattern. If no part of the ID string matches the provided pattern, the given ID string is used without any alteration.
+property.enabled.synopsis=Indicates whether the Regular Expression Identity Mapper is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Regular Expression Identity Mapper implementation.
+property.match-attribute.synopsis=Specifies the name or OID of the attribute whose value should match the provided identifier string after it has been processed by the associated regular expression.
+property.match-attribute.description=All values must refer to the name or OID of an attribute type defined in the Directory Server schema. If multiple attributes or OIDs are provided, at least one of those attributes must contain the provided ID string value in exactly one entry.
+property.match-base-dn.synopsis=Specifies the base DN(s) that should be used when performing searches to map the provided ID string to a user entry. If multiple values are given, searches are performed below all the specified base DNs.
+property.match-base-dn.default-behavior.alias.synopsis=The server searches below all public naming contexts.
+property.match-pattern.synopsis=Specifies the regular expression pattern that is used to identify portions of the ID string that will be replaced.
+property.match-pattern.description=Any portion of the ID string that matches this pattern is replaced in accordance with the provided replace pattern (or is removed if no replace pattern is specified). If multiple substrings within the given ID string match this pattern, all occurrences are replaced. If no part of the given ID string matches this pattern, the ID string is not altered. Exactly one match pattern value must be provided, and it must be a valid regular expression as described in the API documentation for the java.util.regex.Pattern class, including support for capturing groups.
+property.match-pattern.syntax.string.pattern.synopsis=Any valid regular expression pattern which is supported by the javax.util.regex.Pattern class (see http://java.sun.com/j2se/1.5.0/docs/api/java/util/regex/Pattern.html for documentation about this class for Java SE 5).
+property.replace-pattern.synopsis=Specifies the replacement pattern that should be used for substrings in the ID string that match the provided regular expression pattern.
+property.replace-pattern.description=If no replacement pattern is provided, then any matching portions of the ID string will be removed (i.e., replaced with an empty string). The replacement pattern may include a string from a capturing group by using a dollar sign ($) followed by an integer value that indicates which capturing group should be used.
+property.replace-pattern.default-behavior.alias.synopsis=The replace pattern will be the empty string.
+property.replace-pattern.syntax.string.pattern.synopsis=Any valid replacement string that is allowed by the javax.util.regex.Matcher class.
diff --git a/opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_de.properties b/opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_de.properties
new file mode 100644
index 0000000..ce478d9
--- /dev/null
+++ b/opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_de.properties
@@ -0,0 +1,17 @@
+user-friendly-name=Regular Expression Identity Mapper
+user-friendly-plural-name=Regular Expression Identity Mappers
+synopsis=The Regular Expression Identity Mapper provides a way to use a regular expression to translate the provided identifier when searching for the appropriate user entry.
+description=This may be used, for example, if the provided identifier is expected to be an e-mail address or Kerberos principal, but only the username portion (the part before the "@" symbol) should be used in the mapping process. Note that a replacement will be made only if all or part of the provided ID string matches the given match pattern. If no part of the ID string matches the provided pattern, the given ID string is used without any alteration.
+property.enabled.synopsis=Indicates whether the Regular Expression Identity Mapper is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Regular Expression Identity Mapper implementation.
+property.match-attribute.synopsis=Specifies the name or OID of the attribute whose value should match the provided identifier string after it has been processed by the associated regular expression.
+property.match-attribute.description=All values must refer to the name or OID of an attribute type defined in the Directory Server schema. If multiple attributes or OIDs are provided, at least one of those attributes must contain the provided ID string value in exactly one entry.
+property.match-base-dn.synopsis=Specifies the base DN(s) that should be used when performing searches to map the provided ID string to a user entry. If multiple values are given, searches are performed below all the specified base DNs.
+property.match-base-dn.default-behavior.alias.synopsis=The server searches below all public naming contexts.
+property.match-pattern.synopsis=Specifies the regular expression pattern that is used to identify portions of the ID string that will be replaced.
+property.match-pattern.description=Any portion of the ID string that matches this pattern is replaced in accordance with the provided replace pattern (or is removed if no replace pattern is specified). If multiple substrings within the given ID string match this pattern, all occurrences are replaced. If no part of the given ID string matches this pattern, the ID string is not altered. Exactly one match pattern value must be provided, and it must be a valid regular expression as described in the API documentation for the java.util.regex.Pattern class, including support for capturing groups.
+property.match-pattern.syntax.string.pattern.synopsis=Any valid regular expression pattern which is supported by the javax.util.regex.Pattern class (see http://java.sun.com/j2se/1.5.0/docs/api/java/util/regex/Pattern.html for documentation about this class for Java SE 5).
+property.replace-pattern.synopsis=Specifies the replacement pattern that should be used for substrings in the ID string that match the provided regular expression pattern.
+property.replace-pattern.description=If no replacement pattern is provided, then any matching portions of the ID string will be removed (i.e., replaced with an empty string). The replacement pattern may include a string from a capturing group by using a dollar sign ($) followed by an integer value that indicates which capturing group should be used.
+property.replace-pattern.default-behavior.alias.synopsis=The replace pattern will be the empty string.
+property.replace-pattern.syntax.string.pattern.synopsis=Any valid replacement string that is allowed by the javax.util.regex.Matcher class.
diff --git a/opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_es.properties b/opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_es.properties
new file mode 100644
index 0000000..ce478d9
--- /dev/null
+++ b/opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_es.properties
@@ -0,0 +1,17 @@
+user-friendly-name=Regular Expression Identity Mapper
+user-friendly-plural-name=Regular Expression Identity Mappers
+synopsis=The Regular Expression Identity Mapper provides a way to use a regular expression to translate the provided identifier when searching for the appropriate user entry.
+description=This may be used, for example, if the provided identifier is expected to be an e-mail address or Kerberos principal, but only the username portion (the part before the "@" symbol) should be used in the mapping process. Note that a replacement will be made only if all or part of the provided ID string matches the given match pattern. If no part of the ID string matches the provided pattern, the given ID string is used without any alteration.
+property.enabled.synopsis=Indicates whether the Regular Expression Identity Mapper is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Regular Expression Identity Mapper implementation.
+property.match-attribute.synopsis=Specifies the name or OID of the attribute whose value should match the provided identifier string after it has been processed by the associated regular expression.
+property.match-attribute.description=All values must refer to the name or OID of an attribute type defined in the Directory Server schema. If multiple attributes or OIDs are provided, at least one of those attributes must contain the provided ID string value in exactly one entry.
+property.match-base-dn.synopsis=Specifies the base DN(s) that should be used when performing searches to map the provided ID string to a user entry. If multiple values are given, searches are performed below all the specified base DNs.
+property.match-base-dn.default-behavior.alias.synopsis=The server searches below all public naming contexts.
+property.match-pattern.synopsis=Specifies the regular expression pattern that is used to identify portions of the ID string that will be replaced.
+property.match-pattern.description=Any portion of the ID string that matches this pattern is replaced in accordance with the provided replace pattern (or is removed if no replace pattern is specified). If multiple substrings within the given ID string match this pattern, all occurrences are replaced. If no part of the given ID string matches this pattern, the ID string is not altered. Exactly one match pattern value must be provided, and it must be a valid regular expression as described in the API documentation for the java.util.regex.Pattern class, including support for capturing groups.
+property.match-pattern.syntax.string.pattern.synopsis=Any valid regular expression pattern which is supported by the javax.util.regex.Pattern class (see http://java.sun.com/j2se/1.5.0/docs/api/java/util/regex/Pattern.html for documentation about this class for Java SE 5).
+property.replace-pattern.synopsis=Specifies the replacement pattern that should be used for substrings in the ID string that match the provided regular expression pattern.
+property.replace-pattern.description=If no replacement pattern is provided, then any matching portions of the ID string will be removed (i.e., replaced with an empty string). The replacement pattern may include a string from a capturing group by using a dollar sign ($) followed by an integer value that indicates which capturing group should be used.
+property.replace-pattern.default-behavior.alias.synopsis=The replace pattern will be the empty string.
+property.replace-pattern.syntax.string.pattern.synopsis=Any valid replacement string that is allowed by the javax.util.regex.Matcher class.
diff --git a/opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_fr.properties b/opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_fr.properties
new file mode 100644
index 0000000..ce478d9
--- /dev/null
+++ b/opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_fr.properties
@@ -0,0 +1,17 @@
+user-friendly-name=Regular Expression Identity Mapper
+user-friendly-plural-name=Regular Expression Identity Mappers
+synopsis=The Regular Expression Identity Mapper provides a way to use a regular expression to translate the provided identifier when searching for the appropriate user entry.
+description=This may be used, for example, if the provided identifier is expected to be an e-mail address or Kerberos principal, but only the username portion (the part before the "@" symbol) should be used in the mapping process. Note that a replacement will be made only if all or part of the provided ID string matches the given match pattern. If no part of the ID string matches the provided pattern, the given ID string is used without any alteration.
+property.enabled.synopsis=Indicates whether the Regular Expression Identity Mapper is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Regular Expression Identity Mapper implementation.
+property.match-attribute.synopsis=Specifies the name or OID of the attribute whose value should match the provided identifier string after it has been processed by the associated regular expression.
+property.match-attribute.description=All values must refer to the name or OID of an attribute type defined in the Directory Server schema. If multiple attributes or OIDs are provided, at least one of those attributes must contain the provided ID string value in exactly one entry.
+property.match-base-dn.synopsis=Specifies the base DN(s) that should be used when performing searches to map the provided ID string to a user entry. If multiple values are given, searches are performed below all the specified base DNs.
+property.match-base-dn.default-behavior.alias.synopsis=The server searches below all public naming contexts.
+property.match-pattern.synopsis=Specifies the regular expression pattern that is used to identify portions of the ID string that will be replaced.
+property.match-pattern.description=Any portion of the ID string that matches this pattern is replaced in accordance with the provided replace pattern (or is removed if no replace pattern is specified). If multiple substrings within the given ID string match this pattern, all occurrences are replaced. If no part of the given ID string matches this pattern, the ID string is not altered. Exactly one match pattern value must be provided, and it must be a valid regular expression as described in the API documentation for the java.util.regex.Pattern class, including support for capturing groups.
+property.match-pattern.syntax.string.pattern.synopsis=Any valid regular expression pattern which is supported by the javax.util.regex.Pattern class (see http://java.sun.com/j2se/1.5.0/docs/api/java/util/regex/Pattern.html for documentation about this class for Java SE 5).
+property.replace-pattern.synopsis=Specifies the replacement pattern that should be used for substrings in the ID string that match the provided regular expression pattern.
+property.replace-pattern.description=If no replacement pattern is provided, then any matching portions of the ID string will be removed (i.e., replaced with an empty string). The replacement pattern may include a string from a capturing group by using a dollar sign ($) followed by an integer value that indicates which capturing group should be used.
+property.replace-pattern.default-behavior.alias.synopsis=The replace pattern will be the empty string.
+property.replace-pattern.syntax.string.pattern.synopsis=Any valid replacement string that is allowed by the javax.util.regex.Matcher class.
diff --git a/opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_ja.properties b/opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_ja.properties
new file mode 100644
index 0000000..ce478d9
--- /dev/null
+++ b/opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_ja.properties
@@ -0,0 +1,17 @@
+user-friendly-name=Regular Expression Identity Mapper
+user-friendly-plural-name=Regular Expression Identity Mappers
+synopsis=The Regular Expression Identity Mapper provides a way to use a regular expression to translate the provided identifier when searching for the appropriate user entry.
+description=This may be used, for example, if the provided identifier is expected to be an e-mail address or Kerberos principal, but only the username portion (the part before the "@" symbol) should be used in the mapping process. Note that a replacement will be made only if all or part of the provided ID string matches the given match pattern. If no part of the ID string matches the provided pattern, the given ID string is used without any alteration.
+property.enabled.synopsis=Indicates whether the Regular Expression Identity Mapper is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Regular Expression Identity Mapper implementation.
+property.match-attribute.synopsis=Specifies the name or OID of the attribute whose value should match the provided identifier string after it has been processed by the associated regular expression.
+property.match-attribute.description=All values must refer to the name or OID of an attribute type defined in the Directory Server schema. If multiple attributes or OIDs are provided, at least one of those attributes must contain the provided ID string value in exactly one entry.
+property.match-base-dn.synopsis=Specifies the base DN(s) that should be used when performing searches to map the provided ID string to a user entry. If multiple values are given, searches are performed below all the specified base DNs.
+property.match-base-dn.default-behavior.alias.synopsis=The server searches below all public naming contexts.
+property.match-pattern.synopsis=Specifies the regular expression pattern that is used to identify portions of the ID string that will be replaced.
+property.match-pattern.description=Any portion of the ID string that matches this pattern is replaced in accordance with the provided replace pattern (or is removed if no replace pattern is specified). If multiple substrings within the given ID string match this pattern, all occurrences are replaced. If no part of the given ID string matches this pattern, the ID string is not altered. Exactly one match pattern value must be provided, and it must be a valid regular expression as described in the API documentation for the java.util.regex.Pattern class, including support for capturing groups.
+property.match-pattern.syntax.string.pattern.synopsis=Any valid regular expression pattern which is supported by the javax.util.regex.Pattern class (see http://java.sun.com/j2se/1.5.0/docs/api/java/util/regex/Pattern.html for documentation about this class for Java SE 5).
+property.replace-pattern.synopsis=Specifies the replacement pattern that should be used for substrings in the ID string that match the provided regular expression pattern.
+property.replace-pattern.description=If no replacement pattern is provided, then any matching portions of the ID string will be removed (i.e., replaced with an empty string). The replacement pattern may include a string from a capturing group by using a dollar sign ($) followed by an integer value that indicates which capturing group should be used.
+property.replace-pattern.default-behavior.alias.synopsis=The replace pattern will be the empty string.
+property.replace-pattern.syntax.string.pattern.synopsis=Any valid replacement string that is allowed by the javax.util.regex.Matcher class.
diff --git a/opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_ko.properties b/opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_ko.properties
new file mode 100644
index 0000000..ce478d9
--- /dev/null
+++ b/opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_ko.properties
@@ -0,0 +1,17 @@
+user-friendly-name=Regular Expression Identity Mapper
+user-friendly-plural-name=Regular Expression Identity Mappers
+synopsis=The Regular Expression Identity Mapper provides a way to use a regular expression to translate the provided identifier when searching for the appropriate user entry.
+description=This may be used, for example, if the provided identifier is expected to be an e-mail address or Kerberos principal, but only the username portion (the part before the "@" symbol) should be used in the mapping process. Note that a replacement will be made only if all or part of the provided ID string matches the given match pattern. If no part of the ID string matches the provided pattern, the given ID string is used without any alteration.
+property.enabled.synopsis=Indicates whether the Regular Expression Identity Mapper is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Regular Expression Identity Mapper implementation.
+property.match-attribute.synopsis=Specifies the name or OID of the attribute whose value should match the provided identifier string after it has been processed by the associated regular expression.
+property.match-attribute.description=All values must refer to the name or OID of an attribute type defined in the Directory Server schema. If multiple attributes or OIDs are provided, at least one of those attributes must contain the provided ID string value in exactly one entry.
+property.match-base-dn.synopsis=Specifies the base DN(s) that should be used when performing searches to map the provided ID string to a user entry. If multiple values are given, searches are performed below all the specified base DNs.
+property.match-base-dn.default-behavior.alias.synopsis=The server searches below all public naming contexts.
+property.match-pattern.synopsis=Specifies the regular expression pattern that is used to identify portions of the ID string that will be replaced.
+property.match-pattern.description=Any portion of the ID string that matches this pattern is replaced in accordance with the provided replace pattern (or is removed if no replace pattern is specified). If multiple substrings within the given ID string match this pattern, all occurrences are replaced. If no part of the given ID string matches this pattern, the ID string is not altered. Exactly one match pattern value must be provided, and it must be a valid regular expression as described in the API documentation for the java.util.regex.Pattern class, including support for capturing groups.
+property.match-pattern.syntax.string.pattern.synopsis=Any valid regular expression pattern which is supported by the javax.util.regex.Pattern class (see http://java.sun.com/j2se/1.5.0/docs/api/java/util/regex/Pattern.html for documentation about this class for Java SE 5).
+property.replace-pattern.synopsis=Specifies the replacement pattern that should be used for substrings in the ID string that match the provided regular expression pattern.
+property.replace-pattern.description=If no replacement pattern is provided, then any matching portions of the ID string will be removed (i.e., replaced with an empty string). The replacement pattern may include a string from a capturing group by using a dollar sign ($) followed by an integer value that indicates which capturing group should be used.
+property.replace-pattern.default-behavior.alias.synopsis=The replace pattern will be the empty string.
+property.replace-pattern.syntax.string.pattern.synopsis=Any valid replacement string that is allowed by the javax.util.regex.Matcher class.
diff --git a/opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_zh_CN.properties b/opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..ce478d9
--- /dev/null
+++ b/opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_zh_CN.properties
@@ -0,0 +1,17 @@
+user-friendly-name=Regular Expression Identity Mapper
+user-friendly-plural-name=Regular Expression Identity Mappers
+synopsis=The Regular Expression Identity Mapper provides a way to use a regular expression to translate the provided identifier when searching for the appropriate user entry.
+description=This may be used, for example, if the provided identifier is expected to be an e-mail address or Kerberos principal, but only the username portion (the part before the "@" symbol) should be used in the mapping process. Note that a replacement will be made only if all or part of the provided ID string matches the given match pattern. If no part of the ID string matches the provided pattern, the given ID string is used without any alteration.
+property.enabled.synopsis=Indicates whether the Regular Expression Identity Mapper is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Regular Expression Identity Mapper implementation.
+property.match-attribute.synopsis=Specifies the name or OID of the attribute whose value should match the provided identifier string after it has been processed by the associated regular expression.
+property.match-attribute.description=All values must refer to the name or OID of an attribute type defined in the Directory Server schema. If multiple attributes or OIDs are provided, at least one of those attributes must contain the provided ID string value in exactly one entry.
+property.match-base-dn.synopsis=Specifies the base DN(s) that should be used when performing searches to map the provided ID string to a user entry. If multiple values are given, searches are performed below all the specified base DNs.
+property.match-base-dn.default-behavior.alias.synopsis=The server searches below all public naming contexts.
+property.match-pattern.synopsis=Specifies the regular expression pattern that is used to identify portions of the ID string that will be replaced.
+property.match-pattern.description=Any portion of the ID string that matches this pattern is replaced in accordance with the provided replace pattern (or is removed if no replace pattern is specified). If multiple substrings within the given ID string match this pattern, all occurrences are replaced. If no part of the given ID string matches this pattern, the ID string is not altered. Exactly one match pattern value must be provided, and it must be a valid regular expression as described in the API documentation for the java.util.regex.Pattern class, including support for capturing groups.
+property.match-pattern.syntax.string.pattern.synopsis=Any valid regular expression pattern which is supported by the javax.util.regex.Pattern class (see http://java.sun.com/j2se/1.5.0/docs/api/java/util/regex/Pattern.html for documentation about this class for Java SE 5).
+property.replace-pattern.synopsis=Specifies the replacement pattern that should be used for substrings in the ID string that match the provided regular expression pattern.
+property.replace-pattern.description=If no replacement pattern is provided, then any matching portions of the ID string will be removed (i.e., replaced with an empty string). The replacement pattern may include a string from a capturing group by using a dollar sign ($) followed by an integer value that indicates which capturing group should be used.
+property.replace-pattern.default-behavior.alias.synopsis=The replace pattern will be the empty string.
+property.replace-pattern.syntax.string.pattern.synopsis=Any valid replacement string that is allowed by the javax.util.regex.Matcher class.
diff --git a/opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_zh_TW.properties b/opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..ce478d9
--- /dev/null
+++ b/opends/src/admin/messages/RegularExpressionIdentityMapperCfgDefn_zh_TW.properties
@@ -0,0 +1,17 @@
+user-friendly-name=Regular Expression Identity Mapper
+user-friendly-plural-name=Regular Expression Identity Mappers
+synopsis=The Regular Expression Identity Mapper provides a way to use a regular expression to translate the provided identifier when searching for the appropriate user entry.
+description=This may be used, for example, if the provided identifier is expected to be an e-mail address or Kerberos principal, but only the username portion (the part before the "@" symbol) should be used in the mapping process. Note that a replacement will be made only if all or part of the provided ID string matches the given match pattern. If no part of the ID string matches the provided pattern, the given ID string is used without any alteration.
+property.enabled.synopsis=Indicates whether the Regular Expression Identity Mapper is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Regular Expression Identity Mapper implementation.
+property.match-attribute.synopsis=Specifies the name or OID of the attribute whose value should match the provided identifier string after it has been processed by the associated regular expression.
+property.match-attribute.description=All values must refer to the name or OID of an attribute type defined in the Directory Server schema. If multiple attributes or OIDs are provided, at least one of those attributes must contain the provided ID string value in exactly one entry.
+property.match-base-dn.synopsis=Specifies the base DN(s) that should be used when performing searches to map the provided ID string to a user entry. If multiple values are given, searches are performed below all the specified base DNs.
+property.match-base-dn.default-behavior.alias.synopsis=The server searches below all public naming contexts.
+property.match-pattern.synopsis=Specifies the regular expression pattern that is used to identify portions of the ID string that will be replaced.
+property.match-pattern.description=Any portion of the ID string that matches this pattern is replaced in accordance with the provided replace pattern (or is removed if no replace pattern is specified). If multiple substrings within the given ID string match this pattern, all occurrences are replaced. If no part of the given ID string matches this pattern, the ID string is not altered. Exactly one match pattern value must be provided, and it must be a valid regular expression as described in the API documentation for the java.util.regex.Pattern class, including support for capturing groups.
+property.match-pattern.syntax.string.pattern.synopsis=Any valid regular expression pattern which is supported by the javax.util.regex.Pattern class (see http://java.sun.com/j2se/1.5.0/docs/api/java/util/regex/Pattern.html for documentation about this class for Java SE 5).
+property.replace-pattern.synopsis=Specifies the replacement pattern that should be used for substrings in the ID string that match the provided regular expression pattern.
+property.replace-pattern.description=If no replacement pattern is provided, then any matching portions of the ID string will be removed (i.e., replaced with an empty string). The replacement pattern may include a string from a capturing group by using a dollar sign ($) followed by an integer value that indicates which capturing group should be used.
+property.replace-pattern.default-behavior.alias.synopsis=The replace pattern will be the empty string.
+property.replace-pattern.syntax.string.pattern.synopsis=Any valid replacement string that is allowed by the javax.util.regex.Matcher class.
diff --git a/opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn.properties b/opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn.properties
new file mode 100644
index 0000000..aa3b5f3
--- /dev/null
+++ b/opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Repeated Characters Password Validator
+user-friendly-plural-name=Repeated Characters Password Validators
+synopsis=The Repeated Characters Password Validator is used to determine whether a proposed password is acceptable based on the number of times any character appears consecutively in a password value.
+description=It ensures that user passwords do not contain strings of the same character repeated several times, like "aaaaaa" or "aaabbb".
+property.case-sensitive-validation.synopsis=Indicates whether this password validator should treat password characters in a case-sensitive manner.
+property.case-sensitive-validation.description=If the value of this property is false, the validator ignores any differences in capitalization when looking for consecutive characters in the password. If the value is true, the validator considers a character to be repeating only if all consecutive occurrences use the same capitalization.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.max-consecutive-length.synopsis=Specifies the maximum number of times that any character can appear consecutively in a password value.
+property.max-consecutive-length.description=A value of zero indicates that no maximum limit is enforced.
diff --git a/opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_de.properties b/opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_de.properties
new file mode 100644
index 0000000..aa3b5f3
--- /dev/null
+++ b/opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_de.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Repeated Characters Password Validator
+user-friendly-plural-name=Repeated Characters Password Validators
+synopsis=The Repeated Characters Password Validator is used to determine whether a proposed password is acceptable based on the number of times any character appears consecutively in a password value.
+description=It ensures that user passwords do not contain strings of the same character repeated several times, like "aaaaaa" or "aaabbb".
+property.case-sensitive-validation.synopsis=Indicates whether this password validator should treat password characters in a case-sensitive manner.
+property.case-sensitive-validation.description=If the value of this property is false, the validator ignores any differences in capitalization when looking for consecutive characters in the password. If the value is true, the validator considers a character to be repeating only if all consecutive occurrences use the same capitalization.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.max-consecutive-length.synopsis=Specifies the maximum number of times that any character can appear consecutively in a password value.
+property.max-consecutive-length.description=A value of zero indicates that no maximum limit is enforced.
diff --git a/opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_es.properties b/opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_es.properties
new file mode 100644
index 0000000..aa3b5f3
--- /dev/null
+++ b/opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_es.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Repeated Characters Password Validator
+user-friendly-plural-name=Repeated Characters Password Validators
+synopsis=The Repeated Characters Password Validator is used to determine whether a proposed password is acceptable based on the number of times any character appears consecutively in a password value.
+description=It ensures that user passwords do not contain strings of the same character repeated several times, like "aaaaaa" or "aaabbb".
+property.case-sensitive-validation.synopsis=Indicates whether this password validator should treat password characters in a case-sensitive manner.
+property.case-sensitive-validation.description=If the value of this property is false, the validator ignores any differences in capitalization when looking for consecutive characters in the password. If the value is true, the validator considers a character to be repeating only if all consecutive occurrences use the same capitalization.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.max-consecutive-length.synopsis=Specifies the maximum number of times that any character can appear consecutively in a password value.
+property.max-consecutive-length.description=A value of zero indicates that no maximum limit is enforced.
diff --git a/opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_fr.properties b/opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_fr.properties
new file mode 100644
index 0000000..aa3b5f3
--- /dev/null
+++ b/opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_fr.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Repeated Characters Password Validator
+user-friendly-plural-name=Repeated Characters Password Validators
+synopsis=The Repeated Characters Password Validator is used to determine whether a proposed password is acceptable based on the number of times any character appears consecutively in a password value.
+description=It ensures that user passwords do not contain strings of the same character repeated several times, like "aaaaaa" or "aaabbb".
+property.case-sensitive-validation.synopsis=Indicates whether this password validator should treat password characters in a case-sensitive manner.
+property.case-sensitive-validation.description=If the value of this property is false, the validator ignores any differences in capitalization when looking for consecutive characters in the password. If the value is true, the validator considers a character to be repeating only if all consecutive occurrences use the same capitalization.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.max-consecutive-length.synopsis=Specifies the maximum number of times that any character can appear consecutively in a password value.
+property.max-consecutive-length.description=A value of zero indicates that no maximum limit is enforced.
diff --git a/opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_ja.properties b/opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_ja.properties
new file mode 100644
index 0000000..aa3b5f3
--- /dev/null
+++ b/opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_ja.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Repeated Characters Password Validator
+user-friendly-plural-name=Repeated Characters Password Validators
+synopsis=The Repeated Characters Password Validator is used to determine whether a proposed password is acceptable based on the number of times any character appears consecutively in a password value.
+description=It ensures that user passwords do not contain strings of the same character repeated several times, like "aaaaaa" or "aaabbb".
+property.case-sensitive-validation.synopsis=Indicates whether this password validator should treat password characters in a case-sensitive manner.
+property.case-sensitive-validation.description=If the value of this property is false, the validator ignores any differences in capitalization when looking for consecutive characters in the password. If the value is true, the validator considers a character to be repeating only if all consecutive occurrences use the same capitalization.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.max-consecutive-length.synopsis=Specifies the maximum number of times that any character can appear consecutively in a password value.
+property.max-consecutive-length.description=A value of zero indicates that no maximum limit is enforced.
diff --git a/opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_ko.properties b/opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_ko.properties
new file mode 100644
index 0000000..aa3b5f3
--- /dev/null
+++ b/opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_ko.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Repeated Characters Password Validator
+user-friendly-plural-name=Repeated Characters Password Validators
+synopsis=The Repeated Characters Password Validator is used to determine whether a proposed password is acceptable based on the number of times any character appears consecutively in a password value.
+description=It ensures that user passwords do not contain strings of the same character repeated several times, like "aaaaaa" or "aaabbb".
+property.case-sensitive-validation.synopsis=Indicates whether this password validator should treat password characters in a case-sensitive manner.
+property.case-sensitive-validation.description=If the value of this property is false, the validator ignores any differences in capitalization when looking for consecutive characters in the password. If the value is true, the validator considers a character to be repeating only if all consecutive occurrences use the same capitalization.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.max-consecutive-length.synopsis=Specifies the maximum number of times that any character can appear consecutively in a password value.
+property.max-consecutive-length.description=A value of zero indicates that no maximum limit is enforced.
diff --git a/opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_zh_CN.properties b/opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..aa3b5f3
--- /dev/null
+++ b/opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_zh_CN.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Repeated Characters Password Validator
+user-friendly-plural-name=Repeated Characters Password Validators
+synopsis=The Repeated Characters Password Validator is used to determine whether a proposed password is acceptable based on the number of times any character appears consecutively in a password value.
+description=It ensures that user passwords do not contain strings of the same character repeated several times, like "aaaaaa" or "aaabbb".
+property.case-sensitive-validation.synopsis=Indicates whether this password validator should treat password characters in a case-sensitive manner.
+property.case-sensitive-validation.description=If the value of this property is false, the validator ignores any differences in capitalization when looking for consecutive characters in the password. If the value is true, the validator considers a character to be repeating only if all consecutive occurrences use the same capitalization.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.max-consecutive-length.synopsis=Specifies the maximum number of times that any character can appear consecutively in a password value.
+property.max-consecutive-length.description=A value of zero indicates that no maximum limit is enforced.
diff --git a/opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_zh_TW.properties b/opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..aa3b5f3
--- /dev/null
+++ b/opends/src/admin/messages/RepeatedCharactersPasswordValidatorCfgDefn_zh_TW.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Repeated Characters Password Validator
+user-friendly-plural-name=Repeated Characters Password Validators
+synopsis=The Repeated Characters Password Validator is used to determine whether a proposed password is acceptable based on the number of times any character appears consecutively in a password value.
+description=It ensures that user passwords do not contain strings of the same character repeated several times, like "aaaaaa" or "aaabbb".
+property.case-sensitive-validation.synopsis=Indicates whether this password validator should treat password characters in a case-sensitive manner.
+property.case-sensitive-validation.description=If the value of this property is false, the validator ignores any differences in capitalization when looking for consecutive characters in the password. If the value is true, the validator considers a character to be repeating only if all consecutive occurrences use the same capitalization.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.max-consecutive-length.synopsis=Specifies the maximum number of times that any character can appear consecutively in a password value.
+property.max-consecutive-length.description=A value of zero indicates that no maximum limit is enforced.
diff --git a/opends/src/admin/messages/ReplicationDomainCfgDefn.properties b/opends/src/admin/messages/ReplicationDomainCfgDefn.properties
new file mode 100644
index 0000000..1b9d869
--- /dev/null
+++ b/opends/src/admin/messages/ReplicationDomainCfgDefn.properties
@@ -0,0 +1,29 @@
+user-friendly-name=Replication Domain
+user-friendly-plural-name=Replication Domains
+synopsis=A Replication Domain comprises of several Directory Servers sharing the same synchronized set of data.
+property.assured-sd-level.synopsis=The level of acknowledgment for Safe Data assured sub mode.
+property.assured-sd-level.description=When assured mode configured in Safe Data mode, this value defines the number of replication servers that should acknowledge the sent update before the LDAP client call can return.
+property.assured-timeout.synopsis=The timeout value when waiting for assured mode acknowledgements.
+property.assured-timeout.description=Defines the amount of milliseconds the server will wait for assured acknowledgements (in either Safe Data or Safe Read assured sub modes) before returning anyway the LDAP client call.
+property.assured-type.synopsis=Defines the assured mode of the replicated domain.
+property.assured-type.description=The assured mode can be disable or enabled. When enabled, two sub modes are available: Safe Data or Safe Read modes.
+property.assured-type.syntax.enumeration.value.not-assured.synopsis=Updates sent for replication (for being replayed on other LDAP servers of the topology) are sent without waiting for any aknowledgement and the LDAP client call returns immediately.
+property.assured-type.syntax.enumeration.value.safe-data.synopsis=Assured mode is enabled in Safe Data sub mode: updates sent for replication are subject to acknowledgement defined by the assured-sd-level property. After acknowlegement is received, LDAP client call returns.
+property.assured-type.syntax.enumeration.value.safe-read.synopsis=Assured mode is enabled in Safe Read sub mode: updates sent for replication are subject to acknowledgement of LDAP servers of the topology having the same group id than us (defined with assured-sr-group-id property). After acknowlegement is received, LDAP client call returns.
+property.base-dn.synopsis=Specifies the base DN of the replicated data.
+property.group-id.synopsis=The group id associated with this replicated domain.
+property.group-id.description=This value defines the group id of the replicated domain. The replication system will preferably connect and send updates to replicate to a replication server with the same group id as him.
+property.heartbeat-interval.synopsis=Specifies the heart-beat interval that the Directory Server will use when communicating with Replication Servers.
+property.heartbeat-interval.description=The Directory Server expects a regular heart-beat coming from the Replication Server within the specified interval. If a heartbeat is not received within the interval, the Directory Server closes its connection and connects to another Replication Server.
+property.isolation-policy.synopsis=Specifies the behavior of the Directory Server if a write operation is attempted on the data within the Replication Domain when none of the configured Replication Servers are available.
+property.isolation-policy.syntax.enumeration.value.accept-all-updates.synopsis=Indicates that updates should be accepted even though it is not possible to send them to any Replication Server. Best effort is made to re-send those updates to a Replication Servers when one of them is available, however those changes are at risk because they are only available from the historical information. This mode can also introduce high replication latency.
+property.isolation-policy.syntax.enumeration.value.reject-all-updates.synopsis=Indicates that all updates attempted on this Replication Domain are rejected when no Replication Server is available.
+property.referrals-url.synopsis=The URLs other LDAP servers should you to refer to us.
+property.referrals-url.description=URLs used by peer servers of the topology to refer to us through LDAP referrals. If this attribute is not defined, every URLs available to access this server will be used. If defined, only URLs specified here will be used.
+property.referrals-url.syntax.string.pattern.synopsis=A LDAP URL compliant with RFC 2255.
+property.replication-server.synopsis=Specifies the addresses of the Replication Servers within the Replication Domain to which the Directory Server should try to connect at startup time.
+property.replication-server.description=Addresses must be specified using the syntax: hostname:port
+property.replication-server.syntax.string.pattern.synopsis=A host name followed by a ":" and a port number.
+property.server-id.synopsis=Specifies a unique identifier for the Directory Server within the Replication Domain.
+property.server-id.description=Each Directory Server within the same Replication Domain must have a different server ID. A Directory Server which is a member of multiple Replication Domains may use the same server ID for each of its Replication Domain configurations.
+property.window-size.synopsis=Specifies the window size that the Directory Server will use when communicating with Replication Servers.
diff --git a/opends/src/admin/messages/ReplicationDomainCfgDefn_de.properties b/opends/src/admin/messages/ReplicationDomainCfgDefn_de.properties
new file mode 100644
index 0000000..1b9d869
--- /dev/null
+++ b/opends/src/admin/messages/ReplicationDomainCfgDefn_de.properties
@@ -0,0 +1,29 @@
+user-friendly-name=Replication Domain
+user-friendly-plural-name=Replication Domains
+synopsis=A Replication Domain comprises of several Directory Servers sharing the same synchronized set of data.
+property.assured-sd-level.synopsis=The level of acknowledgment for Safe Data assured sub mode.
+property.assured-sd-level.description=When assured mode configured in Safe Data mode, this value defines the number of replication servers that should acknowledge the sent update before the LDAP client call can return.
+property.assured-timeout.synopsis=The timeout value when waiting for assured mode acknowledgements.
+property.assured-timeout.description=Defines the amount of milliseconds the server will wait for assured acknowledgements (in either Safe Data or Safe Read assured sub modes) before returning anyway the LDAP client call.
+property.assured-type.synopsis=Defines the assured mode of the replicated domain.
+property.assured-type.description=The assured mode can be disable or enabled. When enabled, two sub modes are available: Safe Data or Safe Read modes.
+property.assured-type.syntax.enumeration.value.not-assured.synopsis=Updates sent for replication (for being replayed on other LDAP servers of the topology) are sent without waiting for any aknowledgement and the LDAP client call returns immediately.
+property.assured-type.syntax.enumeration.value.safe-data.synopsis=Assured mode is enabled in Safe Data sub mode: updates sent for replication are subject to acknowledgement defined by the assured-sd-level property. After acknowlegement is received, LDAP client call returns.
+property.assured-type.syntax.enumeration.value.safe-read.synopsis=Assured mode is enabled in Safe Read sub mode: updates sent for replication are subject to acknowledgement of LDAP servers of the topology having the same group id than us (defined with assured-sr-group-id property). After acknowlegement is received, LDAP client call returns.
+property.base-dn.synopsis=Specifies the base DN of the replicated data.
+property.group-id.synopsis=The group id associated with this replicated domain.
+property.group-id.description=This value defines the group id of the replicated domain. The replication system will preferably connect and send updates to replicate to a replication server with the same group id as him.
+property.heartbeat-interval.synopsis=Specifies the heart-beat interval that the Directory Server will use when communicating with Replication Servers.
+property.heartbeat-interval.description=The Directory Server expects a regular heart-beat coming from the Replication Server within the specified interval. If a heartbeat is not received within the interval, the Directory Server closes its connection and connects to another Replication Server.
+property.isolation-policy.synopsis=Specifies the behavior of the Directory Server if a write operation is attempted on the data within the Replication Domain when none of the configured Replication Servers are available.
+property.isolation-policy.syntax.enumeration.value.accept-all-updates.synopsis=Indicates that updates should be accepted even though it is not possible to send them to any Replication Server. Best effort is made to re-send those updates to a Replication Servers when one of them is available, however those changes are at risk because they are only available from the historical information. This mode can also introduce high replication latency.
+property.isolation-policy.syntax.enumeration.value.reject-all-updates.synopsis=Indicates that all updates attempted on this Replication Domain are rejected when no Replication Server is available.
+property.referrals-url.synopsis=The URLs other LDAP servers should you to refer to us.
+property.referrals-url.description=URLs used by peer servers of the topology to refer to us through LDAP referrals. If this attribute is not defined, every URLs available to access this server will be used. If defined, only URLs specified here will be used.
+property.referrals-url.syntax.string.pattern.synopsis=A LDAP URL compliant with RFC 2255.
+property.replication-server.synopsis=Specifies the addresses of the Replication Servers within the Replication Domain to which the Directory Server should try to connect at startup time.
+property.replication-server.description=Addresses must be specified using the syntax: hostname:port
+property.replication-server.syntax.string.pattern.synopsis=A host name followed by a ":" and a port number.
+property.server-id.synopsis=Specifies a unique identifier for the Directory Server within the Replication Domain.
+property.server-id.description=Each Directory Server within the same Replication Domain must have a different server ID. A Directory Server which is a member of multiple Replication Domains may use the same server ID for each of its Replication Domain configurations.
+property.window-size.synopsis=Specifies the window size that the Directory Server will use when communicating with Replication Servers.
diff --git a/opends/src/admin/messages/ReplicationDomainCfgDefn_es.properties b/opends/src/admin/messages/ReplicationDomainCfgDefn_es.properties
new file mode 100644
index 0000000..1b9d869
--- /dev/null
+++ b/opends/src/admin/messages/ReplicationDomainCfgDefn_es.properties
@@ -0,0 +1,29 @@
+user-friendly-name=Replication Domain
+user-friendly-plural-name=Replication Domains
+synopsis=A Replication Domain comprises of several Directory Servers sharing the same synchronized set of data.
+property.assured-sd-level.synopsis=The level of acknowledgment for Safe Data assured sub mode.
+property.assured-sd-level.description=When assured mode configured in Safe Data mode, this value defines the number of replication servers that should acknowledge the sent update before the LDAP client call can return.
+property.assured-timeout.synopsis=The timeout value when waiting for assured mode acknowledgements.
+property.assured-timeout.description=Defines the amount of milliseconds the server will wait for assured acknowledgements (in either Safe Data or Safe Read assured sub modes) before returning anyway the LDAP client call.
+property.assured-type.synopsis=Defines the assured mode of the replicated domain.
+property.assured-type.description=The assured mode can be disable or enabled. When enabled, two sub modes are available: Safe Data or Safe Read modes.
+property.assured-type.syntax.enumeration.value.not-assured.synopsis=Updates sent for replication (for being replayed on other LDAP servers of the topology) are sent without waiting for any aknowledgement and the LDAP client call returns immediately.
+property.assured-type.syntax.enumeration.value.safe-data.synopsis=Assured mode is enabled in Safe Data sub mode: updates sent for replication are subject to acknowledgement defined by the assured-sd-level property. After acknowlegement is received, LDAP client call returns.
+property.assured-type.syntax.enumeration.value.safe-read.synopsis=Assured mode is enabled in Safe Read sub mode: updates sent for replication are subject to acknowledgement of LDAP servers of the topology having the same group id than us (defined with assured-sr-group-id property). After acknowlegement is received, LDAP client call returns.
+property.base-dn.synopsis=Specifies the base DN of the replicated data.
+property.group-id.synopsis=The group id associated with this replicated domain.
+property.group-id.description=This value defines the group id of the replicated domain. The replication system will preferably connect and send updates to replicate to a replication server with the same group id as him.
+property.heartbeat-interval.synopsis=Specifies the heart-beat interval that the Directory Server will use when communicating with Replication Servers.
+property.heartbeat-interval.description=The Directory Server expects a regular heart-beat coming from the Replication Server within the specified interval. If a heartbeat is not received within the interval, the Directory Server closes its connection and connects to another Replication Server.
+property.isolation-policy.synopsis=Specifies the behavior of the Directory Server if a write operation is attempted on the data within the Replication Domain when none of the configured Replication Servers are available.
+property.isolation-policy.syntax.enumeration.value.accept-all-updates.synopsis=Indicates that updates should be accepted even though it is not possible to send them to any Replication Server. Best effort is made to re-send those updates to a Replication Servers when one of them is available, however those changes are at risk because they are only available from the historical information. This mode can also introduce high replication latency.
+property.isolation-policy.syntax.enumeration.value.reject-all-updates.synopsis=Indicates that all updates attempted on this Replication Domain are rejected when no Replication Server is available.
+property.referrals-url.synopsis=The URLs other LDAP servers should you to refer to us.
+property.referrals-url.description=URLs used by peer servers of the topology to refer to us through LDAP referrals. If this attribute is not defined, every URLs available to access this server will be used. If defined, only URLs specified here will be used.
+property.referrals-url.syntax.string.pattern.synopsis=A LDAP URL compliant with RFC 2255.
+property.replication-server.synopsis=Specifies the addresses of the Replication Servers within the Replication Domain to which the Directory Server should try to connect at startup time.
+property.replication-server.description=Addresses must be specified using the syntax: hostname:port
+property.replication-server.syntax.string.pattern.synopsis=A host name followed by a ":" and a port number.
+property.server-id.synopsis=Specifies a unique identifier for the Directory Server within the Replication Domain.
+property.server-id.description=Each Directory Server within the same Replication Domain must have a different server ID. A Directory Server which is a member of multiple Replication Domains may use the same server ID for each of its Replication Domain configurations.
+property.window-size.synopsis=Specifies the window size that the Directory Server will use when communicating with Replication Servers.
diff --git a/opends/src/admin/messages/ReplicationDomainCfgDefn_fr.properties b/opends/src/admin/messages/ReplicationDomainCfgDefn_fr.properties
new file mode 100644
index 0000000..1b9d869
--- /dev/null
+++ b/opends/src/admin/messages/ReplicationDomainCfgDefn_fr.properties
@@ -0,0 +1,29 @@
+user-friendly-name=Replication Domain
+user-friendly-plural-name=Replication Domains
+synopsis=A Replication Domain comprises of several Directory Servers sharing the same synchronized set of data.
+property.assured-sd-level.synopsis=The level of acknowledgment for Safe Data assured sub mode.
+property.assured-sd-level.description=When assured mode configured in Safe Data mode, this value defines the number of replication servers that should acknowledge the sent update before the LDAP client call can return.
+property.assured-timeout.synopsis=The timeout value when waiting for assured mode acknowledgements.
+property.assured-timeout.description=Defines the amount of milliseconds the server will wait for assured acknowledgements (in either Safe Data or Safe Read assured sub modes) before returning anyway the LDAP client call.
+property.assured-type.synopsis=Defines the assured mode of the replicated domain.
+property.assured-type.description=The assured mode can be disable or enabled. When enabled, two sub modes are available: Safe Data or Safe Read modes.
+property.assured-type.syntax.enumeration.value.not-assured.synopsis=Updates sent for replication (for being replayed on other LDAP servers of the topology) are sent without waiting for any aknowledgement and the LDAP client call returns immediately.
+property.assured-type.syntax.enumeration.value.safe-data.synopsis=Assured mode is enabled in Safe Data sub mode: updates sent for replication are subject to acknowledgement defined by the assured-sd-level property. After acknowlegement is received, LDAP client call returns.
+property.assured-type.syntax.enumeration.value.safe-read.synopsis=Assured mode is enabled in Safe Read sub mode: updates sent for replication are subject to acknowledgement of LDAP servers of the topology having the same group id than us (defined with assured-sr-group-id property). After acknowlegement is received, LDAP client call returns.
+property.base-dn.synopsis=Specifies the base DN of the replicated data.
+property.group-id.synopsis=The group id associated with this replicated domain.
+property.group-id.description=This value defines the group id of the replicated domain. The replication system will preferably connect and send updates to replicate to a replication server with the same group id as him.
+property.heartbeat-interval.synopsis=Specifies the heart-beat interval that the Directory Server will use when communicating with Replication Servers.
+property.heartbeat-interval.description=The Directory Server expects a regular heart-beat coming from the Replication Server within the specified interval. If a heartbeat is not received within the interval, the Directory Server closes its connection and connects to another Replication Server.
+property.isolation-policy.synopsis=Specifies the behavior of the Directory Server if a write operation is attempted on the data within the Replication Domain when none of the configured Replication Servers are available.
+property.isolation-policy.syntax.enumeration.value.accept-all-updates.synopsis=Indicates that updates should be accepted even though it is not possible to send them to any Replication Server. Best effort is made to re-send those updates to a Replication Servers when one of them is available, however those changes are at risk because they are only available from the historical information. This mode can also introduce high replication latency.
+property.isolation-policy.syntax.enumeration.value.reject-all-updates.synopsis=Indicates that all updates attempted on this Replication Domain are rejected when no Replication Server is available.
+property.referrals-url.synopsis=The URLs other LDAP servers should you to refer to us.
+property.referrals-url.description=URLs used by peer servers of the topology to refer to us through LDAP referrals. If this attribute is not defined, every URLs available to access this server will be used. If defined, only URLs specified here will be used.
+property.referrals-url.syntax.string.pattern.synopsis=A LDAP URL compliant with RFC 2255.
+property.replication-server.synopsis=Specifies the addresses of the Replication Servers within the Replication Domain to which the Directory Server should try to connect at startup time.
+property.replication-server.description=Addresses must be specified using the syntax: hostname:port
+property.replication-server.syntax.string.pattern.synopsis=A host name followed by a ":" and a port number.
+property.server-id.synopsis=Specifies a unique identifier for the Directory Server within the Replication Domain.
+property.server-id.description=Each Directory Server within the same Replication Domain must have a different server ID. A Directory Server which is a member of multiple Replication Domains may use the same server ID for each of its Replication Domain configurations.
+property.window-size.synopsis=Specifies the window size that the Directory Server will use when communicating with Replication Servers.
diff --git a/opends/src/admin/messages/ReplicationDomainCfgDefn_ja.properties b/opends/src/admin/messages/ReplicationDomainCfgDefn_ja.properties
new file mode 100644
index 0000000..1b9d869
--- /dev/null
+++ b/opends/src/admin/messages/ReplicationDomainCfgDefn_ja.properties
@@ -0,0 +1,29 @@
+user-friendly-name=Replication Domain
+user-friendly-plural-name=Replication Domains
+synopsis=A Replication Domain comprises of several Directory Servers sharing the same synchronized set of data.
+property.assured-sd-level.synopsis=The level of acknowledgment for Safe Data assured sub mode.
+property.assured-sd-level.description=When assured mode configured in Safe Data mode, this value defines the number of replication servers that should acknowledge the sent update before the LDAP client call can return.
+property.assured-timeout.synopsis=The timeout value when waiting for assured mode acknowledgements.
+property.assured-timeout.description=Defines the amount of milliseconds the server will wait for assured acknowledgements (in either Safe Data or Safe Read assured sub modes) before returning anyway the LDAP client call.
+property.assured-type.synopsis=Defines the assured mode of the replicated domain.
+property.assured-type.description=The assured mode can be disable or enabled. When enabled, two sub modes are available: Safe Data or Safe Read modes.
+property.assured-type.syntax.enumeration.value.not-assured.synopsis=Updates sent for replication (for being replayed on other LDAP servers of the topology) are sent without waiting for any aknowledgement and the LDAP client call returns immediately.
+property.assured-type.syntax.enumeration.value.safe-data.synopsis=Assured mode is enabled in Safe Data sub mode: updates sent for replication are subject to acknowledgement defined by the assured-sd-level property. After acknowlegement is received, LDAP client call returns.
+property.assured-type.syntax.enumeration.value.safe-read.synopsis=Assured mode is enabled in Safe Read sub mode: updates sent for replication are subject to acknowledgement of LDAP servers of the topology having the same group id than us (defined with assured-sr-group-id property). After acknowlegement is received, LDAP client call returns.
+property.base-dn.synopsis=Specifies the base DN of the replicated data.
+property.group-id.synopsis=The group id associated with this replicated domain.
+property.group-id.description=This value defines the group id of the replicated domain. The replication system will preferably connect and send updates to replicate to a replication server with the same group id as him.
+property.heartbeat-interval.synopsis=Specifies the heart-beat interval that the Directory Server will use when communicating with Replication Servers.
+property.heartbeat-interval.description=The Directory Server expects a regular heart-beat coming from the Replication Server within the specified interval. If a heartbeat is not received within the interval, the Directory Server closes its connection and connects to another Replication Server.
+property.isolation-policy.synopsis=Specifies the behavior of the Directory Server if a write operation is attempted on the data within the Replication Domain when none of the configured Replication Servers are available.
+property.isolation-policy.syntax.enumeration.value.accept-all-updates.synopsis=Indicates that updates should be accepted even though it is not possible to send them to any Replication Server. Best effort is made to re-send those updates to a Replication Servers when one of them is available, however those changes are at risk because they are only available from the historical information. This mode can also introduce high replication latency.
+property.isolation-policy.syntax.enumeration.value.reject-all-updates.synopsis=Indicates that all updates attempted on this Replication Domain are rejected when no Replication Server is available.
+property.referrals-url.synopsis=The URLs other LDAP servers should you to refer to us.
+property.referrals-url.description=URLs used by peer servers of the topology to refer to us through LDAP referrals. If this attribute is not defined, every URLs available to access this server will be used. If defined, only URLs specified here will be used.
+property.referrals-url.syntax.string.pattern.synopsis=A LDAP URL compliant with RFC 2255.
+property.replication-server.synopsis=Specifies the addresses of the Replication Servers within the Replication Domain to which the Directory Server should try to connect at startup time.
+property.replication-server.description=Addresses must be specified using the syntax: hostname:port
+property.replication-server.syntax.string.pattern.synopsis=A host name followed by a ":" and a port number.
+property.server-id.synopsis=Specifies a unique identifier for the Directory Server within the Replication Domain.
+property.server-id.description=Each Directory Server within the same Replication Domain must have a different server ID. A Directory Server which is a member of multiple Replication Domains may use the same server ID for each of its Replication Domain configurations.
+property.window-size.synopsis=Specifies the window size that the Directory Server will use when communicating with Replication Servers.
diff --git a/opends/src/admin/messages/ReplicationDomainCfgDefn_ko.properties b/opends/src/admin/messages/ReplicationDomainCfgDefn_ko.properties
new file mode 100644
index 0000000..1b9d869
--- /dev/null
+++ b/opends/src/admin/messages/ReplicationDomainCfgDefn_ko.properties
@@ -0,0 +1,29 @@
+user-friendly-name=Replication Domain
+user-friendly-plural-name=Replication Domains
+synopsis=A Replication Domain comprises of several Directory Servers sharing the same synchronized set of data.
+property.assured-sd-level.synopsis=The level of acknowledgment for Safe Data assured sub mode.
+property.assured-sd-level.description=When assured mode configured in Safe Data mode, this value defines the number of replication servers that should acknowledge the sent update before the LDAP client call can return.
+property.assured-timeout.synopsis=The timeout value when waiting for assured mode acknowledgements.
+property.assured-timeout.description=Defines the amount of milliseconds the server will wait for assured acknowledgements (in either Safe Data or Safe Read assured sub modes) before returning anyway the LDAP client call.
+property.assured-type.synopsis=Defines the assured mode of the replicated domain.
+property.assured-type.description=The assured mode can be disable or enabled. When enabled, two sub modes are available: Safe Data or Safe Read modes.
+property.assured-type.syntax.enumeration.value.not-assured.synopsis=Updates sent for replication (for being replayed on other LDAP servers of the topology) are sent without waiting for any aknowledgement and the LDAP client call returns immediately.
+property.assured-type.syntax.enumeration.value.safe-data.synopsis=Assured mode is enabled in Safe Data sub mode: updates sent for replication are subject to acknowledgement defined by the assured-sd-level property. After acknowlegement is received, LDAP client call returns.
+property.assured-type.syntax.enumeration.value.safe-read.synopsis=Assured mode is enabled in Safe Read sub mode: updates sent for replication are subject to acknowledgement of LDAP servers of the topology having the same group id than us (defined with assured-sr-group-id property). After acknowlegement is received, LDAP client call returns.
+property.base-dn.synopsis=Specifies the base DN of the replicated data.
+property.group-id.synopsis=The group id associated with this replicated domain.
+property.group-id.description=This value defines the group id of the replicated domain. The replication system will preferably connect and send updates to replicate to a replication server with the same group id as him.
+property.heartbeat-interval.synopsis=Specifies the heart-beat interval that the Directory Server will use when communicating with Replication Servers.
+property.heartbeat-interval.description=The Directory Server expects a regular heart-beat coming from the Replication Server within the specified interval. If a heartbeat is not received within the interval, the Directory Server closes its connection and connects to another Replication Server.
+property.isolation-policy.synopsis=Specifies the behavior of the Directory Server if a write operation is attempted on the data within the Replication Domain when none of the configured Replication Servers are available.
+property.isolation-policy.syntax.enumeration.value.accept-all-updates.synopsis=Indicates that updates should be accepted even though it is not possible to send them to any Replication Server. Best effort is made to re-send those updates to a Replication Servers when one of them is available, however those changes are at risk because they are only available from the historical information. This mode can also introduce high replication latency.
+property.isolation-policy.syntax.enumeration.value.reject-all-updates.synopsis=Indicates that all updates attempted on this Replication Domain are rejected when no Replication Server is available.
+property.referrals-url.synopsis=The URLs other LDAP servers should you to refer to us.
+property.referrals-url.description=URLs used by peer servers of the topology to refer to us through LDAP referrals. If this attribute is not defined, every URLs available to access this server will be used. If defined, only URLs specified here will be used.
+property.referrals-url.syntax.string.pattern.synopsis=A LDAP URL compliant with RFC 2255.
+property.replication-server.synopsis=Specifies the addresses of the Replication Servers within the Replication Domain to which the Directory Server should try to connect at startup time.
+property.replication-server.description=Addresses must be specified using the syntax: hostname:port
+property.replication-server.syntax.string.pattern.synopsis=A host name followed by a ":" and a port number.
+property.server-id.synopsis=Specifies a unique identifier for the Directory Server within the Replication Domain.
+property.server-id.description=Each Directory Server within the same Replication Domain must have a different server ID. A Directory Server which is a member of multiple Replication Domains may use the same server ID for each of its Replication Domain configurations.
+property.window-size.synopsis=Specifies the window size that the Directory Server will use when communicating with Replication Servers.
diff --git a/opends/src/admin/messages/ReplicationDomainCfgDefn_zh_CN.properties b/opends/src/admin/messages/ReplicationDomainCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..1b9d869
--- /dev/null
+++ b/opends/src/admin/messages/ReplicationDomainCfgDefn_zh_CN.properties
@@ -0,0 +1,29 @@
+user-friendly-name=Replication Domain
+user-friendly-plural-name=Replication Domains
+synopsis=A Replication Domain comprises of several Directory Servers sharing the same synchronized set of data.
+property.assured-sd-level.synopsis=The level of acknowledgment for Safe Data assured sub mode.
+property.assured-sd-level.description=When assured mode configured in Safe Data mode, this value defines the number of replication servers that should acknowledge the sent update before the LDAP client call can return.
+property.assured-timeout.synopsis=The timeout value when waiting for assured mode acknowledgements.
+property.assured-timeout.description=Defines the amount of milliseconds the server will wait for assured acknowledgements (in either Safe Data or Safe Read assured sub modes) before returning anyway the LDAP client call.
+property.assured-type.synopsis=Defines the assured mode of the replicated domain.
+property.assured-type.description=The assured mode can be disable or enabled. When enabled, two sub modes are available: Safe Data or Safe Read modes.
+property.assured-type.syntax.enumeration.value.not-assured.synopsis=Updates sent for replication (for being replayed on other LDAP servers of the topology) are sent without waiting for any aknowledgement and the LDAP client call returns immediately.
+property.assured-type.syntax.enumeration.value.safe-data.synopsis=Assured mode is enabled in Safe Data sub mode: updates sent for replication are subject to acknowledgement defined by the assured-sd-level property. After acknowlegement is received, LDAP client call returns.
+property.assured-type.syntax.enumeration.value.safe-read.synopsis=Assured mode is enabled in Safe Read sub mode: updates sent for replication are subject to acknowledgement of LDAP servers of the topology having the same group id than us (defined with assured-sr-group-id property). After acknowlegement is received, LDAP client call returns.
+property.base-dn.synopsis=Specifies the base DN of the replicated data.
+property.group-id.synopsis=The group id associated with this replicated domain.
+property.group-id.description=This value defines the group id of the replicated domain. The replication system will preferably connect and send updates to replicate to a replication server with the same group id as him.
+property.heartbeat-interval.synopsis=Specifies the heart-beat interval that the Directory Server will use when communicating with Replication Servers.
+property.heartbeat-interval.description=The Directory Server expects a regular heart-beat coming from the Replication Server within the specified interval. If a heartbeat is not received within the interval, the Directory Server closes its connection and connects to another Replication Server.
+property.isolation-policy.synopsis=Specifies the behavior of the Directory Server if a write operation is attempted on the data within the Replication Domain when none of the configured Replication Servers are available.
+property.isolation-policy.syntax.enumeration.value.accept-all-updates.synopsis=Indicates that updates should be accepted even though it is not possible to send them to any Replication Server. Best effort is made to re-send those updates to a Replication Servers when one of them is available, however those changes are at risk because they are only available from the historical information. This mode can also introduce high replication latency.
+property.isolation-policy.syntax.enumeration.value.reject-all-updates.synopsis=Indicates that all updates attempted on this Replication Domain are rejected when no Replication Server is available.
+property.referrals-url.synopsis=The URLs other LDAP servers should you to refer to us.
+property.referrals-url.description=URLs used by peer servers of the topology to refer to us through LDAP referrals. If this attribute is not defined, every URLs available to access this server will be used. If defined, only URLs specified here will be used.
+property.referrals-url.syntax.string.pattern.synopsis=A LDAP URL compliant with RFC 2255.
+property.replication-server.synopsis=Specifies the addresses of the Replication Servers within the Replication Domain to which the Directory Server should try to connect at startup time.
+property.replication-server.description=Addresses must be specified using the syntax: hostname:port
+property.replication-server.syntax.string.pattern.synopsis=A host name followed by a ":" and a port number.
+property.server-id.synopsis=Specifies a unique identifier for the Directory Server within the Replication Domain.
+property.server-id.description=Each Directory Server within the same Replication Domain must have a different server ID. A Directory Server which is a member of multiple Replication Domains may use the same server ID for each of its Replication Domain configurations.
+property.window-size.synopsis=Specifies the window size that the Directory Server will use when communicating with Replication Servers.
diff --git a/opends/src/admin/messages/ReplicationDomainCfgDefn_zh_TW.properties b/opends/src/admin/messages/ReplicationDomainCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..1b9d869
--- /dev/null
+++ b/opends/src/admin/messages/ReplicationDomainCfgDefn_zh_TW.properties
@@ -0,0 +1,29 @@
+user-friendly-name=Replication Domain
+user-friendly-plural-name=Replication Domains
+synopsis=A Replication Domain comprises of several Directory Servers sharing the same synchronized set of data.
+property.assured-sd-level.synopsis=The level of acknowledgment for Safe Data assured sub mode.
+property.assured-sd-level.description=When assured mode configured in Safe Data mode, this value defines the number of replication servers that should acknowledge the sent update before the LDAP client call can return.
+property.assured-timeout.synopsis=The timeout value when waiting for assured mode acknowledgements.
+property.assured-timeout.description=Defines the amount of milliseconds the server will wait for assured acknowledgements (in either Safe Data or Safe Read assured sub modes) before returning anyway the LDAP client call.
+property.assured-type.synopsis=Defines the assured mode of the replicated domain.
+property.assured-type.description=The assured mode can be disable or enabled. When enabled, two sub modes are available: Safe Data or Safe Read modes.
+property.assured-type.syntax.enumeration.value.not-assured.synopsis=Updates sent for replication (for being replayed on other LDAP servers of the topology) are sent without waiting for any aknowledgement and the LDAP client call returns immediately.
+property.assured-type.syntax.enumeration.value.safe-data.synopsis=Assured mode is enabled in Safe Data sub mode: updates sent for replication are subject to acknowledgement defined by the assured-sd-level property. After acknowlegement is received, LDAP client call returns.
+property.assured-type.syntax.enumeration.value.safe-read.synopsis=Assured mode is enabled in Safe Read sub mode: updates sent for replication are subject to acknowledgement of LDAP servers of the topology having the same group id than us (defined with assured-sr-group-id property). After acknowlegement is received, LDAP client call returns.
+property.base-dn.synopsis=Specifies the base DN of the replicated data.
+property.group-id.synopsis=The group id associated with this replicated domain.
+property.group-id.description=This value defines the group id of the replicated domain. The replication system will preferably connect and send updates to replicate to a replication server with the same group id as him.
+property.heartbeat-interval.synopsis=Specifies the heart-beat interval that the Directory Server will use when communicating with Replication Servers.
+property.heartbeat-interval.description=The Directory Server expects a regular heart-beat coming from the Replication Server within the specified interval. If a heartbeat is not received within the interval, the Directory Server closes its connection and connects to another Replication Server.
+property.isolation-policy.synopsis=Specifies the behavior of the Directory Server if a write operation is attempted on the data within the Replication Domain when none of the configured Replication Servers are available.
+property.isolation-policy.syntax.enumeration.value.accept-all-updates.synopsis=Indicates that updates should be accepted even though it is not possible to send them to any Replication Server. Best effort is made to re-send those updates to a Replication Servers when one of them is available, however those changes are at risk because they are only available from the historical information. This mode can also introduce high replication latency.
+property.isolation-policy.syntax.enumeration.value.reject-all-updates.synopsis=Indicates that all updates attempted on this Replication Domain are rejected when no Replication Server is available.
+property.referrals-url.synopsis=The URLs other LDAP servers should you to refer to us.
+property.referrals-url.description=URLs used by peer servers of the topology to refer to us through LDAP referrals. If this attribute is not defined, every URLs available to access this server will be used. If defined, only URLs specified here will be used.
+property.referrals-url.syntax.string.pattern.synopsis=A LDAP URL compliant with RFC 2255.
+property.replication-server.synopsis=Specifies the addresses of the Replication Servers within the Replication Domain to which the Directory Server should try to connect at startup time.
+property.replication-server.description=Addresses must be specified using the syntax: hostname:port
+property.replication-server.syntax.string.pattern.synopsis=A host name followed by a ":" and a port number.
+property.server-id.synopsis=Specifies a unique identifier for the Directory Server within the Replication Domain.
+property.server-id.description=Each Directory Server within the same Replication Domain must have a different server ID. A Directory Server which is a member of multiple Replication Domains may use the same server ID for each of its Replication Domain configurations.
+property.window-size.synopsis=Specifies the window size that the Directory Server will use when communicating with Replication Servers.
diff --git a/opends/src/admin/messages/ReplicationServerCfgDefn.properties b/opends/src/admin/messages/ReplicationServerCfgDefn.properties
new file mode 100644
index 0000000..c1f6b44
--- /dev/null
+++ b/opends/src/admin/messages/ReplicationServerCfgDefn.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Replication Server
+user-friendly-plural-name=Replication Servers
+synopsis=Replication Servers publish updates to Directory Servers within a Replication Domain.
+property.assured-timeout.synopsis=The timeout value when waiting for assured mode acknowledgements.
+property.assured-timeout.description=Defines the amount of milliseconds the replication server will wait for assured acknowledgements (in either Safe Data or Safe Read assured sub modes) before forgetting them and answer to the entity that sent an update and is waiting for acknowledgment.
+property.degraded-status-threshold.synopsis=The number of pending changes as threshold value for putting a directory server in degraded status.
+property.degraded-status-threshold.description=This value represents a number of pending changes a replication server has in queue for sending to a directory server. Once this value is crossed, the matching directory server goes in degraded status. When number of pending changes goes back under this value, the directory server is put back in normal status. 0 means status analyzer is disabled and directory servers are never put in degraded status.
+property.group-id.synopsis=The group id for the replication server.
+property.group-id.description=This value defines the group id of the replication server. The replication system of a LDAP server uses the group id of the replicated domain and tries to connect, if possible, to a replication with the same group id.
+property.queue-size.synopsis=Specifies the number of changes that are kept in memory for each Directory Server in the Replication Domain.
+property.replication-db-directory.synopsis=The path where the Replication Server stores all persistent information.
+property.replication-port.synopsis=The port on which this Replication Server waits for connections from other Replication Servers or Directory Servers.
+property.replication-purge-delay.synopsis=The time (in seconds) after which the Replication Server erases all persistent information.
+property.replication-server.synopsis=Specifies the addresses of other Replication Servers to which this Replication Server tries to connect at startup time.
+property.replication-server.description=Addresses must be specified using the syntax: hostname:port
+property.replication-server.syntax.string.pattern.synopsis=A host name followed by a ":" and a port number.
+property.replication-server-id.synopsis=Specifies a unique identifier for the Replication Server.
+property.replication-server-id.description=Each Replication Server must have a different server ID.
+property.window-size.synopsis=Specifies the window size that the Replication Server uses when communicating with other Replication Servers.
diff --git a/opends/src/admin/messages/ReplicationServerCfgDefn_de.properties b/opends/src/admin/messages/ReplicationServerCfgDefn_de.properties
new file mode 100644
index 0000000..c1f6b44
--- /dev/null
+++ b/opends/src/admin/messages/ReplicationServerCfgDefn_de.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Replication Server
+user-friendly-plural-name=Replication Servers
+synopsis=Replication Servers publish updates to Directory Servers within a Replication Domain.
+property.assured-timeout.synopsis=The timeout value when waiting for assured mode acknowledgements.
+property.assured-timeout.description=Defines the amount of milliseconds the replication server will wait for assured acknowledgements (in either Safe Data or Safe Read assured sub modes) before forgetting them and answer to the entity that sent an update and is waiting for acknowledgment.
+property.degraded-status-threshold.synopsis=The number of pending changes as threshold value for putting a directory server in degraded status.
+property.degraded-status-threshold.description=This value represents a number of pending changes a replication server has in queue for sending to a directory server. Once this value is crossed, the matching directory server goes in degraded status. When number of pending changes goes back under this value, the directory server is put back in normal status. 0 means status analyzer is disabled and directory servers are never put in degraded status.
+property.group-id.synopsis=The group id for the replication server.
+property.group-id.description=This value defines the group id of the replication server. The replication system of a LDAP server uses the group id of the replicated domain and tries to connect, if possible, to a replication with the same group id.
+property.queue-size.synopsis=Specifies the number of changes that are kept in memory for each Directory Server in the Replication Domain.
+property.replication-db-directory.synopsis=The path where the Replication Server stores all persistent information.
+property.replication-port.synopsis=The port on which this Replication Server waits for connections from other Replication Servers or Directory Servers.
+property.replication-purge-delay.synopsis=The time (in seconds) after which the Replication Server erases all persistent information.
+property.replication-server.synopsis=Specifies the addresses of other Replication Servers to which this Replication Server tries to connect at startup time.
+property.replication-server.description=Addresses must be specified using the syntax: hostname:port
+property.replication-server.syntax.string.pattern.synopsis=A host name followed by a ":" and a port number.
+property.replication-server-id.synopsis=Specifies a unique identifier for the Replication Server.
+property.replication-server-id.description=Each Replication Server must have a different server ID.
+property.window-size.synopsis=Specifies the window size that the Replication Server uses when communicating with other Replication Servers.
diff --git a/opends/src/admin/messages/ReplicationServerCfgDefn_es.properties b/opends/src/admin/messages/ReplicationServerCfgDefn_es.properties
new file mode 100644
index 0000000..c1f6b44
--- /dev/null
+++ b/opends/src/admin/messages/ReplicationServerCfgDefn_es.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Replication Server
+user-friendly-plural-name=Replication Servers
+synopsis=Replication Servers publish updates to Directory Servers within a Replication Domain.
+property.assured-timeout.synopsis=The timeout value when waiting for assured mode acknowledgements.
+property.assured-timeout.description=Defines the amount of milliseconds the replication server will wait for assured acknowledgements (in either Safe Data or Safe Read assured sub modes) before forgetting them and answer to the entity that sent an update and is waiting for acknowledgment.
+property.degraded-status-threshold.synopsis=The number of pending changes as threshold value for putting a directory server in degraded status.
+property.degraded-status-threshold.description=This value represents a number of pending changes a replication server has in queue for sending to a directory server. Once this value is crossed, the matching directory server goes in degraded status. When number of pending changes goes back under this value, the directory server is put back in normal status. 0 means status analyzer is disabled and directory servers are never put in degraded status.
+property.group-id.synopsis=The group id for the replication server.
+property.group-id.description=This value defines the group id of the replication server. The replication system of a LDAP server uses the group id of the replicated domain and tries to connect, if possible, to a replication with the same group id.
+property.queue-size.synopsis=Specifies the number of changes that are kept in memory for each Directory Server in the Replication Domain.
+property.replication-db-directory.synopsis=The path where the Replication Server stores all persistent information.
+property.replication-port.synopsis=The port on which this Replication Server waits for connections from other Replication Servers or Directory Servers.
+property.replication-purge-delay.synopsis=The time (in seconds) after which the Replication Server erases all persistent information.
+property.replication-server.synopsis=Specifies the addresses of other Replication Servers to which this Replication Server tries to connect at startup time.
+property.replication-server.description=Addresses must be specified using the syntax: hostname:port
+property.replication-server.syntax.string.pattern.synopsis=A host name followed by a ":" and a port number.
+property.replication-server-id.synopsis=Specifies a unique identifier for the Replication Server.
+property.replication-server-id.description=Each Replication Server must have a different server ID.
+property.window-size.synopsis=Specifies the window size that the Replication Server uses when communicating with other Replication Servers.
diff --git a/opends/src/admin/messages/ReplicationServerCfgDefn_fr.properties b/opends/src/admin/messages/ReplicationServerCfgDefn_fr.properties
new file mode 100644
index 0000000..c1f6b44
--- /dev/null
+++ b/opends/src/admin/messages/ReplicationServerCfgDefn_fr.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Replication Server
+user-friendly-plural-name=Replication Servers
+synopsis=Replication Servers publish updates to Directory Servers within a Replication Domain.
+property.assured-timeout.synopsis=The timeout value when waiting for assured mode acknowledgements.
+property.assured-timeout.description=Defines the amount of milliseconds the replication server will wait for assured acknowledgements (in either Safe Data or Safe Read assured sub modes) before forgetting them and answer to the entity that sent an update and is waiting for acknowledgment.
+property.degraded-status-threshold.synopsis=The number of pending changes as threshold value for putting a directory server in degraded status.
+property.degraded-status-threshold.description=This value represents a number of pending changes a replication server has in queue for sending to a directory server. Once this value is crossed, the matching directory server goes in degraded status. When number of pending changes goes back under this value, the directory server is put back in normal status. 0 means status analyzer is disabled and directory servers are never put in degraded status.
+property.group-id.synopsis=The group id for the replication server.
+property.group-id.description=This value defines the group id of the replication server. The replication system of a LDAP server uses the group id of the replicated domain and tries to connect, if possible, to a replication with the same group id.
+property.queue-size.synopsis=Specifies the number of changes that are kept in memory for each Directory Server in the Replication Domain.
+property.replication-db-directory.synopsis=The path where the Replication Server stores all persistent information.
+property.replication-port.synopsis=The port on which this Replication Server waits for connections from other Replication Servers or Directory Servers.
+property.replication-purge-delay.synopsis=The time (in seconds) after which the Replication Server erases all persistent information.
+property.replication-server.synopsis=Specifies the addresses of other Replication Servers to which this Replication Server tries to connect at startup time.
+property.replication-server.description=Addresses must be specified using the syntax: hostname:port
+property.replication-server.syntax.string.pattern.synopsis=A host name followed by a ":" and a port number.
+property.replication-server-id.synopsis=Specifies a unique identifier for the Replication Server.
+property.replication-server-id.description=Each Replication Server must have a different server ID.
+property.window-size.synopsis=Specifies the window size that the Replication Server uses when communicating with other Replication Servers.
diff --git a/opends/src/admin/messages/ReplicationServerCfgDefn_ja.properties b/opends/src/admin/messages/ReplicationServerCfgDefn_ja.properties
new file mode 100644
index 0000000..c1f6b44
--- /dev/null
+++ b/opends/src/admin/messages/ReplicationServerCfgDefn_ja.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Replication Server
+user-friendly-plural-name=Replication Servers
+synopsis=Replication Servers publish updates to Directory Servers within a Replication Domain.
+property.assured-timeout.synopsis=The timeout value when waiting for assured mode acknowledgements.
+property.assured-timeout.description=Defines the amount of milliseconds the replication server will wait for assured acknowledgements (in either Safe Data or Safe Read assured sub modes) before forgetting them and answer to the entity that sent an update and is waiting for acknowledgment.
+property.degraded-status-threshold.synopsis=The number of pending changes as threshold value for putting a directory server in degraded status.
+property.degraded-status-threshold.description=This value represents a number of pending changes a replication server has in queue for sending to a directory server. Once this value is crossed, the matching directory server goes in degraded status. When number of pending changes goes back under this value, the directory server is put back in normal status. 0 means status analyzer is disabled and directory servers are never put in degraded status.
+property.group-id.synopsis=The group id for the replication server.
+property.group-id.description=This value defines the group id of the replication server. The replication system of a LDAP server uses the group id of the replicated domain and tries to connect, if possible, to a replication with the same group id.
+property.queue-size.synopsis=Specifies the number of changes that are kept in memory for each Directory Server in the Replication Domain.
+property.replication-db-directory.synopsis=The path where the Replication Server stores all persistent information.
+property.replication-port.synopsis=The port on which this Replication Server waits for connections from other Replication Servers or Directory Servers.
+property.replication-purge-delay.synopsis=The time (in seconds) after which the Replication Server erases all persistent information.
+property.replication-server.synopsis=Specifies the addresses of other Replication Servers to which this Replication Server tries to connect at startup time.
+property.replication-server.description=Addresses must be specified using the syntax: hostname:port
+property.replication-server.syntax.string.pattern.synopsis=A host name followed by a ":" and a port number.
+property.replication-server-id.synopsis=Specifies a unique identifier for the Replication Server.
+property.replication-server-id.description=Each Replication Server must have a different server ID.
+property.window-size.synopsis=Specifies the window size that the Replication Server uses when communicating with other Replication Servers.
diff --git a/opends/src/admin/messages/ReplicationServerCfgDefn_ko.properties b/opends/src/admin/messages/ReplicationServerCfgDefn_ko.properties
new file mode 100644
index 0000000..c1f6b44
--- /dev/null
+++ b/opends/src/admin/messages/ReplicationServerCfgDefn_ko.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Replication Server
+user-friendly-plural-name=Replication Servers
+synopsis=Replication Servers publish updates to Directory Servers within a Replication Domain.
+property.assured-timeout.synopsis=The timeout value when waiting for assured mode acknowledgements.
+property.assured-timeout.description=Defines the amount of milliseconds the replication server will wait for assured acknowledgements (in either Safe Data or Safe Read assured sub modes) before forgetting them and answer to the entity that sent an update and is waiting for acknowledgment.
+property.degraded-status-threshold.synopsis=The number of pending changes as threshold value for putting a directory server in degraded status.
+property.degraded-status-threshold.description=This value represents a number of pending changes a replication server has in queue for sending to a directory server. Once this value is crossed, the matching directory server goes in degraded status. When number of pending changes goes back under this value, the directory server is put back in normal status. 0 means status analyzer is disabled and directory servers are never put in degraded status.
+property.group-id.synopsis=The group id for the replication server.
+property.group-id.description=This value defines the group id of the replication server. The replication system of a LDAP server uses the group id of the replicated domain and tries to connect, if possible, to a replication with the same group id.
+property.queue-size.synopsis=Specifies the number of changes that are kept in memory for each Directory Server in the Replication Domain.
+property.replication-db-directory.synopsis=The path where the Replication Server stores all persistent information.
+property.replication-port.synopsis=The port on which this Replication Server waits for connections from other Replication Servers or Directory Servers.
+property.replication-purge-delay.synopsis=The time (in seconds) after which the Replication Server erases all persistent information.
+property.replication-server.synopsis=Specifies the addresses of other Replication Servers to which this Replication Server tries to connect at startup time.
+property.replication-server.description=Addresses must be specified using the syntax: hostname:port
+property.replication-server.syntax.string.pattern.synopsis=A host name followed by a ":" and a port number.
+property.replication-server-id.synopsis=Specifies a unique identifier for the Replication Server.
+property.replication-server-id.description=Each Replication Server must have a different server ID.
+property.window-size.synopsis=Specifies the window size that the Replication Server uses when communicating with other Replication Servers.
diff --git a/opends/src/admin/messages/ReplicationServerCfgDefn_zh_CN.properties b/opends/src/admin/messages/ReplicationServerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..c1f6b44
--- /dev/null
+++ b/opends/src/admin/messages/ReplicationServerCfgDefn_zh_CN.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Replication Server
+user-friendly-plural-name=Replication Servers
+synopsis=Replication Servers publish updates to Directory Servers within a Replication Domain.
+property.assured-timeout.synopsis=The timeout value when waiting for assured mode acknowledgements.
+property.assured-timeout.description=Defines the amount of milliseconds the replication server will wait for assured acknowledgements (in either Safe Data or Safe Read assured sub modes) before forgetting them and answer to the entity that sent an update and is waiting for acknowledgment.
+property.degraded-status-threshold.synopsis=The number of pending changes as threshold value for putting a directory server in degraded status.
+property.degraded-status-threshold.description=This value represents a number of pending changes a replication server has in queue for sending to a directory server. Once this value is crossed, the matching directory server goes in degraded status. When number of pending changes goes back under this value, the directory server is put back in normal status. 0 means status analyzer is disabled and directory servers are never put in degraded status.
+property.group-id.synopsis=The group id for the replication server.
+property.group-id.description=This value defines the group id of the replication server. The replication system of a LDAP server uses the group id of the replicated domain and tries to connect, if possible, to a replication with the same group id.
+property.queue-size.synopsis=Specifies the number of changes that are kept in memory for each Directory Server in the Replication Domain.
+property.replication-db-directory.synopsis=The path where the Replication Server stores all persistent information.
+property.replication-port.synopsis=The port on which this Replication Server waits for connections from other Replication Servers or Directory Servers.
+property.replication-purge-delay.synopsis=The time (in seconds) after which the Replication Server erases all persistent information.
+property.replication-server.synopsis=Specifies the addresses of other Replication Servers to which this Replication Server tries to connect at startup time.
+property.replication-server.description=Addresses must be specified using the syntax: hostname:port
+property.replication-server.syntax.string.pattern.synopsis=A host name followed by a ":" and a port number.
+property.replication-server-id.synopsis=Specifies a unique identifier for the Replication Server.
+property.replication-server-id.description=Each Replication Server must have a different server ID.
+property.window-size.synopsis=Specifies the window size that the Replication Server uses when communicating with other Replication Servers.
diff --git a/opends/src/admin/messages/ReplicationServerCfgDefn_zh_TW.properties b/opends/src/admin/messages/ReplicationServerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..c1f6b44
--- /dev/null
+++ b/opends/src/admin/messages/ReplicationServerCfgDefn_zh_TW.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Replication Server
+user-friendly-plural-name=Replication Servers
+synopsis=Replication Servers publish updates to Directory Servers within a Replication Domain.
+property.assured-timeout.synopsis=The timeout value when waiting for assured mode acknowledgements.
+property.assured-timeout.description=Defines the amount of milliseconds the replication server will wait for assured acknowledgements (in either Safe Data or Safe Read assured sub modes) before forgetting them and answer to the entity that sent an update and is waiting for acknowledgment.
+property.degraded-status-threshold.synopsis=The number of pending changes as threshold value for putting a directory server in degraded status.
+property.degraded-status-threshold.description=This value represents a number of pending changes a replication server has in queue for sending to a directory server. Once this value is crossed, the matching directory server goes in degraded status. When number of pending changes goes back under this value, the directory server is put back in normal status. 0 means status analyzer is disabled and directory servers are never put in degraded status.
+property.group-id.synopsis=The group id for the replication server.
+property.group-id.description=This value defines the group id of the replication server. The replication system of a LDAP server uses the group id of the replicated domain and tries to connect, if possible, to a replication with the same group id.
+property.queue-size.synopsis=Specifies the number of changes that are kept in memory for each Directory Server in the Replication Domain.
+property.replication-db-directory.synopsis=The path where the Replication Server stores all persistent information.
+property.replication-port.synopsis=The port on which this Replication Server waits for connections from other Replication Servers or Directory Servers.
+property.replication-purge-delay.synopsis=The time (in seconds) after which the Replication Server erases all persistent information.
+property.replication-server.synopsis=Specifies the addresses of other Replication Servers to which this Replication Server tries to connect at startup time.
+property.replication-server.description=Addresses must be specified using the syntax: hostname:port
+property.replication-server.syntax.string.pattern.synopsis=A host name followed by a ":" and a port number.
+property.replication-server-id.synopsis=Specifies a unique identifier for the Replication Server.
+property.replication-server-id.description=Each Replication Server must have a different server ID.
+property.window-size.synopsis=Specifies the window size that the Replication Server uses when communicating with other Replication Servers.
diff --git a/opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn.properties b/opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn.properties
new file mode 100644
index 0000000..aac8716
--- /dev/null
+++ b/opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn.properties
@@ -0,0 +1,12 @@
+user-friendly-name=Replication Synchronization Provider
+user-friendly-plural-name=Replication Synchronization Providers
+synopsis=The Replication Synchronization Provider provides multi-master replication of data across multiple Directory Server instances.
+property.enabled.synopsis=Indicates whether the Replication Synchronization Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Replication Synchronization Provider implementation.
+property.num-update-replay-threads.synopsis=Specifies the number of update replay threads.
+property.num-update-replay-threads.description=This value is the number of threads created for replaying every updates received for all the replication domains.
+relation.replication-domain.user-friendly-name=Replication Domain
+relation.replication-domain.user-friendly-plural-name=Replication Domains
+relation.replication-domain.synopsis=A Replication Domain comprises of several Directory Servers sharing the same synchronized set of data.
+relation.replication-server.user-friendly-name=Replication Server
+relation.replication-server.synopsis=Replication Servers publish updates to Directory Servers within a Replication Domain.
diff --git a/opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_de.properties b/opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_de.properties
new file mode 100644
index 0000000..aac8716
--- /dev/null
+++ b/opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_de.properties
@@ -0,0 +1,12 @@
+user-friendly-name=Replication Synchronization Provider
+user-friendly-plural-name=Replication Synchronization Providers
+synopsis=The Replication Synchronization Provider provides multi-master replication of data across multiple Directory Server instances.
+property.enabled.synopsis=Indicates whether the Replication Synchronization Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Replication Synchronization Provider implementation.
+property.num-update-replay-threads.synopsis=Specifies the number of update replay threads.
+property.num-update-replay-threads.description=This value is the number of threads created for replaying every updates received for all the replication domains.
+relation.replication-domain.user-friendly-name=Replication Domain
+relation.replication-domain.user-friendly-plural-name=Replication Domains
+relation.replication-domain.synopsis=A Replication Domain comprises of several Directory Servers sharing the same synchronized set of data.
+relation.replication-server.user-friendly-name=Replication Server
+relation.replication-server.synopsis=Replication Servers publish updates to Directory Servers within a Replication Domain.
diff --git a/opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_es.properties b/opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_es.properties
new file mode 100644
index 0000000..aac8716
--- /dev/null
+++ b/opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_es.properties
@@ -0,0 +1,12 @@
+user-friendly-name=Replication Synchronization Provider
+user-friendly-plural-name=Replication Synchronization Providers
+synopsis=The Replication Synchronization Provider provides multi-master replication of data across multiple Directory Server instances.
+property.enabled.synopsis=Indicates whether the Replication Synchronization Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Replication Synchronization Provider implementation.
+property.num-update-replay-threads.synopsis=Specifies the number of update replay threads.
+property.num-update-replay-threads.description=This value is the number of threads created for replaying every updates received for all the replication domains.
+relation.replication-domain.user-friendly-name=Replication Domain
+relation.replication-domain.user-friendly-plural-name=Replication Domains
+relation.replication-domain.synopsis=A Replication Domain comprises of several Directory Servers sharing the same synchronized set of data.
+relation.replication-server.user-friendly-name=Replication Server
+relation.replication-server.synopsis=Replication Servers publish updates to Directory Servers within a Replication Domain.
diff --git a/opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_fr.properties b/opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_fr.properties
new file mode 100644
index 0000000..aac8716
--- /dev/null
+++ b/opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_fr.properties
@@ -0,0 +1,12 @@
+user-friendly-name=Replication Synchronization Provider
+user-friendly-plural-name=Replication Synchronization Providers
+synopsis=The Replication Synchronization Provider provides multi-master replication of data across multiple Directory Server instances.
+property.enabled.synopsis=Indicates whether the Replication Synchronization Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Replication Synchronization Provider implementation.
+property.num-update-replay-threads.synopsis=Specifies the number of update replay threads.
+property.num-update-replay-threads.description=This value is the number of threads created for replaying every updates received for all the replication domains.
+relation.replication-domain.user-friendly-name=Replication Domain
+relation.replication-domain.user-friendly-plural-name=Replication Domains
+relation.replication-domain.synopsis=A Replication Domain comprises of several Directory Servers sharing the same synchronized set of data.
+relation.replication-server.user-friendly-name=Replication Server
+relation.replication-server.synopsis=Replication Servers publish updates to Directory Servers within a Replication Domain.
diff --git a/opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_ja.properties b/opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_ja.properties
new file mode 100644
index 0000000..aac8716
--- /dev/null
+++ b/opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_ja.properties
@@ -0,0 +1,12 @@
+user-friendly-name=Replication Synchronization Provider
+user-friendly-plural-name=Replication Synchronization Providers
+synopsis=The Replication Synchronization Provider provides multi-master replication of data across multiple Directory Server instances.
+property.enabled.synopsis=Indicates whether the Replication Synchronization Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Replication Synchronization Provider implementation.
+property.num-update-replay-threads.synopsis=Specifies the number of update replay threads.
+property.num-update-replay-threads.description=This value is the number of threads created for replaying every updates received for all the replication domains.
+relation.replication-domain.user-friendly-name=Replication Domain
+relation.replication-domain.user-friendly-plural-name=Replication Domains
+relation.replication-domain.synopsis=A Replication Domain comprises of several Directory Servers sharing the same synchronized set of data.
+relation.replication-server.user-friendly-name=Replication Server
+relation.replication-server.synopsis=Replication Servers publish updates to Directory Servers within a Replication Domain.
diff --git a/opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_ko.properties b/opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_ko.properties
new file mode 100644
index 0000000..aac8716
--- /dev/null
+++ b/opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_ko.properties
@@ -0,0 +1,12 @@
+user-friendly-name=Replication Synchronization Provider
+user-friendly-plural-name=Replication Synchronization Providers
+synopsis=The Replication Synchronization Provider provides multi-master replication of data across multiple Directory Server instances.
+property.enabled.synopsis=Indicates whether the Replication Synchronization Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Replication Synchronization Provider implementation.
+property.num-update-replay-threads.synopsis=Specifies the number of update replay threads.
+property.num-update-replay-threads.description=This value is the number of threads created for replaying every updates received for all the replication domains.
+relation.replication-domain.user-friendly-name=Replication Domain
+relation.replication-domain.user-friendly-plural-name=Replication Domains
+relation.replication-domain.synopsis=A Replication Domain comprises of several Directory Servers sharing the same synchronized set of data.
+relation.replication-server.user-friendly-name=Replication Server
+relation.replication-server.synopsis=Replication Servers publish updates to Directory Servers within a Replication Domain.
diff --git a/opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_zh_CN.properties b/opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..aac8716
--- /dev/null
+++ b/opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_zh_CN.properties
@@ -0,0 +1,12 @@
+user-friendly-name=Replication Synchronization Provider
+user-friendly-plural-name=Replication Synchronization Providers
+synopsis=The Replication Synchronization Provider provides multi-master replication of data across multiple Directory Server instances.
+property.enabled.synopsis=Indicates whether the Replication Synchronization Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Replication Synchronization Provider implementation.
+property.num-update-replay-threads.synopsis=Specifies the number of update replay threads.
+property.num-update-replay-threads.description=This value is the number of threads created for replaying every updates received for all the replication domains.
+relation.replication-domain.user-friendly-name=Replication Domain
+relation.replication-domain.user-friendly-plural-name=Replication Domains
+relation.replication-domain.synopsis=A Replication Domain comprises of several Directory Servers sharing the same synchronized set of data.
+relation.replication-server.user-friendly-name=Replication Server
+relation.replication-server.synopsis=Replication Servers publish updates to Directory Servers within a Replication Domain.
diff --git a/opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_zh_TW.properties b/opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..aac8716
--- /dev/null
+++ b/opends/src/admin/messages/ReplicationSynchronizationProviderCfgDefn_zh_TW.properties
@@ -0,0 +1,12 @@
+user-friendly-name=Replication Synchronization Provider
+user-friendly-plural-name=Replication Synchronization Providers
+synopsis=The Replication Synchronization Provider provides multi-master replication of data across multiple Directory Server instances.
+property.enabled.synopsis=Indicates whether the Replication Synchronization Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Replication Synchronization Provider implementation.
+property.num-update-replay-threads.synopsis=Specifies the number of update replay threads.
+property.num-update-replay-threads.description=This value is the number of threads created for replaying every updates received for all the replication domains.
+relation.replication-domain.user-friendly-name=Replication Domain
+relation.replication-domain.user-friendly-plural-name=Replication Domains
+relation.replication-domain.synopsis=A Replication Domain comprises of several Directory Servers sharing the same synchronized set of data.
+relation.replication-server.user-friendly-name=Replication Server
+relation.replication-server.synopsis=Replication Servers publish updates to Directory Servers within a Replication Domain.
diff --git a/opends/src/admin/messages/RootCfgDefn.properties b/opends/src/admin/messages/RootCfgDefn.properties
new file mode 100644
index 0000000..54efd5e
--- /dev/null
+++ b/opends/src/admin/messages/RootCfgDefn.properties
@@ -0,0 +1,127 @@
+user-friendly-name=Root
+user-friendly-plural-name=Roots
+synopsis=The root configuration provides an entry point to the rest of the OpenDS Directory Server configuration.
+tag.core-server.synopsis=Core server
+tag.database.synopsis=Caching and back-ends
+tag.logging.synopsis=Logging
+tag.replication.synopsis=Replication
+tag.security.synopsis=Authentication and authorization
+tag.user-management.synopsis=User management
+relation.access-control-handler.user-friendly-name=Access Control Handler
+relation.access-control-handler.synopsis=Access Control Handlers manage the application-wide access control. The OpenDS access control handler is defined through an extensible interface, so that alternate implementations can be created. Only one access control handler may be active in the server at any given time.
+relation.access-control-handler.description=Note that OpenDS also has a privilege subsystem, which may have an impact on what clients may be allowed to do in the server. For example, any user with the bypass-acl privilege is not subject to access control checking regardless of whether the access control implementation is enabled.
+relation.account-status-notification-handler.user-friendly-name=Account Status Notification Handler
+relation.account-status-notification-handler.user-friendly-plural-name=Account Status Notification Handlers
+relation.account-status-notification-handler.synopsis=Account Status Notification Handlers are invoked to provide notification to users in some form (for example, by an email message) when the status of a user's account has changed in some way. The Account Status Notification Handler can be used to notify the user and/or administrators of the change.
+relation.administration-connector.user-friendly-name=Administration Connector
+relation.administration-connector.synopsis=The Administration Connector is used to interact with administration tools using LDAP.
+relation.administration-connector.description=It is a dedicated entry point for administration.
+relation.alert-handler.user-friendly-name=Alert Handler
+relation.alert-handler.user-friendly-plural-name=Alert Handlers
+relation.alert-handler.synopsis=Alert Handlers are used to notify administrators of significant problems or notable events that occur in the Directory Server.
+relation.attribute-syntax.user-friendly-name=Attribute Syntax
+relation.attribute-syntax.user-friendly-plural-name=Attribute Syntaxes
+relation.attribute-syntax.synopsis=Attribute Syntaxes define the type of data that may be stored in an attribute with that syntax. A syntax is generally associated with a set of matching rules that indicate how to perform matching operations against values of that syntax.
+relation.backend.user-friendly-name=Backend
+relation.backend.user-friendly-plural-name=Backends
+relation.backend.synopsis=Backends are responsible for providing access to the underlying data presented by the server.
+relation.backend.description=The data may be stored locally in an embedded database, remotely in an external system, or generated on the fly (for example, calculated from other information that is available).
+relation.certificate-mapper.user-friendly-name=Certificate Mapper
+relation.certificate-mapper.user-friendly-plural-name=Certificate Mappers
+relation.certificate-mapper.synopsis=Certificate Mappers are responsible for establishing a mapping between a client certificate and the entry for the user that corresponds to that certificate.
+relation.connection-handler.user-friendly-name=Connection Handler
+relation.connection-handler.user-friendly-plural-name=Connection Handlers
+relation.connection-handler.synopsis=Connection Handlers are responsible for handling all interaction with the clients, including accepting the connections, reading requests, and sending responses.
+relation.crypto-manager.user-friendly-name=Crypto Manager
+relation.crypto-manager.synopsis=The Crypto Manager provides a common interface for performing compression, decompression, hashing, encryption and other kinds of cryptographic operations.
+relation.entry-cache.user-friendly-name=Entry Cache
+relation.entry-cache.user-friendly-plural-name=Entry Caches
+relation.entry-cache.synopsis=Entry Caches are responsible for caching entries which are likely to be accessed by client applications in order to improve Directory Server performance.
+relation.extended-operation-handler.user-friendly-name=Extended Operation Handler
+relation.extended-operation-handler.user-friendly-plural-name=Extended Operation Handlers
+relation.extended-operation-handler.synopsis=Extended Operation Handlers processes the different types of extended operations in the server.
+relation.extension.user-friendly-name=Extension
+relation.extension.user-friendly-plural-name=Extensions
+relation.extension.synopsis=The Extension allows to extend the configuration with new type of objects.
+relation.extension.description=It is an entry point for extensions that requires configuration objects that does not inherit from an existing top-level object.
+relation.global-configuration.user-friendly-name=Global Configuration
+relation.global-configuration.synopsis=The Global contains properties that affect the overall operation of the OpenDS Directory Server .
+relation.group-implementation.user-friendly-name=Group Implementation
+relation.group-implementation.user-friendly-plural-name=Group Implementations
+relation.group-implementation.synopsis=Group Implementations define named collections of users.
+relation.group-implementation.description=Different group implementations may have different ways of determining membership. For example, some groups may explicitly list the members, and/or they may dynamically determine membership.
+relation.identity-mapper.user-friendly-name=Identity Mapper
+relation.identity-mapper.user-friendly-plural-name=Identity Mappers
+relation.identity-mapper.synopsis=Identity Mappers are responsible for establishing a mapping between an identifier string provided by a client, and the entry for the user that corresponds to that identifier. Identity Mappers are used to process several SASL mechanisms to map an authorization ID (e.g., a Kerberos principal when using GSSAPI) to a directory user. They are also used when processing requests with the proxied authorization control.
+relation.key-manager-provider.user-friendly-name=Key Manager Provider
+relation.key-manager-provider.user-friendly-plural-name=Key Manager Providers
+relation.key-manager-provider.synopsis=Key Manager Providers are responsible for managing the key material that is used to authenticate an SSL connection to its peer.
+relation.key-manager-provider.description=Key Manager Providers essentially provide access to the certificate that is used by the server when performing SSL or StartTLS negotiation.
+relation.log-publisher.user-friendly-name=Log Publisher
+relation.log-publisher.user-friendly-plural-name=Log Publishers
+relation.log-publisher.synopsis=Log Publishers are responsible for distributing log messages from different loggers to a destination.
+relation.log-retention-policy.user-friendly-name=Log Retention Policy
+relation.log-retention-policy.user-friendly-plural-name=Log Retention Policies
+relation.log-retention-policy.synopsis=Log Retention Policies are used to specify when log files should be cleaned.
+relation.log-rotation-policy.user-friendly-name=Log Rotation Policy
+relation.log-rotation-policy.user-friendly-plural-name=Log Rotation Policies
+relation.log-rotation-policy.synopsis=Log Rotation Policies are used to specify when log files should be rotated.
+relation.matching-rule.user-friendly-name=Matching Rule
+relation.matching-rule.user-friendly-plural-name=Matching Rules
+relation.matching-rule.synopsis=Matching Rules define a set of rules for performing matching operations against assertion values.
+relation.matching-rule.description=Matching rules are frequently associated with an attribute syntax and are used to compare values according to that syntax. For example, the distinguishedNameEqualityMatch matching rule can be used to determine whether two DNs are equal and can ignore unnecessary spaces around commas and equal signs, differences in capitalization in attribute names, an so on.
+relation.monitor-provider.user-friendly-name=Monitor Provider
+relation.monitor-provider.user-friendly-plural-name=Monitor Providers
+relation.monitor-provider.synopsis=Monitor Providers can be used to provide information about the state of the server or one of its components.
+relation.monitor-provider.description=This information is useful for monitoring or troubleshooting.
+relation.network-group.user-friendly-name=Network Group
+relation.network-group.user-friendly-plural-name=Network Groups
+relation.network-group.synopsis=The Network Group is used to classify incoming connections and route requests to workflows.
+relation.password-generator.user-friendly-name=Password Generator
+relation.password-generator.user-friendly-plural-name=Password Generators
+relation.password-generator.synopsis=Password Generators are used by the password modify extended operation to construct a new password for the user.
+relation.password-generator.description=The server allows any number of password validators to be defined. This can impose any kinds of restrictions on the characteristics of valid passwords. Therefore, it is not feasible for the server to attempt to generate a password on its own that will meet all the requirements of all the validators. The password generator makes it possible to provide custom logic for creating a new password.
+relation.password-policy.user-friendly-name=Password Policy
+relation.password-policy.user-friendly-plural-name=Password Policies
+relation.password-policy.synopsis=Password Policies define a number of password management rules, as well as requirements for authentication processing.
+relation.password-storage-scheme.user-friendly-name=Password Storage Scheme
+relation.password-storage-scheme.user-friendly-plural-name=Password Storage Schemes
+relation.password-storage-scheme.synopsis=Password Storage Schemes encode new passwords provided by users so that they are stored in an encoded manner. This makes it difficult or impossible for someone to determine the clear-text passwords from the encoded values.
+relation.password-storage-scheme.description=Password Storage Schemes also determine whether a clear-text password provided by a client matches the encoded value stored in the server.
+relation.password-validator.user-friendly-name=Password Validator
+relation.password-validator.user-friendly-plural-name=Password Validators
+relation.password-validator.synopsis=Password Validators are responsible for determining whether a proposed password is acceptable for use and could include checks like ensuring it meets minimum length requirements, that it has an appropriate range of characters, or that it is not in the history.
+relation.password-validator.description=The password policy for a user specifies the set of password validators that should be used whenever that user provides a new password. In order to activate a password validator, the corresponding configuration entry must be enabled, and the DN of that entry should be included in the password-validator attribute of the password policy in which you want that validator active. All password validator configuration entries must contain the password-validator structural objectclass.
+relation.plugin-root.user-friendly-name=Plugin Root
+relation.plugin-root.synopsis=The Plugin Root defines the parent entry for all plug-ins defined in the server.
+relation.plugin-root.description=It can also include configuration attributes that define the order in which those plug-ins are to be loaded and invoked.
+relation.root-dn.user-friendly-name=Root DN
+relation.root-dn.synopsis=The Root DN configuration contains all the Root DN Users defined in the Directory Server. In addition, it also defines the default set of privileges that Root DN Users automatically inherit.
+relation.root-dse-backend.user-friendly-name=Root DSE Backend
+relation.root-dse-backend.synopsis=The Root DSE Backend contains the Directory Server root DSE.
+relation.root-dse-backend.description=This is a special meta-backend that dynamically generates the root DSE entry for base-level searches and simply redirects to other backends for operations in other scopes.
+relation.sasl-mechanism-handler.user-friendly-name=SASL Mechanism Handler
+relation.sasl-mechanism-handler.user-friendly-plural-name=SASL Mechanism Handlers
+relation.sasl-mechanism-handler.synopsis=The SASL mechanism handler configuration entry is the parent for all SASL mechanism handlers defined in the OpenDS Directory Server.
+relation.sasl-mechanism-handler.description=SASL mechanism handlers are responsible for authenticating users during the course of processing a SASL (Simple Authentication and Security Layer, as defined in RFC 4422) bind.
+relation.synchronization-provider.user-friendly-name=Synchronization Provider
+relation.synchronization-provider.user-friendly-plural-name=Synchronization Providers
+relation.synchronization-provider.synopsis=Synchronization Providers are responsible for handling synchronization of the Directory Server data with other OpenDS instances or other data repositories.
+relation.synchronization-provider.description=The OpenDS Directory Server takes a centralized approach to replication, rather than the point-to-point approach taken by Sun Java System Directory Server. In OpenDS, one or more replication servers are created in the environment. The replication servers typically do not store user data but keep a log of all changes made within the topology. Each Directory Server instance in the topology is pointed at the replication servers. This plan simplifies the deployment and management of the environment. Although you can run the replication server on the same system (or even in the same instance) as the Directory Server, the two servers can be separated onto different systems. This approach can provide better performance or functionality in large environments.
+relation.trust-manager-provider.user-friendly-name=Trust Manager Provider
+relation.trust-manager-provider.user-friendly-plural-name=Trust Manager Providers
+relation.trust-manager-provider.synopsis=Trust Manager Providers determine whether to trust presented certificates.
+relation.virtual-attribute.user-friendly-name=Virtual Attribute
+relation.virtual-attribute.user-friendly-plural-name=Virtual Attributes
+relation.virtual-attribute.synopsis=Virtual Attributes are responsible for dynamically generating attribute values that appear in entries but are not persistently stored in the backend.
+relation.virtual-attribute.description=Virtual attributes are associated with a virtual attribute provider, which contains the logic for generating the value.
+relation.workflow.user-friendly-name=Workflow
+relation.workflow.user-friendly-plural-name=Workflows
+relation.workflow.synopsis=The Workflow is a list of processing steps (Work Flow Elements) that are applied to data as it is retrieved from the Directory Server.
+relation.workflow-element.user-friendly-name=Workflow Element
+relation.workflow-element.user-friendly-plural-name=Workflow Elements
+relation.workflow-element.synopsis=Workflow Elements implement a single processing step in a Work Flow.
+relation.workflow-element.description=A Workflow Element can perform a task such as mapping DNs, renaming attributes, filtering attributes, joining data sources, proxying, or load-balancing. The simplest Workflow Element is the Local Backend Work Flow Element, which routes data to a Backend.
+relation.work-queue.user-friendly-name=Work Queue
+relation.work-queue.synopsis=The Work Queue provides the configuration for the server work queue and is responsible for ensuring that requests received from clients are processed in a timely manner.
+relation.work-queue.description=Only a single work queue can be defined in the server. Whenever a connection handler receives a client request, it should place the request in the work queue to be processed appropriately.
diff --git a/opends/src/admin/messages/RootCfgDefn_de.properties b/opends/src/admin/messages/RootCfgDefn_de.properties
new file mode 100644
index 0000000..54efd5e
--- /dev/null
+++ b/opends/src/admin/messages/RootCfgDefn_de.properties
@@ -0,0 +1,127 @@
+user-friendly-name=Root
+user-friendly-plural-name=Roots
+synopsis=The root configuration provides an entry point to the rest of the OpenDS Directory Server configuration.
+tag.core-server.synopsis=Core server
+tag.database.synopsis=Caching and back-ends
+tag.logging.synopsis=Logging
+tag.replication.synopsis=Replication
+tag.security.synopsis=Authentication and authorization
+tag.user-management.synopsis=User management
+relation.access-control-handler.user-friendly-name=Access Control Handler
+relation.access-control-handler.synopsis=Access Control Handlers manage the application-wide access control. The OpenDS access control handler is defined through an extensible interface, so that alternate implementations can be created. Only one access control handler may be active in the server at any given time.
+relation.access-control-handler.description=Note that OpenDS also has a privilege subsystem, which may have an impact on what clients may be allowed to do in the server. For example, any user with the bypass-acl privilege is not subject to access control checking regardless of whether the access control implementation is enabled.
+relation.account-status-notification-handler.user-friendly-name=Account Status Notification Handler
+relation.account-status-notification-handler.user-friendly-plural-name=Account Status Notification Handlers
+relation.account-status-notification-handler.synopsis=Account Status Notification Handlers are invoked to provide notification to users in some form (for example, by an email message) when the status of a user's account has changed in some way. The Account Status Notification Handler can be used to notify the user and/or administrators of the change.
+relation.administration-connector.user-friendly-name=Administration Connector
+relation.administration-connector.synopsis=The Administration Connector is used to interact with administration tools using LDAP.
+relation.administration-connector.description=It is a dedicated entry point for administration.
+relation.alert-handler.user-friendly-name=Alert Handler
+relation.alert-handler.user-friendly-plural-name=Alert Handlers
+relation.alert-handler.synopsis=Alert Handlers are used to notify administrators of significant problems or notable events that occur in the Directory Server.
+relation.attribute-syntax.user-friendly-name=Attribute Syntax
+relation.attribute-syntax.user-friendly-plural-name=Attribute Syntaxes
+relation.attribute-syntax.synopsis=Attribute Syntaxes define the type of data that may be stored in an attribute with that syntax. A syntax is generally associated with a set of matching rules that indicate how to perform matching operations against values of that syntax.
+relation.backend.user-friendly-name=Backend
+relation.backend.user-friendly-plural-name=Backends
+relation.backend.synopsis=Backends are responsible for providing access to the underlying data presented by the server.
+relation.backend.description=The data may be stored locally in an embedded database, remotely in an external system, or generated on the fly (for example, calculated from other information that is available).
+relation.certificate-mapper.user-friendly-name=Certificate Mapper
+relation.certificate-mapper.user-friendly-plural-name=Certificate Mappers
+relation.certificate-mapper.synopsis=Certificate Mappers are responsible for establishing a mapping between a client certificate and the entry for the user that corresponds to that certificate.
+relation.connection-handler.user-friendly-name=Connection Handler
+relation.connection-handler.user-friendly-plural-name=Connection Handlers
+relation.connection-handler.synopsis=Connection Handlers are responsible for handling all interaction with the clients, including accepting the connections, reading requests, and sending responses.
+relation.crypto-manager.user-friendly-name=Crypto Manager
+relation.crypto-manager.synopsis=The Crypto Manager provides a common interface for performing compression, decompression, hashing, encryption and other kinds of cryptographic operations.
+relation.entry-cache.user-friendly-name=Entry Cache
+relation.entry-cache.user-friendly-plural-name=Entry Caches
+relation.entry-cache.synopsis=Entry Caches are responsible for caching entries which are likely to be accessed by client applications in order to improve Directory Server performance.
+relation.extended-operation-handler.user-friendly-name=Extended Operation Handler
+relation.extended-operation-handler.user-friendly-plural-name=Extended Operation Handlers
+relation.extended-operation-handler.synopsis=Extended Operation Handlers processes the different types of extended operations in the server.
+relation.extension.user-friendly-name=Extension
+relation.extension.user-friendly-plural-name=Extensions
+relation.extension.synopsis=The Extension allows to extend the configuration with new type of objects.
+relation.extension.description=It is an entry point for extensions that requires configuration objects that does not inherit from an existing top-level object.
+relation.global-configuration.user-friendly-name=Global Configuration
+relation.global-configuration.synopsis=The Global contains properties that affect the overall operation of the OpenDS Directory Server .
+relation.group-implementation.user-friendly-name=Group Implementation
+relation.group-implementation.user-friendly-plural-name=Group Implementations
+relation.group-implementation.synopsis=Group Implementations define named collections of users.
+relation.group-implementation.description=Different group implementations may have different ways of determining membership. For example, some groups may explicitly list the members, and/or they may dynamically determine membership.
+relation.identity-mapper.user-friendly-name=Identity Mapper
+relation.identity-mapper.user-friendly-plural-name=Identity Mappers
+relation.identity-mapper.synopsis=Identity Mappers are responsible for establishing a mapping between an identifier string provided by a client, and the entry for the user that corresponds to that identifier. Identity Mappers are used to process several SASL mechanisms to map an authorization ID (e.g., a Kerberos principal when using GSSAPI) to a directory user. They are also used when processing requests with the proxied authorization control.
+relation.key-manager-provider.user-friendly-name=Key Manager Provider
+relation.key-manager-provider.user-friendly-plural-name=Key Manager Providers
+relation.key-manager-provider.synopsis=Key Manager Providers are responsible for managing the key material that is used to authenticate an SSL connection to its peer.
+relation.key-manager-provider.description=Key Manager Providers essentially provide access to the certificate that is used by the server when performing SSL or StartTLS negotiation.
+relation.log-publisher.user-friendly-name=Log Publisher
+relation.log-publisher.user-friendly-plural-name=Log Publishers
+relation.log-publisher.synopsis=Log Publishers are responsible for distributing log messages from different loggers to a destination.
+relation.log-retention-policy.user-friendly-name=Log Retention Policy
+relation.log-retention-policy.user-friendly-plural-name=Log Retention Policies
+relation.log-retention-policy.synopsis=Log Retention Policies are used to specify when log files should be cleaned.
+relation.log-rotation-policy.user-friendly-name=Log Rotation Policy
+relation.log-rotation-policy.user-friendly-plural-name=Log Rotation Policies
+relation.log-rotation-policy.synopsis=Log Rotation Policies are used to specify when log files should be rotated.
+relation.matching-rule.user-friendly-name=Matching Rule
+relation.matching-rule.user-friendly-plural-name=Matching Rules
+relation.matching-rule.synopsis=Matching Rules define a set of rules for performing matching operations against assertion values.
+relation.matching-rule.description=Matching rules are frequently associated with an attribute syntax and are used to compare values according to that syntax. For example, the distinguishedNameEqualityMatch matching rule can be used to determine whether two DNs are equal and can ignore unnecessary spaces around commas and equal signs, differences in capitalization in attribute names, an so on.
+relation.monitor-provider.user-friendly-name=Monitor Provider
+relation.monitor-provider.user-friendly-plural-name=Monitor Providers
+relation.monitor-provider.synopsis=Monitor Providers can be used to provide information about the state of the server or one of its components.
+relation.monitor-provider.description=This information is useful for monitoring or troubleshooting.
+relation.network-group.user-friendly-name=Network Group
+relation.network-group.user-friendly-plural-name=Network Groups
+relation.network-group.synopsis=The Network Group is used to classify incoming connections and route requests to workflows.
+relation.password-generator.user-friendly-name=Password Generator
+relation.password-generator.user-friendly-plural-name=Password Generators
+relation.password-generator.synopsis=Password Generators are used by the password modify extended operation to construct a new password for the user.
+relation.password-generator.description=The server allows any number of password validators to be defined. This can impose any kinds of restrictions on the characteristics of valid passwords. Therefore, it is not feasible for the server to attempt to generate a password on its own that will meet all the requirements of all the validators. The password generator makes it possible to provide custom logic for creating a new password.
+relation.password-policy.user-friendly-name=Password Policy
+relation.password-policy.user-friendly-plural-name=Password Policies
+relation.password-policy.synopsis=Password Policies define a number of password management rules, as well as requirements for authentication processing.
+relation.password-storage-scheme.user-friendly-name=Password Storage Scheme
+relation.password-storage-scheme.user-friendly-plural-name=Password Storage Schemes
+relation.password-storage-scheme.synopsis=Password Storage Schemes encode new passwords provided by users so that they are stored in an encoded manner. This makes it difficult or impossible for someone to determine the clear-text passwords from the encoded values.
+relation.password-storage-scheme.description=Password Storage Schemes also determine whether a clear-text password provided by a client matches the encoded value stored in the server.
+relation.password-validator.user-friendly-name=Password Validator
+relation.password-validator.user-friendly-plural-name=Password Validators
+relation.password-validator.synopsis=Password Validators are responsible for determining whether a proposed password is acceptable for use and could include checks like ensuring it meets minimum length requirements, that it has an appropriate range of characters, or that it is not in the history.
+relation.password-validator.description=The password policy for a user specifies the set of password validators that should be used whenever that user provides a new password. In order to activate a password validator, the corresponding configuration entry must be enabled, and the DN of that entry should be included in the password-validator attribute of the password policy in which you want that validator active. All password validator configuration entries must contain the password-validator structural objectclass.
+relation.plugin-root.user-friendly-name=Plugin Root
+relation.plugin-root.synopsis=The Plugin Root defines the parent entry for all plug-ins defined in the server.
+relation.plugin-root.description=It can also include configuration attributes that define the order in which those plug-ins are to be loaded and invoked.
+relation.root-dn.user-friendly-name=Root DN
+relation.root-dn.synopsis=The Root DN configuration contains all the Root DN Users defined in the Directory Server. In addition, it also defines the default set of privileges that Root DN Users automatically inherit.
+relation.root-dse-backend.user-friendly-name=Root DSE Backend
+relation.root-dse-backend.synopsis=The Root DSE Backend contains the Directory Server root DSE.
+relation.root-dse-backend.description=This is a special meta-backend that dynamically generates the root DSE entry for base-level searches and simply redirects to other backends for operations in other scopes.
+relation.sasl-mechanism-handler.user-friendly-name=SASL Mechanism Handler
+relation.sasl-mechanism-handler.user-friendly-plural-name=SASL Mechanism Handlers
+relation.sasl-mechanism-handler.synopsis=The SASL mechanism handler configuration entry is the parent for all SASL mechanism handlers defined in the OpenDS Directory Server.
+relation.sasl-mechanism-handler.description=SASL mechanism handlers are responsible for authenticating users during the course of processing a SASL (Simple Authentication and Security Layer, as defined in RFC 4422) bind.
+relation.synchronization-provider.user-friendly-name=Synchronization Provider
+relation.synchronization-provider.user-friendly-plural-name=Synchronization Providers
+relation.synchronization-provider.synopsis=Synchronization Providers are responsible for handling synchronization of the Directory Server data with other OpenDS instances or other data repositories.
+relation.synchronization-provider.description=The OpenDS Directory Server takes a centralized approach to replication, rather than the point-to-point approach taken by Sun Java System Directory Server. In OpenDS, one or more replication servers are created in the environment. The replication servers typically do not store user data but keep a log of all changes made within the topology. Each Directory Server instance in the topology is pointed at the replication servers. This plan simplifies the deployment and management of the environment. Although you can run the replication server on the same system (or even in the same instance) as the Directory Server, the two servers can be separated onto different systems. This approach can provide better performance or functionality in large environments.
+relation.trust-manager-provider.user-friendly-name=Trust Manager Provider
+relation.trust-manager-provider.user-friendly-plural-name=Trust Manager Providers
+relation.trust-manager-provider.synopsis=Trust Manager Providers determine whether to trust presented certificates.
+relation.virtual-attribute.user-friendly-name=Virtual Attribute
+relation.virtual-attribute.user-friendly-plural-name=Virtual Attributes
+relation.virtual-attribute.synopsis=Virtual Attributes are responsible for dynamically generating attribute values that appear in entries but are not persistently stored in the backend.
+relation.virtual-attribute.description=Virtual attributes are associated with a virtual attribute provider, which contains the logic for generating the value.
+relation.workflow.user-friendly-name=Workflow
+relation.workflow.user-friendly-plural-name=Workflows
+relation.workflow.synopsis=The Workflow is a list of processing steps (Work Flow Elements) that are applied to data as it is retrieved from the Directory Server.
+relation.workflow-element.user-friendly-name=Workflow Element
+relation.workflow-element.user-friendly-plural-name=Workflow Elements
+relation.workflow-element.synopsis=Workflow Elements implement a single processing step in a Work Flow.
+relation.workflow-element.description=A Workflow Element can perform a task such as mapping DNs, renaming attributes, filtering attributes, joining data sources, proxying, or load-balancing. The simplest Workflow Element is the Local Backend Work Flow Element, which routes data to a Backend.
+relation.work-queue.user-friendly-name=Work Queue
+relation.work-queue.synopsis=The Work Queue provides the configuration for the server work queue and is responsible for ensuring that requests received from clients are processed in a timely manner.
+relation.work-queue.description=Only a single work queue can be defined in the server. Whenever a connection handler receives a client request, it should place the request in the work queue to be processed appropriately.
diff --git a/opends/src/admin/messages/RootCfgDefn_es.properties b/opends/src/admin/messages/RootCfgDefn_es.properties
new file mode 100644
index 0000000..54efd5e
--- /dev/null
+++ b/opends/src/admin/messages/RootCfgDefn_es.properties
@@ -0,0 +1,127 @@
+user-friendly-name=Root
+user-friendly-plural-name=Roots
+synopsis=The root configuration provides an entry point to the rest of the OpenDS Directory Server configuration.
+tag.core-server.synopsis=Core server
+tag.database.synopsis=Caching and back-ends
+tag.logging.synopsis=Logging
+tag.replication.synopsis=Replication
+tag.security.synopsis=Authentication and authorization
+tag.user-management.synopsis=User management
+relation.access-control-handler.user-friendly-name=Access Control Handler
+relation.access-control-handler.synopsis=Access Control Handlers manage the application-wide access control. The OpenDS access control handler is defined through an extensible interface, so that alternate implementations can be created. Only one access control handler may be active in the server at any given time.
+relation.access-control-handler.description=Note that OpenDS also has a privilege subsystem, which may have an impact on what clients may be allowed to do in the server. For example, any user with the bypass-acl privilege is not subject to access control checking regardless of whether the access control implementation is enabled.
+relation.account-status-notification-handler.user-friendly-name=Account Status Notification Handler
+relation.account-status-notification-handler.user-friendly-plural-name=Account Status Notification Handlers
+relation.account-status-notification-handler.synopsis=Account Status Notification Handlers are invoked to provide notification to users in some form (for example, by an email message) when the status of a user's account has changed in some way. The Account Status Notification Handler can be used to notify the user and/or administrators of the change.
+relation.administration-connector.user-friendly-name=Administration Connector
+relation.administration-connector.synopsis=The Administration Connector is used to interact with administration tools using LDAP.
+relation.administration-connector.description=It is a dedicated entry point for administration.
+relation.alert-handler.user-friendly-name=Alert Handler
+relation.alert-handler.user-friendly-plural-name=Alert Handlers
+relation.alert-handler.synopsis=Alert Handlers are used to notify administrators of significant problems or notable events that occur in the Directory Server.
+relation.attribute-syntax.user-friendly-name=Attribute Syntax
+relation.attribute-syntax.user-friendly-plural-name=Attribute Syntaxes
+relation.attribute-syntax.synopsis=Attribute Syntaxes define the type of data that may be stored in an attribute with that syntax. A syntax is generally associated with a set of matching rules that indicate how to perform matching operations against values of that syntax.
+relation.backend.user-friendly-name=Backend
+relation.backend.user-friendly-plural-name=Backends
+relation.backend.synopsis=Backends are responsible for providing access to the underlying data presented by the server.
+relation.backend.description=The data may be stored locally in an embedded database, remotely in an external system, or generated on the fly (for example, calculated from other information that is available).
+relation.certificate-mapper.user-friendly-name=Certificate Mapper
+relation.certificate-mapper.user-friendly-plural-name=Certificate Mappers
+relation.certificate-mapper.synopsis=Certificate Mappers are responsible for establishing a mapping between a client certificate and the entry for the user that corresponds to that certificate.
+relation.connection-handler.user-friendly-name=Connection Handler
+relation.connection-handler.user-friendly-plural-name=Connection Handlers
+relation.connection-handler.synopsis=Connection Handlers are responsible for handling all interaction with the clients, including accepting the connections, reading requests, and sending responses.
+relation.crypto-manager.user-friendly-name=Crypto Manager
+relation.crypto-manager.synopsis=The Crypto Manager provides a common interface for performing compression, decompression, hashing, encryption and other kinds of cryptographic operations.
+relation.entry-cache.user-friendly-name=Entry Cache
+relation.entry-cache.user-friendly-plural-name=Entry Caches
+relation.entry-cache.synopsis=Entry Caches are responsible for caching entries which are likely to be accessed by client applications in order to improve Directory Server performance.
+relation.extended-operation-handler.user-friendly-name=Extended Operation Handler
+relation.extended-operation-handler.user-friendly-plural-name=Extended Operation Handlers
+relation.extended-operation-handler.synopsis=Extended Operation Handlers processes the different types of extended operations in the server.
+relation.extension.user-friendly-name=Extension
+relation.extension.user-friendly-plural-name=Extensions
+relation.extension.synopsis=The Extension allows to extend the configuration with new type of objects.
+relation.extension.description=It is an entry point for extensions that requires configuration objects that does not inherit from an existing top-level object.
+relation.global-configuration.user-friendly-name=Global Configuration
+relation.global-configuration.synopsis=The Global contains properties that affect the overall operation of the OpenDS Directory Server .
+relation.group-implementation.user-friendly-name=Group Implementation
+relation.group-implementation.user-friendly-plural-name=Group Implementations
+relation.group-implementation.synopsis=Group Implementations define named collections of users.
+relation.group-implementation.description=Different group implementations may have different ways of determining membership. For example, some groups may explicitly list the members, and/or they may dynamically determine membership.
+relation.identity-mapper.user-friendly-name=Identity Mapper
+relation.identity-mapper.user-friendly-plural-name=Identity Mappers
+relation.identity-mapper.synopsis=Identity Mappers are responsible for establishing a mapping between an identifier string provided by a client, and the entry for the user that corresponds to that identifier. Identity Mappers are used to process several SASL mechanisms to map an authorization ID (e.g., a Kerberos principal when using GSSAPI) to a directory user. They are also used when processing requests with the proxied authorization control.
+relation.key-manager-provider.user-friendly-name=Key Manager Provider
+relation.key-manager-provider.user-friendly-plural-name=Key Manager Providers
+relation.key-manager-provider.synopsis=Key Manager Providers are responsible for managing the key material that is used to authenticate an SSL connection to its peer.
+relation.key-manager-provider.description=Key Manager Providers essentially provide access to the certificate that is used by the server when performing SSL or StartTLS negotiation.
+relation.log-publisher.user-friendly-name=Log Publisher
+relation.log-publisher.user-friendly-plural-name=Log Publishers
+relation.log-publisher.synopsis=Log Publishers are responsible for distributing log messages from different loggers to a destination.
+relation.log-retention-policy.user-friendly-name=Log Retention Policy
+relation.log-retention-policy.user-friendly-plural-name=Log Retention Policies
+relation.log-retention-policy.synopsis=Log Retention Policies are used to specify when log files should be cleaned.
+relation.log-rotation-policy.user-friendly-name=Log Rotation Policy
+relation.log-rotation-policy.user-friendly-plural-name=Log Rotation Policies
+relation.log-rotation-policy.synopsis=Log Rotation Policies are used to specify when log files should be rotated.
+relation.matching-rule.user-friendly-name=Matching Rule
+relation.matching-rule.user-friendly-plural-name=Matching Rules
+relation.matching-rule.synopsis=Matching Rules define a set of rules for performing matching operations against assertion values.
+relation.matching-rule.description=Matching rules are frequently associated with an attribute syntax and are used to compare values according to that syntax. For example, the distinguishedNameEqualityMatch matching rule can be used to determine whether two DNs are equal and can ignore unnecessary spaces around commas and equal signs, differences in capitalization in attribute names, an so on.
+relation.monitor-provider.user-friendly-name=Monitor Provider
+relation.monitor-provider.user-friendly-plural-name=Monitor Providers
+relation.monitor-provider.synopsis=Monitor Providers can be used to provide information about the state of the server or one of its components.
+relation.monitor-provider.description=This information is useful for monitoring or troubleshooting.
+relation.network-group.user-friendly-name=Network Group
+relation.network-group.user-friendly-plural-name=Network Groups
+relation.network-group.synopsis=The Network Group is used to classify incoming connections and route requests to workflows.
+relation.password-generator.user-friendly-name=Password Generator
+relation.password-generator.user-friendly-plural-name=Password Generators
+relation.password-generator.synopsis=Password Generators are used by the password modify extended operation to construct a new password for the user.
+relation.password-generator.description=The server allows any number of password validators to be defined. This can impose any kinds of restrictions on the characteristics of valid passwords. Therefore, it is not feasible for the server to attempt to generate a password on its own that will meet all the requirements of all the validators. The password generator makes it possible to provide custom logic for creating a new password.
+relation.password-policy.user-friendly-name=Password Policy
+relation.password-policy.user-friendly-plural-name=Password Policies
+relation.password-policy.synopsis=Password Policies define a number of password management rules, as well as requirements for authentication processing.
+relation.password-storage-scheme.user-friendly-name=Password Storage Scheme
+relation.password-storage-scheme.user-friendly-plural-name=Password Storage Schemes
+relation.password-storage-scheme.synopsis=Password Storage Schemes encode new passwords provided by users so that they are stored in an encoded manner. This makes it difficult or impossible for someone to determine the clear-text passwords from the encoded values.
+relation.password-storage-scheme.description=Password Storage Schemes also determine whether a clear-text password provided by a client matches the encoded value stored in the server.
+relation.password-validator.user-friendly-name=Password Validator
+relation.password-validator.user-friendly-plural-name=Password Validators
+relation.password-validator.synopsis=Password Validators are responsible for determining whether a proposed password is acceptable for use and could include checks like ensuring it meets minimum length requirements, that it has an appropriate range of characters, or that it is not in the history.
+relation.password-validator.description=The password policy for a user specifies the set of password validators that should be used whenever that user provides a new password. In order to activate a password validator, the corresponding configuration entry must be enabled, and the DN of that entry should be included in the password-validator attribute of the password policy in which you want that validator active. All password validator configuration entries must contain the password-validator structural objectclass.
+relation.plugin-root.user-friendly-name=Plugin Root
+relation.plugin-root.synopsis=The Plugin Root defines the parent entry for all plug-ins defined in the server.
+relation.plugin-root.description=It can also include configuration attributes that define the order in which those plug-ins are to be loaded and invoked.
+relation.root-dn.user-friendly-name=Root DN
+relation.root-dn.synopsis=The Root DN configuration contains all the Root DN Users defined in the Directory Server. In addition, it also defines the default set of privileges that Root DN Users automatically inherit.
+relation.root-dse-backend.user-friendly-name=Root DSE Backend
+relation.root-dse-backend.synopsis=The Root DSE Backend contains the Directory Server root DSE.
+relation.root-dse-backend.description=This is a special meta-backend that dynamically generates the root DSE entry for base-level searches and simply redirects to other backends for operations in other scopes.
+relation.sasl-mechanism-handler.user-friendly-name=SASL Mechanism Handler
+relation.sasl-mechanism-handler.user-friendly-plural-name=SASL Mechanism Handlers
+relation.sasl-mechanism-handler.synopsis=The SASL mechanism handler configuration entry is the parent for all SASL mechanism handlers defined in the OpenDS Directory Server.
+relation.sasl-mechanism-handler.description=SASL mechanism handlers are responsible for authenticating users during the course of processing a SASL (Simple Authentication and Security Layer, as defined in RFC 4422) bind.
+relation.synchronization-provider.user-friendly-name=Synchronization Provider
+relation.synchronization-provider.user-friendly-plural-name=Synchronization Providers
+relation.synchronization-provider.synopsis=Synchronization Providers are responsible for handling synchronization of the Directory Server data with other OpenDS instances or other data repositories.
+relation.synchronization-provider.description=The OpenDS Directory Server takes a centralized approach to replication, rather than the point-to-point approach taken by Sun Java System Directory Server. In OpenDS, one or more replication servers are created in the environment. The replication servers typically do not store user data but keep a log of all changes made within the topology. Each Directory Server instance in the topology is pointed at the replication servers. This plan simplifies the deployment and management of the environment. Although you can run the replication server on the same system (or even in the same instance) as the Directory Server, the two servers can be separated onto different systems. This approach can provide better performance or functionality in large environments.
+relation.trust-manager-provider.user-friendly-name=Trust Manager Provider
+relation.trust-manager-provider.user-friendly-plural-name=Trust Manager Providers
+relation.trust-manager-provider.synopsis=Trust Manager Providers determine whether to trust presented certificates.
+relation.virtual-attribute.user-friendly-name=Virtual Attribute
+relation.virtual-attribute.user-friendly-plural-name=Virtual Attributes
+relation.virtual-attribute.synopsis=Virtual Attributes are responsible for dynamically generating attribute values that appear in entries but are not persistently stored in the backend.
+relation.virtual-attribute.description=Virtual attributes are associated with a virtual attribute provider, which contains the logic for generating the value.
+relation.workflow.user-friendly-name=Workflow
+relation.workflow.user-friendly-plural-name=Workflows
+relation.workflow.synopsis=The Workflow is a list of processing steps (Work Flow Elements) that are applied to data as it is retrieved from the Directory Server.
+relation.workflow-element.user-friendly-name=Workflow Element
+relation.workflow-element.user-friendly-plural-name=Workflow Elements
+relation.workflow-element.synopsis=Workflow Elements implement a single processing step in a Work Flow.
+relation.workflow-element.description=A Workflow Element can perform a task such as mapping DNs, renaming attributes, filtering attributes, joining data sources, proxying, or load-balancing. The simplest Workflow Element is the Local Backend Work Flow Element, which routes data to a Backend.
+relation.work-queue.user-friendly-name=Work Queue
+relation.work-queue.synopsis=The Work Queue provides the configuration for the server work queue and is responsible for ensuring that requests received from clients are processed in a timely manner.
+relation.work-queue.description=Only a single work queue can be defined in the server. Whenever a connection handler receives a client request, it should place the request in the work queue to be processed appropriately.
diff --git a/opends/src/admin/messages/RootCfgDefn_fr.properties b/opends/src/admin/messages/RootCfgDefn_fr.properties
new file mode 100644
index 0000000..54efd5e
--- /dev/null
+++ b/opends/src/admin/messages/RootCfgDefn_fr.properties
@@ -0,0 +1,127 @@
+user-friendly-name=Root
+user-friendly-plural-name=Roots
+synopsis=The root configuration provides an entry point to the rest of the OpenDS Directory Server configuration.
+tag.core-server.synopsis=Core server
+tag.database.synopsis=Caching and back-ends
+tag.logging.synopsis=Logging
+tag.replication.synopsis=Replication
+tag.security.synopsis=Authentication and authorization
+tag.user-management.synopsis=User management
+relation.access-control-handler.user-friendly-name=Access Control Handler
+relation.access-control-handler.synopsis=Access Control Handlers manage the application-wide access control. The OpenDS access control handler is defined through an extensible interface, so that alternate implementations can be created. Only one access control handler may be active in the server at any given time.
+relation.access-control-handler.description=Note that OpenDS also has a privilege subsystem, which may have an impact on what clients may be allowed to do in the server. For example, any user with the bypass-acl privilege is not subject to access control checking regardless of whether the access control implementation is enabled.
+relation.account-status-notification-handler.user-friendly-name=Account Status Notification Handler
+relation.account-status-notification-handler.user-friendly-plural-name=Account Status Notification Handlers
+relation.account-status-notification-handler.synopsis=Account Status Notification Handlers are invoked to provide notification to users in some form (for example, by an email message) when the status of a user's account has changed in some way. The Account Status Notification Handler can be used to notify the user and/or administrators of the change.
+relation.administration-connector.user-friendly-name=Administration Connector
+relation.administration-connector.synopsis=The Administration Connector is used to interact with administration tools using LDAP.
+relation.administration-connector.description=It is a dedicated entry point for administration.
+relation.alert-handler.user-friendly-name=Alert Handler
+relation.alert-handler.user-friendly-plural-name=Alert Handlers
+relation.alert-handler.synopsis=Alert Handlers are used to notify administrators of significant problems or notable events that occur in the Directory Server.
+relation.attribute-syntax.user-friendly-name=Attribute Syntax
+relation.attribute-syntax.user-friendly-plural-name=Attribute Syntaxes
+relation.attribute-syntax.synopsis=Attribute Syntaxes define the type of data that may be stored in an attribute with that syntax. A syntax is generally associated with a set of matching rules that indicate how to perform matching operations against values of that syntax.
+relation.backend.user-friendly-name=Backend
+relation.backend.user-friendly-plural-name=Backends
+relation.backend.synopsis=Backends are responsible for providing access to the underlying data presented by the server.
+relation.backend.description=The data may be stored locally in an embedded database, remotely in an external system, or generated on the fly (for example, calculated from other information that is available).
+relation.certificate-mapper.user-friendly-name=Certificate Mapper
+relation.certificate-mapper.user-friendly-plural-name=Certificate Mappers
+relation.certificate-mapper.synopsis=Certificate Mappers are responsible for establishing a mapping between a client certificate and the entry for the user that corresponds to that certificate.
+relation.connection-handler.user-friendly-name=Connection Handler
+relation.connection-handler.user-friendly-plural-name=Connection Handlers
+relation.connection-handler.synopsis=Connection Handlers are responsible for handling all interaction with the clients, including accepting the connections, reading requests, and sending responses.
+relation.crypto-manager.user-friendly-name=Crypto Manager
+relation.crypto-manager.synopsis=The Crypto Manager provides a common interface for performing compression, decompression, hashing, encryption and other kinds of cryptographic operations.
+relation.entry-cache.user-friendly-name=Entry Cache
+relation.entry-cache.user-friendly-plural-name=Entry Caches
+relation.entry-cache.synopsis=Entry Caches are responsible for caching entries which are likely to be accessed by client applications in order to improve Directory Server performance.
+relation.extended-operation-handler.user-friendly-name=Extended Operation Handler
+relation.extended-operation-handler.user-friendly-plural-name=Extended Operation Handlers
+relation.extended-operation-handler.synopsis=Extended Operation Handlers processes the different types of extended operations in the server.
+relation.extension.user-friendly-name=Extension
+relation.extension.user-friendly-plural-name=Extensions
+relation.extension.synopsis=The Extension allows to extend the configuration with new type of objects.
+relation.extension.description=It is an entry point for extensions that requires configuration objects that does not inherit from an existing top-level object.
+relation.global-configuration.user-friendly-name=Global Configuration
+relation.global-configuration.synopsis=The Global contains properties that affect the overall operation of the OpenDS Directory Server .
+relation.group-implementation.user-friendly-name=Group Implementation
+relation.group-implementation.user-friendly-plural-name=Group Implementations
+relation.group-implementation.synopsis=Group Implementations define named collections of users.
+relation.group-implementation.description=Different group implementations may have different ways of determining membership. For example, some groups may explicitly list the members, and/or they may dynamically determine membership.
+relation.identity-mapper.user-friendly-name=Identity Mapper
+relation.identity-mapper.user-friendly-plural-name=Identity Mappers
+relation.identity-mapper.synopsis=Identity Mappers are responsible for establishing a mapping between an identifier string provided by a client, and the entry for the user that corresponds to that identifier. Identity Mappers are used to process several SASL mechanisms to map an authorization ID (e.g., a Kerberos principal when using GSSAPI) to a directory user. They are also used when processing requests with the proxied authorization control.
+relation.key-manager-provider.user-friendly-name=Key Manager Provider
+relation.key-manager-provider.user-friendly-plural-name=Key Manager Providers
+relation.key-manager-provider.synopsis=Key Manager Providers are responsible for managing the key material that is used to authenticate an SSL connection to its peer.
+relation.key-manager-provider.description=Key Manager Providers essentially provide access to the certificate that is used by the server when performing SSL or StartTLS negotiation.
+relation.log-publisher.user-friendly-name=Log Publisher
+relation.log-publisher.user-friendly-plural-name=Log Publishers
+relation.log-publisher.synopsis=Log Publishers are responsible for distributing log messages from different loggers to a destination.
+relation.log-retention-policy.user-friendly-name=Log Retention Policy
+relation.log-retention-policy.user-friendly-plural-name=Log Retention Policies
+relation.log-retention-policy.synopsis=Log Retention Policies are used to specify when log files should be cleaned.
+relation.log-rotation-policy.user-friendly-name=Log Rotation Policy
+relation.log-rotation-policy.user-friendly-plural-name=Log Rotation Policies
+relation.log-rotation-policy.synopsis=Log Rotation Policies are used to specify when log files should be rotated.
+relation.matching-rule.user-friendly-name=Matching Rule
+relation.matching-rule.user-friendly-plural-name=Matching Rules
+relation.matching-rule.synopsis=Matching Rules define a set of rules for performing matching operations against assertion values.
+relation.matching-rule.description=Matching rules are frequently associated with an attribute syntax and are used to compare values according to that syntax. For example, the distinguishedNameEqualityMatch matching rule can be used to determine whether two DNs are equal and can ignore unnecessary spaces around commas and equal signs, differences in capitalization in attribute names, an so on.
+relation.monitor-provider.user-friendly-name=Monitor Provider
+relation.monitor-provider.user-friendly-plural-name=Monitor Providers
+relation.monitor-provider.synopsis=Monitor Providers can be used to provide information about the state of the server or one of its components.
+relation.monitor-provider.description=This information is useful for monitoring or troubleshooting.
+relation.network-group.user-friendly-name=Network Group
+relation.network-group.user-friendly-plural-name=Network Groups
+relation.network-group.synopsis=The Network Group is used to classify incoming connections and route requests to workflows.
+relation.password-generator.user-friendly-name=Password Generator
+relation.password-generator.user-friendly-plural-name=Password Generators
+relation.password-generator.synopsis=Password Generators are used by the password modify extended operation to construct a new password for the user.
+relation.password-generator.description=The server allows any number of password validators to be defined. This can impose any kinds of restrictions on the characteristics of valid passwords. Therefore, it is not feasible for the server to attempt to generate a password on its own that will meet all the requirements of all the validators. The password generator makes it possible to provide custom logic for creating a new password.
+relation.password-policy.user-friendly-name=Password Policy
+relation.password-policy.user-friendly-plural-name=Password Policies
+relation.password-policy.synopsis=Password Policies define a number of password management rules, as well as requirements for authentication processing.
+relation.password-storage-scheme.user-friendly-name=Password Storage Scheme
+relation.password-storage-scheme.user-friendly-plural-name=Password Storage Schemes
+relation.password-storage-scheme.synopsis=Password Storage Schemes encode new passwords provided by users so that they are stored in an encoded manner. This makes it difficult or impossible for someone to determine the clear-text passwords from the encoded values.
+relation.password-storage-scheme.description=Password Storage Schemes also determine whether a clear-text password provided by a client matches the encoded value stored in the server.
+relation.password-validator.user-friendly-name=Password Validator
+relation.password-validator.user-friendly-plural-name=Password Validators
+relation.password-validator.synopsis=Password Validators are responsible for determining whether a proposed password is acceptable for use and could include checks like ensuring it meets minimum length requirements, that it has an appropriate range of characters, or that it is not in the history.
+relation.password-validator.description=The password policy for a user specifies the set of password validators that should be used whenever that user provides a new password. In order to activate a password validator, the corresponding configuration entry must be enabled, and the DN of that entry should be included in the password-validator attribute of the password policy in which you want that validator active. All password validator configuration entries must contain the password-validator structural objectclass.
+relation.plugin-root.user-friendly-name=Plugin Root
+relation.plugin-root.synopsis=The Plugin Root defines the parent entry for all plug-ins defined in the server.
+relation.plugin-root.description=It can also include configuration attributes that define the order in which those plug-ins are to be loaded and invoked.
+relation.root-dn.user-friendly-name=Root DN
+relation.root-dn.synopsis=The Root DN configuration contains all the Root DN Users defined in the Directory Server. In addition, it also defines the default set of privileges that Root DN Users automatically inherit.
+relation.root-dse-backend.user-friendly-name=Root DSE Backend
+relation.root-dse-backend.synopsis=The Root DSE Backend contains the Directory Server root DSE.
+relation.root-dse-backend.description=This is a special meta-backend that dynamically generates the root DSE entry for base-level searches and simply redirects to other backends for operations in other scopes.
+relation.sasl-mechanism-handler.user-friendly-name=SASL Mechanism Handler
+relation.sasl-mechanism-handler.user-friendly-plural-name=SASL Mechanism Handlers
+relation.sasl-mechanism-handler.synopsis=The SASL mechanism handler configuration entry is the parent for all SASL mechanism handlers defined in the OpenDS Directory Server.
+relation.sasl-mechanism-handler.description=SASL mechanism handlers are responsible for authenticating users during the course of processing a SASL (Simple Authentication and Security Layer, as defined in RFC 4422) bind.
+relation.synchronization-provider.user-friendly-name=Synchronization Provider
+relation.synchronization-provider.user-friendly-plural-name=Synchronization Providers
+relation.synchronization-provider.synopsis=Synchronization Providers are responsible for handling synchronization of the Directory Server data with other OpenDS instances or other data repositories.
+relation.synchronization-provider.description=The OpenDS Directory Server takes a centralized approach to replication, rather than the point-to-point approach taken by Sun Java System Directory Server. In OpenDS, one or more replication servers are created in the environment. The replication servers typically do not store user data but keep a log of all changes made within the topology. Each Directory Server instance in the topology is pointed at the replication servers. This plan simplifies the deployment and management of the environment. Although you can run the replication server on the same system (or even in the same instance) as the Directory Server, the two servers can be separated onto different systems. This approach can provide better performance or functionality in large environments.
+relation.trust-manager-provider.user-friendly-name=Trust Manager Provider
+relation.trust-manager-provider.user-friendly-plural-name=Trust Manager Providers
+relation.trust-manager-provider.synopsis=Trust Manager Providers determine whether to trust presented certificates.
+relation.virtual-attribute.user-friendly-name=Virtual Attribute
+relation.virtual-attribute.user-friendly-plural-name=Virtual Attributes
+relation.virtual-attribute.synopsis=Virtual Attributes are responsible for dynamically generating attribute values that appear in entries but are not persistently stored in the backend.
+relation.virtual-attribute.description=Virtual attributes are associated with a virtual attribute provider, which contains the logic for generating the value.
+relation.workflow.user-friendly-name=Workflow
+relation.workflow.user-friendly-plural-name=Workflows
+relation.workflow.synopsis=The Workflow is a list of processing steps (Work Flow Elements) that are applied to data as it is retrieved from the Directory Server.
+relation.workflow-element.user-friendly-name=Workflow Element
+relation.workflow-element.user-friendly-plural-name=Workflow Elements
+relation.workflow-element.synopsis=Workflow Elements implement a single processing step in a Work Flow.
+relation.workflow-element.description=A Workflow Element can perform a task such as mapping DNs, renaming attributes, filtering attributes, joining data sources, proxying, or load-balancing. The simplest Workflow Element is the Local Backend Work Flow Element, which routes data to a Backend.
+relation.work-queue.user-friendly-name=Work Queue
+relation.work-queue.synopsis=The Work Queue provides the configuration for the server work queue and is responsible for ensuring that requests received from clients are processed in a timely manner.
+relation.work-queue.description=Only a single work queue can be defined in the server. Whenever a connection handler receives a client request, it should place the request in the work queue to be processed appropriately.
diff --git a/opends/src/admin/messages/RootCfgDefn_ja.properties b/opends/src/admin/messages/RootCfgDefn_ja.properties
new file mode 100644
index 0000000..54efd5e
--- /dev/null
+++ b/opends/src/admin/messages/RootCfgDefn_ja.properties
@@ -0,0 +1,127 @@
+user-friendly-name=Root
+user-friendly-plural-name=Roots
+synopsis=The root configuration provides an entry point to the rest of the OpenDS Directory Server configuration.
+tag.core-server.synopsis=Core server
+tag.database.synopsis=Caching and back-ends
+tag.logging.synopsis=Logging
+tag.replication.synopsis=Replication
+tag.security.synopsis=Authentication and authorization
+tag.user-management.synopsis=User management
+relation.access-control-handler.user-friendly-name=Access Control Handler
+relation.access-control-handler.synopsis=Access Control Handlers manage the application-wide access control. The OpenDS access control handler is defined through an extensible interface, so that alternate implementations can be created. Only one access control handler may be active in the server at any given time.
+relation.access-control-handler.description=Note that OpenDS also has a privilege subsystem, which may have an impact on what clients may be allowed to do in the server. For example, any user with the bypass-acl privilege is not subject to access control checking regardless of whether the access control implementation is enabled.
+relation.account-status-notification-handler.user-friendly-name=Account Status Notification Handler
+relation.account-status-notification-handler.user-friendly-plural-name=Account Status Notification Handlers
+relation.account-status-notification-handler.synopsis=Account Status Notification Handlers are invoked to provide notification to users in some form (for example, by an email message) when the status of a user's account has changed in some way. The Account Status Notification Handler can be used to notify the user and/or administrators of the change.
+relation.administration-connector.user-friendly-name=Administration Connector
+relation.administration-connector.synopsis=The Administration Connector is used to interact with administration tools using LDAP.
+relation.administration-connector.description=It is a dedicated entry point for administration.
+relation.alert-handler.user-friendly-name=Alert Handler
+relation.alert-handler.user-friendly-plural-name=Alert Handlers
+relation.alert-handler.synopsis=Alert Handlers are used to notify administrators of significant problems or notable events that occur in the Directory Server.
+relation.attribute-syntax.user-friendly-name=Attribute Syntax
+relation.attribute-syntax.user-friendly-plural-name=Attribute Syntaxes
+relation.attribute-syntax.synopsis=Attribute Syntaxes define the type of data that may be stored in an attribute with that syntax. A syntax is generally associated with a set of matching rules that indicate how to perform matching operations against values of that syntax.
+relation.backend.user-friendly-name=Backend
+relation.backend.user-friendly-plural-name=Backends
+relation.backend.synopsis=Backends are responsible for providing access to the underlying data presented by the server.
+relation.backend.description=The data may be stored locally in an embedded database, remotely in an external system, or generated on the fly (for example, calculated from other information that is available).
+relation.certificate-mapper.user-friendly-name=Certificate Mapper
+relation.certificate-mapper.user-friendly-plural-name=Certificate Mappers
+relation.certificate-mapper.synopsis=Certificate Mappers are responsible for establishing a mapping between a client certificate and the entry for the user that corresponds to that certificate.
+relation.connection-handler.user-friendly-name=Connection Handler
+relation.connection-handler.user-friendly-plural-name=Connection Handlers
+relation.connection-handler.synopsis=Connection Handlers are responsible for handling all interaction with the clients, including accepting the connections, reading requests, and sending responses.
+relation.crypto-manager.user-friendly-name=Crypto Manager
+relation.crypto-manager.synopsis=The Crypto Manager provides a common interface for performing compression, decompression, hashing, encryption and other kinds of cryptographic operations.
+relation.entry-cache.user-friendly-name=Entry Cache
+relation.entry-cache.user-friendly-plural-name=Entry Caches
+relation.entry-cache.synopsis=Entry Caches are responsible for caching entries which are likely to be accessed by client applications in order to improve Directory Server performance.
+relation.extended-operation-handler.user-friendly-name=Extended Operation Handler
+relation.extended-operation-handler.user-friendly-plural-name=Extended Operation Handlers
+relation.extended-operation-handler.synopsis=Extended Operation Handlers processes the different types of extended operations in the server.
+relation.extension.user-friendly-name=Extension
+relation.extension.user-friendly-plural-name=Extensions
+relation.extension.synopsis=The Extension allows to extend the configuration with new type of objects.
+relation.extension.description=It is an entry point for extensions that requires configuration objects that does not inherit from an existing top-level object.
+relation.global-configuration.user-friendly-name=Global Configuration
+relation.global-configuration.synopsis=The Global contains properties that affect the overall operation of the OpenDS Directory Server .
+relation.group-implementation.user-friendly-name=Group Implementation
+relation.group-implementation.user-friendly-plural-name=Group Implementations
+relation.group-implementation.synopsis=Group Implementations define named collections of users.
+relation.group-implementation.description=Different group implementations may have different ways of determining membership. For example, some groups may explicitly list the members, and/or they may dynamically determine membership.
+relation.identity-mapper.user-friendly-name=Identity Mapper
+relation.identity-mapper.user-friendly-plural-name=Identity Mappers
+relation.identity-mapper.synopsis=Identity Mappers are responsible for establishing a mapping between an identifier string provided by a client, and the entry for the user that corresponds to that identifier. Identity Mappers are used to process several SASL mechanisms to map an authorization ID (e.g., a Kerberos principal when using GSSAPI) to a directory user. They are also used when processing requests with the proxied authorization control.
+relation.key-manager-provider.user-friendly-name=Key Manager Provider
+relation.key-manager-provider.user-friendly-plural-name=Key Manager Providers
+relation.key-manager-provider.synopsis=Key Manager Providers are responsible for managing the key material that is used to authenticate an SSL connection to its peer.
+relation.key-manager-provider.description=Key Manager Providers essentially provide access to the certificate that is used by the server when performing SSL or StartTLS negotiation.
+relation.log-publisher.user-friendly-name=Log Publisher
+relation.log-publisher.user-friendly-plural-name=Log Publishers
+relation.log-publisher.synopsis=Log Publishers are responsible for distributing log messages from different loggers to a destination.
+relation.log-retention-policy.user-friendly-name=Log Retention Policy
+relation.log-retention-policy.user-friendly-plural-name=Log Retention Policies
+relation.log-retention-policy.synopsis=Log Retention Policies are used to specify when log files should be cleaned.
+relation.log-rotation-policy.user-friendly-name=Log Rotation Policy
+relation.log-rotation-policy.user-friendly-plural-name=Log Rotation Policies
+relation.log-rotation-policy.synopsis=Log Rotation Policies are used to specify when log files should be rotated.
+relation.matching-rule.user-friendly-name=Matching Rule
+relation.matching-rule.user-friendly-plural-name=Matching Rules
+relation.matching-rule.synopsis=Matching Rules define a set of rules for performing matching operations against assertion values.
+relation.matching-rule.description=Matching rules are frequently associated with an attribute syntax and are used to compare values according to that syntax. For example, the distinguishedNameEqualityMatch matching rule can be used to determine whether two DNs are equal and can ignore unnecessary spaces around commas and equal signs, differences in capitalization in attribute names, an so on.
+relation.monitor-provider.user-friendly-name=Monitor Provider
+relation.monitor-provider.user-friendly-plural-name=Monitor Providers
+relation.monitor-provider.synopsis=Monitor Providers can be used to provide information about the state of the server or one of its components.
+relation.monitor-provider.description=This information is useful for monitoring or troubleshooting.
+relation.network-group.user-friendly-name=Network Group
+relation.network-group.user-friendly-plural-name=Network Groups
+relation.network-group.synopsis=The Network Group is used to classify incoming connections and route requests to workflows.
+relation.password-generator.user-friendly-name=Password Generator
+relation.password-generator.user-friendly-plural-name=Password Generators
+relation.password-generator.synopsis=Password Generators are used by the password modify extended operation to construct a new password for the user.
+relation.password-generator.description=The server allows any number of password validators to be defined. This can impose any kinds of restrictions on the characteristics of valid passwords. Therefore, it is not feasible for the server to attempt to generate a password on its own that will meet all the requirements of all the validators. The password generator makes it possible to provide custom logic for creating a new password.
+relation.password-policy.user-friendly-name=Password Policy
+relation.password-policy.user-friendly-plural-name=Password Policies
+relation.password-policy.synopsis=Password Policies define a number of password management rules, as well as requirements for authentication processing.
+relation.password-storage-scheme.user-friendly-name=Password Storage Scheme
+relation.password-storage-scheme.user-friendly-plural-name=Password Storage Schemes
+relation.password-storage-scheme.synopsis=Password Storage Schemes encode new passwords provided by users so that they are stored in an encoded manner. This makes it difficult or impossible for someone to determine the clear-text passwords from the encoded values.
+relation.password-storage-scheme.description=Password Storage Schemes also determine whether a clear-text password provided by a client matches the encoded value stored in the server.
+relation.password-validator.user-friendly-name=Password Validator
+relation.password-validator.user-friendly-plural-name=Password Validators
+relation.password-validator.synopsis=Password Validators are responsible for determining whether a proposed password is acceptable for use and could include checks like ensuring it meets minimum length requirements, that it has an appropriate range of characters, or that it is not in the history.
+relation.password-validator.description=The password policy for a user specifies the set of password validators that should be used whenever that user provides a new password. In order to activate a password validator, the corresponding configuration entry must be enabled, and the DN of that entry should be included in the password-validator attribute of the password policy in which you want that validator active. All password validator configuration entries must contain the password-validator structural objectclass.
+relation.plugin-root.user-friendly-name=Plugin Root
+relation.plugin-root.synopsis=The Plugin Root defines the parent entry for all plug-ins defined in the server.
+relation.plugin-root.description=It can also include configuration attributes that define the order in which those plug-ins are to be loaded and invoked.
+relation.root-dn.user-friendly-name=Root DN
+relation.root-dn.synopsis=The Root DN configuration contains all the Root DN Users defined in the Directory Server. In addition, it also defines the default set of privileges that Root DN Users automatically inherit.
+relation.root-dse-backend.user-friendly-name=Root DSE Backend
+relation.root-dse-backend.synopsis=The Root DSE Backend contains the Directory Server root DSE.
+relation.root-dse-backend.description=This is a special meta-backend that dynamically generates the root DSE entry for base-level searches and simply redirects to other backends for operations in other scopes.
+relation.sasl-mechanism-handler.user-friendly-name=SASL Mechanism Handler
+relation.sasl-mechanism-handler.user-friendly-plural-name=SASL Mechanism Handlers
+relation.sasl-mechanism-handler.synopsis=The SASL mechanism handler configuration entry is the parent for all SASL mechanism handlers defined in the OpenDS Directory Server.
+relation.sasl-mechanism-handler.description=SASL mechanism handlers are responsible for authenticating users during the course of processing a SASL (Simple Authentication and Security Layer, as defined in RFC 4422) bind.
+relation.synchronization-provider.user-friendly-name=Synchronization Provider
+relation.synchronization-provider.user-friendly-plural-name=Synchronization Providers
+relation.synchronization-provider.synopsis=Synchronization Providers are responsible for handling synchronization of the Directory Server data with other OpenDS instances or other data repositories.
+relation.synchronization-provider.description=The OpenDS Directory Server takes a centralized approach to replication, rather than the point-to-point approach taken by Sun Java System Directory Server. In OpenDS, one or more replication servers are created in the environment. The replication servers typically do not store user data but keep a log of all changes made within the topology. Each Directory Server instance in the topology is pointed at the replication servers. This plan simplifies the deployment and management of the environment. Although you can run the replication server on the same system (or even in the same instance) as the Directory Server, the two servers can be separated onto different systems. This approach can provide better performance or functionality in large environments.
+relation.trust-manager-provider.user-friendly-name=Trust Manager Provider
+relation.trust-manager-provider.user-friendly-plural-name=Trust Manager Providers
+relation.trust-manager-provider.synopsis=Trust Manager Providers determine whether to trust presented certificates.
+relation.virtual-attribute.user-friendly-name=Virtual Attribute
+relation.virtual-attribute.user-friendly-plural-name=Virtual Attributes
+relation.virtual-attribute.synopsis=Virtual Attributes are responsible for dynamically generating attribute values that appear in entries but are not persistently stored in the backend.
+relation.virtual-attribute.description=Virtual attributes are associated with a virtual attribute provider, which contains the logic for generating the value.
+relation.workflow.user-friendly-name=Workflow
+relation.workflow.user-friendly-plural-name=Workflows
+relation.workflow.synopsis=The Workflow is a list of processing steps (Work Flow Elements) that are applied to data as it is retrieved from the Directory Server.
+relation.workflow-element.user-friendly-name=Workflow Element
+relation.workflow-element.user-friendly-plural-name=Workflow Elements
+relation.workflow-element.synopsis=Workflow Elements implement a single processing step in a Work Flow.
+relation.workflow-element.description=A Workflow Element can perform a task such as mapping DNs, renaming attributes, filtering attributes, joining data sources, proxying, or load-balancing. The simplest Workflow Element is the Local Backend Work Flow Element, which routes data to a Backend.
+relation.work-queue.user-friendly-name=Work Queue
+relation.work-queue.synopsis=The Work Queue provides the configuration for the server work queue and is responsible for ensuring that requests received from clients are processed in a timely manner.
+relation.work-queue.description=Only a single work queue can be defined in the server. Whenever a connection handler receives a client request, it should place the request in the work queue to be processed appropriately.
diff --git a/opends/src/admin/messages/RootCfgDefn_ko.properties b/opends/src/admin/messages/RootCfgDefn_ko.properties
new file mode 100644
index 0000000..54efd5e
--- /dev/null
+++ b/opends/src/admin/messages/RootCfgDefn_ko.properties
@@ -0,0 +1,127 @@
+user-friendly-name=Root
+user-friendly-plural-name=Roots
+synopsis=The root configuration provides an entry point to the rest of the OpenDS Directory Server configuration.
+tag.core-server.synopsis=Core server
+tag.database.synopsis=Caching and back-ends
+tag.logging.synopsis=Logging
+tag.replication.synopsis=Replication
+tag.security.synopsis=Authentication and authorization
+tag.user-management.synopsis=User management
+relation.access-control-handler.user-friendly-name=Access Control Handler
+relation.access-control-handler.synopsis=Access Control Handlers manage the application-wide access control. The OpenDS access control handler is defined through an extensible interface, so that alternate implementations can be created. Only one access control handler may be active in the server at any given time.
+relation.access-control-handler.description=Note that OpenDS also has a privilege subsystem, which may have an impact on what clients may be allowed to do in the server. For example, any user with the bypass-acl privilege is not subject to access control checking regardless of whether the access control implementation is enabled.
+relation.account-status-notification-handler.user-friendly-name=Account Status Notification Handler
+relation.account-status-notification-handler.user-friendly-plural-name=Account Status Notification Handlers
+relation.account-status-notification-handler.synopsis=Account Status Notification Handlers are invoked to provide notification to users in some form (for example, by an email message) when the status of a user's account has changed in some way. The Account Status Notification Handler can be used to notify the user and/or administrators of the change.
+relation.administration-connector.user-friendly-name=Administration Connector
+relation.administration-connector.synopsis=The Administration Connector is used to interact with administration tools using LDAP.
+relation.administration-connector.description=It is a dedicated entry point for administration.
+relation.alert-handler.user-friendly-name=Alert Handler
+relation.alert-handler.user-friendly-plural-name=Alert Handlers
+relation.alert-handler.synopsis=Alert Handlers are used to notify administrators of significant problems or notable events that occur in the Directory Server.
+relation.attribute-syntax.user-friendly-name=Attribute Syntax
+relation.attribute-syntax.user-friendly-plural-name=Attribute Syntaxes
+relation.attribute-syntax.synopsis=Attribute Syntaxes define the type of data that may be stored in an attribute with that syntax. A syntax is generally associated with a set of matching rules that indicate how to perform matching operations against values of that syntax.
+relation.backend.user-friendly-name=Backend
+relation.backend.user-friendly-plural-name=Backends
+relation.backend.synopsis=Backends are responsible for providing access to the underlying data presented by the server.
+relation.backend.description=The data may be stored locally in an embedded database, remotely in an external system, or generated on the fly (for example, calculated from other information that is available).
+relation.certificate-mapper.user-friendly-name=Certificate Mapper
+relation.certificate-mapper.user-friendly-plural-name=Certificate Mappers
+relation.certificate-mapper.synopsis=Certificate Mappers are responsible for establishing a mapping between a client certificate and the entry for the user that corresponds to that certificate.
+relation.connection-handler.user-friendly-name=Connection Handler
+relation.connection-handler.user-friendly-plural-name=Connection Handlers
+relation.connection-handler.synopsis=Connection Handlers are responsible for handling all interaction with the clients, including accepting the connections, reading requests, and sending responses.
+relation.crypto-manager.user-friendly-name=Crypto Manager
+relation.crypto-manager.synopsis=The Crypto Manager provides a common interface for performing compression, decompression, hashing, encryption and other kinds of cryptographic operations.
+relation.entry-cache.user-friendly-name=Entry Cache
+relation.entry-cache.user-friendly-plural-name=Entry Caches
+relation.entry-cache.synopsis=Entry Caches are responsible for caching entries which are likely to be accessed by client applications in order to improve Directory Server performance.
+relation.extended-operation-handler.user-friendly-name=Extended Operation Handler
+relation.extended-operation-handler.user-friendly-plural-name=Extended Operation Handlers
+relation.extended-operation-handler.synopsis=Extended Operation Handlers processes the different types of extended operations in the server.
+relation.extension.user-friendly-name=Extension
+relation.extension.user-friendly-plural-name=Extensions
+relation.extension.synopsis=The Extension allows to extend the configuration with new type of objects.
+relation.extension.description=It is an entry point for extensions that requires configuration objects that does not inherit from an existing top-level object.
+relation.global-configuration.user-friendly-name=Global Configuration
+relation.global-configuration.synopsis=The Global contains properties that affect the overall operation of the OpenDS Directory Server .
+relation.group-implementation.user-friendly-name=Group Implementation
+relation.group-implementation.user-friendly-plural-name=Group Implementations
+relation.group-implementation.synopsis=Group Implementations define named collections of users.
+relation.group-implementation.description=Different group implementations may have different ways of determining membership. For example, some groups may explicitly list the members, and/or they may dynamically determine membership.
+relation.identity-mapper.user-friendly-name=Identity Mapper
+relation.identity-mapper.user-friendly-plural-name=Identity Mappers
+relation.identity-mapper.synopsis=Identity Mappers are responsible for establishing a mapping between an identifier string provided by a client, and the entry for the user that corresponds to that identifier. Identity Mappers are used to process several SASL mechanisms to map an authorization ID (e.g., a Kerberos principal when using GSSAPI) to a directory user. They are also used when processing requests with the proxied authorization control.
+relation.key-manager-provider.user-friendly-name=Key Manager Provider
+relation.key-manager-provider.user-friendly-plural-name=Key Manager Providers
+relation.key-manager-provider.synopsis=Key Manager Providers are responsible for managing the key material that is used to authenticate an SSL connection to its peer.
+relation.key-manager-provider.description=Key Manager Providers essentially provide access to the certificate that is used by the server when performing SSL or StartTLS negotiation.
+relation.log-publisher.user-friendly-name=Log Publisher
+relation.log-publisher.user-friendly-plural-name=Log Publishers
+relation.log-publisher.synopsis=Log Publishers are responsible for distributing log messages from different loggers to a destination.
+relation.log-retention-policy.user-friendly-name=Log Retention Policy
+relation.log-retention-policy.user-friendly-plural-name=Log Retention Policies
+relation.log-retention-policy.synopsis=Log Retention Policies are used to specify when log files should be cleaned.
+relation.log-rotation-policy.user-friendly-name=Log Rotation Policy
+relation.log-rotation-policy.user-friendly-plural-name=Log Rotation Policies
+relation.log-rotation-policy.synopsis=Log Rotation Policies are used to specify when log files should be rotated.
+relation.matching-rule.user-friendly-name=Matching Rule
+relation.matching-rule.user-friendly-plural-name=Matching Rules
+relation.matching-rule.synopsis=Matching Rules define a set of rules for performing matching operations against assertion values.
+relation.matching-rule.description=Matching rules are frequently associated with an attribute syntax and are used to compare values according to that syntax. For example, the distinguishedNameEqualityMatch matching rule can be used to determine whether two DNs are equal and can ignore unnecessary spaces around commas and equal signs, differences in capitalization in attribute names, an so on.
+relation.monitor-provider.user-friendly-name=Monitor Provider
+relation.monitor-provider.user-friendly-plural-name=Monitor Providers
+relation.monitor-provider.synopsis=Monitor Providers can be used to provide information about the state of the server or one of its components.
+relation.monitor-provider.description=This information is useful for monitoring or troubleshooting.
+relation.network-group.user-friendly-name=Network Group
+relation.network-group.user-friendly-plural-name=Network Groups
+relation.network-group.synopsis=The Network Group is used to classify incoming connections and route requests to workflows.
+relation.password-generator.user-friendly-name=Password Generator
+relation.password-generator.user-friendly-plural-name=Password Generators
+relation.password-generator.synopsis=Password Generators are used by the password modify extended operation to construct a new password for the user.
+relation.password-generator.description=The server allows any number of password validators to be defined. This can impose any kinds of restrictions on the characteristics of valid passwords. Therefore, it is not feasible for the server to attempt to generate a password on its own that will meet all the requirements of all the validators. The password generator makes it possible to provide custom logic for creating a new password.
+relation.password-policy.user-friendly-name=Password Policy
+relation.password-policy.user-friendly-plural-name=Password Policies
+relation.password-policy.synopsis=Password Policies define a number of password management rules, as well as requirements for authentication processing.
+relation.password-storage-scheme.user-friendly-name=Password Storage Scheme
+relation.password-storage-scheme.user-friendly-plural-name=Password Storage Schemes
+relation.password-storage-scheme.synopsis=Password Storage Schemes encode new passwords provided by users so that they are stored in an encoded manner. This makes it difficult or impossible for someone to determine the clear-text passwords from the encoded values.
+relation.password-storage-scheme.description=Password Storage Schemes also determine whether a clear-text password provided by a client matches the encoded value stored in the server.
+relation.password-validator.user-friendly-name=Password Validator
+relation.password-validator.user-friendly-plural-name=Password Validators
+relation.password-validator.synopsis=Password Validators are responsible for determining whether a proposed password is acceptable for use and could include checks like ensuring it meets minimum length requirements, that it has an appropriate range of characters, or that it is not in the history.
+relation.password-validator.description=The password policy for a user specifies the set of password validators that should be used whenever that user provides a new password. In order to activate a password validator, the corresponding configuration entry must be enabled, and the DN of that entry should be included in the password-validator attribute of the password policy in which you want that validator active. All password validator configuration entries must contain the password-validator structural objectclass.
+relation.plugin-root.user-friendly-name=Plugin Root
+relation.plugin-root.synopsis=The Plugin Root defines the parent entry for all plug-ins defined in the server.
+relation.plugin-root.description=It can also include configuration attributes that define the order in which those plug-ins are to be loaded and invoked.
+relation.root-dn.user-friendly-name=Root DN
+relation.root-dn.synopsis=The Root DN configuration contains all the Root DN Users defined in the Directory Server. In addition, it also defines the default set of privileges that Root DN Users automatically inherit.
+relation.root-dse-backend.user-friendly-name=Root DSE Backend
+relation.root-dse-backend.synopsis=The Root DSE Backend contains the Directory Server root DSE.
+relation.root-dse-backend.description=This is a special meta-backend that dynamically generates the root DSE entry for base-level searches and simply redirects to other backends for operations in other scopes.
+relation.sasl-mechanism-handler.user-friendly-name=SASL Mechanism Handler
+relation.sasl-mechanism-handler.user-friendly-plural-name=SASL Mechanism Handlers
+relation.sasl-mechanism-handler.synopsis=The SASL mechanism handler configuration entry is the parent for all SASL mechanism handlers defined in the OpenDS Directory Server.
+relation.sasl-mechanism-handler.description=SASL mechanism handlers are responsible for authenticating users during the course of processing a SASL (Simple Authentication and Security Layer, as defined in RFC 4422) bind.
+relation.synchronization-provider.user-friendly-name=Synchronization Provider
+relation.synchronization-provider.user-friendly-plural-name=Synchronization Providers
+relation.synchronization-provider.synopsis=Synchronization Providers are responsible for handling synchronization of the Directory Server data with other OpenDS instances or other data repositories.
+relation.synchronization-provider.description=The OpenDS Directory Server takes a centralized approach to replication, rather than the point-to-point approach taken by Sun Java System Directory Server. In OpenDS, one or more replication servers are created in the environment. The replication servers typically do not store user data but keep a log of all changes made within the topology. Each Directory Server instance in the topology is pointed at the replication servers. This plan simplifies the deployment and management of the environment. Although you can run the replication server on the same system (or even in the same instance) as the Directory Server, the two servers can be separated onto different systems. This approach can provide better performance or functionality in large environments.
+relation.trust-manager-provider.user-friendly-name=Trust Manager Provider
+relation.trust-manager-provider.user-friendly-plural-name=Trust Manager Providers
+relation.trust-manager-provider.synopsis=Trust Manager Providers determine whether to trust presented certificates.
+relation.virtual-attribute.user-friendly-name=Virtual Attribute
+relation.virtual-attribute.user-friendly-plural-name=Virtual Attributes
+relation.virtual-attribute.synopsis=Virtual Attributes are responsible for dynamically generating attribute values that appear in entries but are not persistently stored in the backend.
+relation.virtual-attribute.description=Virtual attributes are associated with a virtual attribute provider, which contains the logic for generating the value.
+relation.workflow.user-friendly-name=Workflow
+relation.workflow.user-friendly-plural-name=Workflows
+relation.workflow.synopsis=The Workflow is a list of processing steps (Work Flow Elements) that are applied to data as it is retrieved from the Directory Server.
+relation.workflow-element.user-friendly-name=Workflow Element
+relation.workflow-element.user-friendly-plural-name=Workflow Elements
+relation.workflow-element.synopsis=Workflow Elements implement a single processing step in a Work Flow.
+relation.workflow-element.description=A Workflow Element can perform a task such as mapping DNs, renaming attributes, filtering attributes, joining data sources, proxying, or load-balancing. The simplest Workflow Element is the Local Backend Work Flow Element, which routes data to a Backend.
+relation.work-queue.user-friendly-name=Work Queue
+relation.work-queue.synopsis=The Work Queue provides the configuration for the server work queue and is responsible for ensuring that requests received from clients are processed in a timely manner.
+relation.work-queue.description=Only a single work queue can be defined in the server. Whenever a connection handler receives a client request, it should place the request in the work queue to be processed appropriately.
diff --git a/opends/src/admin/messages/RootCfgDefn_zh_CN.properties b/opends/src/admin/messages/RootCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..54efd5e
--- /dev/null
+++ b/opends/src/admin/messages/RootCfgDefn_zh_CN.properties
@@ -0,0 +1,127 @@
+user-friendly-name=Root
+user-friendly-plural-name=Roots
+synopsis=The root configuration provides an entry point to the rest of the OpenDS Directory Server configuration.
+tag.core-server.synopsis=Core server
+tag.database.synopsis=Caching and back-ends
+tag.logging.synopsis=Logging
+tag.replication.synopsis=Replication
+tag.security.synopsis=Authentication and authorization
+tag.user-management.synopsis=User management
+relation.access-control-handler.user-friendly-name=Access Control Handler
+relation.access-control-handler.synopsis=Access Control Handlers manage the application-wide access control. The OpenDS access control handler is defined through an extensible interface, so that alternate implementations can be created. Only one access control handler may be active in the server at any given time.
+relation.access-control-handler.description=Note that OpenDS also has a privilege subsystem, which may have an impact on what clients may be allowed to do in the server. For example, any user with the bypass-acl privilege is not subject to access control checking regardless of whether the access control implementation is enabled.
+relation.account-status-notification-handler.user-friendly-name=Account Status Notification Handler
+relation.account-status-notification-handler.user-friendly-plural-name=Account Status Notification Handlers
+relation.account-status-notification-handler.synopsis=Account Status Notification Handlers are invoked to provide notification to users in some form (for example, by an email message) when the status of a user's account has changed in some way. The Account Status Notification Handler can be used to notify the user and/or administrators of the change.
+relation.administration-connector.user-friendly-name=Administration Connector
+relation.administration-connector.synopsis=The Administration Connector is used to interact with administration tools using LDAP.
+relation.administration-connector.description=It is a dedicated entry point for administration.
+relation.alert-handler.user-friendly-name=Alert Handler
+relation.alert-handler.user-friendly-plural-name=Alert Handlers
+relation.alert-handler.synopsis=Alert Handlers are used to notify administrators of significant problems or notable events that occur in the Directory Server.
+relation.attribute-syntax.user-friendly-name=Attribute Syntax
+relation.attribute-syntax.user-friendly-plural-name=Attribute Syntaxes
+relation.attribute-syntax.synopsis=Attribute Syntaxes define the type of data that may be stored in an attribute with that syntax. A syntax is generally associated with a set of matching rules that indicate how to perform matching operations against values of that syntax.
+relation.backend.user-friendly-name=Backend
+relation.backend.user-friendly-plural-name=Backends
+relation.backend.synopsis=Backends are responsible for providing access to the underlying data presented by the server.
+relation.backend.description=The data may be stored locally in an embedded database, remotely in an external system, or generated on the fly (for example, calculated from other information that is available).
+relation.certificate-mapper.user-friendly-name=Certificate Mapper
+relation.certificate-mapper.user-friendly-plural-name=Certificate Mappers
+relation.certificate-mapper.synopsis=Certificate Mappers are responsible for establishing a mapping between a client certificate and the entry for the user that corresponds to that certificate.
+relation.connection-handler.user-friendly-name=Connection Handler
+relation.connection-handler.user-friendly-plural-name=Connection Handlers
+relation.connection-handler.synopsis=Connection Handlers are responsible for handling all interaction with the clients, including accepting the connections, reading requests, and sending responses.
+relation.crypto-manager.user-friendly-name=Crypto Manager
+relation.crypto-manager.synopsis=The Crypto Manager provides a common interface for performing compression, decompression, hashing, encryption and other kinds of cryptographic operations.
+relation.entry-cache.user-friendly-name=Entry Cache
+relation.entry-cache.user-friendly-plural-name=Entry Caches
+relation.entry-cache.synopsis=Entry Caches are responsible for caching entries which are likely to be accessed by client applications in order to improve Directory Server performance.
+relation.extended-operation-handler.user-friendly-name=Extended Operation Handler
+relation.extended-operation-handler.user-friendly-plural-name=Extended Operation Handlers
+relation.extended-operation-handler.synopsis=Extended Operation Handlers processes the different types of extended operations in the server.
+relation.extension.user-friendly-name=Extension
+relation.extension.user-friendly-plural-name=Extensions
+relation.extension.synopsis=The Extension allows to extend the configuration with new type of objects.
+relation.extension.description=It is an entry point for extensions that requires configuration objects that does not inherit from an existing top-level object.
+relation.global-configuration.user-friendly-name=Global Configuration
+relation.global-configuration.synopsis=The Global contains properties that affect the overall operation of the OpenDS Directory Server .
+relation.group-implementation.user-friendly-name=Group Implementation
+relation.group-implementation.user-friendly-plural-name=Group Implementations
+relation.group-implementation.synopsis=Group Implementations define named collections of users.
+relation.group-implementation.description=Different group implementations may have different ways of determining membership. For example, some groups may explicitly list the members, and/or they may dynamically determine membership.
+relation.identity-mapper.user-friendly-name=Identity Mapper
+relation.identity-mapper.user-friendly-plural-name=Identity Mappers
+relation.identity-mapper.synopsis=Identity Mappers are responsible for establishing a mapping between an identifier string provided by a client, and the entry for the user that corresponds to that identifier. Identity Mappers are used to process several SASL mechanisms to map an authorization ID (e.g., a Kerberos principal when using GSSAPI) to a directory user. They are also used when processing requests with the proxied authorization control.
+relation.key-manager-provider.user-friendly-name=Key Manager Provider
+relation.key-manager-provider.user-friendly-plural-name=Key Manager Providers
+relation.key-manager-provider.synopsis=Key Manager Providers are responsible for managing the key material that is used to authenticate an SSL connection to its peer.
+relation.key-manager-provider.description=Key Manager Providers essentially provide access to the certificate that is used by the server when performing SSL or StartTLS negotiation.
+relation.log-publisher.user-friendly-name=Log Publisher
+relation.log-publisher.user-friendly-plural-name=Log Publishers
+relation.log-publisher.synopsis=Log Publishers are responsible for distributing log messages from different loggers to a destination.
+relation.log-retention-policy.user-friendly-name=Log Retention Policy
+relation.log-retention-policy.user-friendly-plural-name=Log Retention Policies
+relation.log-retention-policy.synopsis=Log Retention Policies are used to specify when log files should be cleaned.
+relation.log-rotation-policy.user-friendly-name=Log Rotation Policy
+relation.log-rotation-policy.user-friendly-plural-name=Log Rotation Policies
+relation.log-rotation-policy.synopsis=Log Rotation Policies are used to specify when log files should be rotated.
+relation.matching-rule.user-friendly-name=Matching Rule
+relation.matching-rule.user-friendly-plural-name=Matching Rules
+relation.matching-rule.synopsis=Matching Rules define a set of rules for performing matching operations against assertion values.
+relation.matching-rule.description=Matching rules are frequently associated with an attribute syntax and are used to compare values according to that syntax. For example, the distinguishedNameEqualityMatch matching rule can be used to determine whether two DNs are equal and can ignore unnecessary spaces around commas and equal signs, differences in capitalization in attribute names, an so on.
+relation.monitor-provider.user-friendly-name=Monitor Provider
+relation.monitor-provider.user-friendly-plural-name=Monitor Providers
+relation.monitor-provider.synopsis=Monitor Providers can be used to provide information about the state of the server or one of its components.
+relation.monitor-provider.description=This information is useful for monitoring or troubleshooting.
+relation.network-group.user-friendly-name=Network Group
+relation.network-group.user-friendly-plural-name=Network Groups
+relation.network-group.synopsis=The Network Group is used to classify incoming connections and route requests to workflows.
+relation.password-generator.user-friendly-name=Password Generator
+relation.password-generator.user-friendly-plural-name=Password Generators
+relation.password-generator.synopsis=Password Generators are used by the password modify extended operation to construct a new password for the user.
+relation.password-generator.description=The server allows any number of password validators to be defined. This can impose any kinds of restrictions on the characteristics of valid passwords. Therefore, it is not feasible for the server to attempt to generate a password on its own that will meet all the requirements of all the validators. The password generator makes it possible to provide custom logic for creating a new password.
+relation.password-policy.user-friendly-name=Password Policy
+relation.password-policy.user-friendly-plural-name=Password Policies
+relation.password-policy.synopsis=Password Policies define a number of password management rules, as well as requirements for authentication processing.
+relation.password-storage-scheme.user-friendly-name=Password Storage Scheme
+relation.password-storage-scheme.user-friendly-plural-name=Password Storage Schemes
+relation.password-storage-scheme.synopsis=Password Storage Schemes encode new passwords provided by users so that they are stored in an encoded manner. This makes it difficult or impossible for someone to determine the clear-text passwords from the encoded values.
+relation.password-storage-scheme.description=Password Storage Schemes also determine whether a clear-text password provided by a client matches the encoded value stored in the server.
+relation.password-validator.user-friendly-name=Password Validator
+relation.password-validator.user-friendly-plural-name=Password Validators
+relation.password-validator.synopsis=Password Validators are responsible for determining whether a proposed password is acceptable for use and could include checks like ensuring it meets minimum length requirements, that it has an appropriate range of characters, or that it is not in the history.
+relation.password-validator.description=The password policy for a user specifies the set of password validators that should be used whenever that user provides a new password. In order to activate a password validator, the corresponding configuration entry must be enabled, and the DN of that entry should be included in the password-validator attribute of the password policy in which you want that validator active. All password validator configuration entries must contain the password-validator structural objectclass.
+relation.plugin-root.user-friendly-name=Plugin Root
+relation.plugin-root.synopsis=The Plugin Root defines the parent entry for all plug-ins defined in the server.
+relation.plugin-root.description=It can also include configuration attributes that define the order in which those plug-ins are to be loaded and invoked.
+relation.root-dn.user-friendly-name=Root DN
+relation.root-dn.synopsis=The Root DN configuration contains all the Root DN Users defined in the Directory Server. In addition, it also defines the default set of privileges that Root DN Users automatically inherit.
+relation.root-dse-backend.user-friendly-name=Root DSE Backend
+relation.root-dse-backend.synopsis=The Root DSE Backend contains the Directory Server root DSE.
+relation.root-dse-backend.description=This is a special meta-backend that dynamically generates the root DSE entry for base-level searches and simply redirects to other backends for operations in other scopes.
+relation.sasl-mechanism-handler.user-friendly-name=SASL Mechanism Handler
+relation.sasl-mechanism-handler.user-friendly-plural-name=SASL Mechanism Handlers
+relation.sasl-mechanism-handler.synopsis=The SASL mechanism handler configuration entry is the parent for all SASL mechanism handlers defined in the OpenDS Directory Server.
+relation.sasl-mechanism-handler.description=SASL mechanism handlers are responsible for authenticating users during the course of processing a SASL (Simple Authentication and Security Layer, as defined in RFC 4422) bind.
+relation.synchronization-provider.user-friendly-name=Synchronization Provider
+relation.synchronization-provider.user-friendly-plural-name=Synchronization Providers
+relation.synchronization-provider.synopsis=Synchronization Providers are responsible for handling synchronization of the Directory Server data with other OpenDS instances or other data repositories.
+relation.synchronization-provider.description=The OpenDS Directory Server takes a centralized approach to replication, rather than the point-to-point approach taken by Sun Java System Directory Server. In OpenDS, one or more replication servers are created in the environment. The replication servers typically do not store user data but keep a log of all changes made within the topology. Each Directory Server instance in the topology is pointed at the replication servers. This plan simplifies the deployment and management of the environment. Although you can run the replication server on the same system (or even in the same instance) as the Directory Server, the two servers can be separated onto different systems. This approach can provide better performance or functionality in large environments.
+relation.trust-manager-provider.user-friendly-name=Trust Manager Provider
+relation.trust-manager-provider.user-friendly-plural-name=Trust Manager Providers
+relation.trust-manager-provider.synopsis=Trust Manager Providers determine whether to trust presented certificates.
+relation.virtual-attribute.user-friendly-name=Virtual Attribute
+relation.virtual-attribute.user-friendly-plural-name=Virtual Attributes
+relation.virtual-attribute.synopsis=Virtual Attributes are responsible for dynamically generating attribute values that appear in entries but are not persistently stored in the backend.
+relation.virtual-attribute.description=Virtual attributes are associated with a virtual attribute provider, which contains the logic for generating the value.
+relation.workflow.user-friendly-name=Workflow
+relation.workflow.user-friendly-plural-name=Workflows
+relation.workflow.synopsis=The Workflow is a list of processing steps (Work Flow Elements) that are applied to data as it is retrieved from the Directory Server.
+relation.workflow-element.user-friendly-name=Workflow Element
+relation.workflow-element.user-friendly-plural-name=Workflow Elements
+relation.workflow-element.synopsis=Workflow Elements implement a single processing step in a Work Flow.
+relation.workflow-element.description=A Workflow Element can perform a task such as mapping DNs, renaming attributes, filtering attributes, joining data sources, proxying, or load-balancing. The simplest Workflow Element is the Local Backend Work Flow Element, which routes data to a Backend.
+relation.work-queue.user-friendly-name=Work Queue
+relation.work-queue.synopsis=The Work Queue provides the configuration for the server work queue and is responsible for ensuring that requests received from clients are processed in a timely manner.
+relation.work-queue.description=Only a single work queue can be defined in the server. Whenever a connection handler receives a client request, it should place the request in the work queue to be processed appropriately.
diff --git a/opends/src/admin/messages/RootCfgDefn_zh_TW.properties b/opends/src/admin/messages/RootCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..54efd5e
--- /dev/null
+++ b/opends/src/admin/messages/RootCfgDefn_zh_TW.properties
@@ -0,0 +1,127 @@
+user-friendly-name=Root
+user-friendly-plural-name=Roots
+synopsis=The root configuration provides an entry point to the rest of the OpenDS Directory Server configuration.
+tag.core-server.synopsis=Core server
+tag.database.synopsis=Caching and back-ends
+tag.logging.synopsis=Logging
+tag.replication.synopsis=Replication
+tag.security.synopsis=Authentication and authorization
+tag.user-management.synopsis=User management
+relation.access-control-handler.user-friendly-name=Access Control Handler
+relation.access-control-handler.synopsis=Access Control Handlers manage the application-wide access control. The OpenDS access control handler is defined through an extensible interface, so that alternate implementations can be created. Only one access control handler may be active in the server at any given time.
+relation.access-control-handler.description=Note that OpenDS also has a privilege subsystem, which may have an impact on what clients may be allowed to do in the server. For example, any user with the bypass-acl privilege is not subject to access control checking regardless of whether the access control implementation is enabled.
+relation.account-status-notification-handler.user-friendly-name=Account Status Notification Handler
+relation.account-status-notification-handler.user-friendly-plural-name=Account Status Notification Handlers
+relation.account-status-notification-handler.synopsis=Account Status Notification Handlers are invoked to provide notification to users in some form (for example, by an email message) when the status of a user's account has changed in some way. The Account Status Notification Handler can be used to notify the user and/or administrators of the change.
+relation.administration-connector.user-friendly-name=Administration Connector
+relation.administration-connector.synopsis=The Administration Connector is used to interact with administration tools using LDAP.
+relation.administration-connector.description=It is a dedicated entry point for administration.
+relation.alert-handler.user-friendly-name=Alert Handler
+relation.alert-handler.user-friendly-plural-name=Alert Handlers
+relation.alert-handler.synopsis=Alert Handlers are used to notify administrators of significant problems or notable events that occur in the Directory Server.
+relation.attribute-syntax.user-friendly-name=Attribute Syntax
+relation.attribute-syntax.user-friendly-plural-name=Attribute Syntaxes
+relation.attribute-syntax.synopsis=Attribute Syntaxes define the type of data that may be stored in an attribute with that syntax. A syntax is generally associated with a set of matching rules that indicate how to perform matching operations against values of that syntax.
+relation.backend.user-friendly-name=Backend
+relation.backend.user-friendly-plural-name=Backends
+relation.backend.synopsis=Backends are responsible for providing access to the underlying data presented by the server.
+relation.backend.description=The data may be stored locally in an embedded database, remotely in an external system, or generated on the fly (for example, calculated from other information that is available).
+relation.certificate-mapper.user-friendly-name=Certificate Mapper
+relation.certificate-mapper.user-friendly-plural-name=Certificate Mappers
+relation.certificate-mapper.synopsis=Certificate Mappers are responsible for establishing a mapping between a client certificate and the entry for the user that corresponds to that certificate.
+relation.connection-handler.user-friendly-name=Connection Handler
+relation.connection-handler.user-friendly-plural-name=Connection Handlers
+relation.connection-handler.synopsis=Connection Handlers are responsible for handling all interaction with the clients, including accepting the connections, reading requests, and sending responses.
+relation.crypto-manager.user-friendly-name=Crypto Manager
+relation.crypto-manager.synopsis=The Crypto Manager provides a common interface for performing compression, decompression, hashing, encryption and other kinds of cryptographic operations.
+relation.entry-cache.user-friendly-name=Entry Cache
+relation.entry-cache.user-friendly-plural-name=Entry Caches
+relation.entry-cache.synopsis=Entry Caches are responsible for caching entries which are likely to be accessed by client applications in order to improve Directory Server performance.
+relation.extended-operation-handler.user-friendly-name=Extended Operation Handler
+relation.extended-operation-handler.user-friendly-plural-name=Extended Operation Handlers
+relation.extended-operation-handler.synopsis=Extended Operation Handlers processes the different types of extended operations in the server.
+relation.extension.user-friendly-name=Extension
+relation.extension.user-friendly-plural-name=Extensions
+relation.extension.synopsis=The Extension allows to extend the configuration with new type of objects.
+relation.extension.description=It is an entry point for extensions that requires configuration objects that does not inherit from an existing top-level object.
+relation.global-configuration.user-friendly-name=Global Configuration
+relation.global-configuration.synopsis=The Global contains properties that affect the overall operation of the OpenDS Directory Server .
+relation.group-implementation.user-friendly-name=Group Implementation
+relation.group-implementation.user-friendly-plural-name=Group Implementations
+relation.group-implementation.synopsis=Group Implementations define named collections of users.
+relation.group-implementation.description=Different group implementations may have different ways of determining membership. For example, some groups may explicitly list the members, and/or they may dynamically determine membership.
+relation.identity-mapper.user-friendly-name=Identity Mapper
+relation.identity-mapper.user-friendly-plural-name=Identity Mappers
+relation.identity-mapper.synopsis=Identity Mappers are responsible for establishing a mapping between an identifier string provided by a client, and the entry for the user that corresponds to that identifier. Identity Mappers are used to process several SASL mechanisms to map an authorization ID (e.g., a Kerberos principal when using GSSAPI) to a directory user. They are also used when processing requests with the proxied authorization control.
+relation.key-manager-provider.user-friendly-name=Key Manager Provider
+relation.key-manager-provider.user-friendly-plural-name=Key Manager Providers
+relation.key-manager-provider.synopsis=Key Manager Providers are responsible for managing the key material that is used to authenticate an SSL connection to its peer.
+relation.key-manager-provider.description=Key Manager Providers essentially provide access to the certificate that is used by the server when performing SSL or StartTLS negotiation.
+relation.log-publisher.user-friendly-name=Log Publisher
+relation.log-publisher.user-friendly-plural-name=Log Publishers
+relation.log-publisher.synopsis=Log Publishers are responsible for distributing log messages from different loggers to a destination.
+relation.log-retention-policy.user-friendly-name=Log Retention Policy
+relation.log-retention-policy.user-friendly-plural-name=Log Retention Policies
+relation.log-retention-policy.synopsis=Log Retention Policies are used to specify when log files should be cleaned.
+relation.log-rotation-policy.user-friendly-name=Log Rotation Policy
+relation.log-rotation-policy.user-friendly-plural-name=Log Rotation Policies
+relation.log-rotation-policy.synopsis=Log Rotation Policies are used to specify when log files should be rotated.
+relation.matching-rule.user-friendly-name=Matching Rule
+relation.matching-rule.user-friendly-plural-name=Matching Rules
+relation.matching-rule.synopsis=Matching Rules define a set of rules for performing matching operations against assertion values.
+relation.matching-rule.description=Matching rules are frequently associated with an attribute syntax and are used to compare values according to that syntax. For example, the distinguishedNameEqualityMatch matching rule can be used to determine whether two DNs are equal and can ignore unnecessary spaces around commas and equal signs, differences in capitalization in attribute names, an so on.
+relation.monitor-provider.user-friendly-name=Monitor Provider
+relation.monitor-provider.user-friendly-plural-name=Monitor Providers
+relation.monitor-provider.synopsis=Monitor Providers can be used to provide information about the state of the server or one of its components.
+relation.monitor-provider.description=This information is useful for monitoring or troubleshooting.
+relation.network-group.user-friendly-name=Network Group
+relation.network-group.user-friendly-plural-name=Network Groups
+relation.network-group.synopsis=The Network Group is used to classify incoming connections and route requests to workflows.
+relation.password-generator.user-friendly-name=Password Generator
+relation.password-generator.user-friendly-plural-name=Password Generators
+relation.password-generator.synopsis=Password Generators are used by the password modify extended operation to construct a new password for the user.
+relation.password-generator.description=The server allows any number of password validators to be defined. This can impose any kinds of restrictions on the characteristics of valid passwords. Therefore, it is not feasible for the server to attempt to generate a password on its own that will meet all the requirements of all the validators. The password generator makes it possible to provide custom logic for creating a new password.
+relation.password-policy.user-friendly-name=Password Policy
+relation.password-policy.user-friendly-plural-name=Password Policies
+relation.password-policy.synopsis=Password Policies define a number of password management rules, as well as requirements for authentication processing.
+relation.password-storage-scheme.user-friendly-name=Password Storage Scheme
+relation.password-storage-scheme.user-friendly-plural-name=Password Storage Schemes
+relation.password-storage-scheme.synopsis=Password Storage Schemes encode new passwords provided by users so that they are stored in an encoded manner. This makes it difficult or impossible for someone to determine the clear-text passwords from the encoded values.
+relation.password-storage-scheme.description=Password Storage Schemes also determine whether a clear-text password provided by a client matches the encoded value stored in the server.
+relation.password-validator.user-friendly-name=Password Validator
+relation.password-validator.user-friendly-plural-name=Password Validators
+relation.password-validator.synopsis=Password Validators are responsible for determining whether a proposed password is acceptable for use and could include checks like ensuring it meets minimum length requirements, that it has an appropriate range of characters, or that it is not in the history.
+relation.password-validator.description=The password policy for a user specifies the set of password validators that should be used whenever that user provides a new password. In order to activate a password validator, the corresponding configuration entry must be enabled, and the DN of that entry should be included in the password-validator attribute of the password policy in which you want that validator active. All password validator configuration entries must contain the password-validator structural objectclass.
+relation.plugin-root.user-friendly-name=Plugin Root
+relation.plugin-root.synopsis=The Plugin Root defines the parent entry for all plug-ins defined in the server.
+relation.plugin-root.description=It can also include configuration attributes that define the order in which those plug-ins are to be loaded and invoked.
+relation.root-dn.user-friendly-name=Root DN
+relation.root-dn.synopsis=The Root DN configuration contains all the Root DN Users defined in the Directory Server. In addition, it also defines the default set of privileges that Root DN Users automatically inherit.
+relation.root-dse-backend.user-friendly-name=Root DSE Backend
+relation.root-dse-backend.synopsis=The Root DSE Backend contains the Directory Server root DSE.
+relation.root-dse-backend.description=This is a special meta-backend that dynamically generates the root DSE entry for base-level searches and simply redirects to other backends for operations in other scopes.
+relation.sasl-mechanism-handler.user-friendly-name=SASL Mechanism Handler
+relation.sasl-mechanism-handler.user-friendly-plural-name=SASL Mechanism Handlers
+relation.sasl-mechanism-handler.synopsis=The SASL mechanism handler configuration entry is the parent for all SASL mechanism handlers defined in the OpenDS Directory Server.
+relation.sasl-mechanism-handler.description=SASL mechanism handlers are responsible for authenticating users during the course of processing a SASL (Simple Authentication and Security Layer, as defined in RFC 4422) bind.
+relation.synchronization-provider.user-friendly-name=Synchronization Provider
+relation.synchronization-provider.user-friendly-plural-name=Synchronization Providers
+relation.synchronization-provider.synopsis=Synchronization Providers are responsible for handling synchronization of the Directory Server data with other OpenDS instances or other data repositories.
+relation.synchronization-provider.description=The OpenDS Directory Server takes a centralized approach to replication, rather than the point-to-point approach taken by Sun Java System Directory Server. In OpenDS, one or more replication servers are created in the environment. The replication servers typically do not store user data but keep a log of all changes made within the topology. Each Directory Server instance in the topology is pointed at the replication servers. This plan simplifies the deployment and management of the environment. Although you can run the replication server on the same system (or even in the same instance) as the Directory Server, the two servers can be separated onto different systems. This approach can provide better performance or functionality in large environments.
+relation.trust-manager-provider.user-friendly-name=Trust Manager Provider
+relation.trust-manager-provider.user-friendly-plural-name=Trust Manager Providers
+relation.trust-manager-provider.synopsis=Trust Manager Providers determine whether to trust presented certificates.
+relation.virtual-attribute.user-friendly-name=Virtual Attribute
+relation.virtual-attribute.user-friendly-plural-name=Virtual Attributes
+relation.virtual-attribute.synopsis=Virtual Attributes are responsible for dynamically generating attribute values that appear in entries but are not persistently stored in the backend.
+relation.virtual-attribute.description=Virtual attributes are associated with a virtual attribute provider, which contains the logic for generating the value.
+relation.workflow.user-friendly-name=Workflow
+relation.workflow.user-friendly-plural-name=Workflows
+relation.workflow.synopsis=The Workflow is a list of processing steps (Work Flow Elements) that are applied to data as it is retrieved from the Directory Server.
+relation.workflow-element.user-friendly-name=Workflow Element
+relation.workflow-element.user-friendly-plural-name=Workflow Elements
+relation.workflow-element.synopsis=Workflow Elements implement a single processing step in a Work Flow.
+relation.workflow-element.description=A Workflow Element can perform a task such as mapping DNs, renaming attributes, filtering attributes, joining data sources, proxying, or load-balancing. The simplest Workflow Element is the Local Backend Work Flow Element, which routes data to a Backend.
+relation.work-queue.user-friendly-name=Work Queue
+relation.work-queue.synopsis=The Work Queue provides the configuration for the server work queue and is responsible for ensuring that requests received from clients are processed in a timely manner.
+relation.work-queue.description=Only a single work queue can be defined in the server. Whenever a connection handler receives a client request, it should place the request in the work queue to be processed appropriately.
diff --git a/opends/src/admin/messages/RootDNCfgDefn.properties b/opends/src/admin/messages/RootDNCfgDefn.properties
new file mode 100644
index 0000000..aa1bb8e
--- /dev/null
+++ b/opends/src/admin/messages/RootDNCfgDefn.properties
@@ -0,0 +1,29 @@
+user-friendly-name=Root DN
+user-friendly-plural-name=Root Dns
+synopsis=The Root DN configuration contains all the Root DN Users defined in the Directory Server. In addition, it also defines the default set of privileges that Root DN Users automatically inherit.
+property.default-root-privilege-name.synopsis=Specifies the names of the privileges that root users will be granted by default.
+property.default-root-privilege-name.syntax.enumeration.value.backend-backup.synopsis=Allows the user to request that the server process backup tasks.
+property.default-root-privilege-name.syntax.enumeration.value.backend-restore.synopsis=Allows the user to request that the server process restore tasks.
+property.default-root-privilege-name.syntax.enumeration.value.bypass-acl.synopsis=Allows the associated user to bypass access control checks performed by the server.
+property.default-root-privilege-name.syntax.enumeration.value.cancel-request.synopsis=Allows the user to cancel operations in progress on other client connections.
+property.default-root-privilege-name.syntax.enumeration.value.config-read.synopsis=Allows the associated user to read the server configuration.
+property.default-root-privilege-name.syntax.enumeration.value.config-write.synopsis=Allows the associated user to update the server configuration. The config-read privilege is also required.
+property.default-root-privilege-name.syntax.enumeration.value.data-sync.synopsis=Allows the user to participate in data synchronization.
+property.default-root-privilege-name.syntax.enumeration.value.disconnect-client.synopsis=Allows the user to terminate other client connections.
+property.default-root-privilege-name.syntax.enumeration.value.jmx-notify.synopsis=Allows the associated user to subscribe to receive JMX notifications.
+property.default-root-privilege-name.syntax.enumeration.value.jmx-read.synopsis=Allows the associated user to perform JMX read operations.
+property.default-root-privilege-name.syntax.enumeration.value.jmx-write.synopsis=Allows the associated user to perform JMX write operations.
+property.default-root-privilege-name.syntax.enumeration.value.ldif-export.synopsis=Allows the user to request that the server process LDIF export tasks.
+property.default-root-privilege-name.syntax.enumeration.value.ldif-import.synopsis=Allows the user to request that the server process LDIF import tasks.
+property.default-root-privilege-name.syntax.enumeration.value.modify-acl.synopsis=Allows the associated user to modify the server's access control configuration.
+property.default-root-privilege-name.syntax.enumeration.value.password-reset.synopsis=Allows the user to reset user passwords.
+property.default-root-privilege-name.syntax.enumeration.value.privilege-change.synopsis=Allows the user to make changes to the set of defined root privileges, as well as to grant and revoke privileges for users.
+property.default-root-privilege-name.syntax.enumeration.value.proxied-auth.synopsis=Allows the user to use the proxied authorization control, or to perform a bind that specifies an alternate authorization identity.
+property.default-root-privilege-name.syntax.enumeration.value.server-restart.synopsis=Allows the user to request that the server perform an in-core restart.
+property.default-root-privilege-name.syntax.enumeration.value.server-shutdown.synopsis=Allows the user to request that the server shut down.
+property.default-root-privilege-name.syntax.enumeration.value.unindexed-search.synopsis=Allows the user to request that the server process a search that cannot be optimized using server indexes.
+property.default-root-privilege-name.syntax.enumeration.value.update-schema.synopsis=Allows the user to make changes to the server schema.
+relation.root-dn-user.user-friendly-name=Root DN User
+relation.root-dn-user.user-friendly-plural-name=Root DN Users
+relation.root-dn-user.synopsis=A Root DN User are administrative users who can granted special privileges that are not available to non-root users (for example, the ability to bind to the server in lockdown mode).
+relation.root-dn-user.description=By default a Root DN User inherits the default set of privileges defined in the Root DN configuration.
diff --git a/opends/src/admin/messages/RootDNCfgDefn_de.properties b/opends/src/admin/messages/RootDNCfgDefn_de.properties
new file mode 100644
index 0000000..aa1bb8e
--- /dev/null
+++ b/opends/src/admin/messages/RootDNCfgDefn_de.properties
@@ -0,0 +1,29 @@
+user-friendly-name=Root DN
+user-friendly-plural-name=Root Dns
+synopsis=The Root DN configuration contains all the Root DN Users defined in the Directory Server. In addition, it also defines the default set of privileges that Root DN Users automatically inherit.
+property.default-root-privilege-name.synopsis=Specifies the names of the privileges that root users will be granted by default.
+property.default-root-privilege-name.syntax.enumeration.value.backend-backup.synopsis=Allows the user to request that the server process backup tasks.
+property.default-root-privilege-name.syntax.enumeration.value.backend-restore.synopsis=Allows the user to request that the server process restore tasks.
+property.default-root-privilege-name.syntax.enumeration.value.bypass-acl.synopsis=Allows the associated user to bypass access control checks performed by the server.
+property.default-root-privilege-name.syntax.enumeration.value.cancel-request.synopsis=Allows the user to cancel operations in progress on other client connections.
+property.default-root-privilege-name.syntax.enumeration.value.config-read.synopsis=Allows the associated user to read the server configuration.
+property.default-root-privilege-name.syntax.enumeration.value.config-write.synopsis=Allows the associated user to update the server configuration. The config-read privilege is also required.
+property.default-root-privilege-name.syntax.enumeration.value.data-sync.synopsis=Allows the user to participate in data synchronization.
+property.default-root-privilege-name.syntax.enumeration.value.disconnect-client.synopsis=Allows the user to terminate other client connections.
+property.default-root-privilege-name.syntax.enumeration.value.jmx-notify.synopsis=Allows the associated user to subscribe to receive JMX notifications.
+property.default-root-privilege-name.syntax.enumeration.value.jmx-read.synopsis=Allows the associated user to perform JMX read operations.
+property.default-root-privilege-name.syntax.enumeration.value.jmx-write.synopsis=Allows the associated user to perform JMX write operations.
+property.default-root-privilege-name.syntax.enumeration.value.ldif-export.synopsis=Allows the user to request that the server process LDIF export tasks.
+property.default-root-privilege-name.syntax.enumeration.value.ldif-import.synopsis=Allows the user to request that the server process LDIF import tasks.
+property.default-root-privilege-name.syntax.enumeration.value.modify-acl.synopsis=Allows the associated user to modify the server's access control configuration.
+property.default-root-privilege-name.syntax.enumeration.value.password-reset.synopsis=Allows the user to reset user passwords.
+property.default-root-privilege-name.syntax.enumeration.value.privilege-change.synopsis=Allows the user to make changes to the set of defined root privileges, as well as to grant and revoke privileges for users.
+property.default-root-privilege-name.syntax.enumeration.value.proxied-auth.synopsis=Allows the user to use the proxied authorization control, or to perform a bind that specifies an alternate authorization identity.
+property.default-root-privilege-name.syntax.enumeration.value.server-restart.synopsis=Allows the user to request that the server perform an in-core restart.
+property.default-root-privilege-name.syntax.enumeration.value.server-shutdown.synopsis=Allows the user to request that the server shut down.
+property.default-root-privilege-name.syntax.enumeration.value.unindexed-search.synopsis=Allows the user to request that the server process a search that cannot be optimized using server indexes.
+property.default-root-privilege-name.syntax.enumeration.value.update-schema.synopsis=Allows the user to make changes to the server schema.
+relation.root-dn-user.user-friendly-name=Root DN User
+relation.root-dn-user.user-friendly-plural-name=Root DN Users
+relation.root-dn-user.synopsis=A Root DN User are administrative users who can granted special privileges that are not available to non-root users (for example, the ability to bind to the server in lockdown mode).
+relation.root-dn-user.description=By default a Root DN User inherits the default set of privileges defined in the Root DN configuration.
diff --git a/opends/src/admin/messages/RootDNCfgDefn_es.properties b/opends/src/admin/messages/RootDNCfgDefn_es.properties
new file mode 100644
index 0000000..aa1bb8e
--- /dev/null
+++ b/opends/src/admin/messages/RootDNCfgDefn_es.properties
@@ -0,0 +1,29 @@
+user-friendly-name=Root DN
+user-friendly-plural-name=Root Dns
+synopsis=The Root DN configuration contains all the Root DN Users defined in the Directory Server. In addition, it also defines the default set of privileges that Root DN Users automatically inherit.
+property.default-root-privilege-name.synopsis=Specifies the names of the privileges that root users will be granted by default.
+property.default-root-privilege-name.syntax.enumeration.value.backend-backup.synopsis=Allows the user to request that the server process backup tasks.
+property.default-root-privilege-name.syntax.enumeration.value.backend-restore.synopsis=Allows the user to request that the server process restore tasks.
+property.default-root-privilege-name.syntax.enumeration.value.bypass-acl.synopsis=Allows the associated user to bypass access control checks performed by the server.
+property.default-root-privilege-name.syntax.enumeration.value.cancel-request.synopsis=Allows the user to cancel operations in progress on other client connections.
+property.default-root-privilege-name.syntax.enumeration.value.config-read.synopsis=Allows the associated user to read the server configuration.
+property.default-root-privilege-name.syntax.enumeration.value.config-write.synopsis=Allows the associated user to update the server configuration. The config-read privilege is also required.
+property.default-root-privilege-name.syntax.enumeration.value.data-sync.synopsis=Allows the user to participate in data synchronization.
+property.default-root-privilege-name.syntax.enumeration.value.disconnect-client.synopsis=Allows the user to terminate other client connections.
+property.default-root-privilege-name.syntax.enumeration.value.jmx-notify.synopsis=Allows the associated user to subscribe to receive JMX notifications.
+property.default-root-privilege-name.syntax.enumeration.value.jmx-read.synopsis=Allows the associated user to perform JMX read operations.
+property.default-root-privilege-name.syntax.enumeration.value.jmx-write.synopsis=Allows the associated user to perform JMX write operations.
+property.default-root-privilege-name.syntax.enumeration.value.ldif-export.synopsis=Allows the user to request that the server process LDIF export tasks.
+property.default-root-privilege-name.syntax.enumeration.value.ldif-import.synopsis=Allows the user to request that the server process LDIF import tasks.
+property.default-root-privilege-name.syntax.enumeration.value.modify-acl.synopsis=Allows the associated user to modify the server's access control configuration.
+property.default-root-privilege-name.syntax.enumeration.value.password-reset.synopsis=Allows the user to reset user passwords.
+property.default-root-privilege-name.syntax.enumeration.value.privilege-change.synopsis=Allows the user to make changes to the set of defined root privileges, as well as to grant and revoke privileges for users.
+property.default-root-privilege-name.syntax.enumeration.value.proxied-auth.synopsis=Allows the user to use the proxied authorization control, or to perform a bind that specifies an alternate authorization identity.
+property.default-root-privilege-name.syntax.enumeration.value.server-restart.synopsis=Allows the user to request that the server perform an in-core restart.
+property.default-root-privilege-name.syntax.enumeration.value.server-shutdown.synopsis=Allows the user to request that the server shut down.
+property.default-root-privilege-name.syntax.enumeration.value.unindexed-search.synopsis=Allows the user to request that the server process a search that cannot be optimized using server indexes.
+property.default-root-privilege-name.syntax.enumeration.value.update-schema.synopsis=Allows the user to make changes to the server schema.
+relation.root-dn-user.user-friendly-name=Root DN User
+relation.root-dn-user.user-friendly-plural-name=Root DN Users
+relation.root-dn-user.synopsis=A Root DN User are administrative users who can granted special privileges that are not available to non-root users (for example, the ability to bind to the server in lockdown mode).
+relation.root-dn-user.description=By default a Root DN User inherits the default set of privileges defined in the Root DN configuration.
diff --git a/opends/src/admin/messages/RootDNCfgDefn_fr.properties b/opends/src/admin/messages/RootDNCfgDefn_fr.properties
new file mode 100644
index 0000000..aa1bb8e
--- /dev/null
+++ b/opends/src/admin/messages/RootDNCfgDefn_fr.properties
@@ -0,0 +1,29 @@
+user-friendly-name=Root DN
+user-friendly-plural-name=Root Dns
+synopsis=The Root DN configuration contains all the Root DN Users defined in the Directory Server. In addition, it also defines the default set of privileges that Root DN Users automatically inherit.
+property.default-root-privilege-name.synopsis=Specifies the names of the privileges that root users will be granted by default.
+property.default-root-privilege-name.syntax.enumeration.value.backend-backup.synopsis=Allows the user to request that the server process backup tasks.
+property.default-root-privilege-name.syntax.enumeration.value.backend-restore.synopsis=Allows the user to request that the server process restore tasks.
+property.default-root-privilege-name.syntax.enumeration.value.bypass-acl.synopsis=Allows the associated user to bypass access control checks performed by the server.
+property.default-root-privilege-name.syntax.enumeration.value.cancel-request.synopsis=Allows the user to cancel operations in progress on other client connections.
+property.default-root-privilege-name.syntax.enumeration.value.config-read.synopsis=Allows the associated user to read the server configuration.
+property.default-root-privilege-name.syntax.enumeration.value.config-write.synopsis=Allows the associated user to update the server configuration. The config-read privilege is also required.
+property.default-root-privilege-name.syntax.enumeration.value.data-sync.synopsis=Allows the user to participate in data synchronization.
+property.default-root-privilege-name.syntax.enumeration.value.disconnect-client.synopsis=Allows the user to terminate other client connections.
+property.default-root-privilege-name.syntax.enumeration.value.jmx-notify.synopsis=Allows the associated user to subscribe to receive JMX notifications.
+property.default-root-privilege-name.syntax.enumeration.value.jmx-read.synopsis=Allows the associated user to perform JMX read operations.
+property.default-root-privilege-name.syntax.enumeration.value.jmx-write.synopsis=Allows the associated user to perform JMX write operations.
+property.default-root-privilege-name.syntax.enumeration.value.ldif-export.synopsis=Allows the user to request that the server process LDIF export tasks.
+property.default-root-privilege-name.syntax.enumeration.value.ldif-import.synopsis=Allows the user to request that the server process LDIF import tasks.
+property.default-root-privilege-name.syntax.enumeration.value.modify-acl.synopsis=Allows the associated user to modify the server's access control configuration.
+property.default-root-privilege-name.syntax.enumeration.value.password-reset.synopsis=Allows the user to reset user passwords.
+property.default-root-privilege-name.syntax.enumeration.value.privilege-change.synopsis=Allows the user to make changes to the set of defined root privileges, as well as to grant and revoke privileges for users.
+property.default-root-privilege-name.syntax.enumeration.value.proxied-auth.synopsis=Allows the user to use the proxied authorization control, or to perform a bind that specifies an alternate authorization identity.
+property.default-root-privilege-name.syntax.enumeration.value.server-restart.synopsis=Allows the user to request that the server perform an in-core restart.
+property.default-root-privilege-name.syntax.enumeration.value.server-shutdown.synopsis=Allows the user to request that the server shut down.
+property.default-root-privilege-name.syntax.enumeration.value.unindexed-search.synopsis=Allows the user to request that the server process a search that cannot be optimized using server indexes.
+property.default-root-privilege-name.syntax.enumeration.value.update-schema.synopsis=Allows the user to make changes to the server schema.
+relation.root-dn-user.user-friendly-name=Root DN User
+relation.root-dn-user.user-friendly-plural-name=Root DN Users
+relation.root-dn-user.synopsis=A Root DN User are administrative users who can granted special privileges that are not available to non-root users (for example, the ability to bind to the server in lockdown mode).
+relation.root-dn-user.description=By default a Root DN User inherits the default set of privileges defined in the Root DN configuration.
diff --git a/opends/src/admin/messages/RootDNCfgDefn_ja.properties b/opends/src/admin/messages/RootDNCfgDefn_ja.properties
new file mode 100644
index 0000000..aa1bb8e
--- /dev/null
+++ b/opends/src/admin/messages/RootDNCfgDefn_ja.properties
@@ -0,0 +1,29 @@
+user-friendly-name=Root DN
+user-friendly-plural-name=Root Dns
+synopsis=The Root DN configuration contains all the Root DN Users defined in the Directory Server. In addition, it also defines the default set of privileges that Root DN Users automatically inherit.
+property.default-root-privilege-name.synopsis=Specifies the names of the privileges that root users will be granted by default.
+property.default-root-privilege-name.syntax.enumeration.value.backend-backup.synopsis=Allows the user to request that the server process backup tasks.
+property.default-root-privilege-name.syntax.enumeration.value.backend-restore.synopsis=Allows the user to request that the server process restore tasks.
+property.default-root-privilege-name.syntax.enumeration.value.bypass-acl.synopsis=Allows the associated user to bypass access control checks performed by the server.
+property.default-root-privilege-name.syntax.enumeration.value.cancel-request.synopsis=Allows the user to cancel operations in progress on other client connections.
+property.default-root-privilege-name.syntax.enumeration.value.config-read.synopsis=Allows the associated user to read the server configuration.
+property.default-root-privilege-name.syntax.enumeration.value.config-write.synopsis=Allows the associated user to update the server configuration. The config-read privilege is also required.
+property.default-root-privilege-name.syntax.enumeration.value.data-sync.synopsis=Allows the user to participate in data synchronization.
+property.default-root-privilege-name.syntax.enumeration.value.disconnect-client.synopsis=Allows the user to terminate other client connections.
+property.default-root-privilege-name.syntax.enumeration.value.jmx-notify.synopsis=Allows the associated user to subscribe to receive JMX notifications.
+property.default-root-privilege-name.syntax.enumeration.value.jmx-read.synopsis=Allows the associated user to perform JMX read operations.
+property.default-root-privilege-name.syntax.enumeration.value.jmx-write.synopsis=Allows the associated user to perform JMX write operations.
+property.default-root-privilege-name.syntax.enumeration.value.ldif-export.synopsis=Allows the user to request that the server process LDIF export tasks.
+property.default-root-privilege-name.syntax.enumeration.value.ldif-import.synopsis=Allows the user to request that the server process LDIF import tasks.
+property.default-root-privilege-name.syntax.enumeration.value.modify-acl.synopsis=Allows the associated user to modify the server's access control configuration.
+property.default-root-privilege-name.syntax.enumeration.value.password-reset.synopsis=Allows the user to reset user passwords.
+property.default-root-privilege-name.syntax.enumeration.value.privilege-change.synopsis=Allows the user to make changes to the set of defined root privileges, as well as to grant and revoke privileges for users.
+property.default-root-privilege-name.syntax.enumeration.value.proxied-auth.synopsis=Allows the user to use the proxied authorization control, or to perform a bind that specifies an alternate authorization identity.
+property.default-root-privilege-name.syntax.enumeration.value.server-restart.synopsis=Allows the user to request that the server perform an in-core restart.
+property.default-root-privilege-name.syntax.enumeration.value.server-shutdown.synopsis=Allows the user to request that the server shut down.
+property.default-root-privilege-name.syntax.enumeration.value.unindexed-search.synopsis=Allows the user to request that the server process a search that cannot be optimized using server indexes.
+property.default-root-privilege-name.syntax.enumeration.value.update-schema.synopsis=Allows the user to make changes to the server schema.
+relation.root-dn-user.user-friendly-name=Root DN User
+relation.root-dn-user.user-friendly-plural-name=Root DN Users
+relation.root-dn-user.synopsis=A Root DN User are administrative users who can granted special privileges that are not available to non-root users (for example, the ability to bind to the server in lockdown mode).
+relation.root-dn-user.description=By default a Root DN User inherits the default set of privileges defined in the Root DN configuration.
diff --git a/opends/src/admin/messages/RootDNCfgDefn_ko.properties b/opends/src/admin/messages/RootDNCfgDefn_ko.properties
new file mode 100644
index 0000000..aa1bb8e
--- /dev/null
+++ b/opends/src/admin/messages/RootDNCfgDefn_ko.properties
@@ -0,0 +1,29 @@
+user-friendly-name=Root DN
+user-friendly-plural-name=Root Dns
+synopsis=The Root DN configuration contains all the Root DN Users defined in the Directory Server. In addition, it also defines the default set of privileges that Root DN Users automatically inherit.
+property.default-root-privilege-name.synopsis=Specifies the names of the privileges that root users will be granted by default.
+property.default-root-privilege-name.syntax.enumeration.value.backend-backup.synopsis=Allows the user to request that the server process backup tasks.
+property.default-root-privilege-name.syntax.enumeration.value.backend-restore.synopsis=Allows the user to request that the server process restore tasks.
+property.default-root-privilege-name.syntax.enumeration.value.bypass-acl.synopsis=Allows the associated user to bypass access control checks performed by the server.
+property.default-root-privilege-name.syntax.enumeration.value.cancel-request.synopsis=Allows the user to cancel operations in progress on other client connections.
+property.default-root-privilege-name.syntax.enumeration.value.config-read.synopsis=Allows the associated user to read the server configuration.
+property.default-root-privilege-name.syntax.enumeration.value.config-write.synopsis=Allows the associated user to update the server configuration. The config-read privilege is also required.
+property.default-root-privilege-name.syntax.enumeration.value.data-sync.synopsis=Allows the user to participate in data synchronization.
+property.default-root-privilege-name.syntax.enumeration.value.disconnect-client.synopsis=Allows the user to terminate other client connections.
+property.default-root-privilege-name.syntax.enumeration.value.jmx-notify.synopsis=Allows the associated user to subscribe to receive JMX notifications.
+property.default-root-privilege-name.syntax.enumeration.value.jmx-read.synopsis=Allows the associated user to perform JMX read operations.
+property.default-root-privilege-name.syntax.enumeration.value.jmx-write.synopsis=Allows the associated user to perform JMX write operations.
+property.default-root-privilege-name.syntax.enumeration.value.ldif-export.synopsis=Allows the user to request that the server process LDIF export tasks.
+property.default-root-privilege-name.syntax.enumeration.value.ldif-import.synopsis=Allows the user to request that the server process LDIF import tasks.
+property.default-root-privilege-name.syntax.enumeration.value.modify-acl.synopsis=Allows the associated user to modify the server's access control configuration.
+property.default-root-privilege-name.syntax.enumeration.value.password-reset.synopsis=Allows the user to reset user passwords.
+property.default-root-privilege-name.syntax.enumeration.value.privilege-change.synopsis=Allows the user to make changes to the set of defined root privileges, as well as to grant and revoke privileges for users.
+property.default-root-privilege-name.syntax.enumeration.value.proxied-auth.synopsis=Allows the user to use the proxied authorization control, or to perform a bind that specifies an alternate authorization identity.
+property.default-root-privilege-name.syntax.enumeration.value.server-restart.synopsis=Allows the user to request that the server perform an in-core restart.
+property.default-root-privilege-name.syntax.enumeration.value.server-shutdown.synopsis=Allows the user to request that the server shut down.
+property.default-root-privilege-name.syntax.enumeration.value.unindexed-search.synopsis=Allows the user to request that the server process a search that cannot be optimized using server indexes.
+property.default-root-privilege-name.syntax.enumeration.value.update-schema.synopsis=Allows the user to make changes to the server schema.
+relation.root-dn-user.user-friendly-name=Root DN User
+relation.root-dn-user.user-friendly-plural-name=Root DN Users
+relation.root-dn-user.synopsis=A Root DN User are administrative users who can granted special privileges that are not available to non-root users (for example, the ability to bind to the server in lockdown mode).
+relation.root-dn-user.description=By default a Root DN User inherits the default set of privileges defined in the Root DN configuration.
diff --git a/opends/src/admin/messages/RootDNCfgDefn_zh_CN.properties b/opends/src/admin/messages/RootDNCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..aa1bb8e
--- /dev/null
+++ b/opends/src/admin/messages/RootDNCfgDefn_zh_CN.properties
@@ -0,0 +1,29 @@
+user-friendly-name=Root DN
+user-friendly-plural-name=Root Dns
+synopsis=The Root DN configuration contains all the Root DN Users defined in the Directory Server. In addition, it also defines the default set of privileges that Root DN Users automatically inherit.
+property.default-root-privilege-name.synopsis=Specifies the names of the privileges that root users will be granted by default.
+property.default-root-privilege-name.syntax.enumeration.value.backend-backup.synopsis=Allows the user to request that the server process backup tasks.
+property.default-root-privilege-name.syntax.enumeration.value.backend-restore.synopsis=Allows the user to request that the server process restore tasks.
+property.default-root-privilege-name.syntax.enumeration.value.bypass-acl.synopsis=Allows the associated user to bypass access control checks performed by the server.
+property.default-root-privilege-name.syntax.enumeration.value.cancel-request.synopsis=Allows the user to cancel operations in progress on other client connections.
+property.default-root-privilege-name.syntax.enumeration.value.config-read.synopsis=Allows the associated user to read the server configuration.
+property.default-root-privilege-name.syntax.enumeration.value.config-write.synopsis=Allows the associated user to update the server configuration. The config-read privilege is also required.
+property.default-root-privilege-name.syntax.enumeration.value.data-sync.synopsis=Allows the user to participate in data synchronization.
+property.default-root-privilege-name.syntax.enumeration.value.disconnect-client.synopsis=Allows the user to terminate other client connections.
+property.default-root-privilege-name.syntax.enumeration.value.jmx-notify.synopsis=Allows the associated user to subscribe to receive JMX notifications.
+property.default-root-privilege-name.syntax.enumeration.value.jmx-read.synopsis=Allows the associated user to perform JMX read operations.
+property.default-root-privilege-name.syntax.enumeration.value.jmx-write.synopsis=Allows the associated user to perform JMX write operations.
+property.default-root-privilege-name.syntax.enumeration.value.ldif-export.synopsis=Allows the user to request that the server process LDIF export tasks.
+property.default-root-privilege-name.syntax.enumeration.value.ldif-import.synopsis=Allows the user to request that the server process LDIF import tasks.
+property.default-root-privilege-name.syntax.enumeration.value.modify-acl.synopsis=Allows the associated user to modify the server's access control configuration.
+property.default-root-privilege-name.syntax.enumeration.value.password-reset.synopsis=Allows the user to reset user passwords.
+property.default-root-privilege-name.syntax.enumeration.value.privilege-change.synopsis=Allows the user to make changes to the set of defined root privileges, as well as to grant and revoke privileges for users.
+property.default-root-privilege-name.syntax.enumeration.value.proxied-auth.synopsis=Allows the user to use the proxied authorization control, or to perform a bind that specifies an alternate authorization identity.
+property.default-root-privilege-name.syntax.enumeration.value.server-restart.synopsis=Allows the user to request that the server perform an in-core restart.
+property.default-root-privilege-name.syntax.enumeration.value.server-shutdown.synopsis=Allows the user to request that the server shut down.
+property.default-root-privilege-name.syntax.enumeration.value.unindexed-search.synopsis=Allows the user to request that the server process a search that cannot be optimized using server indexes.
+property.default-root-privilege-name.syntax.enumeration.value.update-schema.synopsis=Allows the user to make changes to the server schema.
+relation.root-dn-user.user-friendly-name=Root DN User
+relation.root-dn-user.user-friendly-plural-name=Root DN Users
+relation.root-dn-user.synopsis=A Root DN User are administrative users who can granted special privileges that are not available to non-root users (for example, the ability to bind to the server in lockdown mode).
+relation.root-dn-user.description=By default a Root DN User inherits the default set of privileges defined in the Root DN configuration.
diff --git a/opends/src/admin/messages/RootDNCfgDefn_zh_TW.properties b/opends/src/admin/messages/RootDNCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..aa1bb8e
--- /dev/null
+++ b/opends/src/admin/messages/RootDNCfgDefn_zh_TW.properties
@@ -0,0 +1,29 @@
+user-friendly-name=Root DN
+user-friendly-plural-name=Root Dns
+synopsis=The Root DN configuration contains all the Root DN Users defined in the Directory Server. In addition, it also defines the default set of privileges that Root DN Users automatically inherit.
+property.default-root-privilege-name.synopsis=Specifies the names of the privileges that root users will be granted by default.
+property.default-root-privilege-name.syntax.enumeration.value.backend-backup.synopsis=Allows the user to request that the server process backup tasks.
+property.default-root-privilege-name.syntax.enumeration.value.backend-restore.synopsis=Allows the user to request that the server process restore tasks.
+property.default-root-privilege-name.syntax.enumeration.value.bypass-acl.synopsis=Allows the associated user to bypass access control checks performed by the server.
+property.default-root-privilege-name.syntax.enumeration.value.cancel-request.synopsis=Allows the user to cancel operations in progress on other client connections.
+property.default-root-privilege-name.syntax.enumeration.value.config-read.synopsis=Allows the associated user to read the server configuration.
+property.default-root-privilege-name.syntax.enumeration.value.config-write.synopsis=Allows the associated user to update the server configuration. The config-read privilege is also required.
+property.default-root-privilege-name.syntax.enumeration.value.data-sync.synopsis=Allows the user to participate in data synchronization.
+property.default-root-privilege-name.syntax.enumeration.value.disconnect-client.synopsis=Allows the user to terminate other client connections.
+property.default-root-privilege-name.syntax.enumeration.value.jmx-notify.synopsis=Allows the associated user to subscribe to receive JMX notifications.
+property.default-root-privilege-name.syntax.enumeration.value.jmx-read.synopsis=Allows the associated user to perform JMX read operations.
+property.default-root-privilege-name.syntax.enumeration.value.jmx-write.synopsis=Allows the associated user to perform JMX write operations.
+property.default-root-privilege-name.syntax.enumeration.value.ldif-export.synopsis=Allows the user to request that the server process LDIF export tasks.
+property.default-root-privilege-name.syntax.enumeration.value.ldif-import.synopsis=Allows the user to request that the server process LDIF import tasks.
+property.default-root-privilege-name.syntax.enumeration.value.modify-acl.synopsis=Allows the associated user to modify the server's access control configuration.
+property.default-root-privilege-name.syntax.enumeration.value.password-reset.synopsis=Allows the user to reset user passwords.
+property.default-root-privilege-name.syntax.enumeration.value.privilege-change.synopsis=Allows the user to make changes to the set of defined root privileges, as well as to grant and revoke privileges for users.
+property.default-root-privilege-name.syntax.enumeration.value.proxied-auth.synopsis=Allows the user to use the proxied authorization control, or to perform a bind that specifies an alternate authorization identity.
+property.default-root-privilege-name.syntax.enumeration.value.server-restart.synopsis=Allows the user to request that the server perform an in-core restart.
+property.default-root-privilege-name.syntax.enumeration.value.server-shutdown.synopsis=Allows the user to request that the server shut down.
+property.default-root-privilege-name.syntax.enumeration.value.unindexed-search.synopsis=Allows the user to request that the server process a search that cannot be optimized using server indexes.
+property.default-root-privilege-name.syntax.enumeration.value.update-schema.synopsis=Allows the user to make changes to the server schema.
+relation.root-dn-user.user-friendly-name=Root DN User
+relation.root-dn-user.user-friendly-plural-name=Root DN Users
+relation.root-dn-user.synopsis=A Root DN User are administrative users who can granted special privileges that are not available to non-root users (for example, the ability to bind to the server in lockdown mode).
+relation.root-dn-user.description=By default a Root DN User inherits the default set of privileges defined in the Root DN configuration.
diff --git a/opends/src/admin/messages/RootDNUserCfgDefn.properties b/opends/src/admin/messages/RootDNUserCfgDefn.properties
new file mode 100644
index 0000000..87aa596
--- /dev/null
+++ b/opends/src/admin/messages/RootDNUserCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Root DN User
+user-friendly-plural-name=Root DN Users
+synopsis=A Root DN User are administrative users who can granted special privileges that are not available to non-root users (for example, the ability to bind to the server in lockdown mode).
+description=By default a Root DN User inherits the default set of privileges defined in the Root DN configuration.
+property.alternate-bind-dn.synopsis=Specifies one or more alternate DNs that can be used to bind to the server as this root user.
+property.alternate-bind-dn.default-behavior.alias.synopsis=This root user is allowed to bind only using the DN of the associated configuration entry.
diff --git a/opends/src/admin/messages/RootDNUserCfgDefn_de.properties b/opends/src/admin/messages/RootDNUserCfgDefn_de.properties
new file mode 100644
index 0000000..87aa596
--- /dev/null
+++ b/opends/src/admin/messages/RootDNUserCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Root DN User
+user-friendly-plural-name=Root DN Users
+synopsis=A Root DN User are administrative users who can granted special privileges that are not available to non-root users (for example, the ability to bind to the server in lockdown mode).
+description=By default a Root DN User inherits the default set of privileges defined in the Root DN configuration.
+property.alternate-bind-dn.synopsis=Specifies one or more alternate DNs that can be used to bind to the server as this root user.
+property.alternate-bind-dn.default-behavior.alias.synopsis=This root user is allowed to bind only using the DN of the associated configuration entry.
diff --git a/opends/src/admin/messages/RootDNUserCfgDefn_es.properties b/opends/src/admin/messages/RootDNUserCfgDefn_es.properties
new file mode 100644
index 0000000..87aa596
--- /dev/null
+++ b/opends/src/admin/messages/RootDNUserCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Root DN User
+user-friendly-plural-name=Root DN Users
+synopsis=A Root DN User are administrative users who can granted special privileges that are not available to non-root users (for example, the ability to bind to the server in lockdown mode).
+description=By default a Root DN User inherits the default set of privileges defined in the Root DN configuration.
+property.alternate-bind-dn.synopsis=Specifies one or more alternate DNs that can be used to bind to the server as this root user.
+property.alternate-bind-dn.default-behavior.alias.synopsis=This root user is allowed to bind only using the DN of the associated configuration entry.
diff --git a/opends/src/admin/messages/RootDNUserCfgDefn_fr.properties b/opends/src/admin/messages/RootDNUserCfgDefn_fr.properties
new file mode 100644
index 0000000..87aa596
--- /dev/null
+++ b/opends/src/admin/messages/RootDNUserCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Root DN User
+user-friendly-plural-name=Root DN Users
+synopsis=A Root DN User are administrative users who can granted special privileges that are not available to non-root users (for example, the ability to bind to the server in lockdown mode).
+description=By default a Root DN User inherits the default set of privileges defined in the Root DN configuration.
+property.alternate-bind-dn.synopsis=Specifies one or more alternate DNs that can be used to bind to the server as this root user.
+property.alternate-bind-dn.default-behavior.alias.synopsis=This root user is allowed to bind only using the DN of the associated configuration entry.
diff --git a/opends/src/admin/messages/RootDNUserCfgDefn_ja.properties b/opends/src/admin/messages/RootDNUserCfgDefn_ja.properties
new file mode 100644
index 0000000..87aa596
--- /dev/null
+++ b/opends/src/admin/messages/RootDNUserCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Root DN User
+user-friendly-plural-name=Root DN Users
+synopsis=A Root DN User are administrative users who can granted special privileges that are not available to non-root users (for example, the ability to bind to the server in lockdown mode).
+description=By default a Root DN User inherits the default set of privileges defined in the Root DN configuration.
+property.alternate-bind-dn.synopsis=Specifies one or more alternate DNs that can be used to bind to the server as this root user.
+property.alternate-bind-dn.default-behavior.alias.synopsis=This root user is allowed to bind only using the DN of the associated configuration entry.
diff --git a/opends/src/admin/messages/RootDNUserCfgDefn_ko.properties b/opends/src/admin/messages/RootDNUserCfgDefn_ko.properties
new file mode 100644
index 0000000..87aa596
--- /dev/null
+++ b/opends/src/admin/messages/RootDNUserCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Root DN User
+user-friendly-plural-name=Root DN Users
+synopsis=A Root DN User are administrative users who can granted special privileges that are not available to non-root users (for example, the ability to bind to the server in lockdown mode).
+description=By default a Root DN User inherits the default set of privileges defined in the Root DN configuration.
+property.alternate-bind-dn.synopsis=Specifies one or more alternate DNs that can be used to bind to the server as this root user.
+property.alternate-bind-dn.default-behavior.alias.synopsis=This root user is allowed to bind only using the DN of the associated configuration entry.
diff --git a/opends/src/admin/messages/RootDNUserCfgDefn_zh_CN.properties b/opends/src/admin/messages/RootDNUserCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..87aa596
--- /dev/null
+++ b/opends/src/admin/messages/RootDNUserCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Root DN User
+user-friendly-plural-name=Root DN Users
+synopsis=A Root DN User are administrative users who can granted special privileges that are not available to non-root users (for example, the ability to bind to the server in lockdown mode).
+description=By default a Root DN User inherits the default set of privileges defined in the Root DN configuration.
+property.alternate-bind-dn.synopsis=Specifies one or more alternate DNs that can be used to bind to the server as this root user.
+property.alternate-bind-dn.default-behavior.alias.synopsis=This root user is allowed to bind only using the DN of the associated configuration entry.
diff --git a/opends/src/admin/messages/RootDNUserCfgDefn_zh_TW.properties b/opends/src/admin/messages/RootDNUserCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..87aa596
--- /dev/null
+++ b/opends/src/admin/messages/RootDNUserCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Root DN User
+user-friendly-plural-name=Root DN Users
+synopsis=A Root DN User are administrative users who can granted special privileges that are not available to non-root users (for example, the ability to bind to the server in lockdown mode).
+description=By default a Root DN User inherits the default set of privileges defined in the Root DN configuration.
+property.alternate-bind-dn.synopsis=Specifies one or more alternate DNs that can be used to bind to the server as this root user.
+property.alternate-bind-dn.default-behavior.alias.synopsis=This root user is allowed to bind only using the DN of the associated configuration entry.
diff --git a/opends/src/admin/messages/RootDSEBackendCfgDefn.properties b/opends/src/admin/messages/RootDSEBackendCfgDefn.properties
new file mode 100644
index 0000000..08c5228
--- /dev/null
+++ b/opends/src/admin/messages/RootDSEBackendCfgDefn.properties
@@ -0,0 +1,7 @@
+user-friendly-name=Root DSE Backend
+user-friendly-plural-name=Root DSE Backends
+synopsis=The Root DSE Backend contains the Directory Server root DSE.
+description=This is a special meta-backend that dynamically generates the root DSE entry for base-level searches and simply redirects to other backends for operations in other scopes.
+property.show-all-attributes.synopsis=Indicates whether all attributes in the root DSE are to be treated like user attributes (and therefore returned to clients by default) regardless of the Directory Server schema configuration.
+property.subordinate-base-dn.synopsis=Specifies the set of base DNs used for singleLevel, wholeSubtree, and subordinateSubtree searches based at the root DSE.
+property.subordinate-base-dn.default-behavior.alias.synopsis=The set of all user-defined suffixes is used.
diff --git a/opends/src/admin/messages/RootDSEBackendCfgDefn_de.properties b/opends/src/admin/messages/RootDSEBackendCfgDefn_de.properties
new file mode 100644
index 0000000..08c5228
--- /dev/null
+++ b/opends/src/admin/messages/RootDSEBackendCfgDefn_de.properties
@@ -0,0 +1,7 @@
+user-friendly-name=Root DSE Backend
+user-friendly-plural-name=Root DSE Backends
+synopsis=The Root DSE Backend contains the Directory Server root DSE.
+description=This is a special meta-backend that dynamically generates the root DSE entry for base-level searches and simply redirects to other backends for operations in other scopes.
+property.show-all-attributes.synopsis=Indicates whether all attributes in the root DSE are to be treated like user attributes (and therefore returned to clients by default) regardless of the Directory Server schema configuration.
+property.subordinate-base-dn.synopsis=Specifies the set of base DNs used for singleLevel, wholeSubtree, and subordinateSubtree searches based at the root DSE.
+property.subordinate-base-dn.default-behavior.alias.synopsis=The set of all user-defined suffixes is used.
diff --git a/opends/src/admin/messages/RootDSEBackendCfgDefn_es.properties b/opends/src/admin/messages/RootDSEBackendCfgDefn_es.properties
new file mode 100644
index 0000000..08c5228
--- /dev/null
+++ b/opends/src/admin/messages/RootDSEBackendCfgDefn_es.properties
@@ -0,0 +1,7 @@
+user-friendly-name=Root DSE Backend
+user-friendly-plural-name=Root DSE Backends
+synopsis=The Root DSE Backend contains the Directory Server root DSE.
+description=This is a special meta-backend that dynamically generates the root DSE entry for base-level searches and simply redirects to other backends for operations in other scopes.
+property.show-all-attributes.synopsis=Indicates whether all attributes in the root DSE are to be treated like user attributes (and therefore returned to clients by default) regardless of the Directory Server schema configuration.
+property.subordinate-base-dn.synopsis=Specifies the set of base DNs used for singleLevel, wholeSubtree, and subordinateSubtree searches based at the root DSE.
+property.subordinate-base-dn.default-behavior.alias.synopsis=The set of all user-defined suffixes is used.
diff --git a/opends/src/admin/messages/RootDSEBackendCfgDefn_fr.properties b/opends/src/admin/messages/RootDSEBackendCfgDefn_fr.properties
new file mode 100644
index 0000000..08c5228
--- /dev/null
+++ b/opends/src/admin/messages/RootDSEBackendCfgDefn_fr.properties
@@ -0,0 +1,7 @@
+user-friendly-name=Root DSE Backend
+user-friendly-plural-name=Root DSE Backends
+synopsis=The Root DSE Backend contains the Directory Server root DSE.
+description=This is a special meta-backend that dynamically generates the root DSE entry for base-level searches and simply redirects to other backends for operations in other scopes.
+property.show-all-attributes.synopsis=Indicates whether all attributes in the root DSE are to be treated like user attributes (and therefore returned to clients by default) regardless of the Directory Server schema configuration.
+property.subordinate-base-dn.synopsis=Specifies the set of base DNs used for singleLevel, wholeSubtree, and subordinateSubtree searches based at the root DSE.
+property.subordinate-base-dn.default-behavior.alias.synopsis=The set of all user-defined suffixes is used.
diff --git a/opends/src/admin/messages/RootDSEBackendCfgDefn_ja.properties b/opends/src/admin/messages/RootDSEBackendCfgDefn_ja.properties
new file mode 100644
index 0000000..08c5228
--- /dev/null
+++ b/opends/src/admin/messages/RootDSEBackendCfgDefn_ja.properties
@@ -0,0 +1,7 @@
+user-friendly-name=Root DSE Backend
+user-friendly-plural-name=Root DSE Backends
+synopsis=The Root DSE Backend contains the Directory Server root DSE.
+description=This is a special meta-backend that dynamically generates the root DSE entry for base-level searches and simply redirects to other backends for operations in other scopes.
+property.show-all-attributes.synopsis=Indicates whether all attributes in the root DSE are to be treated like user attributes (and therefore returned to clients by default) regardless of the Directory Server schema configuration.
+property.subordinate-base-dn.synopsis=Specifies the set of base DNs used for singleLevel, wholeSubtree, and subordinateSubtree searches based at the root DSE.
+property.subordinate-base-dn.default-behavior.alias.synopsis=The set of all user-defined suffixes is used.
diff --git a/opends/src/admin/messages/RootDSEBackendCfgDefn_ko.properties b/opends/src/admin/messages/RootDSEBackendCfgDefn_ko.properties
new file mode 100644
index 0000000..08c5228
--- /dev/null
+++ b/opends/src/admin/messages/RootDSEBackendCfgDefn_ko.properties
@@ -0,0 +1,7 @@
+user-friendly-name=Root DSE Backend
+user-friendly-plural-name=Root DSE Backends
+synopsis=The Root DSE Backend contains the Directory Server root DSE.
+description=This is a special meta-backend that dynamically generates the root DSE entry for base-level searches and simply redirects to other backends for operations in other scopes.
+property.show-all-attributes.synopsis=Indicates whether all attributes in the root DSE are to be treated like user attributes (and therefore returned to clients by default) regardless of the Directory Server schema configuration.
+property.subordinate-base-dn.synopsis=Specifies the set of base DNs used for singleLevel, wholeSubtree, and subordinateSubtree searches based at the root DSE.
+property.subordinate-base-dn.default-behavior.alias.synopsis=The set of all user-defined suffixes is used.
diff --git a/opends/src/admin/messages/RootDSEBackendCfgDefn_zh_CN.properties b/opends/src/admin/messages/RootDSEBackendCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..08c5228
--- /dev/null
+++ b/opends/src/admin/messages/RootDSEBackendCfgDefn_zh_CN.properties
@@ -0,0 +1,7 @@
+user-friendly-name=Root DSE Backend
+user-friendly-plural-name=Root DSE Backends
+synopsis=The Root DSE Backend contains the Directory Server root DSE.
+description=This is a special meta-backend that dynamically generates the root DSE entry for base-level searches and simply redirects to other backends for operations in other scopes.
+property.show-all-attributes.synopsis=Indicates whether all attributes in the root DSE are to be treated like user attributes (and therefore returned to clients by default) regardless of the Directory Server schema configuration.
+property.subordinate-base-dn.synopsis=Specifies the set of base DNs used for singleLevel, wholeSubtree, and subordinateSubtree searches based at the root DSE.
+property.subordinate-base-dn.default-behavior.alias.synopsis=The set of all user-defined suffixes is used.
diff --git a/opends/src/admin/messages/RootDSEBackendCfgDefn_zh_TW.properties b/opends/src/admin/messages/RootDSEBackendCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..08c5228
--- /dev/null
+++ b/opends/src/admin/messages/RootDSEBackendCfgDefn_zh_TW.properties
@@ -0,0 +1,7 @@
+user-friendly-name=Root DSE Backend
+user-friendly-plural-name=Root DSE Backends
+synopsis=The Root DSE Backend contains the Directory Server root DSE.
+description=This is a special meta-backend that dynamically generates the root DSE entry for base-level searches and simply redirects to other backends for operations in other scopes.
+property.show-all-attributes.synopsis=Indicates whether all attributes in the root DSE are to be treated like user attributes (and therefore returned to clients by default) regardless of the Directory Server schema configuration.
+property.subordinate-base-dn.synopsis=Specifies the set of base DNs used for singleLevel, wholeSubtree, and subordinateSubtree searches based at the root DSE.
+property.subordinate-base-dn.default-behavior.alias.synopsis=The set of all user-defined suffixes is used.
diff --git a/opends/src/admin/messages/SASLMechanismHandlerCfgDefn.properties b/opends/src/admin/messages/SASLMechanismHandlerCfgDefn.properties
new file mode 100644
index 0000000..7a97303
--- /dev/null
+++ b/opends/src/admin/messages/SASLMechanismHandlerCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=SASL Mechanism Handler
+user-friendly-plural-name=SASL Mechanism Handlers
+synopsis=The SASL mechanism handler configuration entry is the parent for all SASL mechanism handlers defined in the OpenDS Directory Server.
+description=SASL mechanism handlers are responsible for authenticating users during the course of processing a SASL (Simple Authentication and Security Layer, as defined in RFC 4422) bind.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/SASLMechanismHandlerCfgDefn_de.properties b/opends/src/admin/messages/SASLMechanismHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..7a97303
--- /dev/null
+++ b/opends/src/admin/messages/SASLMechanismHandlerCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=SASL Mechanism Handler
+user-friendly-plural-name=SASL Mechanism Handlers
+synopsis=The SASL mechanism handler configuration entry is the parent for all SASL mechanism handlers defined in the OpenDS Directory Server.
+description=SASL mechanism handlers are responsible for authenticating users during the course of processing a SASL (Simple Authentication and Security Layer, as defined in RFC 4422) bind.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/SASLMechanismHandlerCfgDefn_es.properties b/opends/src/admin/messages/SASLMechanismHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..7a97303
--- /dev/null
+++ b/opends/src/admin/messages/SASLMechanismHandlerCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=SASL Mechanism Handler
+user-friendly-plural-name=SASL Mechanism Handlers
+synopsis=The SASL mechanism handler configuration entry is the parent for all SASL mechanism handlers defined in the OpenDS Directory Server.
+description=SASL mechanism handlers are responsible for authenticating users during the course of processing a SASL (Simple Authentication and Security Layer, as defined in RFC 4422) bind.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/SASLMechanismHandlerCfgDefn_fr.properties b/opends/src/admin/messages/SASLMechanismHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..7a97303
--- /dev/null
+++ b/opends/src/admin/messages/SASLMechanismHandlerCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=SASL Mechanism Handler
+user-friendly-plural-name=SASL Mechanism Handlers
+synopsis=The SASL mechanism handler configuration entry is the parent for all SASL mechanism handlers defined in the OpenDS Directory Server.
+description=SASL mechanism handlers are responsible for authenticating users during the course of processing a SASL (Simple Authentication and Security Layer, as defined in RFC 4422) bind.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/SASLMechanismHandlerCfgDefn_ja.properties b/opends/src/admin/messages/SASLMechanismHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..7a97303
--- /dev/null
+++ b/opends/src/admin/messages/SASLMechanismHandlerCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=SASL Mechanism Handler
+user-friendly-plural-name=SASL Mechanism Handlers
+synopsis=The SASL mechanism handler configuration entry is the parent for all SASL mechanism handlers defined in the OpenDS Directory Server.
+description=SASL mechanism handlers are responsible for authenticating users during the course of processing a SASL (Simple Authentication and Security Layer, as defined in RFC 4422) bind.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/SASLMechanismHandlerCfgDefn_ko.properties b/opends/src/admin/messages/SASLMechanismHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..7a97303
--- /dev/null
+++ b/opends/src/admin/messages/SASLMechanismHandlerCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=SASL Mechanism Handler
+user-friendly-plural-name=SASL Mechanism Handlers
+synopsis=The SASL mechanism handler configuration entry is the parent for all SASL mechanism handlers defined in the OpenDS Directory Server.
+description=SASL mechanism handlers are responsible for authenticating users during the course of processing a SASL (Simple Authentication and Security Layer, as defined in RFC 4422) bind.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/SASLMechanismHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/SASLMechanismHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..7a97303
--- /dev/null
+++ b/opends/src/admin/messages/SASLMechanismHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=SASL Mechanism Handler
+user-friendly-plural-name=SASL Mechanism Handlers
+synopsis=The SASL mechanism handler configuration entry is the parent for all SASL mechanism handlers defined in the OpenDS Directory Server.
+description=SASL mechanism handlers are responsible for authenticating users during the course of processing a SASL (Simple Authentication and Security Layer, as defined in RFC 4422) bind.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/SASLMechanismHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/SASLMechanismHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..7a97303
--- /dev/null
+++ b/opends/src/admin/messages/SASLMechanismHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=SASL Mechanism Handler
+user-friendly-plural-name=SASL Mechanism Handlers
+synopsis=The SASL mechanism handler configuration entry is the parent for all SASL mechanism handlers defined in the OpenDS Directory Server.
+description=SASL mechanism handlers are responsible for authenticating users during the course of processing a SASL (Simple Authentication and Security Layer, as defined in RFC 4422) bind.
+property.enabled.synopsis=Indicates whether the SASL mechanism handler is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SASL mechanism handler implementation.
diff --git a/opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn.properties b/opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn.properties
new file mode 100644
index 0000000..6a70a88
--- /dev/null
+++ b/opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=SHA1 Password Storage Scheme
+user-friendly-plural-name=SHA1 Password Storage Schemes
+synopsis=The SHA1 Password Storage Scheme provides a mechanism for encoding user passwords using an unsalted form of the SHA-1 message digest algorithm. Because the implementation does not use any kind of salting mechanism, a given password always has the same encoded form.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "SHA".
+property.enabled.synopsis=Indicates whether the SHA1 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SHA1 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_de.properties b/opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_de.properties
new file mode 100644
index 0000000..6a70a88
--- /dev/null
+++ b/opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=SHA1 Password Storage Scheme
+user-friendly-plural-name=SHA1 Password Storage Schemes
+synopsis=The SHA1 Password Storage Scheme provides a mechanism for encoding user passwords using an unsalted form of the SHA-1 message digest algorithm. Because the implementation does not use any kind of salting mechanism, a given password always has the same encoded form.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "SHA".
+property.enabled.synopsis=Indicates whether the SHA1 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SHA1 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_es.properties b/opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_es.properties
new file mode 100644
index 0000000..6a70a88
--- /dev/null
+++ b/opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=SHA1 Password Storage Scheme
+user-friendly-plural-name=SHA1 Password Storage Schemes
+synopsis=The SHA1 Password Storage Scheme provides a mechanism for encoding user passwords using an unsalted form of the SHA-1 message digest algorithm. Because the implementation does not use any kind of salting mechanism, a given password always has the same encoded form.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "SHA".
+property.enabled.synopsis=Indicates whether the SHA1 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SHA1 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_fr.properties b/opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_fr.properties
new file mode 100644
index 0000000..6a70a88
--- /dev/null
+++ b/opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=SHA1 Password Storage Scheme
+user-friendly-plural-name=SHA1 Password Storage Schemes
+synopsis=The SHA1 Password Storage Scheme provides a mechanism for encoding user passwords using an unsalted form of the SHA-1 message digest algorithm. Because the implementation does not use any kind of salting mechanism, a given password always has the same encoded form.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "SHA".
+property.enabled.synopsis=Indicates whether the SHA1 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SHA1 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_ja.properties b/opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_ja.properties
new file mode 100644
index 0000000..6a70a88
--- /dev/null
+++ b/opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=SHA1 Password Storage Scheme
+user-friendly-plural-name=SHA1 Password Storage Schemes
+synopsis=The SHA1 Password Storage Scheme provides a mechanism for encoding user passwords using an unsalted form of the SHA-1 message digest algorithm. Because the implementation does not use any kind of salting mechanism, a given password always has the same encoded form.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "SHA".
+property.enabled.synopsis=Indicates whether the SHA1 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SHA1 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_ko.properties b/opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_ko.properties
new file mode 100644
index 0000000..6a70a88
--- /dev/null
+++ b/opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=SHA1 Password Storage Scheme
+user-friendly-plural-name=SHA1 Password Storage Schemes
+synopsis=The SHA1 Password Storage Scheme provides a mechanism for encoding user passwords using an unsalted form of the SHA-1 message digest algorithm. Because the implementation does not use any kind of salting mechanism, a given password always has the same encoded form.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "SHA".
+property.enabled.synopsis=Indicates whether the SHA1 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SHA1 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_zh_CN.properties b/opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..6a70a88
--- /dev/null
+++ b/opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=SHA1 Password Storage Scheme
+user-friendly-plural-name=SHA1 Password Storage Schemes
+synopsis=The SHA1 Password Storage Scheme provides a mechanism for encoding user passwords using an unsalted form of the SHA-1 message digest algorithm. Because the implementation does not use any kind of salting mechanism, a given password always has the same encoded form.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "SHA".
+property.enabled.synopsis=Indicates whether the SHA1 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SHA1 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_zh_TW.properties b/opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..6a70a88
--- /dev/null
+++ b/opends/src/admin/messages/SHA1PasswordStorageSchemeCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=SHA1 Password Storage Scheme
+user-friendly-plural-name=SHA1 Password Storage Schemes
+synopsis=The SHA1 Password Storage Scheme provides a mechanism for encoding user passwords using an unsalted form of the SHA-1 message digest algorithm. Because the implementation does not use any kind of salting mechanism, a given password always has the same encoded form.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "SHA".
+property.enabled.synopsis=Indicates whether the SHA1 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SHA1 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn.properties b/opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn.properties
new file mode 100644
index 0000000..ada86f7
--- /dev/null
+++ b/opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn.properties
@@ -0,0 +1,18 @@
+user-friendly-name=SMTP Account Status Notification Handler
+user-friendly-plural-name=SMTP Account Status Notification Handlers
+synopsis=The SMTP Account Status Notification Handler is a notification handler that sends email messages to end users and/or administrators whenever an account status notification is generated.
+property.email-address-attribute-type.synopsis=Specifies which attribute in the user's entries may be used to obtain the email address when notifying the end user.
+property.email-address-attribute-type.description=You can specify more than one email address as separate values. In this case, the OpenDS server sends a notification to all email addresses identified.
+property.email-address-attribute-type.default-behavior.alias.synopsis=If no email address attribute types are specified, then no attempt is made to send email notification messages to end users. Only those users specified in the set of additional recipient addresses are sent the notification messages.
+property.enabled.synopsis=Indicates whether the SMTP Account Status Notification Handler is enabled. Only enabled handlers are invoked whenever a related event occurs in the server.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SMTP Account Status Notification Handler implementation.
+property.message-subject.synopsis=Specifies the subject that should be used for email messages generated by this account status notification handler.
+property.message-subject.description=The values for this property should begin with the name of an account status notification type followed by a colon and the subject that should be used for the associated notification message. If an email message is generated for an account status notification type for which no subject is defined, then that message is given a generic subject.
+property.message-template-file.synopsis=Specifies the path to the file containing the message template to generate the email notification messages.
+property.message-template-file.description=The values for this property should begin with the name of an account status notification type followed by a colon and the path to the template file that should be used for that notification type. If an account status notification has a notification type that is not associated with a message template file, then no email message is generated for that notification.
+property.recipient-address.synopsis=Specifies an email address to which notification messages are sent, either instead of or in addition to the end user for whom the notification has been generated.
+property.recipient-address.description=This may be used to ensure that server administrators also receive a copy of any notification messages that are generated.
+property.recipient-address.default-behavior.alias.synopsis=If no additional recipient addresses are specified, then only the end users that are the subjects of the account status notifications receive the notification messages.
+property.sender-address.synopsis=Specifies the email address from which the message is sent. Note that this does not necessarily have to be a legitimate email address.
+property.send-message-without-end-user-address.synopsis=Indicates whether an email notification message should be generated and sent to the set of notification recipients even if the user entry does not contain any values for any of the email address attributes (that is, in cases when it is not be possible to notify the end user).
+property.send-message-without-end-user-address.description=This is only applicable if both one or more email address attribute types and one or more additional recipient addresses are specified.
diff --git a/opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_de.properties b/opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..ada86f7
--- /dev/null
+++ b/opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_de.properties
@@ -0,0 +1,18 @@
+user-friendly-name=SMTP Account Status Notification Handler
+user-friendly-plural-name=SMTP Account Status Notification Handlers
+synopsis=The SMTP Account Status Notification Handler is a notification handler that sends email messages to end users and/or administrators whenever an account status notification is generated.
+property.email-address-attribute-type.synopsis=Specifies which attribute in the user's entries may be used to obtain the email address when notifying the end user.
+property.email-address-attribute-type.description=You can specify more than one email address as separate values. In this case, the OpenDS server sends a notification to all email addresses identified.
+property.email-address-attribute-type.default-behavior.alias.synopsis=If no email address attribute types are specified, then no attempt is made to send email notification messages to end users. Only those users specified in the set of additional recipient addresses are sent the notification messages.
+property.enabled.synopsis=Indicates whether the SMTP Account Status Notification Handler is enabled. Only enabled handlers are invoked whenever a related event occurs in the server.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SMTP Account Status Notification Handler implementation.
+property.message-subject.synopsis=Specifies the subject that should be used for email messages generated by this account status notification handler.
+property.message-subject.description=The values for this property should begin with the name of an account status notification type followed by a colon and the subject that should be used for the associated notification message. If an email message is generated for an account status notification type for which no subject is defined, then that message is given a generic subject.
+property.message-template-file.synopsis=Specifies the path to the file containing the message template to generate the email notification messages.
+property.message-template-file.description=The values for this property should begin with the name of an account status notification type followed by a colon and the path to the template file that should be used for that notification type. If an account status notification has a notification type that is not associated with a message template file, then no email message is generated for that notification.
+property.recipient-address.synopsis=Specifies an email address to which notification messages are sent, either instead of or in addition to the end user for whom the notification has been generated.
+property.recipient-address.description=This may be used to ensure that server administrators also receive a copy of any notification messages that are generated.
+property.recipient-address.default-behavior.alias.synopsis=If no additional recipient addresses are specified, then only the end users that are the subjects of the account status notifications receive the notification messages.
+property.sender-address.synopsis=Specifies the email address from which the message is sent. Note that this does not necessarily have to be a legitimate email address.
+property.send-message-without-end-user-address.synopsis=Indicates whether an email notification message should be generated and sent to the set of notification recipients even if the user entry does not contain any values for any of the email address attributes (that is, in cases when it is not be possible to notify the end user).
+property.send-message-without-end-user-address.description=This is only applicable if both one or more email address attribute types and one or more additional recipient addresses are specified.
diff --git a/opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_es.properties b/opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..ada86f7
--- /dev/null
+++ b/opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_es.properties
@@ -0,0 +1,18 @@
+user-friendly-name=SMTP Account Status Notification Handler
+user-friendly-plural-name=SMTP Account Status Notification Handlers
+synopsis=The SMTP Account Status Notification Handler is a notification handler that sends email messages to end users and/or administrators whenever an account status notification is generated.
+property.email-address-attribute-type.synopsis=Specifies which attribute in the user's entries may be used to obtain the email address when notifying the end user.
+property.email-address-attribute-type.description=You can specify more than one email address as separate values. In this case, the OpenDS server sends a notification to all email addresses identified.
+property.email-address-attribute-type.default-behavior.alias.synopsis=If no email address attribute types are specified, then no attempt is made to send email notification messages to end users. Only those users specified in the set of additional recipient addresses are sent the notification messages.
+property.enabled.synopsis=Indicates whether the SMTP Account Status Notification Handler is enabled. Only enabled handlers are invoked whenever a related event occurs in the server.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SMTP Account Status Notification Handler implementation.
+property.message-subject.synopsis=Specifies the subject that should be used for email messages generated by this account status notification handler.
+property.message-subject.description=The values for this property should begin with the name of an account status notification type followed by a colon and the subject that should be used for the associated notification message. If an email message is generated for an account status notification type for which no subject is defined, then that message is given a generic subject.
+property.message-template-file.synopsis=Specifies the path to the file containing the message template to generate the email notification messages.
+property.message-template-file.description=The values for this property should begin with the name of an account status notification type followed by a colon and the path to the template file that should be used for that notification type. If an account status notification has a notification type that is not associated with a message template file, then no email message is generated for that notification.
+property.recipient-address.synopsis=Specifies an email address to which notification messages are sent, either instead of or in addition to the end user for whom the notification has been generated.
+property.recipient-address.description=This may be used to ensure that server administrators also receive a copy of any notification messages that are generated.
+property.recipient-address.default-behavior.alias.synopsis=If no additional recipient addresses are specified, then only the end users that are the subjects of the account status notifications receive the notification messages.
+property.sender-address.synopsis=Specifies the email address from which the message is sent. Note that this does not necessarily have to be a legitimate email address.
+property.send-message-without-end-user-address.synopsis=Indicates whether an email notification message should be generated and sent to the set of notification recipients even if the user entry does not contain any values for any of the email address attributes (that is, in cases when it is not be possible to notify the end user).
+property.send-message-without-end-user-address.description=This is only applicable if both one or more email address attribute types and one or more additional recipient addresses are specified.
diff --git a/opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_fr.properties b/opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..ada86f7
--- /dev/null
+++ b/opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_fr.properties
@@ -0,0 +1,18 @@
+user-friendly-name=SMTP Account Status Notification Handler
+user-friendly-plural-name=SMTP Account Status Notification Handlers
+synopsis=The SMTP Account Status Notification Handler is a notification handler that sends email messages to end users and/or administrators whenever an account status notification is generated.
+property.email-address-attribute-type.synopsis=Specifies which attribute in the user's entries may be used to obtain the email address when notifying the end user.
+property.email-address-attribute-type.description=You can specify more than one email address as separate values. In this case, the OpenDS server sends a notification to all email addresses identified.
+property.email-address-attribute-type.default-behavior.alias.synopsis=If no email address attribute types are specified, then no attempt is made to send email notification messages to end users. Only those users specified in the set of additional recipient addresses are sent the notification messages.
+property.enabled.synopsis=Indicates whether the SMTP Account Status Notification Handler is enabled. Only enabled handlers are invoked whenever a related event occurs in the server.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SMTP Account Status Notification Handler implementation.
+property.message-subject.synopsis=Specifies the subject that should be used for email messages generated by this account status notification handler.
+property.message-subject.description=The values for this property should begin with the name of an account status notification type followed by a colon and the subject that should be used for the associated notification message. If an email message is generated for an account status notification type for which no subject is defined, then that message is given a generic subject.
+property.message-template-file.synopsis=Specifies the path to the file containing the message template to generate the email notification messages.
+property.message-template-file.description=The values for this property should begin with the name of an account status notification type followed by a colon and the path to the template file that should be used for that notification type. If an account status notification has a notification type that is not associated with a message template file, then no email message is generated for that notification.
+property.recipient-address.synopsis=Specifies an email address to which notification messages are sent, either instead of or in addition to the end user for whom the notification has been generated.
+property.recipient-address.description=This may be used to ensure that server administrators also receive a copy of any notification messages that are generated.
+property.recipient-address.default-behavior.alias.synopsis=If no additional recipient addresses are specified, then only the end users that are the subjects of the account status notifications receive the notification messages.
+property.sender-address.synopsis=Specifies the email address from which the message is sent. Note that this does not necessarily have to be a legitimate email address.
+property.send-message-without-end-user-address.synopsis=Indicates whether an email notification message should be generated and sent to the set of notification recipients even if the user entry does not contain any values for any of the email address attributes (that is, in cases when it is not be possible to notify the end user).
+property.send-message-without-end-user-address.description=This is only applicable if both one or more email address attribute types and one or more additional recipient addresses are specified.
diff --git a/opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_ja.properties b/opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..ada86f7
--- /dev/null
+++ b/opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_ja.properties
@@ -0,0 +1,18 @@
+user-friendly-name=SMTP Account Status Notification Handler
+user-friendly-plural-name=SMTP Account Status Notification Handlers
+synopsis=The SMTP Account Status Notification Handler is a notification handler that sends email messages to end users and/or administrators whenever an account status notification is generated.
+property.email-address-attribute-type.synopsis=Specifies which attribute in the user's entries may be used to obtain the email address when notifying the end user.
+property.email-address-attribute-type.description=You can specify more than one email address as separate values. In this case, the OpenDS server sends a notification to all email addresses identified.
+property.email-address-attribute-type.default-behavior.alias.synopsis=If no email address attribute types are specified, then no attempt is made to send email notification messages to end users. Only those users specified in the set of additional recipient addresses are sent the notification messages.
+property.enabled.synopsis=Indicates whether the SMTP Account Status Notification Handler is enabled. Only enabled handlers are invoked whenever a related event occurs in the server.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SMTP Account Status Notification Handler implementation.
+property.message-subject.synopsis=Specifies the subject that should be used for email messages generated by this account status notification handler.
+property.message-subject.description=The values for this property should begin with the name of an account status notification type followed by a colon and the subject that should be used for the associated notification message. If an email message is generated for an account status notification type for which no subject is defined, then that message is given a generic subject.
+property.message-template-file.synopsis=Specifies the path to the file containing the message template to generate the email notification messages.
+property.message-template-file.description=The values for this property should begin with the name of an account status notification type followed by a colon and the path to the template file that should be used for that notification type. If an account status notification has a notification type that is not associated with a message template file, then no email message is generated for that notification.
+property.recipient-address.synopsis=Specifies an email address to which notification messages are sent, either instead of or in addition to the end user for whom the notification has been generated.
+property.recipient-address.description=This may be used to ensure that server administrators also receive a copy of any notification messages that are generated.
+property.recipient-address.default-behavior.alias.synopsis=If no additional recipient addresses are specified, then only the end users that are the subjects of the account status notifications receive the notification messages.
+property.sender-address.synopsis=Specifies the email address from which the message is sent. Note that this does not necessarily have to be a legitimate email address.
+property.send-message-without-end-user-address.synopsis=Indicates whether an email notification message should be generated and sent to the set of notification recipients even if the user entry does not contain any values for any of the email address attributes (that is, in cases when it is not be possible to notify the end user).
+property.send-message-without-end-user-address.description=This is only applicable if both one or more email address attribute types and one or more additional recipient addresses are specified.
diff --git a/opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_ko.properties b/opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..ada86f7
--- /dev/null
+++ b/opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_ko.properties
@@ -0,0 +1,18 @@
+user-friendly-name=SMTP Account Status Notification Handler
+user-friendly-plural-name=SMTP Account Status Notification Handlers
+synopsis=The SMTP Account Status Notification Handler is a notification handler that sends email messages to end users and/or administrators whenever an account status notification is generated.
+property.email-address-attribute-type.synopsis=Specifies which attribute in the user's entries may be used to obtain the email address when notifying the end user.
+property.email-address-attribute-type.description=You can specify more than one email address as separate values. In this case, the OpenDS server sends a notification to all email addresses identified.
+property.email-address-attribute-type.default-behavior.alias.synopsis=If no email address attribute types are specified, then no attempt is made to send email notification messages to end users. Only those users specified in the set of additional recipient addresses are sent the notification messages.
+property.enabled.synopsis=Indicates whether the SMTP Account Status Notification Handler is enabled. Only enabled handlers are invoked whenever a related event occurs in the server.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SMTP Account Status Notification Handler implementation.
+property.message-subject.synopsis=Specifies the subject that should be used for email messages generated by this account status notification handler.
+property.message-subject.description=The values for this property should begin with the name of an account status notification type followed by a colon and the subject that should be used for the associated notification message. If an email message is generated for an account status notification type for which no subject is defined, then that message is given a generic subject.
+property.message-template-file.synopsis=Specifies the path to the file containing the message template to generate the email notification messages.
+property.message-template-file.description=The values for this property should begin with the name of an account status notification type followed by a colon and the path to the template file that should be used for that notification type. If an account status notification has a notification type that is not associated with a message template file, then no email message is generated for that notification.
+property.recipient-address.synopsis=Specifies an email address to which notification messages are sent, either instead of or in addition to the end user for whom the notification has been generated.
+property.recipient-address.description=This may be used to ensure that server administrators also receive a copy of any notification messages that are generated.
+property.recipient-address.default-behavior.alias.synopsis=If no additional recipient addresses are specified, then only the end users that are the subjects of the account status notifications receive the notification messages.
+property.sender-address.synopsis=Specifies the email address from which the message is sent. Note that this does not necessarily have to be a legitimate email address.
+property.send-message-without-end-user-address.synopsis=Indicates whether an email notification message should be generated and sent to the set of notification recipients even if the user entry does not contain any values for any of the email address attributes (that is, in cases when it is not be possible to notify the end user).
+property.send-message-without-end-user-address.description=This is only applicable if both one or more email address attribute types and one or more additional recipient addresses are specified.
diff --git a/opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..ada86f7
--- /dev/null
+++ b/opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,18 @@
+user-friendly-name=SMTP Account Status Notification Handler
+user-friendly-plural-name=SMTP Account Status Notification Handlers
+synopsis=The SMTP Account Status Notification Handler is a notification handler that sends email messages to end users and/or administrators whenever an account status notification is generated.
+property.email-address-attribute-type.synopsis=Specifies which attribute in the user's entries may be used to obtain the email address when notifying the end user.
+property.email-address-attribute-type.description=You can specify more than one email address as separate values. In this case, the OpenDS server sends a notification to all email addresses identified.
+property.email-address-attribute-type.default-behavior.alias.synopsis=If no email address attribute types are specified, then no attempt is made to send email notification messages to end users. Only those users specified in the set of additional recipient addresses are sent the notification messages.
+property.enabled.synopsis=Indicates whether the SMTP Account Status Notification Handler is enabled. Only enabled handlers are invoked whenever a related event occurs in the server.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SMTP Account Status Notification Handler implementation.
+property.message-subject.synopsis=Specifies the subject that should be used for email messages generated by this account status notification handler.
+property.message-subject.description=The values for this property should begin with the name of an account status notification type followed by a colon and the subject that should be used for the associated notification message. If an email message is generated for an account status notification type for which no subject is defined, then that message is given a generic subject.
+property.message-template-file.synopsis=Specifies the path to the file containing the message template to generate the email notification messages.
+property.message-template-file.description=The values for this property should begin with the name of an account status notification type followed by a colon and the path to the template file that should be used for that notification type. If an account status notification has a notification type that is not associated with a message template file, then no email message is generated for that notification.
+property.recipient-address.synopsis=Specifies an email address to which notification messages are sent, either instead of or in addition to the end user for whom the notification has been generated.
+property.recipient-address.description=This may be used to ensure that server administrators also receive a copy of any notification messages that are generated.
+property.recipient-address.default-behavior.alias.synopsis=If no additional recipient addresses are specified, then only the end users that are the subjects of the account status notifications receive the notification messages.
+property.sender-address.synopsis=Specifies the email address from which the message is sent. Note that this does not necessarily have to be a legitimate email address.
+property.send-message-without-end-user-address.synopsis=Indicates whether an email notification message should be generated and sent to the set of notification recipients even if the user entry does not contain any values for any of the email address attributes (that is, in cases when it is not be possible to notify the end user).
+property.send-message-without-end-user-address.description=This is only applicable if both one or more email address attribute types and one or more additional recipient addresses are specified.
diff --git a/opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..ada86f7
--- /dev/null
+++ b/opends/src/admin/messages/SMTPAccountStatusNotificationHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,18 @@
+user-friendly-name=SMTP Account Status Notification Handler
+user-friendly-plural-name=SMTP Account Status Notification Handlers
+synopsis=The SMTP Account Status Notification Handler is a notification handler that sends email messages to end users and/or administrators whenever an account status notification is generated.
+property.email-address-attribute-type.synopsis=Specifies which attribute in the user's entries may be used to obtain the email address when notifying the end user.
+property.email-address-attribute-type.description=You can specify more than one email address as separate values. In this case, the OpenDS server sends a notification to all email addresses identified.
+property.email-address-attribute-type.default-behavior.alias.synopsis=If no email address attribute types are specified, then no attempt is made to send email notification messages to end users. Only those users specified in the set of additional recipient addresses are sent the notification messages.
+property.enabled.synopsis=Indicates whether the SMTP Account Status Notification Handler is enabled. Only enabled handlers are invoked whenever a related event occurs in the server.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SMTP Account Status Notification Handler implementation.
+property.message-subject.synopsis=Specifies the subject that should be used for email messages generated by this account status notification handler.
+property.message-subject.description=The values for this property should begin with the name of an account status notification type followed by a colon and the subject that should be used for the associated notification message. If an email message is generated for an account status notification type for which no subject is defined, then that message is given a generic subject.
+property.message-template-file.synopsis=Specifies the path to the file containing the message template to generate the email notification messages.
+property.message-template-file.description=The values for this property should begin with the name of an account status notification type followed by a colon and the path to the template file that should be used for that notification type. If an account status notification has a notification type that is not associated with a message template file, then no email message is generated for that notification.
+property.recipient-address.synopsis=Specifies an email address to which notification messages are sent, either instead of or in addition to the end user for whom the notification has been generated.
+property.recipient-address.description=This may be used to ensure that server administrators also receive a copy of any notification messages that are generated.
+property.recipient-address.default-behavior.alias.synopsis=If no additional recipient addresses are specified, then only the end users that are the subjects of the account status notifications receive the notification messages.
+property.sender-address.synopsis=Specifies the email address from which the message is sent. Note that this does not necessarily have to be a legitimate email address.
+property.send-message-without-end-user-address.synopsis=Indicates whether an email notification message should be generated and sent to the set of notification recipients even if the user entry does not contain any values for any of the email address attributes (that is, in cases when it is not be possible to notify the end user).
+property.send-message-without-end-user-address.description=This is only applicable if both one or more email address attribute types and one or more additional recipient addresses are specified.
diff --git a/opends/src/admin/messages/SMTPAlertHandlerCfgDefn.properties b/opends/src/admin/messages/SMTPAlertHandlerCfgDefn.properties
new file mode 100644
index 0000000..0aae836
--- /dev/null
+++ b/opends/src/admin/messages/SMTPAlertHandlerCfgDefn.properties
@@ -0,0 +1,18 @@
+user-friendly-name=SMTP Alert Handler
+user-friendly-plural-name=SMTP Alert Handlers
+synopsis=The SMTP Alert Handler may be used to send e-mail messages to notify administrators of significant events that occur within the server.
+property.disabled-alert-type.synopsis=Specifies the names of the alert types that are disabled for this alert handler.
+property.disabled-alert-type.description=If there are any values for this attribute, then no alerts with any of the specified types are allowed. If there are no values for this attribute, then only alerts with a type included in the set of enabled alert types are allowed, or if there are no values for the enabled alert types option, then all alert types are allowed.
+property.disabled-alert-type.default-behavior.alias.synopsis=If there is a set of enabled alert types, then only alerts with one of those types are allowed. Otherwise, all alerts are allowed.
+property.enabled.synopsis=Indicates whether the SMTP Alert Handler is enabled.
+property.enabled-alert-type.synopsis=Specifies the names of the alert types that are enabled for this alert handler.
+property.enabled-alert-type.description=If there are any values for this attribute, then only alerts with one of the specified types are allowed (unless they are also included in the disabled alert types). If there are no values for this attribute, then any alert with a type not included in the list of disabled alert types is allowed.
+property.enabled-alert-type.default-behavior.alias.synopsis=All alerts with types not included in the set of disabled alert types are allowed.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SMTP Alert Handler implementation.
+property.message-body.synopsis=Specifies the body that should be used for email messages generated by this alert handler.
+property.message-body.description=The token "%%%%alert-type%%%%" is dynamically replaced with the alert type string. The token "%%%%alert-id%%%%" is dynamically replaced with the alert ID value. The token "%%%%alert-message%%%%" is dynamically replaced with the alert message. The token "\\n" is replaced with an end-of-line marker.
+property.message-subject.synopsis=Specifies the subject that should be used for email messages generated by this alert handler.
+property.message-subject.description=The token "%%%%alert-type%%%%" is dynamically replaced with the alert type string. The token "%%%%alert-id%%%%" is dynamically replaced with the alert ID value. The token "%%%%alert-message%%%%" is dynamically replaced with the alert message. The token "\\n" is replaced with an end-of-line marker.
+property.recipient-address.synopsis=Specifies an email address to which the messages should be sent.
+property.recipient-address.description=Multiple values may be provided if there should be more than one recipient.
+property.sender-address.synopsis=Specifies the email address to use as the sender for messages generated by this alert handler.
diff --git a/opends/src/admin/messages/SMTPAlertHandlerCfgDefn_de.properties b/opends/src/admin/messages/SMTPAlertHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..0aae836
--- /dev/null
+++ b/opends/src/admin/messages/SMTPAlertHandlerCfgDefn_de.properties
@@ -0,0 +1,18 @@
+user-friendly-name=SMTP Alert Handler
+user-friendly-plural-name=SMTP Alert Handlers
+synopsis=The SMTP Alert Handler may be used to send e-mail messages to notify administrators of significant events that occur within the server.
+property.disabled-alert-type.synopsis=Specifies the names of the alert types that are disabled for this alert handler.
+property.disabled-alert-type.description=If there are any values for this attribute, then no alerts with any of the specified types are allowed. If there are no values for this attribute, then only alerts with a type included in the set of enabled alert types are allowed, or if there are no values for the enabled alert types option, then all alert types are allowed.
+property.disabled-alert-type.default-behavior.alias.synopsis=If there is a set of enabled alert types, then only alerts with one of those types are allowed. Otherwise, all alerts are allowed.
+property.enabled.synopsis=Indicates whether the SMTP Alert Handler is enabled.
+property.enabled-alert-type.synopsis=Specifies the names of the alert types that are enabled for this alert handler.
+property.enabled-alert-type.description=If there are any values for this attribute, then only alerts with one of the specified types are allowed (unless they are also included in the disabled alert types). If there are no values for this attribute, then any alert with a type not included in the list of disabled alert types is allowed.
+property.enabled-alert-type.default-behavior.alias.synopsis=All alerts with types not included in the set of disabled alert types are allowed.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SMTP Alert Handler implementation.
+property.message-body.synopsis=Specifies the body that should be used for email messages generated by this alert handler.
+property.message-body.description=The token "%%%%alert-type%%%%" is dynamically replaced with the alert type string. The token "%%%%alert-id%%%%" is dynamically replaced with the alert ID value. The token "%%%%alert-message%%%%" is dynamically replaced with the alert message. The token "\\n" is replaced with an end-of-line marker.
+property.message-subject.synopsis=Specifies the subject that should be used for email messages generated by this alert handler.
+property.message-subject.description=The token "%%%%alert-type%%%%" is dynamically replaced with the alert type string. The token "%%%%alert-id%%%%" is dynamically replaced with the alert ID value. The token "%%%%alert-message%%%%" is dynamically replaced with the alert message. The token "\\n" is replaced with an end-of-line marker.
+property.recipient-address.synopsis=Specifies an email address to which the messages should be sent.
+property.recipient-address.description=Multiple values may be provided if there should be more than one recipient.
+property.sender-address.synopsis=Specifies the email address to use as the sender for messages generated by this alert handler.
diff --git a/opends/src/admin/messages/SMTPAlertHandlerCfgDefn_es.properties b/opends/src/admin/messages/SMTPAlertHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..0aae836
--- /dev/null
+++ b/opends/src/admin/messages/SMTPAlertHandlerCfgDefn_es.properties
@@ -0,0 +1,18 @@
+user-friendly-name=SMTP Alert Handler
+user-friendly-plural-name=SMTP Alert Handlers
+synopsis=The SMTP Alert Handler may be used to send e-mail messages to notify administrators of significant events that occur within the server.
+property.disabled-alert-type.synopsis=Specifies the names of the alert types that are disabled for this alert handler.
+property.disabled-alert-type.description=If there are any values for this attribute, then no alerts with any of the specified types are allowed. If there are no values for this attribute, then only alerts with a type included in the set of enabled alert types are allowed, or if there are no values for the enabled alert types option, then all alert types are allowed.
+property.disabled-alert-type.default-behavior.alias.synopsis=If there is a set of enabled alert types, then only alerts with one of those types are allowed. Otherwise, all alerts are allowed.
+property.enabled.synopsis=Indicates whether the SMTP Alert Handler is enabled.
+property.enabled-alert-type.synopsis=Specifies the names of the alert types that are enabled for this alert handler.
+property.enabled-alert-type.description=If there are any values for this attribute, then only alerts with one of the specified types are allowed (unless they are also included in the disabled alert types). If there are no values for this attribute, then any alert with a type not included in the list of disabled alert types is allowed.
+property.enabled-alert-type.default-behavior.alias.synopsis=All alerts with types not included in the set of disabled alert types are allowed.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SMTP Alert Handler implementation.
+property.message-body.synopsis=Specifies the body that should be used for email messages generated by this alert handler.
+property.message-body.description=The token "%%%%alert-type%%%%" is dynamically replaced with the alert type string. The token "%%%%alert-id%%%%" is dynamically replaced with the alert ID value. The token "%%%%alert-message%%%%" is dynamically replaced with the alert message. The token "\\n" is replaced with an end-of-line marker.
+property.message-subject.synopsis=Specifies the subject that should be used for email messages generated by this alert handler.
+property.message-subject.description=The token "%%%%alert-type%%%%" is dynamically replaced with the alert type string. The token "%%%%alert-id%%%%" is dynamically replaced with the alert ID value. The token "%%%%alert-message%%%%" is dynamically replaced with the alert message. The token "\\n" is replaced with an end-of-line marker.
+property.recipient-address.synopsis=Specifies an email address to which the messages should be sent.
+property.recipient-address.description=Multiple values may be provided if there should be more than one recipient.
+property.sender-address.synopsis=Specifies the email address to use as the sender for messages generated by this alert handler.
diff --git a/opends/src/admin/messages/SMTPAlertHandlerCfgDefn_fr.properties b/opends/src/admin/messages/SMTPAlertHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..0aae836
--- /dev/null
+++ b/opends/src/admin/messages/SMTPAlertHandlerCfgDefn_fr.properties
@@ -0,0 +1,18 @@
+user-friendly-name=SMTP Alert Handler
+user-friendly-plural-name=SMTP Alert Handlers
+synopsis=The SMTP Alert Handler may be used to send e-mail messages to notify administrators of significant events that occur within the server.
+property.disabled-alert-type.synopsis=Specifies the names of the alert types that are disabled for this alert handler.
+property.disabled-alert-type.description=If there are any values for this attribute, then no alerts with any of the specified types are allowed. If there are no values for this attribute, then only alerts with a type included in the set of enabled alert types are allowed, or if there are no values for the enabled alert types option, then all alert types are allowed.
+property.disabled-alert-type.default-behavior.alias.synopsis=If there is a set of enabled alert types, then only alerts with one of those types are allowed. Otherwise, all alerts are allowed.
+property.enabled.synopsis=Indicates whether the SMTP Alert Handler is enabled.
+property.enabled-alert-type.synopsis=Specifies the names of the alert types that are enabled for this alert handler.
+property.enabled-alert-type.description=If there are any values for this attribute, then only alerts with one of the specified types are allowed (unless they are also included in the disabled alert types). If there are no values for this attribute, then any alert with a type not included in the list of disabled alert types is allowed.
+property.enabled-alert-type.default-behavior.alias.synopsis=All alerts with types not included in the set of disabled alert types are allowed.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SMTP Alert Handler implementation.
+property.message-body.synopsis=Specifies the body that should be used for email messages generated by this alert handler.
+property.message-body.description=The token "%%%%alert-type%%%%" is dynamically replaced with the alert type string. The token "%%%%alert-id%%%%" is dynamically replaced with the alert ID value. The token "%%%%alert-message%%%%" is dynamically replaced with the alert message. The token "\\n" is replaced with an end-of-line marker.
+property.message-subject.synopsis=Specifies the subject that should be used for email messages generated by this alert handler.
+property.message-subject.description=The token "%%%%alert-type%%%%" is dynamically replaced with the alert type string. The token "%%%%alert-id%%%%" is dynamically replaced with the alert ID value. The token "%%%%alert-message%%%%" is dynamically replaced with the alert message. The token "\\n" is replaced with an end-of-line marker.
+property.recipient-address.synopsis=Specifies an email address to which the messages should be sent.
+property.recipient-address.description=Multiple values may be provided if there should be more than one recipient.
+property.sender-address.synopsis=Specifies the email address to use as the sender for messages generated by this alert handler.
diff --git a/opends/src/admin/messages/SMTPAlertHandlerCfgDefn_ja.properties b/opends/src/admin/messages/SMTPAlertHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..0aae836
--- /dev/null
+++ b/opends/src/admin/messages/SMTPAlertHandlerCfgDefn_ja.properties
@@ -0,0 +1,18 @@
+user-friendly-name=SMTP Alert Handler
+user-friendly-plural-name=SMTP Alert Handlers
+synopsis=The SMTP Alert Handler may be used to send e-mail messages to notify administrators of significant events that occur within the server.
+property.disabled-alert-type.synopsis=Specifies the names of the alert types that are disabled for this alert handler.
+property.disabled-alert-type.description=If there are any values for this attribute, then no alerts with any of the specified types are allowed. If there are no values for this attribute, then only alerts with a type included in the set of enabled alert types are allowed, or if there are no values for the enabled alert types option, then all alert types are allowed.
+property.disabled-alert-type.default-behavior.alias.synopsis=If there is a set of enabled alert types, then only alerts with one of those types are allowed. Otherwise, all alerts are allowed.
+property.enabled.synopsis=Indicates whether the SMTP Alert Handler is enabled.
+property.enabled-alert-type.synopsis=Specifies the names of the alert types that are enabled for this alert handler.
+property.enabled-alert-type.description=If there are any values for this attribute, then only alerts with one of the specified types are allowed (unless they are also included in the disabled alert types). If there are no values for this attribute, then any alert with a type not included in the list of disabled alert types is allowed.
+property.enabled-alert-type.default-behavior.alias.synopsis=All alerts with types not included in the set of disabled alert types are allowed.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SMTP Alert Handler implementation.
+property.message-body.synopsis=Specifies the body that should be used for email messages generated by this alert handler.
+property.message-body.description=The token "%%%%alert-type%%%%" is dynamically replaced with the alert type string. The token "%%%%alert-id%%%%" is dynamically replaced with the alert ID value. The token "%%%%alert-message%%%%" is dynamically replaced with the alert message. The token "\\n" is replaced with an end-of-line marker.
+property.message-subject.synopsis=Specifies the subject that should be used for email messages generated by this alert handler.
+property.message-subject.description=The token "%%%%alert-type%%%%" is dynamically replaced with the alert type string. The token "%%%%alert-id%%%%" is dynamically replaced with the alert ID value. The token "%%%%alert-message%%%%" is dynamically replaced with the alert message. The token "\\n" is replaced with an end-of-line marker.
+property.recipient-address.synopsis=Specifies an email address to which the messages should be sent.
+property.recipient-address.description=Multiple values may be provided if there should be more than one recipient.
+property.sender-address.synopsis=Specifies the email address to use as the sender for messages generated by this alert handler.
diff --git a/opends/src/admin/messages/SMTPAlertHandlerCfgDefn_ko.properties b/opends/src/admin/messages/SMTPAlertHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..0aae836
--- /dev/null
+++ b/opends/src/admin/messages/SMTPAlertHandlerCfgDefn_ko.properties
@@ -0,0 +1,18 @@
+user-friendly-name=SMTP Alert Handler
+user-friendly-plural-name=SMTP Alert Handlers
+synopsis=The SMTP Alert Handler may be used to send e-mail messages to notify administrators of significant events that occur within the server.
+property.disabled-alert-type.synopsis=Specifies the names of the alert types that are disabled for this alert handler.
+property.disabled-alert-type.description=If there are any values for this attribute, then no alerts with any of the specified types are allowed. If there are no values for this attribute, then only alerts with a type included in the set of enabled alert types are allowed, or if there are no values for the enabled alert types option, then all alert types are allowed.
+property.disabled-alert-type.default-behavior.alias.synopsis=If there is a set of enabled alert types, then only alerts with one of those types are allowed. Otherwise, all alerts are allowed.
+property.enabled.synopsis=Indicates whether the SMTP Alert Handler is enabled.
+property.enabled-alert-type.synopsis=Specifies the names of the alert types that are enabled for this alert handler.
+property.enabled-alert-type.description=If there are any values for this attribute, then only alerts with one of the specified types are allowed (unless they are also included in the disabled alert types). If there are no values for this attribute, then any alert with a type not included in the list of disabled alert types is allowed.
+property.enabled-alert-type.default-behavior.alias.synopsis=All alerts with types not included in the set of disabled alert types are allowed.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SMTP Alert Handler implementation.
+property.message-body.synopsis=Specifies the body that should be used for email messages generated by this alert handler.
+property.message-body.description=The token "%%%%alert-type%%%%" is dynamically replaced with the alert type string. The token "%%%%alert-id%%%%" is dynamically replaced with the alert ID value. The token "%%%%alert-message%%%%" is dynamically replaced with the alert message. The token "\\n" is replaced with an end-of-line marker.
+property.message-subject.synopsis=Specifies the subject that should be used for email messages generated by this alert handler.
+property.message-subject.description=The token "%%%%alert-type%%%%" is dynamically replaced with the alert type string. The token "%%%%alert-id%%%%" is dynamically replaced with the alert ID value. The token "%%%%alert-message%%%%" is dynamically replaced with the alert message. The token "\\n" is replaced with an end-of-line marker.
+property.recipient-address.synopsis=Specifies an email address to which the messages should be sent.
+property.recipient-address.description=Multiple values may be provided if there should be more than one recipient.
+property.sender-address.synopsis=Specifies the email address to use as the sender for messages generated by this alert handler.
diff --git a/opends/src/admin/messages/SMTPAlertHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/SMTPAlertHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..0aae836
--- /dev/null
+++ b/opends/src/admin/messages/SMTPAlertHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,18 @@
+user-friendly-name=SMTP Alert Handler
+user-friendly-plural-name=SMTP Alert Handlers
+synopsis=The SMTP Alert Handler may be used to send e-mail messages to notify administrators of significant events that occur within the server.
+property.disabled-alert-type.synopsis=Specifies the names of the alert types that are disabled for this alert handler.
+property.disabled-alert-type.description=If there are any values for this attribute, then no alerts with any of the specified types are allowed. If there are no values for this attribute, then only alerts with a type included in the set of enabled alert types are allowed, or if there are no values for the enabled alert types option, then all alert types are allowed.
+property.disabled-alert-type.default-behavior.alias.synopsis=If there is a set of enabled alert types, then only alerts with one of those types are allowed. Otherwise, all alerts are allowed.
+property.enabled.synopsis=Indicates whether the SMTP Alert Handler is enabled.
+property.enabled-alert-type.synopsis=Specifies the names of the alert types that are enabled for this alert handler.
+property.enabled-alert-type.description=If there are any values for this attribute, then only alerts with one of the specified types are allowed (unless they are also included in the disabled alert types). If there are no values for this attribute, then any alert with a type not included in the list of disabled alert types is allowed.
+property.enabled-alert-type.default-behavior.alias.synopsis=All alerts with types not included in the set of disabled alert types are allowed.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SMTP Alert Handler implementation.
+property.message-body.synopsis=Specifies the body that should be used for email messages generated by this alert handler.
+property.message-body.description=The token "%%%%alert-type%%%%" is dynamically replaced with the alert type string. The token "%%%%alert-id%%%%" is dynamically replaced with the alert ID value. The token "%%%%alert-message%%%%" is dynamically replaced with the alert message. The token "\\n" is replaced with an end-of-line marker.
+property.message-subject.synopsis=Specifies the subject that should be used for email messages generated by this alert handler.
+property.message-subject.description=The token "%%%%alert-type%%%%" is dynamically replaced with the alert type string. The token "%%%%alert-id%%%%" is dynamically replaced with the alert ID value. The token "%%%%alert-message%%%%" is dynamically replaced with the alert message. The token "\\n" is replaced with an end-of-line marker.
+property.recipient-address.synopsis=Specifies an email address to which the messages should be sent.
+property.recipient-address.description=Multiple values may be provided if there should be more than one recipient.
+property.sender-address.synopsis=Specifies the email address to use as the sender for messages generated by this alert handler.
diff --git a/opends/src/admin/messages/SMTPAlertHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/SMTPAlertHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..0aae836
--- /dev/null
+++ b/opends/src/admin/messages/SMTPAlertHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,18 @@
+user-friendly-name=SMTP Alert Handler
+user-friendly-plural-name=SMTP Alert Handlers
+synopsis=The SMTP Alert Handler may be used to send e-mail messages to notify administrators of significant events that occur within the server.
+property.disabled-alert-type.synopsis=Specifies the names of the alert types that are disabled for this alert handler.
+property.disabled-alert-type.description=If there are any values for this attribute, then no alerts with any of the specified types are allowed. If there are no values for this attribute, then only alerts with a type included in the set of enabled alert types are allowed, or if there are no values for the enabled alert types option, then all alert types are allowed.
+property.disabled-alert-type.default-behavior.alias.synopsis=If there is a set of enabled alert types, then only alerts with one of those types are allowed. Otherwise, all alerts are allowed.
+property.enabled.synopsis=Indicates whether the SMTP Alert Handler is enabled.
+property.enabled-alert-type.synopsis=Specifies the names of the alert types that are enabled for this alert handler.
+property.enabled-alert-type.description=If there are any values for this attribute, then only alerts with one of the specified types are allowed (unless they are also included in the disabled alert types). If there are no values for this attribute, then any alert with a type not included in the list of disabled alert types is allowed.
+property.enabled-alert-type.default-behavior.alias.synopsis=All alerts with types not included in the set of disabled alert types are allowed.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SMTP Alert Handler implementation.
+property.message-body.synopsis=Specifies the body that should be used for email messages generated by this alert handler.
+property.message-body.description=The token "%%%%alert-type%%%%" is dynamically replaced with the alert type string. The token "%%%%alert-id%%%%" is dynamically replaced with the alert ID value. The token "%%%%alert-message%%%%" is dynamically replaced with the alert message. The token "\\n" is replaced with an end-of-line marker.
+property.message-subject.synopsis=Specifies the subject that should be used for email messages generated by this alert handler.
+property.message-subject.description=The token "%%%%alert-type%%%%" is dynamically replaced with the alert type string. The token "%%%%alert-id%%%%" is dynamically replaced with the alert ID value. The token "%%%%alert-message%%%%" is dynamically replaced with the alert message. The token "\\n" is replaced with an end-of-line marker.
+property.recipient-address.synopsis=Specifies an email address to which the messages should be sent.
+property.recipient-address.description=Multiple values may be provided if there should be more than one recipient.
+property.sender-address.synopsis=Specifies the email address to use as the sender for messages generated by this alert handler.
diff --git a/opends/src/admin/messages/SNMPConnectionHandlerCfgDefn.properties b/opends/src/admin/messages/SNMPConnectionHandlerCfgDefn.properties
new file mode 100644
index 0000000..6acdb00
--- /dev/null
+++ b/opends/src/admin/messages/SNMPConnectionHandlerCfgDefn.properties
@@ -0,0 +1,31 @@
+user-friendly-name=SNMP Connection Handler
+user-friendly-plural-name=SNMP Connection Handlers
+synopsis=The SNMP Connection Handler can be used to process SNMP requests to retrieve monitoring information described by the MIB 2605. Supported protocol are SNMP V1, V2c and V3.
+description=The SNMP connection handler will process SNMP requests sent by SNMP Managers to retrieve information described the MIB 2605. To enable the SNMP Connection Handler, the ds-cfg-opendmk-jarfile parameter has to be set to the OpenDMK jar files location.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.allowed-manager.synopsis=Specifies the hosts of the managers to be granted the access rights. This property is required for SNMP v1 and v2 security configuration. An asterik (*) opens access to all managers.
+property.allowed-user.synopsis=Specifies the users to be granted the access rights. This property is required for SNMP v3 security configuration. An asterik (*) opens access to all users.
+property.community.synopsis=Specifies the v1,v2 community or the v3 context name allowed to access the MIB 2605 monitoring information or the USM MIB. The mapping between "community" and "context name" is set.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the SNMP Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SNMP Connection Handler implementation.
+property.listen-port.synopsis=Specifies the port number on which the SNMP Connection Handler will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.opendmk-jarfile.synopsis=Indicates the OpenDMK runtime jar file location
+property.registered-mbean.synopsis=Indicates whether the SNMP objects have to be registered in the Directory Server MBeanServer or not allowing to access SNMP Objects with RMI connector if enabled.
+property.security-agent-file.synopsis=Specifies the USM security configuration to receive authenticated only SNMP requests.
+property.security-level.synopsis=Specifies the type of security level : NoAuthNoPriv : No security mechanisms activated, AuthNoPriv : Authentication activated with no privacy, AuthPriv : Authentication with privacy activated. This property id required for SNMP V3 security configuration.
+property.security-level.syntax.enumeration.value.authnopriv.synopsis=Authentication activated with no privacy.
+property.security-level.syntax.enumeration.value.authpriv.synopsis=Authentication with privacy activated.
+property.security-level.syntax.enumeration.value.noauthnopriv.synopsis=No security mechanisms activated.
+property.trap-port.synopsis=Specifies the port to use to send SNMP Traps.
+property.traps-community.synopsis=Specifies the community string that must be include in the traps sent to define managers (trap-destinations). This property is used in the context of SNMP v1, v2 and v3.
+property.traps-destination.synopsis=Specifies the hosts to which V1 traps will be sent. V1 Traps are sent to every host listed.
+property.traps-destination.description=If this list is empty, V1 traps are sent to "localhost". Each host in the list must be identifed by its name or complete IP Addess.
+property.traps-destination.default-behavior.alias.synopsis=If the list is empty, V1 traps are sent to "localhost".
diff --git a/opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_de.properties b/opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..6acdb00
--- /dev/null
+++ b/opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_de.properties
@@ -0,0 +1,31 @@
+user-friendly-name=SNMP Connection Handler
+user-friendly-plural-name=SNMP Connection Handlers
+synopsis=The SNMP Connection Handler can be used to process SNMP requests to retrieve monitoring information described by the MIB 2605. Supported protocol are SNMP V1, V2c and V3.
+description=The SNMP connection handler will process SNMP requests sent by SNMP Managers to retrieve information described the MIB 2605. To enable the SNMP Connection Handler, the ds-cfg-opendmk-jarfile parameter has to be set to the OpenDMK jar files location.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.allowed-manager.synopsis=Specifies the hosts of the managers to be granted the access rights. This property is required for SNMP v1 and v2 security configuration. An asterik (*) opens access to all managers.
+property.allowed-user.synopsis=Specifies the users to be granted the access rights. This property is required for SNMP v3 security configuration. An asterik (*) opens access to all users.
+property.community.synopsis=Specifies the v1,v2 community or the v3 context name allowed to access the MIB 2605 monitoring information or the USM MIB. The mapping between "community" and "context name" is set.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the SNMP Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SNMP Connection Handler implementation.
+property.listen-port.synopsis=Specifies the port number on which the SNMP Connection Handler will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.opendmk-jarfile.synopsis=Indicates the OpenDMK runtime jar file location
+property.registered-mbean.synopsis=Indicates whether the SNMP objects have to be registered in the Directory Server MBeanServer or not allowing to access SNMP Objects with RMI connector if enabled.
+property.security-agent-file.synopsis=Specifies the USM security configuration to receive authenticated only SNMP requests.
+property.security-level.synopsis=Specifies the type of security level : NoAuthNoPriv : No security mechanisms activated, AuthNoPriv : Authentication activated with no privacy, AuthPriv : Authentication with privacy activated. This property id required for SNMP V3 security configuration.
+property.security-level.syntax.enumeration.value.authnopriv.synopsis=Authentication activated with no privacy.
+property.security-level.syntax.enumeration.value.authpriv.synopsis=Authentication with privacy activated.
+property.security-level.syntax.enumeration.value.noauthnopriv.synopsis=No security mechanisms activated.
+property.trap-port.synopsis=Specifies the port to use to send SNMP Traps.
+property.traps-community.synopsis=Specifies the community string that must be include in the traps sent to define managers (trap-destinations). This property is used in the context of SNMP v1, v2 and v3.
+property.traps-destination.synopsis=Specifies the hosts to which V1 traps will be sent. V1 Traps are sent to every host listed.
+property.traps-destination.description=If this list is empty, V1 traps are sent to "localhost". Each host in the list must be identifed by its name or complete IP Addess.
+property.traps-destination.default-behavior.alias.synopsis=If the list is empty, V1 traps are sent to "localhost".
diff --git a/opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_es.properties b/opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..6acdb00
--- /dev/null
+++ b/opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_es.properties
@@ -0,0 +1,31 @@
+user-friendly-name=SNMP Connection Handler
+user-friendly-plural-name=SNMP Connection Handlers
+synopsis=The SNMP Connection Handler can be used to process SNMP requests to retrieve monitoring information described by the MIB 2605. Supported protocol are SNMP V1, V2c and V3.
+description=The SNMP connection handler will process SNMP requests sent by SNMP Managers to retrieve information described the MIB 2605. To enable the SNMP Connection Handler, the ds-cfg-opendmk-jarfile parameter has to be set to the OpenDMK jar files location.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.allowed-manager.synopsis=Specifies the hosts of the managers to be granted the access rights. This property is required for SNMP v1 and v2 security configuration. An asterik (*) opens access to all managers.
+property.allowed-user.synopsis=Specifies the users to be granted the access rights. This property is required for SNMP v3 security configuration. An asterik (*) opens access to all users.
+property.community.synopsis=Specifies the v1,v2 community or the v3 context name allowed to access the MIB 2605 monitoring information or the USM MIB. The mapping between "community" and "context name" is set.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the SNMP Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SNMP Connection Handler implementation.
+property.listen-port.synopsis=Specifies the port number on which the SNMP Connection Handler will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.opendmk-jarfile.synopsis=Indicates the OpenDMK runtime jar file location
+property.registered-mbean.synopsis=Indicates whether the SNMP objects have to be registered in the Directory Server MBeanServer or not allowing to access SNMP Objects with RMI connector if enabled.
+property.security-agent-file.synopsis=Specifies the USM security configuration to receive authenticated only SNMP requests.
+property.security-level.synopsis=Specifies the type of security level : NoAuthNoPriv : No security mechanisms activated, AuthNoPriv : Authentication activated with no privacy, AuthPriv : Authentication with privacy activated. This property id required for SNMP V3 security configuration.
+property.security-level.syntax.enumeration.value.authnopriv.synopsis=Authentication activated with no privacy.
+property.security-level.syntax.enumeration.value.authpriv.synopsis=Authentication with privacy activated.
+property.security-level.syntax.enumeration.value.noauthnopriv.synopsis=No security mechanisms activated.
+property.trap-port.synopsis=Specifies the port to use to send SNMP Traps.
+property.traps-community.synopsis=Specifies the community string that must be include in the traps sent to define managers (trap-destinations). This property is used in the context of SNMP v1, v2 and v3.
+property.traps-destination.synopsis=Specifies the hosts to which V1 traps will be sent. V1 Traps are sent to every host listed.
+property.traps-destination.description=If this list is empty, V1 traps are sent to "localhost". Each host in the list must be identifed by its name or complete IP Addess.
+property.traps-destination.default-behavior.alias.synopsis=If the list is empty, V1 traps are sent to "localhost".
diff --git a/opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_fr.properties b/opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..6acdb00
--- /dev/null
+++ b/opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_fr.properties
@@ -0,0 +1,31 @@
+user-friendly-name=SNMP Connection Handler
+user-friendly-plural-name=SNMP Connection Handlers
+synopsis=The SNMP Connection Handler can be used to process SNMP requests to retrieve monitoring information described by the MIB 2605. Supported protocol are SNMP V1, V2c and V3.
+description=The SNMP connection handler will process SNMP requests sent by SNMP Managers to retrieve information described the MIB 2605. To enable the SNMP Connection Handler, the ds-cfg-opendmk-jarfile parameter has to be set to the OpenDMK jar files location.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.allowed-manager.synopsis=Specifies the hosts of the managers to be granted the access rights. This property is required for SNMP v1 and v2 security configuration. An asterik (*) opens access to all managers.
+property.allowed-user.synopsis=Specifies the users to be granted the access rights. This property is required for SNMP v3 security configuration. An asterik (*) opens access to all users.
+property.community.synopsis=Specifies the v1,v2 community or the v3 context name allowed to access the MIB 2605 monitoring information or the USM MIB. The mapping between "community" and "context name" is set.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the SNMP Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SNMP Connection Handler implementation.
+property.listen-port.synopsis=Specifies the port number on which the SNMP Connection Handler will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.opendmk-jarfile.synopsis=Indicates the OpenDMK runtime jar file location
+property.registered-mbean.synopsis=Indicates whether the SNMP objects have to be registered in the Directory Server MBeanServer or not allowing to access SNMP Objects with RMI connector if enabled.
+property.security-agent-file.synopsis=Specifies the USM security configuration to receive authenticated only SNMP requests.
+property.security-level.synopsis=Specifies the type of security level : NoAuthNoPriv : No security mechanisms activated, AuthNoPriv : Authentication activated with no privacy, AuthPriv : Authentication with privacy activated. This property id required for SNMP V3 security configuration.
+property.security-level.syntax.enumeration.value.authnopriv.synopsis=Authentication activated with no privacy.
+property.security-level.syntax.enumeration.value.authpriv.synopsis=Authentication with privacy activated.
+property.security-level.syntax.enumeration.value.noauthnopriv.synopsis=No security mechanisms activated.
+property.trap-port.synopsis=Specifies the port to use to send SNMP Traps.
+property.traps-community.synopsis=Specifies the community string that must be include in the traps sent to define managers (trap-destinations). This property is used in the context of SNMP v1, v2 and v3.
+property.traps-destination.synopsis=Specifies the hosts to which V1 traps will be sent. V1 Traps are sent to every host listed.
+property.traps-destination.description=If this list is empty, V1 traps are sent to "localhost". Each host in the list must be identifed by its name or complete IP Addess.
+property.traps-destination.default-behavior.alias.synopsis=If the list is empty, V1 traps are sent to "localhost".
diff --git a/opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_ja.properties b/opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..6acdb00
--- /dev/null
+++ b/opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_ja.properties
@@ -0,0 +1,31 @@
+user-friendly-name=SNMP Connection Handler
+user-friendly-plural-name=SNMP Connection Handlers
+synopsis=The SNMP Connection Handler can be used to process SNMP requests to retrieve monitoring information described by the MIB 2605. Supported protocol are SNMP V1, V2c and V3.
+description=The SNMP connection handler will process SNMP requests sent by SNMP Managers to retrieve information described the MIB 2605. To enable the SNMP Connection Handler, the ds-cfg-opendmk-jarfile parameter has to be set to the OpenDMK jar files location.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.allowed-manager.synopsis=Specifies the hosts of the managers to be granted the access rights. This property is required for SNMP v1 and v2 security configuration. An asterik (*) opens access to all managers.
+property.allowed-user.synopsis=Specifies the users to be granted the access rights. This property is required for SNMP v3 security configuration. An asterik (*) opens access to all users.
+property.community.synopsis=Specifies the v1,v2 community or the v3 context name allowed to access the MIB 2605 monitoring information or the USM MIB. The mapping between "community" and "context name" is set.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the SNMP Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SNMP Connection Handler implementation.
+property.listen-port.synopsis=Specifies the port number on which the SNMP Connection Handler will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.opendmk-jarfile.synopsis=Indicates the OpenDMK runtime jar file location
+property.registered-mbean.synopsis=Indicates whether the SNMP objects have to be registered in the Directory Server MBeanServer or not allowing to access SNMP Objects with RMI connector if enabled.
+property.security-agent-file.synopsis=Specifies the USM security configuration to receive authenticated only SNMP requests.
+property.security-level.synopsis=Specifies the type of security level : NoAuthNoPriv : No security mechanisms activated, AuthNoPriv : Authentication activated with no privacy, AuthPriv : Authentication with privacy activated. This property id required for SNMP V3 security configuration.
+property.security-level.syntax.enumeration.value.authnopriv.synopsis=Authentication activated with no privacy.
+property.security-level.syntax.enumeration.value.authpriv.synopsis=Authentication with privacy activated.
+property.security-level.syntax.enumeration.value.noauthnopriv.synopsis=No security mechanisms activated.
+property.trap-port.synopsis=Specifies the port to use to send SNMP Traps.
+property.traps-community.synopsis=Specifies the community string that must be include in the traps sent to define managers (trap-destinations). This property is used in the context of SNMP v1, v2 and v3.
+property.traps-destination.synopsis=Specifies the hosts to which V1 traps will be sent. V1 Traps are sent to every host listed.
+property.traps-destination.description=If this list is empty, V1 traps are sent to "localhost". Each host in the list must be identifed by its name or complete IP Addess.
+property.traps-destination.default-behavior.alias.synopsis=If the list is empty, V1 traps are sent to "localhost".
diff --git a/opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_ko.properties b/opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..6acdb00
--- /dev/null
+++ b/opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_ko.properties
@@ -0,0 +1,31 @@
+user-friendly-name=SNMP Connection Handler
+user-friendly-plural-name=SNMP Connection Handlers
+synopsis=The SNMP Connection Handler can be used to process SNMP requests to retrieve monitoring information described by the MIB 2605. Supported protocol are SNMP V1, V2c and V3.
+description=The SNMP connection handler will process SNMP requests sent by SNMP Managers to retrieve information described the MIB 2605. To enable the SNMP Connection Handler, the ds-cfg-opendmk-jarfile parameter has to be set to the OpenDMK jar files location.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.allowed-manager.synopsis=Specifies the hosts of the managers to be granted the access rights. This property is required for SNMP v1 and v2 security configuration. An asterik (*) opens access to all managers.
+property.allowed-user.synopsis=Specifies the users to be granted the access rights. This property is required for SNMP v3 security configuration. An asterik (*) opens access to all users.
+property.community.synopsis=Specifies the v1,v2 community or the v3 context name allowed to access the MIB 2605 monitoring information or the USM MIB. The mapping between "community" and "context name" is set.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the SNMP Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SNMP Connection Handler implementation.
+property.listen-port.synopsis=Specifies the port number on which the SNMP Connection Handler will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.opendmk-jarfile.synopsis=Indicates the OpenDMK runtime jar file location
+property.registered-mbean.synopsis=Indicates whether the SNMP objects have to be registered in the Directory Server MBeanServer or not allowing to access SNMP Objects with RMI connector if enabled.
+property.security-agent-file.synopsis=Specifies the USM security configuration to receive authenticated only SNMP requests.
+property.security-level.synopsis=Specifies the type of security level : NoAuthNoPriv : No security mechanisms activated, AuthNoPriv : Authentication activated with no privacy, AuthPriv : Authentication with privacy activated. This property id required for SNMP V3 security configuration.
+property.security-level.syntax.enumeration.value.authnopriv.synopsis=Authentication activated with no privacy.
+property.security-level.syntax.enumeration.value.authpriv.synopsis=Authentication with privacy activated.
+property.security-level.syntax.enumeration.value.noauthnopriv.synopsis=No security mechanisms activated.
+property.trap-port.synopsis=Specifies the port to use to send SNMP Traps.
+property.traps-community.synopsis=Specifies the community string that must be include in the traps sent to define managers (trap-destinations). This property is used in the context of SNMP v1, v2 and v3.
+property.traps-destination.synopsis=Specifies the hosts to which V1 traps will be sent. V1 Traps are sent to every host listed.
+property.traps-destination.description=If this list is empty, V1 traps are sent to "localhost". Each host in the list must be identifed by its name or complete IP Addess.
+property.traps-destination.default-behavior.alias.synopsis=If the list is empty, V1 traps are sent to "localhost".
diff --git a/opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..6acdb00
--- /dev/null
+++ b/opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,31 @@
+user-friendly-name=SNMP Connection Handler
+user-friendly-plural-name=SNMP Connection Handlers
+synopsis=The SNMP Connection Handler can be used to process SNMP requests to retrieve monitoring information described by the MIB 2605. Supported protocol are SNMP V1, V2c and V3.
+description=The SNMP connection handler will process SNMP requests sent by SNMP Managers to retrieve information described the MIB 2605. To enable the SNMP Connection Handler, the ds-cfg-opendmk-jarfile parameter has to be set to the OpenDMK jar files location.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.allowed-manager.synopsis=Specifies the hosts of the managers to be granted the access rights. This property is required for SNMP v1 and v2 security configuration. An asterik (*) opens access to all managers.
+property.allowed-user.synopsis=Specifies the users to be granted the access rights. This property is required for SNMP v3 security configuration. An asterik (*) opens access to all users.
+property.community.synopsis=Specifies the v1,v2 community or the v3 context name allowed to access the MIB 2605 monitoring information or the USM MIB. The mapping between "community" and "context name" is set.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the SNMP Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SNMP Connection Handler implementation.
+property.listen-port.synopsis=Specifies the port number on which the SNMP Connection Handler will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.opendmk-jarfile.synopsis=Indicates the OpenDMK runtime jar file location
+property.registered-mbean.synopsis=Indicates whether the SNMP objects have to be registered in the Directory Server MBeanServer or not allowing to access SNMP Objects with RMI connector if enabled.
+property.security-agent-file.synopsis=Specifies the USM security configuration to receive authenticated only SNMP requests.
+property.security-level.synopsis=Specifies the type of security level : NoAuthNoPriv : No security mechanisms activated, AuthNoPriv : Authentication activated with no privacy, AuthPriv : Authentication with privacy activated. This property id required for SNMP V3 security configuration.
+property.security-level.syntax.enumeration.value.authnopriv.synopsis=Authentication activated with no privacy.
+property.security-level.syntax.enumeration.value.authpriv.synopsis=Authentication with privacy activated.
+property.security-level.syntax.enumeration.value.noauthnopriv.synopsis=No security mechanisms activated.
+property.trap-port.synopsis=Specifies the port to use to send SNMP Traps.
+property.traps-community.synopsis=Specifies the community string that must be include in the traps sent to define managers (trap-destinations). This property is used in the context of SNMP v1, v2 and v3.
+property.traps-destination.synopsis=Specifies the hosts to which V1 traps will be sent. V1 Traps are sent to every host listed.
+property.traps-destination.description=If this list is empty, V1 traps are sent to "localhost". Each host in the list must be identifed by its name or complete IP Addess.
+property.traps-destination.default-behavior.alias.synopsis=If the list is empty, V1 traps are sent to "localhost".
diff --git a/opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..6acdb00
--- /dev/null
+++ b/opends/src/admin/messages/SNMPConnectionHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,31 @@
+user-friendly-name=SNMP Connection Handler
+user-friendly-plural-name=SNMP Connection Handlers
+synopsis=The SNMP Connection Handler can be used to process SNMP requests to retrieve monitoring information described by the MIB 2605. Supported protocol are SNMP V1, V2c and V3.
+description=The SNMP connection handler will process SNMP requests sent by SNMP Managers to retrieve information described the MIB 2605. To enable the SNMP Connection Handler, the ds-cfg-opendmk-jarfile parameter has to be set to the OpenDMK jar files location.
+property.allowed-client.synopsis=Specifies a set of host names or address masks that determine the clients that are allowed to establish connections to this connection handler.
+property.allowed-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask.
+property.allowed-client.default-behavior.alias.synopsis=All clients with addresses that do not match an address on the deny list are allowed. If there is no deny list, then all clients are allowed.
+property.allowed-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.allowed-manager.synopsis=Specifies the hosts of the managers to be granted the access rights. This property is required for SNMP v1 and v2 security configuration. An asterik (*) opens access to all managers.
+property.allowed-user.synopsis=Specifies the users to be granted the access rights. This property is required for SNMP v3 security configuration. An asterik (*) opens access to all users.
+property.community.synopsis=Specifies the v1,v2 community or the v3 context name allowed to access the MIB 2605 monitoring information or the USM MIB. The mapping between "community" and "context name" is set.
+property.denied-client.synopsis=Specifies a set of host names or address masks that determine the clients that are not allowed to establish connections to this connection handler.
+property.denied-client.description=Valid values include a host name, a fully qualified domain name, a domain name, an IP address, or a subnetwork with subnetwork mask. If both allowed and denied client masks are defined and a client connection matches one or more masks in both lists, then the connection is denied. If only a denied list is specified, then any client not matching a mask in that list is allowed.
+property.denied-client.default-behavior.alias.synopsis=If an allow list is specified, then only clients with addresses on the allow list are allowed. Otherwise, all clients are allowed.
+property.denied-client.requires-admin-action.synopsis=Changes to this configuration attribute take effect immediately and do not interfere with connections that may have already been established.
+property.enabled.synopsis=Indicates whether the SNMP Connection Handler is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the SNMP Connection Handler implementation.
+property.listen-port.synopsis=Specifies the port number on which the SNMP Connection Handler will listen for connections from clients.
+property.listen-port.description=Only a single port number may be provided.
+property.opendmk-jarfile.synopsis=Indicates the OpenDMK runtime jar file location
+property.registered-mbean.synopsis=Indicates whether the SNMP objects have to be registered in the Directory Server MBeanServer or not allowing to access SNMP Objects with RMI connector if enabled.
+property.security-agent-file.synopsis=Specifies the USM security configuration to receive authenticated only SNMP requests.
+property.security-level.synopsis=Specifies the type of security level : NoAuthNoPriv : No security mechanisms activated, AuthNoPriv : Authentication activated with no privacy, AuthPriv : Authentication with privacy activated. This property id required for SNMP V3 security configuration.
+property.security-level.syntax.enumeration.value.authnopriv.synopsis=Authentication activated with no privacy.
+property.security-level.syntax.enumeration.value.authpriv.synopsis=Authentication with privacy activated.
+property.security-level.syntax.enumeration.value.noauthnopriv.synopsis=No security mechanisms activated.
+property.trap-port.synopsis=Specifies the port to use to send SNMP Traps.
+property.traps-community.synopsis=Specifies the community string that must be include in the traps sent to define managers (trap-destinations). This property is used in the context of SNMP v1, v2 and v3.
+property.traps-destination.synopsis=Specifies the hosts to which V1 traps will be sent. V1 Traps are sent to every host listed.
+property.traps-destination.description=If this list is empty, V1 traps are sent to "localhost". Each host in the list must be identifed by its name or complete IP Addess.
+property.traps-destination.default-behavior.alias.synopsis=If the list is empty, V1 traps are sent to "localhost".
diff --git a/opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn.properties b/opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn.properties
new file mode 100644
index 0000000..59564ef
--- /dev/null
+++ b/opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted MD5 Password Storage Scheme
+user-friendly-plural-name=Salted MD5 Password Storage Schemes
+synopsis=The Salted MD5 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the MD5 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SMD5", and an implementation of the auth password syntax, with a storage scheme name of "MD5". Although the MD5 digest algorithm is relatively secure, recent cryptanalysis work has identified mechanisms for generating MD5 collisions. This does not impact the security of this algorithm as it is used in OpenDS, but it is recommended that the MD5 password storage scheme only be used if client applications require it for compatibility purposes, and that a stronger digest like SSHA or SSHA256 be used for environments in which MD5 support is not required.
+property.enabled.synopsis=Indicates whether the Salted MD5 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted MD5 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_de.properties b/opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_de.properties
new file mode 100644
index 0000000..59564ef
--- /dev/null
+++ b/opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted MD5 Password Storage Scheme
+user-friendly-plural-name=Salted MD5 Password Storage Schemes
+synopsis=The Salted MD5 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the MD5 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SMD5", and an implementation of the auth password syntax, with a storage scheme name of "MD5". Although the MD5 digest algorithm is relatively secure, recent cryptanalysis work has identified mechanisms for generating MD5 collisions. This does not impact the security of this algorithm as it is used in OpenDS, but it is recommended that the MD5 password storage scheme only be used if client applications require it for compatibility purposes, and that a stronger digest like SSHA or SSHA256 be used for environments in which MD5 support is not required.
+property.enabled.synopsis=Indicates whether the Salted MD5 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted MD5 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_es.properties b/opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_es.properties
new file mode 100644
index 0000000..59564ef
--- /dev/null
+++ b/opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted MD5 Password Storage Scheme
+user-friendly-plural-name=Salted MD5 Password Storage Schemes
+synopsis=The Salted MD5 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the MD5 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SMD5", and an implementation of the auth password syntax, with a storage scheme name of "MD5". Although the MD5 digest algorithm is relatively secure, recent cryptanalysis work has identified mechanisms for generating MD5 collisions. This does not impact the security of this algorithm as it is used in OpenDS, but it is recommended that the MD5 password storage scheme only be used if client applications require it for compatibility purposes, and that a stronger digest like SSHA or SSHA256 be used for environments in which MD5 support is not required.
+property.enabled.synopsis=Indicates whether the Salted MD5 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted MD5 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_fr.properties b/opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_fr.properties
new file mode 100644
index 0000000..59564ef
--- /dev/null
+++ b/opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted MD5 Password Storage Scheme
+user-friendly-plural-name=Salted MD5 Password Storage Schemes
+synopsis=The Salted MD5 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the MD5 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SMD5", and an implementation of the auth password syntax, with a storage scheme name of "MD5". Although the MD5 digest algorithm is relatively secure, recent cryptanalysis work has identified mechanisms for generating MD5 collisions. This does not impact the security of this algorithm as it is used in OpenDS, but it is recommended that the MD5 password storage scheme only be used if client applications require it for compatibility purposes, and that a stronger digest like SSHA or SSHA256 be used for environments in which MD5 support is not required.
+property.enabled.synopsis=Indicates whether the Salted MD5 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted MD5 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_ja.properties b/opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_ja.properties
new file mode 100644
index 0000000..59564ef
--- /dev/null
+++ b/opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted MD5 Password Storage Scheme
+user-friendly-plural-name=Salted MD5 Password Storage Schemes
+synopsis=The Salted MD5 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the MD5 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SMD5", and an implementation of the auth password syntax, with a storage scheme name of "MD5". Although the MD5 digest algorithm is relatively secure, recent cryptanalysis work has identified mechanisms for generating MD5 collisions. This does not impact the security of this algorithm as it is used in OpenDS, but it is recommended that the MD5 password storage scheme only be used if client applications require it for compatibility purposes, and that a stronger digest like SSHA or SSHA256 be used for environments in which MD5 support is not required.
+property.enabled.synopsis=Indicates whether the Salted MD5 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted MD5 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_ko.properties b/opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_ko.properties
new file mode 100644
index 0000000..59564ef
--- /dev/null
+++ b/opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted MD5 Password Storage Scheme
+user-friendly-plural-name=Salted MD5 Password Storage Schemes
+synopsis=The Salted MD5 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the MD5 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SMD5", and an implementation of the auth password syntax, with a storage scheme name of "MD5". Although the MD5 digest algorithm is relatively secure, recent cryptanalysis work has identified mechanisms for generating MD5 collisions. This does not impact the security of this algorithm as it is used in OpenDS, but it is recommended that the MD5 password storage scheme only be used if client applications require it for compatibility purposes, and that a stronger digest like SSHA or SSHA256 be used for environments in which MD5 support is not required.
+property.enabled.synopsis=Indicates whether the Salted MD5 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted MD5 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_zh_CN.properties b/opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..59564ef
--- /dev/null
+++ b/opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted MD5 Password Storage Scheme
+user-friendly-plural-name=Salted MD5 Password Storage Schemes
+synopsis=The Salted MD5 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the MD5 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SMD5", and an implementation of the auth password syntax, with a storage scheme name of "MD5". Although the MD5 digest algorithm is relatively secure, recent cryptanalysis work has identified mechanisms for generating MD5 collisions. This does not impact the security of this algorithm as it is used in OpenDS, but it is recommended that the MD5 password storage scheme only be used if client applications require it for compatibility purposes, and that a stronger digest like SSHA or SSHA256 be used for environments in which MD5 support is not required.
+property.enabled.synopsis=Indicates whether the Salted MD5 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted MD5 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_zh_TW.properties b/opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..59564ef
--- /dev/null
+++ b/opends/src/admin/messages/SaltedMD5PasswordStorageSchemeCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted MD5 Password Storage Scheme
+user-friendly-plural-name=Salted MD5 Password Storage Schemes
+synopsis=The Salted MD5 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the MD5 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SMD5", and an implementation of the auth password syntax, with a storage scheme name of "MD5". Although the MD5 digest algorithm is relatively secure, recent cryptanalysis work has identified mechanisms for generating MD5 collisions. This does not impact the security of this algorithm as it is used in OpenDS, but it is recommended that the MD5 password storage scheme only be used if client applications require it for compatibility purposes, and that a stronger digest like SSHA or SSHA256 be used for environments in which MD5 support is not required.
+property.enabled.synopsis=Indicates whether the Salted MD5 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted MD5 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn.properties b/opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn.properties
new file mode 100644
index 0000000..e9a0b7a
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA1 Password Storage Scheme
+user-friendly-plural-name=Salted SHA1 Password Storage Schemes
+synopsis=The Salted SHA1 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the SHA-1 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA", and an implementation of the auth password syntax, with a storage scheme name of "SHA1".
+property.enabled.synopsis=Indicates whether the Salted SHA1 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA1 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_de.properties b/opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_de.properties
new file mode 100644
index 0000000..e9a0b7a
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA1 Password Storage Scheme
+user-friendly-plural-name=Salted SHA1 Password Storage Schemes
+synopsis=The Salted SHA1 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the SHA-1 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA", and an implementation of the auth password syntax, with a storage scheme name of "SHA1".
+property.enabled.synopsis=Indicates whether the Salted SHA1 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA1 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_es.properties b/opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_es.properties
new file mode 100644
index 0000000..e9a0b7a
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA1 Password Storage Scheme
+user-friendly-plural-name=Salted SHA1 Password Storage Schemes
+synopsis=The Salted SHA1 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the SHA-1 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA", and an implementation of the auth password syntax, with a storage scheme name of "SHA1".
+property.enabled.synopsis=Indicates whether the Salted SHA1 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA1 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_fr.properties b/opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_fr.properties
new file mode 100644
index 0000000..e9a0b7a
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA1 Password Storage Scheme
+user-friendly-plural-name=Salted SHA1 Password Storage Schemes
+synopsis=The Salted SHA1 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the SHA-1 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA", and an implementation of the auth password syntax, with a storage scheme name of "SHA1".
+property.enabled.synopsis=Indicates whether the Salted SHA1 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA1 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_ja.properties b/opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_ja.properties
new file mode 100644
index 0000000..e9a0b7a
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA1 Password Storage Scheme
+user-friendly-plural-name=Salted SHA1 Password Storage Schemes
+synopsis=The Salted SHA1 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the SHA-1 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA", and an implementation of the auth password syntax, with a storage scheme name of "SHA1".
+property.enabled.synopsis=Indicates whether the Salted SHA1 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA1 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_ko.properties b/opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_ko.properties
new file mode 100644
index 0000000..e9a0b7a
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA1 Password Storage Scheme
+user-friendly-plural-name=Salted SHA1 Password Storage Schemes
+synopsis=The Salted SHA1 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the SHA-1 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA", and an implementation of the auth password syntax, with a storage scheme name of "SHA1".
+property.enabled.synopsis=Indicates whether the Salted SHA1 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA1 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_zh_CN.properties b/opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..e9a0b7a
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA1 Password Storage Scheme
+user-friendly-plural-name=Salted SHA1 Password Storage Schemes
+synopsis=The Salted SHA1 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the SHA-1 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA", and an implementation of the auth password syntax, with a storage scheme name of "SHA1".
+property.enabled.synopsis=Indicates whether the Salted SHA1 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA1 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_zh_TW.properties b/opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..e9a0b7a
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA1PasswordStorageSchemeCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA1 Password Storage Scheme
+user-friendly-plural-name=Salted SHA1 Password Storage Schemes
+synopsis=The Salted SHA1 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the SHA-1 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA", and an implementation of the auth password syntax, with a storage scheme name of "SHA1".
+property.enabled.synopsis=Indicates whether the Salted SHA1 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA1 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn.properties b/opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn.properties
new file mode 100644
index 0000000..7497ca9
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA256 Password Storage Scheme
+user-friendly-plural-name=Salted SHA256 Password Storage Schemes
+synopsis=The Salted SHA256 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the 256-bit SHA-2 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA256", and an implementation of the auth password syntax, with a storage scheme name of "SHA256".
+property.enabled.synopsis=Indicates whether the Salted SHA256 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA256 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_de.properties b/opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_de.properties
new file mode 100644
index 0000000..7497ca9
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA256 Password Storage Scheme
+user-friendly-plural-name=Salted SHA256 Password Storage Schemes
+synopsis=The Salted SHA256 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the 256-bit SHA-2 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA256", and an implementation of the auth password syntax, with a storage scheme name of "SHA256".
+property.enabled.synopsis=Indicates whether the Salted SHA256 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA256 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_es.properties b/opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_es.properties
new file mode 100644
index 0000000..7497ca9
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA256 Password Storage Scheme
+user-friendly-plural-name=Salted SHA256 Password Storage Schemes
+synopsis=The Salted SHA256 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the 256-bit SHA-2 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA256", and an implementation of the auth password syntax, with a storage scheme name of "SHA256".
+property.enabled.synopsis=Indicates whether the Salted SHA256 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA256 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_fr.properties b/opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_fr.properties
new file mode 100644
index 0000000..7497ca9
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA256 Password Storage Scheme
+user-friendly-plural-name=Salted SHA256 Password Storage Schemes
+synopsis=The Salted SHA256 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the 256-bit SHA-2 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA256", and an implementation of the auth password syntax, with a storage scheme name of "SHA256".
+property.enabled.synopsis=Indicates whether the Salted SHA256 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA256 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_ja.properties b/opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_ja.properties
new file mode 100644
index 0000000..7497ca9
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA256 Password Storage Scheme
+user-friendly-plural-name=Salted SHA256 Password Storage Schemes
+synopsis=The Salted SHA256 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the 256-bit SHA-2 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA256", and an implementation of the auth password syntax, with a storage scheme name of "SHA256".
+property.enabled.synopsis=Indicates whether the Salted SHA256 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA256 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_ko.properties b/opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_ko.properties
new file mode 100644
index 0000000..7497ca9
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA256 Password Storage Scheme
+user-friendly-plural-name=Salted SHA256 Password Storage Schemes
+synopsis=The Salted SHA256 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the 256-bit SHA-2 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA256", and an implementation of the auth password syntax, with a storage scheme name of "SHA256".
+property.enabled.synopsis=Indicates whether the Salted SHA256 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA256 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_zh_CN.properties b/opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..7497ca9
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA256 Password Storage Scheme
+user-friendly-plural-name=Salted SHA256 Password Storage Schemes
+synopsis=The Salted SHA256 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the 256-bit SHA-2 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA256", and an implementation of the auth password syntax, with a storage scheme name of "SHA256".
+property.enabled.synopsis=Indicates whether the Salted SHA256 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA256 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_zh_TW.properties b/opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..7497ca9
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA256PasswordStorageSchemeCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA256 Password Storage Scheme
+user-friendly-plural-name=Salted SHA256 Password Storage Schemes
+synopsis=The Salted SHA256 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the 256-bit SHA-2 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA256", and an implementation of the auth password syntax, with a storage scheme name of "SHA256".
+property.enabled.synopsis=Indicates whether the Salted SHA256 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA256 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn.properties b/opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn.properties
new file mode 100644
index 0000000..87ec5e0
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA384 Password Storage Scheme
+user-friendly-plural-name=Salted SHA384 Password Storage Schemes
+synopsis=The Salted SHA384 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the 384-bit SHA-2 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA384", and an implementation of the auth password syntax, with a storage scheme name of "SHA384".
+property.enabled.synopsis=Indicates whether the Salted SHA384 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA384 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_de.properties b/opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_de.properties
new file mode 100644
index 0000000..87ec5e0
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA384 Password Storage Scheme
+user-friendly-plural-name=Salted SHA384 Password Storage Schemes
+synopsis=The Salted SHA384 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the 384-bit SHA-2 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA384", and an implementation of the auth password syntax, with a storage scheme name of "SHA384".
+property.enabled.synopsis=Indicates whether the Salted SHA384 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA384 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_es.properties b/opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_es.properties
new file mode 100644
index 0000000..87ec5e0
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA384 Password Storage Scheme
+user-friendly-plural-name=Salted SHA384 Password Storage Schemes
+synopsis=The Salted SHA384 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the 384-bit SHA-2 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA384", and an implementation of the auth password syntax, with a storage scheme name of "SHA384".
+property.enabled.synopsis=Indicates whether the Salted SHA384 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA384 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_fr.properties b/opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_fr.properties
new file mode 100644
index 0000000..87ec5e0
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA384 Password Storage Scheme
+user-friendly-plural-name=Salted SHA384 Password Storage Schemes
+synopsis=The Salted SHA384 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the 384-bit SHA-2 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA384", and an implementation of the auth password syntax, with a storage scheme name of "SHA384".
+property.enabled.synopsis=Indicates whether the Salted SHA384 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA384 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_ja.properties b/opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_ja.properties
new file mode 100644
index 0000000..87ec5e0
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA384 Password Storage Scheme
+user-friendly-plural-name=Salted SHA384 Password Storage Schemes
+synopsis=The Salted SHA384 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the 384-bit SHA-2 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA384", and an implementation of the auth password syntax, with a storage scheme name of "SHA384".
+property.enabled.synopsis=Indicates whether the Salted SHA384 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA384 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_ko.properties b/opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_ko.properties
new file mode 100644
index 0000000..87ec5e0
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA384 Password Storage Scheme
+user-friendly-plural-name=Salted SHA384 Password Storage Schemes
+synopsis=The Salted SHA384 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the 384-bit SHA-2 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA384", and an implementation of the auth password syntax, with a storage scheme name of "SHA384".
+property.enabled.synopsis=Indicates whether the Salted SHA384 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA384 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_zh_CN.properties b/opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..87ec5e0
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA384 Password Storage Scheme
+user-friendly-plural-name=Salted SHA384 Password Storage Schemes
+synopsis=The Salted SHA384 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the 384-bit SHA-2 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA384", and an implementation of the auth password syntax, with a storage scheme name of "SHA384".
+property.enabled.synopsis=Indicates whether the Salted SHA384 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA384 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_zh_TW.properties b/opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..87ec5e0
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA384PasswordStorageSchemeCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA384 Password Storage Scheme
+user-friendly-plural-name=Salted SHA384 Password Storage Schemes
+synopsis=The Salted SHA384 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the 384-bit SHA-2 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA384", and an implementation of the auth password syntax, with a storage scheme name of "SHA384".
+property.enabled.synopsis=Indicates whether the Salted SHA384 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA384 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn.properties b/opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn.properties
new file mode 100644
index 0000000..bd450cd
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA512 Password Storage Scheme
+user-friendly-plural-name=Salted SHA512 Password Storage Schemes
+synopsis=The Salted SHA512 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the 512-bit SHA-2 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA512", and an implementation of the auth password syntax, with a storage scheme name of "SHA512".
+property.enabled.synopsis=Indicates whether the Salted SHA512 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA512 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_de.properties b/opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_de.properties
new file mode 100644
index 0000000..bd450cd
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA512 Password Storage Scheme
+user-friendly-plural-name=Salted SHA512 Password Storage Schemes
+synopsis=The Salted SHA512 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the 512-bit SHA-2 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA512", and an implementation of the auth password syntax, with a storage scheme name of "SHA512".
+property.enabled.synopsis=Indicates whether the Salted SHA512 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA512 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_es.properties b/opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_es.properties
new file mode 100644
index 0000000..bd450cd
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA512 Password Storage Scheme
+user-friendly-plural-name=Salted SHA512 Password Storage Schemes
+synopsis=The Salted SHA512 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the 512-bit SHA-2 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA512", and an implementation of the auth password syntax, with a storage scheme name of "SHA512".
+property.enabled.synopsis=Indicates whether the Salted SHA512 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA512 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_fr.properties b/opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_fr.properties
new file mode 100644
index 0000000..bd450cd
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA512 Password Storage Scheme
+user-friendly-plural-name=Salted SHA512 Password Storage Schemes
+synopsis=The Salted SHA512 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the 512-bit SHA-2 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA512", and an implementation of the auth password syntax, with a storage scheme name of "SHA512".
+property.enabled.synopsis=Indicates whether the Salted SHA512 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA512 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_ja.properties b/opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_ja.properties
new file mode 100644
index 0000000..bd450cd
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA512 Password Storage Scheme
+user-friendly-plural-name=Salted SHA512 Password Storage Schemes
+synopsis=The Salted SHA512 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the 512-bit SHA-2 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA512", and an implementation of the auth password syntax, with a storage scheme name of "SHA512".
+property.enabled.synopsis=Indicates whether the Salted SHA512 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA512 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_ko.properties b/opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_ko.properties
new file mode 100644
index 0000000..bd450cd
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA512 Password Storage Scheme
+user-friendly-plural-name=Salted SHA512 Password Storage Schemes
+synopsis=The Salted SHA512 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the 512-bit SHA-2 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA512", and an implementation of the auth password syntax, with a storage scheme name of "SHA512".
+property.enabled.synopsis=Indicates whether the Salted SHA512 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA512 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_zh_CN.properties b/opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..bd450cd
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA512 Password Storage Scheme
+user-friendly-plural-name=Salted SHA512 Password Storage Schemes
+synopsis=The Salted SHA512 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the 512-bit SHA-2 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA512", and an implementation of the auth password syntax, with a storage scheme name of "SHA512".
+property.enabled.synopsis=Indicates whether the Salted SHA512 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA512 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_zh_TW.properties b/opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..bd450cd
--- /dev/null
+++ b/opends/src/admin/messages/SaltedSHA512PasswordStorageSchemeCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Salted SHA512 Password Storage Scheme
+user-friendly-plural-name=Salted SHA512 Password Storage Schemes
+synopsis=The Salted SHA512 Password Storage Scheme provides a mechanism for encoding user passwords using a salted form of the 512-bit SHA-2 message digest algorithm.
+description=This scheme contains an implementation for the user password syntax, with a storage scheme name of "SSHA512", and an implementation of the auth password syntax, with a storage scheme name of "SHA512".
+property.enabled.synopsis=Indicates whether the Salted SHA512 Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Salted SHA512 Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/SchemaBackendCfgDefn.properties b/opends/src/admin/messages/SchemaBackendCfgDefn.properties
new file mode 100644
index 0000000..d6deab9
--- /dev/null
+++ b/opends/src/admin/messages/SchemaBackendCfgDefn.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Schema Backend
+user-friendly-plural-name=Schema Backends
+synopsis=The Schema Backend provides access to the Directory Server schema information, including the attribute types, object classes, attribute syntaxes, matching rules, matching rule uses, DIT content rules, and DIT structure rules that it contains.
+description=The server allows "modify" operations in this backend to alter the server schema definitions. The configuration entry for this backend is based on the ds-cfg-schema-backend structural object class. Note that any attribute types included in this entry that are not included in this object class (or the parent ds-cfg-backend class) appears directly in the schema entry.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.schema-entry-dn.synopsis=Defines the base DNs of the subtrees in which the schema information is published in addition to the value included in the base-dn property.
+property.schema-entry-dn.description=The value provided in the base-dn property is the only one that appears in the subschemaSubentry operational attribute of the server's root DSE (which is necessary because that is a single-valued attribute) and as a virtual attribute in other entries. The schema-entry-dn attribute may be used to make the schema information available in other locations to accommodate certain client applications that have been hard-coded to expect the schema to reside in a specific location.
+property.show-all-attributes.synopsis=Indicates whether to treat all attributes in the schema entry as if they were user attributes regardless of their configuration.
+property.show-all-attributes.description=This may provide compatibility with some applications that expect schema attributes like attributeTypes and objectClasses to be included by default even if they are not requested. Note that the ldapSyntaxes attribute is always treated as operational in order to avoid problems with attempts to modify the schema over protocol.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/SchemaBackendCfgDefn_de.properties b/opends/src/admin/messages/SchemaBackendCfgDefn_de.properties
new file mode 100644
index 0000000..d6deab9
--- /dev/null
+++ b/opends/src/admin/messages/SchemaBackendCfgDefn_de.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Schema Backend
+user-friendly-plural-name=Schema Backends
+synopsis=The Schema Backend provides access to the Directory Server schema information, including the attribute types, object classes, attribute syntaxes, matching rules, matching rule uses, DIT content rules, and DIT structure rules that it contains.
+description=The server allows "modify" operations in this backend to alter the server schema definitions. The configuration entry for this backend is based on the ds-cfg-schema-backend structural object class. Note that any attribute types included in this entry that are not included in this object class (or the parent ds-cfg-backend class) appears directly in the schema entry.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.schema-entry-dn.synopsis=Defines the base DNs of the subtrees in which the schema information is published in addition to the value included in the base-dn property.
+property.schema-entry-dn.description=The value provided in the base-dn property is the only one that appears in the subschemaSubentry operational attribute of the server's root DSE (which is necessary because that is a single-valued attribute) and as a virtual attribute in other entries. The schema-entry-dn attribute may be used to make the schema information available in other locations to accommodate certain client applications that have been hard-coded to expect the schema to reside in a specific location.
+property.show-all-attributes.synopsis=Indicates whether to treat all attributes in the schema entry as if they were user attributes regardless of their configuration.
+property.show-all-attributes.description=This may provide compatibility with some applications that expect schema attributes like attributeTypes and objectClasses to be included by default even if they are not requested. Note that the ldapSyntaxes attribute is always treated as operational in order to avoid problems with attempts to modify the schema over protocol.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/SchemaBackendCfgDefn_es.properties b/opends/src/admin/messages/SchemaBackendCfgDefn_es.properties
new file mode 100644
index 0000000..d6deab9
--- /dev/null
+++ b/opends/src/admin/messages/SchemaBackendCfgDefn_es.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Schema Backend
+user-friendly-plural-name=Schema Backends
+synopsis=The Schema Backend provides access to the Directory Server schema information, including the attribute types, object classes, attribute syntaxes, matching rules, matching rule uses, DIT content rules, and DIT structure rules that it contains.
+description=The server allows "modify" operations in this backend to alter the server schema definitions. The configuration entry for this backend is based on the ds-cfg-schema-backend structural object class. Note that any attribute types included in this entry that are not included in this object class (or the parent ds-cfg-backend class) appears directly in the schema entry.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.schema-entry-dn.synopsis=Defines the base DNs of the subtrees in which the schema information is published in addition to the value included in the base-dn property.
+property.schema-entry-dn.description=The value provided in the base-dn property is the only one that appears in the subschemaSubentry operational attribute of the server's root DSE (which is necessary because that is a single-valued attribute) and as a virtual attribute in other entries. The schema-entry-dn attribute may be used to make the schema information available in other locations to accommodate certain client applications that have been hard-coded to expect the schema to reside in a specific location.
+property.show-all-attributes.synopsis=Indicates whether to treat all attributes in the schema entry as if they were user attributes regardless of their configuration.
+property.show-all-attributes.description=This may provide compatibility with some applications that expect schema attributes like attributeTypes and objectClasses to be included by default even if they are not requested. Note that the ldapSyntaxes attribute is always treated as operational in order to avoid problems with attempts to modify the schema over protocol.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/SchemaBackendCfgDefn_fr.properties b/opends/src/admin/messages/SchemaBackendCfgDefn_fr.properties
new file mode 100644
index 0000000..d6deab9
--- /dev/null
+++ b/opends/src/admin/messages/SchemaBackendCfgDefn_fr.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Schema Backend
+user-friendly-plural-name=Schema Backends
+synopsis=The Schema Backend provides access to the Directory Server schema information, including the attribute types, object classes, attribute syntaxes, matching rules, matching rule uses, DIT content rules, and DIT structure rules that it contains.
+description=The server allows "modify" operations in this backend to alter the server schema definitions. The configuration entry for this backend is based on the ds-cfg-schema-backend structural object class. Note that any attribute types included in this entry that are not included in this object class (or the parent ds-cfg-backend class) appears directly in the schema entry.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.schema-entry-dn.synopsis=Defines the base DNs of the subtrees in which the schema information is published in addition to the value included in the base-dn property.
+property.schema-entry-dn.description=The value provided in the base-dn property is the only one that appears in the subschemaSubentry operational attribute of the server's root DSE (which is necessary because that is a single-valued attribute) and as a virtual attribute in other entries. The schema-entry-dn attribute may be used to make the schema information available in other locations to accommodate certain client applications that have been hard-coded to expect the schema to reside in a specific location.
+property.show-all-attributes.synopsis=Indicates whether to treat all attributes in the schema entry as if they were user attributes regardless of their configuration.
+property.show-all-attributes.description=This may provide compatibility with some applications that expect schema attributes like attributeTypes and objectClasses to be included by default even if they are not requested. Note that the ldapSyntaxes attribute is always treated as operational in order to avoid problems with attempts to modify the schema over protocol.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/SchemaBackendCfgDefn_ja.properties b/opends/src/admin/messages/SchemaBackendCfgDefn_ja.properties
new file mode 100644
index 0000000..d6deab9
--- /dev/null
+++ b/opends/src/admin/messages/SchemaBackendCfgDefn_ja.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Schema Backend
+user-friendly-plural-name=Schema Backends
+synopsis=The Schema Backend provides access to the Directory Server schema information, including the attribute types, object classes, attribute syntaxes, matching rules, matching rule uses, DIT content rules, and DIT structure rules that it contains.
+description=The server allows "modify" operations in this backend to alter the server schema definitions. The configuration entry for this backend is based on the ds-cfg-schema-backend structural object class. Note that any attribute types included in this entry that are not included in this object class (or the parent ds-cfg-backend class) appears directly in the schema entry.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.schema-entry-dn.synopsis=Defines the base DNs of the subtrees in which the schema information is published in addition to the value included in the base-dn property.
+property.schema-entry-dn.description=The value provided in the base-dn property is the only one that appears in the subschemaSubentry operational attribute of the server's root DSE (which is necessary because that is a single-valued attribute) and as a virtual attribute in other entries. The schema-entry-dn attribute may be used to make the schema information available in other locations to accommodate certain client applications that have been hard-coded to expect the schema to reside in a specific location.
+property.show-all-attributes.synopsis=Indicates whether to treat all attributes in the schema entry as if they were user attributes regardless of their configuration.
+property.show-all-attributes.description=This may provide compatibility with some applications that expect schema attributes like attributeTypes and objectClasses to be included by default even if they are not requested. Note that the ldapSyntaxes attribute is always treated as operational in order to avoid problems with attempts to modify the schema over protocol.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/SchemaBackendCfgDefn_ko.properties b/opends/src/admin/messages/SchemaBackendCfgDefn_ko.properties
new file mode 100644
index 0000000..d6deab9
--- /dev/null
+++ b/opends/src/admin/messages/SchemaBackendCfgDefn_ko.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Schema Backend
+user-friendly-plural-name=Schema Backends
+synopsis=The Schema Backend provides access to the Directory Server schema information, including the attribute types, object classes, attribute syntaxes, matching rules, matching rule uses, DIT content rules, and DIT structure rules that it contains.
+description=The server allows "modify" operations in this backend to alter the server schema definitions. The configuration entry for this backend is based on the ds-cfg-schema-backend structural object class. Note that any attribute types included in this entry that are not included in this object class (or the parent ds-cfg-backend class) appears directly in the schema entry.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.schema-entry-dn.synopsis=Defines the base DNs of the subtrees in which the schema information is published in addition to the value included in the base-dn property.
+property.schema-entry-dn.description=The value provided in the base-dn property is the only one that appears in the subschemaSubentry operational attribute of the server's root DSE (which is necessary because that is a single-valued attribute) and as a virtual attribute in other entries. The schema-entry-dn attribute may be used to make the schema information available in other locations to accommodate certain client applications that have been hard-coded to expect the schema to reside in a specific location.
+property.show-all-attributes.synopsis=Indicates whether to treat all attributes in the schema entry as if they were user attributes regardless of their configuration.
+property.show-all-attributes.description=This may provide compatibility with some applications that expect schema attributes like attributeTypes and objectClasses to be included by default even if they are not requested. Note that the ldapSyntaxes attribute is always treated as operational in order to avoid problems with attempts to modify the schema over protocol.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/SchemaBackendCfgDefn_zh_CN.properties b/opends/src/admin/messages/SchemaBackendCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..d6deab9
--- /dev/null
+++ b/opends/src/admin/messages/SchemaBackendCfgDefn_zh_CN.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Schema Backend
+user-friendly-plural-name=Schema Backends
+synopsis=The Schema Backend provides access to the Directory Server schema information, including the attribute types, object classes, attribute syntaxes, matching rules, matching rule uses, DIT content rules, and DIT structure rules that it contains.
+description=The server allows "modify" operations in this backend to alter the server schema definitions. The configuration entry for this backend is based on the ds-cfg-schema-backend structural object class. Note that any attribute types included in this entry that are not included in this object class (or the parent ds-cfg-backend class) appears directly in the schema entry.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.schema-entry-dn.synopsis=Defines the base DNs of the subtrees in which the schema information is published in addition to the value included in the base-dn property.
+property.schema-entry-dn.description=The value provided in the base-dn property is the only one that appears in the subschemaSubentry operational attribute of the server's root DSE (which is necessary because that is a single-valued attribute) and as a virtual attribute in other entries. The schema-entry-dn attribute may be used to make the schema information available in other locations to accommodate certain client applications that have been hard-coded to expect the schema to reside in a specific location.
+property.show-all-attributes.synopsis=Indicates whether to treat all attributes in the schema entry as if they were user attributes regardless of their configuration.
+property.show-all-attributes.description=This may provide compatibility with some applications that expect schema attributes like attributeTypes and objectClasses to be included by default even if they are not requested. Note that the ldapSyntaxes attribute is always treated as operational in order to avoid problems with attempts to modify the schema over protocol.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/SchemaBackendCfgDefn_zh_TW.properties b/opends/src/admin/messages/SchemaBackendCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..d6deab9
--- /dev/null
+++ b/opends/src/admin/messages/SchemaBackendCfgDefn_zh_TW.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Schema Backend
+user-friendly-plural-name=Schema Backends
+synopsis=The Schema Backend provides access to the Directory Server schema information, including the attribute types, object classes, attribute syntaxes, matching rules, matching rule uses, DIT content rules, and DIT structure rules that it contains.
+description=The server allows "modify" operations in this backend to alter the server schema definitions. The configuration entry for this backend is based on the ds-cfg-schema-backend structural object class. Note that any attribute types included in this entry that are not included in this object class (or the parent ds-cfg-backend class) appears directly in the schema entry.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.schema-entry-dn.synopsis=Defines the base DNs of the subtrees in which the schema information is published in addition to the value included in the base-dn property.
+property.schema-entry-dn.description=The value provided in the base-dn property is the only one that appears in the subschemaSubentry operational attribute of the server's root DSE (which is necessary because that is a single-valued attribute) and as a virtual attribute in other entries. The schema-entry-dn attribute may be used to make the schema information available in other locations to accommodate certain client applications that have been hard-coded to expect the schema to reside in a specific location.
+property.show-all-attributes.synopsis=Indicates whether to treat all attributes in the schema entry as if they were user attributes regardless of their configuration.
+property.show-all-attributes.description=This may provide compatibility with some applications that expect schema attributes like attributeTypes and objectClasses to be included by default even if they are not requested. Note that the ldapSyntaxes attribute is always treated as operational in order to avoid problems with attempts to modify the schema over protocol.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/SevenBitCleanPluginCfgDefn.properties b/opends/src/admin/messages/SevenBitCleanPluginCfgDefn.properties
new file mode 100644
index 0000000..37ea266
--- /dev/null
+++ b/opends/src/admin/messages/SevenBitCleanPluginCfgDefn.properties
@@ -0,0 +1,63 @@
+user-friendly-name=Seven Bit Clean Plugin
+user-friendly-plural-name=Seven Bit Clean Plugins
+synopsis=The Seven Bit Clean Plugin ensures that values for a specified set of attributes are 7-bit clean.
+description=That is, for those attributes, the values are not allowed to contain any bytes having the high-order bit set, which is used to indicate the presence of non-ASCII characters. Some applications do not properly handle attribute values that contain non-ASCII characters, and this plug-in can help ensure that attributes used by those applications do not contain characters that can cause problems in those applications.
+property.attribute-type.synopsis=Specifies the name or OID of an attribute type for which values should be checked to ensure that they are 7-bit clean.
+property.base-dn.synopsis=Specifies the base DN below which the checking is performed.
+property.base-dn.description=Any attempt to update a value for one of the configured attributes below this base DN must be 7-bit clean for the operation to be allowed.
+property.base-dn.default-behavior.alias.synopsis=All entries below all public naming contexts will be checked.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/SevenBitCleanPluginCfgDefn_de.properties b/opends/src/admin/messages/SevenBitCleanPluginCfgDefn_de.properties
new file mode 100644
index 0000000..37ea266
--- /dev/null
+++ b/opends/src/admin/messages/SevenBitCleanPluginCfgDefn_de.properties
@@ -0,0 +1,63 @@
+user-friendly-name=Seven Bit Clean Plugin
+user-friendly-plural-name=Seven Bit Clean Plugins
+synopsis=The Seven Bit Clean Plugin ensures that values for a specified set of attributes are 7-bit clean.
+description=That is, for those attributes, the values are not allowed to contain any bytes having the high-order bit set, which is used to indicate the presence of non-ASCII characters. Some applications do not properly handle attribute values that contain non-ASCII characters, and this plug-in can help ensure that attributes used by those applications do not contain characters that can cause problems in those applications.
+property.attribute-type.synopsis=Specifies the name or OID of an attribute type for which values should be checked to ensure that they are 7-bit clean.
+property.base-dn.synopsis=Specifies the base DN below which the checking is performed.
+property.base-dn.description=Any attempt to update a value for one of the configured attributes below this base DN must be 7-bit clean for the operation to be allowed.
+property.base-dn.default-behavior.alias.synopsis=All entries below all public naming contexts will be checked.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/SevenBitCleanPluginCfgDefn_es.properties b/opends/src/admin/messages/SevenBitCleanPluginCfgDefn_es.properties
new file mode 100644
index 0000000..37ea266
--- /dev/null
+++ b/opends/src/admin/messages/SevenBitCleanPluginCfgDefn_es.properties
@@ -0,0 +1,63 @@
+user-friendly-name=Seven Bit Clean Plugin
+user-friendly-plural-name=Seven Bit Clean Plugins
+synopsis=The Seven Bit Clean Plugin ensures that values for a specified set of attributes are 7-bit clean.
+description=That is, for those attributes, the values are not allowed to contain any bytes having the high-order bit set, which is used to indicate the presence of non-ASCII characters. Some applications do not properly handle attribute values that contain non-ASCII characters, and this plug-in can help ensure that attributes used by those applications do not contain characters that can cause problems in those applications.
+property.attribute-type.synopsis=Specifies the name or OID of an attribute type for which values should be checked to ensure that they are 7-bit clean.
+property.base-dn.synopsis=Specifies the base DN below which the checking is performed.
+property.base-dn.description=Any attempt to update a value for one of the configured attributes below this base DN must be 7-bit clean for the operation to be allowed.
+property.base-dn.default-behavior.alias.synopsis=All entries below all public naming contexts will be checked.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/SevenBitCleanPluginCfgDefn_fr.properties b/opends/src/admin/messages/SevenBitCleanPluginCfgDefn_fr.properties
new file mode 100644
index 0000000..37ea266
--- /dev/null
+++ b/opends/src/admin/messages/SevenBitCleanPluginCfgDefn_fr.properties
@@ -0,0 +1,63 @@
+user-friendly-name=Seven Bit Clean Plugin
+user-friendly-plural-name=Seven Bit Clean Plugins
+synopsis=The Seven Bit Clean Plugin ensures that values for a specified set of attributes are 7-bit clean.
+description=That is, for those attributes, the values are not allowed to contain any bytes having the high-order bit set, which is used to indicate the presence of non-ASCII characters. Some applications do not properly handle attribute values that contain non-ASCII characters, and this plug-in can help ensure that attributes used by those applications do not contain characters that can cause problems in those applications.
+property.attribute-type.synopsis=Specifies the name or OID of an attribute type for which values should be checked to ensure that they are 7-bit clean.
+property.base-dn.synopsis=Specifies the base DN below which the checking is performed.
+property.base-dn.description=Any attempt to update a value for one of the configured attributes below this base DN must be 7-bit clean for the operation to be allowed.
+property.base-dn.default-behavior.alias.synopsis=All entries below all public naming contexts will be checked.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/SevenBitCleanPluginCfgDefn_ja.properties b/opends/src/admin/messages/SevenBitCleanPluginCfgDefn_ja.properties
new file mode 100644
index 0000000..37ea266
--- /dev/null
+++ b/opends/src/admin/messages/SevenBitCleanPluginCfgDefn_ja.properties
@@ -0,0 +1,63 @@
+user-friendly-name=Seven Bit Clean Plugin
+user-friendly-plural-name=Seven Bit Clean Plugins
+synopsis=The Seven Bit Clean Plugin ensures that values for a specified set of attributes are 7-bit clean.
+description=That is, for those attributes, the values are not allowed to contain any bytes having the high-order bit set, which is used to indicate the presence of non-ASCII characters. Some applications do not properly handle attribute values that contain non-ASCII characters, and this plug-in can help ensure that attributes used by those applications do not contain characters that can cause problems in those applications.
+property.attribute-type.synopsis=Specifies the name or OID of an attribute type for which values should be checked to ensure that they are 7-bit clean.
+property.base-dn.synopsis=Specifies the base DN below which the checking is performed.
+property.base-dn.description=Any attempt to update a value for one of the configured attributes below this base DN must be 7-bit clean for the operation to be allowed.
+property.base-dn.default-behavior.alias.synopsis=All entries below all public naming contexts will be checked.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/SevenBitCleanPluginCfgDefn_ko.properties b/opends/src/admin/messages/SevenBitCleanPluginCfgDefn_ko.properties
new file mode 100644
index 0000000..37ea266
--- /dev/null
+++ b/opends/src/admin/messages/SevenBitCleanPluginCfgDefn_ko.properties
@@ -0,0 +1,63 @@
+user-friendly-name=Seven Bit Clean Plugin
+user-friendly-plural-name=Seven Bit Clean Plugins
+synopsis=The Seven Bit Clean Plugin ensures that values for a specified set of attributes are 7-bit clean.
+description=That is, for those attributes, the values are not allowed to contain any bytes having the high-order bit set, which is used to indicate the presence of non-ASCII characters. Some applications do not properly handle attribute values that contain non-ASCII characters, and this plug-in can help ensure that attributes used by those applications do not contain characters that can cause problems in those applications.
+property.attribute-type.synopsis=Specifies the name or OID of an attribute type for which values should be checked to ensure that they are 7-bit clean.
+property.base-dn.synopsis=Specifies the base DN below which the checking is performed.
+property.base-dn.description=Any attempt to update a value for one of the configured attributes below this base DN must be 7-bit clean for the operation to be allowed.
+property.base-dn.default-behavior.alias.synopsis=All entries below all public naming contexts will be checked.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/SevenBitCleanPluginCfgDefn_zh_CN.properties b/opends/src/admin/messages/SevenBitCleanPluginCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..37ea266
--- /dev/null
+++ b/opends/src/admin/messages/SevenBitCleanPluginCfgDefn_zh_CN.properties
@@ -0,0 +1,63 @@
+user-friendly-name=Seven Bit Clean Plugin
+user-friendly-plural-name=Seven Bit Clean Plugins
+synopsis=The Seven Bit Clean Plugin ensures that values for a specified set of attributes are 7-bit clean.
+description=That is, for those attributes, the values are not allowed to contain any bytes having the high-order bit set, which is used to indicate the presence of non-ASCII characters. Some applications do not properly handle attribute values that contain non-ASCII characters, and this plug-in can help ensure that attributes used by those applications do not contain characters that can cause problems in those applications.
+property.attribute-type.synopsis=Specifies the name or OID of an attribute type for which values should be checked to ensure that they are 7-bit clean.
+property.base-dn.synopsis=Specifies the base DN below which the checking is performed.
+property.base-dn.description=Any attempt to update a value for one of the configured attributes below this base DN must be 7-bit clean for the operation to be allowed.
+property.base-dn.default-behavior.alias.synopsis=All entries below all public naming contexts will be checked.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/SevenBitCleanPluginCfgDefn_zh_TW.properties b/opends/src/admin/messages/SevenBitCleanPluginCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..37ea266
--- /dev/null
+++ b/opends/src/admin/messages/SevenBitCleanPluginCfgDefn_zh_TW.properties
@@ -0,0 +1,63 @@
+user-friendly-name=Seven Bit Clean Plugin
+user-friendly-plural-name=Seven Bit Clean Plugins
+synopsis=The Seven Bit Clean Plugin ensures that values for a specified set of attributes are 7-bit clean.
+description=That is, for those attributes, the values are not allowed to contain any bytes having the high-order bit set, which is used to indicate the presence of non-ASCII characters. Some applications do not properly handle attribute values that contain non-ASCII characters, and this plug-in can help ensure that attributes used by those applications do not contain characters that can cause problems in those applications.
+property.attribute-type.synopsis=Specifies the name or OID of an attribute type for which values should be checked to ensure that they are 7-bit clean.
+property.base-dn.synopsis=Specifies the base DN below which the checking is performed.
+property.base-dn.description=Any attempt to update a value for one of the configured attributes below this base DN must be 7-bit clean for the operation to be allowed.
+property.base-dn.default-behavior.alias.synopsis=All entries below all public naming contexts will be checked.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
diff --git a/opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn.properties b/opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn.properties
new file mode 100644
index 0000000..847e5bd
--- /dev/null
+++ b/opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Similarity Based Password Validator
+user-friendly-plural-name=Similarity Based Password Validators
+synopsis=The Similarity Based Password Validator determines whether a proposed password is acceptable by measuring how similar it is to the user's current password.
+description=In particular, it uses the Levenshtein Distance algorithm to determine the minimum number of changes (where a change may be inserting, deleting, or replacing a character) to transform one string into the other. It can be used to prevent users from making only minor changes to their current password when setting a new password. Note that for this password validator to be effective, it is necessary to have access to the user's current password. Therefore, if this password validator is to be enabled, the password-change-requires-current-password attribute in the password policy configuration must also be set to true.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.min-password-difference.synopsis=Specifies the minimum difference of new and old password.
+property.min-password-difference.description=A value of zero indicates that no difference between passwords is acceptable.
diff --git a/opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_de.properties b/opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_de.properties
new file mode 100644
index 0000000..847e5bd
--- /dev/null
+++ b/opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_de.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Similarity Based Password Validator
+user-friendly-plural-name=Similarity Based Password Validators
+synopsis=The Similarity Based Password Validator determines whether a proposed password is acceptable by measuring how similar it is to the user's current password.
+description=In particular, it uses the Levenshtein Distance algorithm to determine the minimum number of changes (where a change may be inserting, deleting, or replacing a character) to transform one string into the other. It can be used to prevent users from making only minor changes to their current password when setting a new password. Note that for this password validator to be effective, it is necessary to have access to the user's current password. Therefore, if this password validator is to be enabled, the password-change-requires-current-password attribute in the password policy configuration must also be set to true.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.min-password-difference.synopsis=Specifies the minimum difference of new and old password.
+property.min-password-difference.description=A value of zero indicates that no difference between passwords is acceptable.
diff --git a/opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_es.properties b/opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_es.properties
new file mode 100644
index 0000000..847e5bd
--- /dev/null
+++ b/opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_es.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Similarity Based Password Validator
+user-friendly-plural-name=Similarity Based Password Validators
+synopsis=The Similarity Based Password Validator determines whether a proposed password is acceptable by measuring how similar it is to the user's current password.
+description=In particular, it uses the Levenshtein Distance algorithm to determine the minimum number of changes (where a change may be inserting, deleting, or replacing a character) to transform one string into the other. It can be used to prevent users from making only minor changes to their current password when setting a new password. Note that for this password validator to be effective, it is necessary to have access to the user's current password. Therefore, if this password validator is to be enabled, the password-change-requires-current-password attribute in the password policy configuration must also be set to true.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.min-password-difference.synopsis=Specifies the minimum difference of new and old password.
+property.min-password-difference.description=A value of zero indicates that no difference between passwords is acceptable.
diff --git a/opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_fr.properties b/opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_fr.properties
new file mode 100644
index 0000000..847e5bd
--- /dev/null
+++ b/opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_fr.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Similarity Based Password Validator
+user-friendly-plural-name=Similarity Based Password Validators
+synopsis=The Similarity Based Password Validator determines whether a proposed password is acceptable by measuring how similar it is to the user's current password.
+description=In particular, it uses the Levenshtein Distance algorithm to determine the minimum number of changes (where a change may be inserting, deleting, or replacing a character) to transform one string into the other. It can be used to prevent users from making only minor changes to their current password when setting a new password. Note that for this password validator to be effective, it is necessary to have access to the user's current password. Therefore, if this password validator is to be enabled, the password-change-requires-current-password attribute in the password policy configuration must also be set to true.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.min-password-difference.synopsis=Specifies the minimum difference of new and old password.
+property.min-password-difference.description=A value of zero indicates that no difference between passwords is acceptable.
diff --git a/opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_ja.properties b/opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_ja.properties
new file mode 100644
index 0000000..847e5bd
--- /dev/null
+++ b/opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_ja.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Similarity Based Password Validator
+user-friendly-plural-name=Similarity Based Password Validators
+synopsis=The Similarity Based Password Validator determines whether a proposed password is acceptable by measuring how similar it is to the user's current password.
+description=In particular, it uses the Levenshtein Distance algorithm to determine the minimum number of changes (where a change may be inserting, deleting, or replacing a character) to transform one string into the other. It can be used to prevent users from making only minor changes to their current password when setting a new password. Note that for this password validator to be effective, it is necessary to have access to the user's current password. Therefore, if this password validator is to be enabled, the password-change-requires-current-password attribute in the password policy configuration must also be set to true.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.min-password-difference.synopsis=Specifies the minimum difference of new and old password.
+property.min-password-difference.description=A value of zero indicates that no difference between passwords is acceptable.
diff --git a/opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_ko.properties b/opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_ko.properties
new file mode 100644
index 0000000..847e5bd
--- /dev/null
+++ b/opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_ko.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Similarity Based Password Validator
+user-friendly-plural-name=Similarity Based Password Validators
+synopsis=The Similarity Based Password Validator determines whether a proposed password is acceptable by measuring how similar it is to the user's current password.
+description=In particular, it uses the Levenshtein Distance algorithm to determine the minimum number of changes (where a change may be inserting, deleting, or replacing a character) to transform one string into the other. It can be used to prevent users from making only minor changes to their current password when setting a new password. Note that for this password validator to be effective, it is necessary to have access to the user's current password. Therefore, if this password validator is to be enabled, the password-change-requires-current-password attribute in the password policy configuration must also be set to true.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.min-password-difference.synopsis=Specifies the minimum difference of new and old password.
+property.min-password-difference.description=A value of zero indicates that no difference between passwords is acceptable.
diff --git a/opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_zh_CN.properties b/opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..847e5bd
--- /dev/null
+++ b/opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_zh_CN.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Similarity Based Password Validator
+user-friendly-plural-name=Similarity Based Password Validators
+synopsis=The Similarity Based Password Validator determines whether a proposed password is acceptable by measuring how similar it is to the user's current password.
+description=In particular, it uses the Levenshtein Distance algorithm to determine the minimum number of changes (where a change may be inserting, deleting, or replacing a character) to transform one string into the other. It can be used to prevent users from making only minor changes to their current password when setting a new password. Note that for this password validator to be effective, it is necessary to have access to the user's current password. Therefore, if this password validator is to be enabled, the password-change-requires-current-password attribute in the password policy configuration must also be set to true.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.min-password-difference.synopsis=Specifies the minimum difference of new and old password.
+property.min-password-difference.description=A value of zero indicates that no difference between passwords is acceptable.
diff --git a/opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_zh_TW.properties b/opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..847e5bd
--- /dev/null
+++ b/opends/src/admin/messages/SimilarityBasedPasswordValidatorCfgDefn_zh_TW.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Similarity Based Password Validator
+user-friendly-plural-name=Similarity Based Password Validators
+synopsis=The Similarity Based Password Validator determines whether a proposed password is acceptable by measuring how similar it is to the user's current password.
+description=In particular, it uses the Levenshtein Distance algorithm to determine the minimum number of changes (where a change may be inserting, deleting, or replacing a character) to transform one string into the other. It can be used to prevent users from making only minor changes to their current password when setting a new password. Note that for this password validator to be effective, it is necessary to have access to the user's current password. Therefore, if this password validator is to be enabled, the password-change-requires-current-password attribute in the password policy configuration must also be set to true.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.min-password-difference.synopsis=Specifies the minimum difference of new and old password.
+property.min-password-difference.description=A value of zero indicates that no difference between passwords is acceptable.
diff --git a/opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn.properties b/opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn.properties
new file mode 100644
index 0000000..33b4226
--- /dev/null
+++ b/opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Size Limit Log Retention Policy
+user-friendly-plural-name=Size Limit Log Retention Policies
+synopsis=Retention policy based on the amount of space taken by all the log files on disk.
+property.disk-space-used.synopsis=Specifies the maximum total disk space used by the log files.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Size Limit Log Retention Policy implementation.
diff --git a/opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_de.properties b/opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_de.properties
new file mode 100644
index 0000000..33b4226
--- /dev/null
+++ b/opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_de.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Size Limit Log Retention Policy
+user-friendly-plural-name=Size Limit Log Retention Policies
+synopsis=Retention policy based on the amount of space taken by all the log files on disk.
+property.disk-space-used.synopsis=Specifies the maximum total disk space used by the log files.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Size Limit Log Retention Policy implementation.
diff --git a/opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_es.properties b/opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_es.properties
new file mode 100644
index 0000000..33b4226
--- /dev/null
+++ b/opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_es.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Size Limit Log Retention Policy
+user-friendly-plural-name=Size Limit Log Retention Policies
+synopsis=Retention policy based on the amount of space taken by all the log files on disk.
+property.disk-space-used.synopsis=Specifies the maximum total disk space used by the log files.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Size Limit Log Retention Policy implementation.
diff --git a/opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_fr.properties b/opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_fr.properties
new file mode 100644
index 0000000..33b4226
--- /dev/null
+++ b/opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_fr.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Size Limit Log Retention Policy
+user-friendly-plural-name=Size Limit Log Retention Policies
+synopsis=Retention policy based on the amount of space taken by all the log files on disk.
+property.disk-space-used.synopsis=Specifies the maximum total disk space used by the log files.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Size Limit Log Retention Policy implementation.
diff --git a/opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_ja.properties b/opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_ja.properties
new file mode 100644
index 0000000..33b4226
--- /dev/null
+++ b/opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_ja.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Size Limit Log Retention Policy
+user-friendly-plural-name=Size Limit Log Retention Policies
+synopsis=Retention policy based on the amount of space taken by all the log files on disk.
+property.disk-space-used.synopsis=Specifies the maximum total disk space used by the log files.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Size Limit Log Retention Policy implementation.
diff --git a/opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_ko.properties b/opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_ko.properties
new file mode 100644
index 0000000..33b4226
--- /dev/null
+++ b/opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_ko.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Size Limit Log Retention Policy
+user-friendly-plural-name=Size Limit Log Retention Policies
+synopsis=Retention policy based on the amount of space taken by all the log files on disk.
+property.disk-space-used.synopsis=Specifies the maximum total disk space used by the log files.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Size Limit Log Retention Policy implementation.
diff --git a/opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_zh_CN.properties b/opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..33b4226
--- /dev/null
+++ b/opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_zh_CN.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Size Limit Log Retention Policy
+user-friendly-plural-name=Size Limit Log Retention Policies
+synopsis=Retention policy based on the amount of space taken by all the log files on disk.
+property.disk-space-used.synopsis=Specifies the maximum total disk space used by the log files.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Size Limit Log Retention Policy implementation.
diff --git a/opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_zh_TW.properties b/opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..33b4226
--- /dev/null
+++ b/opends/src/admin/messages/SizeLimitLogRetentionPolicyCfgDefn_zh_TW.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Size Limit Log Retention Policy
+user-friendly-plural-name=Size Limit Log Retention Policies
+synopsis=Retention policy based on the amount of space taken by all the log files on disk.
+property.disk-space-used.synopsis=Specifies the maximum total disk space used by the log files.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Size Limit Log Retention Policy implementation.
diff --git a/opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn.properties b/opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn.properties
new file mode 100644
index 0000000..611f804
--- /dev/null
+++ b/opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Size Limit Log Rotation Policy
+user-friendly-plural-name=Size Limit Log Rotation Policies
+synopsis=Rotation policy based on the size of the log file.
+property.file-size-limit.synopsis=Specifies the maximum size that a log file can reach before it is rotated.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Size Limit Log Rotation Policy implementation.
diff --git a/opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_de.properties b/opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_de.properties
new file mode 100644
index 0000000..611f804
--- /dev/null
+++ b/opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_de.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Size Limit Log Rotation Policy
+user-friendly-plural-name=Size Limit Log Rotation Policies
+synopsis=Rotation policy based on the size of the log file.
+property.file-size-limit.synopsis=Specifies the maximum size that a log file can reach before it is rotated.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Size Limit Log Rotation Policy implementation.
diff --git a/opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_es.properties b/opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_es.properties
new file mode 100644
index 0000000..611f804
--- /dev/null
+++ b/opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_es.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Size Limit Log Rotation Policy
+user-friendly-plural-name=Size Limit Log Rotation Policies
+synopsis=Rotation policy based on the size of the log file.
+property.file-size-limit.synopsis=Specifies the maximum size that a log file can reach before it is rotated.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Size Limit Log Rotation Policy implementation.
diff --git a/opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_fr.properties b/opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_fr.properties
new file mode 100644
index 0000000..611f804
--- /dev/null
+++ b/opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_fr.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Size Limit Log Rotation Policy
+user-friendly-plural-name=Size Limit Log Rotation Policies
+synopsis=Rotation policy based on the size of the log file.
+property.file-size-limit.synopsis=Specifies the maximum size that a log file can reach before it is rotated.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Size Limit Log Rotation Policy implementation.
diff --git a/opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_ja.properties b/opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_ja.properties
new file mode 100644
index 0000000..611f804
--- /dev/null
+++ b/opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_ja.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Size Limit Log Rotation Policy
+user-friendly-plural-name=Size Limit Log Rotation Policies
+synopsis=Rotation policy based on the size of the log file.
+property.file-size-limit.synopsis=Specifies the maximum size that a log file can reach before it is rotated.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Size Limit Log Rotation Policy implementation.
diff --git a/opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_ko.properties b/opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_ko.properties
new file mode 100644
index 0000000..611f804
--- /dev/null
+++ b/opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_ko.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Size Limit Log Rotation Policy
+user-friendly-plural-name=Size Limit Log Rotation Policies
+synopsis=Rotation policy based on the size of the log file.
+property.file-size-limit.synopsis=Specifies the maximum size that a log file can reach before it is rotated.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Size Limit Log Rotation Policy implementation.
diff --git a/opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_zh_CN.properties b/opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..611f804
--- /dev/null
+++ b/opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_zh_CN.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Size Limit Log Rotation Policy
+user-friendly-plural-name=Size Limit Log Rotation Policies
+synopsis=Rotation policy based on the size of the log file.
+property.file-size-limit.synopsis=Specifies the maximum size that a log file can reach before it is rotated.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Size Limit Log Rotation Policy implementation.
diff --git a/opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_zh_TW.properties b/opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..611f804
--- /dev/null
+++ b/opends/src/admin/messages/SizeLimitLogRotationPolicyCfgDefn_zh_TW.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Size Limit Log Rotation Policy
+user-friendly-plural-name=Size Limit Log Rotation Policies
+synopsis=Rotation policy based on the size of the log file.
+property.file-size-limit.synopsis=Specifies the maximum size that a log file can reach before it is rotated.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Size Limit Log Rotation Policy implementation.
diff --git a/opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn.properties b/opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn.properties
new file mode 100644
index 0000000..92ee691
--- /dev/null
+++ b/opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Soft Reference Entry Cache
+user-friendly-plural-name=Soft Reference Entry Caches
+synopsis=The Soft Reference Entry Cache is a Directory Server entry cache implementation that uses soft references to manage objects to allow them to be freed if the JVM is running low on memory.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.enabled.synopsis=Indicates whether the Soft Reference Entry Cache is enabled.
+property.exclude-filter.synopsis=The set of filters that define the entries that should be excluded from the cache.
+property.include-filter.synopsis=The set of filters that define the entries that should be included in the cache.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Soft Reference Entry Cache implementation.
+property.lock-timeout.synopsis=Specifies the length of time in milliseconds to wait while attempting to acquire a read or write lock.
diff --git a/opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_de.properties b/opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_de.properties
new file mode 100644
index 0000000..92ee691
--- /dev/null
+++ b/opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_de.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Soft Reference Entry Cache
+user-friendly-plural-name=Soft Reference Entry Caches
+synopsis=The Soft Reference Entry Cache is a Directory Server entry cache implementation that uses soft references to manage objects to allow them to be freed if the JVM is running low on memory.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.enabled.synopsis=Indicates whether the Soft Reference Entry Cache is enabled.
+property.exclude-filter.synopsis=The set of filters that define the entries that should be excluded from the cache.
+property.include-filter.synopsis=The set of filters that define the entries that should be included in the cache.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Soft Reference Entry Cache implementation.
+property.lock-timeout.synopsis=Specifies the length of time in milliseconds to wait while attempting to acquire a read or write lock.
diff --git a/opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_es.properties b/opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_es.properties
new file mode 100644
index 0000000..92ee691
--- /dev/null
+++ b/opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_es.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Soft Reference Entry Cache
+user-friendly-plural-name=Soft Reference Entry Caches
+synopsis=The Soft Reference Entry Cache is a Directory Server entry cache implementation that uses soft references to manage objects to allow them to be freed if the JVM is running low on memory.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.enabled.synopsis=Indicates whether the Soft Reference Entry Cache is enabled.
+property.exclude-filter.synopsis=The set of filters that define the entries that should be excluded from the cache.
+property.include-filter.synopsis=The set of filters that define the entries that should be included in the cache.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Soft Reference Entry Cache implementation.
+property.lock-timeout.synopsis=Specifies the length of time in milliseconds to wait while attempting to acquire a read or write lock.
diff --git a/opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_fr.properties b/opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_fr.properties
new file mode 100644
index 0000000..92ee691
--- /dev/null
+++ b/opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_fr.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Soft Reference Entry Cache
+user-friendly-plural-name=Soft Reference Entry Caches
+synopsis=The Soft Reference Entry Cache is a Directory Server entry cache implementation that uses soft references to manage objects to allow them to be freed if the JVM is running low on memory.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.enabled.synopsis=Indicates whether the Soft Reference Entry Cache is enabled.
+property.exclude-filter.synopsis=The set of filters that define the entries that should be excluded from the cache.
+property.include-filter.synopsis=The set of filters that define the entries that should be included in the cache.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Soft Reference Entry Cache implementation.
+property.lock-timeout.synopsis=Specifies the length of time in milliseconds to wait while attempting to acquire a read or write lock.
diff --git a/opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_ja.properties b/opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_ja.properties
new file mode 100644
index 0000000..92ee691
--- /dev/null
+++ b/opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_ja.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Soft Reference Entry Cache
+user-friendly-plural-name=Soft Reference Entry Caches
+synopsis=The Soft Reference Entry Cache is a Directory Server entry cache implementation that uses soft references to manage objects to allow them to be freed if the JVM is running low on memory.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.enabled.synopsis=Indicates whether the Soft Reference Entry Cache is enabled.
+property.exclude-filter.synopsis=The set of filters that define the entries that should be excluded from the cache.
+property.include-filter.synopsis=The set of filters that define the entries that should be included in the cache.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Soft Reference Entry Cache implementation.
+property.lock-timeout.synopsis=Specifies the length of time in milliseconds to wait while attempting to acquire a read or write lock.
diff --git a/opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_ko.properties b/opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_ko.properties
new file mode 100644
index 0000000..92ee691
--- /dev/null
+++ b/opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_ko.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Soft Reference Entry Cache
+user-friendly-plural-name=Soft Reference Entry Caches
+synopsis=The Soft Reference Entry Cache is a Directory Server entry cache implementation that uses soft references to manage objects to allow them to be freed if the JVM is running low on memory.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.enabled.synopsis=Indicates whether the Soft Reference Entry Cache is enabled.
+property.exclude-filter.synopsis=The set of filters that define the entries that should be excluded from the cache.
+property.include-filter.synopsis=The set of filters that define the entries that should be included in the cache.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Soft Reference Entry Cache implementation.
+property.lock-timeout.synopsis=Specifies the length of time in milliseconds to wait while attempting to acquire a read or write lock.
diff --git a/opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_zh_CN.properties b/opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..92ee691
--- /dev/null
+++ b/opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_zh_CN.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Soft Reference Entry Cache
+user-friendly-plural-name=Soft Reference Entry Caches
+synopsis=The Soft Reference Entry Cache is a Directory Server entry cache implementation that uses soft references to manage objects to allow them to be freed if the JVM is running low on memory.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.enabled.synopsis=Indicates whether the Soft Reference Entry Cache is enabled.
+property.exclude-filter.synopsis=The set of filters that define the entries that should be excluded from the cache.
+property.include-filter.synopsis=The set of filters that define the entries that should be included in the cache.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Soft Reference Entry Cache implementation.
+property.lock-timeout.synopsis=Specifies the length of time in milliseconds to wait while attempting to acquire a read or write lock.
diff --git a/opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_zh_TW.properties b/opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..92ee691
--- /dev/null
+++ b/opends/src/admin/messages/SoftReferenceEntryCacheCfgDefn_zh_TW.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Soft Reference Entry Cache
+user-friendly-plural-name=Soft Reference Entry Caches
+synopsis=The Soft Reference Entry Cache is a Directory Server entry cache implementation that uses soft references to manage objects to allow them to be freed if the JVM is running low on memory.
+property.cache-level.synopsis=Specifies the cache level in the cache order if more than one instance of the cache is configured.
+property.enabled.synopsis=Indicates whether the Soft Reference Entry Cache is enabled.
+property.exclude-filter.synopsis=The set of filters that define the entries that should be excluded from the cache.
+property.include-filter.synopsis=The set of filters that define the entries that should be included in the cache.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Soft Reference Entry Cache implementation.
+property.lock-timeout.synopsis=Specifies the length of time in milliseconds to wait while attempting to acquire a read or write lock.
diff --git a/opends/src/admin/messages/StackTraceMonitorProviderCfgDefn.properties b/opends/src/admin/messages/StackTraceMonitorProviderCfgDefn.properties
new file mode 100644
index 0000000..66ad763
--- /dev/null
+++ b/opends/src/admin/messages/StackTraceMonitorProviderCfgDefn.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Stack Trace Monitor Provider
+user-friendly-plural-name=Stack Trace Monitor Providers
+synopsis=The Stack Trace Monitor Provider enables clients to obtain a stack trace of all the threads that are currently running in the Directory Server.
+property.enabled.synopsis=Indicates whether the Stack Trace Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Stack Trace Monitor Provider implementation.
diff --git a/opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_de.properties b/opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_de.properties
new file mode 100644
index 0000000..66ad763
--- /dev/null
+++ b/opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_de.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Stack Trace Monitor Provider
+user-friendly-plural-name=Stack Trace Monitor Providers
+synopsis=The Stack Trace Monitor Provider enables clients to obtain a stack trace of all the threads that are currently running in the Directory Server.
+property.enabled.synopsis=Indicates whether the Stack Trace Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Stack Trace Monitor Provider implementation.
diff --git a/opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_es.properties b/opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_es.properties
new file mode 100644
index 0000000..66ad763
--- /dev/null
+++ b/opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_es.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Stack Trace Monitor Provider
+user-friendly-plural-name=Stack Trace Monitor Providers
+synopsis=The Stack Trace Monitor Provider enables clients to obtain a stack trace of all the threads that are currently running in the Directory Server.
+property.enabled.synopsis=Indicates whether the Stack Trace Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Stack Trace Monitor Provider implementation.
diff --git a/opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_fr.properties b/opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_fr.properties
new file mode 100644
index 0000000..66ad763
--- /dev/null
+++ b/opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_fr.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Stack Trace Monitor Provider
+user-friendly-plural-name=Stack Trace Monitor Providers
+synopsis=The Stack Trace Monitor Provider enables clients to obtain a stack trace of all the threads that are currently running in the Directory Server.
+property.enabled.synopsis=Indicates whether the Stack Trace Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Stack Trace Monitor Provider implementation.
diff --git a/opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_ja.properties b/opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_ja.properties
new file mode 100644
index 0000000..66ad763
--- /dev/null
+++ b/opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_ja.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Stack Trace Monitor Provider
+user-friendly-plural-name=Stack Trace Monitor Providers
+synopsis=The Stack Trace Monitor Provider enables clients to obtain a stack trace of all the threads that are currently running in the Directory Server.
+property.enabled.synopsis=Indicates whether the Stack Trace Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Stack Trace Monitor Provider implementation.
diff --git a/opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_ko.properties b/opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_ko.properties
new file mode 100644
index 0000000..66ad763
--- /dev/null
+++ b/opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_ko.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Stack Trace Monitor Provider
+user-friendly-plural-name=Stack Trace Monitor Providers
+synopsis=The Stack Trace Monitor Provider enables clients to obtain a stack trace of all the threads that are currently running in the Directory Server.
+property.enabled.synopsis=Indicates whether the Stack Trace Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Stack Trace Monitor Provider implementation.
diff --git a/opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_zh_CN.properties b/opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..66ad763
--- /dev/null
+++ b/opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_zh_CN.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Stack Trace Monitor Provider
+user-friendly-plural-name=Stack Trace Monitor Providers
+synopsis=The Stack Trace Monitor Provider enables clients to obtain a stack trace of all the threads that are currently running in the Directory Server.
+property.enabled.synopsis=Indicates whether the Stack Trace Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Stack Trace Monitor Provider implementation.
diff --git a/opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_zh_TW.properties b/opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..66ad763
--- /dev/null
+++ b/opends/src/admin/messages/StackTraceMonitorProviderCfgDefn_zh_TW.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Stack Trace Monitor Provider
+user-friendly-plural-name=Stack Trace Monitor Providers
+synopsis=The Stack Trace Monitor Provider enables clients to obtain a stack trace of all the threads that are currently running in the Directory Server.
+property.enabled.synopsis=Indicates whether the Stack Trace Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Stack Trace Monitor Provider implementation.
diff --git a/opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn.properties b/opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn.properties
new file mode 100644
index 0000000..46db7a5
--- /dev/null
+++ b/opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Start TLS Extended Operation Handler
+user-friendly-plural-name=Start TLS Extended Operation Handlers
+synopsis=The Start TLS Extended Operation Handler provides the ability clients to use the StartTLS extended operation to initiate a secure communication channel over an otherwise clear-text LDAP connection.
+property.enabled.synopsis=Indicates whether the Start TLS Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Start TLS Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_de.properties b/opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..46db7a5
--- /dev/null
+++ b/opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_de.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Start TLS Extended Operation Handler
+user-friendly-plural-name=Start TLS Extended Operation Handlers
+synopsis=The Start TLS Extended Operation Handler provides the ability clients to use the StartTLS extended operation to initiate a secure communication channel over an otherwise clear-text LDAP connection.
+property.enabled.synopsis=Indicates whether the Start TLS Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Start TLS Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_es.properties b/opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..46db7a5
--- /dev/null
+++ b/opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_es.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Start TLS Extended Operation Handler
+user-friendly-plural-name=Start TLS Extended Operation Handlers
+synopsis=The Start TLS Extended Operation Handler provides the ability clients to use the StartTLS extended operation to initiate a secure communication channel over an otherwise clear-text LDAP connection.
+property.enabled.synopsis=Indicates whether the Start TLS Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Start TLS Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_fr.properties b/opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..46db7a5
--- /dev/null
+++ b/opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_fr.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Start TLS Extended Operation Handler
+user-friendly-plural-name=Start TLS Extended Operation Handlers
+synopsis=The Start TLS Extended Operation Handler provides the ability clients to use the StartTLS extended operation to initiate a secure communication channel over an otherwise clear-text LDAP connection.
+property.enabled.synopsis=Indicates whether the Start TLS Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Start TLS Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_ja.properties b/opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..46db7a5
--- /dev/null
+++ b/opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_ja.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Start TLS Extended Operation Handler
+user-friendly-plural-name=Start TLS Extended Operation Handlers
+synopsis=The Start TLS Extended Operation Handler provides the ability clients to use the StartTLS extended operation to initiate a secure communication channel over an otherwise clear-text LDAP connection.
+property.enabled.synopsis=Indicates whether the Start TLS Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Start TLS Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_ko.properties b/opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..46db7a5
--- /dev/null
+++ b/opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_ko.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Start TLS Extended Operation Handler
+user-friendly-plural-name=Start TLS Extended Operation Handlers
+synopsis=The Start TLS Extended Operation Handler provides the ability clients to use the StartTLS extended operation to initiate a secure communication channel over an otherwise clear-text LDAP connection.
+property.enabled.synopsis=Indicates whether the Start TLS Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Start TLS Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..46db7a5
--- /dev/null
+++ b/opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Start TLS Extended Operation Handler
+user-friendly-plural-name=Start TLS Extended Operation Handlers
+synopsis=The Start TLS Extended Operation Handler provides the ability clients to use the StartTLS extended operation to initiate a secure communication channel over an otherwise clear-text LDAP connection.
+property.enabled.synopsis=Indicates whether the Start TLS Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Start TLS Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..46db7a5
--- /dev/null
+++ b/opends/src/admin/messages/StartTLSExtendedOperationHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Start TLS Extended Operation Handler
+user-friendly-plural-name=Start TLS Extended Operation Handlers
+synopsis=The Start TLS Extended Operation Handler provides the ability clients to use the StartTLS extended operation to initiate a secure communication channel over an otherwise clear-text LDAP connection.
+property.enabled.synopsis=Indicates whether the Start TLS Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Start TLS Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/StaticGroupImplementationCfgDefn.properties b/opends/src/admin/messages/StaticGroupImplementationCfgDefn.properties
new file mode 100644
index 0000000..a3b269f
--- /dev/null
+++ b/opends/src/admin/messages/StaticGroupImplementationCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Static Group Implementation
+user-friendly-plural-name=Static Group Implementations
+synopsis=The Static Group Implementation provides a grouping mechanism in which the group membership is based on an explicit list of the DNs of the users that are members of the group.
+description=Note that it is possible to nest static groups by including the DN of a nested group in the member list for the parent group.
+property.enabled.synopsis=Indicates whether the Static Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Static Group Implementation implementation.
diff --git a/opends/src/admin/messages/StaticGroupImplementationCfgDefn_de.properties b/opends/src/admin/messages/StaticGroupImplementationCfgDefn_de.properties
new file mode 100644
index 0000000..a3b269f
--- /dev/null
+++ b/opends/src/admin/messages/StaticGroupImplementationCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Static Group Implementation
+user-friendly-plural-name=Static Group Implementations
+synopsis=The Static Group Implementation provides a grouping mechanism in which the group membership is based on an explicit list of the DNs of the users that are members of the group.
+description=Note that it is possible to nest static groups by including the DN of a nested group in the member list for the parent group.
+property.enabled.synopsis=Indicates whether the Static Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Static Group Implementation implementation.
diff --git a/opends/src/admin/messages/StaticGroupImplementationCfgDefn_es.properties b/opends/src/admin/messages/StaticGroupImplementationCfgDefn_es.properties
new file mode 100644
index 0000000..a3b269f
--- /dev/null
+++ b/opends/src/admin/messages/StaticGroupImplementationCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Static Group Implementation
+user-friendly-plural-name=Static Group Implementations
+synopsis=The Static Group Implementation provides a grouping mechanism in which the group membership is based on an explicit list of the DNs of the users that are members of the group.
+description=Note that it is possible to nest static groups by including the DN of a nested group in the member list for the parent group.
+property.enabled.synopsis=Indicates whether the Static Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Static Group Implementation implementation.
diff --git a/opends/src/admin/messages/StaticGroupImplementationCfgDefn_fr.properties b/opends/src/admin/messages/StaticGroupImplementationCfgDefn_fr.properties
new file mode 100644
index 0000000..a3b269f
--- /dev/null
+++ b/opends/src/admin/messages/StaticGroupImplementationCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Static Group Implementation
+user-friendly-plural-name=Static Group Implementations
+synopsis=The Static Group Implementation provides a grouping mechanism in which the group membership is based on an explicit list of the DNs of the users that are members of the group.
+description=Note that it is possible to nest static groups by including the DN of a nested group in the member list for the parent group.
+property.enabled.synopsis=Indicates whether the Static Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Static Group Implementation implementation.
diff --git a/opends/src/admin/messages/StaticGroupImplementationCfgDefn_ja.properties b/opends/src/admin/messages/StaticGroupImplementationCfgDefn_ja.properties
new file mode 100644
index 0000000..a3b269f
--- /dev/null
+++ b/opends/src/admin/messages/StaticGroupImplementationCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Static Group Implementation
+user-friendly-plural-name=Static Group Implementations
+synopsis=The Static Group Implementation provides a grouping mechanism in which the group membership is based on an explicit list of the DNs of the users that are members of the group.
+description=Note that it is possible to nest static groups by including the DN of a nested group in the member list for the parent group.
+property.enabled.synopsis=Indicates whether the Static Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Static Group Implementation implementation.
diff --git a/opends/src/admin/messages/StaticGroupImplementationCfgDefn_ko.properties b/opends/src/admin/messages/StaticGroupImplementationCfgDefn_ko.properties
new file mode 100644
index 0000000..a3b269f
--- /dev/null
+++ b/opends/src/admin/messages/StaticGroupImplementationCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Static Group Implementation
+user-friendly-plural-name=Static Group Implementations
+synopsis=The Static Group Implementation provides a grouping mechanism in which the group membership is based on an explicit list of the DNs of the users that are members of the group.
+description=Note that it is possible to nest static groups by including the DN of a nested group in the member list for the parent group.
+property.enabled.synopsis=Indicates whether the Static Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Static Group Implementation implementation.
diff --git a/opends/src/admin/messages/StaticGroupImplementationCfgDefn_zh_CN.properties b/opends/src/admin/messages/StaticGroupImplementationCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..a3b269f
--- /dev/null
+++ b/opends/src/admin/messages/StaticGroupImplementationCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Static Group Implementation
+user-friendly-plural-name=Static Group Implementations
+synopsis=The Static Group Implementation provides a grouping mechanism in which the group membership is based on an explicit list of the DNs of the users that are members of the group.
+description=Note that it is possible to nest static groups by including the DN of a nested group in the member list for the parent group.
+property.enabled.synopsis=Indicates whether the Static Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Static Group Implementation implementation.
diff --git a/opends/src/admin/messages/StaticGroupImplementationCfgDefn_zh_TW.properties b/opends/src/admin/messages/StaticGroupImplementationCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..a3b269f
--- /dev/null
+++ b/opends/src/admin/messages/StaticGroupImplementationCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Static Group Implementation
+user-friendly-plural-name=Static Group Implementations
+synopsis=The Static Group Implementation provides a grouping mechanism in which the group membership is based on an explicit list of the DNs of the users that are members of the group.
+description=Note that it is possible to nest static groups by including the DN of a nested group in the member list for the parent group.
+property.enabled.synopsis=Indicates whether the Static Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Static Group Implementation implementation.
diff --git a/opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn.properties b/opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn.properties
new file mode 100644
index 0000000..86a7f21
--- /dev/null
+++ b/opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Subject Attribute To User Attribute Certificate Mapper
+user-friendly-plural-name=Subject Attribute To User Attribute Certificate Mappers
+synopsis=The Subject Attribute To User Attribute Certificate Mapper maps client certificates to user entries by mapping the values of attributes contained in the certificate subject to attributes contained in user entries.
+property.enabled.synopsis=Indicates whether the Subject Attribute To User Attribute Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Subject Attribute To User Attribute Certificate Mapper implementation.
+property.subject-attribute-mapping.synopsis=Specifies a mapping between certificate attributes and user attributes.
+property.subject-attribute-mapping.description=Each value should be in the form "certattr:userattr" where certattr is the name of the attribute in the certificate subject and userattr is the name of the corresponding attribute in user entries. There may be multiple mappings defined, and when performing the mapping values for all attributes present in the certificate subject that have mappings defined must be present in the corresponding user entries.
+property.user-base-dn.synopsis=Specifies the base DNs that should be used when performing searches to map the client certificate to a user entry.
+property.user-base-dn.default-behavior.alias.synopsis=The server will perform the search in all public naming contexts.
diff --git a/opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_de.properties b/opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_de.properties
new file mode 100644
index 0000000..86a7f21
--- /dev/null
+++ b/opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_de.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Subject Attribute To User Attribute Certificate Mapper
+user-friendly-plural-name=Subject Attribute To User Attribute Certificate Mappers
+synopsis=The Subject Attribute To User Attribute Certificate Mapper maps client certificates to user entries by mapping the values of attributes contained in the certificate subject to attributes contained in user entries.
+property.enabled.synopsis=Indicates whether the Subject Attribute To User Attribute Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Subject Attribute To User Attribute Certificate Mapper implementation.
+property.subject-attribute-mapping.synopsis=Specifies a mapping between certificate attributes and user attributes.
+property.subject-attribute-mapping.description=Each value should be in the form "certattr:userattr" where certattr is the name of the attribute in the certificate subject and userattr is the name of the corresponding attribute in user entries. There may be multiple mappings defined, and when performing the mapping values for all attributes present in the certificate subject that have mappings defined must be present in the corresponding user entries.
+property.user-base-dn.synopsis=Specifies the base DNs that should be used when performing searches to map the client certificate to a user entry.
+property.user-base-dn.default-behavior.alias.synopsis=The server will perform the search in all public naming contexts.
diff --git a/opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_es.properties b/opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_es.properties
new file mode 100644
index 0000000..86a7f21
--- /dev/null
+++ b/opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_es.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Subject Attribute To User Attribute Certificate Mapper
+user-friendly-plural-name=Subject Attribute To User Attribute Certificate Mappers
+synopsis=The Subject Attribute To User Attribute Certificate Mapper maps client certificates to user entries by mapping the values of attributes contained in the certificate subject to attributes contained in user entries.
+property.enabled.synopsis=Indicates whether the Subject Attribute To User Attribute Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Subject Attribute To User Attribute Certificate Mapper implementation.
+property.subject-attribute-mapping.synopsis=Specifies a mapping between certificate attributes and user attributes.
+property.subject-attribute-mapping.description=Each value should be in the form "certattr:userattr" where certattr is the name of the attribute in the certificate subject and userattr is the name of the corresponding attribute in user entries. There may be multiple mappings defined, and when performing the mapping values for all attributes present in the certificate subject that have mappings defined must be present in the corresponding user entries.
+property.user-base-dn.synopsis=Specifies the base DNs that should be used when performing searches to map the client certificate to a user entry.
+property.user-base-dn.default-behavior.alias.synopsis=The server will perform the search in all public naming contexts.
diff --git a/opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_fr.properties b/opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_fr.properties
new file mode 100644
index 0000000..86a7f21
--- /dev/null
+++ b/opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_fr.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Subject Attribute To User Attribute Certificate Mapper
+user-friendly-plural-name=Subject Attribute To User Attribute Certificate Mappers
+synopsis=The Subject Attribute To User Attribute Certificate Mapper maps client certificates to user entries by mapping the values of attributes contained in the certificate subject to attributes contained in user entries.
+property.enabled.synopsis=Indicates whether the Subject Attribute To User Attribute Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Subject Attribute To User Attribute Certificate Mapper implementation.
+property.subject-attribute-mapping.synopsis=Specifies a mapping between certificate attributes and user attributes.
+property.subject-attribute-mapping.description=Each value should be in the form "certattr:userattr" where certattr is the name of the attribute in the certificate subject and userattr is the name of the corresponding attribute in user entries. There may be multiple mappings defined, and when performing the mapping values for all attributes present in the certificate subject that have mappings defined must be present in the corresponding user entries.
+property.user-base-dn.synopsis=Specifies the base DNs that should be used when performing searches to map the client certificate to a user entry.
+property.user-base-dn.default-behavior.alias.synopsis=The server will perform the search in all public naming contexts.
diff --git a/opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_ja.properties b/opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_ja.properties
new file mode 100644
index 0000000..86a7f21
--- /dev/null
+++ b/opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_ja.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Subject Attribute To User Attribute Certificate Mapper
+user-friendly-plural-name=Subject Attribute To User Attribute Certificate Mappers
+synopsis=The Subject Attribute To User Attribute Certificate Mapper maps client certificates to user entries by mapping the values of attributes contained in the certificate subject to attributes contained in user entries.
+property.enabled.synopsis=Indicates whether the Subject Attribute To User Attribute Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Subject Attribute To User Attribute Certificate Mapper implementation.
+property.subject-attribute-mapping.synopsis=Specifies a mapping between certificate attributes and user attributes.
+property.subject-attribute-mapping.description=Each value should be in the form "certattr:userattr" where certattr is the name of the attribute in the certificate subject and userattr is the name of the corresponding attribute in user entries. There may be multiple mappings defined, and when performing the mapping values for all attributes present in the certificate subject that have mappings defined must be present in the corresponding user entries.
+property.user-base-dn.synopsis=Specifies the base DNs that should be used when performing searches to map the client certificate to a user entry.
+property.user-base-dn.default-behavior.alias.synopsis=The server will perform the search in all public naming contexts.
diff --git a/opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_ko.properties b/opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_ko.properties
new file mode 100644
index 0000000..86a7f21
--- /dev/null
+++ b/opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_ko.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Subject Attribute To User Attribute Certificate Mapper
+user-friendly-plural-name=Subject Attribute To User Attribute Certificate Mappers
+synopsis=The Subject Attribute To User Attribute Certificate Mapper maps client certificates to user entries by mapping the values of attributes contained in the certificate subject to attributes contained in user entries.
+property.enabled.synopsis=Indicates whether the Subject Attribute To User Attribute Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Subject Attribute To User Attribute Certificate Mapper implementation.
+property.subject-attribute-mapping.synopsis=Specifies a mapping between certificate attributes and user attributes.
+property.subject-attribute-mapping.description=Each value should be in the form "certattr:userattr" where certattr is the name of the attribute in the certificate subject and userattr is the name of the corresponding attribute in user entries. There may be multiple mappings defined, and when performing the mapping values for all attributes present in the certificate subject that have mappings defined must be present in the corresponding user entries.
+property.user-base-dn.synopsis=Specifies the base DNs that should be used when performing searches to map the client certificate to a user entry.
+property.user-base-dn.default-behavior.alias.synopsis=The server will perform the search in all public naming contexts.
diff --git a/opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_zh_CN.properties b/opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..86a7f21
--- /dev/null
+++ b/opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_zh_CN.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Subject Attribute To User Attribute Certificate Mapper
+user-friendly-plural-name=Subject Attribute To User Attribute Certificate Mappers
+synopsis=The Subject Attribute To User Attribute Certificate Mapper maps client certificates to user entries by mapping the values of attributes contained in the certificate subject to attributes contained in user entries.
+property.enabled.synopsis=Indicates whether the Subject Attribute To User Attribute Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Subject Attribute To User Attribute Certificate Mapper implementation.
+property.subject-attribute-mapping.synopsis=Specifies a mapping between certificate attributes and user attributes.
+property.subject-attribute-mapping.description=Each value should be in the form "certattr:userattr" where certattr is the name of the attribute in the certificate subject and userattr is the name of the corresponding attribute in user entries. There may be multiple mappings defined, and when performing the mapping values for all attributes present in the certificate subject that have mappings defined must be present in the corresponding user entries.
+property.user-base-dn.synopsis=Specifies the base DNs that should be used when performing searches to map the client certificate to a user entry.
+property.user-base-dn.default-behavior.alias.synopsis=The server will perform the search in all public naming contexts.
diff --git a/opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_zh_TW.properties b/opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..86a7f21
--- /dev/null
+++ b/opends/src/admin/messages/SubjectAttributeToUserAttributeCertificateMapperCfgDefn_zh_TW.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Subject Attribute To User Attribute Certificate Mapper
+user-friendly-plural-name=Subject Attribute To User Attribute Certificate Mappers
+synopsis=The Subject Attribute To User Attribute Certificate Mapper maps client certificates to user entries by mapping the values of attributes contained in the certificate subject to attributes contained in user entries.
+property.enabled.synopsis=Indicates whether the Subject Attribute To User Attribute Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Subject Attribute To User Attribute Certificate Mapper implementation.
+property.subject-attribute-mapping.synopsis=Specifies a mapping between certificate attributes and user attributes.
+property.subject-attribute-mapping.description=Each value should be in the form "certattr:userattr" where certattr is the name of the attribute in the certificate subject and userattr is the name of the corresponding attribute in user entries. There may be multiple mappings defined, and when performing the mapping values for all attributes present in the certificate subject that have mappings defined must be present in the corresponding user entries.
+property.user-base-dn.synopsis=Specifies the base DNs that should be used when performing searches to map the client certificate to a user entry.
+property.user-base-dn.default-behavior.alias.synopsis=The server will perform the search in all public naming contexts.
diff --git a/opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn.properties b/opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn.properties
new file mode 100644
index 0000000..3dafc7c
--- /dev/null
+++ b/opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Subject DN To User Attribute Certificate Mapper
+user-friendly-plural-name=Subject DN To User Attribute Certificate Mappers
+synopsis=The Subject DN To User Attribute Certificate Mapper maps client certificates to user entries by looking for the certificate subject DN in a specified attribute of user entries.
+property.enabled.synopsis=Indicates whether the Subject DN To User Attribute Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Subject DN To User Attribute Certificate Mapper implementation.
+property.subject-attribute.synopsis=Specifies the name or OID of the attribute whose value should exactly match the certificate subject DN.
+property.user-base-dn.synopsis=Specifies the base DNs that should be used when performing searches to map the client certificate to a user entry.
+property.user-base-dn.default-behavior.alias.synopsis=The server will perform the search in all public naming contexts.
diff --git a/opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_de.properties b/opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_de.properties
new file mode 100644
index 0000000..3dafc7c
--- /dev/null
+++ b/opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_de.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Subject DN To User Attribute Certificate Mapper
+user-friendly-plural-name=Subject DN To User Attribute Certificate Mappers
+synopsis=The Subject DN To User Attribute Certificate Mapper maps client certificates to user entries by looking for the certificate subject DN in a specified attribute of user entries.
+property.enabled.synopsis=Indicates whether the Subject DN To User Attribute Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Subject DN To User Attribute Certificate Mapper implementation.
+property.subject-attribute.synopsis=Specifies the name or OID of the attribute whose value should exactly match the certificate subject DN.
+property.user-base-dn.synopsis=Specifies the base DNs that should be used when performing searches to map the client certificate to a user entry.
+property.user-base-dn.default-behavior.alias.synopsis=The server will perform the search in all public naming contexts.
diff --git a/opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_es.properties b/opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_es.properties
new file mode 100644
index 0000000..3dafc7c
--- /dev/null
+++ b/opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_es.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Subject DN To User Attribute Certificate Mapper
+user-friendly-plural-name=Subject DN To User Attribute Certificate Mappers
+synopsis=The Subject DN To User Attribute Certificate Mapper maps client certificates to user entries by looking for the certificate subject DN in a specified attribute of user entries.
+property.enabled.synopsis=Indicates whether the Subject DN To User Attribute Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Subject DN To User Attribute Certificate Mapper implementation.
+property.subject-attribute.synopsis=Specifies the name or OID of the attribute whose value should exactly match the certificate subject DN.
+property.user-base-dn.synopsis=Specifies the base DNs that should be used when performing searches to map the client certificate to a user entry.
+property.user-base-dn.default-behavior.alias.synopsis=The server will perform the search in all public naming contexts.
diff --git a/opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_fr.properties b/opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_fr.properties
new file mode 100644
index 0000000..3dafc7c
--- /dev/null
+++ b/opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_fr.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Subject DN To User Attribute Certificate Mapper
+user-friendly-plural-name=Subject DN To User Attribute Certificate Mappers
+synopsis=The Subject DN To User Attribute Certificate Mapper maps client certificates to user entries by looking for the certificate subject DN in a specified attribute of user entries.
+property.enabled.synopsis=Indicates whether the Subject DN To User Attribute Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Subject DN To User Attribute Certificate Mapper implementation.
+property.subject-attribute.synopsis=Specifies the name or OID of the attribute whose value should exactly match the certificate subject DN.
+property.user-base-dn.synopsis=Specifies the base DNs that should be used when performing searches to map the client certificate to a user entry.
+property.user-base-dn.default-behavior.alias.synopsis=The server will perform the search in all public naming contexts.
diff --git a/opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_ja.properties b/opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_ja.properties
new file mode 100644
index 0000000..3dafc7c
--- /dev/null
+++ b/opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_ja.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Subject DN To User Attribute Certificate Mapper
+user-friendly-plural-name=Subject DN To User Attribute Certificate Mappers
+synopsis=The Subject DN To User Attribute Certificate Mapper maps client certificates to user entries by looking for the certificate subject DN in a specified attribute of user entries.
+property.enabled.synopsis=Indicates whether the Subject DN To User Attribute Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Subject DN To User Attribute Certificate Mapper implementation.
+property.subject-attribute.synopsis=Specifies the name or OID of the attribute whose value should exactly match the certificate subject DN.
+property.user-base-dn.synopsis=Specifies the base DNs that should be used when performing searches to map the client certificate to a user entry.
+property.user-base-dn.default-behavior.alias.synopsis=The server will perform the search in all public naming contexts.
diff --git a/opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_ko.properties b/opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_ko.properties
new file mode 100644
index 0000000..3dafc7c
--- /dev/null
+++ b/opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_ko.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Subject DN To User Attribute Certificate Mapper
+user-friendly-plural-name=Subject DN To User Attribute Certificate Mappers
+synopsis=The Subject DN To User Attribute Certificate Mapper maps client certificates to user entries by looking for the certificate subject DN in a specified attribute of user entries.
+property.enabled.synopsis=Indicates whether the Subject DN To User Attribute Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Subject DN To User Attribute Certificate Mapper implementation.
+property.subject-attribute.synopsis=Specifies the name or OID of the attribute whose value should exactly match the certificate subject DN.
+property.user-base-dn.synopsis=Specifies the base DNs that should be used when performing searches to map the client certificate to a user entry.
+property.user-base-dn.default-behavior.alias.synopsis=The server will perform the search in all public naming contexts.
diff --git a/opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_zh_CN.properties b/opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..3dafc7c
--- /dev/null
+++ b/opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_zh_CN.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Subject DN To User Attribute Certificate Mapper
+user-friendly-plural-name=Subject DN To User Attribute Certificate Mappers
+synopsis=The Subject DN To User Attribute Certificate Mapper maps client certificates to user entries by looking for the certificate subject DN in a specified attribute of user entries.
+property.enabled.synopsis=Indicates whether the Subject DN To User Attribute Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Subject DN To User Attribute Certificate Mapper implementation.
+property.subject-attribute.synopsis=Specifies the name or OID of the attribute whose value should exactly match the certificate subject DN.
+property.user-base-dn.synopsis=Specifies the base DNs that should be used when performing searches to map the client certificate to a user entry.
+property.user-base-dn.default-behavior.alias.synopsis=The server will perform the search in all public naming contexts.
diff --git a/opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_zh_TW.properties b/opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..3dafc7c
--- /dev/null
+++ b/opends/src/admin/messages/SubjectDNToUserAttributeCertificateMapperCfgDefn_zh_TW.properties
@@ -0,0 +1,8 @@
+user-friendly-name=Subject DN To User Attribute Certificate Mapper
+user-friendly-plural-name=Subject DN To User Attribute Certificate Mappers
+synopsis=The Subject DN To User Attribute Certificate Mapper maps client certificates to user entries by looking for the certificate subject DN in a specified attribute of user entries.
+property.enabled.synopsis=Indicates whether the Subject DN To User Attribute Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Subject DN To User Attribute Certificate Mapper implementation.
+property.subject-attribute.synopsis=Specifies the name or OID of the attribute whose value should exactly match the certificate subject DN.
+property.user-base-dn.synopsis=Specifies the base DNs that should be used when performing searches to map the client certificate to a user entry.
+property.user-base-dn.default-behavior.alias.synopsis=The server will perform the search in all public naming contexts.
diff --git a/opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn.properties b/opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn.properties
new file mode 100644
index 0000000..e5d6cf7
--- /dev/null
+++ b/opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Subject Equals DN Certificate Mapper
+user-friendly-plural-name=Subject Equals DN Certificate Mappers
+synopsis=The Subject Equals DN Certificate Mapper maps client certificates to user entries based on the assumption that the certificate subject is the same as the DN of the target user entry.
+property.enabled.synopsis=Indicates whether the Subject Equals DN Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Subject Equals DN Certificate Mapper implementation.
diff --git a/opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_de.properties b/opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_de.properties
new file mode 100644
index 0000000..e5d6cf7
--- /dev/null
+++ b/opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_de.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Subject Equals DN Certificate Mapper
+user-friendly-plural-name=Subject Equals DN Certificate Mappers
+synopsis=The Subject Equals DN Certificate Mapper maps client certificates to user entries based on the assumption that the certificate subject is the same as the DN of the target user entry.
+property.enabled.synopsis=Indicates whether the Subject Equals DN Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Subject Equals DN Certificate Mapper implementation.
diff --git a/opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_es.properties b/opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_es.properties
new file mode 100644
index 0000000..e5d6cf7
--- /dev/null
+++ b/opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_es.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Subject Equals DN Certificate Mapper
+user-friendly-plural-name=Subject Equals DN Certificate Mappers
+synopsis=The Subject Equals DN Certificate Mapper maps client certificates to user entries based on the assumption that the certificate subject is the same as the DN of the target user entry.
+property.enabled.synopsis=Indicates whether the Subject Equals DN Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Subject Equals DN Certificate Mapper implementation.
diff --git a/opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_fr.properties b/opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_fr.properties
new file mode 100644
index 0000000..e5d6cf7
--- /dev/null
+++ b/opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_fr.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Subject Equals DN Certificate Mapper
+user-friendly-plural-name=Subject Equals DN Certificate Mappers
+synopsis=The Subject Equals DN Certificate Mapper maps client certificates to user entries based on the assumption that the certificate subject is the same as the DN of the target user entry.
+property.enabled.synopsis=Indicates whether the Subject Equals DN Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Subject Equals DN Certificate Mapper implementation.
diff --git a/opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_ja.properties b/opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_ja.properties
new file mode 100644
index 0000000..e5d6cf7
--- /dev/null
+++ b/opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_ja.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Subject Equals DN Certificate Mapper
+user-friendly-plural-name=Subject Equals DN Certificate Mappers
+synopsis=The Subject Equals DN Certificate Mapper maps client certificates to user entries based on the assumption that the certificate subject is the same as the DN of the target user entry.
+property.enabled.synopsis=Indicates whether the Subject Equals DN Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Subject Equals DN Certificate Mapper implementation.
diff --git a/opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_ko.properties b/opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_ko.properties
new file mode 100644
index 0000000..e5d6cf7
--- /dev/null
+++ b/opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_ko.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Subject Equals DN Certificate Mapper
+user-friendly-plural-name=Subject Equals DN Certificate Mappers
+synopsis=The Subject Equals DN Certificate Mapper maps client certificates to user entries based on the assumption that the certificate subject is the same as the DN of the target user entry.
+property.enabled.synopsis=Indicates whether the Subject Equals DN Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Subject Equals DN Certificate Mapper implementation.
diff --git a/opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_zh_CN.properties b/opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..e5d6cf7
--- /dev/null
+++ b/opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_zh_CN.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Subject Equals DN Certificate Mapper
+user-friendly-plural-name=Subject Equals DN Certificate Mappers
+synopsis=The Subject Equals DN Certificate Mapper maps client certificates to user entries based on the assumption that the certificate subject is the same as the DN of the target user entry.
+property.enabled.synopsis=Indicates whether the Subject Equals DN Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Subject Equals DN Certificate Mapper implementation.
diff --git a/opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_zh_TW.properties b/opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..e5d6cf7
--- /dev/null
+++ b/opends/src/admin/messages/SubjectEqualsDNCertificateMapperCfgDefn_zh_TW.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Subject Equals DN Certificate Mapper
+user-friendly-plural-name=Subject Equals DN Certificate Mappers
+synopsis=The Subject Equals DN Certificate Mapper maps client certificates to user entries based on the assumption that the certificate subject is the same as the DN of the target user entry.
+property.enabled.synopsis=Indicates whether the Subject Equals DN Certificate Mapper is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Subject Equals DN Certificate Mapper implementation.
diff --git a/opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn.properties b/opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn.properties
new file mode 100644
index 0000000..33bb187
--- /dev/null
+++ b/opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Subschema Subentry Virtual Attribute
+user-friendly-plural-name=Subschema Subentry Virtual Attributes
+synopsis=The Subschema Subentry Virtual Attribute generates a virtual attribute that specifies the location of the subschemaSubentry with the schema definitions in effect for the entry. This attribute is defined in RFC 4512.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Subschema Subentry Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_de.properties b/opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_de.properties
new file mode 100644
index 0000000..33bb187
--- /dev/null
+++ b/opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_de.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Subschema Subentry Virtual Attribute
+user-friendly-plural-name=Subschema Subentry Virtual Attributes
+synopsis=The Subschema Subentry Virtual Attribute generates a virtual attribute that specifies the location of the subschemaSubentry with the schema definitions in effect for the entry. This attribute is defined in RFC 4512.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Subschema Subentry Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_es.properties b/opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_es.properties
new file mode 100644
index 0000000..33bb187
--- /dev/null
+++ b/opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_es.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Subschema Subentry Virtual Attribute
+user-friendly-plural-name=Subschema Subentry Virtual Attributes
+synopsis=The Subschema Subentry Virtual Attribute generates a virtual attribute that specifies the location of the subschemaSubentry with the schema definitions in effect for the entry. This attribute is defined in RFC 4512.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Subschema Subentry Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_fr.properties b/opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_fr.properties
new file mode 100644
index 0000000..33bb187
--- /dev/null
+++ b/opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_fr.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Subschema Subentry Virtual Attribute
+user-friendly-plural-name=Subschema Subentry Virtual Attributes
+synopsis=The Subschema Subentry Virtual Attribute generates a virtual attribute that specifies the location of the subschemaSubentry with the schema definitions in effect for the entry. This attribute is defined in RFC 4512.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Subschema Subentry Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_ja.properties b/opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_ja.properties
new file mode 100644
index 0000000..33bb187
--- /dev/null
+++ b/opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_ja.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Subschema Subentry Virtual Attribute
+user-friendly-plural-name=Subschema Subentry Virtual Attributes
+synopsis=The Subschema Subentry Virtual Attribute generates a virtual attribute that specifies the location of the subschemaSubentry with the schema definitions in effect for the entry. This attribute is defined in RFC 4512.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Subschema Subentry Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_ko.properties b/opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_ko.properties
new file mode 100644
index 0000000..33bb187
--- /dev/null
+++ b/opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_ko.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Subschema Subentry Virtual Attribute
+user-friendly-plural-name=Subschema Subentry Virtual Attributes
+synopsis=The Subschema Subentry Virtual Attribute generates a virtual attribute that specifies the location of the subschemaSubentry with the schema definitions in effect for the entry. This attribute is defined in RFC 4512.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Subschema Subentry Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_zh_CN.properties b/opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..33bb187
--- /dev/null
+++ b/opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_zh_CN.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Subschema Subentry Virtual Attribute
+user-friendly-plural-name=Subschema Subentry Virtual Attributes
+synopsis=The Subschema Subentry Virtual Attribute generates a virtual attribute that specifies the location of the subschemaSubentry with the schema definitions in effect for the entry. This attribute is defined in RFC 4512.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Subschema Subentry Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_zh_TW.properties b/opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..33bb187
--- /dev/null
+++ b/opends/src/admin/messages/SubschemaSubentryVirtualAttributeCfgDefn_zh_TW.properties
@@ -0,0 +1,19 @@
+user-friendly-name=Subschema Subentry Virtual Attribute
+user-friendly-plural-name=Subschema Subentry Virtual Attributes
+synopsis=The Subschema Subentry Virtual Attribute generates a virtual attribute that specifies the location of the subschemaSubentry with the schema definitions in effect for the entry. This attribute is defined in RFC 4512.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Subschema Subentry Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/SubstringMatchingRuleCfgDefn.properties b/opends/src/admin/messages/SubstringMatchingRuleCfgDefn.properties
new file mode 100644
index 0000000..6ed8a15
--- /dev/null
+++ b/opends/src/admin/messages/SubstringMatchingRuleCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Substring Matching Rule
+user-friendly-plural-name=Substring Matching Rules
+synopsis=Substring Matching Rules define a set of rules for performing substring matching operations against assertion values.
+description=Substring matching can be used to perform partial matching with attribute values.
+property.enabled.synopsis=Indicates whether the Substring Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Substring Matching Rule implementation.
diff --git a/opends/src/admin/messages/SubstringMatchingRuleCfgDefn_de.properties b/opends/src/admin/messages/SubstringMatchingRuleCfgDefn_de.properties
new file mode 100644
index 0000000..6ed8a15
--- /dev/null
+++ b/opends/src/admin/messages/SubstringMatchingRuleCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Substring Matching Rule
+user-friendly-plural-name=Substring Matching Rules
+synopsis=Substring Matching Rules define a set of rules for performing substring matching operations against assertion values.
+description=Substring matching can be used to perform partial matching with attribute values.
+property.enabled.synopsis=Indicates whether the Substring Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Substring Matching Rule implementation.
diff --git a/opends/src/admin/messages/SubstringMatchingRuleCfgDefn_es.properties b/opends/src/admin/messages/SubstringMatchingRuleCfgDefn_es.properties
new file mode 100644
index 0000000..6ed8a15
--- /dev/null
+++ b/opends/src/admin/messages/SubstringMatchingRuleCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Substring Matching Rule
+user-friendly-plural-name=Substring Matching Rules
+synopsis=Substring Matching Rules define a set of rules for performing substring matching operations against assertion values.
+description=Substring matching can be used to perform partial matching with attribute values.
+property.enabled.synopsis=Indicates whether the Substring Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Substring Matching Rule implementation.
diff --git a/opends/src/admin/messages/SubstringMatchingRuleCfgDefn_fr.properties b/opends/src/admin/messages/SubstringMatchingRuleCfgDefn_fr.properties
new file mode 100644
index 0000000..6ed8a15
--- /dev/null
+++ b/opends/src/admin/messages/SubstringMatchingRuleCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Substring Matching Rule
+user-friendly-plural-name=Substring Matching Rules
+synopsis=Substring Matching Rules define a set of rules for performing substring matching operations against assertion values.
+description=Substring matching can be used to perform partial matching with attribute values.
+property.enabled.synopsis=Indicates whether the Substring Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Substring Matching Rule implementation.
diff --git a/opends/src/admin/messages/SubstringMatchingRuleCfgDefn_ja.properties b/opends/src/admin/messages/SubstringMatchingRuleCfgDefn_ja.properties
new file mode 100644
index 0000000..6ed8a15
--- /dev/null
+++ b/opends/src/admin/messages/SubstringMatchingRuleCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Substring Matching Rule
+user-friendly-plural-name=Substring Matching Rules
+synopsis=Substring Matching Rules define a set of rules for performing substring matching operations against assertion values.
+description=Substring matching can be used to perform partial matching with attribute values.
+property.enabled.synopsis=Indicates whether the Substring Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Substring Matching Rule implementation.
diff --git a/opends/src/admin/messages/SubstringMatchingRuleCfgDefn_ko.properties b/opends/src/admin/messages/SubstringMatchingRuleCfgDefn_ko.properties
new file mode 100644
index 0000000..6ed8a15
--- /dev/null
+++ b/opends/src/admin/messages/SubstringMatchingRuleCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Substring Matching Rule
+user-friendly-plural-name=Substring Matching Rules
+synopsis=Substring Matching Rules define a set of rules for performing substring matching operations against assertion values.
+description=Substring matching can be used to perform partial matching with attribute values.
+property.enabled.synopsis=Indicates whether the Substring Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Substring Matching Rule implementation.
diff --git a/opends/src/admin/messages/SubstringMatchingRuleCfgDefn_zh_CN.properties b/opends/src/admin/messages/SubstringMatchingRuleCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..6ed8a15
--- /dev/null
+++ b/opends/src/admin/messages/SubstringMatchingRuleCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Substring Matching Rule
+user-friendly-plural-name=Substring Matching Rules
+synopsis=Substring Matching Rules define a set of rules for performing substring matching operations against assertion values.
+description=Substring matching can be used to perform partial matching with attribute values.
+property.enabled.synopsis=Indicates whether the Substring Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Substring Matching Rule implementation.
diff --git a/opends/src/admin/messages/SubstringMatchingRuleCfgDefn_zh_TW.properties b/opends/src/admin/messages/SubstringMatchingRuleCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..6ed8a15
--- /dev/null
+++ b/opends/src/admin/messages/SubstringMatchingRuleCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Substring Matching Rule
+user-friendly-plural-name=Substring Matching Rules
+synopsis=Substring Matching Rules define a set of rules for performing substring matching operations against assertion values.
+description=Substring matching can be used to perform partial matching with attribute values.
+property.enabled.synopsis=Indicates whether the Substring Matching Rule is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Substring Matching Rule implementation.
diff --git a/opends/src/admin/messages/SynchronizationProviderCfgDefn.properties b/opends/src/admin/messages/SynchronizationProviderCfgDefn.properties
new file mode 100644
index 0000000..9d8a80d
--- /dev/null
+++ b/opends/src/admin/messages/SynchronizationProviderCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Synchronization Provider
+user-friendly-plural-name=Synchronization Providers
+synopsis=Synchronization Providers are responsible for handling synchronization of the Directory Server data with other OpenDS instances or other data repositories.
+description=The OpenDS Directory Server takes a centralized approach to replication, rather than the point-to-point approach taken by Sun Java System Directory Server. In OpenDS, one or more replication servers are created in the environment. The replication servers typically do not store user data but keep a log of all changes made within the topology. Each Directory Server instance in the topology is pointed at the replication servers. This plan simplifies the deployment and management of the environment. Although you can run the replication server on the same system (or even in the same instance) as the Directory Server, the two servers can be separated onto different systems. This approach can provide better performance or functionality in large environments.
+property.enabled.synopsis=Indicates whether the Synchronization Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Synchronization Provider implementation.
diff --git a/opends/src/admin/messages/SynchronizationProviderCfgDefn_de.properties b/opends/src/admin/messages/SynchronizationProviderCfgDefn_de.properties
new file mode 100644
index 0000000..9d8a80d
--- /dev/null
+++ b/opends/src/admin/messages/SynchronizationProviderCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Synchronization Provider
+user-friendly-plural-name=Synchronization Providers
+synopsis=Synchronization Providers are responsible for handling synchronization of the Directory Server data with other OpenDS instances or other data repositories.
+description=The OpenDS Directory Server takes a centralized approach to replication, rather than the point-to-point approach taken by Sun Java System Directory Server. In OpenDS, one or more replication servers are created in the environment. The replication servers typically do not store user data but keep a log of all changes made within the topology. Each Directory Server instance in the topology is pointed at the replication servers. This plan simplifies the deployment and management of the environment. Although you can run the replication server on the same system (or even in the same instance) as the Directory Server, the two servers can be separated onto different systems. This approach can provide better performance or functionality in large environments.
+property.enabled.synopsis=Indicates whether the Synchronization Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Synchronization Provider implementation.
diff --git a/opends/src/admin/messages/SynchronizationProviderCfgDefn_es.properties b/opends/src/admin/messages/SynchronizationProviderCfgDefn_es.properties
new file mode 100644
index 0000000..9d8a80d
--- /dev/null
+++ b/opends/src/admin/messages/SynchronizationProviderCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Synchronization Provider
+user-friendly-plural-name=Synchronization Providers
+synopsis=Synchronization Providers are responsible for handling synchronization of the Directory Server data with other OpenDS instances or other data repositories.
+description=The OpenDS Directory Server takes a centralized approach to replication, rather than the point-to-point approach taken by Sun Java System Directory Server. In OpenDS, one or more replication servers are created in the environment. The replication servers typically do not store user data but keep a log of all changes made within the topology. Each Directory Server instance in the topology is pointed at the replication servers. This plan simplifies the deployment and management of the environment. Although you can run the replication server on the same system (or even in the same instance) as the Directory Server, the two servers can be separated onto different systems. This approach can provide better performance or functionality in large environments.
+property.enabled.synopsis=Indicates whether the Synchronization Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Synchronization Provider implementation.
diff --git a/opends/src/admin/messages/SynchronizationProviderCfgDefn_fr.properties b/opends/src/admin/messages/SynchronizationProviderCfgDefn_fr.properties
new file mode 100644
index 0000000..9d8a80d
--- /dev/null
+++ b/opends/src/admin/messages/SynchronizationProviderCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Synchronization Provider
+user-friendly-plural-name=Synchronization Providers
+synopsis=Synchronization Providers are responsible for handling synchronization of the Directory Server data with other OpenDS instances or other data repositories.
+description=The OpenDS Directory Server takes a centralized approach to replication, rather than the point-to-point approach taken by Sun Java System Directory Server. In OpenDS, one or more replication servers are created in the environment. The replication servers typically do not store user data but keep a log of all changes made within the topology. Each Directory Server instance in the topology is pointed at the replication servers. This plan simplifies the deployment and management of the environment. Although you can run the replication server on the same system (or even in the same instance) as the Directory Server, the two servers can be separated onto different systems. This approach can provide better performance or functionality in large environments.
+property.enabled.synopsis=Indicates whether the Synchronization Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Synchronization Provider implementation.
diff --git a/opends/src/admin/messages/SynchronizationProviderCfgDefn_ja.properties b/opends/src/admin/messages/SynchronizationProviderCfgDefn_ja.properties
new file mode 100644
index 0000000..9d8a80d
--- /dev/null
+++ b/opends/src/admin/messages/SynchronizationProviderCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Synchronization Provider
+user-friendly-plural-name=Synchronization Providers
+synopsis=Synchronization Providers are responsible for handling synchronization of the Directory Server data with other OpenDS instances or other data repositories.
+description=The OpenDS Directory Server takes a centralized approach to replication, rather than the point-to-point approach taken by Sun Java System Directory Server. In OpenDS, one or more replication servers are created in the environment. The replication servers typically do not store user data but keep a log of all changes made within the topology. Each Directory Server instance in the topology is pointed at the replication servers. This plan simplifies the deployment and management of the environment. Although you can run the replication server on the same system (or even in the same instance) as the Directory Server, the two servers can be separated onto different systems. This approach can provide better performance or functionality in large environments.
+property.enabled.synopsis=Indicates whether the Synchronization Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Synchronization Provider implementation.
diff --git a/opends/src/admin/messages/SynchronizationProviderCfgDefn_ko.properties b/opends/src/admin/messages/SynchronizationProviderCfgDefn_ko.properties
new file mode 100644
index 0000000..9d8a80d
--- /dev/null
+++ b/opends/src/admin/messages/SynchronizationProviderCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Synchronization Provider
+user-friendly-plural-name=Synchronization Providers
+synopsis=Synchronization Providers are responsible for handling synchronization of the Directory Server data with other OpenDS instances or other data repositories.
+description=The OpenDS Directory Server takes a centralized approach to replication, rather than the point-to-point approach taken by Sun Java System Directory Server. In OpenDS, one or more replication servers are created in the environment. The replication servers typically do not store user data but keep a log of all changes made within the topology. Each Directory Server instance in the topology is pointed at the replication servers. This plan simplifies the deployment and management of the environment. Although you can run the replication server on the same system (or even in the same instance) as the Directory Server, the two servers can be separated onto different systems. This approach can provide better performance or functionality in large environments.
+property.enabled.synopsis=Indicates whether the Synchronization Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Synchronization Provider implementation.
diff --git a/opends/src/admin/messages/SynchronizationProviderCfgDefn_zh_CN.properties b/opends/src/admin/messages/SynchronizationProviderCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..9d8a80d
--- /dev/null
+++ b/opends/src/admin/messages/SynchronizationProviderCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Synchronization Provider
+user-friendly-plural-name=Synchronization Providers
+synopsis=Synchronization Providers are responsible for handling synchronization of the Directory Server data with other OpenDS instances or other data repositories.
+description=The OpenDS Directory Server takes a centralized approach to replication, rather than the point-to-point approach taken by Sun Java System Directory Server. In OpenDS, one or more replication servers are created in the environment. The replication servers typically do not store user data but keep a log of all changes made within the topology. Each Directory Server instance in the topology is pointed at the replication servers. This plan simplifies the deployment and management of the environment. Although you can run the replication server on the same system (or even in the same instance) as the Directory Server, the two servers can be separated onto different systems. This approach can provide better performance or functionality in large environments.
+property.enabled.synopsis=Indicates whether the Synchronization Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Synchronization Provider implementation.
diff --git a/opends/src/admin/messages/SynchronizationProviderCfgDefn_zh_TW.properties b/opends/src/admin/messages/SynchronizationProviderCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..9d8a80d
--- /dev/null
+++ b/opends/src/admin/messages/SynchronizationProviderCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Synchronization Provider
+user-friendly-plural-name=Synchronization Providers
+synopsis=Synchronization Providers are responsible for handling synchronization of the Directory Server data with other OpenDS instances or other data repositories.
+description=The OpenDS Directory Server takes a centralized approach to replication, rather than the point-to-point approach taken by Sun Java System Directory Server. In OpenDS, one or more replication servers are created in the environment. The replication servers typically do not store user data but keep a log of all changes made within the topology. Each Directory Server instance in the topology is pointed at the replication servers. This plan simplifies the deployment and management of the environment. Although you can run the replication server on the same system (or even in the same instance) as the Directory Server, the two servers can be separated onto different systems. This approach can provide better performance or functionality in large environments.
+property.enabled.synopsis=Indicates whether the Synchronization Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Synchronization Provider implementation.
diff --git a/opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn.properties b/opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn.properties
new file mode 100644
index 0000000..3262882
--- /dev/null
+++ b/opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn.properties
@@ -0,0 +1,5 @@
+user-friendly-name=System Info Monitor Provider
+user-friendly-plural-name=System Info Monitor Providers
+synopsis=The System Info Monitor Provider can be used to publish information about the system and virtual machine on which the Directory Server is running.
+property.enabled.synopsis=Indicates whether the System Info Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the System Info Monitor Provider implementation.
diff --git a/opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_de.properties b/opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_de.properties
new file mode 100644
index 0000000..3262882
--- /dev/null
+++ b/opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_de.properties
@@ -0,0 +1,5 @@
+user-friendly-name=System Info Monitor Provider
+user-friendly-plural-name=System Info Monitor Providers
+synopsis=The System Info Monitor Provider can be used to publish information about the system and virtual machine on which the Directory Server is running.
+property.enabled.synopsis=Indicates whether the System Info Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the System Info Monitor Provider implementation.
diff --git a/opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_es.properties b/opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_es.properties
new file mode 100644
index 0000000..3262882
--- /dev/null
+++ b/opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_es.properties
@@ -0,0 +1,5 @@
+user-friendly-name=System Info Monitor Provider
+user-friendly-plural-name=System Info Monitor Providers
+synopsis=The System Info Monitor Provider can be used to publish information about the system and virtual machine on which the Directory Server is running.
+property.enabled.synopsis=Indicates whether the System Info Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the System Info Monitor Provider implementation.
diff --git a/opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_fr.properties b/opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_fr.properties
new file mode 100644
index 0000000..3262882
--- /dev/null
+++ b/opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_fr.properties
@@ -0,0 +1,5 @@
+user-friendly-name=System Info Monitor Provider
+user-friendly-plural-name=System Info Monitor Providers
+synopsis=The System Info Monitor Provider can be used to publish information about the system and virtual machine on which the Directory Server is running.
+property.enabled.synopsis=Indicates whether the System Info Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the System Info Monitor Provider implementation.
diff --git a/opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_ja.properties b/opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_ja.properties
new file mode 100644
index 0000000..3262882
--- /dev/null
+++ b/opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_ja.properties
@@ -0,0 +1,5 @@
+user-friendly-name=System Info Monitor Provider
+user-friendly-plural-name=System Info Monitor Providers
+synopsis=The System Info Monitor Provider can be used to publish information about the system and virtual machine on which the Directory Server is running.
+property.enabled.synopsis=Indicates whether the System Info Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the System Info Monitor Provider implementation.
diff --git a/opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_ko.properties b/opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_ko.properties
new file mode 100644
index 0000000..3262882
--- /dev/null
+++ b/opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_ko.properties
@@ -0,0 +1,5 @@
+user-friendly-name=System Info Monitor Provider
+user-friendly-plural-name=System Info Monitor Providers
+synopsis=The System Info Monitor Provider can be used to publish information about the system and virtual machine on which the Directory Server is running.
+property.enabled.synopsis=Indicates whether the System Info Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the System Info Monitor Provider implementation.
diff --git a/opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_zh_CN.properties b/opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..3262882
--- /dev/null
+++ b/opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_zh_CN.properties
@@ -0,0 +1,5 @@
+user-friendly-name=System Info Monitor Provider
+user-friendly-plural-name=System Info Monitor Providers
+synopsis=The System Info Monitor Provider can be used to publish information about the system and virtual machine on which the Directory Server is running.
+property.enabled.synopsis=Indicates whether the System Info Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the System Info Monitor Provider implementation.
diff --git a/opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_zh_TW.properties b/opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..3262882
--- /dev/null
+++ b/opends/src/admin/messages/SystemInfoMonitorProviderCfgDefn_zh_TW.properties
@@ -0,0 +1,5 @@
+user-friendly-name=System Info Monitor Provider
+user-friendly-plural-name=System Info Monitor Providers
+synopsis=The System Info Monitor Provider can be used to publish information about the system and virtual machine on which the Directory Server is running.
+property.enabled.synopsis=Indicates whether the System Info Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the System Info Monitor Provider implementation.
diff --git a/opends/src/admin/messages/TaskBackendCfgDefn.properties b/opends/src/admin/messages/TaskBackendCfgDefn.properties
new file mode 100644
index 0000000..6ba97a2
--- /dev/null
+++ b/opends/src/admin/messages/TaskBackendCfgDefn.properties
@@ -0,0 +1,21 @@
+user-friendly-name=Task Backend
+user-friendly-plural-name=Task Backends
+synopsis=The Task Backend provides a mechanism for scheduling tasks in the OpenDS Directory Server. Tasks are intended to provide access to certain types of administrative functions in the server that may not be convenient to perform remotely.
+description=OpenDS supports tasks to backup and restore backends, to import and export LDIF files, and to stop and restart the server. The details of a task are in an entry that is below the root of the Task Backend. The Task Backend is responsible for decoding that task entry and ensuring that it is processed as requested. Tasks may be invoked immediately, but they may also be scheduled for execution at some future time. The task backend can also process recurring tasks to ensure that maintenance operations (for example, backups) are performed automatically on a regular basis.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.notification-sender-address.synopsis=Specifies the email address to use as the sender (that is, the "From:" address) address for notification mail messages generated when a task completes execution.
+property.notification-sender-address.default-behavior.alias.synopsis=The default sender address used is "opends-task-notification@" followed by the canonical address of the system on which the server is running.
+property.task-backing-file.synopsis=Specifies the path to the backing file for storing information about the tasks configured in the server.
+property.task-backing-file.description=It may be either an absolute path or a relative path to the base of the OpenDS Directory Server instance.
+property.task-retention-time.synopsis=Specifies the length of time that task entries should be retained after processing on the associated task has been completed.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/TaskBackendCfgDefn_de.properties b/opends/src/admin/messages/TaskBackendCfgDefn_de.properties
new file mode 100644
index 0000000..6ba97a2
--- /dev/null
+++ b/opends/src/admin/messages/TaskBackendCfgDefn_de.properties
@@ -0,0 +1,21 @@
+user-friendly-name=Task Backend
+user-friendly-plural-name=Task Backends
+synopsis=The Task Backend provides a mechanism for scheduling tasks in the OpenDS Directory Server. Tasks are intended to provide access to certain types of administrative functions in the server that may not be convenient to perform remotely.
+description=OpenDS supports tasks to backup and restore backends, to import and export LDIF files, and to stop and restart the server. The details of a task are in an entry that is below the root of the Task Backend. The Task Backend is responsible for decoding that task entry and ensuring that it is processed as requested. Tasks may be invoked immediately, but they may also be scheduled for execution at some future time. The task backend can also process recurring tasks to ensure that maintenance operations (for example, backups) are performed automatically on a regular basis.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.notification-sender-address.synopsis=Specifies the email address to use as the sender (that is, the "From:" address) address for notification mail messages generated when a task completes execution.
+property.notification-sender-address.default-behavior.alias.synopsis=The default sender address used is "opends-task-notification@" followed by the canonical address of the system on which the server is running.
+property.task-backing-file.synopsis=Specifies the path to the backing file for storing information about the tasks configured in the server.
+property.task-backing-file.description=It may be either an absolute path or a relative path to the base of the OpenDS Directory Server instance.
+property.task-retention-time.synopsis=Specifies the length of time that task entries should be retained after processing on the associated task has been completed.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/TaskBackendCfgDefn_es.properties b/opends/src/admin/messages/TaskBackendCfgDefn_es.properties
new file mode 100644
index 0000000..6ba97a2
--- /dev/null
+++ b/opends/src/admin/messages/TaskBackendCfgDefn_es.properties
@@ -0,0 +1,21 @@
+user-friendly-name=Task Backend
+user-friendly-plural-name=Task Backends
+synopsis=The Task Backend provides a mechanism for scheduling tasks in the OpenDS Directory Server. Tasks are intended to provide access to certain types of administrative functions in the server that may not be convenient to perform remotely.
+description=OpenDS supports tasks to backup and restore backends, to import and export LDIF files, and to stop and restart the server. The details of a task are in an entry that is below the root of the Task Backend. The Task Backend is responsible for decoding that task entry and ensuring that it is processed as requested. Tasks may be invoked immediately, but they may also be scheduled for execution at some future time. The task backend can also process recurring tasks to ensure that maintenance operations (for example, backups) are performed automatically on a regular basis.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.notification-sender-address.synopsis=Specifies the email address to use as the sender (that is, the "From:" address) address for notification mail messages generated when a task completes execution.
+property.notification-sender-address.default-behavior.alias.synopsis=The default sender address used is "opends-task-notification@" followed by the canonical address of the system on which the server is running.
+property.task-backing-file.synopsis=Specifies the path to the backing file for storing information about the tasks configured in the server.
+property.task-backing-file.description=It may be either an absolute path or a relative path to the base of the OpenDS Directory Server instance.
+property.task-retention-time.synopsis=Specifies the length of time that task entries should be retained after processing on the associated task has been completed.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/TaskBackendCfgDefn_fr.properties b/opends/src/admin/messages/TaskBackendCfgDefn_fr.properties
new file mode 100644
index 0000000..6ba97a2
--- /dev/null
+++ b/opends/src/admin/messages/TaskBackendCfgDefn_fr.properties
@@ -0,0 +1,21 @@
+user-friendly-name=Task Backend
+user-friendly-plural-name=Task Backends
+synopsis=The Task Backend provides a mechanism for scheduling tasks in the OpenDS Directory Server. Tasks are intended to provide access to certain types of administrative functions in the server that may not be convenient to perform remotely.
+description=OpenDS supports tasks to backup and restore backends, to import and export LDIF files, and to stop and restart the server. The details of a task are in an entry that is below the root of the Task Backend. The Task Backend is responsible for decoding that task entry and ensuring that it is processed as requested. Tasks may be invoked immediately, but they may also be scheduled for execution at some future time. The task backend can also process recurring tasks to ensure that maintenance operations (for example, backups) are performed automatically on a regular basis.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.notification-sender-address.synopsis=Specifies the email address to use as the sender (that is, the "From:" address) address for notification mail messages generated when a task completes execution.
+property.notification-sender-address.default-behavior.alias.synopsis=The default sender address used is "opends-task-notification@" followed by the canonical address of the system on which the server is running.
+property.task-backing-file.synopsis=Specifies the path to the backing file for storing information about the tasks configured in the server.
+property.task-backing-file.description=It may be either an absolute path or a relative path to the base of the OpenDS Directory Server instance.
+property.task-retention-time.synopsis=Specifies the length of time that task entries should be retained after processing on the associated task has been completed.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/TaskBackendCfgDefn_ja.properties b/opends/src/admin/messages/TaskBackendCfgDefn_ja.properties
new file mode 100644
index 0000000..6ba97a2
--- /dev/null
+++ b/opends/src/admin/messages/TaskBackendCfgDefn_ja.properties
@@ -0,0 +1,21 @@
+user-friendly-name=Task Backend
+user-friendly-plural-name=Task Backends
+synopsis=The Task Backend provides a mechanism for scheduling tasks in the OpenDS Directory Server. Tasks are intended to provide access to certain types of administrative functions in the server that may not be convenient to perform remotely.
+description=OpenDS supports tasks to backup and restore backends, to import and export LDIF files, and to stop and restart the server. The details of a task are in an entry that is below the root of the Task Backend. The Task Backend is responsible for decoding that task entry and ensuring that it is processed as requested. Tasks may be invoked immediately, but they may also be scheduled for execution at some future time. The task backend can also process recurring tasks to ensure that maintenance operations (for example, backups) are performed automatically on a regular basis.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.notification-sender-address.synopsis=Specifies the email address to use as the sender (that is, the "From:" address) address for notification mail messages generated when a task completes execution.
+property.notification-sender-address.default-behavior.alias.synopsis=The default sender address used is "opends-task-notification@" followed by the canonical address of the system on which the server is running.
+property.task-backing-file.synopsis=Specifies the path to the backing file for storing information about the tasks configured in the server.
+property.task-backing-file.description=It may be either an absolute path or a relative path to the base of the OpenDS Directory Server instance.
+property.task-retention-time.synopsis=Specifies the length of time that task entries should be retained after processing on the associated task has been completed.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/TaskBackendCfgDefn_ko.properties b/opends/src/admin/messages/TaskBackendCfgDefn_ko.properties
new file mode 100644
index 0000000..6ba97a2
--- /dev/null
+++ b/opends/src/admin/messages/TaskBackendCfgDefn_ko.properties
@@ -0,0 +1,21 @@
+user-friendly-name=Task Backend
+user-friendly-plural-name=Task Backends
+synopsis=The Task Backend provides a mechanism for scheduling tasks in the OpenDS Directory Server. Tasks are intended to provide access to certain types of administrative functions in the server that may not be convenient to perform remotely.
+description=OpenDS supports tasks to backup and restore backends, to import and export LDIF files, and to stop and restart the server. The details of a task are in an entry that is below the root of the Task Backend. The Task Backend is responsible for decoding that task entry and ensuring that it is processed as requested. Tasks may be invoked immediately, but they may also be scheduled for execution at some future time. The task backend can also process recurring tasks to ensure that maintenance operations (for example, backups) are performed automatically on a regular basis.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.notification-sender-address.synopsis=Specifies the email address to use as the sender (that is, the "From:" address) address for notification mail messages generated when a task completes execution.
+property.notification-sender-address.default-behavior.alias.synopsis=The default sender address used is "opends-task-notification@" followed by the canonical address of the system on which the server is running.
+property.task-backing-file.synopsis=Specifies the path to the backing file for storing information about the tasks configured in the server.
+property.task-backing-file.description=It may be either an absolute path or a relative path to the base of the OpenDS Directory Server instance.
+property.task-retention-time.synopsis=Specifies the length of time that task entries should be retained after processing on the associated task has been completed.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/TaskBackendCfgDefn_zh_CN.properties b/opends/src/admin/messages/TaskBackendCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..6ba97a2
--- /dev/null
+++ b/opends/src/admin/messages/TaskBackendCfgDefn_zh_CN.properties
@@ -0,0 +1,21 @@
+user-friendly-name=Task Backend
+user-friendly-plural-name=Task Backends
+synopsis=The Task Backend provides a mechanism for scheduling tasks in the OpenDS Directory Server. Tasks are intended to provide access to certain types of administrative functions in the server that may not be convenient to perform remotely.
+description=OpenDS supports tasks to backup and restore backends, to import and export LDIF files, and to stop and restart the server. The details of a task are in an entry that is below the root of the Task Backend. The Task Backend is responsible for decoding that task entry and ensuring that it is processed as requested. Tasks may be invoked immediately, but they may also be scheduled for execution at some future time. The task backend can also process recurring tasks to ensure that maintenance operations (for example, backups) are performed automatically on a regular basis.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.notification-sender-address.synopsis=Specifies the email address to use as the sender (that is, the "From:" address) address for notification mail messages generated when a task completes execution.
+property.notification-sender-address.default-behavior.alias.synopsis=The default sender address used is "opends-task-notification@" followed by the canonical address of the system on which the server is running.
+property.task-backing-file.synopsis=Specifies the path to the backing file for storing information about the tasks configured in the server.
+property.task-backing-file.description=It may be either an absolute path or a relative path to the base of the OpenDS Directory Server instance.
+property.task-retention-time.synopsis=Specifies the length of time that task entries should be retained after processing on the associated task has been completed.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/TaskBackendCfgDefn_zh_TW.properties b/opends/src/admin/messages/TaskBackendCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..6ba97a2
--- /dev/null
+++ b/opends/src/admin/messages/TaskBackendCfgDefn_zh_TW.properties
@@ -0,0 +1,21 @@
+user-friendly-name=Task Backend
+user-friendly-plural-name=Task Backends
+synopsis=The Task Backend provides a mechanism for scheduling tasks in the OpenDS Directory Server. Tasks are intended to provide access to certain types of administrative functions in the server that may not be convenient to perform remotely.
+description=OpenDS supports tasks to backup and restore backends, to import and export LDIF files, and to stop and restart the server. The details of a task are in an entry that is below the root of the Task Backend. The Task Backend is responsible for decoding that task entry and ensuring that it is processed as requested. Tasks may be invoked immediately, but they may also be scheduled for execution at some future time. The task backend can also process recurring tasks to ensure that maintenance operations (for example, backups) are performed automatically on a regular basis.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.notification-sender-address.synopsis=Specifies the email address to use as the sender (that is, the "From:" address) address for notification mail messages generated when a task completes execution.
+property.notification-sender-address.default-behavior.alias.synopsis=The default sender address used is "opends-task-notification@" followed by the canonical address of the system on which the server is running.
+property.task-backing-file.synopsis=Specifies the path to the backing file for storing information about the tasks configured in the server.
+property.task-backing-file.description=It may be either an absolute path or a relative path to the base of the OpenDS Directory Server instance.
+property.task-retention-time.synopsis=Specifies the length of time that task entries should be retained after processing on the associated task has been completed.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn.properties b/opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn.properties
new file mode 100644
index 0000000..cfd75eb
--- /dev/null
+++ b/opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Telephone Number Attribute Syntax
+user-friendly-plural-name=Telephone Number Attribute Syntaxes
+synopsis=Telephone Number Attribute Syntaxes define an attribute syntax for storing telephone number information.
+property.enabled.synopsis=Indicates whether the Telephone Number Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Telephone Number Attribute Syntax implementation.
+property.strict-format.synopsis=Indicates whether to require telephone number values to strictly comply with the standard definition for this syntax.
diff --git a/opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_de.properties b/opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_de.properties
new file mode 100644
index 0000000..cfd75eb
--- /dev/null
+++ b/opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Telephone Number Attribute Syntax
+user-friendly-plural-name=Telephone Number Attribute Syntaxes
+synopsis=Telephone Number Attribute Syntaxes define an attribute syntax for storing telephone number information.
+property.enabled.synopsis=Indicates whether the Telephone Number Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Telephone Number Attribute Syntax implementation.
+property.strict-format.synopsis=Indicates whether to require telephone number values to strictly comply with the standard definition for this syntax.
diff --git a/opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_es.properties b/opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_es.properties
new file mode 100644
index 0000000..cfd75eb
--- /dev/null
+++ b/opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Telephone Number Attribute Syntax
+user-friendly-plural-name=Telephone Number Attribute Syntaxes
+synopsis=Telephone Number Attribute Syntaxes define an attribute syntax for storing telephone number information.
+property.enabled.synopsis=Indicates whether the Telephone Number Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Telephone Number Attribute Syntax implementation.
+property.strict-format.synopsis=Indicates whether to require telephone number values to strictly comply with the standard definition for this syntax.
diff --git a/opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_fr.properties b/opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_fr.properties
new file mode 100644
index 0000000..cfd75eb
--- /dev/null
+++ b/opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Telephone Number Attribute Syntax
+user-friendly-plural-name=Telephone Number Attribute Syntaxes
+synopsis=Telephone Number Attribute Syntaxes define an attribute syntax for storing telephone number information.
+property.enabled.synopsis=Indicates whether the Telephone Number Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Telephone Number Attribute Syntax implementation.
+property.strict-format.synopsis=Indicates whether to require telephone number values to strictly comply with the standard definition for this syntax.
diff --git a/opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_ja.properties b/opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_ja.properties
new file mode 100644
index 0000000..cfd75eb
--- /dev/null
+++ b/opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Telephone Number Attribute Syntax
+user-friendly-plural-name=Telephone Number Attribute Syntaxes
+synopsis=Telephone Number Attribute Syntaxes define an attribute syntax for storing telephone number information.
+property.enabled.synopsis=Indicates whether the Telephone Number Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Telephone Number Attribute Syntax implementation.
+property.strict-format.synopsis=Indicates whether to require telephone number values to strictly comply with the standard definition for this syntax.
diff --git a/opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_ko.properties b/opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_ko.properties
new file mode 100644
index 0000000..cfd75eb
--- /dev/null
+++ b/opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Telephone Number Attribute Syntax
+user-friendly-plural-name=Telephone Number Attribute Syntaxes
+synopsis=Telephone Number Attribute Syntaxes define an attribute syntax for storing telephone number information.
+property.enabled.synopsis=Indicates whether the Telephone Number Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Telephone Number Attribute Syntax implementation.
+property.strict-format.synopsis=Indicates whether to require telephone number values to strictly comply with the standard definition for this syntax.
diff --git a/opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_zh_CN.properties b/opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..cfd75eb
--- /dev/null
+++ b/opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Telephone Number Attribute Syntax
+user-friendly-plural-name=Telephone Number Attribute Syntaxes
+synopsis=Telephone Number Attribute Syntaxes define an attribute syntax for storing telephone number information.
+property.enabled.synopsis=Indicates whether the Telephone Number Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Telephone Number Attribute Syntax implementation.
+property.strict-format.synopsis=Indicates whether to require telephone number values to strictly comply with the standard definition for this syntax.
diff --git a/opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_zh_TW.properties b/opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..cfd75eb
--- /dev/null
+++ b/opends/src/admin/messages/TelephoneNumberAttributeSyntaxCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Telephone Number Attribute Syntax
+user-friendly-plural-name=Telephone Number Attribute Syntaxes
+synopsis=Telephone Number Attribute Syntaxes define an attribute syntax for storing telephone number information.
+property.enabled.synopsis=Indicates whether the Telephone Number Attribute Syntax is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Telephone Number Attribute Syntax implementation.
+property.strict-format.synopsis=Indicates whether to require telephone number values to strictly comply with the standard definition for this syntax.
diff --git a/opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn.properties b/opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn.properties
new file mode 100644
index 0000000..6f2fcc8
--- /dev/null
+++ b/opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Time Limit Log Rotation Policy
+user-friendly-plural-name=Time Limit Log Rotation Policies
+synopsis=Rotation policy based on the time since last rotation.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Time Limit Log Rotation Policy implementation.
+property.rotation-interval.synopsis=Specifies the time interval between rotations.
diff --git a/opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_de.properties b/opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_de.properties
new file mode 100644
index 0000000..6f2fcc8
--- /dev/null
+++ b/opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_de.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Time Limit Log Rotation Policy
+user-friendly-plural-name=Time Limit Log Rotation Policies
+synopsis=Rotation policy based on the time since last rotation.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Time Limit Log Rotation Policy implementation.
+property.rotation-interval.synopsis=Specifies the time interval between rotations.
diff --git a/opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_es.properties b/opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_es.properties
new file mode 100644
index 0000000..6f2fcc8
--- /dev/null
+++ b/opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_es.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Time Limit Log Rotation Policy
+user-friendly-plural-name=Time Limit Log Rotation Policies
+synopsis=Rotation policy based on the time since last rotation.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Time Limit Log Rotation Policy implementation.
+property.rotation-interval.synopsis=Specifies the time interval between rotations.
diff --git a/opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_fr.properties b/opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_fr.properties
new file mode 100644
index 0000000..6f2fcc8
--- /dev/null
+++ b/opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_fr.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Time Limit Log Rotation Policy
+user-friendly-plural-name=Time Limit Log Rotation Policies
+synopsis=Rotation policy based on the time since last rotation.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Time Limit Log Rotation Policy implementation.
+property.rotation-interval.synopsis=Specifies the time interval between rotations.
diff --git a/opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_ja.properties b/opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_ja.properties
new file mode 100644
index 0000000..6f2fcc8
--- /dev/null
+++ b/opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_ja.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Time Limit Log Rotation Policy
+user-friendly-plural-name=Time Limit Log Rotation Policies
+synopsis=Rotation policy based on the time since last rotation.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Time Limit Log Rotation Policy implementation.
+property.rotation-interval.synopsis=Specifies the time interval between rotations.
diff --git a/opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_ko.properties b/opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_ko.properties
new file mode 100644
index 0000000..6f2fcc8
--- /dev/null
+++ b/opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_ko.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Time Limit Log Rotation Policy
+user-friendly-plural-name=Time Limit Log Rotation Policies
+synopsis=Rotation policy based on the time since last rotation.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Time Limit Log Rotation Policy implementation.
+property.rotation-interval.synopsis=Specifies the time interval between rotations.
diff --git a/opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_zh_CN.properties b/opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..6f2fcc8
--- /dev/null
+++ b/opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_zh_CN.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Time Limit Log Rotation Policy
+user-friendly-plural-name=Time Limit Log Rotation Policies
+synopsis=Rotation policy based on the time since last rotation.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Time Limit Log Rotation Policy implementation.
+property.rotation-interval.synopsis=Specifies the time interval between rotations.
diff --git a/opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_zh_TW.properties b/opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..6f2fcc8
--- /dev/null
+++ b/opends/src/admin/messages/TimeLimitLogRotationPolicyCfgDefn_zh_TW.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Time Limit Log Rotation Policy
+user-friendly-plural-name=Time Limit Log Rotation Policies
+synopsis=Rotation policy based on the time since last rotation.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Time Limit Log Rotation Policy implementation.
+property.rotation-interval.synopsis=Specifies the time interval between rotations.
diff --git a/opends/src/admin/messages/TraditionalWorkQueueCfgDefn.properties b/opends/src/admin/messages/TraditionalWorkQueueCfgDefn.properties
new file mode 100644
index 0000000..e5a4e97
--- /dev/null
+++ b/opends/src/admin/messages/TraditionalWorkQueueCfgDefn.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Traditional Work Queue
+user-friendly-plural-name=Traditional Work Queues
+synopsis=The Traditional Work Queue is a type of work queue that uses a number of worker threads that watch a queue and pick up an operation to process whenever one becomes available.
+description=The traditional work queue is a FIFO queue serviced by a fixed number of worker threads. This fixed number of threads can be changed on the fly, with the change taking effect as soon as it is made. You can limit the size of the work queue to a specified number of operations. When this many operations are in the queue, waiting to be picked up by threads, any new requests are rejected with an error message.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Traditional Work Queue implementation.
+property.max-work-queue-capacity.synopsis=Specifies the maximum number of queued operations that can be in the work queue at any given time.
+property.max-work-queue-capacity.description=If the work queue is already full and additional requests are received by the server, the requests are rejected. A value of zero indicates that there is no limit to the size of the queue.
+property.max-work-queue-capacity.default-behavior.alias.synopsis=The work queue does not impose any limit on the number of operations that can be enqueued at any one time.
+property.num-worker-threads.synopsis=Specifies the number of worker threads to be used for processing operations placed in the queue.
+property.num-worker-threads.description=If the value is increased, the additional worker threads are created immediately. If the value is reduced, the appropriate number of threads are destroyed as operations complete processing.
diff --git a/opends/src/admin/messages/TraditionalWorkQueueCfgDefn_de.properties b/opends/src/admin/messages/TraditionalWorkQueueCfgDefn_de.properties
new file mode 100644
index 0000000..e5a4e97
--- /dev/null
+++ b/opends/src/admin/messages/TraditionalWorkQueueCfgDefn_de.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Traditional Work Queue
+user-friendly-plural-name=Traditional Work Queues
+synopsis=The Traditional Work Queue is a type of work queue that uses a number of worker threads that watch a queue and pick up an operation to process whenever one becomes available.
+description=The traditional work queue is a FIFO queue serviced by a fixed number of worker threads. This fixed number of threads can be changed on the fly, with the change taking effect as soon as it is made. You can limit the size of the work queue to a specified number of operations. When this many operations are in the queue, waiting to be picked up by threads, any new requests are rejected with an error message.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Traditional Work Queue implementation.
+property.max-work-queue-capacity.synopsis=Specifies the maximum number of queued operations that can be in the work queue at any given time.
+property.max-work-queue-capacity.description=If the work queue is already full and additional requests are received by the server, the requests are rejected. A value of zero indicates that there is no limit to the size of the queue.
+property.max-work-queue-capacity.default-behavior.alias.synopsis=The work queue does not impose any limit on the number of operations that can be enqueued at any one time.
+property.num-worker-threads.synopsis=Specifies the number of worker threads to be used for processing operations placed in the queue.
+property.num-worker-threads.description=If the value is increased, the additional worker threads are created immediately. If the value is reduced, the appropriate number of threads are destroyed as operations complete processing.
diff --git a/opends/src/admin/messages/TraditionalWorkQueueCfgDefn_es.properties b/opends/src/admin/messages/TraditionalWorkQueueCfgDefn_es.properties
new file mode 100644
index 0000000..e5a4e97
--- /dev/null
+++ b/opends/src/admin/messages/TraditionalWorkQueueCfgDefn_es.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Traditional Work Queue
+user-friendly-plural-name=Traditional Work Queues
+synopsis=The Traditional Work Queue is a type of work queue that uses a number of worker threads that watch a queue and pick up an operation to process whenever one becomes available.
+description=The traditional work queue is a FIFO queue serviced by a fixed number of worker threads. This fixed number of threads can be changed on the fly, with the change taking effect as soon as it is made. You can limit the size of the work queue to a specified number of operations. When this many operations are in the queue, waiting to be picked up by threads, any new requests are rejected with an error message.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Traditional Work Queue implementation.
+property.max-work-queue-capacity.synopsis=Specifies the maximum number of queued operations that can be in the work queue at any given time.
+property.max-work-queue-capacity.description=If the work queue is already full and additional requests are received by the server, the requests are rejected. A value of zero indicates that there is no limit to the size of the queue.
+property.max-work-queue-capacity.default-behavior.alias.synopsis=The work queue does not impose any limit on the number of operations that can be enqueued at any one time.
+property.num-worker-threads.synopsis=Specifies the number of worker threads to be used for processing operations placed in the queue.
+property.num-worker-threads.description=If the value is increased, the additional worker threads are created immediately. If the value is reduced, the appropriate number of threads are destroyed as operations complete processing.
diff --git a/opends/src/admin/messages/TraditionalWorkQueueCfgDefn_fr.properties b/opends/src/admin/messages/TraditionalWorkQueueCfgDefn_fr.properties
new file mode 100644
index 0000000..e5a4e97
--- /dev/null
+++ b/opends/src/admin/messages/TraditionalWorkQueueCfgDefn_fr.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Traditional Work Queue
+user-friendly-plural-name=Traditional Work Queues
+synopsis=The Traditional Work Queue is a type of work queue that uses a number of worker threads that watch a queue and pick up an operation to process whenever one becomes available.
+description=The traditional work queue is a FIFO queue serviced by a fixed number of worker threads. This fixed number of threads can be changed on the fly, with the change taking effect as soon as it is made. You can limit the size of the work queue to a specified number of operations. When this many operations are in the queue, waiting to be picked up by threads, any new requests are rejected with an error message.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Traditional Work Queue implementation.
+property.max-work-queue-capacity.synopsis=Specifies the maximum number of queued operations that can be in the work queue at any given time.
+property.max-work-queue-capacity.description=If the work queue is already full and additional requests are received by the server, the requests are rejected. A value of zero indicates that there is no limit to the size of the queue.
+property.max-work-queue-capacity.default-behavior.alias.synopsis=The work queue does not impose any limit on the number of operations that can be enqueued at any one time.
+property.num-worker-threads.synopsis=Specifies the number of worker threads to be used for processing operations placed in the queue.
+property.num-worker-threads.description=If the value is increased, the additional worker threads are created immediately. If the value is reduced, the appropriate number of threads are destroyed as operations complete processing.
diff --git a/opends/src/admin/messages/TraditionalWorkQueueCfgDefn_ja.properties b/opends/src/admin/messages/TraditionalWorkQueueCfgDefn_ja.properties
new file mode 100644
index 0000000..e5a4e97
--- /dev/null
+++ b/opends/src/admin/messages/TraditionalWorkQueueCfgDefn_ja.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Traditional Work Queue
+user-friendly-plural-name=Traditional Work Queues
+synopsis=The Traditional Work Queue is a type of work queue that uses a number of worker threads that watch a queue and pick up an operation to process whenever one becomes available.
+description=The traditional work queue is a FIFO queue serviced by a fixed number of worker threads. This fixed number of threads can be changed on the fly, with the change taking effect as soon as it is made. You can limit the size of the work queue to a specified number of operations. When this many operations are in the queue, waiting to be picked up by threads, any new requests are rejected with an error message.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Traditional Work Queue implementation.
+property.max-work-queue-capacity.synopsis=Specifies the maximum number of queued operations that can be in the work queue at any given time.
+property.max-work-queue-capacity.description=If the work queue is already full and additional requests are received by the server, the requests are rejected. A value of zero indicates that there is no limit to the size of the queue.
+property.max-work-queue-capacity.default-behavior.alias.synopsis=The work queue does not impose any limit on the number of operations that can be enqueued at any one time.
+property.num-worker-threads.synopsis=Specifies the number of worker threads to be used for processing operations placed in the queue.
+property.num-worker-threads.description=If the value is increased, the additional worker threads are created immediately. If the value is reduced, the appropriate number of threads are destroyed as operations complete processing.
diff --git a/opends/src/admin/messages/TraditionalWorkQueueCfgDefn_ko.properties b/opends/src/admin/messages/TraditionalWorkQueueCfgDefn_ko.properties
new file mode 100644
index 0000000..e5a4e97
--- /dev/null
+++ b/opends/src/admin/messages/TraditionalWorkQueueCfgDefn_ko.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Traditional Work Queue
+user-friendly-plural-name=Traditional Work Queues
+synopsis=The Traditional Work Queue is a type of work queue that uses a number of worker threads that watch a queue and pick up an operation to process whenever one becomes available.
+description=The traditional work queue is a FIFO queue serviced by a fixed number of worker threads. This fixed number of threads can be changed on the fly, with the change taking effect as soon as it is made. You can limit the size of the work queue to a specified number of operations. When this many operations are in the queue, waiting to be picked up by threads, any new requests are rejected with an error message.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Traditional Work Queue implementation.
+property.max-work-queue-capacity.synopsis=Specifies the maximum number of queued operations that can be in the work queue at any given time.
+property.max-work-queue-capacity.description=If the work queue is already full and additional requests are received by the server, the requests are rejected. A value of zero indicates that there is no limit to the size of the queue.
+property.max-work-queue-capacity.default-behavior.alias.synopsis=The work queue does not impose any limit on the number of operations that can be enqueued at any one time.
+property.num-worker-threads.synopsis=Specifies the number of worker threads to be used for processing operations placed in the queue.
+property.num-worker-threads.description=If the value is increased, the additional worker threads are created immediately. If the value is reduced, the appropriate number of threads are destroyed as operations complete processing.
diff --git a/opends/src/admin/messages/TraditionalWorkQueueCfgDefn_zh_CN.properties b/opends/src/admin/messages/TraditionalWorkQueueCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..e5a4e97
--- /dev/null
+++ b/opends/src/admin/messages/TraditionalWorkQueueCfgDefn_zh_CN.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Traditional Work Queue
+user-friendly-plural-name=Traditional Work Queues
+synopsis=The Traditional Work Queue is a type of work queue that uses a number of worker threads that watch a queue and pick up an operation to process whenever one becomes available.
+description=The traditional work queue is a FIFO queue serviced by a fixed number of worker threads. This fixed number of threads can be changed on the fly, with the change taking effect as soon as it is made. You can limit the size of the work queue to a specified number of operations. When this many operations are in the queue, waiting to be picked up by threads, any new requests are rejected with an error message.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Traditional Work Queue implementation.
+property.max-work-queue-capacity.synopsis=Specifies the maximum number of queued operations that can be in the work queue at any given time.
+property.max-work-queue-capacity.description=If the work queue is already full and additional requests are received by the server, the requests are rejected. A value of zero indicates that there is no limit to the size of the queue.
+property.max-work-queue-capacity.default-behavior.alias.synopsis=The work queue does not impose any limit on the number of operations that can be enqueued at any one time.
+property.num-worker-threads.synopsis=Specifies the number of worker threads to be used for processing operations placed in the queue.
+property.num-worker-threads.description=If the value is increased, the additional worker threads are created immediately. If the value is reduced, the appropriate number of threads are destroyed as operations complete processing.
diff --git a/opends/src/admin/messages/TraditionalWorkQueueCfgDefn_zh_TW.properties b/opends/src/admin/messages/TraditionalWorkQueueCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..e5a4e97
--- /dev/null
+++ b/opends/src/admin/messages/TraditionalWorkQueueCfgDefn_zh_TW.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Traditional Work Queue
+user-friendly-plural-name=Traditional Work Queues
+synopsis=The Traditional Work Queue is a type of work queue that uses a number of worker threads that watch a queue and pick up an operation to process whenever one becomes available.
+description=The traditional work queue is a FIFO queue serviced by a fixed number of worker threads. This fixed number of threads can be changed on the fly, with the change taking effect as soon as it is made. You can limit the size of the work queue to a specified number of operations. When this many operations are in the queue, waiting to be picked up by threads, any new requests are rejected with an error message.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Traditional Work Queue implementation.
+property.max-work-queue-capacity.synopsis=Specifies the maximum number of queued operations that can be in the work queue at any given time.
+property.max-work-queue-capacity.description=If the work queue is already full and additional requests are received by the server, the requests are rejected. A value of zero indicates that there is no limit to the size of the queue.
+property.max-work-queue-capacity.default-behavior.alias.synopsis=The work queue does not impose any limit on the number of operations that can be enqueued at any one time.
+property.num-worker-threads.synopsis=Specifies the number of worker threads to be used for processing operations placed in the queue.
+property.num-worker-threads.description=If the value is increased, the additional worker threads are created immediately. If the value is reduced, the appropriate number of threads are destroyed as operations complete processing.
diff --git a/opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn.properties b/opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn.properties
new file mode 100644
index 0000000..8f5dbf6
--- /dev/null
+++ b/opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Triple DES Password Storage Scheme
+user-friendly-plural-name=Triple DES Password Storage Schemes
+synopsis=The Triple DES Password Storage Scheme provides a mechanism for encoding user passwords using the triple-DES (DES/EDE) reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "3DES".
+property.enabled.synopsis=Indicates whether the Triple DES Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Triple DES Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_de.properties b/opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_de.properties
new file mode 100644
index 0000000..8f5dbf6
--- /dev/null
+++ b/opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Triple DES Password Storage Scheme
+user-friendly-plural-name=Triple DES Password Storage Schemes
+synopsis=The Triple DES Password Storage Scheme provides a mechanism for encoding user passwords using the triple-DES (DES/EDE) reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "3DES".
+property.enabled.synopsis=Indicates whether the Triple DES Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Triple DES Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_es.properties b/opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_es.properties
new file mode 100644
index 0000000..8f5dbf6
--- /dev/null
+++ b/opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Triple DES Password Storage Scheme
+user-friendly-plural-name=Triple DES Password Storage Schemes
+synopsis=The Triple DES Password Storage Scheme provides a mechanism for encoding user passwords using the triple-DES (DES/EDE) reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "3DES".
+property.enabled.synopsis=Indicates whether the Triple DES Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Triple DES Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_fr.properties b/opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_fr.properties
new file mode 100644
index 0000000..8f5dbf6
--- /dev/null
+++ b/opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Triple DES Password Storage Scheme
+user-friendly-plural-name=Triple DES Password Storage Schemes
+synopsis=The Triple DES Password Storage Scheme provides a mechanism for encoding user passwords using the triple-DES (DES/EDE) reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "3DES".
+property.enabled.synopsis=Indicates whether the Triple DES Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Triple DES Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_ja.properties b/opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_ja.properties
new file mode 100644
index 0000000..8f5dbf6
--- /dev/null
+++ b/opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Triple DES Password Storage Scheme
+user-friendly-plural-name=Triple DES Password Storage Schemes
+synopsis=The Triple DES Password Storage Scheme provides a mechanism for encoding user passwords using the triple-DES (DES/EDE) reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "3DES".
+property.enabled.synopsis=Indicates whether the Triple DES Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Triple DES Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_ko.properties b/opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_ko.properties
new file mode 100644
index 0000000..8f5dbf6
--- /dev/null
+++ b/opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Triple DES Password Storage Scheme
+user-friendly-plural-name=Triple DES Password Storage Schemes
+synopsis=The Triple DES Password Storage Scheme provides a mechanism for encoding user passwords using the triple-DES (DES/EDE) reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "3DES".
+property.enabled.synopsis=Indicates whether the Triple DES Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Triple DES Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_zh_CN.properties b/opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..8f5dbf6
--- /dev/null
+++ b/opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Triple DES Password Storage Scheme
+user-friendly-plural-name=Triple DES Password Storage Schemes
+synopsis=The Triple DES Password Storage Scheme provides a mechanism for encoding user passwords using the triple-DES (DES/EDE) reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "3DES".
+property.enabled.synopsis=Indicates whether the Triple DES Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Triple DES Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_zh_TW.properties b/opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..8f5dbf6
--- /dev/null
+++ b/opends/src/admin/messages/TripleDESPasswordStorageSchemeCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Triple DES Password Storage Scheme
+user-friendly-plural-name=Triple DES Password Storage Schemes
+synopsis=The Triple DES Password Storage Scheme provides a mechanism for encoding user passwords using the triple-DES (DES/EDE) reversible encryption mechanism.
+description=This scheme contains only an implementation for the user password syntax, with a storage scheme name of "3DES".
+property.enabled.synopsis=Indicates whether the Triple DES Password Storage Scheme is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Triple DES Password Storage Scheme implementation.
diff --git a/opends/src/admin/messages/TrustManagerProviderCfgDefn.properties b/opends/src/admin/messages/TrustManagerProviderCfgDefn.properties
new file mode 100644
index 0000000..b22b687
--- /dev/null
+++ b/opends/src/admin/messages/TrustManagerProviderCfgDefn.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Trust Manager Provider
+user-friendly-plural-name=Trust Manager Providers
+synopsis=Trust Manager Providers determine whether to trust presented certificates.
+property.enabled.synopsis=Indicate whether the Trust Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Trust Manager Provider implementation.
diff --git a/opends/src/admin/messages/TrustManagerProviderCfgDefn_de.properties b/opends/src/admin/messages/TrustManagerProviderCfgDefn_de.properties
new file mode 100644
index 0000000..b22b687
--- /dev/null
+++ b/opends/src/admin/messages/TrustManagerProviderCfgDefn_de.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Trust Manager Provider
+user-friendly-plural-name=Trust Manager Providers
+synopsis=Trust Manager Providers determine whether to trust presented certificates.
+property.enabled.synopsis=Indicate whether the Trust Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Trust Manager Provider implementation.
diff --git a/opends/src/admin/messages/TrustManagerProviderCfgDefn_es.properties b/opends/src/admin/messages/TrustManagerProviderCfgDefn_es.properties
new file mode 100644
index 0000000..b22b687
--- /dev/null
+++ b/opends/src/admin/messages/TrustManagerProviderCfgDefn_es.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Trust Manager Provider
+user-friendly-plural-name=Trust Manager Providers
+synopsis=Trust Manager Providers determine whether to trust presented certificates.
+property.enabled.synopsis=Indicate whether the Trust Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Trust Manager Provider implementation.
diff --git a/opends/src/admin/messages/TrustManagerProviderCfgDefn_fr.properties b/opends/src/admin/messages/TrustManagerProviderCfgDefn_fr.properties
new file mode 100644
index 0000000..b22b687
--- /dev/null
+++ b/opends/src/admin/messages/TrustManagerProviderCfgDefn_fr.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Trust Manager Provider
+user-friendly-plural-name=Trust Manager Providers
+synopsis=Trust Manager Providers determine whether to trust presented certificates.
+property.enabled.synopsis=Indicate whether the Trust Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Trust Manager Provider implementation.
diff --git a/opends/src/admin/messages/TrustManagerProviderCfgDefn_ja.properties b/opends/src/admin/messages/TrustManagerProviderCfgDefn_ja.properties
new file mode 100644
index 0000000..b22b687
--- /dev/null
+++ b/opends/src/admin/messages/TrustManagerProviderCfgDefn_ja.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Trust Manager Provider
+user-friendly-plural-name=Trust Manager Providers
+synopsis=Trust Manager Providers determine whether to trust presented certificates.
+property.enabled.synopsis=Indicate whether the Trust Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Trust Manager Provider implementation.
diff --git a/opends/src/admin/messages/TrustManagerProviderCfgDefn_ko.properties b/opends/src/admin/messages/TrustManagerProviderCfgDefn_ko.properties
new file mode 100644
index 0000000..b22b687
--- /dev/null
+++ b/opends/src/admin/messages/TrustManagerProviderCfgDefn_ko.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Trust Manager Provider
+user-friendly-plural-name=Trust Manager Providers
+synopsis=Trust Manager Providers determine whether to trust presented certificates.
+property.enabled.synopsis=Indicate whether the Trust Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Trust Manager Provider implementation.
diff --git a/opends/src/admin/messages/TrustManagerProviderCfgDefn_zh_CN.properties b/opends/src/admin/messages/TrustManagerProviderCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..b22b687
--- /dev/null
+++ b/opends/src/admin/messages/TrustManagerProviderCfgDefn_zh_CN.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Trust Manager Provider
+user-friendly-plural-name=Trust Manager Providers
+synopsis=Trust Manager Providers determine whether to trust presented certificates.
+property.enabled.synopsis=Indicate whether the Trust Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Trust Manager Provider implementation.
diff --git a/opends/src/admin/messages/TrustManagerProviderCfgDefn_zh_TW.properties b/opends/src/admin/messages/TrustManagerProviderCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..b22b687
--- /dev/null
+++ b/opends/src/admin/messages/TrustManagerProviderCfgDefn_zh_TW.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Trust Manager Provider
+user-friendly-plural-name=Trust Manager Providers
+synopsis=Trust Manager Providers determine whether to trust presented certificates.
+property.enabled.synopsis=Indicate whether the Trust Manager Provider is enabled for use.
+property.java-class.synopsis=The fully-qualified name of the Java class that provides the Trust Manager Provider implementation.
diff --git a/opends/src/admin/messages/TrustStoreBackendCfgDefn.properties b/opends/src/admin/messages/TrustStoreBackendCfgDefn.properties
new file mode 100644
index 0000000..08fdbe9
--- /dev/null
+++ b/opends/src/admin/messages/TrustStoreBackendCfgDefn.properties
@@ -0,0 +1,29 @@
+user-friendly-name=Trust Store Backend
+user-friendly-plural-name=Trust Store Backends
+synopsis=The Trust Store Backend provides an LDAP view of a file-based trust store. It is used by the administrative cryptographic framework.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.trust-store-file.synopsis=Specifies the path to the file that stores the trust information.
+property.trust-store-file.description=It may be an absolute path, or a path that is relative to the OpenDS Directory Server instance root.
+property.trust-store-pin.synopsis=Specifies the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-type.synopsis=Specifies the format for the data in the key store file.
+property.trust-store-type.description=Valid values should always include 'JKS' and 'PKCS12', but different implementations may allow other values as well.
+property.trust-store-type.default-behavior.alias.synopsis=The JVM default value is used.
+property.trust-store-type.requires-admin-action.synopsis=Changes to this property take effect the next time that the key manager is accessed.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/TrustStoreBackendCfgDefn_de.properties b/opends/src/admin/messages/TrustStoreBackendCfgDefn_de.properties
new file mode 100644
index 0000000..08fdbe9
--- /dev/null
+++ b/opends/src/admin/messages/TrustStoreBackendCfgDefn_de.properties
@@ -0,0 +1,29 @@
+user-friendly-name=Trust Store Backend
+user-friendly-plural-name=Trust Store Backends
+synopsis=The Trust Store Backend provides an LDAP view of a file-based trust store. It is used by the administrative cryptographic framework.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.trust-store-file.synopsis=Specifies the path to the file that stores the trust information.
+property.trust-store-file.description=It may be an absolute path, or a path that is relative to the OpenDS Directory Server instance root.
+property.trust-store-pin.synopsis=Specifies the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-type.synopsis=Specifies the format for the data in the key store file.
+property.trust-store-type.description=Valid values should always include 'JKS' and 'PKCS12', but different implementations may allow other values as well.
+property.trust-store-type.default-behavior.alias.synopsis=The JVM default value is used.
+property.trust-store-type.requires-admin-action.synopsis=Changes to this property take effect the next time that the key manager is accessed.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/TrustStoreBackendCfgDefn_es.properties b/opends/src/admin/messages/TrustStoreBackendCfgDefn_es.properties
new file mode 100644
index 0000000..08fdbe9
--- /dev/null
+++ b/opends/src/admin/messages/TrustStoreBackendCfgDefn_es.properties
@@ -0,0 +1,29 @@
+user-friendly-name=Trust Store Backend
+user-friendly-plural-name=Trust Store Backends
+synopsis=The Trust Store Backend provides an LDAP view of a file-based trust store. It is used by the administrative cryptographic framework.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.trust-store-file.synopsis=Specifies the path to the file that stores the trust information.
+property.trust-store-file.description=It may be an absolute path, or a path that is relative to the OpenDS Directory Server instance root.
+property.trust-store-pin.synopsis=Specifies the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-type.synopsis=Specifies the format for the data in the key store file.
+property.trust-store-type.description=Valid values should always include 'JKS' and 'PKCS12', but different implementations may allow other values as well.
+property.trust-store-type.default-behavior.alias.synopsis=The JVM default value is used.
+property.trust-store-type.requires-admin-action.synopsis=Changes to this property take effect the next time that the key manager is accessed.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/TrustStoreBackendCfgDefn_fr.properties b/opends/src/admin/messages/TrustStoreBackendCfgDefn_fr.properties
new file mode 100644
index 0000000..08fdbe9
--- /dev/null
+++ b/opends/src/admin/messages/TrustStoreBackendCfgDefn_fr.properties
@@ -0,0 +1,29 @@
+user-friendly-name=Trust Store Backend
+user-friendly-plural-name=Trust Store Backends
+synopsis=The Trust Store Backend provides an LDAP view of a file-based trust store. It is used by the administrative cryptographic framework.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.trust-store-file.synopsis=Specifies the path to the file that stores the trust information.
+property.trust-store-file.description=It may be an absolute path, or a path that is relative to the OpenDS Directory Server instance root.
+property.trust-store-pin.synopsis=Specifies the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-type.synopsis=Specifies the format for the data in the key store file.
+property.trust-store-type.description=Valid values should always include 'JKS' and 'PKCS12', but different implementations may allow other values as well.
+property.trust-store-type.default-behavior.alias.synopsis=The JVM default value is used.
+property.trust-store-type.requires-admin-action.synopsis=Changes to this property take effect the next time that the key manager is accessed.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/TrustStoreBackendCfgDefn_ja.properties b/opends/src/admin/messages/TrustStoreBackendCfgDefn_ja.properties
new file mode 100644
index 0000000..08fdbe9
--- /dev/null
+++ b/opends/src/admin/messages/TrustStoreBackendCfgDefn_ja.properties
@@ -0,0 +1,29 @@
+user-friendly-name=Trust Store Backend
+user-friendly-plural-name=Trust Store Backends
+synopsis=The Trust Store Backend provides an LDAP view of a file-based trust store. It is used by the administrative cryptographic framework.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.trust-store-file.synopsis=Specifies the path to the file that stores the trust information.
+property.trust-store-file.description=It may be an absolute path, or a path that is relative to the OpenDS Directory Server instance root.
+property.trust-store-pin.synopsis=Specifies the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-type.synopsis=Specifies the format for the data in the key store file.
+property.trust-store-type.description=Valid values should always include 'JKS' and 'PKCS12', but different implementations may allow other values as well.
+property.trust-store-type.default-behavior.alias.synopsis=The JVM default value is used.
+property.trust-store-type.requires-admin-action.synopsis=Changes to this property take effect the next time that the key manager is accessed.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/TrustStoreBackendCfgDefn_ko.properties b/opends/src/admin/messages/TrustStoreBackendCfgDefn_ko.properties
new file mode 100644
index 0000000..08fdbe9
--- /dev/null
+++ b/opends/src/admin/messages/TrustStoreBackendCfgDefn_ko.properties
@@ -0,0 +1,29 @@
+user-friendly-name=Trust Store Backend
+user-friendly-plural-name=Trust Store Backends
+synopsis=The Trust Store Backend provides an LDAP view of a file-based trust store. It is used by the administrative cryptographic framework.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.trust-store-file.synopsis=Specifies the path to the file that stores the trust information.
+property.trust-store-file.description=It may be an absolute path, or a path that is relative to the OpenDS Directory Server instance root.
+property.trust-store-pin.synopsis=Specifies the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-type.synopsis=Specifies the format for the data in the key store file.
+property.trust-store-type.description=Valid values should always include 'JKS' and 'PKCS12', but different implementations may allow other values as well.
+property.trust-store-type.default-behavior.alias.synopsis=The JVM default value is used.
+property.trust-store-type.requires-admin-action.synopsis=Changes to this property take effect the next time that the key manager is accessed.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/TrustStoreBackendCfgDefn_zh_CN.properties b/opends/src/admin/messages/TrustStoreBackendCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..08fdbe9
--- /dev/null
+++ b/opends/src/admin/messages/TrustStoreBackendCfgDefn_zh_CN.properties
@@ -0,0 +1,29 @@
+user-friendly-name=Trust Store Backend
+user-friendly-plural-name=Trust Store Backends
+synopsis=The Trust Store Backend provides an LDAP view of a file-based trust store. It is used by the administrative cryptographic framework.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.trust-store-file.synopsis=Specifies the path to the file that stores the trust information.
+property.trust-store-file.description=It may be an absolute path, or a path that is relative to the OpenDS Directory Server instance root.
+property.trust-store-pin.synopsis=Specifies the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-type.synopsis=Specifies the format for the data in the key store file.
+property.trust-store-type.description=Valid values should always include 'JKS' and 'PKCS12', but different implementations may allow other values as well.
+property.trust-store-type.default-behavior.alias.synopsis=The JVM default value is used.
+property.trust-store-type.requires-admin-action.synopsis=Changes to this property take effect the next time that the key manager is accessed.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/TrustStoreBackendCfgDefn_zh_TW.properties b/opends/src/admin/messages/TrustStoreBackendCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..08fdbe9
--- /dev/null
+++ b/opends/src/admin/messages/TrustStoreBackendCfgDefn_zh_TW.properties
@@ -0,0 +1,29 @@
+user-friendly-name=Trust Store Backend
+user-friendly-plural-name=Trust Store Backends
+synopsis=The Trust Store Backend provides an LDAP view of a file-based trust store. It is used by the administrative cryptographic framework.
+property.backend-id.synopsis=Specifies a name to identify the associated backend.
+property.backend-id.description=The name must be unique among all backends in the server. The backend ID may not be altered after the backend is created in the server.
+property.base-dn.synopsis=Specifies the base DN(s) for the data that the backend handles.
+property.base-dn.description=A single backend may be responsible for one or more base DNs. Note that no two backends may have the same base DN although one backend may have a base DN that is below a base DN provided by another backend (similar to the use of sub-suffixes in the Sun Java System Directory Server). If any of the base DNs is subordinate to a base DN for another backend, then all base DNs for that backend must be subordinate to that same base DN.
+property.base-dn.requires-admin-action.synopsis=No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used.
+property.enabled.synopsis=Indicates whether the backend is enabled in the server.
+property.enabled.description=If a backend is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the backend implementation.
+property.trust-store-file.synopsis=Specifies the path to the file that stores the trust information.
+property.trust-store-file.description=It may be an absolute path, or a path that is relative to the OpenDS Directory Server instance root.
+property.trust-store-pin.synopsis=Specifies the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-pin-environment-variable.synopsis=Specifies the name of the environment variable that contains the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin-environment-variable.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-pin-file.synopsis=Specifies the path to the text file whose only contents should be a single line containing the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin-file.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-pin-property.synopsis=Specifies the name of the Java property that contains the clear-text PIN needed to access the Trust Store Backend .
+property.trust-store-pin-property.requires-admin-action.synopsis=Changes to this property will take effect the next time that the Trust Store Backend is accessed.
+property.trust-store-type.synopsis=Specifies the format for the data in the key store file.
+property.trust-store-type.description=Valid values should always include 'JKS' and 'PKCS12', but different implementations may allow other values as well.
+property.trust-store-type.default-behavior.alias.synopsis=The JVM default value is used.
+property.trust-store-type.requires-admin-action.synopsis=Changes to this property take effect the next time that the key manager is accessed.
+property.writability-mode.synopsis=Specifies the behavior that the backend should use when processing write operations.
+property.writability-mode.syntax.enumeration.value.disabled.synopsis=Causes all write attempts to fail.
+property.writability-mode.syntax.enumeration.value.enabled.synopsis=Allows write operations to be performed in that backend (if the requested operation is valid, the user has permission to perform the operation, the backend supports that type of write operation, and the global writability mode property is also enabled).
+property.writability-mode.syntax.enumeration.value.internal-only.synopsis=Causes external write attempts to fail but allows writes by replication and internal operations.
diff --git a/opends/src/admin/messages/UniqueAttributePluginCfgDefn.properties b/opends/src/admin/messages/UniqueAttributePluginCfgDefn.properties
new file mode 100644
index 0000000..2175a98
--- /dev/null
+++ b/opends/src/admin/messages/UniqueAttributePluginCfgDefn.properties
@@ -0,0 +1,62 @@
+user-friendly-name=Unique Attribute Plugin
+user-friendly-plural-name=Unique Attribute Plugins
+synopsis=The Unique Attribute Plugin enforces constraints on the value of an attribute within a portion of the directory.
+description=The values for each attribute must be unique within each base DN specified in the plugin's base-dn property or within all of the server's public naming contexts if no base DNs were specified.
+property.base-dn.synopsis=Specifies a base DN within which the attribute must be unique.
+property.base-dn.default-behavior.alias.synopsis=The plug-in uses the server's public naming contexts in the searches.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
+property.type.synopsis=Specifies the type of attributes to check for value uniqueness.
diff --git a/opends/src/admin/messages/UniqueAttributePluginCfgDefn_de.properties b/opends/src/admin/messages/UniqueAttributePluginCfgDefn_de.properties
new file mode 100644
index 0000000..2175a98
--- /dev/null
+++ b/opends/src/admin/messages/UniqueAttributePluginCfgDefn_de.properties
@@ -0,0 +1,62 @@
+user-friendly-name=Unique Attribute Plugin
+user-friendly-plural-name=Unique Attribute Plugins
+synopsis=The Unique Attribute Plugin enforces constraints on the value of an attribute within a portion of the directory.
+description=The values for each attribute must be unique within each base DN specified in the plugin's base-dn property or within all of the server's public naming contexts if no base DNs were specified.
+property.base-dn.synopsis=Specifies a base DN within which the attribute must be unique.
+property.base-dn.default-behavior.alias.synopsis=The plug-in uses the server's public naming contexts in the searches.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
+property.type.synopsis=Specifies the type of attributes to check for value uniqueness.
diff --git a/opends/src/admin/messages/UniqueAttributePluginCfgDefn_es.properties b/opends/src/admin/messages/UniqueAttributePluginCfgDefn_es.properties
new file mode 100644
index 0000000..2175a98
--- /dev/null
+++ b/opends/src/admin/messages/UniqueAttributePluginCfgDefn_es.properties
@@ -0,0 +1,62 @@
+user-friendly-name=Unique Attribute Plugin
+user-friendly-plural-name=Unique Attribute Plugins
+synopsis=The Unique Attribute Plugin enforces constraints on the value of an attribute within a portion of the directory.
+description=The values for each attribute must be unique within each base DN specified in the plugin's base-dn property or within all of the server's public naming contexts if no base DNs were specified.
+property.base-dn.synopsis=Specifies a base DN within which the attribute must be unique.
+property.base-dn.default-behavior.alias.synopsis=The plug-in uses the server's public naming contexts in the searches.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
+property.type.synopsis=Specifies the type of attributes to check for value uniqueness.
diff --git a/opends/src/admin/messages/UniqueAttributePluginCfgDefn_fr.properties b/opends/src/admin/messages/UniqueAttributePluginCfgDefn_fr.properties
new file mode 100644
index 0000000..2175a98
--- /dev/null
+++ b/opends/src/admin/messages/UniqueAttributePluginCfgDefn_fr.properties
@@ -0,0 +1,62 @@
+user-friendly-name=Unique Attribute Plugin
+user-friendly-plural-name=Unique Attribute Plugins
+synopsis=The Unique Attribute Plugin enforces constraints on the value of an attribute within a portion of the directory.
+description=The values for each attribute must be unique within each base DN specified in the plugin's base-dn property or within all of the server's public naming contexts if no base DNs were specified.
+property.base-dn.synopsis=Specifies a base DN within which the attribute must be unique.
+property.base-dn.default-behavior.alias.synopsis=The plug-in uses the server's public naming contexts in the searches.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
+property.type.synopsis=Specifies the type of attributes to check for value uniqueness.
diff --git a/opends/src/admin/messages/UniqueAttributePluginCfgDefn_ja.properties b/opends/src/admin/messages/UniqueAttributePluginCfgDefn_ja.properties
new file mode 100644
index 0000000..2175a98
--- /dev/null
+++ b/opends/src/admin/messages/UniqueAttributePluginCfgDefn_ja.properties
@@ -0,0 +1,62 @@
+user-friendly-name=Unique Attribute Plugin
+user-friendly-plural-name=Unique Attribute Plugins
+synopsis=The Unique Attribute Plugin enforces constraints on the value of an attribute within a portion of the directory.
+description=The values for each attribute must be unique within each base DN specified in the plugin's base-dn property or within all of the server's public naming contexts if no base DNs were specified.
+property.base-dn.synopsis=Specifies a base DN within which the attribute must be unique.
+property.base-dn.default-behavior.alias.synopsis=The plug-in uses the server's public naming contexts in the searches.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
+property.type.synopsis=Specifies the type of attributes to check for value uniqueness.
diff --git a/opends/src/admin/messages/UniqueAttributePluginCfgDefn_ko.properties b/opends/src/admin/messages/UniqueAttributePluginCfgDefn_ko.properties
new file mode 100644
index 0000000..2175a98
--- /dev/null
+++ b/opends/src/admin/messages/UniqueAttributePluginCfgDefn_ko.properties
@@ -0,0 +1,62 @@
+user-friendly-name=Unique Attribute Plugin
+user-friendly-plural-name=Unique Attribute Plugins
+synopsis=The Unique Attribute Plugin enforces constraints on the value of an attribute within a portion of the directory.
+description=The values for each attribute must be unique within each base DN specified in the plugin's base-dn property or within all of the server's public naming contexts if no base DNs were specified.
+property.base-dn.synopsis=Specifies a base DN within which the attribute must be unique.
+property.base-dn.default-behavior.alias.synopsis=The plug-in uses the server's public naming contexts in the searches.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
+property.type.synopsis=Specifies the type of attributes to check for value uniqueness.
diff --git a/opends/src/admin/messages/UniqueAttributePluginCfgDefn_zh_CN.properties b/opends/src/admin/messages/UniqueAttributePluginCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..2175a98
--- /dev/null
+++ b/opends/src/admin/messages/UniqueAttributePluginCfgDefn_zh_CN.properties
@@ -0,0 +1,62 @@
+user-friendly-name=Unique Attribute Plugin
+user-friendly-plural-name=Unique Attribute Plugins
+synopsis=The Unique Attribute Plugin enforces constraints on the value of an attribute within a portion of the directory.
+description=The values for each attribute must be unique within each base DN specified in the plugin's base-dn property or within all of the server's public naming contexts if no base DNs were specified.
+property.base-dn.synopsis=Specifies a base DN within which the attribute must be unique.
+property.base-dn.default-behavior.alias.synopsis=The plug-in uses the server's public naming contexts in the searches.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
+property.type.synopsis=Specifies the type of attributes to check for value uniqueness.
diff --git a/opends/src/admin/messages/UniqueAttributePluginCfgDefn_zh_TW.properties b/opends/src/admin/messages/UniqueAttributePluginCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..2175a98
--- /dev/null
+++ b/opends/src/admin/messages/UniqueAttributePluginCfgDefn_zh_TW.properties
@@ -0,0 +1,62 @@
+user-friendly-name=Unique Attribute Plugin
+user-friendly-plural-name=Unique Attribute Plugins
+synopsis=The Unique Attribute Plugin enforces constraints on the value of an attribute within a portion of the directory.
+description=The values for each attribute must be unique within each base DN specified in the plugin's base-dn property or within all of the server's public naming contexts if no base DNs were specified.
+property.base-dn.synopsis=Specifies a base DN within which the attribute must be unique.
+property.base-dn.default-behavior.alias.synopsis=The plug-in uses the server's public naming contexts in the searches.
+property.enabled.synopsis=Indicates whether the plug-in is enabled for use.
+property.invoke-for-internal-operations.synopsis=Indicates whether the plug-in should be invoked for internal operations.
+property.invoke-for-internal-operations.description=Any plug-in that can be invoked for internal operations must ensure that it does not create any new internal operatons that can cause the same plug-in to be re-invoked.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the plug-in implementation.
+property.plugin-type.synopsis=Specifies the set of plug-in types for the plug-in, which specifies the times at which the plug-in is invoked.
+property.plugin-type.syntax.enumeration.value.intermediateresponse.synopsis=Invoked before sending an intermediate repsonse message to the client.
+property.plugin-type.syntax.enumeration.value.ldifexport.synopsis=Invoked for each operation to be written during an LDIF export.
+property.plugin-type.syntax.enumeration.value.ldifimport.synopsis=Invoked for each entry read during an LDIF import.
+property.plugin-type.syntax.enumeration.value.postconnect.synopsis=Invoked whenever a new connection is established to the server.
+property.plugin-type.syntax.enumeration.value.postdisconnect.synopsis=Invoked whenever an existing connection is terminated (by either the client or the server).
+property.plugin-type.syntax.enumeration.value.postoperationabandon.synopsis=Invoked after completing the abandon processing.
+property.plugin-type.syntax.enumeration.value.postoperationadd.synopsis=Invoked after completing the core add processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationbind.synopsis=Invoked after completing the core bind processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationcompare.synopsis=Invoked after completing the core compare processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationdelete.synopsis=Invoked after completing the core delete processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationextended.synopsis=Invoked after completing the core extended processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodify.synopsis=Invoked after completing the core modify processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationmodifydn.synopsis=Invoked after completing the core modify DN processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationsearch.synopsis=Invoked after completing the core search processing but before sending the response to the client.
+property.plugin-type.syntax.enumeration.value.postoperationunbind.synopsis=Invoked after completing the unbind processing.
+property.plugin-type.syntax.enumeration.value.postresponseadd.synopsis=Invoked after sending the add response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsebind.synopsis=Invoked after sending the bind response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsecompare.synopsis=Invoked after sending the compare response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsedelete.synopsis=Invoked after sending the delete response to the client.
+property.plugin-type.syntax.enumeration.value.postresponseextended.synopsis=Invoked after sending the extended response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodify.synopsis=Invoked after sending the modify response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsemodifydn.synopsis=Invoked after sending the modify DN response to the client.
+property.plugin-type.syntax.enumeration.value.postresponsesearch.synopsis=Invoked after sending the search result done message to the client.
+property.plugin-type.syntax.enumeration.value.postsynchronizationadd.synopsis=Invoked after completing post-synchronization processing for an add operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationdelete.synopsis=Invoked after completing post-synchronization processing for a delete operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodify.synopsis=Invoked after completing post-synchronization processing for a modify operation.
+property.plugin-type.syntax.enumeration.value.postsynchronizationmodifydn.synopsis=Invoked after completing post-synchronization processing for a modify DN operation.
+property.plugin-type.syntax.enumeration.value.preoperationadd.synopsis=Invoked prior to performing the core add processing.
+property.plugin-type.syntax.enumeration.value.preoperationbind.synopsis=Invoked prior to performing the core bind processing.
+property.plugin-type.syntax.enumeration.value.preoperationcompare.synopsis=Invoked prior to performing the core compare processing.
+property.plugin-type.syntax.enumeration.value.preoperationdelete.synopsis=Invoked prior to performing the core delete processing.
+property.plugin-type.syntax.enumeration.value.preoperationextended.synopsis=Invoked prior to performing the core extended processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodify.synopsis=Invoked prior to performing the core modify processing.
+property.plugin-type.syntax.enumeration.value.preoperationmodifydn.synopsis=Invoked prior to performing the core modify DN processing.
+property.plugin-type.syntax.enumeration.value.preoperationsearch.synopsis=Invoked prior to performing the core search processing.
+property.plugin-type.syntax.enumeration.value.preparseabandon.synopsis=Invoked prior to parsing an abandon request.
+property.plugin-type.syntax.enumeration.value.preparseadd.synopsis=Invoked prior to parsing an add request.
+property.plugin-type.syntax.enumeration.value.preparsebind.synopsis=Invoked prior to parsing a bind request.
+property.plugin-type.syntax.enumeration.value.preparsecompare.synopsis=Invoked prior to parsing a compare request.
+property.plugin-type.syntax.enumeration.value.preparsedelete.synopsis=Invoked prior to parsing a delete request.
+property.plugin-type.syntax.enumeration.value.preparseextended.synopsis=Invoked prior to parsing an extended request.
+property.plugin-type.syntax.enumeration.value.preparsemodify.synopsis=Invoked prior to parsing a modify request.
+property.plugin-type.syntax.enumeration.value.preparsemodifydn.synopsis=Invoked prior to parsing a modify DN request.
+property.plugin-type.syntax.enumeration.value.preparsesearch.synopsis=Invoked prior to parsing a search request.
+property.plugin-type.syntax.enumeration.value.preparseunbind.synopsis=Invoked prior to parsing an unbind request.
+property.plugin-type.syntax.enumeration.value.searchresultentry.synopsis=Invoked before sending a search result entry to the client.
+property.plugin-type.syntax.enumeration.value.searchresultreference.synopsis=Invoked before sending a search result reference to the client.
+property.plugin-type.syntax.enumeration.value.shutdown.synopsis=Invoked during a graceful Directory Server shutdown.
+property.plugin-type.syntax.enumeration.value.startup.synopsis=Invoked during the Directory Server startup process.
+property.plugin-type.syntax.enumeration.value.subordinatemodifydn.synopsis=Invoked in the course of moving or renaming an entry subordinate to the target of a modify DN operation.
+property.type.synopsis=Specifies the type of attributes to check for value uniqueness.
diff --git a/opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn.properties b/opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn.properties
new file mode 100644
index 0000000..43c0c8e
--- /dev/null
+++ b/opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Unique Characters Password Validator
+user-friendly-plural-name=Unique Characters Password Validators
+synopsis=The Unique Characters Password Validator is used to determine whether a proposed password is acceptable based on the number of unique characters that it contains.
+description=This validator can be used to prevent simple passwords that contain only a few characters like "aabbcc" or "abcabc".
+property.case-sensitive-validation.synopsis=Indicates whether this password validator should treat password characters in a case-sensitive manner.
+property.case-sensitive-validation.description=A value of true indicates that the validator does not consider a capital letter to be the same as its lower-case counterpart. A value of false indicates that the validator ignores differences in capitalization when looking at the number of unique characters in the password.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.min-unique-characters.synopsis=Specifies the minimum number of unique characters that a password will be allowed to contain.
+property.min-unique-characters.description=A value of zero indicates that no minimum value is enforced.
diff --git a/opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_de.properties b/opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_de.properties
new file mode 100644
index 0000000..43c0c8e
--- /dev/null
+++ b/opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_de.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Unique Characters Password Validator
+user-friendly-plural-name=Unique Characters Password Validators
+synopsis=The Unique Characters Password Validator is used to determine whether a proposed password is acceptable based on the number of unique characters that it contains.
+description=This validator can be used to prevent simple passwords that contain only a few characters like "aabbcc" or "abcabc".
+property.case-sensitive-validation.synopsis=Indicates whether this password validator should treat password characters in a case-sensitive manner.
+property.case-sensitive-validation.description=A value of true indicates that the validator does not consider a capital letter to be the same as its lower-case counterpart. A value of false indicates that the validator ignores differences in capitalization when looking at the number of unique characters in the password.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.min-unique-characters.synopsis=Specifies the minimum number of unique characters that a password will be allowed to contain.
+property.min-unique-characters.description=A value of zero indicates that no minimum value is enforced.
diff --git a/opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_es.properties b/opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_es.properties
new file mode 100644
index 0000000..43c0c8e
--- /dev/null
+++ b/opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_es.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Unique Characters Password Validator
+user-friendly-plural-name=Unique Characters Password Validators
+synopsis=The Unique Characters Password Validator is used to determine whether a proposed password is acceptable based on the number of unique characters that it contains.
+description=This validator can be used to prevent simple passwords that contain only a few characters like "aabbcc" or "abcabc".
+property.case-sensitive-validation.synopsis=Indicates whether this password validator should treat password characters in a case-sensitive manner.
+property.case-sensitive-validation.description=A value of true indicates that the validator does not consider a capital letter to be the same as its lower-case counterpart. A value of false indicates that the validator ignores differences in capitalization when looking at the number of unique characters in the password.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.min-unique-characters.synopsis=Specifies the minimum number of unique characters that a password will be allowed to contain.
+property.min-unique-characters.description=A value of zero indicates that no minimum value is enforced.
diff --git a/opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_fr.properties b/opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_fr.properties
new file mode 100644
index 0000000..43c0c8e
--- /dev/null
+++ b/opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_fr.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Unique Characters Password Validator
+user-friendly-plural-name=Unique Characters Password Validators
+synopsis=The Unique Characters Password Validator is used to determine whether a proposed password is acceptable based on the number of unique characters that it contains.
+description=This validator can be used to prevent simple passwords that contain only a few characters like "aabbcc" or "abcabc".
+property.case-sensitive-validation.synopsis=Indicates whether this password validator should treat password characters in a case-sensitive manner.
+property.case-sensitive-validation.description=A value of true indicates that the validator does not consider a capital letter to be the same as its lower-case counterpart. A value of false indicates that the validator ignores differences in capitalization when looking at the number of unique characters in the password.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.min-unique-characters.synopsis=Specifies the minimum number of unique characters that a password will be allowed to contain.
+property.min-unique-characters.description=A value of zero indicates that no minimum value is enforced.
diff --git a/opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_ja.properties b/opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_ja.properties
new file mode 100644
index 0000000..43c0c8e
--- /dev/null
+++ b/opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_ja.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Unique Characters Password Validator
+user-friendly-plural-name=Unique Characters Password Validators
+synopsis=The Unique Characters Password Validator is used to determine whether a proposed password is acceptable based on the number of unique characters that it contains.
+description=This validator can be used to prevent simple passwords that contain only a few characters like "aabbcc" or "abcabc".
+property.case-sensitive-validation.synopsis=Indicates whether this password validator should treat password characters in a case-sensitive manner.
+property.case-sensitive-validation.description=A value of true indicates that the validator does not consider a capital letter to be the same as its lower-case counterpart. A value of false indicates that the validator ignores differences in capitalization when looking at the number of unique characters in the password.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.min-unique-characters.synopsis=Specifies the minimum number of unique characters that a password will be allowed to contain.
+property.min-unique-characters.description=A value of zero indicates that no minimum value is enforced.
diff --git a/opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_ko.properties b/opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_ko.properties
new file mode 100644
index 0000000..43c0c8e
--- /dev/null
+++ b/opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_ko.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Unique Characters Password Validator
+user-friendly-plural-name=Unique Characters Password Validators
+synopsis=The Unique Characters Password Validator is used to determine whether a proposed password is acceptable based on the number of unique characters that it contains.
+description=This validator can be used to prevent simple passwords that contain only a few characters like "aabbcc" or "abcabc".
+property.case-sensitive-validation.synopsis=Indicates whether this password validator should treat password characters in a case-sensitive manner.
+property.case-sensitive-validation.description=A value of true indicates that the validator does not consider a capital letter to be the same as its lower-case counterpart. A value of false indicates that the validator ignores differences in capitalization when looking at the number of unique characters in the password.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.min-unique-characters.synopsis=Specifies the minimum number of unique characters that a password will be allowed to contain.
+property.min-unique-characters.description=A value of zero indicates that no minimum value is enforced.
diff --git a/opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_zh_CN.properties b/opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..43c0c8e
--- /dev/null
+++ b/opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_zh_CN.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Unique Characters Password Validator
+user-friendly-plural-name=Unique Characters Password Validators
+synopsis=The Unique Characters Password Validator is used to determine whether a proposed password is acceptable based on the number of unique characters that it contains.
+description=This validator can be used to prevent simple passwords that contain only a few characters like "aabbcc" or "abcabc".
+property.case-sensitive-validation.synopsis=Indicates whether this password validator should treat password characters in a case-sensitive manner.
+property.case-sensitive-validation.description=A value of true indicates that the validator does not consider a capital letter to be the same as its lower-case counterpart. A value of false indicates that the validator ignores differences in capitalization when looking at the number of unique characters in the password.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.min-unique-characters.synopsis=Specifies the minimum number of unique characters that a password will be allowed to contain.
+property.min-unique-characters.description=A value of zero indicates that no minimum value is enforced.
diff --git a/opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_zh_TW.properties b/opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..43c0c8e
--- /dev/null
+++ b/opends/src/admin/messages/UniqueCharactersPasswordValidatorCfgDefn_zh_TW.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Unique Characters Password Validator
+user-friendly-plural-name=Unique Characters Password Validators
+synopsis=The Unique Characters Password Validator is used to determine whether a proposed password is acceptable based on the number of unique characters that it contains.
+description=This validator can be used to prevent simple passwords that contain only a few characters like "aabbcc" or "abcabc".
+property.case-sensitive-validation.synopsis=Indicates whether this password validator should treat password characters in a case-sensitive manner.
+property.case-sensitive-validation.description=A value of true indicates that the validator does not consider a capital letter to be the same as its lower-case counterpart. A value of false indicates that the validator ignores differences in capitalization when looking at the number of unique characters in the password.
+property.enabled.synopsis=Indicates whether the password validator is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the password validator implementation.
+property.min-unique-characters.synopsis=Specifies the minimum number of unique characters that a password will be allowed to contain.
+property.min-unique-characters.description=A value of zero indicates that no minimum value is enforced.
diff --git a/opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn.properties b/opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn.properties
new file mode 100644
index 0000000..4f14f2f
--- /dev/null
+++ b/opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn.properties
@@ -0,0 +1,21 @@
+user-friendly-name=User Defined Virtual Attribute
+user-friendly-plural-name=User Defined Virtual Attributes
+synopsis=The User Defined Virtual Attribute creates virtual attributes with user-defined values in entries that match the criteria defined in the plug-in's configuration.
+description=The functionality of these attributes is similar to Class of Service (CoS) in the Sun Java System Directory Server.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the User Defined Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
+property.value.synopsis=Specifies the values to be included in the virtual attribute.
diff --git a/opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_de.properties b/opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_de.properties
new file mode 100644
index 0000000..4f14f2f
--- /dev/null
+++ b/opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_de.properties
@@ -0,0 +1,21 @@
+user-friendly-name=User Defined Virtual Attribute
+user-friendly-plural-name=User Defined Virtual Attributes
+synopsis=The User Defined Virtual Attribute creates virtual attributes with user-defined values in entries that match the criteria defined in the plug-in's configuration.
+description=The functionality of these attributes is similar to Class of Service (CoS) in the Sun Java System Directory Server.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the User Defined Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
+property.value.synopsis=Specifies the values to be included in the virtual attribute.
diff --git a/opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_es.properties b/opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_es.properties
new file mode 100644
index 0000000..4f14f2f
--- /dev/null
+++ b/opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_es.properties
@@ -0,0 +1,21 @@
+user-friendly-name=User Defined Virtual Attribute
+user-friendly-plural-name=User Defined Virtual Attributes
+synopsis=The User Defined Virtual Attribute creates virtual attributes with user-defined values in entries that match the criteria defined in the plug-in's configuration.
+description=The functionality of these attributes is similar to Class of Service (CoS) in the Sun Java System Directory Server.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the User Defined Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
+property.value.synopsis=Specifies the values to be included in the virtual attribute.
diff --git a/opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_fr.properties b/opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_fr.properties
new file mode 100644
index 0000000..4f14f2f
--- /dev/null
+++ b/opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_fr.properties
@@ -0,0 +1,21 @@
+user-friendly-name=User Defined Virtual Attribute
+user-friendly-plural-name=User Defined Virtual Attributes
+synopsis=The User Defined Virtual Attribute creates virtual attributes with user-defined values in entries that match the criteria defined in the plug-in's configuration.
+description=The functionality of these attributes is similar to Class of Service (CoS) in the Sun Java System Directory Server.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the User Defined Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
+property.value.synopsis=Specifies the values to be included in the virtual attribute.
diff --git a/opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_ja.properties b/opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_ja.properties
new file mode 100644
index 0000000..4f14f2f
--- /dev/null
+++ b/opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_ja.properties
@@ -0,0 +1,21 @@
+user-friendly-name=User Defined Virtual Attribute
+user-friendly-plural-name=User Defined Virtual Attributes
+synopsis=The User Defined Virtual Attribute creates virtual attributes with user-defined values in entries that match the criteria defined in the plug-in's configuration.
+description=The functionality of these attributes is similar to Class of Service (CoS) in the Sun Java System Directory Server.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the User Defined Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
+property.value.synopsis=Specifies the values to be included in the virtual attribute.
diff --git a/opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_ko.properties b/opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_ko.properties
new file mode 100644
index 0000000..4f14f2f
--- /dev/null
+++ b/opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_ko.properties
@@ -0,0 +1,21 @@
+user-friendly-name=User Defined Virtual Attribute
+user-friendly-plural-name=User Defined Virtual Attributes
+synopsis=The User Defined Virtual Attribute creates virtual attributes with user-defined values in entries that match the criteria defined in the plug-in's configuration.
+description=The functionality of these attributes is similar to Class of Service (CoS) in the Sun Java System Directory Server.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the User Defined Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
+property.value.synopsis=Specifies the values to be included in the virtual attribute.
diff --git a/opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_zh_CN.properties b/opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..4f14f2f
--- /dev/null
+++ b/opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_zh_CN.properties
@@ -0,0 +1,21 @@
+user-friendly-name=User Defined Virtual Attribute
+user-friendly-plural-name=User Defined Virtual Attributes
+synopsis=The User Defined Virtual Attribute creates virtual attributes with user-defined values in entries that match the criteria defined in the plug-in's configuration.
+description=The functionality of these attributes is similar to Class of Service (CoS) in the Sun Java System Directory Server.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the User Defined Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
+property.value.synopsis=Specifies the values to be included in the virtual attribute.
diff --git a/opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_zh_TW.properties b/opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..4f14f2f
--- /dev/null
+++ b/opends/src/admin/messages/UserDefinedVirtualAttributeCfgDefn_zh_TW.properties
@@ -0,0 +1,21 @@
+user-friendly-name=User Defined Virtual Attribute
+user-friendly-plural-name=User Defined Virtual Attributes
+synopsis=The User Defined Virtual Attribute creates virtual attributes with user-defined values in entries that match the criteria defined in the plug-in's configuration.
+description=The functionality of these attributes is similar to Class of Service (CoS) in the Sun Java System Directory Server.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the User Defined Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
+property.value.synopsis=Specifies the values to be included in the virtual attribute.
diff --git a/opends/src/admin/messages/VersionMonitorProviderCfgDefn.properties b/opends/src/admin/messages/VersionMonitorProviderCfgDefn.properties
new file mode 100644
index 0000000..4492a68
--- /dev/null
+++ b/opends/src/admin/messages/VersionMonitorProviderCfgDefn.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Version Monitor Provider
+user-friendly-plural-name=Version Monitor Providers
+synopsis=The Version Monitor Provider can be used to publish Directory Server version information.
+property.enabled.synopsis=Indicates whether the Version Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Version Monitor Provider implementation.
diff --git a/opends/src/admin/messages/VersionMonitorProviderCfgDefn_de.properties b/opends/src/admin/messages/VersionMonitorProviderCfgDefn_de.properties
new file mode 100644
index 0000000..4492a68
--- /dev/null
+++ b/opends/src/admin/messages/VersionMonitorProviderCfgDefn_de.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Version Monitor Provider
+user-friendly-plural-name=Version Monitor Providers
+synopsis=The Version Monitor Provider can be used to publish Directory Server version information.
+property.enabled.synopsis=Indicates whether the Version Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Version Monitor Provider implementation.
diff --git a/opends/src/admin/messages/VersionMonitorProviderCfgDefn_es.properties b/opends/src/admin/messages/VersionMonitorProviderCfgDefn_es.properties
new file mode 100644
index 0000000..4492a68
--- /dev/null
+++ b/opends/src/admin/messages/VersionMonitorProviderCfgDefn_es.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Version Monitor Provider
+user-friendly-plural-name=Version Monitor Providers
+synopsis=The Version Monitor Provider can be used to publish Directory Server version information.
+property.enabled.synopsis=Indicates whether the Version Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Version Monitor Provider implementation.
diff --git a/opends/src/admin/messages/VersionMonitorProviderCfgDefn_fr.properties b/opends/src/admin/messages/VersionMonitorProviderCfgDefn_fr.properties
new file mode 100644
index 0000000..4492a68
--- /dev/null
+++ b/opends/src/admin/messages/VersionMonitorProviderCfgDefn_fr.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Version Monitor Provider
+user-friendly-plural-name=Version Monitor Providers
+synopsis=The Version Monitor Provider can be used to publish Directory Server version information.
+property.enabled.synopsis=Indicates whether the Version Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Version Monitor Provider implementation.
diff --git a/opends/src/admin/messages/VersionMonitorProviderCfgDefn_ja.properties b/opends/src/admin/messages/VersionMonitorProviderCfgDefn_ja.properties
new file mode 100644
index 0000000..4492a68
--- /dev/null
+++ b/opends/src/admin/messages/VersionMonitorProviderCfgDefn_ja.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Version Monitor Provider
+user-friendly-plural-name=Version Monitor Providers
+synopsis=The Version Monitor Provider can be used to publish Directory Server version information.
+property.enabled.synopsis=Indicates whether the Version Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Version Monitor Provider implementation.
diff --git a/opends/src/admin/messages/VersionMonitorProviderCfgDefn_ko.properties b/opends/src/admin/messages/VersionMonitorProviderCfgDefn_ko.properties
new file mode 100644
index 0000000..4492a68
--- /dev/null
+++ b/opends/src/admin/messages/VersionMonitorProviderCfgDefn_ko.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Version Monitor Provider
+user-friendly-plural-name=Version Monitor Providers
+synopsis=The Version Monitor Provider can be used to publish Directory Server version information.
+property.enabled.synopsis=Indicates whether the Version Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Version Monitor Provider implementation.
diff --git a/opends/src/admin/messages/VersionMonitorProviderCfgDefn_zh_CN.properties b/opends/src/admin/messages/VersionMonitorProviderCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..4492a68
--- /dev/null
+++ b/opends/src/admin/messages/VersionMonitorProviderCfgDefn_zh_CN.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Version Monitor Provider
+user-friendly-plural-name=Version Monitor Providers
+synopsis=The Version Monitor Provider can be used to publish Directory Server version information.
+property.enabled.synopsis=Indicates whether the Version Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Version Monitor Provider implementation.
diff --git a/opends/src/admin/messages/VersionMonitorProviderCfgDefn_zh_TW.properties b/opends/src/admin/messages/VersionMonitorProviderCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..4492a68
--- /dev/null
+++ b/opends/src/admin/messages/VersionMonitorProviderCfgDefn_zh_TW.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Version Monitor Provider
+user-friendly-plural-name=Version Monitor Providers
+synopsis=The Version Monitor Provider can be used to publish Directory Server version information.
+property.enabled.synopsis=Indicates whether the Version Monitor Provider is enabled for use.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Version Monitor Provider implementation.
diff --git a/opends/src/admin/messages/VirtualAttributeCfgDefn.properties b/opends/src/admin/messages/VirtualAttributeCfgDefn.properties
new file mode 100644
index 0000000..93d0756
--- /dev/null
+++ b/opends/src/admin/messages/VirtualAttributeCfgDefn.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Virtual Attribute
+user-friendly-plural-name=Virtual Attributes
+synopsis=Virtual Attributes are responsible for dynamically generating attribute values that appear in entries but are not persistently stored in the backend.
+description=Virtual attributes are associated with a virtual attribute provider, which contains the logic for generating the value.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/VirtualAttributeCfgDefn_de.properties b/opends/src/admin/messages/VirtualAttributeCfgDefn_de.properties
new file mode 100644
index 0000000..93d0756
--- /dev/null
+++ b/opends/src/admin/messages/VirtualAttributeCfgDefn_de.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Virtual Attribute
+user-friendly-plural-name=Virtual Attributes
+synopsis=Virtual Attributes are responsible for dynamically generating attribute values that appear in entries but are not persistently stored in the backend.
+description=Virtual attributes are associated with a virtual attribute provider, which contains the logic for generating the value.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/VirtualAttributeCfgDefn_es.properties b/opends/src/admin/messages/VirtualAttributeCfgDefn_es.properties
new file mode 100644
index 0000000..93d0756
--- /dev/null
+++ b/opends/src/admin/messages/VirtualAttributeCfgDefn_es.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Virtual Attribute
+user-friendly-plural-name=Virtual Attributes
+synopsis=Virtual Attributes are responsible for dynamically generating attribute values that appear in entries but are not persistently stored in the backend.
+description=Virtual attributes are associated with a virtual attribute provider, which contains the logic for generating the value.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/VirtualAttributeCfgDefn_fr.properties b/opends/src/admin/messages/VirtualAttributeCfgDefn_fr.properties
new file mode 100644
index 0000000..93d0756
--- /dev/null
+++ b/opends/src/admin/messages/VirtualAttributeCfgDefn_fr.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Virtual Attribute
+user-friendly-plural-name=Virtual Attributes
+synopsis=Virtual Attributes are responsible for dynamically generating attribute values that appear in entries but are not persistently stored in the backend.
+description=Virtual attributes are associated with a virtual attribute provider, which contains the logic for generating the value.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/VirtualAttributeCfgDefn_ja.properties b/opends/src/admin/messages/VirtualAttributeCfgDefn_ja.properties
new file mode 100644
index 0000000..93d0756
--- /dev/null
+++ b/opends/src/admin/messages/VirtualAttributeCfgDefn_ja.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Virtual Attribute
+user-friendly-plural-name=Virtual Attributes
+synopsis=Virtual Attributes are responsible for dynamically generating attribute values that appear in entries but are not persistently stored in the backend.
+description=Virtual attributes are associated with a virtual attribute provider, which contains the logic for generating the value.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/VirtualAttributeCfgDefn_ko.properties b/opends/src/admin/messages/VirtualAttributeCfgDefn_ko.properties
new file mode 100644
index 0000000..93d0756
--- /dev/null
+++ b/opends/src/admin/messages/VirtualAttributeCfgDefn_ko.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Virtual Attribute
+user-friendly-plural-name=Virtual Attributes
+synopsis=Virtual Attributes are responsible for dynamically generating attribute values that appear in entries but are not persistently stored in the backend.
+description=Virtual attributes are associated with a virtual attribute provider, which contains the logic for generating the value.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/VirtualAttributeCfgDefn_zh_CN.properties b/opends/src/admin/messages/VirtualAttributeCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..93d0756
--- /dev/null
+++ b/opends/src/admin/messages/VirtualAttributeCfgDefn_zh_CN.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Virtual Attribute
+user-friendly-plural-name=Virtual Attributes
+synopsis=Virtual Attributes are responsible for dynamically generating attribute values that appear in entries but are not persistently stored in the backend.
+description=Virtual attributes are associated with a virtual attribute provider, which contains the logic for generating the value.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/VirtualAttributeCfgDefn_zh_TW.properties b/opends/src/admin/messages/VirtualAttributeCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..93d0756
--- /dev/null
+++ b/opends/src/admin/messages/VirtualAttributeCfgDefn_zh_TW.properties
@@ -0,0 +1,20 @@
+user-friendly-name=Virtual Attribute
+user-friendly-plural-name=Virtual Attributes
+synopsis=Virtual Attributes are responsible for dynamically generating attribute values that appear in entries but are not persistently stored in the backend.
+description=Virtual attributes are associated with a virtual attribute provider, which contains the logic for generating the value.
+property.attribute-type.synopsis=Specifies the attribute type for the attribute whose values are to be dynamically assigned by the virtual attribute.
+property.base-dn.synopsis=Specifies the base DNs for the branches containing entries that are eligible to use this virtual attribute.
+property.base-dn.description=If no values are given, then the server generates virtual attributes anywhere in the server.
+property.base-dn.default-behavior.alias.synopsis=The location of the entry in the server is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.conflict-behavior.synopsis=Specifies the behavior that the server is to exhibit for entries that already contain one or more real values for the associated attribute.
+property.conflict-behavior.syntax.enumeration.value.merge-real-and-virtual.synopsis=Indicates that the virtual attribute provider is to preserve any real values contained in the entry and merge them with the set of generated virtual values so that both the real and virtual values are used.
+property.conflict-behavior.syntax.enumeration.value.real-overrides-virtual.synopsis=Indicates that any real values contained in the entry are preserved and used, and virtual values are not generated.
+property.conflict-behavior.syntax.enumeration.value.virtual-overrides-real.synopsis=Indicates that the virtual attribute provider suppresses any real values contained in the entry and generates virtual values and uses them.
+property.enabled.synopsis=Indicates whether the Virtual Attribute is enabled for use.
+property.filter.synopsis=Specifies the search filters to be applied against entries to determine if the virtual attribute is to be generated for those entries.
+property.filter.description=If no values are given, then any entry is eligible to have the value generated. If one or more filters are specified, then only entries that match at least one of those filters are allowed to have the virtual attribute.
+property.filter.syntax.string.pattern.synopsis=Any valid search filter string.
+property.group-dn.synopsis=Specifies the DNs of the groups whose members can be eligible to use this virtual attribute.
+property.group-dn.description=If no values are given, then group membership is not taken into account when generating the virtual attribute. If one or more group DNs are specified, then only members of those groups are allowed to have the virtual attribute.
+property.group-dn.default-behavior.alias.synopsis=Group membership is not taken into account when determining whether an entry is eligible to use this virtual attribute.
+property.java-class.synopsis=Specifies the fully-qualified name of the virtual attribute provider class that generates the attribute values.
diff --git a/opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn.properties b/opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn.properties
new file mode 100644
index 0000000..a73b4e0
--- /dev/null
+++ b/opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Virtual Static Group Implementation
+user-friendly-plural-name=Virtual Static Group Implementations
+synopsis=The Virtual Static Group Implementation provides a grouping mechanism in which the membership for the virtual static group is based on the membership for another group defined within the server.
+description=The primary benefit of virtual static groups is that they make it possible to present other types of groups (for example, dynamic groups) as if they were static groups for the benefit of applications that do not support alternate grouping mechanisms.
+property.enabled.synopsis=Indicates whether the Virtual Static Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Virtual Static Group Implementation implementation.
diff --git a/opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_de.properties b/opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_de.properties
new file mode 100644
index 0000000..a73b4e0
--- /dev/null
+++ b/opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_de.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Virtual Static Group Implementation
+user-friendly-plural-name=Virtual Static Group Implementations
+synopsis=The Virtual Static Group Implementation provides a grouping mechanism in which the membership for the virtual static group is based on the membership for another group defined within the server.
+description=The primary benefit of virtual static groups is that they make it possible to present other types of groups (for example, dynamic groups) as if they were static groups for the benefit of applications that do not support alternate grouping mechanisms.
+property.enabled.synopsis=Indicates whether the Virtual Static Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Virtual Static Group Implementation implementation.
diff --git a/opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_es.properties b/opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_es.properties
new file mode 100644
index 0000000..a73b4e0
--- /dev/null
+++ b/opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_es.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Virtual Static Group Implementation
+user-friendly-plural-name=Virtual Static Group Implementations
+synopsis=The Virtual Static Group Implementation provides a grouping mechanism in which the membership for the virtual static group is based on the membership for another group defined within the server.
+description=The primary benefit of virtual static groups is that they make it possible to present other types of groups (for example, dynamic groups) as if they were static groups for the benefit of applications that do not support alternate grouping mechanisms.
+property.enabled.synopsis=Indicates whether the Virtual Static Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Virtual Static Group Implementation implementation.
diff --git a/opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_fr.properties b/opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_fr.properties
new file mode 100644
index 0000000..a73b4e0
--- /dev/null
+++ b/opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_fr.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Virtual Static Group Implementation
+user-friendly-plural-name=Virtual Static Group Implementations
+synopsis=The Virtual Static Group Implementation provides a grouping mechanism in which the membership for the virtual static group is based on the membership for another group defined within the server.
+description=The primary benefit of virtual static groups is that they make it possible to present other types of groups (for example, dynamic groups) as if they were static groups for the benefit of applications that do not support alternate grouping mechanisms.
+property.enabled.synopsis=Indicates whether the Virtual Static Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Virtual Static Group Implementation implementation.
diff --git a/opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_ja.properties b/opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_ja.properties
new file mode 100644
index 0000000..a73b4e0
--- /dev/null
+++ b/opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_ja.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Virtual Static Group Implementation
+user-friendly-plural-name=Virtual Static Group Implementations
+synopsis=The Virtual Static Group Implementation provides a grouping mechanism in which the membership for the virtual static group is based on the membership for another group defined within the server.
+description=The primary benefit of virtual static groups is that they make it possible to present other types of groups (for example, dynamic groups) as if they were static groups for the benefit of applications that do not support alternate grouping mechanisms.
+property.enabled.synopsis=Indicates whether the Virtual Static Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Virtual Static Group Implementation implementation.
diff --git a/opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_ko.properties b/opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_ko.properties
new file mode 100644
index 0000000..a73b4e0
--- /dev/null
+++ b/opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_ko.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Virtual Static Group Implementation
+user-friendly-plural-name=Virtual Static Group Implementations
+synopsis=The Virtual Static Group Implementation provides a grouping mechanism in which the membership for the virtual static group is based on the membership for another group defined within the server.
+description=The primary benefit of virtual static groups is that they make it possible to present other types of groups (for example, dynamic groups) as if they were static groups for the benefit of applications that do not support alternate grouping mechanisms.
+property.enabled.synopsis=Indicates whether the Virtual Static Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Virtual Static Group Implementation implementation.
diff --git a/opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_zh_CN.properties b/opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..a73b4e0
--- /dev/null
+++ b/opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_zh_CN.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Virtual Static Group Implementation
+user-friendly-plural-name=Virtual Static Group Implementations
+synopsis=The Virtual Static Group Implementation provides a grouping mechanism in which the membership for the virtual static group is based on the membership for another group defined within the server.
+description=The primary benefit of virtual static groups is that they make it possible to present other types of groups (for example, dynamic groups) as if they were static groups for the benefit of applications that do not support alternate grouping mechanisms.
+property.enabled.synopsis=Indicates whether the Virtual Static Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Virtual Static Group Implementation implementation.
diff --git a/opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_zh_TW.properties b/opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..a73b4e0
--- /dev/null
+++ b/opends/src/admin/messages/VirtualStaticGroupImplementationCfgDefn_zh_TW.properties
@@ -0,0 +1,6 @@
+user-friendly-name=Virtual Static Group Implementation
+user-friendly-plural-name=Virtual Static Group Implementations
+synopsis=The Virtual Static Group Implementation provides a grouping mechanism in which the membership for the virtual static group is based on the membership for another group defined within the server.
+description=The primary benefit of virtual static groups is that they make it possible to present other types of groups (for example, dynamic groups) as if they were static groups for the benefit of applications that do not support alternate grouping mechanisms.
+property.enabled.synopsis=Indicates whether the Virtual Static Group Implementation is enabled.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Virtual Static Group Implementation implementation.
diff --git a/opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn.properties b/opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn.properties
new file mode 100644
index 0000000..4c89328
--- /dev/null
+++ b/opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Who Am I Extended Operation Handler
+user-friendly-plural-name=Who Am I Extended Operation Handlers
+synopsis=The Who Am I Extended Operation Handler provides the ability for clients to request their authorization identity using the "Who Am I?" extended operation as defined in RFC 4532.
+property.enabled.synopsis=Indicates whether the Who Am I Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Who Am I Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_de.properties b/opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_de.properties
new file mode 100644
index 0000000..4c89328
--- /dev/null
+++ b/opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_de.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Who Am I Extended Operation Handler
+user-friendly-plural-name=Who Am I Extended Operation Handlers
+synopsis=The Who Am I Extended Operation Handler provides the ability for clients to request their authorization identity using the "Who Am I?" extended operation as defined in RFC 4532.
+property.enabled.synopsis=Indicates whether the Who Am I Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Who Am I Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_es.properties b/opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_es.properties
new file mode 100644
index 0000000..4c89328
--- /dev/null
+++ b/opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_es.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Who Am I Extended Operation Handler
+user-friendly-plural-name=Who Am I Extended Operation Handlers
+synopsis=The Who Am I Extended Operation Handler provides the ability for clients to request their authorization identity using the "Who Am I?" extended operation as defined in RFC 4532.
+property.enabled.synopsis=Indicates whether the Who Am I Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Who Am I Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_fr.properties b/opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_fr.properties
new file mode 100644
index 0000000..4c89328
--- /dev/null
+++ b/opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_fr.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Who Am I Extended Operation Handler
+user-friendly-plural-name=Who Am I Extended Operation Handlers
+synopsis=The Who Am I Extended Operation Handler provides the ability for clients to request their authorization identity using the "Who Am I?" extended operation as defined in RFC 4532.
+property.enabled.synopsis=Indicates whether the Who Am I Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Who Am I Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_ja.properties b/opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_ja.properties
new file mode 100644
index 0000000..4c89328
--- /dev/null
+++ b/opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_ja.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Who Am I Extended Operation Handler
+user-friendly-plural-name=Who Am I Extended Operation Handlers
+synopsis=The Who Am I Extended Operation Handler provides the ability for clients to request their authorization identity using the "Who Am I?" extended operation as defined in RFC 4532.
+property.enabled.synopsis=Indicates whether the Who Am I Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Who Am I Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_ko.properties b/opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_ko.properties
new file mode 100644
index 0000000..4c89328
--- /dev/null
+++ b/opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_ko.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Who Am I Extended Operation Handler
+user-friendly-plural-name=Who Am I Extended Operation Handlers
+synopsis=The Who Am I Extended Operation Handler provides the ability for clients to request their authorization identity using the "Who Am I?" extended operation as defined in RFC 4532.
+property.enabled.synopsis=Indicates whether the Who Am I Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Who Am I Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_zh_CN.properties b/opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..4c89328
--- /dev/null
+++ b/opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_zh_CN.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Who Am I Extended Operation Handler
+user-friendly-plural-name=Who Am I Extended Operation Handlers
+synopsis=The Who Am I Extended Operation Handler provides the ability for clients to request their authorization identity using the "Who Am I?" extended operation as defined in RFC 4532.
+property.enabled.synopsis=Indicates whether the Who Am I Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Who Am I Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_zh_TW.properties b/opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..4c89328
--- /dev/null
+++ b/opends/src/admin/messages/WhoAmIExtendedOperationHandlerCfgDefn_zh_TW.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Who Am I Extended Operation Handler
+user-friendly-plural-name=Who Am I Extended Operation Handlers
+synopsis=The Who Am I Extended Operation Handler provides the ability for clients to request their authorization identity using the "Who Am I?" extended operation as defined in RFC 4532.
+property.enabled.synopsis=Indicates whether the Who Am I Extended Operation Handler is enabled (that is, whether the types of extended operations are allowed in the server).
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Who Am I Extended Operation Handler implementation.
diff --git a/opends/src/admin/messages/WorkQueueCfgDefn.properties b/opends/src/admin/messages/WorkQueueCfgDefn.properties
new file mode 100644
index 0000000..bff9ac4
--- /dev/null
+++ b/opends/src/admin/messages/WorkQueueCfgDefn.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Work Queue
+user-friendly-plural-name=Work Queues
+synopsis=The Work Queue provides the configuration for the server work queue and is responsible for ensuring that requests received from clients are processed in a timely manner.
+description=Only a single work queue can be defined in the server. Whenever a connection handler receives a client request, it should place the request in the work queue to be processed appropriately.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Work Queue implementation.
diff --git a/opends/src/admin/messages/WorkQueueCfgDefn_de.properties b/opends/src/admin/messages/WorkQueueCfgDefn_de.properties
new file mode 100644
index 0000000..bff9ac4
--- /dev/null
+++ b/opends/src/admin/messages/WorkQueueCfgDefn_de.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Work Queue
+user-friendly-plural-name=Work Queues
+synopsis=The Work Queue provides the configuration for the server work queue and is responsible for ensuring that requests received from clients are processed in a timely manner.
+description=Only a single work queue can be defined in the server. Whenever a connection handler receives a client request, it should place the request in the work queue to be processed appropriately.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Work Queue implementation.
diff --git a/opends/src/admin/messages/WorkQueueCfgDefn_es.properties b/opends/src/admin/messages/WorkQueueCfgDefn_es.properties
new file mode 100644
index 0000000..bff9ac4
--- /dev/null
+++ b/opends/src/admin/messages/WorkQueueCfgDefn_es.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Work Queue
+user-friendly-plural-name=Work Queues
+synopsis=The Work Queue provides the configuration for the server work queue and is responsible for ensuring that requests received from clients are processed in a timely manner.
+description=Only a single work queue can be defined in the server. Whenever a connection handler receives a client request, it should place the request in the work queue to be processed appropriately.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Work Queue implementation.
diff --git a/opends/src/admin/messages/WorkQueueCfgDefn_fr.properties b/opends/src/admin/messages/WorkQueueCfgDefn_fr.properties
new file mode 100644
index 0000000..bff9ac4
--- /dev/null
+++ b/opends/src/admin/messages/WorkQueueCfgDefn_fr.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Work Queue
+user-friendly-plural-name=Work Queues
+synopsis=The Work Queue provides the configuration for the server work queue and is responsible for ensuring that requests received from clients are processed in a timely manner.
+description=Only a single work queue can be defined in the server. Whenever a connection handler receives a client request, it should place the request in the work queue to be processed appropriately.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Work Queue implementation.
diff --git a/opends/src/admin/messages/WorkQueueCfgDefn_ja.properties b/opends/src/admin/messages/WorkQueueCfgDefn_ja.properties
new file mode 100644
index 0000000..bff9ac4
--- /dev/null
+++ b/opends/src/admin/messages/WorkQueueCfgDefn_ja.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Work Queue
+user-friendly-plural-name=Work Queues
+synopsis=The Work Queue provides the configuration for the server work queue and is responsible for ensuring that requests received from clients are processed in a timely manner.
+description=Only a single work queue can be defined in the server. Whenever a connection handler receives a client request, it should place the request in the work queue to be processed appropriately.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Work Queue implementation.
diff --git a/opends/src/admin/messages/WorkQueueCfgDefn_ko.properties b/opends/src/admin/messages/WorkQueueCfgDefn_ko.properties
new file mode 100644
index 0000000..bff9ac4
--- /dev/null
+++ b/opends/src/admin/messages/WorkQueueCfgDefn_ko.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Work Queue
+user-friendly-plural-name=Work Queues
+synopsis=The Work Queue provides the configuration for the server work queue and is responsible for ensuring that requests received from clients are processed in a timely manner.
+description=Only a single work queue can be defined in the server. Whenever a connection handler receives a client request, it should place the request in the work queue to be processed appropriately.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Work Queue implementation.
diff --git a/opends/src/admin/messages/WorkQueueCfgDefn_zh_CN.properties b/opends/src/admin/messages/WorkQueueCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..bff9ac4
--- /dev/null
+++ b/opends/src/admin/messages/WorkQueueCfgDefn_zh_CN.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Work Queue
+user-friendly-plural-name=Work Queues
+synopsis=The Work Queue provides the configuration for the server work queue and is responsible for ensuring that requests received from clients are processed in a timely manner.
+description=Only a single work queue can be defined in the server. Whenever a connection handler receives a client request, it should place the request in the work queue to be processed appropriately.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Work Queue implementation.
diff --git a/opends/src/admin/messages/WorkQueueCfgDefn_zh_TW.properties b/opends/src/admin/messages/WorkQueueCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..bff9ac4
--- /dev/null
+++ b/opends/src/admin/messages/WorkQueueCfgDefn_zh_TW.properties
@@ -0,0 +1,5 @@
+user-friendly-name=Work Queue
+user-friendly-plural-name=Work Queues
+synopsis=The Work Queue provides the configuration for the server work queue and is responsible for ensuring that requests received from clients are processed in a timely manner.
+description=Only a single work queue can be defined in the server. Whenever a connection handler receives a client request, it should place the request in the work queue to be processed appropriately.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Work Queue implementation.
diff --git a/opends/src/admin/messages/WorkflowCfgDefn.properties b/opends/src/admin/messages/WorkflowCfgDefn.properties
new file mode 100644
index 0000000..be4bae6
--- /dev/null
+++ b/opends/src/admin/messages/WorkflowCfgDefn.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Workflow
+user-friendly-plural-name=Workflows
+synopsis=The Workflow is a list of processing steps (Work Flow Elements) that are applied to data as it is retrieved from the Directory Server.
+property.base-dn.synopsis=Specifies the base DN of the data targeted by the Workflow .
+property.enabled.synopsis=Indicates whether the Workflow is enabled for use in the server.
+property.enabled.description=If a Workflow is not enabled, then its contents are not accessible when processing operations.
+property.workflow-element.synopsis=Specifies the root Work Flow Element in the Workflow .
+property.workflow-element.syntax.aggregation.constraint-synopsis=The referenced workflow element must be enabled.
+property.workflow-id.synopsis=Provides a name that identifies the Workflow.
+property.workflow-id.description=The name must be unique among all Workflows in the server.
diff --git a/opends/src/admin/messages/WorkflowCfgDefn_de.properties b/opends/src/admin/messages/WorkflowCfgDefn_de.properties
new file mode 100644
index 0000000..be4bae6
--- /dev/null
+++ b/opends/src/admin/messages/WorkflowCfgDefn_de.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Workflow
+user-friendly-plural-name=Workflows
+synopsis=The Workflow is a list of processing steps (Work Flow Elements) that are applied to data as it is retrieved from the Directory Server.
+property.base-dn.synopsis=Specifies the base DN of the data targeted by the Workflow .
+property.enabled.synopsis=Indicates whether the Workflow is enabled for use in the server.
+property.enabled.description=If a Workflow is not enabled, then its contents are not accessible when processing operations.
+property.workflow-element.synopsis=Specifies the root Work Flow Element in the Workflow .
+property.workflow-element.syntax.aggregation.constraint-synopsis=The referenced workflow element must be enabled.
+property.workflow-id.synopsis=Provides a name that identifies the Workflow.
+property.workflow-id.description=The name must be unique among all Workflows in the server.
diff --git a/opends/src/admin/messages/WorkflowCfgDefn_es.properties b/opends/src/admin/messages/WorkflowCfgDefn_es.properties
new file mode 100644
index 0000000..be4bae6
--- /dev/null
+++ b/opends/src/admin/messages/WorkflowCfgDefn_es.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Workflow
+user-friendly-plural-name=Workflows
+synopsis=The Workflow is a list of processing steps (Work Flow Elements) that are applied to data as it is retrieved from the Directory Server.
+property.base-dn.synopsis=Specifies the base DN of the data targeted by the Workflow .
+property.enabled.synopsis=Indicates whether the Workflow is enabled for use in the server.
+property.enabled.description=If a Workflow is not enabled, then its contents are not accessible when processing operations.
+property.workflow-element.synopsis=Specifies the root Work Flow Element in the Workflow .
+property.workflow-element.syntax.aggregation.constraint-synopsis=The referenced workflow element must be enabled.
+property.workflow-id.synopsis=Provides a name that identifies the Workflow.
+property.workflow-id.description=The name must be unique among all Workflows in the server.
diff --git a/opends/src/admin/messages/WorkflowCfgDefn_fr.properties b/opends/src/admin/messages/WorkflowCfgDefn_fr.properties
new file mode 100644
index 0000000..be4bae6
--- /dev/null
+++ b/opends/src/admin/messages/WorkflowCfgDefn_fr.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Workflow
+user-friendly-plural-name=Workflows
+synopsis=The Workflow is a list of processing steps (Work Flow Elements) that are applied to data as it is retrieved from the Directory Server.
+property.base-dn.synopsis=Specifies the base DN of the data targeted by the Workflow .
+property.enabled.synopsis=Indicates whether the Workflow is enabled for use in the server.
+property.enabled.description=If a Workflow is not enabled, then its contents are not accessible when processing operations.
+property.workflow-element.synopsis=Specifies the root Work Flow Element in the Workflow .
+property.workflow-element.syntax.aggregation.constraint-synopsis=The referenced workflow element must be enabled.
+property.workflow-id.synopsis=Provides a name that identifies the Workflow.
+property.workflow-id.description=The name must be unique among all Workflows in the server.
diff --git a/opends/src/admin/messages/WorkflowCfgDefn_ja.properties b/opends/src/admin/messages/WorkflowCfgDefn_ja.properties
new file mode 100644
index 0000000..be4bae6
--- /dev/null
+++ b/opends/src/admin/messages/WorkflowCfgDefn_ja.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Workflow
+user-friendly-plural-name=Workflows
+synopsis=The Workflow is a list of processing steps (Work Flow Elements) that are applied to data as it is retrieved from the Directory Server.
+property.base-dn.synopsis=Specifies the base DN of the data targeted by the Workflow .
+property.enabled.synopsis=Indicates whether the Workflow is enabled for use in the server.
+property.enabled.description=If a Workflow is not enabled, then its contents are not accessible when processing operations.
+property.workflow-element.synopsis=Specifies the root Work Flow Element in the Workflow .
+property.workflow-element.syntax.aggregation.constraint-synopsis=The referenced workflow element must be enabled.
+property.workflow-id.synopsis=Provides a name that identifies the Workflow.
+property.workflow-id.description=The name must be unique among all Workflows in the server.
diff --git a/opends/src/admin/messages/WorkflowCfgDefn_ko.properties b/opends/src/admin/messages/WorkflowCfgDefn_ko.properties
new file mode 100644
index 0000000..be4bae6
--- /dev/null
+++ b/opends/src/admin/messages/WorkflowCfgDefn_ko.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Workflow
+user-friendly-plural-name=Workflows
+synopsis=The Workflow is a list of processing steps (Work Flow Elements) that are applied to data as it is retrieved from the Directory Server.
+property.base-dn.synopsis=Specifies the base DN of the data targeted by the Workflow .
+property.enabled.synopsis=Indicates whether the Workflow is enabled for use in the server.
+property.enabled.description=If a Workflow is not enabled, then its contents are not accessible when processing operations.
+property.workflow-element.synopsis=Specifies the root Work Flow Element in the Workflow .
+property.workflow-element.syntax.aggregation.constraint-synopsis=The referenced workflow element must be enabled.
+property.workflow-id.synopsis=Provides a name that identifies the Workflow.
+property.workflow-id.description=The name must be unique among all Workflows in the server.
diff --git a/opends/src/admin/messages/WorkflowCfgDefn_zh_CN.properties b/opends/src/admin/messages/WorkflowCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..be4bae6
--- /dev/null
+++ b/opends/src/admin/messages/WorkflowCfgDefn_zh_CN.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Workflow
+user-friendly-plural-name=Workflows
+synopsis=The Workflow is a list of processing steps (Work Flow Elements) that are applied to data as it is retrieved from the Directory Server.
+property.base-dn.synopsis=Specifies the base DN of the data targeted by the Workflow .
+property.enabled.synopsis=Indicates whether the Workflow is enabled for use in the server.
+property.enabled.description=If a Workflow is not enabled, then its contents are not accessible when processing operations.
+property.workflow-element.synopsis=Specifies the root Work Flow Element in the Workflow .
+property.workflow-element.syntax.aggregation.constraint-synopsis=The referenced workflow element must be enabled.
+property.workflow-id.synopsis=Provides a name that identifies the Workflow.
+property.workflow-id.description=The name must be unique among all Workflows in the server.
diff --git a/opends/src/admin/messages/WorkflowCfgDefn_zh_TW.properties b/opends/src/admin/messages/WorkflowCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..be4bae6
--- /dev/null
+++ b/opends/src/admin/messages/WorkflowCfgDefn_zh_TW.properties
@@ -0,0 +1,10 @@
+user-friendly-name=Workflow
+user-friendly-plural-name=Workflows
+synopsis=The Workflow is a list of processing steps (Work Flow Elements) that are applied to data as it is retrieved from the Directory Server.
+property.base-dn.synopsis=Specifies the base DN of the data targeted by the Workflow .
+property.enabled.synopsis=Indicates whether the Workflow is enabled for use in the server.
+property.enabled.description=If a Workflow is not enabled, then its contents are not accessible when processing operations.
+property.workflow-element.synopsis=Specifies the root Work Flow Element in the Workflow .
+property.workflow-element.syntax.aggregation.constraint-synopsis=The referenced workflow element must be enabled.
+property.workflow-id.synopsis=Provides a name that identifies the Workflow.
+property.workflow-id.description=The name must be unique among all Workflows in the server.
diff --git a/opends/src/admin/messages/WorkflowElementCfgDefn.properties b/opends/src/admin/messages/WorkflowElementCfgDefn.properties
new file mode 100644
index 0000000..2904e2e
--- /dev/null
+++ b/opends/src/admin/messages/WorkflowElementCfgDefn.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Workflow Element
+user-friendly-plural-name=Workflow Elements
+synopsis=Workflow Elements implement a single processing step in a Work Flow.
+description=A Workflow Element can perform a task such as mapping DNs, renaming attributes, filtering attributes, joining data sources, proxying, or load-balancing. The simplest Workflow Element is the Local Backend Work Flow Element, which routes data to a Backend.
+property.enabled.synopsis=Indicates whether the Workflow Element is enabled for use in the server.
+property.enabled.description=If a Workflow Element is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Workflow Element implementation.
+property.workflow-element-id.synopsis=Provides a name that identifies the associated Workflow Element .
+property.workflow-element-id.description=The name must be unique among all Workflow Elements in the server.
diff --git a/opends/src/admin/messages/WorkflowElementCfgDefn_de.properties b/opends/src/admin/messages/WorkflowElementCfgDefn_de.properties
new file mode 100644
index 0000000..2904e2e
--- /dev/null
+++ b/opends/src/admin/messages/WorkflowElementCfgDefn_de.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Workflow Element
+user-friendly-plural-name=Workflow Elements
+synopsis=Workflow Elements implement a single processing step in a Work Flow.
+description=A Workflow Element can perform a task such as mapping DNs, renaming attributes, filtering attributes, joining data sources, proxying, or load-balancing. The simplest Workflow Element is the Local Backend Work Flow Element, which routes data to a Backend.
+property.enabled.synopsis=Indicates whether the Workflow Element is enabled for use in the server.
+property.enabled.description=If a Workflow Element is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Workflow Element implementation.
+property.workflow-element-id.synopsis=Provides a name that identifies the associated Workflow Element .
+property.workflow-element-id.description=The name must be unique among all Workflow Elements in the server.
diff --git a/opends/src/admin/messages/WorkflowElementCfgDefn_es.properties b/opends/src/admin/messages/WorkflowElementCfgDefn_es.properties
new file mode 100644
index 0000000..2904e2e
--- /dev/null
+++ b/opends/src/admin/messages/WorkflowElementCfgDefn_es.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Workflow Element
+user-friendly-plural-name=Workflow Elements
+synopsis=Workflow Elements implement a single processing step in a Work Flow.
+description=A Workflow Element can perform a task such as mapping DNs, renaming attributes, filtering attributes, joining data sources, proxying, or load-balancing. The simplest Workflow Element is the Local Backend Work Flow Element, which routes data to a Backend.
+property.enabled.synopsis=Indicates whether the Workflow Element is enabled for use in the server.
+property.enabled.description=If a Workflow Element is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Workflow Element implementation.
+property.workflow-element-id.synopsis=Provides a name that identifies the associated Workflow Element .
+property.workflow-element-id.description=The name must be unique among all Workflow Elements in the server.
diff --git a/opends/src/admin/messages/WorkflowElementCfgDefn_fr.properties b/opends/src/admin/messages/WorkflowElementCfgDefn_fr.properties
new file mode 100644
index 0000000..2904e2e
--- /dev/null
+++ b/opends/src/admin/messages/WorkflowElementCfgDefn_fr.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Workflow Element
+user-friendly-plural-name=Workflow Elements
+synopsis=Workflow Elements implement a single processing step in a Work Flow.
+description=A Workflow Element can perform a task such as mapping DNs, renaming attributes, filtering attributes, joining data sources, proxying, or load-balancing. The simplest Workflow Element is the Local Backend Work Flow Element, which routes data to a Backend.
+property.enabled.synopsis=Indicates whether the Workflow Element is enabled for use in the server.
+property.enabled.description=If a Workflow Element is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Workflow Element implementation.
+property.workflow-element-id.synopsis=Provides a name that identifies the associated Workflow Element .
+property.workflow-element-id.description=The name must be unique among all Workflow Elements in the server.
diff --git a/opends/src/admin/messages/WorkflowElementCfgDefn_ja.properties b/opends/src/admin/messages/WorkflowElementCfgDefn_ja.properties
new file mode 100644
index 0000000..2904e2e
--- /dev/null
+++ b/opends/src/admin/messages/WorkflowElementCfgDefn_ja.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Workflow Element
+user-friendly-plural-name=Workflow Elements
+synopsis=Workflow Elements implement a single processing step in a Work Flow.
+description=A Workflow Element can perform a task such as mapping DNs, renaming attributes, filtering attributes, joining data sources, proxying, or load-balancing. The simplest Workflow Element is the Local Backend Work Flow Element, which routes data to a Backend.
+property.enabled.synopsis=Indicates whether the Workflow Element is enabled for use in the server.
+property.enabled.description=If a Workflow Element is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Workflow Element implementation.
+property.workflow-element-id.synopsis=Provides a name that identifies the associated Workflow Element .
+property.workflow-element-id.description=The name must be unique among all Workflow Elements in the server.
diff --git a/opends/src/admin/messages/WorkflowElementCfgDefn_ko.properties b/opends/src/admin/messages/WorkflowElementCfgDefn_ko.properties
new file mode 100644
index 0000000..2904e2e
--- /dev/null
+++ b/opends/src/admin/messages/WorkflowElementCfgDefn_ko.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Workflow Element
+user-friendly-plural-name=Workflow Elements
+synopsis=Workflow Elements implement a single processing step in a Work Flow.
+description=A Workflow Element can perform a task such as mapping DNs, renaming attributes, filtering attributes, joining data sources, proxying, or load-balancing. The simplest Workflow Element is the Local Backend Work Flow Element, which routes data to a Backend.
+property.enabled.synopsis=Indicates whether the Workflow Element is enabled for use in the server.
+property.enabled.description=If a Workflow Element is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Workflow Element implementation.
+property.workflow-element-id.synopsis=Provides a name that identifies the associated Workflow Element .
+property.workflow-element-id.description=The name must be unique among all Workflow Elements in the server.
diff --git a/opends/src/admin/messages/WorkflowElementCfgDefn_zh_CN.properties b/opends/src/admin/messages/WorkflowElementCfgDefn_zh_CN.properties
new file mode 100644
index 0000000..2904e2e
--- /dev/null
+++ b/opends/src/admin/messages/WorkflowElementCfgDefn_zh_CN.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Workflow Element
+user-friendly-plural-name=Workflow Elements
+synopsis=Workflow Elements implement a single processing step in a Work Flow.
+description=A Workflow Element can perform a task such as mapping DNs, renaming attributes, filtering attributes, joining data sources, proxying, or load-balancing. The simplest Workflow Element is the Local Backend Work Flow Element, which routes data to a Backend.
+property.enabled.synopsis=Indicates whether the Workflow Element is enabled for use in the server.
+property.enabled.description=If a Workflow Element is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Workflow Element implementation.
+property.workflow-element-id.synopsis=Provides a name that identifies the associated Workflow Element .
+property.workflow-element-id.description=The name must be unique among all Workflow Elements in the server.
diff --git a/opends/src/admin/messages/WorkflowElementCfgDefn_zh_TW.properties b/opends/src/admin/messages/WorkflowElementCfgDefn_zh_TW.properties
new file mode 100644
index 0000000..2904e2e
--- /dev/null
+++ b/opends/src/admin/messages/WorkflowElementCfgDefn_zh_TW.properties
@@ -0,0 +1,9 @@
+user-friendly-name=Workflow Element
+user-friendly-plural-name=Workflow Elements
+synopsis=Workflow Elements implement a single processing step in a Work Flow.
+description=A Workflow Element can perform a task such as mapping DNs, renaming attributes, filtering attributes, joining data sources, proxying, or load-balancing. The simplest Workflow Element is the Local Backend Work Flow Element, which routes data to a Backend.
+property.enabled.synopsis=Indicates whether the Workflow Element is enabled for use in the server.
+property.enabled.description=If a Workflow Element is not enabled, then its contents are not accessible when processing operations.
+property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Workflow Element implementation.
+property.workflow-element-id.synopsis=Provides a name that identifies the associated Workflow Element .
+property.workflow-element-id.description=The name must be unique among all Workflow Elements in the server.
--
Gitblit v1.10.0