martin: doc/architecture Makefile,1.9,1.10 server.sgml,1.27,1.28

[cvs at intevation.de]

Author: martin

Update of /kolabrepository/doc/architecture
In directory doto:/tmp/cvs-serv19138

Modified Files:
	Makefile server.sgml 
Log Message:
Martin K.: Added new sections about Maintaining the server


Index: Makefile
===================================================================
RCS file: /kolabrepository/doc/architecture/Makefile,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -d -r1.9 -r1.10
--- Makefile	3 Oct 2004 04:34:17 -0000	1.9
+++ Makefile	29 Oct 2004 04:41:26 -0000	1.10
@@ -37,9 +37,8 @@
 concept/index.html: $(SGML_SRC) $(INCLUDED_SRCS)
 	$(HTML_CMD) $(SGML_SRC)
 	cp erfrakon.png $(HTML_DEST_DIR)/
-	cp $(HTML_DEST_DIR)/index.html $(HTML_DEST_DIR)/index.html.tmp
-	cat $(HTML_DEST_DIR)/index.html.tmp | sed -e 's/SRC=\"erfrakon\"/SRC=\"erfrakon\.png\"/g' > $(HTML_DEST_DIR)/index.html
-	rm $(HTML_DEST_DIR)/index.html.tmp
+	cat $(HTML_DEST_DIR)/index.html | sed -e 's/SRC=\"erfrakon\"/SRC=\"erfrakon\.png\"/g' > $(HTML_DEST_DIR)/index.html.tmp
+	mv $(HTML_DEST_DIR)/index.html.tmp $(HTML_DEST_DIR)/index.html
 
 $(NAME).ps: $(SGML_SRC) $(INCLUDED_SRCS)
 	$(PS_CMD) $(SGML_SRC)

Index: server.sgml
===================================================================
RCS file: /kolabrepository/doc/architecture/server.sgml,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -d -r1.27 -r1.28
--- server.sgml	3 Oct 2004 18:56:28 -0000	1.27
+++ server.sgml	29 Oct 2004 04:41:26 -0000	1.28
@@ -1553,10 +1553,10 @@
 
 </sect2>
 
-<sect2><title> Mandatory SMTP Email Addresses </title> 
+<sect2><title> Mandatory SMTP Email Addresses </title>
 <para>
-Common Internet pratice and internet standards (RFCs) require the existance of the 
-following three email addresses. 
+Common Internet pratice and internet standards (RFCs) require the existance of the
+following three email addresses.
 </para>
 
 <orderedlist>
@@ -2020,5 +2020,38 @@
 </para>
 <para>With Kolab 3.0 we will use Apache mod_rewrite modules in order to have a transparent server side support for legacy Kolab clients. We use this mod_rewrite in order to process the download requests with a php script, fetch the required freebusy list from the appropriate Kolab server and then present the result to the requesting client.
 </para>
+</sect1>
+<sect1><title> Maintainance of Kolab server </title>
+<para>
+</para>
+<sect2><title> Installation of Kolab server </title>
+<para>
+</para>
+</sect2>
+<sect2><title> Upgrade of Kolab server </title>
+<para>It is save to expect that for security reasons, new features or bugfixes a new release of
+the Kolab server is often desirable.</para>
+<para>We use the same <filename>obmtool</filename> for upgrading which is used for installing the Kolab server.</para>
+<para>A save method for updating in case a short downfime is acceptable is first to become the superuser of the system and then
+get the proper shell environment. Afterwards the new kolab rpm packages get installed and compiled if required.
+The <filename>obmtool</filename> takes care about downloading further required packages automatically. The intermediate
+<filename>kolabconf</filename> which happens to depend on OpenLDAP is sometimes mandatory for doing an update of the
+current configuration of the Kolab services. Last but not least all Kolab server processes get started.</para>
+<para>Further refinement typically happens via the Kolab web administration gui.</para>
+<orderedlist>
+<listitem><para>#su -</para>
+<listitem><para>#/kolab/etc/rc --eval all env</para>
+<listitem><para>#/kolab/etc/rc all stop</para>
+<listitem><para>#./obmtool kolab (from the correct location of course)</para>
+<listitem><para>#/kolab/etc/rc openldap start (only openldap is needed when running kolabconf)</para>
+<listitem><para>#/kolab/sbin/kolabconf</para>
+<listitem><para>#/kolab/etc/rc openldap stop</para>
+<listitem><para>#/kolab/etc/rc all start</para>
+</orderedlist>
+<para>
+Just keep an eye out during the for .rpmsave files. They will cause the different
+services not to start...
+</para>
+</sect2>
 </sect1>
 </chapter>