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.
...
The user must have access to a SICS database and have administration access rights.
No prerequisites.
Installation Overview # The installation of the SICS software is in three stages:
Installation of the DBMS. Installation of the SICS System Administration Utility. Installation of each SICS client. This chapter describes only the installation of the software prior to setting up all of the database components. For subsequent configuration details see the relevant “Database Preparation” chapter for your database.
In this document it is assumed that the SICS software is installed to the folder:
...
Starting the DSB # The DSB is part of the SICS System Administration Utility. The DSB is located in the ‘Database Setup’ Folder.
Initially, the DSB GUI looks like this:
There are two ‘alias’ entries in the ‘Data sources’ listbox. The first one represents the database one is logged in to. The second one represents the SICS application / runtime image.
Select either data source to populate the ‘Tables’ and ‘Views’ listbox.
...
The following is a list of Web Services which use “List Framework”. This list is not exhaustive and should be considered only as examples.
P&C Claims # S.No Name of the Web Service 1 Create New Claim 2 Update Claim 3 Create and Update Claim FGU 4 Create Headline Loss 5 Update Headline Loss 6 Headline Loss: Retrieve Claim List 7 Move Claim from one Claim Program to Another 8 Create Claim program 9 Update Claim Program 10 Create Claim Group 11 Update Claim Group 12 Delete Claim-to-SOC relation Insurable Object # S.
...
This section describes the necessary database preparation that must be completed before any of the SICS software can be executed. Your DBA will be responsible for correctly configuring and creating the SICS database.
Database setup # Before any of the SICS tables can be created, you will need to create the files necessary for the storage of the database using the DBMS tools. This will generally involve creating the instance, specifying where the tablespace files will be stored, creating and configuring the database for your specific requirements.
...
The format of the SICS database has been designed to be as flexible as possible. Its structure has only been enforced where necessary, allowing for multiple configuration possibilities. The configuration at your site should be determined in advance by your DBA, based on your requirements and the specification of your Database Management System (DBMS).
Note: Terminology in this chapter relates to Oracle. SQL Server does not have the concept of Instances, but the following text still applies.
...
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’.