Core Services in Client Framework Upgrade

Core Services in Financials Client Framework

In the Rice project, Core Services provides access to namespaces and parameters, as well as related objects. As such, Core Services are very important not only to Rice itself but to applications written within Rice frameworks.

As part of the strategy to provide abstractions around future changes to Rice, the Financials team split the Core Services, KNS, and KRAD portions of Rice 2.5.x into separate classes to isolate financials from Rice KNS & KRAD. This had a couple of different upshots, but one of the most important is that tables for the core services business objects were copied to the client side.

Let's go through each of the core services business objects and see what happened precisely:
* Namespaces: an exact list of namespaces must be shared between Financials and Rice, so this was a complete copy
* Parameters: Rice has no need to access Financials-specific parameters, just as Financials has _little_ (not quite none) need to access KEW, KIM, KEN, KL, and KSB parameters. So much of the parameters belong either on the client or the server side but not both. This leaves the KR-KRAD and KR-NS parameters; the KR-NS parameters are of course particularly important to Financials. The script makes copies of some of these parameters and moves others, depending on if Financials had provided their own, out of the box override of Rice behavior.
* Parameter Types: As with namespaces, this was a straight copy - the Financials and Rice data must be exactly the same.
* Parameer Components: Many components will be recreated automatically when you restart the server. Still: for an upgrade, there's a large likelihood that most Financials components have already been created once. Given that, all KFS and KR-NS components are copied to Financials.
* Derived Components and Component Sets: it is understood that Financials will recreate these as needed on startup. No data is copied over at all.
* Styles: Financials doesn't really use Styles but for the sake of minimizing strange side-effects while splitting the client framework from Rice, they were left in. As such, Financials copies the structure of the krcr_style_t table but removes any data from it. It is suggested that implementation teams not get too emotionally attached to the Styles functionality in financials-cf core services.

How to use the upgrade scripts

If you are running Rice bundled, there is NO upgrade process. The following instructions should be used only if you're using a Rice set up with a separate Rice database or if you are currently splitting a bundled database.

There are four basic steps to running the upgrade scripts for core services business objects:

# Make copies of the five major core services tables currently in Rice in the KFS database/schema. Those five tables are:
#* KRCR_NMSPC_T
#* KRCR_CMPNT_T
#* KRCR_PARM_TYP_T
#* KRCR_PARM_T
#* KRCR_STYLE_T
# Download the version of the upgrade script - attached to this page - appropriate for your database, MySQL or Oracle.
# Review the "For Financials" portion of the script and run that in your client database
# Review the "For Rice" portion of the script and run that in your Rice server database

Great - you've upgraded your core services.