1. Revision Update and Reports
SFX Version 4 introduces many new features. In this lesson we will introduce the changes in SFX Revision Update and Reports.
SFX Version 4

2. What is Rev-Up? Revision Update What is Rev-Up?
At regular intervals, Ex Libris provides SFX KnowledgeBase packages containing Software updates and database updates with new and updated targets, sources, services, portfolios and objects.
Each KnowledgeBase update provided by Ex Libris is called a revision package, and the program that is used to apply the revision is called rev-up.

3. General Changes in SFX V4
Before we go on to explain what changed in Rev-up in SFx version 4, just a quick reminder on one of the major changes in SFX version 4:
One of the big changes behind the scenes in version 4, is the separation between local and global information.
Global Global kb maintained by Ex Libris and all of the descriptive data in the kb. This data will only be held once, in the global instance. In the local instance, we will store customer specific information: activation status, local data for date coverage, linking parameters, local parsers, and local overrides of global data.
This global local separation has a major affect on Rev-Up.

4. Less clean-up operations
What Changed in Rev-Up?
SFX version 4 introduces a new and upgraded Rev up program. What’s new in Rev-Up?
Since the knowledge base database packages is undergoing constant growth, it became crucial to improve the time it takes to apply the package.
A few changes were made in order to reduce the time the rev-up runs:
1. Since the SFX database tables structure was changed, the Rev up part called “Apply kbdb” which applies knowledge base database changes had to be adapted to work with the new database structure. In general, the apply KBDB needs to work now in the context of separation between the global instance and its related local instances.
2. The backup and roll back functionalities were also adapted for the same reasons of new database structure and separation between local and global.
3. The rev-up sequence changed – First the global instance is updated and then minor updates and cleaning is done on the local instance. The reason for this change is that on SFX V4 the main update work is done on the global instance. The local instance undergo very minor update as will be detailed further in the presentation.
BTW, When multiple revisions are run in one go, the same mechanism will be used as in V3 – each revision ((with extra, SW, KBSW and KBDB packages) will be applied one after the other, on all instances.
4. The update of sfxglb is completely automatic without the need to compare with the local instance in order to detect localization. For this reason there are not going to be also “Not-deleted” items and “Not-changed” items. This is again due to the separation between the global instance and its related local instances.
5. The local instance are undergoing only a small set of “clean-up” operations: For example, local portfolios related to targets that have been deleted from the global instance will be removed from the local instance and will not be left as “orphan” portfolios.
6. The reports will no longer be created during the rev-up: Since there is no need to check what items were not deleted or changed due to localization and then produce a report, from SFX 4 the reports will be given as part of the KBDB package.
=> Since V4 rev-up, is faster and more efficient will decrease the Total Cost of Ownership for the SFX clients. => Reduce TCO
Apply KBDB
Backup/ Rollback
Lower TCO
Reports
Sequence
Less clean-up operations
Automation

5. What Did not Change? Applying knowledgebase software Software updates
Extra packages
What Did not Change in Rev-up?
Applying Knowledge base software and Software updates (new parser or parser updates) and extra packages are the same as in Version 3. Localization will remain on the local instance and the update will not be done where there is localization. The Global instance will be updated, same as in version 3.

6. The V4 Rev-Up Options Backup
New option to apply V4 packages that are also been released for V3
The SFX V4 rev-up options will remain very similar except for the following changes:
The back up option was changed to fit the new database structure.
A new option was added in order to apply packages that are also being released for V3: This option will be used in case V4 will have updates released more frequently than the updates released for V3.This option will be used by the installer/upgrader and is needed to keep V3 and V4 in sync. Upon upgrade, this option will run all V4 revisions missing on the V4 installation until and including the latest V3 revision.

7. Applying KBDB on Local Instances

8. Revision Reports provide a detailed statement about the revision update results: it lists all of the changes, additions and deletions included in the revision update.

9. KBDB Report Tables KB_REPORT LCL_REPORT
Report data will be stored in two tables:
KB_REPORT table, which belongs to the global instance
LCL_REPORT table, which belongs to the local instance.
It is possible to create reports on the fly.
The KB_REPORT table:
Contains global report data such as the changes/additions/deletions done to global items (included in the knowledge base database package.)
The KB_REPORT table also Contains local report data from all the local instances connected to this global instance: This data is in fact all the changes done during KBDB update to each local instance as a result of changes done to the global items.
The LCL_REPORT table:
Contains local report data for that specific local instance. It will hold all the deletions done during the KBDB update on this specific local instance for INVENTORY and LCL_LINKING info.
Changes/additions/deletions done to global items
Local report data from different instances – in case of deletions/changes of KB_ tables during local instance update
Local report data for the local instance – in case of deletions/changes during local instance update of INVENTORY and LCL_LINKING info

10. Rev-Up Reports - UI
Let us take a look at the revision reports user interface.
To get to these reports, Go to set up and administration section, and under KBUpdate, click on reports.

11. Rev-Up Reports - HTML
There are two main types of reports: text reports and html reports.
This is the HTML report page.
Here you select the options for the report you would like to see
On the top drup down menu, select the relevant revision and date,
Then select the type of changes that you are interested in: either new, updated or deleted.
And, There are some filtering options as well.
When you’re ready, click the submit button.

12. Rev-Up Reports - HTML
This will take you to the report, grouped by terget, target services, and source services.
To see more details, click on the plus sign, which expands the group to show more information.
Let’s scroll down a bit to see the information detailed for each item.
Notice that each line has a clickable KB button that you can use to go directly to the item in the Knowledgebase.

13. Rev-Up Reports - Text
Here we see the second type of report: the text report. The options here are similar:
On the top drup down menu, select the relevant revision and date,
Then select the type of changes that you are interested in: either new, updated or deleted.
And, the way you would like to group the results.

14. Viewing / Cleaning Report Tables
Viewing and Cleaning Report Tables, is possible via ServerAdminUtility.
Select 9 for revision update, and then you will get the revision update options menu.
Please notice that
Viewing is possible in both sfxglb and local instances
But Cleaning is only possible on sfxglb

15. Summary Described Rev-Up Changes
Listed the Main Changes related to applying KBDB to local instances
Run reports
Ok, now let’s review what we did in this lesson:
We described the main changes in rev up, What Changed and what Did not Change.
We saw how to apply Knowledgebase database changes to local instances
And how to run Reports regarding these updates.

16. Thank you for taking the time to view this lesson.