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.
...
Running SICS Scheduler as a Windows Service # SICS Scheduler may be run as a Windows service using the wrapper functionality provided by Apache commons daemon. This applies only when starting the scheduler in unattended mode (using one of the -b options, see Appendix C - Command line parameters).
Initial Installation # The SICS System Administration Utility must be installed in a local drive on the computer. The System Administration Utility must be configured to use only resources on local drives on the computer.
...
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.
...
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.
...
Splash Screen Branding # The SICS splash screen is graphic shown while SICS loads. This graphic contains a background image and the DXC logo. During the loading process, the SICS version and build information is painted on this graphic to inform the user which version of SICS is loading.
The background graphic image changes annually and as part of creating the new graphic, the position of the DXC logo and the SICS version information may change.
...
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>
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.
...
Setting Additional Database Connection Properties # JDBC Connection parameters can be added to configure different aspects of the connection to the database. Configuration properties are platform specific and not common across DB platforms. For some DB platforms, JDBC connection properties can be provided as part of the connection URL (configured with the <dataSource> tag in sics-database-sources.xml).
It is also possible - for all DB platforms - to configure JDBC connection properties on the command line and/or with the <additionalJdbcConnectionProperties> tag in sics-database-sources.
...
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:
...