On Thu, Aug 6, 2020 at 9:09 AM Christopher Schultz wrote: I don't know if you are interested in such things, but being table to > export a configuration from one machine to another might be useful for > your installer, too. Something like "deploy to server A, > manually-configure, tweak, test, prove" and then "copy deployment > configuration to servers B - Z". >
The alternative installer doesn't export a configuration, but it does let you repeat an installation using command-line options to get a similar effect; e.g.: apache-tomcat-a.b.c-setup.exe /type=core /serviceusername="domain\account" /jvmoptions="-Djavax.net.ssl.trustStoreType=WINDOWS-ROOT" /jvmms=2048 /jvmmx=2048 /silent /log="c:\windows\temp\tomcatinstall.log" (all on one line of course) For reference: /type="core" - installs only the core components (no docs, Manager, Host Manager, or examples web apps) /serviceusername="domain\account" - runs the service using the specified account (and also, by default permissions are set on the install directories to allow this account to write to the logs, temp, and work directories) /jvmoptions="-Djavax.net.ssl.trustStoreType=WINDOWS-ROOT" - tells the Java instance running Tomcat to trust the Windows certificate store /jvmms=2048 /jvmmx=2048 - sets the Java memory pool sizes for the service /silent - hands-free installation /log="c:\windows\temp\tomcatinstall.log" - logs to the specified file See the documentation - https://github.com/Bill-Stewart/ApacheTomcatSetup - for further information. Bill
