v4.8

Appendix A

Technical Doc, Desktop
v4.8

Using Unsupported Database Systems # The document Hardware and Software Requirements lists the kind of RDBMS (database systems) that are officially supported with SICS. DXC does not provide any assistance on installation, nor any bugfixing for unsupported database systems.

Generating SQL

Technical Doc, Desktop
v4.8

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. ...

Appendix B

Technical Doc, Desktop
v4.8

Client Configuration # Configuration Files # SICS has several configuration files: Command line parameters Ini file settings Resource registry settings Log configuration Class loader configuration Command Line Parameters # See Appendix C - Command line parameters Ini File Settings # NOTE: This information does not apply to SICS API Server. Please see separate installation documentation for SICS API Server. The ini file settings serve to configure one or more login properties. ...

Data Providers

Technical Doc, Desktop
v4.8

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. ...

Appendix C

Technical Doc, Desktop
v4.8

Command Line Parameters # SICS Command Line Parameters # NOTE: This information does not apply to SICS API Server. Please see separate installation documentation for SICS API Server. This appendix describes the command line parameters that can be specified in the shortcut that starts the SICS system. SICS command lines follow this template with 6 elements: <Path to JRE><JRE arguments><Main class><Target type><Product><SICS application command line arguments> Element Description <Path to JRE> Path to the Java runtime. ...

Auto-Registration of SICS Workstation with SNS

Technical Doc, Desktop
v4.8

Registration # Upon startup (after login), the SICS Workstation will find an available TCP/IP port and start listening for incoming Web Service calls on this port. Then, it will register itself with SNS, providing the user’s login name (first level user in case of two-level login), database name, database schema and the user’s OS name. SNS will assign and reply a token, which SICS will remember. Note: If the user is logged in as the table owner (empty schema), then the registration will be done using an empty string for database schema, not Java null / database NULL. ...

Noteworthy

Technical Doc, Desktop
v4.8

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. ...

Appendix D

Technical Doc, Desktop
v4.8

Logging of SQL Statements # SICS reads and modifies database information using SQL statements via the JDBC standard interface. For debugging and performance measurement purposes, it may be of interest to review all SQL statements issued by SICS against the database. To do so, one must activate SQL logging. There are two options available: Global activation. This is done in the configuration file log4j2.xml (see Log Configuration above) and will affect all users running SICS from this installation location. ...