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