Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 9 Next »

1       Introduction

This document is intended for technical staff installing Signifikant Platform on a Windows 2016 server (or later).

A good practice is to change background color of Production server to solid blue to make it different from Test and Staging servers.

2       Installation

2.1              .Net Framework

Install Microsoft Framework 4.7 or 4.8.

Some operating systems will need a configuration of .NET Framework according to below. Please check if these settings are available in your environment and if so, turn on features below. Make sure to check the HTTP activation for the version of .NET you are running.

2.2              SQL Server

Install SQL Server as database engine on Manager Server and Web Server.

  • Manager Server will need access to

    • A database engine for the editorial database. An SQL Server hotel on a separate server may be used.

    • A database engine used for temporary databases during publication. An SQL Server installed locally will be needed.

  • Web Server will need access to a database engine installed locally.

  • If Express edition is used, the instance name does not have to be changed.

  • If non Express edition is used, make sure to name the database instance. This name will be referred to in the configuration.

Install SQL Management studio.

2.3              IIS

Activate server role: Web Server (IIS).

2.4              ASP.NET i IIS7

Activate ASP.NET in IIS7 by adding roles to the server.

 

Same information from a Windows 2012 server, the feature installation confirmation window:

Still need of support of IIS6 metabase

Installing applications to IIS require components installed with IIS6 metabase. Enable and install the component.


2.5              Applikations pool

Defined chosen application pool to be run by ”LocalSystem” to make it a privileged process with administrator access to databases and files. It may be that it will be defined using AppPoolIdentity.

For versions prior to 4.2.3

Set that the applications pool will use 32 bit applications since it will refer .Net Framework 4.5.x.

For version 4.2.3 and later

Set that the applications pool will use 32 bit applications during the installation. After the installation reset Enable 32-Bit application to false.

Also select LocalSystem for application pool login, a suitable session timeout and select to Suspend the application, rather then Terminate it to reduce startup time after idle time out.

For version 5.1 and later

Disable 32 bit applications for applications. Signifikant Server and Web-application performs better when run in 64-bit application pools.


Activate ASP.NET service set it to start automatically. The service is needed to support user session data in a state server.


Also check that there is no automatic recycling of the default application pool which may interfere with usage, import or publication.

2.6      Windows Search

Free text search in Pdf and HTML files are implemented with the Widows Search service. When installing on a Windows Server ensure that the service installed.

2.6.2        Server 2016 and later

Windows Search Service in Server 2012 is found in Server Manager> Features > Windows Search.

  • Start Server Manager.

  • Click Manage, and then click Add Roles and Features

  • On the Before You Begin page, click Next

  • On the Installation Type page, select Role-based or Feature-based Installation, and then click Next

  • On the Server Selection page, select the server or virtual hard disk on which to install Windows Search Service

  • On the Features page, select Windows Search Service, and then click Next

  • On the Confirmation page, verify that Windows Search Service is listed, and then click Install

2.7              Connectivity

Connectivity between Manager Server and Web Server(s) using http(s) port 80/443 is required.

3       Access

Signifikant will need access rights and credentials to access the server and SQL Server/Management Studio in order to perform installations and deliver support. Make sure to provide the needed security tools and credentials.

4       Operational aspects

Operational aspects not covered in guides. Procedures need to follow client’s standard operating procedures. Ensure the following is covered by client’s standard operating procedures:

  • Adequate backup

  • Monitoring of SQL and IIS worker process

  • Virus protection and IT-security setup

  • Ensure client has a test environment

  • Ensure client understands down time procedures

  • Organisation for handling incidents and changes



  • No labels