Contents
-
Introducing Tachyon
-
Quick Start
-
Implementing Tachyon
-
Using Settings
-
Using Explorer
-
Using Guaranteed State
-
Using Inventory
-
Using Experience
-
Using Patch Success
-
Troubleshooting
-
Extending Tachyon
-
Training
-
Reference
-
Supported Platforms
-
1E Companion Products
-
Server Sizing
-
Communication Ports
-
Tachyon installation requirements on-premises
-
Naming conventions
-
Log files
- Server installers
-
Tachyon Server reference
-
Tachyon client reference
-
Explorer reference
-
Inventory reference
-
Tachyon Product Packs reference
-
Tachyon release information
-
Glossary
-
Index
-
Supported Platforms
Summary
A table of the Windows installer properties for the SLA Platform installer.Tachyon Setup is the only supported method of installing a Tachyon Server. Installation using standalone MSI is not supported unless advised by 1E, which may be necessary in complex installations, using non-interactive (quiet/silent) command-lines, and may require post-install configuration steps.
Mandatory properties must be provided when installing using a command-line. The table shows which default values are managed by Tachyon Setup
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. Tachyon Setup prompts for the SQL Server database instance. | |
CATALOG_DATABASE_USEINTEGRATEDSECURITY | 1 | No | Determines which method the SLA Platform services and application pools will acess the 1E Catalog database
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. Tachyon 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. Tachyon 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
Tachyon Setup uses 1: Windows authentication. |
CUSTOMER_USERNAME | The installer account | No | The default web user.
The Domain part of the username will restrict access to SLA Platform to just users from that domain. See Requirements: Server Installation Account Tachyon Setup uses the default: the installer account. |
IIS_HOST_HEADER | Host header used for the HTTP binding of the SLA Platform website. See HTTP binding note below. Tachyon Setup uses the same HTTP host header as the Tachyon website, which defaults to the servername FQDN. | ||
IIS_HTTP_PORT | 8080 | No | Port used for the HTTP binding of the SLA Platform website. See HTTP binding note below. Tachyon Setup uses the same HTTP port as the Tachyon website, which defaults to 80. This causes the SLA Platform web applications to be installed under the Tachyon website. |
IIS_HTTPS_PORT | 8443 | No | Port used for the HTTPS binding of the SLA Platform website. Used only if SLA_ENABLE_HTTPS=1. See HTTPS binding note below. Tachyon Setup uses the same HTTPS port as the Tachyon website, which defaults to 443. This causes the SLA Platform web applications to be installed under the Tachyon 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 See HTTP binding note below. Tachyon Setup uses the same HTTP IP Address binding as the HTTP binding IP Address of the Tachyon website, which defaults to * (all). This causes the SLA Platform web applications to be installed under the Tachyon website. |
IIS_SITE_NAME | SLA Platform Web Site | No | Website name. Not configurable in the installer UI. Tachyon Setup does not use this as it expects the SLA PLatform will be installed under the Tachyon 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. See HTTPS binding note below. Tachyon Setup uses the same web server certificate as the Tachyon 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. Tachyon 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. Tachyon 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. See HTTPS binding note below. Tachyon Setup uses the same web server certificate as the Tachyon website. | |
INSTALLFOLDER | C:\Program Files\1E\SLAPlatform\ | No | The installation directory in the Custom Setup screen. If you change the install location please ensure the service account has the necessary NTFS security permissions, as described in Preparation: Services and NTFS Security. Tachyon Setup uses the same parent folder as the Tachyon installation. The SLA Platform installer does not support INSTALLDIR. |
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.
An additional logs folder is found in C:\ProgramData\1E\Platform Consumer If you change the logs folder location please ensure the service account has the necessary NTFS security permissions, as described in Preparation: Services and NTFS Security The SLA Platform installer does not support LOGPATH Not used by Tachyon Setup. |
SLA_ENABLE_HTTPS | 1 | No | Determines whether an HTTPS binding is created in addition to the HTTP binding. Tachyon 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). Tachyon Setup uses 0: Network Service. The service account is used for the following:
|
SVC_USEACCOUNT_PASSWORD | Yes | Password for SVC_USEACCOUNT_USERNAME. Not used by Tachyon Setup. | |
SVC_USEACCOUNT_USERNAME | No | The service account if SVC_USEACCOUNT=1. Must be specified as domain\username. Not used by Tachyon Setup. | |
TARGETDIR | C:\ | No |
You need to use the msiexec /a SLA.Platform.Installer.msi TARGETDIR="C:\Source\SLAPlatform" Not used by Tachyon Setup. |