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. ...
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. ...
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 17 or higher. This does not imply that we promote Tomcat 10. ...
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
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. ...
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. ...
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. ...
SICS (Batch Server) requires a 64-bit Java Development Kit (JDK) with Java 17+ specification. As of 2025-07-15, the latest Java 21 version is 21.0.8.9.1. At the time of writing, SICS is shipped with the Amazon Corretto 21.0.8.9.1 (64-bit version). Note that SICS (Batch Server) will not run with Java versions prior to 17. Go to Amazon Corretto Production-ready distribution of OpenJDK and follow the instructions for downloading and installing java.
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. ...
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. ...