[Unicore-cvs-commits] SF.net SVN: unicore:[17508] gateway/trunk/src/main/doc/manual.txt

[<bsc...@us...>]

Revision: 17508
          http://sourceforge.net/p/unicore/svn/17508
Author:   bschuller
Date:     2013-11-29 09:47:44 +0000 (Fri, 29 Nov 2013)
Log Message:
-----------
update docs

Modified Paths:
--------------
    gateway/trunk/src/main/doc/manual.txt

Modified: gateway/trunk/src/main/doc/manual.txt
===================================================================
--- gateway/trunk/src/main/doc/manual.txt	2013-11-29 09:15:54 UTC (rev 17507)
+++ gateway/trunk/src/main/doc/manual.txt	2013-11-29 09:47:44 UTC (rev 17508)
@@ -128,37 +128,20 @@
 
  $> apt-get install unicore-gateway
 
-Upgrade from to 6.5.0 version
------------------------------
+Upgrade from version 6.6.x
+--------------------------
 
-Gateway 6.5.0 (released in UNICORE quickstart 6.6.0) introduces a lot of new features and therefore the 
-update form the previous version requires special attention as configuration files format have changed for
-+gateway.properties+ and +security.properties+. What's more +crlcheck.properties+ file is obsolete 
-and not used any more: CRL settings are provided in +security.properties+.
+Apart from updates of Java libraries, there are no radical changes, and updating is straightforward.
  
 The general update procedure is presented below, with possible variations:
 
  1. Stop the old Gateway.
  2. Update the server package. This step mostly applies for RPM/DEB managed installations. For Quickstart installation
- it is advised to install Gateway along with other needed components to a separate directory.
- 3. Port configuration of pre-1.5.0 server to the new syntax. It can be done in two ways:
-   * Manually by applying all old values to the new template configuration. There are quite a few properties to be 
-   ported so this requires several minutes of work. The advantage of manual porting is that the new template files 
-   with new options and updated comments are used. Note: for RPM installations the new files will be named +*.rpmnew+.
-   * Automatically, using UNICORE configurator. You have to install the +unicore-configurator+ package. It is included in 
-   Quickstart, for distributions install simply run appropriate command: +yum install unicore-configurator+ or 
-   +apt-get install unicore-configurator+. Using the configurator you can update the old files automatically:
-      ** For RPM/DEB installations it is enough to run +unicore-config-update.py gateway+. 
-      ** For Quickstart put your old configuration files in the folder with the newly installed Gateway 
-      and specify its directory with +-c+ option: +./unicore-config-update.py -c GATEWAY_CONFIG_DIR gateway+.
-   Carefully read the output of the program - there can be some problems reported. 
-   Option +-h+ provides help, with information about the usage: how to perform dry run, how to recover files 
-   from backup etc.
- 4. Start the newly installed Gateway.
- 5. Verify log file and fix any problems reported.
+ it is enough to replace the *.jar files with the new ones.
+ 3. Start the newly installed Gateway.
+ 4. Verify log file and fix any problems reported.
 
 
-
 Configuration
 -------------
 

This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.