/tags/v4.8/ Recent content in v4.8 on Hugo -- gohugo.io /sicsdocs/technical/desktop/database_preparation/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/database_preparation/ This this section you will find database preparation steps for supported DBMS’es. Oracle Microsoft SQL Server PostgreSQL /sicsdocs/technical/desktop/adh_setup/introduction/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/adh_setup/introduction/ This document describes how to setup DXC SICS in order to be able to use the Automated Document Handling (ADH) functionality both in SICS Workstation and SICS ADH Server. For an easy understanding, all the configuration process is explained following a step-by-step approach. Configuration is stored in the database and shared among SICS Workstation and DXC SICS ADH Server. Specific server settings are described in DXC SICS ADH Server - Setup and Configuration. /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/emessaging_setup/introduction/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/emessaging_setup/introduction/ This document describes how to setup SICS in order to be able to process eMessages both in SICS Workstation and eventually in SICS API Server. For an easy understanding, all the configuration process is explained following a step-by-step approach. /sicsdocs/technical/desktop/installation_guide/introduction/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/installation_guide/introduction/ Welcome to this SICS version! # This document describes the steps that must be followed in order to install SICS in your environment. On a high level, the installation procedure involves three main activities: SICS Software Installation This involves installing the SICS software (including documentation and various other system files), and Business Objects Reporting Universes after downloading from the SICS software delivery site. The installation of the SICS reporting tool (Business Objects) itself, is covered in a different document. /sicsdocs/technical/desktop/schema_browser/introduction/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/schema_browser/introduction/ The Database Schema Browser (DSB) is a tool can be used to check that the database structure (schema) matches the requirements of the SICS runtime image being used. It is also possible to compare two database structures against one another. /sicsdocs/technical/server/api_server/xsd_patterns/introduction/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/xsd_patterns/introduction/ This document explains how Lists (collections) are handled in the SICS API Server XSD files. The document is relevant for developers who program SOAP calls to invoke Web Services. /sicsdocs/sys_admin_guide/segregating_data_by_access_code/introduction_to_access_codes/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/sys_admin_guide/segregating_data_by_access_code/introduction_to_access_codes/ This section describes the SICS “Segregate Data by Access Code” feature. This feature allows data to be segregated between different legal entities sharing the same SICS installation. Usually, these entities will be recorded as different Base Companies in SICS. However, there is also a business requirement that several Base Companies should share the same Access Code. This chapter describes segregating data per Access Code, instead of segregating data per Base Company. /sicsdocs/technical/desktop/installation_guide/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/installation_guide/ /sicsdocs/technical/server/api_server/xsd_patterns/list_elements/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/xsd_patterns/list_elements/ In the SICS API Server XSD’s three different types of lists are used: ReplaceAllList CreateList/AddList UpdateList In the following we will use the example where: ‘Master’ is a domain object. It has 1:M relationship with ‘DetailA’ and ‘DetailB’ objects. ReplaceAllList # This type of ‘List’ is used to perform ‘replaceAll’ operation. The ‘replaceAll’ operation will replace all the existing elements in the collection and add new ones present in the list. /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/adh_setup/prerequisites/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/adh_setup/prerequisites/ The user must have access to a SICS database and have administration access rights. /sicsdocs/technical/desktop/emessaging_setup/prerequisites/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/emessaging_setup/prerequisites/ No prerequisites. /sicsdocs/technical/desktop/installation_guide/sics_software_installation/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/installation_guide/sics_software_installation/ 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: /sicsdocs/technical/desktop/schema_browser/using_the_dsb/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/schema_browser/using_the_dsb/ 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. /sicsdocs/technical/server/api_server/xsd_patterns/appendix_a/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/xsd_patterns/appendix_a/ 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. /sicsdocs/technical/desktop/database_preparation/oracle/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/database_preparation/oracle/ 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. /sicsdocs/technical/desktop/installation_guide/database_structure/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/installation_guide/database_structure/ 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. /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/adh_setup/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/adh_setup/ /sicsdocs/technical/desktop/adh_setup/step_by_step/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/adh_setup/step_by_step/ Create Automated Document Handling Base Data # In the SICS System Administration Utility, open the “Database Updating” function and select “Update Automated Document Handling Data”. Define Processing Options # Open System Parameters and select the Automated Document Handling / Processing Options section. The “XML Input Pattern Generation Algorithm” option defines which logic should be used when automatically generating the input pattern from a document. This functionality is triggered when the user creates a mapping from a specific document already present in the database. /sicsdocs/technical/desktop/emessaging_setup/step_by_step/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/emessaging_setup/step_by_step/ Enable eMessaging module # In order to enable the eMessaging module, the user must enter the module key. This setting must be entered using the System Administration function in either SICS Workstation or SICS System Administration Utility. Once the console has started, click on “System Administration” and select “System Parameter Maintenance” function. A new window will appear. Locate and open the “Module Key” tab, enter in Edit mode and provide the value for"EMessaging Module Unlock Key", as shown in the figure below. /sicsdocs/sys_admin_guide/segregating_data_by_access_code/system_setup/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/sys_admin_guide/segregating_data_by_access_code/system_setup/ This section describes what the SICS System Administrator has to do in order to activate the Access Code features. Note! It is important that these steps are carefully reviewed and executed before allowing users to enter data into the system. Main System Parameter (Enable/Disable Access Code Option) # On the System Parameters, Global Defaults window, you decide whether or not to use data segregation, by selecting or de-selecting the Segregate Data by Access Code check box. /sicsdocs/technical/desktop/installation_guide/database_prep/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/installation_guide/database_prep/ MS SQL Server # Please see Database Preparation for SQL Server. Oracle # Please see Database Preparation for Oracle. PostgreSQL # Please see Database Preparation for PostgreSQL. /sicsdocs/technical/desktop/config_manager/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/config_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/emessaging_setup/v48_change_to_rules/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/emessaging_setup/v48_change_to_rules/ v4.8 Changes to rules # The following rules have been changed and will require action on the part of users to maintain existing (or comparable) functionality. PreviousMessageMappingRule has replaced PreviousMessageReferenceRule. The old rule is still available and both are optional to allow switch-over. Example Mapping Sets and XPATH: NAME FRK_MSG_TYPE IS_NOT_SPECIFIC ORDER_N DESCRIPTION FRK_MATCHING_RULE TA Receiver Ref CP RCSR ACORD_TECHACC N 110 Base Company ID / Agency EXT_MATCH_POP TA Receiver Ref CP RCSR ACORD_TECHACC N 110 TA Sender ID EXT_MATCH_POP TA Receiver Ref CP RCSR ACORD_TECHACC N 110 TA Contract Period Start End EXT_MATCH_POP TA Receiver Ref CP RCSR ACORD_TECHACC N 110 TA Sender Contract Section Reference EXACT_MATCH TA Receiver Ref CP RCSR ACORD_TECHACC N 110 Receiver Contract Reference EXT_MATCH_POP TA Receiver Ref CP RCSR ACORD_TECHACC N 110 TA Receiver Contract Section Reference EXT_MATCH_POP TA Receiver Ref CP HLR ACORD_TECHACC N 112 TA HighLevelReference EXT_MATCH_POP TA Receiver Ref CP HLR ACORD_TECHACC N 112 TA Contract Period Start End EXT_MATCH_POP TA Receiver Ref CP HLR ACORD_TECHACC N 112 Receiver Contract Reference EXT_MATCH_POP TA Receiver Ref Risk Code ACORD_TECHACC N 114 TA Lloyds Risk Code EXT_MATCH_POP TA Receiver Ref Risk Code ACORD_TECHACC N 114 TA Contract Period Start End EXT_MATCH_POP TA Receiver Ref Risk Code ACORD_TECHACC N 114 Receiver Contract Reference EXT_MATCH_POP TA Receiver Ref CP SCSR ACORD_TECHACC N 120 TA Sender Contract Section Reference EXT_MATCH_POP TA Receiver Ref CP SCSR ACORD_TECHACC N 120 TA Contract Period Start End EXT_MATCH_POP TA Receiver Ref CP SCSR ACORD_TECHACC N 120 Receiver Contract Reference EXT_MATCH_POP TA Receiver Ref CP ACORD_TECHACC Y 130 Receiver Contract Reference EXT_MATCH_POP TA Receiver Ref CP ACORD_TECHACC Y 130 TA Contract Period Start End EXT_MATCH_POP TA Sender Ref CP RCSR ACORD_TECHACC N 140 TA Receiver Contract Section Reference EXT_MATCH_POP TA Sender Ref CP RCSR ACORD_TECHACC N 140 TA Sender ID EXT_MATCH_POP TA Sender Ref CP RCSR ACORD_TECHACC N 140 TA Contract Period Start End EXT_MATCH_POP TA Sender Ref CP RCSR ACORD_TECHACC N 140 TA Sender Contract Section Reference EXACT_MATCH TA Sender Ref CP HLR ACORD_TECHACC N 142 TA HighLevelReference EXT_MATCH_POP TA Sender Ref CP HLR ACORD_TECHACC N 142 TA Contract Period Start End EXT_MATCH_POP TA Sender Ref CP HLR ACORD_TECHACC N 142 TA Sender ID EXT_MATCH_POP TA Sender Ref CP Risk Code ACORD_TECHACC N 144 TA Lloyds Risk Code EXT_MATCH_POP TA Sender Ref CP Risk Code ACORD_TECHACC N 144 TA Sender ID EXT_MATCH_POP TA Sender Ref CP Risk Code ACORD_TECHACC N 144 TA Contract Period Start End EXT_MATCH_POP TA Sender Ref CP SCSR ACORD_TECHACC N 150 TA Sender ID EXT_MATCH_POP TA Sender Ref CP SCSR ACORD_TECHACC N 150 TA Contract Period Start End EXT_MATCH_POP TA Sender Ref CP SCSR ACORD_TECHACC N 150 TA Sender Contract Section Reference EXT_MATCH_POP TA Sender Ref CP ACORD_TECHACC Y 160 TA Contract Period Start End EXT_MATCH_POP TA Sender Ref CP ACORD_TECHACC Y 160 TA Sender ID EXT_MATCH_POP Placing Receiver Ref CP RCSR ACORD_PLA N 500 Placing Section Level Sender Contract Section Reference EXT_MATCH_POP Placing Receiver Ref CP RCSR ACORD_PLA N 500 Placing Section Level Receiver Contract Section Reference EXT_MATCH_POP Placing Receiver Ref CP RCSR ACORD_PLA N 500 Receiver Contract Reference EXT_MATCH_POP Placing Receiver Ref CP RCSR ACORD_PLA N 500 Placing Contract Period EXT_MATCH_POP Receiver Contract Reference jv-ins-re:Contract[jv-ins-re:InsurerReference[translate(. /sicsdocs/technical/desktop/installation_guide/co_existence_of_pc_life/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/installation_guide/co_existence_of_pc_life/ Sharing tables and data # Please see the System Administrator Guide for details. Installing a Combined P&C and Life Database # In order to prepare the database to be used by both products, the following procedure MUST be followed: Install both SICS P&C and SICS Life on the same (or two different) PCs Create tables and base data from the SICS Life System Administration Utility (as described in this document) Start the SICS P&C System Administration Utility and execute the following: Update Security Update Reference Data Update EDI Base Data Note that step 2 will create all tables for both the Life system and the P&C system. /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/emessaging_setup/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/emessaging_setup/ /sicsdocs/technical/desktop/installation_guide/appendix_a/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/installation_guide/appendix_a/ 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. /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/server/api_server/xsd_patterns/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/xsd_patterns/ /sicsdocs/technical/desktop/installation_guide/appendix_b/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/installation_guide/appendix_b/ 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. /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/schema_browser/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/schema_browser/ /sicsdocs/technical/desktop/installation_guide/appendix_c/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/installation_guide/appendix_c/ 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. /sicsdocs/technical/desktop/live_desktop_and_sns_server/auto_reg_workstation_with_sns/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/live_desktop_and_sns_server/auto_reg_workstation_with_sns/ 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. /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. /sicsdocs/technical/desktop/installation_guide/appendix_d/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/installation_guide/appendix_d/ 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. /sicsdocs/technical/desktop/installation_guide/appendix_e/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/installation_guide/appendix_e/ Password Handling in Oracle # When using SICS with an Oracle database the user can change his or her password when logging into SICS, assuming the password is not already expired. This feature can be used in combination with user account settings in Oracle such as password lifetime and password validation. Any error message issued by Oracle during login will be presented to the SICS user. The relevant Oracle error messages are: /sicsdocs/technical/desktop/installation_guide/appendix_f/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/installation_guide/appendix_f/ Password Encryption # The database connection password may be encrypted. In the SICS installation folder, there is a file named encrypt.bat. This bat file takes a plain-text string (the password) as input, calls a SICS utility program and outputs an encrypted version of the string. This encrypted value will always be prefixed with % so as to later recognize it as an encrypted value. The encrypted password can be provided in the command line password field and/or the ini file settings password field, see above. /sicsdocs/technical/desktop/installation_guide/appendix_g/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/installation_guide/appendix_g/ Running SICS Scheduler as a Windows Service # SICS Scheduler may be run as a Windows service using the wrapper functionality provided by Apache commons daemon. This applies only when starting the scheduler in unattended mode (using one of the -b options, see Appendix C - Command line parameters). Initial Installation # The SICS System Administration Utility must be installed in a local drive on the computer. The System Administration Utility must be configured to use only resources on local drives on the computer. /sicsdocs/technical/desktop/installation_guide/appendix_h/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/installation_guide/appendix_h/ Splash Screen Branding # The SICS splash screen is graphic shown while SICS loads. This graphic contains a background image and the DXC logo. During the loading process, the SICS version and build information is painted on this graphic to inform the user which version of SICS is loading. The background graphic image changes annually and as part of creating the new graphic, the position of the DXC logo and the SICS version information may change. /sicsdocs/technical/desktop/installation_guide/appendix_i/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/installation_guide/appendix_i/ Setting Additional Database Connection Properties # JDBC Connection parameters can be added to configure different aspects of the connection to the database. Configuration properties are platform specific and not common across DB platforms. For some DB platforms, JDBC connection properties can be provided as part of the connection URL (configured with the <dataSource> tag in sics-database-sources.xml). It is also possible - for all DB platforms - to configure JDBC connection properties on the command line and/or with the <additionalJdbcConnectionProperties> tag in sics-database-sources. /sicsdocs/sys_admin_guide/system_parameters/task_management/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/sys_admin_guide/system_parameters/task_management/ Before the task management functionality can be used, there are a number of setup tasks to be performed. General Settings # Field Description Default language All descriptions and names on Task Management templates are displayed in the language selected.Values: Customized by your company, e.g.:EnglishFrenchGermanItalianNorwegianSpanishDefault: EnglishRelevant when: Your company wants to show the Reference Data values (dropdown lists) in some language other than the default language. Applicable for P&C, Cede, Life Open list of claim TM templates after closing claim worksheet Selected: Upon closing a claim worksheet on a claim where ‘Transfer to Ledger’ is not selected, system automatically opens Task Management / Start Process for the current claimNot selected: Task management is not opened upon saving claim worksheetRelevant when: You want to make sure e.