ispman/docs UPGRADING,1.6,1.7

Update of /cvsroot/ispman/ispman/docs
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv855/docs

Modified Files:
	UPGRADING 
Log Message:
updated UPGRADING for new install method

Index: UPGRADING
===================================================================
RCS file: /cvsroot/ispman/ispman/docs/UPGRADING,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7
--- UPGRADING	1 Aug 2004 21:00:04 -0000	1.6
+++ UPGRADING	4 Aug 2004 20:16:24 -0000	1.7
@@ -1,11 +1,6 @@
-!!! Temporary Notice:
-!!! This file is not uptodate with new install procedures, so the
-!!! instructions below may not be accurate. 
-!!! Wait for this notice to disappear before following any of this!
 
-
-Upgrade Instructions
-====================
+Upgrade ISPMan from earlier version
+===================================
 
 Note:   Depending on which ispman version you are running, the
         following may work more or less smooth for you.
@@ -21,43 +16,62 @@
 upgrading on a testsystem first.
 
 
-Prepare for upgrade
+
+Preparation
+===========
+Updated ISPMan versions may come with modified LDAP schema, which
+makes it necessary to migrate the data.
+
+Thus, you should dump your existing ISPMan data to some temporary LDIF
+file:
+        -> <installdir>/bin/ispman.ldifdump > /tmp/myispman.ldif
+
+You may want to save this file to a more save location also for backup
+purposes.
+
+
+Next, the <installdir> has to be cleaned, so we get rid of any files,
+that are not contained in the updated version anymore.
+Best way to do this is to remove all subdirs except the conf
+directory, but be aware that this will remove any customization you
+have made to ISPMan files.
+
+
+
+Update ISPMan files
 ===================
 
-Do the normal preparation after you acquired the update via tarball or
+Do the normal ISPMan install after you acquired the update via tarball or
 cvs (see INSTALL for more info):
 
 So this will be something like
--> ./configure
--> make ispman
+        -> ./configure --prefix=<installdir>
+        -> make
+        -> make install
 
-This will generate the following files among other things:
+Besides the updated ISPMan files, the following important things get
+installed:
 
-tmp/conf/ispman.conf:
-        Your new ispman.conf based on your existing config data.
+<installdir>/conf/ispam.conf.example
+        A new default example for ispman.conf
 
-tmp/ldif/ispman.ldif:
+<installdir>/conf/ldif/ispman.ldif:
         This is the basic LDAP DIT for ispman.
         Though, most of this should already exist in your LDAP, it may
         contain additional entries (e.g. confVars) that are not
         present yet.
 
-tmp/conf/schema/*:
+<installdir>/conf/schema/*:
         Updated schema files.
 
-tmp/conf/ldap.conf:
-tmp/conf/sldap.conf:
-        example config files for openldap
-
 
 
 Migrate your LDAP data
 ======================
-Dump your ispman data to some temporary LDIF file:
-e.g. -> /opt/ispman/bin/ispman.ldifdump > /tmp/myispman.ldif
-
-Now use "ldifupdate" to check and migrate your ispman data.
--> ./scripts/ldifupdate -i /tmp/myispman.ldif -o /tmp/changes.ldif -m modify
+On your exported ISPMan data use "ldifupdate" to check consistency and
+do any needed migration:
+        -> <installdir>/bin/ispman.ldifupdate \
+                -i /tmp/myispman.ldif -o /tmp/changes.ldif -m modify
 
 This reads your data from the generated LDIF (myispman.ldif) and
 checks it against some migration/validity rules.
@@ -68,21 +82,18 @@
 
 In case ldifupdate warns you about some missing defaults, you need to
 adjust some defaults at the beginning of that script.
--> vi ./scripts/ldifupdate
-
+        -> vi <installdir>/bin/ispman.ldifupdate
 
 
 Apply config/schema changes
 ===========================
-Compare your openldap configs (slapd.conf, ldap.conf) against the new
-generated versions.
-Apply any necessary changes introduced by the new files.
+The install/upgrade process doesn't touch your existing ispman.conf,
+but comes with a new ispman.conf.example file.
+Make sure your ispman.conf contains the same config keys as the example.
 
-Copy the new schema files
-        tmp/schema/dnszone.schema,
-        tmp/conf/schema/proftpd.schema
-        tmp/schema/ispman.schema 
-to your openldap schema directory.
+Next update your LDAP schemas. In case your OpenLDAP doesn't use the
+schemas directly from <installdir>/conf/schema, make sure to copy the
+updated files to OpenLDAP's schema directory.
 
 Check that your slapd.conf contains at least the following schemas:
         core.schema
@@ -104,30 +115,29 @@
 
 Import new ISPMan data
 ======================
-Now load the new LDIF files to your LDAP server.
-
-* use upgrade_from_ldif.pl script to load the generated ispman.ldif:
--> scripts/upgrade_from_ldif.pl tmp/ldif/ispman.ldif 
+Now load the new LDIF files to your LDAP server, to add any newly
+added default data:
+        -> cd <installdir>
+        -> cat conf/ldif/ispman.ldif | ./bin/ispman.substConf | \
+           ./bin/ispman.ldifload -f -
 
 This will only add branches and records that are missing (no delete or
 overwrite), so just ignore any warnings about already existing
 entries.
 
-* apply the changes from ldifupdate (/tmp/changes.ldif from above)    
--> ldapmodify -x -h <ldaphost> -D <binddn> -w <bindpw> -f /tmp/changes.ldif
+Apply the changes from ldifupdate (/tmp/changes.ldif from above)    
+        -> ldapmodify -x -h <ldaphost> -D <binddn> -w <bindpw> \
+                -f /tmp/changes.ldif
 
 This is probably the most elegant way to do this, because it will just
 change what is needed. No big-time export/import.
 
+If that worked out ok, you should be ready to go.
 
-Install ISPMan update
-=====================
-Finish the update with the rest of the normal install procedure    
--> make install_ispman_common
--> make install_ispman_web
 
+Please send any bugs or improvement suggestions to
+ispman-developers-nYvEWQtI3DWkA/[email protected]
 
-For additional info read INSTALL
 
 
     



-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com