Skip to main content

Unattended SDL Web 8.5 Installation

In a recent project, we had the requirement to install the SDL Web 8.5 Content Manager and the Publisher using script only (aka an unattended installation).

I knew about the existence of such an unattended installation, but I for one, have never attempted it. The feature is clearly documented in http://docs.sdl.com/LiveContent/content/en-US/SDL%20Web-v5/GUID-CE873235-5FE0-489D-A63C-B979919D8F9E.

All the prerequisites must still be fulfilled before the actual unattended installation can take place:

  • In Server Manager:
    • Server Roles:
      • Web Server (IIS)
    • Features:
      • .NET Frameowrk 4.6
        • ASP.NET 4.6
        • WCF Services
          • (all of them, including other features needed as dependencies)
    • Web Server Role (IIS)
      • Role Services
        • Common HTTP Features (all of them)
        • Health & Diagnostics (all)
        • Performance (all)
        • Security (all)
  • Install Java Runtime Environment

Content Manager DB must be created in advance. MTS user must be created in advance.

Once all prerequisites are met, I was able to proceed with the actual unattended installation.

To install the Content Manager, I successfully used the following command inside a .bat file:

D:

mkdir "\Software\log"

del "\Software\log\*.*" /Q

cd "\Software\SDL Web 8.5\SDL Web 8.5\Content Manager"

SDLWeb85CM.exe -s -log "D:\Software\log\install.log" ACCEPT_EULA=true
    DB_SERVER=mydb.eu-west-1.rds.amazonaws.com DB_NAME=Tridion_cm DB_USER=TCMDBUser
    DB_PASSWORD=dbpass TRIDION_CM_ENVIRONMENT_ID=Tridion_cm_dbblabla
    SYSTEM_ACCOUNT_NAME=MTSUser SYSTEM_ACCOUNT_DOMAIN=mydomain
    SYSTEM_ACCOUNT_PASSWORD=mypass LICENSE_PATH="D:\Software\licenses\license.xml"
    CD_LICENSE_PATH="D:\Software\licenses\cd_licenses.xml" WEB_PORT=80
    TTM_DB_SERVER=mydb.eu-west-1.rds.amazonaws.com TTM_DB_NAME=Tridion_Topology
    TTM_DB_USER=TTMDBUser TTM_DB_PASSWORD=pass TTM_WEB_PORT=81
    INSTALLLOCATION="D:\SDL Web" WEBLOCATION="D:\SDL Web\web"

To install the Content Publisher, I ran the following commands. Note that I had to exclude quite a few features from the installation, in order to _only_ install the Transport and Publisher services:

D:

mkdir "\Software\log"

del "\Software\log\*.*" /Q

cd "\Software\SDL Web 8.5\SDL Web 8.5\Content Manager"

SDLWeb85CM.exe -s -log "D:\Software\log\install.log" ACCEPT_EULA=true
    DB_SERVER=mydb.eu-west-1.rds.amazonaws.com DB_NAME=Tridion_cm DB_USER=TCMDBUser
    DB_PASSWORD=pass TRIDION_CM_ENVIRONMENT_ID=Tridion_cm_mydb SYSTEM_ACCOUNT_NAME=MTSUser
    SYSTEM_ACCOUNT_DOMAIN=mydomain SYSTEM_ACCOUNT_PASSWORD=pass
    LICENSE_PATH="D:\Software\licenses\license.xml"
    CD_LICENSE_PATH="D:\Software\licenses\cd_licenses.xml"
    CdWindowsServices_SelectedFeatures=FeatureTransportService
    cm_SelectedFeatures=FeatureContentManager,FeaturePublisherService
    CMECore_SelectedFeatures= CMEGui_SelectedFeatures= ContextExpressions_SelectedFeatures=(All)
    ExperienceManager_SelectedFeatures= Documentation_SelectedFeatures=
    ExternalContentLibrary_SelectedFeatures= SpellChecker_SelectedFeatures= TcmSearch_SelectedFeatures=
    TemplateBuilder_SelectedFeatures= TopologyManager_SelectedFeatures=(All)
    TTM_DB_SERVER=mydb.eu-west-1.rds.amazonaws.com TTM_DB_NAME=Tridion_Topology
    TTM_DB_USER=TTMDBUser TTM_DB_PASSWORD=pass TTM_WEB_PORT=81 INSTALLLOCATION="D:\SDL Web"


Comments

ABAN said…
This dont work bat file gives error of is not a recognized as an internal or external command operable program for batch

Popular posts from this blog

Running sp_updatestats on AWS RDS database

Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: https://dba.stackexchange.com/questions/145982/sp-updatestats-vs-update-statistics I stumbled upon the following post from 2008 (!!!), https://social.msdn.microsoft.com/Forums/sqlserver/en-US/186e3db0-fe37-4c31-b017-8e7c24d19697/spupdatestats-fails-to-run-with-permission-error-under-dbopriveleged-user , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as...

REL Standard Tag Library

The RSTL is a library of REL tags providing standard functionality such as iterating collections, conditionals, imports, assignments, XML XSLT transformations, formatting dates, etc. RSTL distributable is available on my Google Code page under  REL Standard Tag Library . Always use the latest JAR . This post describes each RSTL tag in the library explaining its functionality, attributes and providing examples. For understanding the way expressions are evaluated, please read my post about the  Expression Language used by REL Standard Tag Library . <c:choose> / <c:when> / <c:otherwise> Syntax:     <c:choose>         <c:when test="expr1">             Do something         </c:when>         <c:when test="expr2">             Do something else         </c:when...

Publish Binaries to Mapped Structure Groups

Today's TBB of the Week comes from the high demand in the field to publish binary assets to different mapped Structure Groups. By default SDL Tridion offers two ways of publishing binaries: All binaries publish to a folder defined in your Publication properties; All binaries rendered by a given template publish to a folder corresponding to a given Structure Group; In my view, both cases are terrible, over-simplified and not representing a real use-case. Nobody in the field wants all binaries in one folder and nobody separates binary locations by template. Instead, everybody wants a mapping mechanism that takes a binary and publishes it to a given folder, defined by a Structure Group, and this mapping is done using some kind of metadata. More often than not, the metadata is the TCM Folder location of the Multimedia Component. I have seen this implemented numerous times. So the solution to publish binaries to a given location implies finding a mapping from a TCM Folder to a...