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