[interchange-cvs] interchange - heins modified UPGRADE
interchange-core@icdevgroup.org
interchange-core@icdevgroup.org
Tue Nov 26 12:18:00 2002
User: heins
Date: 2002-11-26 17:03:43 GMT
Modified: . UPGRADE
Log:
* Add procedure for testing Interchange 5 in parallel with Interchange 4
on the same catalog.
Revision Changes Path
2.5 +115 -6 interchange/UPGRADE
rev 2.5, prev_rev 2.4
Index: UPGRADE
===================================================================
RCS file: /var/cvs/interchange/UPGRADE,v
retrieving revision 2.4
retrieving revision 2.5
diff -u -r2.4 -r2.5
--- UPGRADE 26 Nov 2002 15:19:13 -0000 2.4
+++ UPGRADE 26 Nov 2002 17:03:43 -0000 2.5
@@ -9,8 +9,10 @@
More information on upgrades is available in the document icupgrade, part
of the Interchange documentation package.
-BACK UP EVERYTHING BEFORE YOU START!
+NOTE: All below procedures assume you have installed in
+ /usr/lib/interchange -- substitute paths as appropriate.
+BACK UP EVERYTHING BEFORE YOU START!
TO UPGRADE FROM 4.8.x
---------------------
@@ -27,7 +29,10 @@
tar xzf interchange-5.x.tar.gz
cd interchange-5.x
- 3. Install it in the same location as your current software:
+ 3. You can see the section below, "TO TEST BEFORE YOU UPGRADE", if
+ you want to try it out before you switch your running catalog.
+
+ 4. Install it in the same location as your current software:
## Create the makefile
perl Makefile.PL prefix=/usr/lib/interchange
@@ -41,14 +46,119 @@
## Install the software
make install
- 4. You don't need to run makecat again!!!
+ 5. You don't need to run makecat again!!!
- 5. Restart Interchange.
+ 6. Restart Interchange.
- 6. See the "problems with UserTags" section, below.
+ 7. See the "problems with UserTags" section, below.
That should be it. Test the catalog to make sure it works.
+TO TEST BEFORE YOU UPGRADE
+--------------------------
+YOU SHOULD STILL BACK UP, and in addition it is recommended you back
+up your catalog. While the new server should not impact your running
+catalog beyond normal catalog interaction for orders, statistics,
+userdb, and such, it is not outside of the realm of possiblity that
+something could happen. It should not happen in a catalog that is
+based on Foundation and not heavily customized (i.e. using global UserTag
+routines).
+
+1. Install the new Interchange 5.x Interchange (4.9 for alpha/beta versions)
+in /usr/lib/interchange-5 using the procedure from INSTALL.
+
+2. Make /usr/lib/interchange-5/interchange.cfg match your
+/usr/lib/interchange.cfg. Note that there may be new options; but the
+existing one should work if you just copy it.
+
+3. Run bin/compile_link:
+
+ cd /usr/lib/interchange-5
+ bin/compile_link -p 7787
+
+NOTE: If you use the INET mode linking method, you have to run the
+ test server on a different port. Assuming you use the standard
+ 7786 on your live catalog, you would add to interchange.cfg:
+
+ TcpMap localhost:7787
+
+After running compile_link, you should see four new files in the
+/usr/lib/interchange-5/src:
+
+-rwxr-xr-x 1 root root 8088 Oct 3 09:59 tlink
+-rwxr-xr-x 1 root root 8088 Oct 3 09:59 tlink.localhost.7787
+-rwxr-xr-x 1 root root 7704 Oct 3 09:59 vlink
+-rwxr-xr-x 1 root root 7704 Oct 3 09:59 vlink._usr_lib_interchange_5_etc_socket
+
+4. Note the Catalog lines in your interchange.cfg:
+
+ EXAMPLE:
+
+ Catalog foundation /var/lib/interchange/foundation /cgi-bin/foundation
+
+You should comment out all but the one you want to test.
+
+5. Change the /cgi-bin/foundation script link name to /cgi-bin/test5.
+
+ EXAMPLE:
+
+ Catalog foundation /var/lib/interchange/foundation /cgi-bin/test5
+
+6. Copy the src/vlink (UNIX mode) or src/tlink (INET mode) link executable
+to your CGI directory and name it "test5", i.e.
+
+ EXAMPLE:
+
+ cp src/vlink /var/www/cgi-bin/test5
+
+7. IMPORTANT: Make sure its permissions match the permissions on your
+running 4.x catalog! You may have to make it SUID, i.e.:
+
+ EXAMPLE:
+
+ chmod u+s /var/www/cgi-bin/test5
+
+That should only be done if you are in UNIX mode and your current
+link program is SUID.
+
+8. Add this line to the /usr/lib/interchange-5/interchange.cfg file:
+
+ Variable TEST_SERVER 1
+
+9. Copy any *custom* global UserTag files to the usertag/ directory. Do not
+copy any that were distributed with Interchange if you did not modify them.
+
+10. Copy the new Interchange image and CSS files to the interchange-5
+subdirectory in your document root, i.e.:
+
+ EXAMPLE:
+
+ cp -r /usr/lib/interchange-5/share/interchange \
+ /var/www/html/interchange-5
+
+11. Modify your /var/lib/interchange/foundation/catalog.cfg file to
+point the URLs to the test server if appropriate by placing at the
+end:
+
+ ifdef @TEST_SERVER
+ Variable CGI_URL /cgi-bin/test5
+ Variable UI_IMAGE_DIR /interchange-5/
+ Variable UI_IMAGE_DIR_SECURE /interchange-5/
+ ## This ensures the UI image directory will be set properly
+ Pragma dynamic_variables_file_only
+ VendURL http://__SERVER_NAME____CGI_URL__
+ SecureURL https://__SERVER_NAME____CGI_URL__
+ endif
+
+12. Start the new interchange server:
+
+ /usr/lib/interchange-5/bin/restart
+
+At that point, your catalog should be running on both Interchange 5 and
+Interchange 4. Test thoroughly and then upgrade. Note that the UI will
+be significantly changed, and that all features of the UI may not be
+supported by your old catalog. The customer-facing side should function
+in much the same way.
IF YOU UPGRADED FROM 4.6.x
--------------------------
@@ -128,4 +238,3 @@
UserTags, UI_Tag etc.) The message is only a warning as your local UserTag
will override the global one. If you didn't mean to override the global
tag of the same name then simply rename your tag and restart Interchange.
-