/tags/v4.9.3/ Recent content in v4.9.3 on Hugo -- gohugo.io /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/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/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/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/desktop/adh/ /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/server/batch_server/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/batch_server/ /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/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/search/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/search/ /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/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/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/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/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/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/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/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/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/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/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/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.