<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<link rel="home" title="HomePage" href="HomePage.html" />
<link rel="help" title="HowToUseWiki" href="HowToUseWiki.html" />
<link rel="copyright" title="GNU General Public License" href="http://www.gnu.org/copyleft/gpl.html#SEC1" />
<link rel="author" title="The PhpWiki Programming Team" href="http://phpwiki.org/ThePhpWikiProgrammingTeam" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta http-equiv="Content-Language" content="en" />
<meta name="robots" content="noindex,nofollow" />
<meta name="language" content="en" />
<meta name="document-type" content="Public" />
<meta name="document-rating" content="General" />
<meta name="generator" content="PhpWiki" />
<meta name="PHPWIKI_VERSION" content="1.3.14" />

<link rel="stylesheet" type="text/css" charset="iso-8859-1" href="phpwiki-printer.css" />
<title>PhpWiki - Architecture overview</title>
</head>
<body>

<div id="header">
  
<!-- Page title -->
<h1>Architecture overview</h1>
</div>
<div id="content">



<div class="wikitext"><span class="plugin" id="CommentPlugin30"></span><p class="tightenable top">'Normal' linux installations contain a set of important scripts and configuration files that are invoked or read by various server components. If you edit such a script or configuration file your original is overwritten by the new one. If you make a mistake during this edit, your server might mailfunction and you have to undo your changes or, if you're not capable of doing so, hunt for a 'original' one....</p>
<p class="tightenable">There is where the beauty of the SME server templating system comes in. Any of the core scripts and configuration files are rebuild at your will with 1 command only. Here's how it works;</p>
<ul><li class="tightenable bottom">Original files (e.g. all files in /etc/...) are never touched.</li>
<li class="tightenable top bottom">Instead of that, all the above files are in special 'original' directories</li>
<li class="tightenable top bottom">Files are split up in sections (fragments)</li>
<li class="tightenable top bottom">To edit a file, edit the fragment, and save it in a special 'custom' directory</li>
<li class="tightenable top bottom">So we have 'original' fragments and 'custom' fragments.</li>
<li class="tightenable top bottom">When rebuilding the files, the SME server will check for 'custom' fragments before 'original' fragments and build the new source file</li>
<li class="tightenable top bottom">If you don't like your new source file or have made a mistake, juste delete your fragment from the 'custom' directory and rebuild the source file</li>
<li class="tightenable top">You're back with a good file :-)</li>
</ul>
<p class="tightenable bottom">SME Server consists of a modified Red Hat Linux installation, together with a number of server applications as well as the server management software. The management software presents users with a simplified user interface and automatically configures the server applications as necessary.
<br /></p>
<span class="plugin" id="FrameContribsPlugin13"><div class="disabled-plugin"><div class="title">Plugin FrameContribs disabled. (action != 'browse')</div>
<pre>&lt;?plugin FrameContribs src=http://www.contribs.org/docs/rmcnew/Mitel/contribs/e-smith-architecture.gif height=500 width=95% frameborder=0 scrolling=no ?&gt;</pre>
</div>
</span><p class="tightenable top"><br />
Whenever the server management software needs to reconfigure a running server application, it rewrites the application's configuration files, and restarts the application if necessary. The applications are not modified to work within the SME Server framework.</p>
<p class="tightenable">The key to the whole system is the <b>master configuration file</b> (filename <code>/home/e-smith/configuration</code>), which contains a list of parameters that describe how the entire system should behave (IP addresses, domain information, email configuration, and so on).</p>
<p class="tightenable">A set of <b>Unix configuration file templates</b> is stored in the directory <code>/etc/e-smith/templates</code> (stored in the same hierarchy as the real configuration files). Each template is a parameterized version of a server configuration file; it produces different versions depending on the master configuration file.</p>
<p class="tightenable">A set of <b>action</b> programs is stored in the directory <code>/etc/e-smith/events/actions</code>. Each action program instantiates several templates and restarts server applications if necessary.</p>
<p class="tightenable">Whenever a parameter is changed using the user interface, the master configuration file is updated accordingly, then the proper actions are invoked by signalling an <b>event</b>. Events are defined in the directory <code>/etc/e-smith/events</code>. Each event specifies a particular sequence of <b>action</b> programs to completely update the system for a given situation.</p>
<p class="tightenable">So, to recap: here are the steps performed when a system parameter is changed in the user interface (the same steps are used both for the e-smith console and for the web-based manager):</p>
<p class="tightenable"><b>Step 1:</b> The user interface code modifies the settings in the e-smith configuration file to specify the new system configuration.</p>
<p class="tightenable"><b>Step 2:</b> The user interface code signals an event to inform the system that the configuration has changed.</p>
<p class="tightenable"><b>Step 3:</b> The event triggers a sequence of actions.</p>
<p class="tightenable"><b>Step 4:</b> Each action instantiates a set of templates and restarts servers if necessary.</p>
<hr />
<p class="tightenable top bottom">copyright 2000 Mitel Networks. all rights reserved.</p>
<hr />
<p class="tightenable top bottom">Back to <a href="Documentation.html" class="wiki">Documentation</a></p>
</div>

<div id="footer">  <hr class="printer" noshade="noshade" />
<p class="editdate">Owner: &quot;RonM&quot;  Last edited on September 22, 2005 12:55 am by &quot;RonM&quot;</p>
</div>

</div>
<!-- Add your Disclaimer here -->
</body>
</html>
