Semi-Automatic Patch Upgrade Kit for ALEPH Server Structure

1. Semi-Automatic patch upgrade kit www.exlibrisgroup.com

2. ALEPH server structure • After initial installation, software • directories (a50_5) are separated • from the site-specific directories • (u50_5). • With this configuration, when the • system is upgraded and a newer • server version is installed, the • a50_5 root is replaced, whereas • the u50_5 root remains as is.

3. Libraries Management a5x_5 Versus u5x_5 aleph u50_5 a50_5 alephe (active) ….. aleph alephe (original) ndu01 …… alephm

4. UPGRADE - EXL Librarian’s tasks • Analyze rep_changes • Implement u5x_5 related changes on the customer site UNIX files /alephe/www_a_eng/ill-request-doc-head /alephe/www_server_defaults /alephe/error_eng/check_circ /usm01/tab/pc_tab_col.eng

5. UPGRADE - EXL Librarian’s tasks • PRE-HISTORY • All implementation work was done manually • web-page by web-page • table by table • template by template • (Think about multi-database installation…)

6. Semi-Automatic kit is coming... • In general • UPGRADE scripts compare ‘rep_changed’ web files and tables under a5x_5 and that under u5x_5 diff /aleph/a50_5/alephe/www_a_eng/scan-a /aleph/u50_5/alephe/www_a_eng/scan-a diff /aleph/a50_5/usm01/tab/pc_tab_col.eng /aleph/u50_5/lib01/tab/pc_tab_col.eng

7. Semi-Automatic kit is coming... • Localizations with base-suffixes are • also searched, and the file in the a5x_5 • version is also compared with the • a5x_5.14.2.4 version to ensure that the • fix has not already been installed. • The script also takes into account localized • html files existing in the a5x_5 directory • created in the preparation of localized office • and distributor versions.

8. Semi-Automatic kit is coming... • If no differences are found -> • files are marked for direct copy from the new • version (a50_5.14.2.4) into customer’s • directory • If there are differences -> • the files are marked for manual update in the • case of html files, and in the case of Aleph • tables they will be marked in some cases for • manual upgrade, and in others for automatic • upgrade, depending on the nature of the fix.

9. Semi-Automatic kit is coming... • After running the automatic upgrade , • the remaining defined subset of tables • is updated manually

10. 14.2.4 Patch Upgrade - Typical Savings • In a typical 14.2.1 -14.2.4 automatic upgrade • 34 out of 295 HTML changes were manual • 8 out of 106 ALEPH tables were manual • Work load - one day for automatic and manual configuration • At least 4 days if all done manually

11. Place new version as a5x_5.14.2.4 parallel to the active a5x_5 (upgrade scripts are contained in the directory a5x_5.14.2.4/patch_upgrade/conv_to_14.2.4) Create u5x_5.14.2.4 parallel to active u50_5 (Under this directory, sub-directories are created as a container for the upgraded tables and web screens.) Create u5x_5.backup Patch Upgrade Steps

12. Execute Upgrade Kit Patch Upgrade Steps

13. Step1 - Create list of files to be copied The file ‘dir_list’ includes all directories located under u5x_5 that contain files that were rep_changed. It will be used for: Step 2 -- Copying the active table directories from u5x_5 to u5x_5.14.2.4 before running the scripts --Backing up the (old) active table directories in u5x_5 Step 9 -Overwriting the old table directories in u5_x with the new ones from u5x_5.14.2.4 before switching in the new version. Patch Upgrade Steps

14. Step3 - Web pages comparison -u5x_5 special creation date -language sensitive comparison OUTPUT a5x_5.14.2.4/patch_upgrade/conv_to_14.2.4 /results/web web_to_copy.lng web_to_update.lng web_new.lng web_done.lng web_errors.lng Patch Upgrade Steps

15. web_to_copy.lng - list of web pages that can be automatically copied from new patch (as they weren’t adapted by a client) web_to_update.lng - list of web pages that have to be updated manually web_new.lng - list of new web pages that can be automatically copied from new patch web_done.lng - list of web pages that shouldn’t be updated (as rep_changes has already been implemented locally) web_errors.lng -should be empty Web pages comparison OUTPUT

16. Step 4 - Copy new and rep_changed (not customized) Web pages (from a5x_5.14.2.4 to u5x_5.14.2.4) Patch Upgrade Steps

17. Step 5 - Create lib_tab_map (based on ‘updated_dir_list’ see step1) file of full paths of your tab directories, where we define : to which library every fix should be applied. Full paths of demo libraries, user libraries and new patch of demo libraries Patch Upgrade Steps

18. Step 6 - Tables comparison -library code sensitive comparison OUTPUT a5x_5.14.2.4/patch_upgrade/conv_to_14.2.4 /results/tab tabs_to_copy tabs_to_update tabs_new tabs_done tabs_errors Patch Upgrade Steps

19. tabs_to_copy - list of tables that can be automatically copied from new patch (as they weren’t adapted by a client) tabs_to_update - list of tables that have to be updated manually tabs_new - list of tables that can be automatically copied from new patch tabs_done - list of tables that shouldn’t be updated (as rep_changes has already been implemented locally) tabs_errors -should be empty Tables comparison OUTPUT

20. Step 7 - Copy new and rep_changed (not customized) tables (from a5x_5.14.2.4 to u5x_5.14.2.4) Patch Upgrade Steps

21. Step 8 - Automatic upgrade of rep_changed (customized) tables ### tables in tabs_to_update - part of them can be updated automatically using interactive update script Updated tables are copied into u5x_5.14.2.4 Patch Upgrade Steps

22. From this stage there are two different ways to run a kit on a production server versus a test server... production server versus a test server

23. -manual update (in u5x_5.14.2.4) -copy new u5x_5_14.2.4 to active u5x_5 (step 9) - local (u5x_5) adjustments -switch in 14.2.4 to be an active version -post-upgrade fixes -Indexes re-build (not necessary immediately after the switch) Production server

24. manual changes are made in the active environment, since downtime is not such a critical issue Test server

25. Want to see it in live ?