Object Conversion

3.2.2.4 Object Conversion

With the above sharing type considerations, DB object types are converted as DATA LINK and METADATA LINK as part of this application root object conversion step.
User has to connect to Application Root as common user and then apply changes in upgrade mode with the same application name used in step 3.

This step is done from the installer and user has 4 options to do the conversion as:

Shared Application - Here all the function Ids are available as PDB function Ids.
Shared Application and User Authentication - SMS function IDs are available in Approot and the remaining all function IDs are available as PDB function IDs.
Shared Application and Shared Data – Default - Identified list of entities are available in approot and sharing of entities from Approot to individual PDBs is applicable in this model.
Shared Application and Shared Data – Custom - Identified list of entities are available in approot and sharing of entities from Approot to individual PDBs is applicable in this model.
Additionally, User can opt-out the entities which are not required to be the candidates of approot and those function IDs are moved to PDB.

The application name and type of deployment will be stored in CSTB_PARAM table in approot.

Table 3-4 CSTB_PARAM table

PARAM_NAME	PARAM_VAL
MULTI_TENANT_APP_NAME	OBCL
MULTI_TENANT_DEPLOYMENT_MODEL	SA (or) SAUA (or) SASDD (or) SASDC

Object conversion is a one-time activity and if ti is tried again, system will validate based on the availability of cstb_param values.

Parent topic: Steps to be followed