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.
...
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.
...
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.
...
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.
...