/categories/Technical-Doc/ Recent content in Technical Doc on Hugo -- gohugo.io /sicsdocs/technical/misc/technical_changes/26.1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/26.1/ SE-42115 # Added Support for Microsoft SQL Server 2025 https://learn.microsoft.com/en-us/sql/sql-server/what-s-new-in-sql-server-2025 SE-36090 # Added Support for Oracle 26ai https://oracle-base.com/articles/26/articles-26 /sicsdocs/technical/misc/technical_changes/25.4/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/25.4/ SE-38015 # Removed support for PostgreSQL 13 which is now at EOL and Added Support for PostgreSQL 18 https://www.postgresql.org/support/versioning/ SE-36629 # SICS 25.4 ships with Amazon Corretto JRE version 21.0.9.10.1 https://aws.amazon.com/corretto/ /sicsdocs/technical/misc/technical_changes/25.3/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/25.3/ SE-38705 # SICS 25.3 ships with the Amazon Corretto JRE version 21.0.8.9.1 https://aws.amazon.com/corretto/ SE-36612 # Added support for Microsoft Edge WebView2 that allows to embed web content (HTML, CSS, JavaScript) in SICS using the Edge (Chromium) web platform. The WebView2 control uses Microsoft Edge as the rendering engine to display the web content in SICS. https://developer.microsoft.com/en-us/microsoft-edge/webview2/ This is a result of the SWT library upgraded to version 3.126.0. /sicsdocs/technical/misc/technical_changes/25.2/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/25.2/ SE-35337 # Updated 3rd party libraries to their latest version. SICS is now shipped with Amazon Corretto 17.0.15.6.1. Added support for Microsoft Edge WebView2 that allows to embed web content (HTML, CSS, JavaScript) in SICS using the Edge (Chromium) web platform. The WebView2 control uses Microsoft Edge as the rendering engine to display the web content in SICS. https://developer.microsoft.com/en-us/microsoft-edge/webview2/ This is a result of the SWT library upgraded to version 3. /sicsdocs/technical/misc/technical_changes/25.1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/25.1/ SE-32821 # MySQL has been dropped as a supported platform effective from 25.1 Customers looking for a lower cost DBMS platform should target PostgreSQL. SE-31992 # Updated 3rd party libraries to their latest version. SICS is now shipped with Amazon Corretto 17.0.14.7.1. /sicsdocs/technical/misc/technical_changes/24.4/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/24.4/ SE-31692 # Updated 3rd party libraries to their latest version. SICS is now shipped with Amazon Corretto 17.0.13.11.1. /sicsdocs/technical/misc/technical_changes/24.3/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/24.3/ SE-28024 # Updated 3rd party libraries to their latest version. SICS is now shipped with Amazon Corretto 17.0.12.7.1. /sicsdocs/technical/misc/technical_changes/24.2/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/24.2/ SE-27107 # Updated 3rd party libraries to their latest version. SICS is now shipped with Amazon Corretto 17.0.11.9.1. SE-27522 - Asynchronous logging # This release has a new option for asynchronous logging. Configuration details are explained in the System Administrator Guide, under chapter Technical Logging / Log4j Logging. Asynchronous logging is per default disabled. /sicsdocs/technical/misc/technical_changes/24.1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/24.1/ SE-25052 # Updated 3rd party libraries to their latest version. SICS is now shipped with Amazon Corretto 17.0.10.7.1. /sicsdocs/technical/misc/technical_changes/23.4/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/23.4/ SE-22928 # Removed support for Microsoft Windows Server 2012 which is now at EOL for support from Microsoft. https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2012-r2 SE-22292 # Support for Microsoft SQL Server 2022. SE-22292 # Removed support for PostgreSQL 11 https://www.postgresql.org/support/versioning/ SE-22144 # Updated 3rd party libraries to their latest version. SICS is now shipped with Amazon Corretto 17.0.9.8.1. SE-29529 # Updated source name=“JNDI” Instead of “SICSServerJNDI” in sics-database-sources.xml. /sicsdocs/technical/misc/technical_changes/23.3/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/23.3/ SE-21157 # The <caseSensitiveCnuUserNames> tag in the datasource definition controls how the retrieval of the SICS user from the database table handles case. The default value is false, which means that SICS presumes that the user id stored in SICS is in uppercase and it will convert the authentication user id into uppercase in order to retrieve it. In a situation where the authentication user id and the SICS user id are in lowercase or mixed case, then you must set the value to true <caseSensitiveCnuUserNames>true</caseSensitiveCnuUserNames> /sicsdocs/technical/misc/technical_changes/23.2/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/23.2/ SE-18797 # Updated 3rd party libraries to their latest version. Removed the dependency on Apache Xalan to fix CVE-2022-34169. /sicsdocs/technical/misc/technical_changes/23.1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/23.1/ SE-17418 # Removed support for Microsoft Window 8.x which is now at EOL for support from Microsoft. https://learn.microsoft.com/en-us/lifecycle/announcements/windows-8-1-end-support-january-2023 SE-17616 # Updated 3rd party libraries to their latest version. Apache Solr upgraded to version 9.0. https://solr.apache.org/guide/solr/latest/upgrade-notes/major-changes-in-solr-9.html This is a significant upgrade of Solr for Operational Reporting Server, and SICS Search. Be sure to export and import your ORS data as detailed in the system admin guide. See: SICS Operational Reporting Server - Setup and Configuration. /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/misc/technical_changes/22.3/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/22.3/ SE-13088 # Removed support for Microsoft SQL Server 2012 which is now at EOL for support from Microsoft. https://docs.microsoft.com/en-us/lifecycle/products/microsoft-sql-server-2012 Removed support for Oracle 12c which is now at EOL for support from Oracle. https://www.oracle.com/us/support/library/lsp-tech-chart-069290.pdf SE-6370 # Added Support for PostgreSQL 11+ https://www.postgresql.org/files/documentation/pdf/11/postgresql-11-A4.pdf SE-3237 # First delivery of P&C and Life API Server .NET Core Clients. The new clients are compatible with both Windows and Linux. The new clients have not yet been tested with our automated test framework. /sicsdocs/technical/misc/technical_changes/22.2/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/22.2/ SE-11844 # Unicode support in Microsoft SQL Server is now fully implemented via the use of the <unicodeMode>true</unicodeMode> datasource setting. SE-11416 # 3rd party libraries used by SICS has been updated to their latest version, giving SICS access to new functionality and the latest security patches. eMessaging # SICS eMessaging Server now uses JAX-WS for creating and consuming Acord SOAP messages. This was changed to remove the dependency to XMLBeans 3. /sicsdocs/technical/misc/technical_changes/22.1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/22.1/ SE-9505 # Support for Windows Server 2022 SE-11259 # Microsoft Edge is now supported as a replacement for Internet Explorer /sicsdocs/technical/misc/technical_changes/21.4/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/21.4/ SE-8919 # The Axis 1 generated stubs has following minor changes: 1. Array wrappers # Each array type class has been wrapped inside their corresponding wrapper class. Axis1 client (Old) In the example below, you can see that the chainedOperations method was returning an array ChainedOperationResponse[] for all the chained operation responses and also accepting an array ChainedOperationRequest[] for all the chained operation requests. To migrate, simply wrap all array references to their corresponding wrapper classes. /sicsdocs/technical/misc/technical_changes/21.3/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/21.3/ No changes # No technical changes in release 21.3. /sicsdocs/technical/misc/technical_changes/21.2/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/21.2/ SE-1277 # SICS now offically supports MySQL compatible databases. SE-6251 # IBM DB2 was removed as a supported platform. All DB2 related libraries & JDBC drivers were also removed from the delivered software. /sicsdocs/technical/misc/technical_changes/21.1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/21.1/ SE-4218 # Background # 3rd party libraries are starting to require Java 11+. To enable SICS to get access to new functionality and the latest security patches, SICS now requires Java 11+ and is shipped with Amazon Corretto 15.0.2.7.1. JDBC Driver Versions # DBMS JDBC Driver Version Oracle 19.9.0.0 Microsoft SQL Server 9.2.0 MySQL 8.0.23 /sicsdocs/technical/misc/technical_changes/20.4/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/20.4/ SE-3307 # Background # In SE-3307, SICS eMessaging Server was upgraded from using Apache Axis 1.4 SOAP stack to its successor: Apache Axis2 Web services engine due to security vulnerabilities in the Apache Axis 1.4 SOAP stack and also as a technology upgrade to achieve significantly greater speed than earlier versions of Apache Axis. Axis 1 generated client stubs are deprecated, and new client stubs were generated based on Axis2 XML bean data bindings. /sicsdocs/technical/misc/technical_changes/20.3/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/20.3/ SE-3611 # SICS now supports display scaling at 100% & 200% accurately with both fonts & icons displayed at their highest fidelity. Other scaling percentages will work but may introduce some blurriness as the icons are rescaled. We will continue to improve the look of the icons as our capability grows. The runtime argument -Dswt.autoScale=quarter must be present. This is included in the shipped .bat files. /sicsdocs/technical/misc/technical_changes/20.2/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/20.2/ SE-1861 # Adding a new column to an existing table when a default value needs to be set results in SQL to update the entire table. For a table with a large number of rows, this causes a large transaction log in Microsoft SQL Server. To prevent this, large table updates on Microsoft SQL Server will be batched into increments of 10k rows when the Optimized Schema is in use. /sicsdocs/technical/misc/technical_changes/20.1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/20.1/ No technical changes. /sicsdocs/technical/misc/technical_changes/4.9.5/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/4.9.5/ SE-1424 # Background # In SE-1424, SICS API Server was upgraded from using Apache Axis 1.4 SOAP stack to its successor: Apache Axis2 Web services engine due to multiple high-risk security vulnerabilities in the Apache Axis 1.4 SOAP stack. SOAP encoding has been deprecated and is no longer supported by Apache Axis2. SICS API Server with Unrestricted (%NONE%), Axis or .NET Framework (DotNet) compatible WSDL/XSD files was previously using the RPC/encoded style but is now changed to use the RPC/literal style. /sicsdocs/technical/misc/technical_changes/4.8.6/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/4.8.6/ SE-80 # Apache Log4j upgraded to Apache Log4j 2 # Changed to use XML configuration file ’log4j2.xml’ for all SICS products. SICS Desktop - runtime/conf/log4j.properties replaced by runtime/conf/log4j2.xml SICS Servers - WEB-INF/classes/log4j.xml replaced by WEB-INF/classes/log4j2.xml The Log4j 2 configuration syntax is different then Log4j 1.x, but most, if not all, of the same functionality is available. See: Log4j - Migrating from Log4j 1.x - Apache Log4j 2 Apache Solr upgraded to version 7. /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/server/emessaging_server/documentation/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/emessaging_server/documentation/ Delivery contents # This delivery consists of the following components: SicsEMessagingServer.war - Java web application, with WebService interface to SICS eMessaging. WSDL for the interface ACORD documentation A Java command line sample client The individual components are described in greater detail in the respective sections of this document. SICS eMessaging Server # Only the parts of ACORD, 2007 specifically listed in this section are supported by the SICS eMessaging Server. /sicsdocs/technical/server/api_server/installation_guide/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/ /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/desktop_launcher/introduction/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/desktop_launcher/introduction/ The Assure Reinsurance Desktop Launcher is a set of components which can be used for distributing the Assure Re Desktop App from a central location, to a ’local’ folder on the users desktops. Below are the components: Environment Server component (API to manage environments) Environment Admin Web UX (Web user-interface to manage environments) Desktop launching components (Desktop UI to launch the Assure Reinsurance Desktop App) The benefits are: Cloud compatible - the runtime can be stored in any file hosting service in the cloud eco-system (S3, Sharepoint, etc). /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/server/api_server/installation_guide/introduction/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/introduction/ This document describes how to install and configure SICS API Server. SICS API Server can run on 64-bit versions of Windows and Linux. The instructions are based on installation on machines running Microsoft Windows 64 bit. There is also a section on installing SICS API Server on Linux. Main steps Install SICS software products Set up database Test database using GUI-based SICS Configure SICS Install a Java Servlet Container Deploy SICS API Server to the Java Servlet Container Configure the SICS API Server environment Verify correct startup of SICS API Server Steps 1 to 4 are not described in this document and may vary if you are using P&C or Life. /sicsdocs/technical/server/api_server/server_security/introduction/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/server_security/introduction/ SICS API Server is a software component in the SICS product suite. SICS API Server implements the Web Services that allows external applications to call/invoke SICS functions. This document describes the Security features that SICS API Server supports. What this document covers # Security feature Description Authentication How to get SICS API Server to authenticate the sender of Web Services calls. Authorization How to get SICS API Server to check whether a user has the authority (Access Rights) to invoke a web service, and to perform the business logic that is re-used from the SICS on-line system. /sicsdocs/technical/server/api_server/technical_paper/introduction/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/technical_paper/introduction/ SICS API Server is a non-mandatory component in the SICS software package. SICS API Server is a “headless” component that implements Web Services to common SICS functions, allowing other applications, components or front-ends to call SICS business processes directly or via a Services-oriented Architecture (SOA) implementation. This document describes the design of SICS API Server. It explains the basic architecture and important properties. For a full description of the supported Web Services, including WSDL/XSD files and sample SOAP messages, please refer to the documentation that is available after installing SICS API Server. /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/technical/server/batch_server/introduction/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/batch_server/introduction/ The SICS Scheduler system consists of a set of screens in SICS Sys Admin used to set up schedulers and jobs. The schedulers can then be started directly from the SICS Sys Admin which goes into so-called unattended mode and processes jobs. Schedulers can also be started from the command line and many schedulers can run at the same time. Starting from version 4.4.2 there is a new way of running scheduled jobs using the SICS Batch Server. /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/server/operational_reporting/setup_and_configuration/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/operational_reporting/setup_and_configuration/ Requirements # Java 21 or later runtime environment. For best performances, the index should be stored on a unit having a low random-access IO latency, like a SSD. SICS Operational Reporting Server # SICS Operational Reporting Server is an analytics and visualization web platform to give real-time visualization of operational data within SICS. SICS Operational Reporting Server Installation # SICS Operational Reporting Server is a Web Application and can potentially be deployed in any Application Server. /sicsdocs/technical/server/search/setup_and_configuration/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/search/setup_and_configuration/ Requirements # Java 21 or later runtime environment. For best performances, the index should be stored on a unit having a low random-access IO latency, like a SSD. SICS Search Folder Mode # SICS Search Folder Mode is not optimal and can lead to slow search performances and data inconsistency between the index and the database in a multi-user environment. It is therefore advised only for test or demonstration purposes. /sicsdocs/technical/server/api_server/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/ /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBatchProcessEntryPoint/createAccountingOrder/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBatchProcessEntryPoint/createAccountingOrder/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBatchProcessEntryPoint/createAccountingOrder/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBatchProcessEntryPoint/createAccountingOrder/soap1/ Create Accounting Order # Request message # <?xml version="1.0" encoding="ISO-8859-1"?> <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/BatchJobs" 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> <swbpep:createAccountingOrder xmlns:swbpep="urn:SicsWsBatchProcessEntryPoint"> <genericInput /> <createAccountingOrderInput xsi:type="ns1:CessionOrder"> <orderType> <code>CESSION</code> <subclassNumber>191</subclassNumber> </orderType> <title>Cession Order-API</title> <dueDateFrom>2010-01-01</dueDateFrom> <dueDateUpTo>2025-11-10</dueDateUpTo> <shouldCloseWorksheet>true</shouldCloseWorksheet> <extractedAccountingPeriodSet> <code>AYR</code> <subclassNumber>176</subclassNumber> </extractedAccountingPeriodSet> <extractedAccountingYearTo>2010</extractedAccountingYearTo> <extractedAccountingPeriodTo> <code>AYR</code> <subclassNumber>177</subclassNumber> </extractedAccountingPeriodTo> <classifications> <businessTypes> <code>PA</code> <subclassNumber>46</subclassNumber> </businessTypes> <accountClassification> <code>RA</code> <subclassNumber>185</subclassNumber> </accountClassification> </classifications> <businessesList> <businesses> <business> <identifier>IN8955</identifier> </business> <isIncluded>true</isIncluded> </businesses> </businessesList> </createAccountingOrderInput> </swbpep:createAccountingOrder> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Response message # <? /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBatchProcessEntryPoint/createJob/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBatchProcessEntryPoint/createJob/soap1/ Create Job # Request message # <?xml version="1.0" encoding="ISO-8859-1"?> <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/BatchJobs" 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> <swbpep:createJob xmlns:swbpep="urn:SicsWsBatchProcessEntryPoint"> <genericInput /> <createJobInput> <jobIdentifier>job Scheduler</jobIdentifier> <jobActivation> <code>A</code> <subclassNumber>304</subclassNumber> </jobActivation> <priority>0</priority> <desiredScheduler> <name>DEFAULT</name> </desiredScheduler> <desiredStartTime>2025-12-05T13:50:21+00:00</desiredStartTime> <jobStepList> <jobStep xsi:type="ns1:AccountingOrder"> <sequence>1</sequence> <accountingOrder> <identifier>AO3586</identifier> </accountingOrder> </jobStep> </jobStepList> </createJobInput> </swbpep:createJob> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Response message # <?xml version="1.0" encoding="ISO-8859-1"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <swbaep:createJobResponse xmlns:swbaep="urn:SicsWsBatchProcessEntryPoint" xsi:type="swbaep:CreateJobOutput"> <createJobOutput xmlns:ref="http://www.SicsNt.com/ReferenceItems" xsi:type="ref:SicsBatchJobReference"> <jobIdentifier xmlns:cmt="http://www.SicsNt.com/CommonTypes" xsi:type="cmt:String20">job Scheduler</jobIdentifier> </createJobOutput> </swbaep:createJobResponse> </soapenv:Body> </soapenv:Envelope> /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBatchProcessEntryPoint/createOrder/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBatchProcessEntryPoint/createOrder/soap1/ Create Order # Request message # <?xml version="1.0" encoding="ISO-8859-1"?> <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/BatchJobs" 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> <swbpep:createOrder xmlns:swbpep="urn:SicsWsBatchProcessEntryPoint"> <genericInput /> <createOrderInput xsi:type="ns1:RetrocessionProcessingOrder"> <orderSubType> <code>A</code> <subclassNumber>1020</subclassNumber> </orderSubType> <title>API_RPO1</title> <effectivePeriodFrom>2025-02-16T18:55:37+00:00</effectivePeriodFrom> <classificationSelectionByPPSection>true</classificationSelectionByPPSection> <allowMoreThanOnePP>true</allowMoreThanOnePP> <protectionProgramSection> <identifier>PP1545</identifier> <sequenceNumber>0</sequenceNumber> </protectionProgramSection> <classification> <cedent> <identifier>BP590</identifier> </cedent> <baseCompany> <identifier>BP590</identifier> </baseCompany> <reportingUnit> <code>L01</code> </reportingUnit> <excludedRefData> <code>DEATH</code> <subclassNumber>975</subclassNumber> </excludedRefData> <excludedRefData> <code>PTD</code> <subclassNumber>976</subclassNumber> </excludedRefData> </classification> <assumedBusinesses> <assumedBusiness> <identifier>IN7618</identifier> </assumedBusiness> </assumedBusinesses> </createOrderInput> </swbpep:createOrder> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Response message # <? /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/addRealiseNonPropFacOccProtection/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/addRealiseNonPropFacOccProtection/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/addRealiseNonPropFacOccProtection/Assumed-Business/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/addRealiseNonPropFacOccProtection/Assumed-Business/ Add Realise Non Prop Fac Occ Protection # Description # Request message # Response message # /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/addRealizeNonPropFacOccProtectionToLightPolicy/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/addRealizeNonPropFacOccProtectionToLightPolicy/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/addRealizeNonPropFacOccProtectionToLightPolicy/policy_light/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/addRealizeNonPropFacOccProtectionToLightPolicy/policy_light/ Add Realise Non Prop Fac Occ Protection To Light Policy # Description # Request message # Response message # /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/amendClassification/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/amendClassification/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/amendClassification/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/amendClassification/soap1/ Amend Classification # Request message # Response message # /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/createBusinessWithSections/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/createBusinessWithSections/soap1/ Create Business With Sections # Description # Request message # Response message # /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/retrieveReinstatementCondition/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/retrieveReinstatementCondition/soap1/ Create Reinstatement Condition # Request message # <?xml version="1.0" encoding="ISO-8859-1"?> <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> <swbep:createReinstatementCondition xmlns:swbep="urn:SicsWsBusinessEntryPoint"> <genericInput /> <createReinstatementConditionInput> <scopeOfCoverReference> <identifier>IN9045</identifier> <sequenceNumber>0</sequenceNumber> </scopeOfCoverReference> <reinstatementConditionContainer> <isCurrencyOfLoss>true</isCurrencyOfLoss> <reinstatementCalculation> <code>PL</code> <subclassNumber>160</subclassNumber> </reinstatementCalculation> <reinstatementType> <code>SPECIFIC</code> <subclassNumber>130</subclassNumber> </reinstatementType> <exchangeRateOption> <code>DATE</code> <subclassNumber>594</subclassNumber> </exchangeRateOption> <fixedExchangeRateDate>2025-11-03</fixedExchangeRateDate> <fixedExchangeRate> <currency> <isoAlpha>USD</isoAlpha> </currency> <exchangeRateForReinstatement>5</exchangeRateForReinstatement> <exchangeRateNote>EXCHANGE NOTES</exchangeRateNote> </fixedExchangeRate> <reinstatement> <paymentRule> <code>PRORATAMOUNT</code> <subclassNumber>129</subclassNumber> </paymentRule> <percentage>88</percentage> <brokerage>60</brokerage> <brokerageType> <code>PERCENT</code> <subclassNumber>125</subclassNumber> </brokerageType> <reinstatedLiability>89</reinstatedLiability> <comments>Comment Added</comments> </reinstatement> <reinstatement> <paymentRule> <code>PRORATATIME</code> <subclassNumber>129</subclassNumber> </paymentRule> <extraPercentage>70</extraPercentage> <brokerage>50</brokerage> <brokerageType> <code>PERCENT</code> <subclassNumber>125</subclassNumber> </brokerageType> <reinstatedLiability>67</reinstatedLiability> <comments>2nd Reinstatement</comments> </reinstatement> <note>Last Condition</note> </reinstatementConditionContainer> </createReinstatementConditionInput> </swbep:createReinstatementCondition> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Response message # Response message is not shown. /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/retrieveAllAssumedBusinessesLinkedToPlacement/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/retrieveAllAssumedBusinessesLinkedToPlacement/soap1/ Retrieve All Assumed Businesses Linked To Placement # Request message # Response message # /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/updateContractCertaintyCheckList/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/updateContractCertaintyCheckList/soap1/ Update Contract Certainty CheckList # Request message # Response message # /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessPartnerEntryPoint/createOrUpdateCollateral/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessPartnerEntryPoint/createOrUpdateCollateral/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessPartnerEntryPoint/createOrUpdateCollateral/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessPartnerEntryPoint/createOrUpdateCollateral/soap1/ Create Or Update Collateral # Description # Request message # Response message # /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsCommonAccountingEntryPoint/annualBalancePairing/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsCommonAccountingEntryPoint/annualBalancePairing/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsCommonAccountingEntryPoint/annualBalancePairing/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsCommonAccountingEntryPoint/annualBalancePairing/soap1/ Post Booking Review # Request message # Response message # /sicsdocs/technical/server/api_server/soap_library/pc/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/ SOAP webservice documentation # This library contains sample SOAP messages for SICS API Server - P&C. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsPcAccountingEntryPoint/postBookingReview/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsPcAccountingEntryPoint/postBookingReview/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsPcAccountingEntryPoint/postBookingReview/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsPcAccountingEntryPoint/postBookingReview/soap1/ Post Booking Review # 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> <swpaep:postBookingReview xmlns:swpaep="urn:SicsWsPcAccountingEntryPoint"> <genericInput /> <postBookingReview> <accountingPostBookingReview> <worksheetReference> <identifier>TW109075</identifier> </worksheetReference> <selectedReportTypeList> <selectedReportType> <code>CHLOSSINCUR</code> <subclassNumber>1216</subclassNumber> </selectedReportType> </selectedReportTypeList> </accountingPostBookingReview> </postBookingReview> </swpaep:postBookingReview> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Response message # <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <postBookingReviewResponse xmlns="urn:SicsWsPcAccountingEntryPoint"> <postBookingReviewOutput xmlns="" xmlns:acc="http://www.SicsNt.com/Accounting" xsi:type="acc:AccountingPostBookingReviewOutput"> <postBookingReviewReportList xsi:type="acc:ListOfPostBookingReviewReport"> <postBookingReviewReport xsi:type="acc:AccountingPostBookingReviewReport"> <worksheetId xsi:type="xsd:string">TW109075</worksheetId> <reportName xsi:type="xsd:string">Negative Earned Premium</reportName> <businessId xsi:type="xsd:string">PTTY13353</businessId> <sectionName xsi:type="xsd:string">Main Section</sectionName> <accountingClassificationName xsi:type="xsd:string">Property_Fire Insurance</accountingClassificationName> <uwYear xsi:type="xsd:int">2016</uwYear> <baseCurrency xmlns:ref="http://www. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBatchProcessEntryPoint/createAccountingOrder/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBatchProcessEntryPoint/createAccountingOrder/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBatchProcessEntryPoint/createAccountingOrder/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBatchProcessEntryPoint/createAccountingOrder/soap1/ Create Accounting Order # 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/BatchJobs" 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> <swbpep:createAccountingOrder xmlns:swbpep="urn:SicsWsBatchProcessEntryPoint"> <genericInput /> <createAccountingOrderInput xsi:type="ns1:MultiGAAPAccountingOrder"> <title>0526</title> <closeWorksheetAutomatically>true</closeWorksheetAutomatically> <calculationRule xsi:type="ns1:CalculationRulePc"> <blockNegativeAccruals>true</blockNegativeAccruals> <reverseAccruals>true</reverseAccruals> <nonDepositPremiumCalculation>true</nonDepositPremiumCalculation> <onlyUpdateAdjustmentsOnPortfolioProgram>true</onlyUpdateAdjustmentsOnPortfolioProgram> <occurrenceYearReallocationOfAccruals>true</occurrenceYearReallocationOfAccruals> <accumulatedACsplitforAccruals>true</accumulatedACsplitforAccruals> </calculationRule> <currencyConversion> <convertToSectionMainCurrency>true</convertToSectionMainCurrency> <exchangeRateType> <code>DAY</code> <subclassNumber>77</subclassNumber> </exchangeRateType> <exchangeRateCategory> <code>DR</code> <subclassNumber>202</subclassNumber> </exchangeRateCategory> <exchangeRateAsOfType> <code>CURRENT</code> <subclassNumber>201</subclassNumber> </exchangeRateAsOfType> </currencyConversion> <worksheetDetailsOverride> <bookAdjustment>true</bookAdjustment> <populateAccountingPeriod>true</populateAccountingPeriod> </worksheetDetailsOverride> <bookingYearAndPeriod> <bookingYear>2020</bookingYear> <bookingPeriod> <code>M01</code> <subclassNumber>10</subclassNumber> </bookingPeriod> </bookingYearAndPeriod> <orderSelections xsi:type="ns1:OrderSelectionsPc"> <asOfDate>2021-05-26</asOfDate> <includeOnlyBusinessLinkedToPortfolio>true</includeOnlyBusinessLinkedToPortfolio> <excludeBureauBusiness>true</excludeBureauBusiness> <underwritingYearFrom>2020</underwritingYearFrom> <underwritingYearFromUpTo>2021</underwritingYearFromUpTo> <levelOfBusinessList> <levelOfBusiness> <code>IAB</code> <subclassNumber>45</subclassNumber> </levelOfBusiness> <levelOfBusiness> <code>PFP</code> <subclassNumber>45</subclassNumber> </levelOfBusiness> </levelOfBusinessList> <typeOfBusinessList> <typeOfBusiness> <code>PROPTTY</code> <subclassNumber>46</subclassNumber> </typeOfBusiness> <typeOfBusiness> <code>NONPROPTTY</code> <subclassNumber>46</subclassNumber> </typeOfBusiness> </typeOfBusinessList> <mainClassOfBusinessList> <mainClassOfBusiness> <code>AVIATION</code> <subclassNumber>19</subclassNumber> </mainClassOfBusiness> <mainClassOfBusiness> <code>ENERGY</code> <subclassNumber>19</subclassNumber> </mainClassOfBusiness> </mainClassOfBusinessList> <classOfBusinessList> <classOfBusiness> <code>AVIATIONTEST</code> <subclassNumber>3</subclassNumber> </classOfBusiness> <classOfBusiness> <code>ENERGYOF</code> <subclassNumber>3</subclassNumber> </classOfBusiness> </classOfBusinessList> <typeOfParticipationList> <typeOfParticipation> <code>QA</code> <subclassNumber>22</subclassNumber> </typeOfParticipation> <typeOfParticipation> <code>STOPLOSS</code> <subclassNumber>22</subclassNumber> </typeOfParticipation> </typeOfParticipationList> <agreementTypeList> <agreementType> <code>FAC_FAC</code> <subclassNumber>1213</subclassNumber> </agreementType> <agreementType> <code>FAC_OBL</code> <subclassNumber>1213</subclassNumber> </agreementType> </agreementTypeList> <baseCompanyList> <baseCompany> <identifier>111098</identifier> </baseCompany> <baseCompany> <identifier>111095</identifier> </baseCompany> </baseCompanyList> <reportingUnitList> <reportingUnits> <code>AB1</code> </reportingUnits> <reportingUnits> <code>A1</code> </reportingUnits> </reportingUnitList> <masterAgreementList> <masterAgreement> <identifier>SICS3418</identifier> </masterAgreement> <masterAgreement> <identifier>SICS3414</identifier> </masterAgreement> </masterAgreementList> <accountGroupList> <accountGroup> <code>3-10</code> <subclassNumber>225</subclassNumber> </accountGroup> <accountGroup> <code>3-20</code> <subclassNumber>225</subclassNumber> </accountGroup> </accountGroupList> </orderSelections> </createAccountingOrderInput> </swbpep:createAccountingOrder> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Response message # <? /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBatchProcessEntryPoint/createJob/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBatchProcessEntryPoint/createJob/soap1/ Create Job # 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/BatchJobs" 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> <swbpep:createJob xmlns:swbpep="urn:SicsWsBatchProcessEntryPoint"> <genericInput /> <createJobInput> <jobIdentifier>karnakar</jobIdentifier> <jobActivation> <code>A</code> <subclassNumber>304</subclassNumber> </jobActivation> <priority>1</priority> <jobStepList> <jobStep xmlns:bjb="http://www.SicsNt.com/BatchJobs" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" soapenc:arrayType="bjb:JobStep[1]" xsi:type="soapenc:Array"> <JobStep xsi:type="ns1:AccountingOrder"> <sequence>1</sequence> <accountingOrder> <identifier>AO13</identifier> </accountingOrder> </JobStep> </jobStep> </jobStepList> </createJobInput> </swbpep:createJob> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Response message # <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <swbpep:createJobOut xmlns:swbpep="urn:SicsWsBatchProcessEntryPoint" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <createJobOutput xmlns:ref="http://www.SicsNt.com/ReferenceItems" xsi:type="ref:SicsBatchJobReference"> <jobIdentifier xmlns:ct="http://www.SicsNt.com/CommonTypes" xsi:type="ct:String20">karnakar</jobIdentifier> </createJobOutput> </swbpep:createJobOut> </soapenv:Body> </soapenv:Envelope> /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBatchProcessEntryPoint/createOrder/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBatchProcessEntryPoint/createOrder/soap1/ Create Order # 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/BatchJobs" 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> <swbpep:createOrder xmlns:swbpep="urn:SicsWsBatchProcessEntryPoint"> <genericInput /> <createOrderInput xsi:type="ns1:RetrocessionProcessingOrder"> <orderSubType> <code>A</code> <subclassNumber>1020</subclassNumber> </orderSubType> <title>RPKK</title> <effectivePeriodFrom>2018-02-14T13:17:50+00:00</effectivePeriodFrom> <classificationSelectionByPPSection>true</classificationSelectionByPPSection> <protectionProgramSection> <identifier>PP410</identifier> <sequenceNumber>1</sequenceNumber> </protectionProgramSection> <assumedBusinesses> <assumedBusiness xmlns:ref="http://www.SicsNt.com/ReferenceItems" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" soapenc:arrayType="ref:SicsBusinessReference[1]" xsi:type="soapenc:Array"> <SicsBusinessReference> <identifier>IN2835</identifier> </SicsBusinessReference> </assumedBusiness> </assumedBusinesses> </createOrderInput> </swbpep:createOrder> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Response message # <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <swbpep:createOrderOut xmlns:swbpep="urn:SicsWsBatchProcessEntryPoint" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <createOrderOutput xmlns:ref="http://www.SicsNt.com/ReferenceItems" xsi:type="ref:SicsAutomaticOrderReference"> <identifier xmlns:ct="http://www. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/addRealiseNonPropFacOccProtection/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/addRealiseNonPropFacOccProtection/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/addRealiseNonPropFacOccProtection/Assumed-Business/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/addRealiseNonPropFacOccProtection/Assumed-Business/ Add Realise Non Prop Fac Occ Protection # Description # This message creates a new non proportional fac OCC business identifier =SICS2075: Request message # <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> <swbep:addRealiseNonPropFacOccProtection xmlns:swbep="urn:SicsWsBusinessEntryPoint"> <genericInput> <interactiveMessageResponses> <answerYes>BS0225</answerYes> </interactiveMessageResponses> </genericInput> <addRealiseNonPropFacOccProtectionCreateInput> <scopeOfCoverReference> <identifier>NPFAC982A</identifier> <beginDateTime>2025-01-01T00:00:00+00:00</beginDateTime> <sequenceNumber>0</sequenceNumber> </scopeOfCoverReference> <outwardCedentsContractPropertiesList> <outwardCedentsContractProperties> <scopeOfCoverName>Main Section</scopeOfCoverName> <typeOfBusiness> <code>NONPROPFAC</code> <subclassNumber>46</subclassNumber> </typeOfBusiness> <typeOfParticipation> <code>CATCOVER</code> <subclassNumber>22</subclassNumber> </typeOfParticipation> <currency> <isoAlpha>USD</isoAlpha> </currency> </outwardCedentsContractProperties> </outwardCedentsContractPropertiesList> <outwardCedentsContractInsuredPeriodList> <outwardCedentsContractInsuredPeriod> <beginDateTime>2025-01-01T00:00:00+00:00</beginDateTime> <endDateTime>2025-12-31T00:00:00+00:00</endDateTime> </outwardCedentsContractInsuredPeriod> </outwardCedentsContractInsuredPeriodList> <nonPropFacOutwardCedentsContractRetrocessionSharesList> <nonPropFacOutwardCedentsContractRetrocessionShares> <occShareOf100>50</occShareOf100> </nonPropFacOutwardCedentsContractRetrocessionShares> </nonPropFacOutwardCedentsContractRetrocessionSharesList> <nonPropFacOutwardCedentsContractLimitsList> <nonPropFacOutwardCedentsContractLimits> <occLimitPremiumCover>10000</occLimitPremiumCover> <isOccLimitPremiumCoverUnlimited>false</isOccLimitPremiumCoverUnlimited> <occLimitPremiumExcess>10</occLimitPremiumExcess> <occLimitPremiumAggregateLimit>20000</occLimitPremiumAggregateLimit> <isOccLimitPremiumAggregateLimitUnlimited>false</isOccLimitPremiumAggregateLimitUnlimited> <claimBasis> <code>NONE</code> <subclassNumber>95</subclassNumber> </claimBasis> </nonPropFacOutwardCedentsContractLimits> </nonPropFacOutwardCedentsContractLimitsList> <nonPropFacOutwardCedentsContractRetrocessionairePlacementList> <nonPropFacOutwardCedentsContractRetrocessionairePlacement> <businessPartner> <identifier>MAPLE</identifier> </businessPartner> <refLifeCycleStatus> <code>OA</code> <subclassNumber>90</subclassNumber> </refLifeCycleStatus> <grossRetrocededPercentage>50</grossRetrocededPercentage> </nonPropFacOutwardCedentsContractRetrocessionairePlacement> <nonPropFacOutwardCedentsContractRetrocessionairePlacement> <businessPartner> <identifier>STELLAR</identifier> </businessPartner> <refLifeCycleStatus> <code>OA</code> <subclassNumber>90</subclassNumber> </refLifeCycleStatus> <grossRetrocededPercentage>50</grossRetrocededPercentage> </nonPropFacOutwardCedentsContractRetrocessionairePlacement> </nonPropFacOutwardCedentsContractRetrocessionairePlacementList> </addRealiseNonPropFacOccProtectionCreateInput> </swbep:addRealiseNonPropFacOccProtection> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Response message # <soapenv:Envelope xmlns:soapenv="http://schemas. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/addRealizeNonPropFacOccProtectionToLightPolicy/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/addRealizeNonPropFacOccProtectionToLightPolicy/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/addRealizeNonPropFacOccProtectionToLightPolicy/policy_light/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/addRealizeNonPropFacOccProtectionToLightPolicy/policy_light/ Add Realise Non Prop Fac Occ Protection To Light Policy # Description # This message creates a new non proportional fac OCC business identifier =SICS2073: Request message # <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> <swbep:addRealizeNonPropFacOccProtectionToLightPolicy xmlns:swbep="urn:SicsWsBusinessEntryPoint"> <genericInput> <interactiveMessageResponses> <answerYes>BS00655</answerYes> </interactiveMessageResponses> </genericInput> <addNonPropFacOutwardCedentContractToLightPolicyInput> <scopeOfCoverReference> <identifier>PR1011_1</identifier> <beginDateTime>2025-01-01T00:00:00+00:00</beginDateTime> <name>PROPERTY</name> </scopeOfCoverReference> <outwardCedentsContractPropertiesList> <outwardCedentsContractProperties> <title>PR1011_1-OCC1</title> <scopeOfCoverName>Main Section</scopeOfCoverName> <typeOfBusiness> <code>NONPROPFAC</code> <subclassNumber>46</subclassNumber> </typeOfBusiness> <typeOfParticipation> <code>CATCOVER</code> <subclassNumber>22</subclassNumber> </typeOfParticipation> <currency> <isoAlpha>USD</isoAlpha> </currency> </outwardCedentsContractProperties> </outwardCedentsContractPropertiesList> <outwardCedentsContractInsuredPeriodList> <outwardCedentsContractInsuredPeriod> <beginDateTime>2025-01-01T00:00:00+00:00</beginDateTime> <endDateTime>2025-12-31T00:00:00+00:00</endDateTime> </outwardCedentsContractInsuredPeriod> </outwardCedentsContractInsuredPeriodList> <nonPropFacOutwardCedentsContractRetrocessionSharesList> <nonPropFacOutwardCedentsContractRetrocessionShares> <occShareOf100>100</occShareOf100> </nonPropFacOutwardCedentsContractRetrocessionShares> </nonPropFacOutwardCedentsContractRetrocessionSharesList> <nonPropFacOutwardCedentsContractLimitsList> <nonPropFacOutwardCedentsContractLimits> <occLimitPremiumCover /> <isOccLimitPremiumCoverUnlimited>true</isOccLimitPremiumCoverUnlimited> <occLimitPremiumExcess>0</occLimitPremiumExcess> <occLimitPremiumAggregateLimit /> <isOccLimitPremiumAggregateLimitUnlimited>true</isOccLimitPremiumAggregateLimitUnlimited> <claimBasis> <code>NONE</code> <subclassNumber>95</subclassNumber> </claimBasis> </nonPropFacOutwardCedentsContractLimits> </nonPropFacOutwardCedentsContractLimitsList> <nonPropFacOutwardCedentsContractRetrocessionairePlacementList> <nonPropFacOutwardCedentsContractRetrocessionairePlacement> <businessPartner> <identifier>MAPLE</identifier> </businessPartner> <intermediaryBusinessPartner> <identifier>STELLAR</identifier> </intermediaryBusinessPartner> <refLifeCycleStatus> <code>OA</code> <subclassNumber>90</subclassNumber> </refLifeCycleStatus> <grossRetrocededPercentage>5</grossRetrocededPercentage> <accountGroup> <code>NONE</code> <subclassNumber>225</subclassNumber> </accountGroup> </nonPropFacOutwardCedentsContractRetrocessionairePlacement> </nonPropFacOutwardCedentsContractRetrocessionairePlacementList> </addNonPropFacOutwardCedentContractToLightPolicyInput> </swbep:addRealizeNonPropFacOccProtectionToLightPolicy> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Response message # <soapenv:Envelope xmlns:soapenv="http://schemas. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/amendClassification/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/amendClassification/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/amendClassification/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/amendClassification/soap1/ Amend Classification # 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> <swbep:amendClassification xmlns:swbep="urn:SicsWsBusinessEntryPoint"> <amendClassificationInput> <scopeOfCoverReference> <identifier>NPTTY13</identifier> <beginDateTime>2002-01-01T00:00:00</beginDateTime> <sequenceNumber>0</sequenceNumber> <name>Main Section</name> </scopeOfCoverReference> <amendmentNumber>2</amendmentNumber> </amendClassificationInput> </swbep:amendClassification> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Response message # Response message is not shown. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/createBusinessWithSections/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/createBusinessWithSections/soap1/ Create Business With Sections # Description # This message creates a new Business with one insured period and a main section and multiple child sections with identifier =UMA-PC-SECTIONS: Request message # <SOAP-ENV:Envelope SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SOAP-ENV:Body> <swbep:createBusinessWithSections xmlns:swbep="urn:SicsWsBusinessEntryPoint"> <genericInput> </genericInput> <createBusinessWithSectionsInput> <createBusinessInput> <title>UMA - Create with Sections</title> <identifierPrefix>UMA-PC-SECTIONS</identifierPrefix> <identifierSerieNumber>3</identifierSerieNumber> <identifierSuffix>A</identifierSuffix> <businessDirection> <code>PAB</code> <subclassNumber>45</subclassNumber> </businessDirection> <typeOfBusiness> <code>DIRECT</code> <subclassNumber>46</subclassNumber> </typeOfBusiness> <insuredPeriod> <beginDateTime>2004-01-01T00:00:00+00:00</beginDateTime> <endDateTime>2004-12-31T00:00:00+00:00</endDateTime> <underwritingYear>2004</underwritingYear> <canBeAutoProtected>true</canBeAutoProtected> <businessPartnerRelationship> <businessPartner> <identifier>00190</identifier> </businessPartner> <relationshipType> <code>RR</code> <subclassNumber>55</subclassNumber> </relationshipType> </businessPartnerRelationship> <businessPartnerRelationship> <businessPartner> <identifier>00193</identifier> </businessPartner> <relationshipType> <code>IR</code> <subclassNumber>55</subclassNumber> </relationshipType> <businessPartnerIdentifier>00191</businessPartnerIdentifier> <businessPartnerName>UMA CEDENT</businessPartnerName> </businessPartnerRelationship> <lifeCyclePhase> <lifeCycleStatus> <refAgreementLifeCycleStatus> <code>OA</code> <subclassNumber>90</subclassNumber> </refAgreementLifeCycleStatus> </lifeCycleStatus> <scopeOfCover> <currency> <isoAlpha>EUR</isoAlpha> </currency> <classification> <includedCountries> <isoAlpha3>USA</isoAlpha3> </includedCountries> <includedRefData> <code>LIABILITY</code> <subclassNumber>19</subclassNumber> </includedRefData> <includedRefData> <code>LIABPROF</code> <subclassNumber>3</subclassNumber> </includedRefData> </classification> <shareCondition> <signedSharePercent>100</signedSharePercent> </shareCondition> </scopeOfCover> </lifeCyclePhase> </insuredPeriod> </createBusinessInput> <PcScopeOfCoverList> <PcScopeOfCoverInput> <PcScopeOfCover> <name>Section 1</name> <currency> <isoAlpha>EUR</isoAlpha> </currency> <classification> <includedCountries> <isoAlpha3>USA</isoAlpha3> </includedCountries> <includedRefData> <code>LIABILITY</code> <subclassNumber>19</subclassNumber> </includedRefData> <includedRefData> <code>LIABPROF</code> <subclassNumber>3</subclassNumber> </includedRefData> <enlargeParentClassification>true</enlargeParentClassification> </classification> <limitPremiumCondition> <currencyForLimitPremium> <currency> <isoAlpha>EUR</isoAlpha> </currency> </currencyForLimitPremium> <limitCondition> <isOriginal>false</isOriginal> <refConditionPer> <code>TOTAL_SUM</code> <subclassNumber>542</subclassNumber> </refConditionPer> <limit> <currency> <isoAlpha>EUR</isoAlpha> </currency> <refOptionalField> <code>MAIN_L</code> <subclassNumber>1001</subclassNumber> </refOptionalField> <refLimitType> <code>SUMINS</code> <subclassNumber>1004</subclassNumber> </refLimitType> <amount>25000000</amount> <isAdded>true</isAdded> </limit> <limit> <currency> <isoAlpha>EUR</isoAlpha> </currency> <refOptionalField> <code>TL_LOSSPR</code> <subclassNumber>1001</subclassNumber> </refOptionalField> <refLimitType> <code>NONE</code> <subclassNumber>1004</subclassNumber> </refLimitType> <amount>20000000</amount> <isAdded>true</isAdded> </limit> </limitCondition> <refCoverBasis> <code>GR</code> <subclassNumber>411</subclassNumber> </refCoverBasis> <isOriginalCostParticipation>false</isOriginalCostParticipation> <mainSumUpToParentSection>true</mainSumUpToParentSection> <refPremiumType> <code>PF_PROP</code> <subclassNumber>134</subclassNumber> </refPremiumType> </limitPremiumCondition> </PcScopeOfCover> </PcScopeOfCoverInput> <PcScopeOfCoverInput> <PcScopeOfCover> <name>Section 2</name> <currency> <isoAlpha>EUR</isoAlpha> </currency> <classification> <includedCountries> <isoAlpha3>USA</isoAlpha3> </includedCountries> <includedRefData> <code>LIABILITY</code> <subclassNumber>19</subclassNumber> </includedRefData> <includedRefData> <code>LIABPER</code> <subclassNumber>3</subclassNumber> </includedRefData> <includedRefData> <code>LIABILITY</code> <subclassNumber>19</subclassNumber> </includedRefData> <includedRefData> <code>LIABPER</code> <subclassNumber>3</subclassNumber> </includedRefData> <includedRefData> <code>LIABILITY</code> <subclassNumber>19</subclassNumber> </includedRefData> <includedRefData> <code>LIABPER</code> <subclassNumber>3</subclassNumber> </includedRefData> <includedRefData> <code>LIABILITY</code> <subclassNumber>19</subclassNumber> </includedRefData> <includedRefData> <code>LIABPER</code> <subclassNumber>3</subclassNumber> </includedRefData> <enlargeParentClassification>true</enlargeParentClassification> </classification> <limitPremiumCondition> <currencyForLimitPremium> <currency> <isoAlpha>EUR</isoAlpha> </currency> </currencyForLimitPremium> <limitCondition> <isOriginal>false</isOriginal> <refConditionPer> <code>TOTAL_SUM</code> <subclassNumber>542</subclassNumber> </refConditionPer> <limit> <currency> <isoAlpha>EUR</isoAlpha> </currency> <refOptionalField> <code>MAIN_L</code> <subclassNumber>1001</subclassNumber> </refOptionalField> <refLimitType> <code>SUMINS</code> <subclassNumber>1004</subclassNumber> </refLimitType> <amount>25000000</amount> <isAdded>true</isAdded> </limit> <limit> <currency> <isoAlpha>EUR</isoAlpha> </currency> <refOptionalField> <code>TL_LOSSPR</code> <subclassNumber>1001</subclassNumber> </refOptionalField> <refLimitType> <code>NONE</code> <subclassNumber>1004</subclassNumber> </refLimitType> <amount>20000000</amount> <isAdded>true</isAdded> </limit> <limit> <currency> <isoAlpha>EUR</isoAlpha> </currency> <refOptionalField> <code>MAIN_L</code> <subclassNumber>1001</subclassNumber> </refOptionalField> <refLimitType> <code>SUMINS</code> <subclassNumber>1004</subclassNumber> </refLimitType> <amount>25000000</amount> <isAdded>true</isAdded> </limit> <limit> <currency> <isoAlpha>EUR</isoAlpha> </currency> <refOptionalField> <code>TL_LOSSPR</code> <subclassNumber>1001</subclassNumber> </refOptionalField> <refLimitType> <code>NONE</code> <subclassNumber>1004</subclassNumber> </refLimitType> <amount>20000000</amount> <isAdded>true</isAdded> </limit> <limit> <currency> <isoAlpha>EUR</isoAlpha> </currency> <refOptionalField> <code>MAIN_L</code> <subclassNumber>1001</subclassNumber> </refOptionalField> <refLimitType> <code>SUMINS</code> <subclassNumber>1004</subclassNumber> </refLimitType> <amount>25000000</amount> <isAdded>true</isAdded> </limit> <limit> <currency> <isoAlpha>EUR</isoAlpha> </currency> <refOptionalField> <code>TL_LOSSPR</code> <subclassNumber>1001</subclassNumber> </refOptionalField> <refLimitType> <code>NONE</code> <subclassNumber>1004</subclassNumber> </refLimitType> <amount>20000000</amount> <isAdded>true</isAdded> </limit> <limit> <currency> <isoAlpha>EUR</isoAlpha> </currency> <refOptionalField> <code>MAIN_L</code> <subclassNumber>1001</subclassNumber> </refOptionalField> <refLimitType> <code>SUMINS</code> <subclassNumber>1004</subclassNumber> </refLimitType> <amount>25000000</amount> <isAdded>true</isAdded> </limit> <limit> <currency> <isoAlpha>EUR</isoAlpha> </currency> <refOptionalField> <code>TL_LOSSPR</code> <subclassNumber>1001</subclassNumber> </refOptionalField> <refLimitType> <code>NONE</code> <subclassNumber>1004</subclassNumber> </refLimitType> <amount>20000000</amount> <isAdded>true</isAdded> </limit> </limitCondition> <refCoverBasis> <code>GR</code> <subclassNumber>411</subclassNumber> </refCoverBasis> <isOriginalCostParticipation>false</isOriginalCostParticipation> <mainSumUpToParentSection>true</mainSumUpToParentSection> <refPremiumType> <code>PF_PROP</code> <subclassNumber>134</subclassNumber> </refPremiumType> </limitPremiumCondition> </PcScopeOfCover> </PcScopeOfCoverInput> </PcScopeOfCoverList> </createBusinessWithSectionsInput> </swbep:createBusinessWithSections> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Response message # <soapenv:Envelope xmlns:soapenv="http://schemas. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/retrieveReinstatementCondition/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/retrieveReinstatementCondition/soap1/ Create Reinstatement Condition # 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> <swbep:createReinstatementCondition xmlns:swbep="urn:SicsWsBusinessEntryPoint"> <createReinstatementConditionInput> <scopeOfCoverReference> <identifier>NPTTY13</identifier> <beginDateTime>2002-01-01T00:00:00</beginDateTime> <sequenceNumber>0</sequenceNumber> <name>Main Section</name> </scopeOfCoverReference> <reinstatementConditionContainer> <isCurrencyOfLoss>false</isCurrencyOfLoss> <reinstatementType> <code>SPECIFIC</code> <subclassNumber>130</subclassNumber> </reinstatementType> <reinstatement> <paymentRule> <code>PRORATAMOUNT</code> <subclassNumber>129</subclassNumber> </paymentRule> <extraPercentage>11.1</extraPercentage> <brokerage>22.5</brokerage> <brokerageType> <code>PERCENT</code> <subclassNumber>125</subclassNumber> </brokerageType> </reinstatement> <reinstatement> <paymentRule> <code>PRORATAMOUNT</code> <subclassNumber>129</subclassNumber> </paymentRule> <percentage>1</percentage> <extraPercentage>1</extraPercentage> <brokerage>100</brokerage> <brokerageType> <code>PERCENT</code> <subclassNumber>125</subclassNumber> </brokerageType> </reinstatement> </reinstatementConditionContainer> </createReinstatementConditionInput> </swbep:createReinstatementCondition> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Response message # Response message is not shown. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/retrieveAllAssumedBusinessesLinkedToPlacement/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/retrieveAllAssumedBusinessesLinkedToPlacement/soap1/ Retrieve All Assumed Businesses Linked To Placement # 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> <swbep:retrieveAllAssumedBusinessesLinkedToPlacement xmlns:swbep="urn:SicsWsBusinessEntryPoint"> <genericInput /> <retrieveAllAssumedBusinessesLinkedToPlacementInput> <insuredPeriodReference> <objectId>0E08D43E37E811E8AB2415DE0E4A051D</objectId> <identifier>OCC12670-1</identifier> </insuredPeriodReference> </retrieveAllAssumedBusinessesLinkedToPlacementInput> </swbep:retrieveAllAssumedBusinessesLinkedToPlacement> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Response message # <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <swbep:retrieveAllAssumedBusinessesLinkedToPlacementOut xmlns:swbep="urn:SicsWsBusinessEntryPoint" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <retrieveAllAssumedBusinessesLinkedToPlacementOutput xmlns:bus="http://www.SicsNt.com/Business" xsi:type="bus:retrieveAllAssumedBusinessesLinkedToPlacementOutput"> <linkedAssumedBusiness xsi:type="bus:LinkedAssumedBusinessList"> <linkedAssumedBusinesses xsi:type="bus:AssumedBusinessList"> <identifier xsi:type="xsd:string">PTTY14269</identifier> <levelOfBusinessString xsi:type="xsd:string">Assumed Business</levelOfBusinessString> <scopeOfCoverString xsi:type="xsd:string">Main Section - ST17035</scopeOfCoverString> <underwritingYear xsi:type="xsd:int">2016</underwritingYear> <typeOfBusinessString xsi:type="xsd:string">Proportional Treaty</typeOfBusinessString> <basicStatusString xsi:type="xsd:string">Definite</basicStatusString> <retrocededPercentage xmlns:ct="http://www. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/updateContractCertaintyCheckList/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/updateContractCertaintyCheckList/soap1/ Update Contract Certainty CheckList # 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> <swbep:updateContractCertaintyCheckList xmlns:swbep="urn:SicsWsBusinessEntryPoint"> <genericInput /> <updateContractCertaintyCheckListInput> <insuredPeriod> <identifier>PTTY2171</identifier> <beginDateTime>2011-01-01T00:00:00+00:00</beginDateTime> </insuredPeriod> <contractCertaintyCheckList> <insuredPeriodContractCertaintyCheckDetailUpdate> <contractCertaintyCheckDetailKey> <uniqueId>1</uniqueId> </contractCertaintyCheckDetailKey> <contractCertaintyCheckDetail> <isActive>true</isActive> </contractCertaintyCheckDetail> </insuredPeriodContractCertaintyCheckDetailUpdate> </contractCertaintyCheckList> </updateContractCertaintyCheckListInput> </swbep:updateContractCertaintyCheckList> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Response message # Response message is not shown. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessPartnerEntryPoint/createOrUpdateCollateral/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessPartnerEntryPoint/createOrUpdateCollateral/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessPartnerEntryPoint/createOrUpdateCollateral/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessPartnerEntryPoint/createOrUpdateCollateral/soap1/ Create Or Update Collateral # Description # Creating Collateral using createOrUpdateCollateral API. Request message # <?xml version="1.0" encoding="ISO-8859-1"?> <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> <swbpep:createOrUpdateCollateral xmlns:swbpep="urn:SicsWsBusinessPartnerEntryPoint"> <genericInput /> <createOrUpdateCollateralInput> <businessPartnerReference> <identifier>S165</identifier> </businessPartnerReference> <collateral> <letterOfCredit> <issuingBank> <identifier>ABB1</identifier> <partyIdentifierType> <code>BID</code> <subclassNumber>35</subclassNumber> </partyIdentifierType> </issuingBank> <identifier>A1</identifier> <effectiveDate>2023-03-14</effectiveDate> <expirationDate>2023-03-14</expirationDate> <originalAmount>2000</originalAmount> <originalCurrency> <isoAlpha>ADP</isoAlpha> </originalCurrency> <collateralDetailsList> <collateralDetail> <loCAmountType> <code>INCREASE</code> <subclassNumber>1238</subclassNumber> </loCAmountType> <bankDate>2023-03-01</bankDate> <amount>45</amount> </collateralDetail> <collateralDetail> <loCAmountType> <code>DECREASE</code> <subclassNumber>1238</subclassNumber> </loCAmountType> <bankDate>2023-03-02</bankDate> <amount>23.1</amount> </collateralDetail> </collateralDetailsList> <collateralPercentage>75. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsPcClaimEntryPoint/moveLightClaim/move_light_claim/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsPcClaimEntryPoint/moveLightClaim/move_light_claim/ Move LightClaim # Description # This message moves a lightClaim from one section to another. Request message # <?xml version="1.0" encoding="ISO-8859-1"?> <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> <swpclm:moveLightClaim xmlns:swpclm="urn:SicsWsPcClaimEntryPoint"> <genericInput /> <moveLightClaimInput> <policyLight> <identifier>PR0220_1</identifier> </policyLight> <lightClaim> <claimIdentifier>PR0220_1-1A</claimIdentifier> </lightClaim> <targetSection> <identifier>PR0220_1</identifier> <beginDateTime>2025-01-01T00:00:00+00:00</beginDateTime> <name>FIRE</name> </targetSection> </moveLightClaimInput> </swpclm:moveLightClaim> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Response message # <?xml version="1.0" encoding="ISO-8859-1"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <swpclm:moveLightClaimResponse xmlns:swpclm="urn:SicsWsPcClaimEntryPoint" xsi:type="swpclm:MoveLightClaimOutput" /> </soapenv:Body> </soapenv:Envelope> /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsCommonAccountingEntryPoint/annualBalancePairing/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsCommonAccountingEntryPoint/annualBalancePairing/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsCommonAccountingEntryPoint/annualBalancePairing/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsCommonAccountingEntryPoint/annualBalancePairing/soap1/ Post Booking Review # 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> <swcaep:annulBalancePairing xmlns:swcaep="urn:SicsWsCommonAccountingEntryPoint"> <genericInput /> <annulBalancePairing> <pairingObjectIdReference>89A92A5E85054218ACA4C980768A8B03</pairingObjectIdReference> </annulBalancePairing> </swcaep:annulBalancePairing> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Response message # <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <swcaep:annulBalancePairingResponse xmlns:swcaep="urn:SicsWsCommonAccountingEntryPoint" xsi:type="swcaep:AnnulBalancePairingOutput" /> </soapenv:Body> </soapenv:Envelope> /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsDocumentProductionEntryPoint/populateTemplateString/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsDocumentProductionEntryPoint/populateTemplateString/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsDocumentProductionEntryPoint/populateTemplateString/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsDocumentProductionEntryPoint/populateTemplateString/soap1/ Populate Template String # Request # <SOAP-ENV:Envelope SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ref="http://www.SicsNt.com/ReferenceItems" xmlns:SicsNt="http://www.SicsNt.com/SicsNt" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SOAP-ENV:Body> <swdpep:populateTemplateString xmlns:swdpep="urn:SicsWsDocumentProductionEntryPoint"> <PopulateTemplateStringRequest xsi:type="PopulateTemplateStringRequest"> <sourceString xsi:type="xsd:string">Reinsurance Engine Document Production Test: Business Identifier: <#lifeCyclePhase.business.identifier> Business Title: <#lifeCyclePhase.business.title> Insured Period: <#lifeCyclePhase.insuredPeriod.startDate> - <#lifeCyclePhase.insuredPeriod.endDate></sourceString> <sourceInterfaceClass xsi:type="xsd:string">SicsLifeCyclePhaseExternalInterface</sourceInterfaceClass> <sourceObject xsi:type="ref:SicsObjectReference"> <referenceClass xsi:type="xsd:string">SicsLifeCyclePhase</referenceClass> <objectId xsi:type="">F5206FBE7127D611B06700508BACE5A2</objectId> </sourceObject> <showTagsInResult xsi:type="xsd:boolean">false</showTagsInResult> </PopulateTemplateStringRequest> </swdpep:populateTemplateString> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Response # The following text was returned as output for the above input. ‘Reinsurance Engine Document Test Business Identifier: SICS1 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsDocumentProductionEntryPoint/produceDocument/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsDocumentProductionEntryPoint/produceDocument/soap1/ Produce Document # Request # <?xml version="1.0" encoding="UTF-8"?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SicsNt="http://www.SicsNt.com/SicsNt" xmlns:ref="http://www.SicsNt.com/ReferenceItems" 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:Body> <swdpep:produceDocument xmlns:swdpep="urn:SicsWsDocumentProductionEntryPoint"> <ProduceDocumentRequest xsi:type="ProduceDocumentRequest"> <templateSubCategory xsi:type="xsd:string">COVNOT</templateSubCategory> <templateTitle xsi:type="xsd:string">CAJ TEST</templateTitle> <sourceInterfaceClass xsi:type="xsd:string">SicsLifeCyclePhaseExternalInterface</sourceInterfaceClass> <sourceObject xsi:type="ref:SicsObjectReference"> <referenceClass xsi:type="xsd:string">SicsLifeCyclePhase</referenceClass> <objectId xsi:type="">F5206FBE7127D611B06700508BACE5A2</objectId> </sourceObject> </ProduceDocumentRequest> </swdpep:produceDocument> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Response # The above input created a new cover note document in a test database, attached to the relevant business object (the relevant lifeCyclePhase of that business to be exact). The output from this service was simply the document identifier: ‘COV_422’ /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsDomainRetrievalEntryPoint/retrieveObject/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsDomainRetrievalEntryPoint/retrieveObject/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsDomainRetrievalEntryPoint/retrieveObject/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsDomainRetrievalEntryPoint/retrieveObject/soap1/ Retrieve Object # Description # This message retrieves the following fields on a business with identifier = NPTTY1A: Object Field Description Business title The business title Insured Period beginDateTime The Insured Period begin-date Insured Period beginEndTime The Insured Period end-date Request message # <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <ep:retrieveObject soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://www.SicsNt.com/DomainRetrieval" xmlns:sri="http://www.SicsNt.com/ReferenceItems" xmlns:ep="urn:SicsWsDomainRetrievalEntryPoint"> <input> <referenceObject xsi:type="sri:SicsBusinessReference"> <identifier>NPTTY1A</identifier> </referenceObject> <specification> <elementSpecification> <name>title</name> </elementSpecification> <elementSpecification> <name>insuredPeriod</name> <elementSpecification> <name>beginDateTime</name> </elementSpecification> <elementSpecification> <name>endDateTime</name> </elementSpecification> </elementSpecification> </specification> </input> </ep:retrieveObject> </soapenv:Body> </soapenv:Envelope> Response message # <SOAP-ENV:Envelope SOAP-ENV:encodingStyle="http://schemas. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsMigrationEntryPoint/fastCreateClaimWorksheet/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsMigrationEntryPoint/fastCreateClaimWorksheet/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsMigrationEntryPoint/fastCreateClaimWorksheet/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsMigrationEntryPoint/fastCreateClaimWorksheet/soap1/ Fast Create Claim Worksheet # 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/SystemTypes" xmlns:ns2="http://www.SicsNt.com/CommonTypes" xmlns:ns3="http://www.SicsNt.com/Migration" xmlns:ns4="http://www.SicsNt.com/Accounting" xmlns:ns5="http://www.SicsNt.com/ReferenceItems" 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> <swmep:fastCreateClaimWorksheet xmlns:swmep="urn:SicsWsMigrationEntryPoint"> <genericInput xsi:type="ns1:SicsGenericInput" /> <fastCreateClaimWorksheet xsi:type="ns3:SicsFastCreateClaimWorksheetInput"> <worksheet xsi:type="ns4:FastAccountingClaimWorksheetCreate"> <title xsi:type="ns2:String30">title</title> <businessPartnerReference xsi:type="ns2:String40">businessPartnerReference</businessPartnerReference> <comment xsi:type="xsd:string">comment</comment> <policyId xsi:type="ns2:String20">policyId</policyId> <identifierPrefix xsi:type="ns2:String10">FCW</identifierPrefix> <identifierSerieNumber xsi:type="xsd:int">2</identifierSerieNumber> <identifierYearPart xsi:type="xsd:int">2011</identifierYearPart> <dateOfBooking xsi:type="xsd:date">2013-02-08</dateOfBooking> <isVatToBeCalculatedOnGross xsi:type="xsd:boolean">true</isVatToBeCalculatedOnGross> <worksheetAsSpecial xsi:type="xsd:boolean">false</worksheetAsSpecial> <origin xsi:type="ns5:SicsReferenceDataReference"> <code xsi:type="ns5:ReferenceDataCode">MAN</code> <subclassNumber xsi:type="ns5:SubclassNumber">220</subclassNumber> </origin> <registeredBy xsi:type="ns5:SicsUserReference"> <userId xsi:type="ns2:String32">HARALD</userId> </registeredBy> <registrationTimestamp xsi:type="xsd:dateTime">2013-03-05T16:38:10+00:00</registrationTimestamp> <worksheetWorkingInformation xsi:type="ns4:FastWorksheetWorkingInformation"> <receivedDate xsi:type="xsd:date">2013-03-01</receivedDate> <receivedInternalDate xsi:type="xsd:date">2013-03-02</receivedInternalDate> </worksheetWorkingInformation> <worksheetLedgerEntryList xsi:type="ns4:FastWorksheetLedgerEntryList"> <worksheetLedgerEntry xsi:type="ns4:FastWorksheetLedgerEntry"> <ledger xsi:type="ns4:LedgerClaim"> <currency xsi:type="ns5:SicsCurrencyReference"> <isoAlpha xsi:type="ns5:IsoAlpha3">ADP</isoAlpha> </currency> <claimToSoc xsi:type="ns5:SicsPcSocToClaimReference"> <claimIdentifier xsi:type="ns2:String30">0000000011</claimIdentifier> <scopeOfCoverReference xsi:type="ns5:SicsScopeOfCoverReference"> <identifier xsi:type="ns2:String36">SICS162</identifier> <beginDateTime xsi:type="xsd:dateTime">2011-01-01T00:00:00</beginDateTime> <sequenceNumber xsi:type="xsd:int">0</sequenceNumber> <name xsi:type="xsd:string">Main Section</name> </scopeOfCoverReference> </claimToSoc> </ledger> <detailBalanceEntryList xsi:type="ns4:FastAccountingDetailBalanceEntryList"> <accountingDetailBalanceEntry xsi:type="ns4:FastAccountingClaimDetailBalanceEntry"> <entryCode xsi:type="ns5:SicsAccountingEntryCodeReference"> <code xsi:type="xsd:string">30</code> </entryCode> <processId xsi:type="xsd:string">processId</processId> <documentId xsi:type="xsd:string">documentId</documentId> <accountingClassification xsi:type="ns5:SicsAccountingClassificationReference"> <identifier>SICS162</identifier> <beginDateTime>2011-01-01T00:00:00</beginDateTime> <sequenceNumber>0</sequenceNumber> <name>Main Section</name> <classificationName>AVIATION_AVIATIONAH_AFG</classificationName> </accountingClassification> <scopeOfCover xsi:type="ns5:SicsScopeOfCoverReference"> <identifier xsi:type="ns2:String36">SICS162</identifier> <beginDateTime xsi:type="xsd:dateTime">2011-01-01T00:00:00</beginDateTime> <sequenceNumber xsi:type="xsd:int">1</sequenceNumber> <name xsi:type="xsd:string">Main Section</name> </scopeOfCover> <bookingYearPeriod xsi:type="ns5:SicsBookingYearPeriodReference"> <bookingYear xsi:type="xsd:int">2012</bookingYear> <bookingPeriod xsi:type="ns5:SicsReferenceDataReference"> <code xsi:type="ns5:ReferenceDataCode">M04</code> <subclassNumber xsi:type="ns5:SubclassNumber">10</subclassNumber> </bookingPeriod> </bookingYearPeriod> <bookingYearPeriod2 xsi:type="ns5:SicsBookingYearPeriodReference"> <bookingYear xsi:type="xsd:int">2012</bookingYear> <bookingPeriod xsi:type="ns5:SicsReferenceDataReference"> <code xsi:type="ns5:ReferenceDataCode">M05</code> <subclassNumber xsi:type="ns5:SubclassNumber">10</subclassNumber> </bookingPeriod> </bookingYearPeriod2> <bookingYearPeriod3 xsi:type="ns5:SicsBookingYearPeriodReference"> <bookingYear xsi:type="xsd:int">2012</bookingYear> <bookingPeriod xsi:type="ns5:SicsReferenceDataReference"> <code xsi:type="ns5:ReferenceDataCode">M06</code> <subclassNumber xsi:type="ns5:SubclassNumber">10</subclassNumber> </bookingPeriod> </bookingYearPeriod3> <accountingYear xsi:type="xsd:int">2011</accountingYear> <accountingRefPeriod xsi:type="ns5:SicsReferenceDataReference"> <code xsi:type="ns5:ReferenceDataCode">NONE</code> <subclassNumber xsi:type="ns5:SubclassNumber">177</subclassNumber> </accountingRefPeriod> <descriptionOfAccount xsi:type="ns5:SicsReferenceDataReference"> <code xsi:type="ns5:ReferenceDataCode">RA</code> <subclassNumber xsi:type="ns5:SubclassNumber">185</subclassNumber> </descriptionOfAccount> <originalUnderwritingYear xsi:type="xsd:int">2010</originalUnderwritingYear> <occurrenceYear xsi:type="xsd:int">2009</occurrenceYear> <accountingPeriod xsi:type="ns5:SicsWsDatespanReference"> <startDate xsi:type="xsd:date">2011-01-01</startDate> <endDate xsi:type="xsd:date">2011-12-31</endDate> </accountingPeriod> <dueDate xsi:type="xsd:date">2013-03-22</dueDate> <adjustmentAmount xsi:type="ns2:DecimalField">350</adjustmentAmount> <comment xsi:type="xsd:string">comment2</comment> <startDate xsi:type="xsd:date">2011-05-02</startDate> <endDate xsi:type="xsd:date">2011-05-03</endDate> <disabilityPercentage xsi:type="ns2:NonNegativeDecimal3V2">0. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsMigrationEntryPoint/fastCreateTechnicalWorksheet/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsMigrationEntryPoint/fastCreateTechnicalWorksheet/soap1/ Fast Create Technical Worksheet # 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/SystemTypes" xmlns:ns2="http://www.SicsNt.com/CommonTypes" xmlns:ns3="http://www.SicsNt.com/Migration" xmlns:ns4="http://www.SicsNt.com/Accounting" xmlns:ns5="http://www.SicsNt.com/ReferenceItems" 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> <swmep:fastCreateTechnicalWorksheet xmlns:swmep="urn:SicsWsMigrationEntryPoint"> <genericInput xsi:type="ns1:SicsGenericInput" /> <fastCreateTechnicalWorksheet xsi:type="ns3:SicsFastCreateTechnicalWorksheetInput"> <worksheet xsi:type="ns4:FastAccountingWorksheetCreate"> <title xsi:type="ns2:String30">title</title> <businessPartnerReference xsi:type="ns2:String40">businessPartnerReference</businessPartnerReference> <comment xsi:type="xsd:string">comment</comment> <policyId xsi:type="ns2:String20">policyId</policyId> <identifierPrefix xsi:type="ns2:String10">FTW</identifierPrefix> <identifierSerieNumber xsi:type="xsd:int">1</identifierSerieNumber> <identifierYearPart xsi:type="xsd:int">2011</identifierYearPart> <dateOfBooking xsi:type="xsd:date">2013-03-04</dateOfBooking> <isVatToBeCalculatedOnGross xsi:type="xsd:boolean">true</isVatToBeCalculatedOnGross> <worksheetAsSpecial xsi:type="xsd:boolean">false</worksheetAsSpecial> <origin xsi:type="ns5:SicsReferenceDataReference"> <code xsi:type="ns5:ReferenceDataCode">MAN</code> <subclassNumber xsi:type="ns5:SubclassNumber">220</subclassNumber> </origin> <registeredBy xsi:type="ns5:SicsUserReference"> <userId xsi:type="ns2:String32">HARALD</userId> </registeredBy> <registrationTimestamp xsi:type="xsd:dateTime">2013-03-05T16:38:10+00:00</registrationTimestamp> <worksheetWorkingInformation xsi:type="ns4:FastWorksheetWorkingInformation"> <receivedDate xsi:type="xsd:date">2013-03-01</receivedDate> <receivedInternalDate xsi:type="xsd:date">2013-03-02</receivedInternalDate> </worksheetWorkingInformation> <worksheetLedgerEntryList xsi:type="ns4:FastWorksheetLedgerEntryList"> <worksheetLedgerEntry xsi:type="ns4:FastWorksheetLedgerEntry"> <ledger xsi:type="ns4:LedgerBusiness"> <business xsi:type="ns5:SicsBusinessReference"> <identifier xsi:type="ns2:String36">SICS162</identifier> </business> <currency xsi:type="ns5:SicsCurrencyReference"> <isoAlpha xsi:type="ns5:IsoAlpha3">ADP</isoAlpha> </currency> </ledger> <detailBalanceEntryList xsi:type="ns4:FastAccountingDetailBalanceEntryList"> <accountingDetailBalanceEntry xsi:type="ns4:FastAccountingBusinessDetailBalanceEntry"> <entryCode xsi:type="ns5:SicsAccountingEntryCodeReference"> <code xsi:type="xsd:string">10</code> </entryCode> <processId xsi:type="xsd:string">processId</processId> <documentId xsi:type="xsd:string">documentId</documentId> <accountingClassification xsi:type="ns5:SicsAccountingClassificationReference"> <identifier>SICS162</identifier> <beginDateTime>2011-01-01T00:00:00</beginDateTime> <sequenceNumber>0</sequenceNumber> <name>Main Section</name> <classificationName>AVIATION_AVIATIONAH_AFG</classificationName> </accountingClassification> <scopeOfCover xsi:type="ns5:SicsScopeOfCoverReference"> <identifier xsi:type="ns2:String36">SICS162</identifier> <beginDateTime xsi:type="xsd:dateTime">2011-01-01T00:00:00</beginDateTime> <sequenceNumber xsi:type="xsd:int">1</sequenceNumber> <name xsi:type="xsd:string">Main Section</name> </scopeOfCover> <bookingYearPeriod xsi:type="ns5:SicsBookingYearPeriodReference"> <bookingYear xsi:type="xsd:int">2012</bookingYear> <bookingPeriod xsi:type="ns5:SicsReferenceDataReference"> <code xsi:type="ns5:ReferenceDataCode">M04</code> <subclassNumber xsi:type="ns5:SubclassNumber">10</subclassNumber> </bookingPeriod> </bookingYearPeriod> <bookingYearPeriod2 xsi:type="ns5:SicsBookingYearPeriodReference"> <bookingYear xsi:type="xsd:int">2012</bookingYear> <bookingPeriod xsi:type="ns5:SicsReferenceDataReference"> <code xsi:type="ns5:ReferenceDataCode">M05</code> <subclassNumber xsi:type="ns5:SubclassNumber">10</subclassNumber> </bookingPeriod> </bookingYearPeriod2> <bookingYearPeriod3 xsi:type="ns5:SicsBookingYearPeriodReference"> <bookingYear xsi:type="xsd:int">2012</bookingYear> <bookingPeriod xsi:type="ns5:SicsReferenceDataReference"> <code xsi:type="ns5:ReferenceDataCode">M06</code> <subclassNumber xsi:type="ns5:SubclassNumber">10</subclassNumber> </bookingPeriod> </bookingYearPeriod3> <accountingYear xsi:type="xsd:int">2011</accountingYear> <accountingRefPeriod xsi:type="ns5:SicsReferenceDataReference"> <code xsi:type="ns5:ReferenceDataCode">NONE</code> <subclassNumber xsi:type="ns5:SubclassNumber">177</subclassNumber> </accountingRefPeriod> <descriptionOfAccount xsi:type="ns5:SicsReferenceDataReference"> <code xsi:type="ns5:ReferenceDataCode">RA</code> <subclassNumber xsi:type="ns5:SubclassNumber">185</subclassNumber> </descriptionOfAccount> <originalUnderwritingYear xsi:type="xsd:int">2010</originalUnderwritingYear> <occurrenceYear xsi:type="xsd:int">2009</occurrenceYear> <accountingPeriod xsi:type="ns5:SicsWsDatespanReference"> <startDate xsi:type="xsd:date">2011-01-01</startDate> <endDate xsi:type="xsd:date">2011-12-31</endDate> </accountingPeriod> <dueDate xsi:type="xsd:date">2013-03-22</dueDate> <adjustmentAmount xsi:type="ns2:DecimalField">350</adjustmentAmount> <comment xsi:type="xsd:string">comment2</comment> <startDate xsi:type="xsd:date">2011-05-02</startDate> <endDate xsi:type="xsd:date">2011-05-03</endDate> <disabilityPercentage xsi:type="ns2:NonNegativeDecimal3V2">0. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsReferenceItemsEntryPoint/deleteCurrency/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsReferenceItemsEntryPoint/deleteCurrency/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsReferenceItemsEntryPoint/deleteCurrency/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsReferenceItemsEntryPoint/deleteCurrency/soap1/ Delete Currency # Deleting currency isoAlpha “ZZZ”. 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> <swriep:deleteCurrency xmlns:swriep="urn:SicsWsReferenceItemsEntryPoint"> <genericInput /> <deleteCurrencyInput> <isoAlpha>ZZZ</isoAlpha> </deleteCurrencyInput> </swriep:deleteCurrency> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Response message # <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <swriep:deleteCurrencyResponse xmlns:swriep="urn:SicsWsReferenceItemsEntryPoint" xsi:type="swriep:DeleteCurrencyOutput" /> </soapenv:Body> </soapenv:Envelope> /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsSystemAdministrationEntryPoint/updateSystemParameters/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsSystemAdministrationEntryPoint/updateSystemParameters/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsSystemAdministrationEntryPoint/updateSystemParameters/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsSystemAdministrationEntryPoint/updateSystemParameters/soap1/ 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. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsTaskManagementEntryPoint/createProcess/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsTaskManagementEntryPoint/createProcess/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsTaskManagementEntryPoint/createProcess/soap1/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsTaskManagementEntryPoint/createProcess/soap1/ 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. /sicsdocs/technical/misc/sics_docs_installation/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/sics_docs_installation/ /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/misc/desktop_launcher/authorization/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/desktop_launcher/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. /sicsdocs/technical/misc/memory_settings/background/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/memory_settings/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. /sicsdocs/technical/server/api_server/technical_paper/concepts/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/technical_paper/concepts/ 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). /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/server/operational_reporting/deployment/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/operational_reporting/deployment/ 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. /sicsdocs/technical/server/api_server/installation_guide/install_java_container/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/install_java_container/ SICS API Server is a web application running Java 21 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 21 or higher. This does not imply that we promote Tomcat 10. /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/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/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/server/batch_server/overview/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/batch_server/overview/ SICS Batch Server (SBS) is a web application with a simple browser based administration web page. When the SBS starts it allocates and eventually starts a set of schedulers. The name of the schedulers to run, SICS user name, password and various other parameters can be configured in the SBS web application. The simple browser based web page can be used to administer the SBS and to initiate on call only jobs. /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/server/api_server/server_security/security_parameters/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/server_security/security_parameters/ Three parameters determine ‘Secure’ and ‘Non-Secure’ Modes of SICS API Server Start-up. The parameters act as overall switches for the authentication and authorization security functions. The parameters are found in the web.xml file. If SICS API Server is installed as described in SICS API Server - Installation Guide, this file can be found (for Tomcat 10.x) in: %CATALINA_HOME%/webapps/SicsServer/WEB-INF/web.xml. The parameters are: Parameter name Valid values Default Purpose web.xml ApplyServerSecurity true/false false Indicates whether SICS API Server is running in secure mode or not. /sicsdocs/technical/server/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/ /sicsdocs/technical/server/api_server/server_security/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/server_security/ /sicsdocs/technical/server/adh_server/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/adh_server/ Contents # This document contains instructions on how to install and successfully configure an instance of SICS Automated Document Handling Server. Requirements # SICS ADH Server requires an Application Server running in a Java 21 or later runtime environment. Installation # SICS ADH Server is a Web Application and can potentially be deployed in any Application Server. For deploying an instance of SICS ADH Server it is enough to deploy SicsADHServer. /sicsdocs/technical/server/api_server/soap_library/lf/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/ SOAP webservice documentation # This library contains sample SOAP messages for SICS API Server - Life. /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBatchProcessEntryPoint/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBatchProcessEntryPoint/ /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBatchProcessEntryPoint/createJob/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBatchProcessEntryPoint/createJob/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/createBusinessWithSections/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/createBusinessWithSections/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessPartnerEntryPoint/createOrUpdateCollateral/soap2/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessPartnerEntryPoint/createOrUpdateCollateral/soap2/ Create Or Update Collateral # Description # Request message # Response message # /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBatchProcessEntryPoint/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBatchProcessEntryPoint/ /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBatchProcessEntryPoint/createJob/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBatchProcessEntryPoint/createJob/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/createBusinessWithSections/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/createBusinessWithSections/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessPartnerEntryPoint/createOrUpdateCollateral/soap2/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessPartnerEntryPoint/createOrUpdateCollateral/soap2/ Create Or Update Collateral # Description # Updating Collateral using createOrUpdateCollateral API. Request message # <?xml version="1.0" encoding="ISO-8859-1"?> <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> <swbpep:createOrUpdateCollateral xmlns:swbpep="urn:SicsWsBusinessPartnerEntryPoint"> <genericInput /> <createOrUpdateCollateralInput> <businessPartnerReference> <identifier>S165S1A</identifier> </businessPartnerReference> <collateralUpdate> <letterOfCreditUpdate> <issuingBank> <identifier>B130</identifier> <partyIdentifierType> <code>BID</code> <subclassNumber>35</subclassNumber> </partyIdentifierType> </issuingBank> <identifier>A2</identifier> <effectiveDate>2023-03-15</effectiveDate> <expirationDate>2023-03-16</expirationDate> <originalAmount>2400</originalAmount> <originalCurrency> <isoAlpha>NOK</isoAlpha> </originalCurrency> <collateralDetailsList> <collateralDetail> <loCAmountType> <code>INCREASE</code> <subclassNumber>1238</subclassNumber> </loCAmountType> <bankDate>2023-03-13</bankDate> <amount>33</amount> </collateralDetail> </collateralDetailsList> <collateralLatestDetailUpdate> <loCAmountType> <code>DECREASE</code> <subclassNumber>1238</subclassNumber> </loCAmountType> <bankDate>2023-03-15</bankDate> <amount>23</amount> </collateralLatestDetailUpdate> <collateralPercentage>12. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsPcClaimEntryPoint/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsPcClaimEntryPoint/ /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsDomainRetrievalEntryPoint/retrieveObject/soap2/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsDomainRetrievalEntryPoint/retrieveObject/soap2/ Retrieve Object # Description # This message retrieves all fields on a Policy Light with identifier = NB_26377_2104A: Request message # <?xml version="1.0" encoding="ISO-8859-1"?> <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/ReferenceItems" 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> <swdrep:retrieveObject xmlns:swdrep="urn:SicsWsDomainRetrievalEntryPoint"> <genericInput /> <input> <referenceObject xsi:type="ns1:SicsPolicyLightBusinessReference"> <identifier>NB_26377_2104A</identifier> </referenceObject> <specification> <retrieveAll>true</retrieveAll> </specification> </input> </swdrep:retrieveObject> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Response message # Response message is not shown. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsMigrationEntryPoint/fastCreateTechnicalWorksheet/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsMigrationEntryPoint/fastCreateTechnicalWorksheet/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsDocumentProductionEntryPoint/produceDocument/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsDocumentProductionEntryPoint/produceDocument/ Please select example from the menu on the left side. /sicsdocs/technical/desktop/adh/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/adh/ /sicsdocs/technical/misc/hw_and_sw_requirements/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/hw_and_sw_requirements/ /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/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/server/api_server/server_security/authentication/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/server_security/authentication/ If SICS API Server is started in secure mode, all normal Web Services calls must include an authentication token. The caller must obtain this token by sending an initial “login” message to SICS API Server. The Login service # Sample SOAP Request and Response # The SOAP request (input message) for the login service must follow one of these formats (see discussion on OS AUTHENTICATION and <sicsUserId> further down): <SOAP-ENV:Envelope . /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/server/api_server/installation_guide/configure_api_server_for_tomcat_deployment/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/configure_api_server_for_tomcat_deployment/ SICS API Server is delivered as a web application. Web applications are packaged as files with extension .war. The war file is in fact a zipped archive file. The contents may be viewed with a zip application such as WinZip. Any configuration setting done prior to deploying SICS API Server, must therefore be done in the war file. For instance, WinZip allows the user to edit text files from the archive with Notepad or another external editor. /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/misc/desktop_launcher/environment_api_component/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/desktop_launcher/environment_api_component/ Overview # The Enviroment API component is as Spring Boot-based REST API service. It provides endpoints to create, update, delete and list the Assure Re environments. The Enviroment API component stores the environment data. The environment data contains name, description, runtime zip file URL, a unique HASH-value, and other details. Installation # As the Environment API is Spring Boot-based component, it can be run as a normal Java application using the scripts provided in delivery zip-file. /sicsdocs/technical/server/api_server/technical_paper/features/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/technical_paper/features/ Stateless # SICS API Server is designed to operate in a stateless manner. In other words, each SOAP call must contain the data that is necessary for SICS API Server to fully process the SICS business function. Parts of the data may consist of references to data that already exist in the SICS operational database. Commit / Rollback / Unit of Work # Each SOAP call to the SICS API Server will either succeed 100% or fail completely. /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/misc/memory_settings/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/memory_settings/ /sicsdocs/technical/misc/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/ /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/server/batch_server/sbs_admin_web_page/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/batch_server/sbs_admin_web_page/ The SBS provides a simple web GUI to administer the SBS instance. The SBS admin console is available at URL: http://<hostname>:<port>/<rootcontext>/admin URL part Description <hostname> The domain name or IP address of the computer where SBS is running. <port> The SBS port, as configured in the JEE container (Tomcat, WebSphere, etc) where SBS is deployed. <rootcontext> The context root where the SicsBatchServer is published, for example, “sbs”. Note: If admin pages are set up to be protected the user must log in before the management console is opened. /sicsdocs/technical/desktop/adh_setup/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/adh_setup/ /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBatchProcessEntryPoint/createOrder/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBatchProcessEntryPoint/createOrder/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/ /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/retrieveAllAssumedBusinessesLinkedToPlacement/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/retrieveAllAssumedBusinessesLinkedToPlacement/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBatchProcessEntryPoint/createOrder/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBatchProcessEntryPoint/createOrder/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/ /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/retrieveAllAssumedBusinessesLinkedToPlacement/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/retrieveAllAssumedBusinessesLinkedToPlacement/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessPartnerEntryPoint/createOrUpdateCollateral/soap3/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessPartnerEntryPoint/createOrUpdateCollateral/soap3/ Create Or Update Collateral Details # Description # Creating Collateral Details using createOrUpdateCollateralDetails API. Request message # <?xml version="1.0" encoding="ISO-8859-1"?> <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> <swbpep:createOrUpdateCollateralDetails xmlns:swbpep="urn:SicsWsBusinessPartnerEntryPoint"> <genericInput /> <createOrUpdateCollateralDetailsInput> <businessPartnerReference> <identifier>S165S1A</identifier> </businessPartnerReference> <collateralDetailsList> <collateralDetail> <loCCategory> <code>LETT_OF_CRED</code> <subclassNumber>1236</subclassNumber> </loCCategory> <loCAmountType> <code>INCREASE</code> <subclassNumber>1238</subclassNumber> </loCAmountType> <bankDate>2023-03-15</bankDate> <amount>55</amount> </collateralDetail> <collateralDetail> <loCCategory> <code>TRUSTS</code> <subclassNumber>1236</subclassNumber> </loCCategory> <loCAmountType> <code>DECREASE</code> <subclassNumber>1238</subclassNumber> </loCAmountType> <bankDate>2023-03-16</bankDate> <amount>34.5</amount> </collateralDetail> </collateralDetailsList> </createOrUpdateCollateralDetailsInput> </swbpep:createOrUpdateCollateralDetails> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Response message # <? /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsPcClaimEntryPoint/moveLightClaim/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsPcClaimEntryPoint/moveLightClaim/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsDomainRetrievalEntryPoint/retrieveObject/soap3/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsDomainRetrievalEntryPoint/retrieveObject/soap3/ Retrieve Object # Description # This message retrieves all fields on a Light Claim with claimIdentifier = CL_SE25766_A: Request message # <?xml version="1.0" encoding="ISO-8859-1"?> <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/ReferenceItems" 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> <swdrep:retrieveObject xmlns:swdrep="urn:SicsWsDomainRetrievalEntryPoint"> <genericInput /> <input> <referenceObject xsi:type="ns1:SicsLightClaimReference"> <claimIdentifier>CL_SE25766_A</claimIdentifier> </referenceObject> <specification> <retrieveAll>true</retrieveAll> </specification> </input> </swdrep:retrieveObject> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Response message # Response message is not shown. /sicsdocs/technical/server/batch_server/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/batch_server/ /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/server/api_server/technical_paper/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/technical_paper/ /sicsdocs/technical/server/api_server/server_security/authorization/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/server_security/authorization/ Authorization is the process of ensuring that the caller invokes services that the caller is allowed to execute, according to the caller’s SICS user profile. When receiving a service call request, SICS API Server verifies whether the SICS user identified by the “User ID” (present in the Authentication Token) has Access Rights to execute the service, according to the (existing) security set-up defined via the SICS System Administration utility. See also SICS API Server - Installation Guide, on how to set up your own authorization policy. /sicsdocs/technical/server/api_server/installation_guide/configure_tomcat_for_api_server_deployment/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/configure_tomcat_for_api_server_deployment/ Memory Setting # SICS API Server is a memory intensive application and the standard Java VM settings are not sufficient. To avoid out of memory error messages like: java.lang.OutOfMemoryError. Do the following: Ensure Tomcat is not running Start (double-click) the %CATALINA_HOME%\bin\tomcat9w.exe program You will then see a window like this: Figure 1 - Apache Tomcat Windows Service Properties Go to the “Java” tab and at the bottom at the “Java Options:” field and add the following parameters: Set the Initial memory pool 512 MB and Maximum memory pool 1024 MB. /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/server/api_server/technical_paper/deployment/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/technical_paper/deployment/ This section briefly explains the hardware and software required for installing and running the SICS API Server component. It is assumed that there already exists a SICS database that the SICS API Server will work against. Hardware Requirements # The SICS API Server component runs inside a Java servlet container. Such containers are available for many operating systems. One instance of SICS API Server requires at least 1 GB of memory running on a 64-bit operating system. /sicsdocs/technical/misc/desktop_launcher/environment_admin_ui/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/desktop_launcher/environment_admin_ui/ Overview # The Environment Admin UX is a web UI (built on React JS). This webapp is used by system administrators, and can be used to used to manage the Assure Re environments. Installation # The Environment Admin UX can be installed as a static web page, in a webserver of choice, for example an Nginx server. Note: A Java Servlet container (Tomcat, etc.) is not required to run the Environment Admin UX. /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/retrieveReinstatementCondition/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/retrieveReinstatementCondition/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessPartnerEntryPoint/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessPartnerEntryPoint/ /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/retrieveReinstatementCondition/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/retrieveReinstatementCondition/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessPartnerEntryPoint/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessPartnerEntryPoint/ /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessPartnerEntryPoint/createOrUpdateCollateral/soap4/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessPartnerEntryPoint/createOrUpdateCollateral/soap4/ Create Or Update Collateral Details # Description # Updating Collateral Details using createOrUpdateCollateralDetails API. 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> <swbpep:createOrUpdateCollateralDetails xmlns:swbpep="urn:SicsWsBusinessPartnerEntryPoint"> <genericInput /> <createOrUpdateCollateralDetailsInput> <businessPartnerReference> <identifier>S165S1A</identifier> </businessPartnerReference> <collateralLatestDetailUpdate> <loCCategory> <code>LETT_OF_CRED</code> <subclassNumber>1236</subclassNumber> </loCCategory> <loCAmountType> <code>INCREASE</code> <subclassNumber>1238</subclassNumber> </loCAmountType> <bankDate>2023-03-15</bankDate> <amount>54</amount> </collateralLatestDetailUpdate> </createOrUpdateCollateralDetailsInput> </swbpep:createOrUpdateCollateralDetails> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Response message # <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <swbpep:createOrUpdateCollateralDetailsResponse xmlns:swbpep="urn:SicsWsBusinessPartnerEntryPoint" xsi:type="swbpep:CreateOrUpdateCollateralDetailsOutput" /> </soapenv:Body> </soapenv:Envelope> /sicsdocs/technical/desktop/config_manager/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/config_manager/ /sicsdocs/technical/server/emessaging_server/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/emessaging_server/ /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/server/batch_server/tasks/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/batch_server/tasks/ Start Scheduler # The user can start, stop or pause a scheduler by selecting one of the buttons in the Actions column. Run On-Call jobs # A job can be run by giving a valid Job Identifier and an optional parameter file. If a scheduler is specified in the job’s configuration that scheduler will be used. If the job does not specify any scheduler (AUTOMATIC option) the first available scheduler will be used. /sicsdocs/technical/misc/technical_changes/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/ /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/server/api_server/installation_guide/deploy_api_server_to_java_servlet_container/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/deploy_api_server_to_java_servlet_container/ The way to deploy war files differ from the various Java Servlet Containers. The following describe how to do it on Apache Tomcat 10.1.40. https://tomcat.apache.org/tomcat-10.1-doc/index.html Ensure Tomcat is running Open the Tomcat Web Application Manager in a browser. If you have installed it locally on port 8080 the address is: http://localhost:8080/manager/html (or click on the link Tomcat Manager in the Tomcat start page (http://localhost:8080): (You must log in with the username and password set when installed Tomcat) /sicsdocs/technical/misc/desktop_launcher/desktop_launching_component/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/desktop_launcher/desktop_launching_component/ Overview # The Desktop Launching Component is a Desktop UX component that is responsible of managing the environments on local user system. Features # The desktop launcher component will get list of environments from the API server. It also ensure the sanity of local enviroments folder to automatically detect any obsolate environment that is not present on API server and clean that up. The desktop launcher component have a way to ensure that local runtime of an environment should be always up to date with the server environment. /sicsdocs/technical/desktop/emessaging_setup/integration/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/emessaging_setup/integration/ /sicsdocs/technical/server/api_server/server_security/enable_api_server_module/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/server_security/enable_api_server_module/ To enable the API Server module, check the API Server module in use checkbox in System Parameter Maintenance -> Module Key. Figure 1 - Module Keys System Parameter /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/server/batch_server/pre_installation_comments/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/batch_server/pre_installation_comments/ SICS Batch Server can run on 64-bit versions of Windows and Linux. The instructions are based on installation on machines running Microsoft Windows 64 bit. There is also a section on installing SICS Batch Server on Linux. Main steps # Install SICS software products Set up database Test database using GUI-based SICS Configure SICS Install a Java Servlet Container Deploy SICS Batch Server to the Java Servlet Container Configure the SICS batch Server environment Verify correct startup of SICS Batch Server Note: /sicsdocs/technical/server/api_server/soap_library/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/ Examples # This library contains sample SOAP messages for SICS API Server - P&C and Life. /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/updateContractCertaintyCheckList/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsBusinessEntryPoint/updateContractCertaintyCheckList/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsCommonAccountingEntryPoint/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/lf/SicsWsCommonAccountingEntryPoint/ /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/updateContractCertaintyCheckList/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsBusinessEntryPoint/updateContractCertaintyCheckList/ Please select example from the menu on the left side. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsCommonAccountingEntryPoint/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsCommonAccountingEntryPoint/ /sicsdocs/technical/misc/database_maintenance_launcher/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/database_maintenance_launcher/ Introduction # SICS SysAdmin Utility is shipped with a command-line utility for maintenance work on SICS databases. Being a command-line utility means it is a headless application, well suited for automation. The command-line utility is implemented as a Java program which is launched from a class named com.csc.sics.launcher.DatabaseMaintenanceLauncherMain. The SICS Database Maintenance Launcher has the following capabilites: Create a new SICS database Update an existing SICS database to a higher version Create SICS reporting tables and views Create SICS reporting stored procedures and functions Usage # Bootstrapping # In order to execute the SICS Database Maintenance Launcher, a few JAR’s from the lib folder of the SICS SysAdmin Utility must be added to the Java class-path. /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/server/search/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/search/ /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/misc/desktop_launcher/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/desktop_launcher/ /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/server/api_server/installation_guide/configure_api_server_environment/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/configure_api_server_environment/ Required knowledge # Most SICS API Server configuration is specified using XML files. You should be familiar with syntax rules for well formed XML, and be able to comment and uncomment XML fragments. Suggested configuration order # Configure logging Configure security Configure system pool size Configure queue sizes Configure caching of data Configure xml files Configure HTTP return codes Configure logging # Turn on/off Separate Logging of SOAP Messages # The default installation of SICS API Server logs SOAP messages to a separate log. /sicsdocs/technical/server/batch_server/database_compatibility/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/batch_server/database_compatibility/ SICS Batch Server is, like SICS Sys Admin Workstation, dependent on SICS database version. The service pack documentation which is included in every delivery describes database patches, etc. /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/soap_library/pc/SicsWsDocumentProductionEntryPoint/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsDocumentProductionEntryPoint/ /sicsdocs/technical/misc/java_launcher_application/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/java_launcher_application/ /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/server/operational_reporting/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/operational_reporting/ /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/misc/opensource_reports/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/opensource_reports/ Third Party Software Notices And Information # The Product is delivered with Open Source Software (OSS) components potentially developed or owned by third parties. OSS components may be used according to the terms and conditions of the specific licence under which the relevant OSS components are distributed, but are provided “AS IS” by such third parties and DXC. Artifact Version Licenses angus-activation 2.0.3 EDL 1.0 angus-mail 2.0.4 EPL 2.0GPL2 w/ CPEEDL 1. /sicsdocs/technical/server/api_server/server_security/web_services_use_cases/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/server_security/web_services_use_cases/ Use Case security # Each Web Service is defined as a “Use Case” in the SICS Security module. This means that it is possible to “switch off” each of the Web Services that your company do not use, by simply removing the unused Use Cases from the security profiles. Naming convention # All Web Services Use Cases are named with the “API” (Application Programming Interface) prefix, to easily separate them from the normal SICS Workstation Use Cases. /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/server/batch_server/important_notice_on_system_specific_files/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/batch_server/important_notice_on_system_specific_files/ This document covers both SICS Batch Server for Life and for P&C, and for 64-bit version of Windows and Linux. Some files come in different versions for Life and P&C. This document will refer to these files with the “PRODUCT” alias. Replace the alias with ‘pc’ for P&C and ’lf’ for Life. Usually, you would need to download only one specific .war file, matching the desired PRODUCT. The downloaded file could be kept as SicsBatchServer. /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/server/api_server/soap_library/pc/SicsWsDomainRetrievalEntryPoint/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsDomainRetrievalEntryPoint/ /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/server/api_server/installation_guide/verify/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/verify/ Verify SICS API Server startup using the SICS API Server Management console # SICS API Server comes with a rudimentary management console which can be found at: http://<Tomcat-installation:port>/SicsServer/SicsServerManagementConsole and looks like this: When SICS API Server is ready to process SOAP messages the status will be “Running and ready since date/time and the flag will be green: Figure 9 - SICS API Server Management Console Green Status Verify SICS API Server startup by inspecting the log files # SICS API Server writes important startup messages to the SicsServer. /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/server/batch_server/install_servlet_container/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/batch_server/install_servlet_container/ SICS Batch Server is a web application running Java and 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 Tomcat 10.x which is a free and commonly used Java Servlet Container from Apache using Java 21 or higher. This does not imply that we promote Tomcat 10. /sicsdocs/technical/server/api_server/installation_guide/monitoring_sics_server/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/monitoring_sics_server/ SICS API Server can process multiple messages concurrently. The SICS API Server management console is extended to show information of the SICS System pool: Figure 22 - SICS API Server Management Console Figure 23 - SICS API Server Management Console Status /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/server/api_server/soap_library/pc/SicsWsMigrationEntryPoint/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsMigrationEntryPoint/ /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/server/batch_server/install_sbs_on_linux/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/batch_server/install_sbs_on_linux/ Please note that the instructions in this document are based on installing Java and Tomcat in Windows. For installation on Linux distributions please refer to documentation from Sun and Apache, alternatively the package distribution system of the platform. Nevertheless the instructions given in this document also apply for Linux with the following exceptions/notes. Make sure to substitute backslashes in paths \ with forward slashes /. Furthermore it is vital that Tomcat is started up with the Java VM arguments given in section 5. /sicsdocs/technical/server/api_server/installation_guide/multiple_instances/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/multiple_instances/ SICS API Server runs as a web application inside a Java Servlet Container (Tomcat, Websphere etc). How to scale SICS API Server capacity depends on the Java Servlet Container and other infrastructure constraints/possibilities. For different alternatives and guidelines on how to set this up, please refer to the Java Servlet Container provider documentation. For testing purposes, DXC has defined a setup using Tomcat and Apache. The description of this setup is provided below for information purposes, as an example of how Load Balancing can be achieved. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsPcAccountingEntryPoint/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsPcAccountingEntryPoint/ /sicsdocs/technical/server/api_server/installation_guide/additional_information/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/additional_information/ Application managed database connection # Complete the following steps to set up application managed connections to the database. Define and test a database connection in the file sics-database-sources.xml used by SICS workstation. On success, copy the connection entry to file %CATALINA_HOME%/webapps/SicsServer/WEB-INF/classes/sics-database-sources.xml Copy the required JDBC jar(s) into %CATALINA_HOME%/webapps/SicsServer/WEB-INF/lib (similar to the same step for 3.1 “Configure database connection”) Uncomment and specify the following servlet init-parameters in %CATALINA_HOME%/webapps/SicsServer/WEB-INF/web.xml: Parameter Description Required DATABASE The name attribute of the connection specified in %CATALINA_HOME%/webapps/SicsServer/WEB-INF/classes/sics-database-sources. /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/server/batch_server/install_jdk/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/batch_server/install_jdk/ SICS (Batch Server) requires a 64-bit Java Development Kit (JDK) with Java 21+ specification. As of 2026-01-20, the latest Java 21 version is 21.0.10.7.1. At the time of writing, SICS is shipped with the Amazon Corretto 21.0.10.7.1 (64-bit version). Note that SICS (Batch Server) will not run with Java versions prior to 21. Go to Amazon Corretto Production-ready distribution of OpenJDK and follow the instructions for downloading and installing java. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsReferenceItemsEntryPoint/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsReferenceItemsEntryPoint/ /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/server/batch_server/configure_sbs_for_deployment_in_tomcat/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/batch_server/configure_sbs_for_deployment_in_tomcat/ SICS Batch Server is delivered as a web application. Web applications are packaged as files with extension .war. The war file is in fact a zipped archive file. The contents may be viewed with a zip application such as WinZip. Any configuration setting done prior to deploying SICS Batch Server, must therefore be done in the war file. For instance, WinZip allows the user to edit text files from the archive with notepad or another external editor. /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/server/api_server/soap_library/pc/SicsWsSystemAdministrationEntryPoint/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsSystemAdministrationEntryPoint/ /sicsdocs/technical/server/api_server/installation_guide/appendix_a/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/appendix_a/ Required knowledge # This is not an introduction to IBM WebSphere Liberty administration, the user must as a minimum know how to: Open and log into the Admin Center. Create a JDBC data source and install JDBC drivers Create JDBC login credentials Install an Enterprise Application Refer to official IBM WebSphere Liberty documentation and support for assistance. WAS Liberty Memory Parameters # Default JVM memory parameters must be changed. This can be done by creating a file named jvm. /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/server/batch_server/configure_database_connection/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/batch_server/configure_database_connection/ Before SICS Batch Server can be deployed to Tomcat, the database connection must be configured. There are two alternative modes for configuring connection from SICS Batch Server to the database: Application managed database connection Container managed database connection Specific details used by the container managed will be covered first. Container managed database connection # The Container managed connection configuration is a widespread best practice for database access in Java web applications. /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsTaskManagementEntryPoint/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/soap_library/pc/SicsWsTaskManagementEntryPoint/ /sicsdocs/technical/server/api_server/installation_guide/appendix_b/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/appendix_b/ Two-level login is supported when using ‘application managed’ database connection. This is how it works: The user name and password for the first-level ’technical user’ is provided in a configuration text file which is read by SICS SICS will connect to the database using the technical user name and password SICS reads the corresponding SICS User Object from the CNU_USER table SICS detects that the SICS User Object contains a second-level name and password SICS disconnects from the database SICS connects (once more) to the database using the second-level name and password from the SICS User Object This connection is used for all later access and updates to the database In other words, when using application managed login, the db connection is under control by the application, i. /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/server/batch_server/specify_database_environment/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/batch_server/specify_database_environment/ If the SICS Batch Server data is stored in a schema which is not default for the user logged in to the database, the SQL statements issued by the application requires prefixes to table and view names. If such a prefix is required: Open WEB-INF/web.xml inside sbs.war. Change the param-value for ENVIRONMENT to SQL schema. For example if the schema prefix is SICSPROD it should be: <init-param> <param-name>ENVIRONMENT</param-name> <param-value>SICSPROD</param-value> </init-param> /sicsdocs/technical/server/api_server/installation_guide/appendix_c/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/appendix_c/ It is possible to run Tomcat without installing it as a Windows service. This section briefly explains a few differences from the ‘Tomcat installed as a Windows service’ procedure described above. Download and Unzip Tomcat # Download the Tomcat zip file and unzip to some folder. Hereafter, the alias TOMCAT refers to the folder where Tomcat is unzipped. Java setup # Install the 64-bit Java Development Kit 21 (JDK 21) or later as described above. /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/technical/server/batch_server/specify_walkback_directory/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/batch_server/specify_walkback_directory/ When an unexpected error occurs in SICS a so-called walkback is written. This file is important for DXC when troubleshooting errors. The walkback is a zip file containing various information about the SICS installation and the error. The SICS installation includes a walkback viewer which can be used to easily view the content of the walkback. The default folder for walkback files is: <java working directory>/walkback The folder can be changed by: /sicsdocs/technical/server/batch_server/configure_tomcat_for_sbs_deployment/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/batch_server/configure_tomcat_for_sbs_deployment/ SICS Batch Server is a memory intensive application and the standard Java VM settings are not sufficient. To avoid out of memory error messages like: java.lang.OutOfMemoryError. Do the following: Ensure Tomcat is not running Start (double-click) the %CATALINA_HOME%\bin\tomcat10w.exe program You will then see a window like this: Go to the “Java” tab and at the bottom at the “Java Options” field and add the following parameters: Set the Initial memory pool 512 MB and Maximum memory pool 1024 MB. /sicsdocs/technical/server/batch_server/deploy_sbs_to_the_java_servlet_container/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/batch_server/deploy_sbs_to_the_java_servlet_container/ Deployment on Apache Tomcat 10.x # The way to deploy war files differ from the various Java Servlet Containers. The following describe how to do it on Apache Tomcat 10.1.40. Ensure Tomcat is running. Open the Tomcat Web Application Manager in a browser. If you have installed it locally on port 8080 the address is http://localhost:8080/manager/html (or click on the link Tomcat Manager in the Tomcat start page (http://localhost:8080) /sicsdocs/technical/server/batch_server/configure_the_sbs_server_environment/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/batch_server/configure_the_sbs_server_environment/ Required knowledge # Most SICS Batch Server configuration is specified using XML files. You should be familiar with syntax rules for well formed XML, and be able to comment and uncomment XML fragments. Suggested configuration order # Step Description 1 Configure logging 2 Configure security 3 Configure schedulers 4 Configure user authorization interface Configure logging # Configure Log file Destination # Logging in SICS is done using the Apache Log4j 2 library and is configured using a file called log4j2. /sicsdocs/technical/server/batch_server/appendix_a/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/batch_server/appendix_a/ Two-level login is supported when using “application managed” database connection. This is how it works: The user name and password for the first-level ’technical user’ is provided in a configuration text file which is read by SICS. SICS will connect to the database using the technical user name and password. SICS reads the corresponding SICS User Object from the CNU_USER table. SICS detects that the SICS User Object contains a second-level name and password. /sicsdocs/technical/misc/technical_changes/4.7.2/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/technical_changes/4.7.2/ SE-6148 # The SQL Server jTDS JDBC Driver has been replaced by Microsoft JDBC Driver. Please read the instructions in /conf/sics-database-sources.xml. Driver class name has changed # SQL Server database <source> definitions need to change the driver class name in the <driver> element to com.microsoft.sqlserver.jdbc.SQLServerDriver. Example: <source name="SQLServer"> <driver>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver> <accessor>com.csc.troll.accessor.JDBCDatabaseAccessor</accessor> <interface>com.csc.troll.accessor.SQLServer2000Interface</interface> <dataSource>jdbc:sqlserver://hostname;sendStringParametersAsUnicode=false;selectMethod=cursor</dataSource> <useParameterizedSql>true</useParameterizedSql> <statementCacheSize>100</statementCacheSize> </source> SQL Server Windows Authentication (aka ‘Database remote OS authentication’ in SICS) with Microsoft JDBC Driver # In order to use SQL Server Windows Authentication, the integratedSecurity property (URL parameter) must be set to true (;integratedSecurity=true) on the <datasource> URL.