We have implemented an automatic pre-release distribution system.
This allows us to make special request features and corrections quickly
available to everyone.
Many RoAccess clients have both the Unix and NT versions running. So each release file contains the versions for both the Unix and NT version of RoAccess. Here are the basic steps:
Back up your current roaccess directory tree Unzip the Interim Release (Patch) file Read the README file Get either the unix.tar.gz or the nt.zip file Un-tar or unzip the the file in your roaccess top level directory Upload file roaccess/install/ROA_PROC.001 into your AP-PROC database That's it
Interim Release files come in the form PRODUCT_Patch_seq_number.zip.
PRODUCT is [RoAccess|RoLoader|RoPages]. An example would be RoAccess_Patch_10.zip
Each time we make a new patch, it automatically generates the next sequence
number.
Below is a set of Windows snapshots for patch file RoAccess_Patch_16.zip:
A Interim Release file always contains 4 files:
Clicking on the nt.zip file in the above screen brings up:Readme for NT (in DOS format CR/LF) Readme for Unix (In Unix format only linefeeds) The NT version of patches in a .zip file The Unix version of the patches in a tar file in gzip format.
The above shows there are 3 files in this patch release.
The AA_Install.txt is an installation note telling you what needs to be done and why. It may only be an explanation of a simple text edit. If so, no additional files may be supplied.
The other files are to replace existing files.
Below is an example of a AA_Install.txt where two files were to be replaced:
# ________________________________________________________________________ # # $RCSfile: Patch_explanation.html $ # $Revision: 1.6 $ # ________________________________________________________________________ Affected Product ================ RoAccess 5.02 Reason for Patch ================ User Requested that when uploading a file into a BLOB attribute: - automatically redisplay the ItemGet screen without requiring a separate "Continue" click. So it takes one less click and makes uploading many files much faster and convenient - Be able to specify after upload, whether to display the item in Display or Edit mode. Affected Files ============== (Note: NT uses \ slashes. For Unix, use / slashes) roaccess\cgi-bin\Upld.pl roaccess\cgi-bin\UpldQ.pl Description of Installation =========================== Replace these files on your system.
Backup your roaccess directory tree (probablyWinzip) Download the Patch file, like RoAccess Patch 503_12.zip Put the file in a temporary directory Unzip it. Read the README file. Exract the nt.zip file into your roaccess main directory (not the cgi-bin directory) Open nt.zip in Winzip Extract it to your RoAccess top level directory. This will store files there and in any subdirectories Upload the file roaccess\install\ROA_PROC.001 into your AP-PROC database using Autopilot. It contains new stored procedures. That's it.
Backup your roaccess directory tree (probably tar) Download the Patch file, like RoAccess Patch 503_12.zip Put the file in a temporary directory Unzip it. Read the README file. Copy the unix.tar.gz file to your Unix box, and put it in /tmp. You might have a Unix unzip program, so Iust unzip the patch file there. go into your roaccess top directory, and issue the command: gunzip </tmp/unix.tar.gz | tar xpf - This uses the GNU gunzip program (if you don't have it, I can send it) This places all the new files in the roaccess and all subdirectories Upload the file roaccess/install/ROA_PROC.001 into your AP-PROC database using Autopilot. It contains new stored procedures. That's it.
http://yourserver/roaccess/cgi-bin/List_All_Patches.plYou should see your Patch Level you downloaded displayed in the list
http://yourserver/roaccess/cgi-bin/ProcInfo.plYou should see two columns of stored procedure version numbers: what they should be, and what they actually are. If you see any green or red messages, your stored procedures do not match and have probably forgotten to import the ROA_PROC.001 file or it was imported into the wrong database.