Hi Andriy,
There are two many different varfile variants to list them all in the documentation, so the recommended approach mentioned is to run a manual test installation once, which will generate a varfile that you can use for the production automated install. Here is an example varfile to use your own Postgres database:
# install4j response file for Burp Suite Enterprise Edition 2022.5
beuser=burpsuite
beuserandgroup=burpsuite\:burpsuite
dataDirectory=/var/lib/BurpSuiteEnterpriseEdition
dbType=postgres
escapedDataDir=/var/lib/BurpSuiteEnterpriseEdition
escapedInstallationDir=/opt/burpsuite_enterprise
jreHome=/opt/burpsuite_enterprise/jre
logsDirectory=/var/log/BurpSuiteEnterpriseEdition
platformScriptSuffix=sh
sys.adminRights$Boolean=true
sys.component.agent$Boolean=true
sys.component.db$Boolean=false
sys.component.enterprise$Boolean=true
sys.component.web$Boolean=true
sys.installationDir=/opt/burpsuite_enterprise
sys.languageId=en
sys.programGroupDisabled$Boolean=true
webserver_port$Integer=8443
Points to note:
1) When using an external database, the default port of 8443 must be used for initial installation, you can change this after install in the user interface if you want to.
2) Due to using an external database, the user interface will be accessible on HTTPS using a temporary self-signed certificate e.g
https://localhost:8443
- this can be changed after the installation is complete.
3) The database connection and database user information is entered in the browser user interface at the above URL after the command line install has completed.
4) Please also check you have run our database setup script for Postgres and followed this guide before starting the install:
https://portswigger.net/burp/documentation/enterprise/getting-started/setup-ext-db