/tags/v22.4/ Recent content in v22.4 on Hugo -- gohugo.io /sicsdocs/technical/misc/technical_changes/22.4/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/22.4/ SE-16384 Eliminate XSD violations # Remove violations of the XSD strict enforcement, partially to support the new .NET Core client and partially to just be correct. Example: SicsWsAdministrationEntryPoint.isAvailable The modifications to the schema are detailed in the XSD Changes section of the system documentation. https://www.w3.org/TR/xmlschema11-1/#cos-element-consistent If the {particles} property contains, either directly, indirectly (that is, within the {particles} property of a contained model group, recursively), or ·implicitly·, two or more element declarations with the same expanded name, then all their type definitions must be the same top-level definition, that is, all of the following must be true: /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/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/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/emessaging_setup/integration/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/emessaging_setup/integration/ /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.