K2 blackpearl Installation and Configuration Guide > Planning Guide > Deployment Scenarios - K2 Supported Topologies > Small Scale Install | Send feedback |
In many cases K2 blackpearl is installed into an existing infrastructure; therefore, the database components can be easily installed on an existing SQL server. This is true even when all K2 components are installed on an existing server. This is suitable for small usage, such as a test or training environment.
Small Scale Install | |
---|---|
Server A | K2 blackpearl (all components)* Internet Information Server (IIS) SharePoint 2007, SharePoint 2010 (Server or Foundation) or later |
Server B | 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 Small Scale Install configuration for K2 blackpearl is shown below. All K2 components, IIS, SQL Reporting Services, and SharePoint are installed on one server, and the databases are located on a separate server.
For small scale installations, hardware and SQL Server considerations must be taken into account.
If this installation scenario is used, it performs best as a development or proof of concept environment. It is recommended that additional RAM or a faster processor is used in order to maintain acceptable levels of performance.
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 this small scale 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.