Scaling for Better Performance
This scenario is better suited for small organizations that do not require any redundancy. Although able to support an increasing load on the K2 infrastructure, the K2 Server is separated from the SharePoint server for scalability.
| Scaling for Better Performance Install | |
|---|---|
| Server A | SharePoint 2007, SharePoint 2010 (Server or Foundation) |
| Server B | K2 blackpearl (all components)* Internet Information Server (IIS) |
| Server C | SQL Server |
 |
Note: Depending on the SharePoint product installed, either the MOSS, WSS, SharePoint 2010 Server or SharePoint 2010 Foundation components will be displayed for installation. |
The Scaling for Better Performance scenario is shown below. All of the K2 components are separated out from the SharePoint components, with a separate SQL server.
Considerations for the Scaling for Better Performance Install
Since this scenario deploys the various components onto multiple servers, there are some considerations around Kerberos and location of the components that should be addressed.
Kerberos
|
The default method for user authentication for new distributed installations is K2 Pass-Through Authentication. Kerberos is recommended for all configurations, machines and services in a distributed environment except for those that use OAuth (SharePoint 2013 and Azure Active Directory SmartObjects). |
Since the IIS server does not share a server with the K2 Server, the credentials will be passed as a result. Whenever credentials must pass more than one “hop” between servers, Kerberos must be configured. This is known as the “double-hop issue.”
Ensure that all Kerberos settings and necessary configuration takes place before attempting to install K2 blackpearl. To configure Kerberos, refer to the deployment considerations section on Kerberos later in this help file.
SQL Server
The location of the SQL Server is not critical for a K2 installation, as long as the network connection speed to the K2 Server meets minimum requirements. It is also important that the DTC component is configured properly in order for communications between the K2 Server and the SQL Server can function properly. The SQL Server can share physical resources or be located on an independent platform, such as in this install. Considering that in most cases K2 is being introduced into an existing environment, the K2 Databases would be installed on an independent server that runs SQL Server 2008. Since this is a common occurrence, the installation documentation takes this into consideration.
K2 Workspace
Clients access Workspace via the IIS Server operating from the K2 Server. If the user environment expands so that the performance of the K2 Server is affected by the number of users logging onto K2 Workspace, it is advised that the IIS components be relocated to a different server.
