Foundation System Requirements 12.1.x

Foundation 12.1 Hardware Requirements

  Winshuttle application SharePoint Server SQL Server

Processor

64-bit, 4-core Processor

 64-bit, 4-core Processor 64-bit, quad-core Processor

Memory

For non-production use:

16 GB

For non-production use:

16 GB

For non-production use:

16 GB

For production use:

  • Single Server Farm - 32 GB
  • Multi-Server Farm - 16 GB per Front End

For production use:

  • Single Server Farm - 32 GB
  • Multi-Server Farm - 16 GB per Front End

For production use:

32 GB - for both Single and Multi-Server Farm

Storage

120 GB for system drive

120 GB for system drive

500 GB for system drive

To achieve optimal reliability, performance, and ease of use, Winshuttle recommends the following guidelines for split drives:

• 120 GB System Disk

• 120 GB Temp DB Disk

• 120 GB Log Disk

• 140 GB Data Disk

Network

  • IPV4
  • IPV4
 -

Note: In the non-production setup, Winshuttle applications and SharePoint can be on the same server. In this case, 24 GB RAM is required (provided the server is dedicated to Winshuttle). In case other applications are also hosted on the same server, then 32 GB RAM is required.

Foundation 12.1 Operating System, Database, and TLS Protocol Requirements

Operating System

  • Windows Server 2016
  • Windows Server 2012 R2 (64 bit)
  • Windows Server 2012 (64-bit)

Database

  • Microsoft SQL Server 2017
  • Microsoft SQL Server 2016
  • Microsoft SQL Server 2014 (64-bit)
  • Microsoft SQL Server 2012 R2 (64-bit)
  • Microsoft SQL Server 2012 (64-bit)

Networking

  • SSL
  • TLS 1.0
  • TLS 1.1
  • TLS 1.2

Note:
12.x version of the product is compatible with .Net Framework 4.6.2 as well.
For TLS 1.2 support on SQL Server 2012, SP2 or higher needs to be applied in addition to KB 3052404.
For TLS 1.2 support on SQL Server 2014, KB 3052404 may need to be applied.

Regarding Composer and TLS data connections: ODBC drivers compatible with TLS 1.2 must be installed on any server hosting Composer. After installing the drivers, change any connection strings to use the ODBC driver provider.

OLEDB drivers supporting TLS 1.2 must be installed on any server hosting Composer. After installing the drivers, change any connection strings to use the MSOLEDBSQL provider.
Example: Provider=MSOLEDBSQL;Data Source=MySQLServer;Initial Catalog=MyDatabase;User ID=sa;Password=MyPassw0rd$

Foundation 12.1 Server Roles and Features for SAP Integration Server (SAPIS), Composer, and LMS

General Requirements

SAPIS

LMS

Composer

SAP GUI installed on all SAP Integration Servers N/A N/A

Roles

SAPIS

LMS

Composer

Application Server

.NET Framework 4.5

Windows Process Activation Service

  • HTTP Activation
  • Named Piped Activation
  • TCP Activation

Application Server

N/A

Application Server

N/A

Health and Diagnostics

HTTP Logging

 N/A

Health and Diagnostics

HTTP Logging

Performance

  • Static Content Compressions
 N/A

Performance

  • Static Content Compressions
Security
  • Request Filtering
  • Basic Authentication
  • Static Content Compressions
  • Windows Authentication
 Security
  • Request Filtering
  • Basic Authentication
  • Static Content Compressions
  • Windows Authentication
 Security
  • Request Filtering
  • Basic Authentication
  • Static Content Compressions
  • Windows Authentication

Application Development

  • .NET extensibility 3.5
  • .NET extensibility 4.5
  • ISAPI Extensions
  • ISAPI Filters

Application Development

  • .NET extensibility 3.5
  • .NET extensibility 4.5
  • ASP
  • ASP.NET 3.5
  • ASP.NET 4.5
  • ISAPI Extensions
  • ISAPI Filters

Application Development

  • .NET extensibility 3.5
  • .NET extensibility 4.5
  • ASP
  • ASP.NET 3.5
  • ASP.NET 4.5
  • ISAPI Extensions
  • ISAPI Filters

Management Tools

  • IIS Management Console
 N/A N/A

Features

SAPIS

LMS

Composer

.NET Framework 3.5 Features

  • .NET Framework 3.5
  • HTTP Activation
  • Non-HTTP Activation

.NET Framework 3.5 Features

  • .NET Framework 3.5.1
  • HTTP Activation
  • Non-HTTP Activation

.NET Framework 3.5.1 Features

  • .NET Framework 3.5.1
  • HTTP Activation
  • Non-HTTP Activation

.NET Framework 4.5 Features

  • .NET Framework 4.5
  • ASP.NET 4.5
  • WCF Services
  • HTTP Activation

Windows Process Activation Service

  • Process Model
  • .NET Environment 3.5
  • Configuration APIs

Winshuttle SAP Integration Server 12.1 Requirements

SAPIS 12.1 Account Requirements

Account Purpose Requirements
Setup User account Use to install the SAP Integration Server software
  • Local administrator on the server on which Winshuttle Server will be installed.
  • Dbcreator on the SQL instance containing the databases
  • securityadmin on the SQL instance containing the databases
Application Pool account This account runs the IIS application pool for the SAP Integration Server component. After installation of SAPIS , must provide the execute permission for the ‘SaveAutoRunStatus’ stored procedure of the SAPIS Manager database.
  • Local administrator on server
  • Db_datareader on the SAPIS database (minimum)
  • Db_datawriter on the SAPIS database (minimum)
SQL Server Service account Used to install the Server Database

The following server roles are required on the SQL Server instance in order to install the database:

  • Db_datareader
  • Db_datawriter

SAPIS 12.1 Queue Component Requirements

Note: RabbitMQ and Erlang OTP are installed as part of the Winshuttle SAP Integration Server 12.1 Service Bus installation.

Erlang OTP

Version 21

RabbitMQ

Version 3.7.8

Network Ports

Queue messaging requires Port 5672 and management console requires port 15672 to be open.

Note about ASP.NET Requirement

The Winshuttle Server Manager Component requires ASP.NET to be installed and registered with IIS. To do this, run the following command (as an Administrator) from the .NET Framework 4 installation Directory.

C:\Windows\Microsoft.NET\Framework64\v4.0.30319>aspnet_regiis.exe -iru -enable

SAPIS 12.1 Server Manager, Worker, & LaunchGUI Requirements

  Server Manager Server Worker & LaunchGUI

.NET Framework

.NET 4.5

 .NET 4.5

Operating System
  • Windows Server 2016
  • Windows Server 2012 / 2012 R2
  • Windows Server 2016
  • Windows Server 2012 / 2012 R2

Network Ports

RFC calls require ports 33xx to be open

 N/A

SAP

64-bit version of the "librfc32.dll" file.

This is a CRITICAL requirement.

See Where to get LIBR32FC.DLL for more information.

Note: If SAP Message Server is being used, then you must make the appropriate entry for the message server in the services file for the Winshuttle Server Manager and Winshuttle Server Worker machines.

Where to get LIBR32FC.DLL 

  • The librfc32.dll library can be downloaded from Software Download section of the SAP Support Portal.

    • Note: You will need to log in to the SAP Support Portal/Download pages to be able to download files.

  • The librfc32.dll library is typically placed in the C:\Windows\System directory.

Winshuttle User Governance 12.1 Requirements

User Governance 12.1 Account Requirements

Account name/type Description Requirements

Setup user account (installation account)

Used to run the Foundation User Governance installer and deploy the Winshuttle Foundation User Governance .WSP.

The account used to install User Governance should have the same permissions as the account used to install SharePoint.
  • Membership in the Local administrators group on each server on which Winshuttle Foundation User Governance will be installed.
  • SharePoint Farm Administrator.
  • The installation account also requires the SPDataAccess role on every Content Database and Config Database for SharePoint hosting a Winshuttle site.
  • If you are installing to a SQL 2016 database, the installation account requires the following SQL roles: SecurityAdmin, Public, and DBcreator.

SQL Server service account

Used to install the Winshuttle Foundation User Governance database.
  • dbcreator server role on SQL server instance

Email address

Used as the "From" address for task notifications for Winshuttle Transaction or Winshuttle Query script approvals.
  • An outbound SMTP server
Foundation Web Application and Timer Service Account used to run Web applications and the SharePoint Timer Service.
  • db_owner permission on the User Governance database.

Additional User Governance 12.1 Requirements

SharePoint Web Application

ClosedHelp with this

A SharePoint Web Application is composed of an Internet Information Services (IIS) web site that acts as a logical unit for the site collections that you create. When you create a new web application, you also create a new content database and define the authentication method used to connect to the database.

  • Anonymous Authentication must be enabled

Winshuttle Workflow 12.1 Requirements

Recommendation: Using a Development Server

To minimize the risk of disruption and data loss, Winshuttle strongly recommends installing SharePoint and Winshuttle Workflow on a development (i.e., non-production) server first. Because the development server simulates a server in a real work environment (but operates in isolation), you can create, test, and refine your processes before moving them onto a production server. When you are ready to move to the production server, specify the URL of the production server within Winshuttle Workflow, and publish your workflows and/or forms to that server.

Workflow 12.1 SQL and SharePoint Account Requirements

The following sections include information about how to prepare for your Winshuttle Workflow installation, including system requirements, development server, authentication, and accounts details.

Authentication

Winshuttle Workflow requires authentication to access a database and impersonate a system user with sufficient privileges to access the SharePoint Object Model. This is in addition to normal user authentication during SharePoint login.

To give Winshuttle Workflow the authentication it requires, there are two options:

  • SharePoint Object Model Access, which requires Windows authentication.
  • SQL Server Access, which requires either Windows authentication or SQL Server authentication.

What accounts do I need?

To deploy Winshuttle Workflow, you can provide up to 2 accounts and 1 email address:

  • Workflow Admin Account: Communicates with SharePoint and runs the Workflow Central Administration site. This account is also used to run SVservice.
  • Workflow Database Account: Manages the Workflow database.

The following tables provide a summary of accounts and required permissions.

Workflow 12.1 Service Account Requirements

SharePoint 2016

Database SQL Role

SharePoint Content Database

SPDataAccess

SharePoint Configuration Database

SPDataAccess

Workflow 12.1 SharePoint Account Requirements

Domain Account Local server groups SharePoint Access

Winshuttle Workflow Admin account
  • Administrators
  • wss_admin_wpg
  • wss_wpg

Note: Ensure the Workflow Administrator account is a member of these groups on every web front end.
  • Owner group at the root site
  • Owner group for the site collection that contains Workflow sites

-or-

  • Site Collection Administrator for root site
  • Site collection administrator for the site collection that contains Workflow sites.

Composer 12.1 System Requirements

Winshuttle Composer is an HTML 5, browser-based program that connects to a SharePoint instance where Winshuttle Workflow is installed.

Installation Recommendation: It is recommended that you install Composer in each Winshuttle Environment within your landscape. Minimally, you should have a Non-Production instance and a Production instance of Composer installed.

Supported Browsers

  • To run Composer and develop solutions: IE11, Microsoft Edge, Google Chrome, Mozilla Firefox.
  • To run forms created in Composer: IE11, Microsoft Edge, Google Chrome, Mozilla Firefox.

Server Requirements

Note: If you use a host header, you will need to create a DNS entry.

  • IIS 7.5, 8.0, 8.5, 10.0
  • .NET 4.5.x, and 4.6.x
  • Winshuttle Workflow 10.7
  • Microsoft SharePoint 2016 | 2013

    Note: SharePoint and Winshuttle Workflow are required for publishing forms, but do not need to be installed on the same server where Winshuttle Composer is installed.

LMS Requirements

LMS Version Compatibility

LMS Version Supported installation type Supported Winshuttle clients
11.0 Standalone version Winshuttle Studio 10.7, Hotfix 2
11.1.x Foundation (bundled version) Winshuttle Studio 11.1.x
11.2.x Foundation (bundled version) Winshuttle Studio 11.2.x
11.2.12 Foundation (bundled version) Winshuttle Studio 11.2.12
11.3.0 Standalone version Winshuttle Studio 11.3.0
11.4.0 Foundation (bundled version) Winshuttle Studio 11.4.0
12.x Foundation (bundled version) Winshuttle Studio 12.x
12.1 Standalone version Winshuttle Studio 12.1.x

LMS Server Requirements

Operating System

  • Windows Server 2016
  • Windows Server 2012 R2 (64-bit)
  • Windows Server 2012 (64-bit)

Database

  • Microsoft SQL Server 2017
  • Microsoft SQL Server 2016
  • Microsoft SQL Server 2014 (64-bit)
  • Microsoft SQL Server 2012 R2 (64-bit)
  • Microsoft SQL Server 2012 (64-bit)

Minimum database size of 500MB is recommended

Other software

  • .NET Framework 4.5
  • IIS 7.5, 8.0, 8.5, 10.0

LMS Account Requirements

The account used to install the LMS should have the following permissions:

  • Administrator permissions on the target system.
  • dbcreator on the SQL server where the LMS database will be created.
  • securityadmin on the SQL server where the LMS database will be created.

Note:

  • If you are using a custom identity (such as an Active Directory user), the custom identity must be a member of  "Log on as a service policy."
  • The Winshuttle Administrator account specified at the end of installation is required to be a Winshuttle Foundation site collection administrator.

IMPORTANT: Registering ASP.NET with IIS

On occasion the latest .ASP version is not registered with the LMS host machine/VM. The Requirements check performed during installation will not detect this. (The installation will still complete successfully, but the LMS site will not be accessible.)

To avoid this, do the following:

  1. Open a command prompt as an administrator.
  2. Change to the directory where the .NET framework is installed (for example, C:\Windows\Microsoft.NET\Framework\v4.0.30319).
  3. Run the following command: aspnet_regiis.exe -iru

    NOTE: If you have already installed the LMS and .ASP.NET was/is not registered with IIS, you will need to register ASP.NET with IIS, and then re-install the LMS.

Microsoft Azure Requirements (SKUs)

Microsoft SharePoint (Winshuttle User Governance and Winshuttle Workflow)

The minimum hardware requirements for the Foundation components to perform as expected are listed below. Due to the nature of the Azure VM SKUs, and the optimization of SKUs for certain tasks, the minimum recommendation in Azure is to use the D4S_V3 SKU for these two servers (UG and Workflow) in the production environment.

  • 2 Windows Server 2016 machine (64 bit)
  • Quad Core Processor
  • 32 GB RAM
  • 120 GB Hard Disk

Winshuttle Application Servers (LMS, SAPIS, and Composer)

The minimum hardware requirements for the Foundation components to perform as expected are listed below. Due to the nature of the Azure VM SKUs, and the optimization of SKUs for certain tasks, the minimum recommendation in Azure is to use the D4S_V3 SKU for these two servers in the production environment.

  • 2 Windows Server 2016 machine (64 bit)
  • Quad Core Processor
  • 32 GB RAM
  • 120 GB Hard Disk

SQL Mirroring

The minimum hardware requirements for the Foundation components to perform as expected are listed below. Due to the nature of the Azure VM SKUs, and the optimization of SKUs for certain tasks, the minimum recommendation in Azure is to use the E4S_V3 SKU for these two servers in the production environment.

  • 2 Windows Server 2016 machine (64 bit)
  • Quad Core Processor
  • 32 GB RAM
  • 500 GB Hard Disk

Note: Microsoft SQL Server Always On is supported.

Backup Recommendations

Winshuttle recommends a daily backup of the following databases. When hosted in Azure, it is recommended that the backups are stored in a geo-replicated blob-storage.

  • SharePoint Config Database
  • SharePoint Content Database(s)
  • Winshuttle User Governance Database
  • Winshuttle Workflow Database
  • Winshuttle Licensing Database
  • Winshuttle Reporting Database
  • Winshuttle SAPIS Manager Database
  • Winshuttle SAPIS Worker Database
  • Winshuttle SAPIS Launch GUI Worker Database

Note: The preceding databases should be mirrored in the SQL cluster.