/sicsdocs/technical/desktop/config_manager/ Recent content in SICS Configuration Manager on Hugo -- gohugo.io /sicsdocs/technical/desktop/config_manager/introduction/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/config_manager/introduction/ The SICS Configuration Manager module enables the user to compare various SICS system settings / base data between two SICS databases (schemas). The differences (delta) are visually presented. From the delta (all of it, or a selected subset), it is possible to generate a batch of SQL statements that will transfer settings from the source schema to the target schema. The SQL statements can be copied to clipboard or applied directly to the target schema. /sicsdocs/technical/desktop/config_manager/overview/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/config_manager/overview/ In the following, ‘Configuration Manager’ will be abbreviated as ‘CM’. The CM allows to select the target SICS schema (provided it is defined in the \runtime\conf\sics-database-sources.xml file) select the entity / table [data provider] to be compared view a short description of the selected entity / table select to show all rows or just those with differences or just those selected display the result of the comparison as pairs of source and target rows display in a different color all dependencies (forward and reverse) between data providers display in a different color all dependencies (forward only) between a data provider and a non-data provider like e. /sicsdocs/technical/desktop/config_manager/initial_setup/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/config_manager/initial_setup/ The SICS Configuration Manager module is protected by a module key. Start SICS System Administration Utility, open System Parameter Maintenance, switch to the Module Key tab and enter the unlock key for the Configuration Manager. The SICS Configuration Manager module is also protected by a usecase. Make sure the source user (see Starting the Configuration Manager) is assigned a user role which contains the usecase ‘Configuration Manager’. /sicsdocs/technical/desktop/config_manager/starting_config_manager/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/config_manager/starting_config_manager/ Start the SICS System Administration Utility. Log in with a source user and select the source environment. The source user (or the associated 2nd level user if using two level login) must have SELECT, UPDATE, DELETE, INSERT rights on all SICS tables in the source schema. In the case of Oracle, the source user must also have SELECT rights on various RDBMS system tables / views containing meta data (SYS.ALL_TAB_COLUMNS and SYS. /sicsdocs/technical/desktop/config_manager/comparing_data/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/config_manager/comparing_data/ Select the desired data provider from the drop down list. Some data providers handle a large number of database rows and there may be a noticeable delay as the data is being read. Let the mouse rest over the selected data provider in the drop down list in order to display hover help describing details about the selected data provider. The data container will show matching source and target rows in pairs, matching by the extended key. /sicsdocs/technical/desktop/config_manager/generating_sql/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/config_manager/generating_sql/ Click the ‘Show SQL…’ button to generate SQL for the selected items. The result will be similar to the following example INSERT INTO REFERENCE_DATA (SUBCLASS, CODE, DATA_TYPE_CODE, IS_ACTIVE, IS_STATIC, IS_USER_DEFINED, IS_DEFAULT, NUMBER_OF_PERIODS, PERIOD_NUMBER, NAME, EXTERNAL_CODE) VALUES (1001, 'AOPDED', '01001', 'Y', 'N', 'Y', 'N', NULL, NULL, 'AOP Deductible', NULL); INSERT INTO REF_TO_REF (FSK_PARENT, FRK_PARENT, FSK_CHILD, FRK_CHILD) VALUES (1001, 'AOPDED', 1004, 'EML'); INSERT INTO REF_TO_REF (FSK_PARENT, FRK_PARENT, FSK_CHILD, FRK_CHILD) VALUES (1001, 'AOPDED', 1004, 'SUMINS'); INSERT INTO REF_TO_REF (FSK_PARENT, FRK_PARENT, FSK_CHILD, FRK_CHILD) VALUES (1001, 'AOPDED', 1004, 'TSI'); The ‘Apply to db’ button will apply the SQL directly on the target schema. /sicsdocs/technical/desktop/config_manager/data_providers/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/config_manager/data_providers/ A number of data providers are available for selection, but every kind of ‘configurable’ data is not covered. Additional data providers may be added to the framework at relatively low cost. In the following, data provider specific details are described. Data Providers for Reference Data # Entities supported: REFERENCE_DATA REF_TO_REF REF_DATA_NAME REF_DATA_TYPE REF_DATA_DEP_TYPE For notes attached to REFERENCE_DATA items, the link goes via a join table REF_TO_NOTE. This may seem to imply that one REFERENCE_DATA item can have several notes. /sicsdocs/technical/desktop/config_manager/noteworthy/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/config_manager/noteworthy/ The two data values "" (empty string) and null (data missing / not present) are considered different, not equal. The source and target systems should be of the same SICS product type. Comparison of a pure P&C system with a Life or combined system may cause the Configuration Manager to report differences that, although the CM will allow it, should NOT be copied from one system to the other. Generating SQL for category 4 means creating DELETE statements.