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. ...
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. ...
The DXC Assure Reinsurance Desktop Launcher components are secured using OAuth2 authorization flow and role based access. There are mainly two type of roles: admin role (a read-write role, can perform modify operations like create, delete and update the environment along with list environments) user role (a read only role, can perform only list environments) The Desktop Launcher is tested with Keycloak an open-source OAuth2 provider. However it is compatible with any OAuth2 provider. ...
SICS is programmed in Java. The SICS programs are compiled into so-called Java byte code format. The SICS Java byte codes are grouped into a number of compressed files called jars. These jars constitute the main part of a SICS installation. In order to run SICS, one must start a Java Virtual Machine (JVM), a computer program in its own right, and tell it where the Java byte code for SICS is stored, i. ...
Overall description # SICS API Server provides access to SICS functionality through Web Services. Web Services is an industry accepted standard for application interoperability. SICS API Server enables the use of SICS as server component in a number of scenarios: Calling SICS functions from other applications, e.g. to request information from the SICS database (for example retrieving information for a business); perform an operation using SICS logic (for example exchanging a monetary amount using SICS’s exchange rates and rules, create a business or renew a business). ...
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. ...
Introduction # This guide will walk you through the steps to set up and run the Operational reporting server application contained in the artifact assure.reinsurance.operational.reporting.ui.zip on your server. SICS Operational Reporting Server is an analytics and visualization web platform to give real-time visualization of operational data within SICS. Prerequisites # Before you begin, ensure you have the following installed on your server: Node.js (version 20.x or later) npm (Node Package Manager) Step 1: Extract the Artifact # Upload or transfer the artifact assure. ...
SICS API Server is a web application running Java 17 or higher. It is designed to be run in any Servlet/JSP-Container compatible with Servlet specification 2.5 or higher and JSP Specification 2.0 or higher. See http://en.wikipedia.org/wiki/List_of_Servlet_containers for a list of Java Servlet Containers. The following description shows how to install Apache Tomcat 10.1 which is a free and commonly used Java Servlet Container from Apache using Java 17 or higher. This does not imply that we promote Tomcat 10. ...
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 17+ 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. ...