View Categories

SLM Windows On-Premise Installation Guide

SLM Windows on-premise installation provides organizations with the option to deploy Safety Lifecycle Manager within their own Windows Server environment. SLM is an enterprise web application that uses supporting technologies including IIS, Microsoft SQL Server, PHP and Memcached.

An installation can use a dedicated application server or a shared database and application server, with infrastructure requirements varying according to the deployment model.

This guide covers the complete SLM Windows on-premise installation workflow demonstrated in the training, from infrastructure preparation through IIS, SQL Server and PHP configuration to SLM deployment, Memcached and background-task scheduling.

SLM Windows On-Premise Installation Overview

An SLM Windows on-premise installation consists of several infrastructure and application components that must be configured to work together.

The installation process demonstrated in the training covers seven principal stages:

  1. Confirm system infrastructure requirements.
  2. Install and configure IIS.
  3. Install and configure Microsoft SQL Server.
  4. Install and configure PHP.
  5. Install and configure SLM.
  6. Configure Memcached.
  7. Configure Windows Task Scheduler.

Completing these stages establishes the web server, database, application runtime, SLM files, caching service and recurring background processing required by the demonstrated Windows deployment.

Before beginning an installation, review the SLM On-Premise Hardware and Software Requirements guide for the wider infrastructure requirements associated with an on-premise deployment.

SLM Windows On-Premise Installation Requirements

SLM can be deployed using either a dedicated application server or a shared database and application server. The minimum infrastructure requirements demonstrated in the training differ according to the selected architecture.

For a dedicated server, the training identifies:

  • 4–8 CPU cores
  • 8 GB RAM
  • 120 GB disk space
  • Current Windows Server release

For a shared database and application server, the training identifies:

  • 4–8 CPU cores
  • 16 GB RAM
  • 1 TB disk space
  • Current Windows Server release

The training also recommends a dedicated access URL, access to DNS where required, an SSL/TLS certificate for secure data transmission and access to an SMTP delivery or relay service.

These figures reflect the minimum requirements presented in the SLM training. Actual infrastructure sizing should account for the requirements of the specific deployment.

Installing and Configuring IIS for SLM

The IIS stage of an SLM Windows on-premise installation prepares Internet Information Services to host the application and its supporting web components.

The training installs the Web Server (IIS) role through Windows Server Manager and enables the required supporting features.

These include features across several IIS categories:

  • Common HTTP features
  • Health and diagnostics
  • Performance
  • Security
  • Application development
  • Management tools

The demonstrated configuration includes HTTP Redirection, Logging Tools, Request Monitor, Static Content Compression, Request Filtering and authentication features.

Application-development components include the required .NET extensibility and ASP.NET features together with CGI, ISAPI Extensions and ISAPI Filters.

IIS Management Console and Management Scripts and Tools are also enabled.

After IIS has been installed, the training installs PHP Manager for IIS so that PHP can subsequently be registered and configured within the web-server environment.

Installing SQL Server and SLM Databases

SQL Server is a core part of the SLM Windows on-premise installation because it provides the database environment supporting the SLM application.

The training demonstrates installing SQL Server with Database Engine Services and configuring the database engine using the required collation and authentication settings.

SQL Server Management Studio is then installed to provide the administration interface used for the remaining database configuration.

Once SQL Server is available, the three supplied SLM database backups are restored:

  • Cluster
  • Master
  • Revision

The required SLM database logins and users are then created using scripts supplied with the installation documentation. Those scripts are also used to assign the required permissions across the three databases.

Finally, the Cluster database paths are updated to reflect the location in which the SLM application has been installed.

For a more focused explanation of these procedures, see the SLM Database Configuration Guide.

Installing and Configuring PHP

PHP provides the application runtime required by the SLM Windows on-premise installation and should use the compatible version supplied or specified for the SLM release being installed.

The training specifically advises against independently downloading an arbitrary PHP version because it may not be compatible with the SLM software.

The supplied PHP package is extracted into the required Windows directory and its location is added to the Windows system PATH environment variable.

The required Microsoft Visual C++ runtime is also installed before PHP operation is verified from Command Prompt.

Once PHP and IIS are available, PHP is registered through PHP Manager for IIS.

The training then configures several runtime limits, including:

  • Post size
  • Maximum upload size
  • Execution time
  • Memory limit

The required PHP extensions are enabled according to the SLM installation documentation, while unnecessary extensions are disabled.

FastCGI settings are also configured, including the required activity, idle and request timeouts.

API Handler Mappings and SSL

Where the SLM API is installed, additional IIS handler configuration is required.

The training demonstrates editing the PHP handler mapping and adding the PUT and DELETE HTTP verbs required for API operations.

If SSL is being used, the server certificate is imported into IIS using the appropriate PFX certificate file and password.

The certificate can subsequently be selected when the HTTPS binding is created for the SLM website.

For more information about the application programming interface after installation, see the SLM API Usage Guide.

Installing SLM During a Windows On-Premise Installation

After the supporting server components have been prepared, the SLM application package can be installed.

The supplied installation archive contains the application files required by the deployment. Depending on whether the API is included, the package may contain the code base, application stack and API components.

The training demonstrates extracting these files and placing them within an SLM directory on the Windows server.

A new website is then created in IIS with its physical path pointing to the SLM web root.

Virtual directories are created for the required Libraries and Resources folders.

If HTTPS is being used, an HTTPS binding is added using the appropriate hostname and installed SSL certificate.

Where the API is included, additional IIS applications are created for the API itself and its documentation.

Configuring the SLM Environment File

The SLM Windows on-premise installation uses an environment file to define deployment-specific application settings, including hosts, authentication, database connections, caching and email configuration.

The training demonstrates configuring values including:

  • Production or development environment
  • Website hostname
  • API hostname
  • Client code
  • SLM instance identifier
  • SSL status
  • Cache configuration
  • Authentication mode
  • Email configuration
  • Database configuration
  • PHP executable path
  • SMTP configuration

The SLM instance identifier is obtained from the appropriate record in the Cluster database.

Authentication can also be configured according to the deployment, with the training discussing local accounts, SAML and Active Directory as available approaches.

Database connection values identify the SLM databases, SQL Server host and the application, administration and SSRS database accounts.

For the SMTP-specific variables, see the SLM SMTP Configuration Guide.

Configuring Minify and File Permissions

After the environment file has been configured, the training updates the SLM Minify configuration to reflect the installed application paths.

The required paths include the Minify cache location, document root and Libraries directory.

The appropriate Windows permissions must then be assigned so that the IIS accounts can access and write to the required SLM folders.

The training applies these permissions to the Code Base and App Stack directories and, where the API is installed, to the API directory as well.

These permissions are deployment-sensitive and should be applied according to the SLM installation documentation and the security requirements of the environment.

Setting Up Memcached for SLM

Memcached forms part of the SLM Windows on-premise installation by providing the caching service used by SLM to support application performance.

The Windows installation demonstrated in the training uses files and commands supplied as part of the SLM installation documentation.

An elevated Command Prompt is used to create the Memcached scheduled task and start the caching process.

The supplied controls can also be used to stop Memcached or remove its scheduled task when required.

Because the exact commands are supplied with the installation package, administrators should use those deployment-specific instructions rather than recreating the commands manually.

For additional information, see the SLM Memcached Maintenance Guide.

Configuring Windows Background Tasks

The final stage demonstrated in the SLM Windows on-premise installation is configuring Windows Task Scheduler for recurring SLM background processing.

A scheduled task is created using the System account and configured to run with the required privileges.

The demonstrated trigger repeats every minute indefinitely. Its action runs the configured PHP executable and passes the SLM application path and required processing parameters.

The task conditions and settings are then configured to support continuous background processing.

This operating-system task provides the recurring mechanism used to check and process SLM background work.

For details about application-level scheduling, queue monitoring and queue recovery, see the SLM Background Task Manager Guide.

Reviewing the SLM Windows On-Premise Installation

After completing the SLM Windows on-premise installation, administrators should review the major components before treating the environment as ready for use.

The review should confirm that:

  • The Windows Server environment meets the required infrastructure specification.
  • IIS and the required features are installed.
  • SQL Server and SQL Server Management Studio are available.
  • The Cluster, Master and Revision databases are restored and configured.
  • The supported PHP version is installed and registered with IIS.
  • The required PHP extensions and FastCGI settings are configured.
  • The SLM website, virtual directories and optional API applications are configured in IIS.
  • The SLM environment and Minify configuration files contain the appropriate deployment values.
  • Required Windows file permissions have been applied.
  • Memcached is configured and available.
  • The SLM background task is configured in Windows Task Scheduler.

The exact software versions, configuration values, credentials, paths and supplied scripts should always correspond to the SLM release and customer environment being installed.

Microsoft’s IIS architecture documentation provides additional technical background on the Windows web-server platform. SLM-specific installation requirements should continue to follow the MSS installation package and documentation.

Please complete the form below

Please complete the form below.

You will automatically be forwarded to a demonstration video