Architecture Planning

The below topics assist with planning the overall landscape in which K2 will be installed and how the K2 instance(s) should look within the larger ecosystem.


Before installing K2, it is important to understand release cycles as well as compatibility across versions and external products. K2 relies on, and integrates with, a number of external products (SQL Server, Windows Server, SharePoint, etc…) and as such, it is critical to insure that versions of these align with K2 product support. Failure to understand and plan accordingly may result in a longer than expected installation experience.

Learn more about compatibility


Business Continuity Planning (BCP) is the discipline of designing environments and procedures that promote maximum system up time in the event of hardware failure or in some sort of physical catastrophe. BPC is comprised of two areas of focus:

  1. High Availability (HA)
  2. Disaster Recover (DR)

BCP is essential for any production infrastructure. However, the level of rigor of the planning cycles and the resulting level of effort and hardware and software investment must align with the mission criticality of the solutions hosted within the target environment.

Learn more about BCP

Base Platform Component Interaction

When planning the K2 infrastructure it is often useful to understand the components that constitute the K2 platform. Of specific use when planning and troubleshooting specific issues is to understand how the various components interact and communicate with each other.

Learn more about base platform component interaction

Line of Business Systems Interaction

When planning the K2 infrastructure it is imperative to understand the various systems with which the K2 platform will integrate. Having an accurate view of how K2 interrelates with the broader systems, helps determine data dependencies, security needs, subject matter experts and business continuity plans.

This section will focus on how to discuss, capture and present the high-level details for each line of business system (LOB) to which a K2 instance expects to interact.

Learn more about line of busines systems interaction

Performance & Capacity Planning

The aim of this document is to give the reader an overview to undertake capacity planning / management of K2 software and items with relevant teams to assist in the capacity planning / management process.

Learn more about performance and capacity planning

Environment Validation

This document is intended as a validation checklist of key K2 components post installation and integration. The document contains a checklist of environment validation items carried out and if not why.

Learn more about environment validation

Upgrade Planning

The aim of this document is to give the reader an overview to undertake upgrade planning.

Learn more about upgrade planning

Comprehensive Requirements

The aim of this document is to give the reader an overview to fully understand the requirements of a K2 system.

Learn more about comprehensive requirements

Choice of Deployment

Choose the approach that best meets your business needs; evolve your deployment approach as your business evolves and configuration and integration with many industry cloud solutions such as Office 365, Salesforce, SharePoint, and Azure Active Directory.


One of the key value propositions of the K2 platforms is its ability to combine people and systems into seamless solutions. As a result, the landscape contains disparate systems and technologies brought together by the K2 platform. As with any distributed platform, there is a need to understand, plan and configure for a secure environment for authenticated users.

Installation and Configuration

The K2 Getting Started Guides contain a significant amount of detail and discussions around supported topologies as well as detailed installation and configuration instructions.