Skip to main content

Step 1: Preparation

This step provides information about what you need to do to prepare for the installation of SigmafineHub.

Check requirements​

Before proceeding with the installation:

Open the Required Ports​

  • Verify with your IT Administrator that port 443 is open and accessible.

    Your SFHub Application Server uses this port to communicate with all the SF Web Applications.

  • Verify with your IT Administrator that a TCP port for the use of the SFHub application server Web Socket (default 18666) is available. Your SFHub Application Server uses this port to communicate with all the SF Web Applications.

    If port 18666 is not available, a different one can be assigned during the installation process.

  • Verify with your IT Administrator that a TCP port for the use of the SFHub Inter Process Communication (default 8090) is available. Your SFHub Application Server uses this port to communicate with the SFHub services running on the same SFHub Application Server.

    If port 8090 is not available, a different one can be assigned during the installation process.

Enabling Ports Firewall​

Check your firewall configuration to ensure that all ports are enabled. You will eventually change or define rules to enable the communication according to the following requirements:

  • SFHub Web Site port (443) -- Enable inbound and outbound communication.

  • SFHub Web Socket port (18666) -- Enable inbound and outbound communication.

  • SFHub IPC port (8090)-- Enable the inbound communication only.

Software Installation​

  • Prepare the SFHub Application Server; installing required software and configuring it properly using the following instructions. If SQL Server is not installed, please install it.

    During the installation you will be required to connect to the SQL Server

Microsoft SQL Server​

  • SFHub Application Servers require Microsoft SQL Server 2008 R2 or above. (Standard, Enterprise and Express version are all supported.)

  • During the installation you will be required to select how to create or update the SFHub SQL server database:

    • Managed by the installer
    • Manual creation or update

    Managed by the installer

    If you select this option, you will be required to connect to the SQL Server instance to create and configure the SFHub database. The installation supports both Windows and SQL Server Authentication.

    If you are planning to use the SQL Server Authentication:

    • Ensure that you have a SQL Server user with Admin rights that you can use during the installation. If not, you will need to create one.

    • If you are planning to use the Windows Authentication:

      1. Ensure that the SQL Server security setting allows SQL Server and Windows Authentication.

        To verify this setting:

        1. In SQL Server management Studio, right-click on your instance and choose Properties.
        2. Select the Security page.
        3. In Server Authentication, select SQL Server and Windows Authentication.

      2. Configure the Windows User that will run the installation as an Admin of the SQL Server.

    Manual creation or update

    If you select this option, you will be required to:

    1. Download the SQL Script from the SFHub installer.

    2. Execute it on your SQL Server Instance.

    3. Confirm the creation on the installer. It will then check if the database created is consistent.

Microsoft OLEDB Driver for SQL Server​

The SigmafineHub application server and its annexed setup kit uses the Microsoft OLEDB driver installed on the designated Windows server. Whenever you plan to install SigmafineHub on a Windows Server where the Transport Level Security 1.2 (or TLS 1.2) is enabled and TLS1.0 is disabled, you are required to have the Microsoft OLEDB provider MSOLEDBSQL installed on the system.

Please refer to the link below to download the MSOLEDBSQL driver.

https://www.microsoft.com/en-us/download/details.aspx?id=56730

Note

The missing installation of the above driver when TLS 1.2 is enabled, and TLS 1.0 is disabled could results in a failure of the SFHub installation.

.NET Framework 4.8​

  • In case your SFHub Application Server does not have .Net Framework 4.8 installed, please install it.

PI AF Client 2.9.5 or 2.10.9​

  • SFHub Application Server requires PI AF SDK 2.9.5 or 2.10.9. If not installed, please install it.
  • If the SFHub Application Server is installed on the same computer as the SF Server (PIAF Server), please ensure that the PI AF Client 2.9.5 or 2.10.9 is also installed.

PI SDK (Optional)​

  • In case you need to connect SFHub to a Sigmafine server where the configured plug-ins are that use the \'PI SDK\' (for example IMM tank monitoring), we recommend you install the PI SDK on the SFHub server. The version of the PI SDK to be installed must be the same version installed on the Sigmafine Server.

HTTP Rewrite for IIS​

  • The SFHub Application Server requires HTTP Rewrite for IIS

    The installation procedure automatically takes care of this, unless you are running on Windows Server 2008 R2. If running on Windows Server 2008 R2, you need to manually install HTTP Rewrite for IIS.

    To install HTTP Rewrite for IIS:

    1. Download HTTP Rewrite for IIS from the Microsoft web site.
    2. Follow Microsoft\'s instructions for installing it.

Server Roles and Features​

Before proceeding with the installation, we recommend that you install server roles, features, and role services on the SFHub Application Server. For more information, see the Microsoft article "Roles, Role Services, and Features".

Note

The Web Server role must be enabled prior to running the SFHub installation kit.

  1. In Microsoft Server Manager, click Add roles and features to open the wizard and choose Role-based or feature-based installation as the installation type.

  2. On the Select server roles page of the wizard, select the roles appropriate for your operating system:

    Operating SystemRoles
    Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2Basic authentication and Web Server (IIS) Ensure that WCF Services are selected (.NET 4.5)
    Windows Server 2016Basic authentication and Web Server Ensure that WCF Services are selected (.NET 4.5)

  3. On the Select features page, choose the required server features.

  4. Windows Process Activation Service.

    • Process Model
    • Configuration APIs

  5. On the 'Select role services' page for Web Server Role (IIS), select at least the minimum role services listed below:

    Role ServicesRequiredRecommended
    Common HTTP FeaturesStatic Content
    Default Document
    HTTP Redirection    		HTTP Errors
    HTTP Activation
    PerformanceStatic Content Compression
    Dynamic Content Compression    		None
    SecurityWindows Authentication
    Request Filtering    		IP and Domain Restrictions
    ApplicationWindows Server 2012 and later:
    - .NET Extensibility 4.5/4.6
    - ASP.NET 4.5/4.6

    Windows Server 2008 R2:
    - .NET Extensibility 3.5
    - ASP.NET / ASP.NET 3.5    		ISAPI Extensions
    ISAPI Filters
    Management ToolsNoneIIS Management Console (Not applicable for the Server Core minimal installation option in Windows Server 2012 and later)

    IIS Management Scripts and Tools

    Management Service

  6. On the Confirmation page, click Install.

SSL (Secure Socket Layer) access​

  • You are required to enable both Transport Layer Security (TLS) and Secure Sockets Layer (SSL) for your SigmafineHub website, to encrypt your communications over HTTPS.

  • To fully secure access to SigmafineHub, use a digital certificate obtained from a trusted third-party registrar. The installation program can create a self-signed certificate.

  • By default, during a new installation, SigmafineHub will configure the IIS website designated for SigmafineHub to use HTTPS.

    Note

    We recommend you use a certificate obtained from a trusted registrar and have it available before installing the SFHub.

    The self-signed certificate works properly during the installation.

  • Remember to open port 443

Disable FIPS Mode​

SigmafineHub Application Server uses a cryptography algorithm that is not consistent with FIPS (Federal Information Processing Standards). Whenever FIPS is enabled on the Windows Server hosting SigmafineHub, it does not allow the SFHub application server to work properly.

FIPS mode can be disabled from Administrative Tools > Local Security Policy > Local Policies > Security Options, select the policy System Cryptography: use FIPS compliant algorithms for encryption, hashing, and signing and disable it.

Create a service account for SFHub​

  • The SFHub Application Server requires a dedicated service account (it has to be a domain account).

    Create this account on the domain controller with Active Directory Users and Computers.

  • The Name of the service account should be SFHubService

Last updated on