In this document, you’ll find recommendations for software and hardware, so that you can best use WorldAPP’s Enterprise Data Collection Platform for your business needs.
Following these recommendations will assist in keeping the application stable and secure.
System Software Requirements
As a minimum, the WorldAPP Enterprise Data Collection Platform may be deployed on a single server with a minimum requirement of an operating system with Java runtime, application server and the database server installed on it.
For security and performance reasons it is also recommended to use 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 the database server and the web server (if the one is used) deployed on separate physical hardware.
WorldAPP’s Enterprise Data Collection Platform may also be deployed in a virtual environment, however, the performance may slightly degrade compared to the system deployed on a separate physical machine.
|Operating System||Any 64 bit OS compatible with Oracle Java JRE/JDK 1.8|
|Web Server (optional)||Apache HTTP server 2.2 or higher, IIS 8|
MS SQL Server 2016
Oracle 11g, 12c
|Additional Software||one or more SMTP server, DNS server|
The hardware required to run the WorldAPP Enterprise Data Collection Platform in production depends greatly on projected 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 will experience during the peak hours.
Hardware requirements outlined below represent the minimum hardware that is required to get the system up and running and collecting a few thousands of form submissions daily.
If firewalls or other software or hardware is present, and it prevents the Platform from being able to communicate with the required services (such as database, NS servers, SMTP servers, etc.) or from being accessed by users, configuration of such hardware and software should be prepared and applied before installation. If the web server is being used, communications between the application and the web servers should be allowed as well.
Intel x86 64-bit or AMD 64 architecture is supported.
Multicore processors 2Ghz frequency or higher are recommended.
8GB minimum is sufficient for most use cases.
The systems where high load is expected may require more memory.
|HDD||It is recommended 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 external RAID system are recommended.|
|Database Space||200GB of free space for the database is sufficient for most use cases. However the more data is collected with the platform, the more hard disk space will be required. It is recommended to plan provisioning of more disk space if large volumes of data will be collected using the Platform, it is also recommended to reserve space or replication and backups in the production systems.|
|Network Connectivity||At least one dedicated IP address.|
More details and requirements will be provided in the installation instructions shipped with the installation package.
These instructions must be read carefully before rolling out the application.
Typically WorldAPP delivers its self-hosted solutions as a custom package, with the software, configuration and the installation instructions designed with the unique environment configuration that a customer may have. However, delivering such custom deployment package may take some time, which is needed to put together the package and write the proper installation instructions.
WorldAPP’s Data Collection platform is also available in pre-configured installation packages, which are readily available for certain environment configurations and may be delivered much more rapidly than a custom package built per the specific requirements.
WorldAPP’s Enterprise Data Collection Platform installation packages are currently available for the following configurations and platforms:
Microsoft Windows based system
Web Server (optional): Microsoft IIS 8
Operating System for Application server: Microsoft Windows Server 2016
Application Server: Apache Tomcat 7
Database: Microsoft SQL Server 2016
Linux based system
Web Server (optional): Apache Web Server 2.2
Operating System for Application Server: Linux (Red Hat enterprise Linux is recommended)
Application Server: Apache Tomcat 7
Database: MySQL 5.7
Packages include Application binaries, configuration templates, database data structures, initial installation data, instructions and manual for the installation. All files are compressed and available for downloading per request.
For all other systems configurations, WorldAPP will provide a custom deployment package, with optimized configuration settings and detailed installation instructions.
Form.com and Key Survey applications may be configured to allow 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 WorldAPP. 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 WorldAPP 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: