SummaryA list of Windows installer properties for the 1E Catalog installer.
The installer file is: 1ECatalog.msi
Make sure you complete all steps on the Preparation page before installation.
See Installation and upgrades for more details about interactive and non-interactive installations.
|DATABASENAME||1ECatalog||No||Name for the 1E Catalog database.|
If set to 1 on the command-line, it drops the 1ECatalog database during installation if it exists on the specified SQL Server instance. The default behavior for this property is to not drop the existing database.
Exercise caution when using this option as any existing data will be deleted. Do not use this option if you want to preserve your existing data.
Used to enable the download of model file updates, which are used to drive AI Auto-curation. Set 0 to disable and 1 to enable.
This property is no longer available.
TLS 1.2 support is now an integral part of the 1E Catalog installer.
Host header used for the HTTP binding of the website hosting the CatalogWeb web application.
If used, this should be a DNS FQDN of the web server, recommended to be a CNAME, for example:
IP address used for the HTTP binding of the website hosting the CatalogWeb web application.
If you want to be non-specific about the IP address, use the default
See HTTP binding note below .
Port used for the HTTP binding of the website hosting the CatalogWeb web application.
The installation directory in the Destination Folder screen.
The folder where the Catalog.UpdateService.log and Catalog.Integration.UI.log files are found.
|SQLSERVER||(local)||Yes||Name of the SQL Server instance where the 1E Catalog database is installed.|
Password for SVCUSER.
|NT Authority\Network Service||Yes|
You have two options for the Service Account:
If you want to use NT Authority\Network Service do not set the SVCUSER property.
Please refer to Accounts needed to install the Catalog.
If an existing website uses the same HTTP binding (combination of HTTP port and IP address, and also Host Header if used) then the Catalog web application will be created under that website. For example, the Catalog web application is normally created under Default Web Site because it uses port 80 and * by default. If an existing website does not have a matching HTTP binding then the installer will create a new website called CatalogWeb with the specified HTTP binding.