SICS API Server - P&C - System Administration - Update System Parameters

Please select example from the menu on the left side.

SICS API Server - P&C - System Administration - Update System Parameters

Update System Parameters # Request message # <?xml version="1.0" encoding="UTF-8"?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://www.SicsNt.com/SystemAdministration" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <SOAP-ENV:Header /> <SOAP-ENV:Body> <swsaep:updateSystemParameters xmlns:swsaep="urn:SicsWsSystemAdministrationEntryPoint"> <genericInput /> <updateSystemParametersInput> <systemParameters> <systemParameter xsi:type="ns1:SystemParameterBoolean"> <systemParameterKey>DT_ANN_MSG_ENABLED</systemParameterKey> <systemParameterValue>true</systemParameterValue> </systemParameter> <systemParameter xsi:type="ns1:SystemParameterDate"> <systemParameterKey>DT_ANN_MSG_START</systemParameterKey> <systemParameterValue>2022-07-17</systemParameterValue> </systemParameter> <systemParameter xsi:type="ns1:SystemParameterDate"> <systemParameterKey>DT_ANN_MSG_END</systemParameterKey> <systemParameterValue xsi:nil="true" /> </systemParameter> <systemParameter xsi:type="ns1:SystemParameterString"> <systemParameterKey>DT_ANN_MSG_TXT</systemParameterKey> <systemParameterValue>The System will be upgraded over the weekend of Saturday July 2 to Sunday July 3. All functions will be available from Monday July 4th. ...

SICS API Server - P&C - Task Management - Create Process

Please select example from the menu on the left side.

SICS API Server - P&C - Task Management - Create Process

Create Process # Request message # <?xml version="1.0" encoding="UTF-8"?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <SOAP-ENV:Header /> <SOAP-ENV:Body> <swtmep:createProcess xmlns:swtmep="urn:SicsWsTaskManagementEntryPoint"> <genericInput /> <createProcessInput> <processTemplateReference> <processTemplateIdentifier>T3</processTemplateIdentifier> </processTemplateReference> <processInitiator> <userId>OECKHOFF</userId> </processInitiator> <suggestedActualProcessOwner> <userId>ESKARD</userId> </suggestedActualProcessOwner> <suggestedActualTaskOwner> <userId>GREFSUM</userId> </suggestedActualTaskOwner> <startActiveTaskIfPossible>false</startActiveTaskIfPossible> </createProcessInput> </swtmep:createProcess> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Response message # Response message is not shown.

SICS DOCS installation

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

WebConnectivity Gateway

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

SICS Installation Guide

Authentication & Authorization

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

Background

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