Documentation Center

Typical server installation changes

Things that have changed on a single web/app server setup when using InstallTool (IT) or DBUpgradeTool (DBUT).

Prerequisites

You'll find the full list and versions in the documentation Requirements chapters (also present in the Installation and Upgrade guides). Here is a focus on the changes:
  1. Operating System Programs and Features
    • We added an official statement that we only fully qualify on English Windows Server Operating Systems. [TS-7891]
    • By a one-time operation to open up permissions in %WINDIR%\System32\inetsrv\config\applicationHost.config, we can now easily overwrite server settings per web site and/or virtual directory through their web.config file. See Configuring IIS applicationHost.Config. This will move typical settings like <defaultDocument>, <directoryBrowse>, <asp>, <staticContent>, ... to web.config. Note that <security> and <authentication> are still part of applicationHost.config.
    • Installation of Static and Dynamic compression features have been added to requirements.
  2. Third Party Components have been raised to:
    • Microsoft Server .NET Framework 4.5
    • Microsoft .NET Framework Visual C++ Redistributable 2013 (64-bit)
    • Java Development Kit 1.8.0_60 (64-bit)
    • Java Runtime Environment 1.8.0_60 (64-bit)
    • Oracle Data Access Client (ODAC) 12.1.0.1.2
    • PowerShell v4.0 (part of Windows Management Framework 4.0)

While installing or upgrading

InstallTool doesn't stop or start Windows service IISAdmin.

By opening up applicationHost.Config we can enable Static and Dynamic Compression for regular HTTP and SOAP messaging calls out of the box. The end result of applying our typical installation steps will result in a system where WCF SOAP messages and DTD related files that are synchronized by Client Tools are now also compressed.

Starting from IIS 8.x, so Windows 2012R2, InstallTool (IT) will configure every IIS Application Pool to always be alive. This will shorten delays of first requests to an idle server.

Post installation steps

Configuration overview when upgrading from 11.0.X to this version.
Settings / File11.0.0 Config Version12.0.0 Config VersionWhat has changed
Admin.XMLBackgroundTaskConfiguration.xml1.11.1
  • Added handlers: CREATETRANSLATIONFROMLIST, CREATETRANSLATIONFROMREPORT, CREATETRANSLATION
  • Removed handlers: DELETETRANSLATIONS, BATCHPERFORMACTION
Admin.XMLChangeTrackerConfig.xml1.01.0
  • n/a
Admin.XMLExtensionConfiguration.xmln/a1.0
  • New configuration, holds<infoShareExtensionConfig> ; disabled PreTranslation configuration and IMetadataBinding extensions
Admin.XMLInboxConfiguration.xml1.01.0
  • n/a
Admin.XMLPluginConfig.xml1.01.0
  • Deprecated, replaced by Admin.XMLWriteObjPluginConfig.xml
Admin.XMLStatusConfiguration.xml2.03.0
  • <OutOfDateStates> must be configured as regular statuses
Admin.XMLTranslationConfiguration.xml1.02.0
  • Controlled pivot <languagepaths> and moved <ComparisonElements> to Admin.XMLExtensionConfiguration.xml
Admin.XMLWriteObjPluginConfig.xml2.02.0
  • ISHRAISEPUBLISHEVENT should be the last plug-in in section <write ishcondition="ISHType='ISHPublication'">otherwise publishing will not work
  • Element names can be used instead of labels for configuration
  • Deactivated CHECKREVIEWERFILLEDIN and CHECKTRANSLATORFILLEDIN
  • Plugins on Translation Management means: Finetuned @ishcondition CurrentAction called "CreateTranslation" and updated handlers ISHSYSWORDCOUNT, ISHSYSCOPYFISHTOBETRANSLWC and ISHSYSTRANSLATIONLOAD

After the installation is complete, none of our Windows services (including Crawler, TrisoftSolrLucene,...) will start automatically. The first reason is that the database is not guaranteed to be in the right state until you run DBUpgradeTool (DBUT). Another reason is that in a multi server environment you wouldn't want all your servers to pick up the same role. For your convenience on a single web/app server setup, we've provided a simple PowerShell script that will start and mark all services as Automatic. For using it, execute \App\Setup\Manage\Enable-DefaultServices.ps1 as Administrator.