/categories/Server/ Recent content in Server on Hugo -- gohugo.io /sicsdocs/technical/server/emessaging_server/documentation/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/emessaging_server/documentation/ 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. /sicsdocs/technical/server/api_server/installation_guide/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/ /sicsdocs/technical/server/api_server/installation_guide/introduction/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/introduction/ This document describes how to install and configure SICS API Server. SICS API 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 API 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 API Server to the Java Servlet Container Configure the SICS API Server environment Verify correct startup of SICS API Server Steps 1 to 4 are not described in this document and may vary if you are using P&C or Life. /sicsdocs/technical/server/api_server/server_security/introduction/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/server_security/introduction/ SICS API Server is a software component in the SICS product suite. SICS API Server implements the Web Services that allows external applications to call/invoke SICS functions. This document describes the Security features that SICS API Server supports. What this document covers # Security feature Description Authentication How to get SICS API Server to authenticate the sender of Web Services calls. Authorization How to get SICS API Server to check whether a user has the authority (Access Rights) to invoke a web service, and to perform the business logic that is re-used from the SICS on-line system. /sicsdocs/technical/server/api_server/technical_paper/introduction/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/technical_paper/introduction/ SICS API Server is a non-mandatory component in the SICS software package. SICS API Server is a “headless” component that implements Web Services to common SICS functions, allowing other applications, components or front-ends to call SICS business processes directly or via a Services-oriented Architecture (SOA) implementation. This document describes the design of SICS API Server. It explains the basic architecture and important properties. For a full description of the supported Web Services, including WSDL/XSD files and sample SOAP messages, please refer to the documentation that is available after installing SICS API Server. /sicsdocs/technical/server/api_server/xsd_patterns/introduction/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/xsd_patterns/introduction/ This document explains how Lists (collections) are handled in the SICS API Server XSD files. The document is relevant for developers who program SOAP calls to invoke Web Services. /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/server/operational_reporting/setup_and_configuration/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/operational_reporting/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 Operational Reporting Server # SICS Operational Reporting Server is an analytics and visualization web platform to give real-time visualization of operational data within SICS. SICS Operational Reporting Server Installation # SICS Operational Reporting Server is a Web Application and can potentially be deployed in any Application Server. /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/api_server/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/ /sicsdocs/technical/server/api_server/technical_paper/concepts/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/technical_paper/concepts/ Overall description # SICS API Server provides access to SICS functionality through Web Services. Web Services is an industry accepted standard for application interoperability. SICS API Server enables the use of SICS as server component in a number of scenarios: Calling SICS functions from other applications, e.g. to request information from the SICS database (for example retrieving information for a business); perform an operation using SICS logic (for example exchanging a monetary amount using SICS’s exchange rates and rules, create a business or renew a business). /sicsdocs/technical/server/operational_reporting/deployment/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/operational_reporting/deployment/ Introduction # This guide will walk you through the steps to set up and run the Operational reporting server application contained in the artifact assure.reinsurance.operational.reporting.ui.zip on your server. SICS Operational Reporting Server is an analytics and visualization web platform to give real-time visualization of operational data within SICS. Prerequisites # Before you begin, ensure you have the following installed on your server: Node.js (version 20.x or later) npm (Node Package Manager) Step 1: Extract the Artifact # Upload or transfer the artifact assure. /sicsdocs/technical/server/api_server/installation_guide/install_java_container/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/install_java_container/ SICS API Server is a web application running Java 21 or higher. It 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 Apache Tomcat 10.1 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/server/api_server/xsd_patterns/list_elements/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/xsd_patterns/list_elements/ In the SICS API Server XSD’s three different types of lists are used: ReplaceAllList CreateList/AddList UpdateList In the following we will use the example where: ‘Master’ is a domain object. It has 1:M relationship with ‘DetailA’ and ‘DetailB’ objects. ReplaceAllList # This type of ‘List’ is used to perform ‘replaceAll’ operation. The ‘replaceAll’ operation will replace all the existing elements in the collection and add new ones present in the list. /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/server/api_server/server_security/security_parameters/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/server_security/security_parameters/ Three parameters determine ‘Secure’ and ‘Non-Secure’ Modes of SICS API Server Start-up. The parameters act as overall switches for the authentication and authorization security functions. The parameters are found in the web.xml file. If SICS API Server is installed as described in SICS API Server - Installation Guide, this file can be found (for Tomcat 10.x) in: %CATALINA_HOME%/webapps/SicsServer/WEB-INF/web.xml. The parameters are: Parameter name Valid values Default Purpose web.xml ApplyServerSecurity true/false false Indicates whether SICS API Server is running in secure mode or not. /sicsdocs/technical/server/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/ /sicsdocs/technical/server/api_server/server_security/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/server_security/ /sicsdocs/technical/server/adh_server/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/adh_server/ Contents # This document contains instructions on how to install and successfully configure an instance of SICS Automated Document Handling Server. Requirements # SICS ADH Server requires an Application Server running in a Java 21 or later runtime environment. Installation # SICS ADH Server is a Web Application and can potentially be deployed in any Application Server. For deploying an instance of SICS ADH Server it is enough to deploy SicsADHServer. /sicsdocs/technical/server/api_server/xsd_patterns/appendix_a/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/xsd_patterns/appendix_a/ The following is a list of Web Services which use “List Framework”. This list is not exhaustive and should be considered only as examples. P&C Claims # S.No Name of the Web Service 1 Create New Claim 2 Update Claim 3 Create and Update Claim FGU 4 Create Headline Loss 5 Update Headline Loss 6 Headline Loss: Retrieve Claim List 7 Move Claim from one Claim Program to Another 8 Create Claim program 9 Update Claim Program 10 Create Claim Group 11 Update Claim Group 12 Delete Claim-to-SOC relation Insurable Object # S. /sicsdocs/technical/server/api_server/server_security/authentication/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/server_security/authentication/ If SICS API Server is started in secure mode, all normal Web Services calls must include an authentication token. The caller must obtain this token by sending an initial “login” message to SICS API Server. The Login service # Sample SOAP Request and Response # The SOAP request (input message) for the login service must follow one of these formats (see discussion on OS AUTHENTICATION and <sicsUserId> further down): <SOAP-ENV:Envelope . /sicsdocs/technical/server/api_server/installation_guide/configure_api_server_for_tomcat_deployment/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/configure_api_server_for_tomcat_deployment/ SICS API 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 API 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/api_server/technical_paper/features/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/technical_paper/features/ Stateless # SICS API Server is designed to operate in a stateless manner. In other words, each SOAP call must contain the data that is necessary for SICS API Server to fully process the SICS business function. Parts of the data may consist of references to data that already exist in the SICS operational database. Commit / Rollback / Unit of Work # Each SOAP call to the SICS API Server will either succeed 100% or fail completely. /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/api_server/technical_paper/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/technical_paper/ /sicsdocs/technical/server/api_server/server_security/authorization/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/server_security/authorization/ Authorization is the process of ensuring that the caller invokes services that the caller is allowed to execute, according to the caller’s SICS user profile. When receiving a service call request, SICS API Server verifies whether the SICS user identified by the “User ID” (present in the Authentication Token) has Access Rights to execute the service, according to the (existing) security set-up defined via the SICS System Administration utility. See also SICS API Server - Installation Guide, on how to set up your own authorization policy. /sicsdocs/technical/server/api_server/installation_guide/configure_tomcat_for_api_server_deployment/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/configure_tomcat_for_api_server_deployment/ Memory Setting # SICS API 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\tomcat9w.exe program You will then see a window like this: Figure 1 - Apache Tomcat Windows Service Properties 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/api_server/technical_paper/deployment/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/technical_paper/deployment/ This section briefly explains the hardware and software required for installing and running the SICS API Server component. It is assumed that there already exists a SICS database that the SICS API Server will work against. Hardware Requirements # The SICS API Server component runs inside a Java servlet container. Such containers are available for many operating systems. One instance of SICS API Server requires at least 1 GB of memory running on a 64-bit operating system. /sicsdocs/technical/server/emessaging_server/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/emessaging_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/api_server/installation_guide/deploy_api_server_to_java_servlet_container/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/deploy_api_server_to_java_servlet_container/ 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. https://tomcat.apache.org/tomcat-10.1-doc/index.html 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): (You must log in with the username and password set when installed Tomcat) /sicsdocs/technical/server/api_server/server_security/enable_api_server_module/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/server_security/enable_api_server_module/ To enable the API Server module, check the API Server module in use checkbox in System Parameter Maintenance -> Module Key. Figure 1 - Module Keys System Parameter /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/api_server/installation_guide/configure_api_server_environment/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/configure_api_server_environment/ Required knowledge # Most SICS API 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 # Configure logging Configure security Configure system pool size Configure queue sizes Configure caching of data Configure xml files Configure HTTP return codes Configure logging # Turn on/off Separate Logging of SOAP Messages # The default installation of SICS API Server logs SOAP messages to a separate log. /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/operational_reporting/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/operational_reporting/ /sicsdocs/technical/server/api_server/server_security/web_services_use_cases/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/server_security/web_services_use_cases/ Use Case security # Each Web Service is defined as a “Use Case” in the SICS Security module. This means that it is possible to “switch off” each of the Web Services that your company do not use, by simply removing the unused Use Cases from the security profiles. Naming convention # All Web Services Use Cases are named with the “API” (Application Programming Interface) prefix, to easily separate them from the normal SICS Workstation Use Cases. /sicsdocs/technical/server/api_server/xsd_patterns/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/xsd_patterns/ /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/server/api_server/installation_guide/verify/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/verify/ 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. /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/server/api_server/installation_guide/monitoring_sics_server/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/monitoring_sics_server/ 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 /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/api_server/installation_guide/multiple_instances/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/multiple_instances/ 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. /sicsdocs/technical/server/api_server/installation_guide/additional_information/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/additional_information/ 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. /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/api_server/installation_guide/appendix_a/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/appendix_a/ 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. /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/api_server/installation_guide/appendix_b/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/appendix_b/ 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 SICS disconnects from the database SICS connects (once more) to the database using the second-level name and password from the SICS User Object This connection is used for all later access and updates to the database In other words, when using application managed login, the db connection is under control by the application, i. /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/api_server/installation_guide/appendix_c/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/installation_guide/appendix_c/ It is possible to run Tomcat without installing it as a Windows service. This section briefly explains a few differences from the ‘Tomcat installed as a Windows service’ procedure described above. Download and Unzip Tomcat # Download the Tomcat zip file and unzip to some folder. Hereafter, the alias TOMCAT refers to the folder where Tomcat is unzipped. Java setup # Install the 64-bit Java Development Kit 21 (JDK 21) or later as described above. /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.