Kofax Communication Server 10.0.0 User Manual
Page 29
Environment Guide
Version 10.00.00
© Copyright Kofax. All information is subject to change without notice.
29
1)
The shares method (fair share principle)
This method is clearly most effective method for the system administrators, guaranteeing the most
effective utilization of resources on the ESX server. On the other hand, when the administrators add
more and more VMs to the ESX server, this decreases the CPU resources also for the other VMs and
therefore it is not suitable for real-time applications like TCOSS Server, but may be used for other KCS
applications like IPPrinter.
2)
Explicitly grant minimum CPU bandwidth (in MHz)
The particular VM always receives the minimum amount of CPU cycles despite of the fact whether it
needs them or not
– therefore this method is not being favored by the VMware, but it is a clear
precondition for the VM running real-time application. If the necessary resources could not be granted,
the ESX server simply does not start particular VM. Furthermore, due to the Timekeeping issue in the
virtualized environment (see
it is absolutely
necessary for the messaging server to receive enough CPU cycles in order to keep its time
synchronized with the real-time (especially important for the messaging servers due to legacy
reasons).
Note that this method is required for KCS real-time applications (TCOSS Server).
The CPU for the particular VM may be allocated by the context menu “Edit Settings” via the VI client:
In the panel Resources of the Virtual machine Properties dialog:
5.3.2
Memory
Amount of the memory allocated for the particular VM can be configured via the Hardware panel of the
Virtual machine Properties (configured memory can be changed only if the VM is powered off):