/categories/Desktop/ Recent content in Desktop on Hugo -- gohugo.io /sicsdocs/technical/desktop/emessaging_setup/integration/adept/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/emessaging_setup/integration/adept/ Introduction # This document describes how to set up ACORD message integration between the Adept gateway and SICS as a scheduled job. All the required functionality is included in SICS System Administration Utility, but custom configuration is required. Prerequisites # The URL’s, Subscription and credentials of ADEPT , OAuth Broker details (send as Cedent) and/or OAuth Reinsurer (receive Assumed) should be obtained from ADEPT Services. The SICS eMessaging WebService Interface must be running. /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/live_desktop_and_sns_server/introduction/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/live_desktop_and_sns_server/introduction/ Integration between ’external’ applications and SICS can be carried outat the functional level through SICS API Server and various batch interfaces (MTK, General Interface, etc). Integration can also be carried out at a User Interface (GUI) level through SICS Live Desktop. When SICS Live Desktop is enabled, external applications may use Web Service technology to “call into” a SICS Workstation in order to open specific screens (Business, Claim, eMessaging, etc.). This can facilitate a tighter integration between SICS and workflow or other supporting, client-specific, applications. /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/misc/java_launcher_application/introduction/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/java_launcher_application/introduction/ The SICS Java Launcher is a standalone Java application which can be used for distributing a centrally installed version of DXC SICS to a ’local’ folder. The benefits are: Users do not hold file locks on the central installation. Therefore, it will be possible to replace the central installation with a newer version of SICS. Depending on network configuration, it may be faster to start SICS from the ’local’ folder, once the SICS runtime has been copied to this folder. /sicsdocs/technical/misc/memory_settings/introduction/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/memory_settings/introduction/ This document describes how you may change the memory settings of SICS. For most installations of SICS the standard settings are appropriate. Although the memory settings are carefully tailored to suite the memory usage of SICS, you may need to change them to fit a given SICS installation. Conditions that affect memory usage are data volumes, system settings and the functions and modules of SICS in use. /sicsdocs/technical/misc/sics_docs_installation/introduction/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/sics_docs_installation/introduction/ Introduction to SICS DOCS # SICS DOCS is an integrated (all-in-one-place) HTML-based documentation solution which replaces the “legacy” SICS documentation (collection of PDFs, and Word and Excel documents). SICS DOCS is shipped with DXC SICS (starting from version DXC SICS 4.9.5 and onwards). The goal of SICS DOCS is to deliver a better user experience, by providing: Easy access to the documentation Searchability A move away from proprietary software formats (such as MS Word, MS Excel, MS PowerPoint and Adobe PDF). /sicsdocs/technical/desktop/adh/overview/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/adh/overview/ Overview # Introduction # This facility, usually shortened to ‘ADH’, allows users to convert an electronic document in one format into another - the second format usually being one that SICS itself can understand, typically an eMessaging message (though other formats are supported). It is a powerful addition to SICS, as it widens the scope of the eMessaging interface. Users receiving non-ACORD messages and notifications can transform the original document into the ACORD format, and process the resulting message through the extensive eMessaging solution. /sicsdocs/technical/misc/hw_and_sw_requirements/sics_hardware_requirements/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/hw_and_sw_requirements/sics_hardware_requirements/ End-User PC # The requirements described here, are valid for an end-user who performs normal online (GUI) related tasks and who has SICS Workstation and/or System Administration Utility installed on his own PC. For centralized operation, please see the section on Remote Desktop Operation. For heavy processing, please see the section on SICS Batch Server. For interfacing via the SOAP/XML-based API, please see the section on SICS API Server. /sicsdocs/technical/desktop/emessaging_setup/integration/wc/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/emessaging_setup/integration/wc/ Introduction # This document describes how to set up ACORD message integration between the WebConnectivity Gateway and SICS as a scheduled job. All the required functionality is included in SICS System Administration Utility, but custom configuration is required. Prerequisites # The WebConnectivity WC_MR SOAP interface must be running and the URL known. The URL can be verified in a browser. The SICS eMessaging WebService Interface must be running. For installation instructions please see: SICS eMessaging Server. /sicsdocs/technical/desktop/installation_guide/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/installation_guide/ /sicsdocs/technical/desktop/database_preparation/sql_server/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/database_preparation/sql_server/ 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/misc/java_launcher_application/installation/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/java_launcher_application/installation/ Installing the SICS Java Launcher is a matter of extracting the SicsJavaLauncher.zip file to a suitable location and making the relevant configuration settings in the /conf/SicsJavaLauncher.ini file. The configuration settings are described in detail inside the /resources/SicsJavaLauncher.ini file. The location to the 64-bit JRE 21+ installation can be configured in SicsJavaLauncher.bat. By default the script will look for the JRE inside the SICS Java Launcher install folder. Low-level logging and trouble shooting are supported through log4j. /sicsdocs/technical/misc/sics_docs_installation/installation/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/sics_docs_installation/installation/ Installation of SICS DOCS # Installation on a static web-server # Examples of compatible static web-servers: Apache HTTPD server (open-source) Nginx (open-source) Microsoft IIS Example: The web-server publishing root folder is pre-configured as /var/www/html (hereafter referred to as <publishing_root>). (For further instructions, please refer to the official documentation from your web-server vendor.) Step 1. Unzip # Unzip the ZIP version of the SICS DOCS archives you want to install into a sub-folder of your own choice, under the publishing root folder of your web-server. /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/live_desktop_and_sns_server/overview/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/live_desktop_and_sns_server/overview/ SICS Live Desktop has six main parts: SICS Naming Service (SNS) web services SNS Administration web page SICS Live Desktop URL processing service (SUS) Auto-registration of SICS Workstation with SNS Automatic cleanup of dead sessions Web Service Endpoints (WSE) in SICS Workstation SICS Naming Service is a web application that exposes a set of Web Services. It is the main “hub” in SICS Live Desktop. SNS keeps a register of all running SICS Workstations. /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/adh/processing_options/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/adh/processing_options/ Processing Options # Figure 7 Sys parm processing options There are several system-wide processing options that apply to ADH, and they are set on the window above. Rename document file on import # Item Description Selected The name of the file is appended with the date and time that the import took place. Cleared The name of the file is not changed on import. Relevant when This is important if the name of each import document is always the same when delivered to the inbox. /sicsdocs/technical/desktop/adh/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/adh/ /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/misc/hw_and_sw_requirements/sics_software_requirements/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/hw_and_sw_requirements/sics_software_requirements/ End-User PC # The requirements described here, are valid for an end-user who performs normal online (UI) related tasks and who has SICS installed on his own PC. For centralized operation, please see the section on Remote Desktop Operation. For heavy processing, please see the section on SICS Batch Server. For interfacing via the SOAP/XML-based API, please see the section on SICS API Server. Operating System # These Windows versions are supported (64-bit only): /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/desktop/live_desktop_and_sns_server/communication_overview/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/live_desktop_and_sns_server/communication_overview/ Communication Using Web Services # The following diagram shows how communication takes place between the external application, SNS and SICS Workstation. On startup, SICS Workstation starts listening for incoming Web Service calls and also registers itself with SNS. The end-user performs an action in an external web application. Assuming this is an action which is meant to open a screen in SICS, the external application will continue with step 3. /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/misc/memory_settings/determine_java_version/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/memory_settings/determine_java_version/ The Java version being used can be determined as follows: In Help->About SICS, go to System Info. Select the Java tab The properties java.version and java.runtime.version specifies the Java version. The property sun.arch.data.model specifies if the SICS is 64 or 32 bit. Note that this version of SICS requires 64-bit Java 21+. /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/misc/java_launcher_application/installation_of_new_runtime/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/java_launcher_application/installation_of_new_runtime/ Because the SICS Java Launcher works by copying the DXC SICS runtime from a designated folder (call it F), care should be taken when installing a new runtime. The following procedure is recommended: Install the new runtime in a new folder F2 Rename the ‘old’ runtime folder F to F3 Rename F2 to F Delete or archive F3. /sicsdocs/technical/desktop/adh/output_patterns/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/adh/output_patterns/ Output patterns # Selecting Output patterns from the menu opens a find window where you can select a single pattern for further processing, create a pattern, or import a pattern from outside SICS. Figure 8 Output pattern choice Item Description Name The name given to the output pattern. Active Indicates if the output pattern is active or not. Output type eMessaging Message, External or Tabular. Chosen when the pattern is created. /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/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/database_preparation/postgresql/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/database_preparation/postgresql/ 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/config_manager/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/config_manager/ /sicsdocs/technical/desktop/live_desktop_and_sns_server/sics_naming_service/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/live_desktop_and_sns_server/sics_naming_service/ Brief Description # The SICS Naming Service (SNS) is responsible for mapping users to SICS Workstations. The SNS is a JEE web application based on JAX-WS and the METRO web services stack.It must be run within a JEE application server. The list of registered users / workstations is persisted (stored) in a SICS database. The SNS connects to the database via a JNDI datasource. SNS is stateless. That is, each web service request will read data from the database. /sicsdocs/technical/misc/memory_settings/standard_settings/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/memory_settings/standard_settings/ The use of SICS functions obviously varies from user to user and from one SICS session to another. Likewise, the amount of data being processed varies from user to user and from one SICS session to another. Therefore, it is not possible to pre-set the heap memory size in such a way that, the JVM never runs out of memory, and there is no gross over-allocation of memory. The best one can do, is to pre-set the memory limits such that /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/adh/transformation_mappings/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/adh/transformation_mappings/ Transformation mappings # The [Overview]({{"/sicsdocs/technical/desktop/adh/overview/#" | relative_url}}) section described the basics about mappings. Here, further details are explained. Figure 12 Transformation mapping - selection From this table you can view, edit, copy, create or delete a transformation mapping. Other options include activating or inactivating a mapping, unlinking the mapping from existing documents, and importing/exporting the mapping. Only valid mappings can be activated. Import and export are important for copying a mapping from one environment (e. /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/integration/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/emessaging_setup/integration/ /sicsdocs/technical/misc/memory_settings/identifying_memory_problems/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/memory_settings/identifying_memory_problems/ If SICS terminates (abends) with an error message and one of the first lines of the walkback file is: ... java.lang.OutOfMemoryError: Java heap space ... then you have a heap memory problem. Examples of situations when such an error can occur are: Batch processing Long running task, e.g. accounting orders and periodic functions Reading large amounts of data from the SICS database, for instance, asking the Business Partner Ledger to return more than a few thousand balances. /sicsdocs/technical/desktop/emessaging_setup/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/emessaging_setup/ /sicsdocs/technical/desktop/live_desktop_and_sns_server/sics_live_desktop_url_service/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/live_desktop_and_sns_server/sics_live_desktop_url_service/ Brief Description # The SICS Live Desktop URL Service (SUS) is responsible for processing URL requests and transforming them into SICS Workstation web service calls and invoke the call on the correct SICS Workstation. The SUS is a JEE web application bundled together with the SNS. SUSConfiguration # Some properties of SUSare configurable. Enabling/disabling of SUS # The SUS is enabled by default but can be disabled by setting the context parameter enable. /sicsdocs/technical/desktop/adh/transformation_blocks/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/adh/transformation_blocks/ Transformation Blocks # The transformation mapping is at the heart of ADH. This is the part that links the input pattern to the output pattern, via a series of links and functional blocks. These links and blocks are graphical representations of the mapping process. A link directly between the input and output will copy the incoming value without modification to the output. Adding a block provides scope for transforming the incoming value in various ways. /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/adh/adh_in_workstation/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/adh/adh_in_workstation/ Preceding documents relate to the administrative set-up required to create and manage the mapping tools needed to transform an incoming document into a format that can be understood by SICS. For the general user working with incoming documents, there are three main functions. Import Document # This window allows the user to specify an inbox path and an archive path, and to start the import process. Figure 31 Import doucment /sicsdocs/technical/misc/memory_settings/changing_memory_settings/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/memory_settings/changing_memory_settings/ If you identified a memory problem as described in section 4, you may solve the problem by increasing the appropriate maximum memory size parameter. If you use the standard SICS setup, the Java command line parameters are located in the command files: run_sics_workstation.bat and run_sics_sysadmin.bat. Edit the relevant file and increase the -Xmx value. If you use the SICS Launcher setup the JRE command line parameters are located in the SICSJavaLauncher. /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/live_desktop_and_sns_server/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/live_desktop_and_sns_server/ /sicsdocs/technical/desktop/live_desktop_and_sns_server/sns_administration_web_page/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/live_desktop_and_sns_server/sns_administration_web_page/ The SNS provides a simple web GUI for administration tasks. The following administration tasks are available. List registration entries (which desktops are currently registered) Force de-registration of a single, or selection of desktops Ping registered desktops (check if they are still alive) Remove / de-register desktops that do not respond to a ping call. In addition, the status of the automatic cleanup process is visible in the SNS administration web page, see Automatic cleanup of dead sessions for more details. /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/live_desktop_and_sns_server/install_sns_and_sus/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/live_desktop_and_sns_server/install_sns_and_sus/ The SNS, SNS Administration webpage and SUS is packaged as a single JEE application. The SNS is based on JAX-WS, the METRO web services stack, and JPA for persistency. The SNS Administration webpage and the SUS is based on JSP, Servlets and Javascript. The SNS, SNS Admin webpage and SUS is delivered as a war file to be installed in your JEE application server. 4 war files are delivered: War file Description sns. /sicsdocs/technical/desktop/schema_browser/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/schema_browser/ /sicsdocs/technical/desktop/adh/ref_items_translation_tables/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/adh/ref_items_translation_tables/ Figure 44 Reference items - Translation tables Translate blocks are used to convert message values in to SICS values - and require mapping tables to hold both sides of the mapping. These mapping tables are maintained using the translation table function in Reference items. There are two parts to the transformation table - the table definition, and the table contents. First, we consider the definition of the table. Define new table # Figure 45 Translation tables - Define new table /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/adh/revision_support/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/adh/revision_support/ General concept # This section describes the concept of ‘Revisable Entity’. This concept can be applied to various SICS domain objects, see following sections. A revisable entity can have multiple revisions (versions). Revisions are identified, and ordered, by a sequentially assigned revision number. A revision is ‘current’ if and only if it is the newest revision. Each revision has attributes for ‘comment’ and ‘is current’. There is also typically an audit object attached, with attributes for ‘created by user’, ‘created timestamp’, ’edited by user’, ’edited timestamp’. /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/adh/comparing_two_mappings/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/adh/comparing_two_mappings/ General concept # Manual/visual comparison of graphical ADH mappings is cumbersome. The ‘mapping comparison’ feature will list differences between two mappings (two different mappings, or two revisions of the same mapping) for these items: Output Pattern fields and groups Transformation blocks and their properties Connections Input Pattern fields and groups Output Pattern XSL (XML mappings only) Mapping Detail properties Automatic Corrections Double-clicking any difference belonging to the first 4 categories will highlight that difference in the ‘source’ and ’target’ mapping graphical editor. /sicsdocs/technical/desktop/live_desktop_and_sns_server/configuration_of_sics_workstation/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/live_desktop_and_sns_server/configuration_of_sics_workstation/ Configuration # Certain aspects of the SICS Live Desktop part of SICS workstation can be configured in the file /runtime/conf/sics.global.resource.registry.properties, as follows: # Base URL of the SICS Naming Service, with which this Workstation should register. # This is one of several requirements for activating SICS Live Desktop. # The format is # http[s]://<hostname>:<port>/<contextroot> # The SNS WSDL file will then be available at # <SicsNamingService>/webservice?wsdl # and the SNS web service methods (operations) will be available at # <SicsNamingService>/webservice #SicsNamingService=http://cscsvrosl023v. /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/misc/sics_docs_installation/changes/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/sics_docs_installation/changes/ Significant changes to SICS Docs # 25.1 # Added XSD browsing to SOAP API catalog Refined source code metrics 24.4 # Moved SOAP API catalog out of the release notes to its own section. Added API examples. 23.3 # Added details comments to SOAP API catalog 23.2 # Added basic SOAP API catalog 21.2 # Added Auto Test Code Coverage, Source Code metrics 21.1 # Added Release notes, What’s New, API auto-test results, CVE scan reports /sicsdocs/technical/desktop/adh/xml_tabular_data_support/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/adh/xml_tabular_data_support/ Tabular input data format # ADH can support the generation of a suitable Input Pattern for handling tabular data in an XML input file/document, but only if the input format is as described here. Assume the original document contains a table like this: Q1 Q2 Q3 Q4 Premium 100 100 110 120 Commission 20 25 To be processed as a table in ADH, it must be represented in the XML input file as a <table> element with “number”, “numRows” and “numCols” attributes, and having the following three groups of child elements: /sicsdocs/technical/desktop/live_desktop_and_sns_server/ws_endpoints_in_workstation/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/live_desktop_and_sns_server/ws_endpoints_in_workstation/ Public Web Services # These are the Web Service Endpoints published by SICS Workstation. These services are intended to be called by an external application. All parameters are mandatory unless otherwise indicated. All services will return immediately after processing the request (opening the requested screen). Response: The response data structure consists of 1 field: a textual message. If the request is valid (the correct token is provided, see security below), then the response will consist of an empty message. /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/adh/export_and_import_blocks/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/adh/export_and_import_blocks/ To reuse transformation blocks in various mapping(s), you can use the Export/Import blocks actions located in the the context/popup menu in ADH Edit/View Mapping Window. Export Blocks # This action helps in extracting the selected blocks and connection details to a XML file from source mapping. In the Edit/View Mapping Window, for Validation and Transformation rule. After selecting the required blocks, on opening the context menu, we can see the Export Blocks Action /sicsdocs/technical/desktop/live_desktop_and_sns_server/external_application_implementation/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/live_desktop_and_sns_server/external_application_implementation/ An external application that wants to utilize SICS Live Desktop (SLD) functionality, must be able to communicate with SICS Naming Service and SICS Workstation via Web Service requests according to the WSDL files published by the SICS Naming Service and SICS Workstation. The typical usage pattern is for the external application to use “client stubs” that are generated from the WSDL files. The SICS desktop runtime installation provides Java client stubs for SNS as well as SLD. /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.