Skip to main content

Unattended SDL Web 8.5 Installation

Image
By
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"


Labels:

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
21 June, 2019 18:00
Post a Comment

Popular posts from this blog

Scaling Policies

By
This post is part of a bigger topic Autoscaling Publishers in AWS . In a previous post we talked about the Auto Scaling Groups , but we didn't go into details on the Scaling Policies. This is the purpose of this blog post. As defined earlier, the Scaling Policies define the rules according to which the group size is increased or decreased. These rules are based on instance metrics (e.g. CPU), CloudWatch custom metrics, or even CloudWatch alarms and their states and values. We defined a Scaling Policy with Steps, called 'increase_group_size', which is triggered first by the CloudWatch Alarm 'Publish_Alarm' defined earlier. Also depending on the size of the monitored CloudWatch custom metric 'Waiting for Publish', the Scaling Policy with Steps can add a difference number of instances to the group. The scaling policy sets the number of instances in group to 1 if there are between 1000 and 2000 items Waiting for Publish in the queue. It also sets the
Post a Comment
Read more

Toolkit - Dynamic Content Queries

By
This post if part of a series about the  File System Toolkit  - a custom content delivery API for SDL Tridion. This post presents the Dynamic Content Query capability. The requirements for the Toolkit API are that it should be able to provide CustomMeta queries, pagination, and sorting -- all on the file system, without the use third party tools (database, search engines, indexers, etc). Therefore I had to implement a simple database engine and indexer -- which is described in more detail in post Writing My Own Database Engine . The querying logic does not make use of cache. This means the query logic is executed every time. When models are requested, the models are however retrieved using the ModelFactory and those are cached. Query Class This is the main class for dynamic content queries. It is the entry point into the execution logic of a query. The class takes as parameter a Criterion (presented below) which triggers the execution of query in all sub-criteria of a Criterio
Post a Comment
Read more

Running sp_updatestats on AWS RDS database

By
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
1 comment
Read more