Installing the CDA Web Server

This page includes the following:

Installation Steps

Installing the CDA Web Server Application » Configuring IIS for CDA » Configure the Web Application - Customer.Config » Configure the Web Application - Web.Config

Installing the CDA Web Server Application

  1. Verify that the following roles and features are installed:

    Features

    • .NET Framework 3.x Features
      • .NET Framework 3.x (includes .NET 2.0 and 3.0)
      • HTTP Activation
      • Non-HTTP Activation
    • .NET Framework 4.x Features (4 of 7)
      • .NET Framework 4.x
      • ASP.NET 4.x
      • WCF Services (2 of 5)
        • HTTP Activation
        • TCP Port
    • Windows PowerShell (3 of 5)
      • Windows PowerShell 4.0
      • Windows PowerShell 2.0 Engine
      • Windows PowerShell ISE
    • Windows Process Activation Service
      • Process Model
      • .NET Environment
      • Configuration APIs
    • WoW64 Support

    Roles

    • Web Server (IIS) (16 of 43)
      • Web Server (15 of 34)
        • Common HTTP Features (5 of 6)
          • Default Document
          • Directory Browsing
          • HTTP Errors
          • Static Content
          • HTTP Redirection
        • Health and Diagnostics (1 of 6)
          • HTTP Logging
        • Performance (1 of 2)
          • Static Content Compression
        • Security (1 of 9 installed)
          • Request Filtering
        • Application Development (7 of 11)
          • .NET Extensibility 3.x
          • .NET Extensibility 4.x
          • ASP.NET 3.x
          • ASP.NET 4.x
          • ISAPI Extensions
          • ISAPI Filters
          • WebSocket Protocol
      • Management Tools (1 of 7)
        • IIS Management Console

      Note: The version numbers may vary depending on your operating system.

  2. Copy the WebUI folder to IIS.

    Note: Default location: C:\Inetpub\wwwroot\

  3. Allow the IIS_IUSRS user for full control for the logs and StateFiles.
  4. Check the configuration of IIS. See: Configuring IIS for CDA including HTTPS and the recommended IIS Application Initialization settings.

Configuring IIS for CDA

  1. Inside the IIS Manager, right-click Default Websites and select Add Application.
  2. Choose an alias (for example: "CDA"). This is used to define the URL to open the application.
  3. Set the application pool to use ASP.NET in a previously installed version. Keep in mind the General Requirements for Installing the CDA Server
  4. Select the physical path where you have copied the web application to.

    • Alias

      Example value: CDA

    • Application pool

      Example value: ASP.NET v4.5

    • Physical path

      Example value: C:\inetpub\wwwroot\WebUI

Note: The application pool can only contain one single worker process (Web Garden is not supported). You can set the Maximum Worker Process to 1 in the Process Model pane (Actions pane > Advanced Settings > Process Model > Maximum Worker Processes).

Configure HTTPS

To ensure that all communication from and to CDA is encrypted, an HTTPS binding has to be established in the IIS Manager.

Note: If you want to roll out the application without HTTPS bindings, you will need to change the system.serviceModel element in the web.config. See Configuring HTTPs Endpoints for CDA.

To Configure HTTPS

  1. Inside the IIS Manager, right-click the Default Web Site and select Edit Bindings...
  2. Click Add to add a new binding.
  3. Select the https type and your SSL certificate from the corresponding drop-down lists.

    Notes:

Recommended IIS Application Initialization Settings

To keep the instance active at every time, the IIS Application Initialization Module sets the setting to AlwaysRunning .

Note: All workflow executions require an active instance. Especially for planned workflow executions, it is vital to have the instance active during the scheduled time window, otherwise the workflow execution fails.

IIS 8 and Higher

Add the Application Initialization as Windows feature, as described in www.iis.net/learn/get-started/whats-new-in-iis-8/iis-80-application-initialization.

Configure the Web Application - Customer.Config

Tip: Save the Customer.Config in the following folder: C:\Automic\Release.Manager\WebUI

Important! You do not need to make any changes in the customer.config file in order to set up the system. The First-Time CDA Setup screen will guide you through the steps to configure the DB and Automation Engine connections.

To know how to configure the customer.config see: Configuring CDA via Customer.Config File

Configure the Web Application - Web.Config

To Configure HTTPS Endpoints for CDA

By default, CDA only enables HTTP endpoints. To use HTTPS endpoints, open the web.config file and make sure the following <endpoint> sections in the <system.serviceModel> (in bold) are enabled:

<system.serviceModel>

<bindings>

<basicHttpBinding>

<binding name="DeploymentServiceBinding" maxReceivedMessageSize="20000000" maxBufferPoolSize="20000000" maxBufferSize="20000000" messageEncoding="Text" sendTimeout="00:05:00" receiveTimeout="00:05:00">

<security mode="Transport" />

<readerQuotas maxDepth="200" maxStringContentLength="20000000" maxArrayLength="16384" maxBytesPerRead="20000000" maxNameTableCharCount="16384" />

</binding>

<binding name="DeploymentServiceBindingNoSec" maxReceivedMessageSize="20000000" maxBufferPoolSize="20000000" maxBufferSize="20000000" messageEncoding="Text" sendTimeout="00:05:00" receiveTimeout="00:05:00">

<security mode="None" />

<readerQuotas maxDepth="200" maxStringContentLength="20000000" maxArrayLength="16384" maxBytesPerRead="20000000" maxNameTableCharCount="16384" />

</binding>

</basicHttpBinding>

</bindings>

<behaviors>

<serviceBehaviors>

<behavior name="Ventum.Bond2.Web.Service.DeploymentServiceBehavior">

<serviceMetadata httpGetEnabled="true" httpsGetEnabled="true" />

<serviceDebug includeExceptionDetailInFaults="true" />

</behavior>

<behavior name="Ventum.Bond2.Web.Service.IntegrationServiceBehavior">

<serviceMetadata httpGetEnabled="true" httpsGetEnabled="true" />

<serviceDebug includeExceptionDetailInFaults="true" />

</behavior>

</serviceBehaviors>

</behaviors>

<services>

<service behaviorConfiguration="Ventum.Bond2.Web.Service.DeploymentServiceBehavior" name="Ventum.Bond2.Web.Service.DeploymentService">

<endpoint address="" binding="basicHttpBinding" contract="Ventum.Bond2.Services.Deployments.IDeploymentService"bindingConfiguration="DeploymentServiceBinding">

<identity>

<dns value="localhost"/>

</identity>

</endpoint>

<endpoint address="" binding="basicHttpBinding" contract="Ventum.Bond2.Services.Deployments.IDeploymentService" bindingConfiguration="DeploymentServiceBindingNoSec">

<identity>

<dns value="localhost" />

</identity>

</endpoint>

<endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />

</service>

<service behaviorConfiguration="Ventum.Bond2.Web.Service.IntegrationServiceBehavior" name="Ventum.Bond2.Web.Service.IntegrationService">

<endpoint address="" binding="basicHttpBinding"contract="Ventum.Bond2.Services.Integrations.IIntegrationService" bindingConfiguration="DeploymentServiceBinding">

<identity>

<dns value="localhost"/>

</identity>

</endpoint>

<endpoint address="" binding="basicHttpBinding" contract="Ventum.Bond2.Services.Integrations.IIntegrationService" bindingConfiguration="DeploymentServiceBindingNoSec">

<identity>

<dns value="localhost" />

</identity>

</endpoint>

<endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />

</service>

</services>

</system.serviceModel>

To Enable Net 4.8 in the web.config file

To enable Net 4.8 in the web.config file, enhance the httpRuntime entry as follows:

Example: <httpRuntime targetFramework="4.8" executionmaxRequestLength="204800" executionTimeout="360" requestValidationMode="2.0" />

Important! You can verify if the https configuration has been set correctly by accessing the deployment service. Example: https:/sample/Service/DeploymentService.svc

Next step:

Installing the Plug-In for AWI