/sicsdocs/technical/misc/java_launcher_application/ Recent content in SICS Java Launcher Application on Hugo -- gohugo.io /sicsdocs/technical/misc/java_launcher_application/introduction/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/java_launcher_application/introduction/ The SICS Java Launcher is a standalone Java application which can be used for distributing a centrally installed version of DXC SICS to a ’local’ folder. The benefits are: Users do not hold file locks on the central installation. Therefore, it will be possible to replace the central installation with a newer version of SICS. Depending on network configuration, it may be faster to start SICS from the ’local’ folder, once the SICS runtime has been copied to this folder. /sicsdocs/technical/misc/java_launcher_application/installation/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/java_launcher_application/installation/ Installing the SICS Java Launcher is a matter of extracting the SicsJavaLauncher.zip file to a suitable location and making the relevant configuration settings in the /conf/SicsJavaLauncher.ini file. The configuration settings are described in detail inside the /resources/SicsJavaLauncher.ini file. The location to the 64-bit JRE 17+ installation can be configured in SicsJavaLauncher.bat. By default the script will look for the JRE inside the SICS Java Launcher install folder. Low-level logging and trouble shooting are supported through log4j. /sicsdocs/technical/misc/java_launcher_application/installation_of_new_runtime/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/misc/java_launcher_application/installation_of_new_runtime/ Because the SICS Java Launcher works by copying the DXC SICS runtime from a designated folder (call it F), care should be taken when installing a new runtime. The following procedure is recommended: Install the new runtime in a new folder F2 Rename the ‘old’ runtime folder F to F3 Rename F2 to F Delete or archive F3.