Documentation Center

Installing the web application in Tridion 2013 SP1 (.NET)

Run the web-install.ps1 PowerShell script using the available parameters to create the Web application for SDL Digital Experience Accelerator Web sites.

Before you begin

  • If you are installing DXA 1.4, make sure you have .NET 4.5.2 installed.
  • Run the PowerShell script from a machine that has access to your Content Data Store database, for example on the machine that hosts the DXA Web site.

About this task

Setting Parameters
You can set the script parameters before running the script or on the command line:
  • Set the parameters on the command line when you run web-install.ps1 from the PowerShell command line, prefixing the parameters with a hyphen, for example -distDestination
This task describes how to run the script and set parameters on the command line.
Installing on Live and Staging Web sites

You need to run the web-install.ps1 PowerShell script on each machine where you want to publish content to, as defined by your Publication Targets. For example, on a Live machine where your external Web site is running, and/or on your Staging machine where you publish to an internal Web site where Experience Manager is set up for inline editing. Use the deployType parameter to specify the type of machine your are deploying to.

Procedure

  1. Access your SDL Digital Experience Accelerator installation media.
  2. Open a PowerShell command prompt in Run as administrator mode.
  3. Navigate to the \web\2013sp1 folder and run the web-install.ps1 script specifying each parameter-value pair in the following format -parameter "value" (enclosing values in quotes if needed).

    For example (on one line):

    & '.\web-install.ps1' -distDestination "C:\inetpub\wwwroot\My-site\"
    -webName "My-site" -siteDomain "" -sitePort 83 -logFolder "C:\My-site\" -sitePublicationId 11 
    -sessionDbServer "MySessionDBserver"
  4. Specify the following parameters:
    ParameterDescriptionDefault
    defaultDbServerThe server name of your Content Data Store database server.none
    defaultDbTypeThe type of your Content Data Store database.
    Possible values:
    • MSSQL
    • ORACLESQL
    • DB2
    MSSQL
    defaultDbPortThe port of your Content Data Store database.
    • 1433 for MSSQL
    • 1521 for ORACLESQL
    • 50000 for DB2
    defaultDbNameThe name of your Content Data Store database.none
    defaultDbUserThe name of a database user who can access the Content Data Store database.none
    defaultDbPasswordThe password for that database user.none
    deployTypeThe type of Web application deployment.
    Possible values:
    • Staging
    • Live
    Staging
    distDestinationThe root folder of the DXA Web site.none
    logFolderThe path to the log directory.C:\temp\logs
    logLevelThe level of Content Delivery logging.
    Possible values:
    • DEBUG
    • ERROR
    • INFO
    • TRACE
    • ALL
    • OFF
    • WARN
    ERROR
    NonInteractiveA switch that indicates non-interactive mode:
    Possible values:
    • TRUE
    • FALSE

    none

    siteDomainHeader of the DXA Web site used in configuration files.localhost
    siteLogFileThe full path to the Web site log file.C:/temp/logs/site.log
    sitePortThe port of the DXA Web sitenone
    sitePublicationIdThe Publication ID of the imported 400 Example Site Publicationnone
    sessionDbServerThe server name of your Experience Manager database servernone
    sessionDbTypeThe type of your Experience Manager database.
    Possible values:
    • MSSQL
    • ORACLESQL
    • DB2
    none
    sessionDbPortThe port of your Experience Manager database.
    • 1433 for MSSQL
    • 1521 for ORACLESQL
    • 50000 for DB2
    sessionDbNameThe name of your Experience Manager database.none
    sessionDbUserThe name of a database user who can access the Experience Manager database.none
    sessionDbPasswordThe password for that database user.none
    traceLogFile The full path to the Web site trace fileC:/temp/logs/trace.log
    webNameThe name of the DXA Web site.DXA
    webSiteActionThe action to perform when the Web site already exists, used in conjunction with the NonInteractive switch.
    Possible values (the script prompts you to specify):
    • Recreate—delete the old Web site and create a new one with specified parameters.
    • Preserve—use the existing Web site for Web application deployment: the distDestination, sitePort, and siteDomain parameters will be overwritten with Web site data.
    • Cancel—cancels setup.
    Cancel
    The script creates the Web application.
  5. Install a JDBC driver for your database in the bin\lib\ subfolder of the new Web application (copy the driver from one of your Content Delivery Web applications):
    VendorJDBC DriverRequired JAR
    Microsoft SQL ServerMicrosoft SQL Server JDBC Driver 4.0sqljdbc4.jar
    Oracle

    Oracle JDBC driver 12.1.0.1

    Oracle JDBC driver 11.2.0.3

    ojdbc7.jar

    ojdbc6.jar

    IBM DB2IBM Data Server Driver for JDBC and SQLJ (9.7 GA)db2jcc.jar
  6. Copy a valid content delivery licence file (cd_licences.xml) to the Web application bin\config folder.
  7. Start the Web application.