Kofax Communication Server 10.0.0 - Manual (Page 24)

Environment Guide Version 10.00.00
24 © Copyright Kofax. All information is subject to change without notice.
The reason for doing so is to be able to test the disk access to this volume using the dedicated
TcDiskTest tool.
If this recommendation is not fulfilled, it will be not possible to test actual disk throughput with the
dedicated TcDisktest tool afterwards
7.) 1 virtual CPU (VCPU) should be used.
8.) All other KCS applications connecting to the TCOSS must be run in separate VM(s). It is recommended
to connect their VNICs (virtual network adapters) to the same vswitch (virtual switch) as the VM of
TCOSS.
9.) In the case of multi-TCOSS instance operation (ASP model), all TCOSS instances may run in the
single VM. In this way storage TCOSS instances communicate with the media server through internal
vswitch and not over the physical wires.
10.) The TC/PerfLog application must be installed along with KCS setup on the TCOSS and FoIP server)
in order to permanently collect key performance indicators as Windows performance counter log files.
See TC/PerfLog Technical Manual for information about the application.
Non Real-Time Applications
No special requirements.
5.2.3 Resources Estimation for New Customers
In the case of a new customer who would like to deploy the KCS platform directly in their virtualized
environment (without the possibility to measure the real resource needs of their physical servers), refer to
the chapter Resource Estimation and Key Performance Indicators to find initial resource estimates to start
deployment with.
Later, during the operation of the KCS platform, it is required to observe the actual resource utilization. If
the utilization of a particular resource is higher than planned, grant more resources (in the case of CPU or
RAM) and/or – in the case of disk or network utilization – inform system administrators on increased
utilization so that they could match the new increased requirements with the overall resources distribution
on the particular ESX server.
Refer to the chapter Resources Estimation for Existing Customers for the guide how to measure real
resource needs.
5.2.4 Resources Estimation for Existing Customers
During the virtualization planning, the existing customers would usually use any of specialized capacity
planning tools (Platespin PowerRecon, VMware Capacity Planner, …) to collect performance data of their
physical servers (the usage of them is out of scope of this document) and then plan the deployment of their
virtual infrastructure. If this is not the case, the same task can be also accomplished simply by collecting
performance data for the typical workload for the particular application for a longer time (1-2 weeks) by the
Windows performance monitor. It is even possible to collect minimum requirements also if running the
particular application already in the VM. However, in this case the consumed processor utilization should be
measured via the Virtual Infrastructure client in processor bandwidth expressed in MHz.
During this process, the following most important resource requirements should be collected: