This article lists the recommendations on the software and hardware specifications in order to seamlessly use the FORM's Data Collection Platform for your business needs.
Follow these recommendations to keep the application stable and secure.
The FORM Data Collection Platform maybe deployed on a single server with minimum requirements including an operating system with the Java runtime, an application server and the database server installed on it.
For security and performance reasons, we recommend using a web server that would route the traffic to the application.
Some of the application functions require SMTP servers to distribute emails, resolve domain names, validate email addresses, etc.
Although all of the system components may be installed on a single physical server, it is highly recommended to have both the database server and the web server (if used) deployed on some separate physical hardware.
|Operating system||any 64-bit OS compatible with Oracle Java (JDK) 11.0.3|
|Web server (optional)||Apache HTTP server 2.2 or higher, IIS 10|
MS SQL Server 2019
|Additional software||one or more SMTP server, DNS server|
The choice of the hardware required to run the FORM Data Collection Platform largely depends on anticipated amount of system activity (e.g. number of respondents, forms, reports and forms/reports complexity), as well as, the maximum number of concurrent requests that the system may experience during the peak hours.
Hardware requirements outlined below correspond to the minimal hardware setup required to get the system running while collecting a few thousands of form submissions daily.
If firewalls or any other software or hardware installed prevent the Platform from being able to communicate with the required services (such as databases, NS servers, SMTP servers, etc.) or from being accessed by users, such hardware and software should be configured before the installation.
If the web server is being used, the communication between the application and the web servers should be allowed as well.
12GB minimum is sufficient for most use cases; the systems where high load is expected may require more memory.
|HDD||We recommend to install the Platform on a system where RAID is preconfigured. Two SCSI or SAS drives with 148GB capacity configured as a RAID 10 or an external RAID system are recommended.|
200GB allocated for the database is sufficient in most use cases. However, the more data is collected through the platform, the more disk space is required.
We recommend to plan the extensions of disk space if large volumes of data are going to be collected using the Platform. We also recommend to reserve space or replication and backups in the production systems.
|Network Connectivity||At least one dedicated IP address.|
The detailed requirements will be provided in the installation instructions shipped with the installation package. Please read these instructions carefully before rolling out the application.
Typically, FORM delivers its self-hosted solutions as a custom package, with the software configuration and the installation instructions provided according to the unique environment configuration that customers may have.
However, delivering such a custom deployment package may take some time needed to put together the package and compile the proper installation instructions.
The FORM’s Data Collection platform is also available in pre-configured installation packages, which are readily available for certain environment configurations. They can be delivered much faster than a custom package build.
The FORM’s Data Collection Platform installation packages are currently available for the following configurations and platforms:
Microsoft Windows-based system
Web Server (optional): Microsoft IIS 10
Operating System for Application server: Microsoft Windows Server 2019
Application Server: Apache Tomcat 9
Database: Microsoft SQL Server 2019
Web Server (optional): Apache Web Server 2.2
Operating System for Application Server: Linux (Red Hat enterprise Linux is recommended)
Application Server: Apache Tomcat 9
Database: MySQL 8
Packages include: application binaries, configuration templates, database data structures, initial installation data, instructions and the manual for the installation. All files are compressed and available for downloading per request.
For all other systems configurations, FORM will provide a custom deployment package, with optimized configuration settings and detailed installation instructions.
Form.com and Key Survey applications can be configured to allow the Single Sign-On via SAML 2 using Service Provider (SP) initiated POST binding scheme. (http://en.wikipedia.org/wiki/SAML_2.0#HTTP_POST_Binding).
This document describes the configuration settings in the application and on the Identity Provider side that should be made to make SAML Single Sign On possible.
Please note that when SAML is used, the user must exist in the application database. So before the user may authenticate, a user record must be created in the application with the User Login matching the User ID returned by the Identity Provider. Depending on the type of the user one of the following methods may be used to add users into the application:
- Adding user account via Enterprise Admin pages
- Adding a sub-account user to a Multi-Access account
- Adding a sub-account user to Multi-User account
- Adding a Portal User to access portals and mobile apps
- When configuring the Contact Manager and the Portal in the Form.com application, ensure that the column with the “User-Principal-Name” is present in the Contact Manager and that this column is used as a “Login” field in the Portal.
If your account type is Branded/ Private Label, the parameters below have to be provided to FORM. If you have a Self-Hosted instance of the application, these parameters have to be added to the config.properties file of the application.
SAML2_IDP_CERT.SURVEY=-----BEGIN CERTIFICATE-----<CERTIFICATE_PUBLIC_KEY>-----END CERTIFICATE-----
- <IDENTITY_PROVIDER_NAME> - replace the tag with a name of the identity provider. For example, COMPANYIDP
- <SERVICE PROVIDER IDENTIFIER> - replace the tag with the WORLDAPPSP value.
- <CERTIFICATE_PUBLIC_KEY> - replace the tag with a certificate public key provided by the identity provider.
<CERTIFICATE_PUBLIC_KEY>- this parameter should have multiple lines in the config file. Every line must end with "\n\", except for the line where certificate ends.
- <AUTHENTICATION_URL> - specify a URL to the authentication page on the identity provider. Users will be redirected to this page when they try to access a resource that requires authentication without an active session.
Response from Identity Provider
The application is expecting one user parameter in return from the identity provider - NameID, which must match the login name of a user in the FORM system. If the system cannot find the user with such login name, HTTP 401 error response will be sent to the user.
Single Sign-On Configuration Documentation
Below you may find the PDF documents with the full description of Single Sign-On configuration: