SLA Platform installer properties

TeamViewer DEX Platform 26.3 | 1E Platform 23.11 | 1E Platform on-premises 9.x

Explore the installer properties for setting up the 1E SLA Platform. This guide explains each option to help you customize and automate your SLA Platform deployment.

1E Server setup is the only supported method of installing, upgrading, and patching a 1E server. Installation using standalone msi or msp files is not supported unless advised by 1E, which may be necessary in complex installations, using non-interactive (quiet/silent) command-lines, and may require further post-install configuration steps.

Mandatory properties must be provided when installing using a command-line.

The installer file is: SLA.Platform.Installer.msi

Property	Default	Mandatory	Description
CATALOG_DATABASE_NAME	1ECatalog	No	The name of the 1E Catalog database.
CATALOG_DATABASE_SERVER		Yes	The SQL Server instance name which hosts the 1E Catalog database. 1E Setup prompts for the SQL Server database instance.
CATALOG_DATABASE_USEINTEGRATEDSECURITY	1	No	Determines which method the SLA Platform services and application pools will access the 1E Catalog database: 1: Windows authentication uses the specified SVC_USEACCOUNT service account. 0: SQL authentication uses the specified SQL Login. The SLA Platform uses a Linked Server on the SQL Server instance that hosts the SLA Platform databases, to access the 1E Catalog database. The SLA Platform also connects to the Catalog API, which it finds by reading the CatalogSettings table in the 1E Catalog database. 1E Setup uses 1: Windows authentication.
COMMON_DATABASE_SERVER		Yes	The SQL Server instance name which will host the four SLA Platform databases. Do not specify (local) even if the SQL Server instance is local. This avoids issues with Linked servers used by SLA Platform and companion products. DROPOLDDB is not supported. If you want to create new databases then manually drop the old ones first, after backing them up. 1E Setup prompts for the name of the SQL Server instance.
COMMON_DATABASE_USEINTEGRATEDSECURITY	1	No	Determines which method the SLA Platform services and application pools will acess the SLA Platform databases 1: Windows authentication uses the specified SVC_USEACCOUNT service account. 0: SQL authentication uses the specified SQL Login. 1E Setup uses 1: Windows authentication.
CUSTOMER_USERNAME	The installer account	No	The default web user: Must be a domain user account. Normally the same as the Installer account. Specified in the Customization Settings panel in the SLA Platform installer (not available in 1E Setup). This is the only account that can be used when first logging into the SLA Platform website, until the account is used to create additional users. The Domain part of the username will restrict access to SLA Platform to just users from that domain. Refer to SQL Logins for the server installation account 1E Setup uses the default: the installer account.
IIS_HOST_HEADER			Host header used for the HTTP binding of the SLA Platform website. Refer to HTTP binding. 1E Setup uses the same HTTP host header as the 1E Platform website, which defaults to the servername FQDN.
IIS_HTTP_PORT	8080	No	Port used for the HTTP binding of the SLA Platform Website. Refer to HTTP binding. 1E Setup uses the same HTTP port as the 1E Platform website, which defaults to 80. This causes the SLA Platform web applications to be installed under the 1E Platform website.
IIS_HTTPS_PORT	8443	No	Port used for the HTTPS binding of the SLA Platform website. Used only if SLA_ENABLE_HTTPS=1. Refer to HTTPS binding. 1E Setup uses the same HTTPS port as the 1E Platform website, which defaults to 443. This causes the SLA Platform web applications to be installed under the 1E Platform website.
IIS_IP_ADDRESS	*	No	IP address used for the HTTP binding of the SLA Platform website. If you want to be non-specific about the IP address, use the default . Refer to HTTP binding. 1E Setup uses the same HTTP IP Address binding as the HTTP binding IP Address of the 1E Platform website, which defaults to (all). This causes the SLA Platform web applications to be installed under the 1E Platform website.
IIS_SITE_NAME	SLA Platform Web Site	No	Website name. Not configurable in the installer UI. 1E Setup does not use this as it expects the SLA Platform will be installed under the 1E Platform website.
IIS_SSL_CERTIFICATE_SERIAL		Yes, if HTTPS is enabled	The serial number of the specified SSL certificate. Used only if SLA_ENABLE_HTTPS=1. Refer to HTTPS binding 1E Setup uses the same web server certificate as the 1E Platform website.
IIS_SSL_CERTIFICATE_STORE_NAME	My	No	The certificate store in which to search for the specified SSL certificate. My is the Personal store. Used only if SLA_ENABLE_HTTPS=1. 1E Setup uses the default: My.
IIS_SSL_CERTIFICATE_STORE_LOCATION	LocalMachine	No	The account type for the specified certificate store. LocalMachine is the Computer account. Used only if SLA_ENABLE_HTTPS=1. 1E Setup uses the default: LocalMachine.
IIS_SSL_CERTIFICATE_THUMBPRINT		Yes, if HTTPS is enabled	The thumbprint of the specified SSL certificate. Used only if SLA_ENABLE_HTTPS=1. Refer to HTTPS binding. 1E Setup uses the same web server certificate as the 1E Platform website.
INSTALLFOLDER	C:\Program Files\1E\SLAPlatform\	No	The installation directory in the Custom Setup screen. If you change the install location ensure the service account has the necessary NTFS security permissions, as described in Services and NTFS Security. 1E Setup uses the same parent folder as the 1E installation. The SLA Platform installer does not support INSTALLDIR.
INTEGRATE_REST_PORT	6002	No	Port used by SLA Integrate services. The Integrate Manager listens on this port for the Integrate Agent. 1E Setup uses the default 6002.
LOG_FOLDER	C:\ProgramData	No	The folder where the SLA Platform log files are found, as well as other resource files, including inventory product packs. 1E.SLAConnector.sccm_sync.log 1E.SLAPlatformIntegrateAgent.log 1E.SLAPlatformIntegrateManager.log An additional logs folder is in C:\ProgramData\1E\Platform Consumer If you change the logs folder location ensure the service account has the necessary NTFS security permissions, as described in Services and NTFS Security. The SLA Platform installer does not support LOGPATH. Not used by 1E Setup.
SLA_ENABLE_HTTPS	1	No	Determines whether an HTTPS binding is created in addition to the HTTP binding. 1E Setup uses 1: enable HTTPS.
SLA_PLATFORM_FQDN	The FQDN of the server	No	The FQDN of the SLA Platform server.
SVC_USEACCOUNT	1	Yes	Specifies whether the service account is a domain account (1) or Network Service (0). 1E Setup uses 0: Network Service. The service account is used for the following: 1E SLA Platform Engine service 1E SLA Platform Integrate Agent service 1E SLA Platform Integrate Manager service SLAPlatform web application pools (3)
SVC_USEACCOUNT_PASSWORD		Yes	Password for SVC_USEACCOUNT_USERNAME. Not used by 1E Setup.
SVC_USEACCOUNT_USERNAME		No	The service account if SVC_USEACCOUNT=1. Must be specified as domain\username. Not used by 1E Setup.
TARGETDIR	C:\	No	TARGETDIR is used only for administrative installation, it is not used for normal installations. You need to use the TARGETDIR property for an administrative installation of SLA Platform, for example if you want to unpack the MSI to find a specific file. Copy `msiexec /a SLA.Platform.Installer.msi TARGETDIR="C:\Source\SLAPlatform"` Not used by 1E Setup.

HTTP binding

If an existing website uses the same HTTP binding (combination of HTTP port, host header and IP address) then the SLA Platform web applications will be created under that website instead of under a dedicated website called SLA Platform Web Site.

HTTPS binding

When doing a non-interactive install, an HTTPS binding is created only if all of the following are specified:

SLA_ENABLE_HTTPS=1
IIS_SSL_CERTIFICATE_SERIAL
IIS_SSL_CERTIFICATE_THUMBPRINT