Intelledox

Installation Checklist

Infiniti can be installed in a variety of deployment models from a single server to a server farm. A development environment can be set up on a single server with sufficient resources. Test and production environments may require a distributed architecture based on performance requirements. This document explains detailed steps to install Infiniti for development, test and production purposes.

System Requirements

Refer this article for the detailed system requirements.
System Requirements

Installation Planning Checklist

Below is a checklist to help prepare for installation of the Infiniti software. It is recommended that you review these items carefully to ensure you have everything in place and that the target environment is prepared according to the system requirements and recommendations.

Deployment Planning

  • Determine the target environment type.
    • Development
    • Testing
    • Staging
    • Production
    • Other (e.g. Demo or PoC)
  • Determine what deployment topology will be used for this deployment.
    • Single Server Deployment
    • Standard Two-Tier Deployment
    • Standard Scale-Out Deployment
    • Three-Tier Deployment
    • Other (e.g. Azure PaaS)
  • Identify what server(s) you will need.

    • IIS Web Server(s)
    • SQL Server Database Server(s)
    • Reverse Proxy / Network Load Balancer
  • Consider any network requirements that may apply.

  • Define Infiniti instances and naming.
    • Infiniti instance names, e.g. ‘infinitidev’ or ‘HRForms’.
    • Determine relevant target instance URL names for Manage and Produce sites. This will be useful when setting up IIS and also may be important for configuring DNS records, e.g. https://infinitisvr/infinitidev/produce.
    • Determine the name of other components to be installed and configured, such as the database and database login names – it may be worthwhile developing a naming convention if one doesn’t already exist.

System Requirements

  • Check the IIS web server(s) against the Web Server requirements discussed in System Requirements
  • Check the SQL Server database server(s) against the Database Server requirements discussed in System Requirements

Server Access

  • Ensure you have full administrator access to all IIS web servers and SQL Server database servers (access the server either physically or remotely, e.g. permission to allow Remote Desktop access.)
  • Ensure you can access all Infiniti installation media from the target servers. This may require access to an external drive, optical disc, website or FTP server, depending on where the installation media is available.
  • If applicable, confirm that any security procedures are followed to ensure there is no possible breach in gaining access to the target environment.

Installation and Configuration

  • Review the installation steps in this guide and ensure you have all the installation media required.
  • Take note of web server and database server names. You will need these during the installation.
  • If additional components, connectors or custom solutions are to be installed, ensure you have the installation media and any additional documentation ready.
  • Make sure you have a valid Infiniti license to be applied.

Notes

  • Ensure that the correct version of Microsoft .NET Framework and ASP.NET is installed before installation can begin.
  • The previous checklist may not cover all consideration needed for every installation, and equally, it may include items that are not relevant. Use this checklist as is or adapt it to your needs.
  • If there is already a naming convention developed in the organization use the existing convention. If you already do not have a naming convention this is an excellent opportunity to think about a naming convention.
  • Ensure that a supported version of Microsoft SQL Server is installed before installation can begin.

SQL Server

Infiniti supports: Microsoft SQL Server 2008 / 2008 R2 / 2012 / 2014 / 2016 / Express or higher editions.

  • (2005 no longer supported)

Updated 24 days ago

Installation Checklist


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.