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.
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. ...
No technical changes.
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. ...
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. ...
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. ...
This this section you will find database preparation steps for supported DBMS’es. Oracle Microsoft SQL Server PostgreSQL
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. ...
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. ...