From f73b655466092169abac34833fb628fce1fcdebe Mon Sep 17 00:00:00 2001
From: jcduff <jcduff@localhost>
Date: Thu, 23 Oct 2008 14:04:24 +0000
Subject: [PATCH] The commit will bring the following features : - An updated version of the underlying database. BDB JE 3.3 is now used. - Attribute API refactoring providing a better abstraction and offering improved performances. - A new GUI called the Control-Panel to replace the Status-Panel: the specifications for this GUI are available on OpenDS Wiki and contains a link to a mockup. See <https://www.opends.org/wiki/page/ControlPanelUISpecification>. - Some changes in the replication protocol to implement "Assured Replication Mode". The specifications are on OpenDS Wiki at <https://www.opends.org/wiki/page/AssuredMode> and section 7 described some of the replication changes required to support this. Assured Replication is not finished, but the main replication protocol changes to support it are done. As explained by Gilles on an email on the Dev mailing list (http://markmail.org/message/46rgo3meq3vriy4a), with these changes the newer versions of OpenDS may not be able to replicate with OpenDS 1.0 instances. - Support for Service Tags on the platforms where the functionality is available and enabled. Specifications are published at <https://www.opends.org/wiki/page/OpenDSServiceTagEnabled>. For more information on Service Tags see <http://wikis.sun.com/display/ServiceTag/Sun+Service+Tag+FAQ>. - The Admin Connector service. In order to provide agentry of the OpenDS server at any time, a new service has been added, dedicated to the administration, configuration and monitoring of the server. An overview of the Admin Connector service and it's use is available on the OpenDS wiki <https://www.opends.org/wiki/page/ManagingAdministrationTrafficToTheServer> - Updates to the various command line tools to support the Admin Connector service. - Some internal re-architecting of the server to put the foundation of future developments such as virtual directory services. The new NetworkGroups and WorkFlow internal services which have been specified in <https://www.opends.org/wiki/page/BasicOperationRoutingThroughNetworkGroup> are now implemented. - Many bug fixes...
---
opends/src/server/org/opends/server/core/ConnectionHandlerConfigManager.java | 40 +++++++++++++++++++++++++++++++++++++++-
1 files changed, 39 insertions(+), 1 deletions(-)
diff --git a/opends/src/server/org/opends/server/core/ConnectionHandlerConfigManager.java b/opends/src/server/org/opends/server/core/ConnectionHandlerConfigManager.java
index 3c1521e..69218b1 100644
--- a/opends/src/server/org/opends/server/core/ConnectionHandlerConfigManager.java
+++ b/opends/src/server/org/opends/server/core/ConnectionHandlerConfigManager.java
@@ -41,16 +41,19 @@
import java.util.List;
import java.util.concurrent.ConcurrentHashMap;
+import org.opends.server.admin.AdministrationConnector;
import org.opends.server.admin.ClassPropertyDefinition;
import org.opends.server.admin.server.ConfigurationAddListener;
import org.opends.server.admin.server.ConfigurationChangeListener;
import org.opends.server.admin.server.ConfigurationDeleteListener;
import org.opends.server.admin.server.ServerManagementContext;
import org.opends.server.admin.std.meta.*;
+import org.opends.server.admin.std.server.AdministrationConnectorCfg;
import org.opends.server.admin.std.server.ConnectionHandlerCfg;
import org.opends.server.admin.std.server.RootCfg;
import org.opends.server.api.ConnectionHandler;
import org.opends.server.config.ConfigException;
+import org.opends.server.protocols.ldap.LDAPConnectionHandler;
import org.opends.server.types.ConfigChangeResult;
import org.opends.server.types.DN;
import org.opends.server.types.DebugLogLevel;
@@ -77,7 +80,8 @@
// The mapping between configuration entry DNs and their
// corresponding connection handler implementations.
- private ConcurrentHashMap<DN, ConnectionHandler> connectionHandlers;
+ private ConcurrentHashMap<DN, ConnectionHandler> connectionHandlers =
+ new ConcurrentHashMap<DN, ConnectionHandler>();
@@ -325,6 +329,40 @@
/**
+ * Initializes the configuration associated with the Directory
+ * Server administration connector. This should only be called at
+ * Directory Server startup.
+ *
+ * @throws ConfigException
+ * If a critical configuration problem prevents the
+ * administration connector initialization from succeeding.
+ * @throws InitializationException
+ * If a problem occurs while initializing the administration
+ * connector that is not related to the server
+ * configuration.
+ */
+ public void initializeAdministrationConnectorConfig()
+ throws ConfigException, InitializationException {
+
+ RootCfg root =
+ ServerManagementContext.getInstance().getRootConfiguration();
+ AdministrationConnectorCfg administrationConnectorCfg =
+ root.getAdministrationConnector();
+
+ AdministrationConnector ac = new AdministrationConnector();
+ ac.initializeAdministrationConnector(administrationConnectorCfg);
+
+ // Put this connection handler in the hash so that we will be
+ // able to find it if it is altered.
+ LDAPConnectionHandler connectionHandler = ac.getConnectionHandler();
+ connectionHandlers.put(administrationConnectorCfg.dn(), connectionHandler);
+
+ // Register the connection handler with the Directory Server.
+ DirectoryServer.registerConnectionHandler(connectionHandler);
+ }
+
+
+ /**
* {@inheritDoc}
*/
public boolean isConfigurationAddAcceptable(
--
Gitblit v1.10.0