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>
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:
...
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.
...
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)
...
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.
...
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.
...
Release date # July 3rd. 2019.