Changes

From SME Server
Jump to navigationJump to search

SME Server:Documentation:Developers Manual:Chapter1/de (view source)

Revision as of 21:02, 19 May 2007

52 bytes added ,  21:02, 19 May 2007
→‎Architektur Überblick
Line 107: Line 107:  
*Events und Actions
 
*Events und Actions
   −
When a user configures an aspect of the server through one of the user interfaces, the SME Server automatically configures the server applications relevant to that change. The SME Server does so using these steps:
+
Nach Eingaben im Server-Manager oder in der Serverkonsole konfiguriert der SME Server automatisch die Parameter der betreffenden Serveranwendung. Dabei läuft die Konfiguration in folgenden Schritten ab:
   −
    *
+
Über die Benutzereingabe werden Einträge in der Konfigurations-Datenbank geändert. Diese Datenbank, die aktuell eigentlich eine Zusammenstellung mehrerer Datenbanken ist, enthält viele Parameter zur Beschreibung des Systemzustands (IP-Adresse, Domänenname, E-Mail-Konfiguration, Benutzerkonten, etc.). Über die Benutzerschnittstelle wird die Serveranwendung nicht direkt rekonfiguriert, wohl aber der Auruf von Actions und Events, um gewünschte Änderungen zu rekonfigurieren.
   −
      The user interface changes values in the configuration database. This database (actually a collection of databases) contains parameters describing the state of the system (IP address assignments, policy settings, domain names, email server configuration, user accounts, and so on). The user interface does not perform the application reconfiguration, but instead signals an event to perform the changes.
  −
    *
      
       The event relevant to the changes being made to the configuration database is signalled. For example, changes related to email configuration might signal the "email-update" event. These events are collections of scripts and an event can be extended to perform additional functions by adding scripts to the event directory. The actions for an event are run in a defined order to produce the desired system state.
 
       The event relevant to the changes being made to the configuration database is signalled. For example, changes related to email configuration might signal the "email-update" event. These events are collections of scripts and an event can be extended to perform additional functions by adding scripts to the event directory. The actions for an event are run in a defined order to produce the desired system state.
Berdie
1,346

edits

Retrieved from "https://wiki.koozali.org/Special:MobileDiff/3640"

Navigation menu