Documente Academic
Documente Profesional
Documente Cultură
Yes No
Table 10: Product Prerequisites (Continued)
Products Third-Party Component Prerequisites
Acquired by Customer Provided by Genesys
74 Genesys
Chapter 3: Operating Systems Support Tables Table 10: Product Prerequisites
a.From 7.2 and higher, GIS is no longer a standalone product; it is part of Genesys Interaction SDK. Refer to Genesys Interaction SDK for the product pre-requisites.
b.Refer to Genesys Customer Interaction Portal Deployment and Administration Guide for more information.
c.Required for the WinUI Applications of the adapter.
d.iPlanet and iPlanet/JRun are supported only in 6.5.1 ICS.
e.Support & maintenance, upgrades, and licensing are to be purchased directly from Allaire/Macromedia.
f. For Multimedia, Web Collaboration is not supported on WebSphere and JRun.
g.From 7.2 and higher, .Net Server is no longer a standalone product; it is part of Genesys Interaction SDK. Refer to Genesys Interaction SDK for the product pre-requisites.
h.JDK 1.5 is supported for Web API Server for 8.0.
7.5
WFM Database Utility - MDAC 2.7 SP1 or MDAC 2.8, .NET Framework 1.1+, Jet
4.0
WFM Config Utility, WFM Server, WFM Data Aggregator - MDAC 2.7 SP1 or MDAC
2.8
WFM Web Server - Jakarta Tomcat 5.0--5.5 (with Sun J2SE JDK 1.4.x or 5.0
Update 1 or later), or IBM WebSphere 6.0 or 6.1.
WFM Web Supervisor - Sun J2SE JRE 1.4.x, or 5.0 Update 1 or later.
7.6+
WFM Database Utility - MDAC 2.7 SP1 or MDAC 2.8, .NET Framework 1.1+, Jet
4.0
WFM Configuration Utility, WFM Server, WFM Data Aggregator - MDAC 2.7 SP1 or
MDAC 2.8
WFM Web Server - Jakarta Tomcat 5.0--6.0 (with Sun J2SE JDK 5.0 Update 1 or
later), or IBM WebSphere 6.1.
WFM Web Supervisors - Sun J2SE JRE 5.0 Update 1 or later.
Yes No
Table 10: Product Prerequisites (Continued)
Products Third-Party Component Prerequisites
Acquired by Customer Provided by Genesys
Chapter 3: Operating Systems Support Tables Table 11: Suite-Wide Feature Support
Supported Operating Environment 75
Tabl e 11: Sui t e-Wi de Feat ur e Suppor t
This table provides you with references for operating system support variations for a given suite-wide feature.
Table 11: Suite-Wide Feature Support
Suite-Wide Feature Operating Systems Support References
Security-Related Features See the Genesys 7.6 Security Deployment Guide
76 Genesys
Chapter 3: Operating Systems Support Tables Table 11: Suite-Wide Feature Support
Supported Operating Environment 77
Chapt er
4 Vi r t ual Pl at f or m Suppor t
This chapter provides information on Genesys Virtual Platform support.
The chapter includes:
VMware Support, page77
VMwar e Suppor t
Genesys supports VMware for its products and solutions from release 7.5 onward, and will accept service
requests for product issues reported while using Genesys on VMware.
Product certification will be performed primarily for VMware ESX Server - the bare-metal (deployed without
host operating system) virtual engine of Virtual Infrastructure 3 (VI3). However, for lab deployments and tests,
VMware hosted products (require host operating system) such as VMware Server, GSX, or Workstation, can be
used, as well.
Supported VMware deployments are those where both host, if applicable, and guest operating systems are
included in the list of Genesys supported operating systems.
As of today, Genesys is aware of the following caveats that customers shall take into account when deploying
Genesys solutions on VMware:
78 Genesys
Chapter 4: Virtual Platform Support VMware Support
1. VMware shall be run on sufficiently equipped computing platforms, in particular with respect to CPU speed
and available memory. The virtualization can increase the processing load compared to native deployment
on the given node: up to 7% for ESX and up to 30% for hosted products.
2. If license control is performed on VMware, either by running FLEXlm license server on VMware or by
using node-locked application licenses, then the host-id value returned by VMware will be used. One
example for such host-id is the MAC address. By default, VMware generates one MAC address each time it
is launched, based upon certain traits of the physical machine. This would be fine if the image was only run
on the same physical machine each time (since the generated MAC would be the same), but when moving it
around, the MAC changes. A possible workaround is to override the default and force VMware to use a
static (fixed) MAC address.
3. Certain networking products utilized by some Genesys solutions might not work under VMware. This
applies in particular to Dialogic boards, and also, HMP is not currently certified for VMware. The same
might apply to products that require other specialized cards, for example, X.25 network cards. In this case,
additional investigation is required regarding compatibility with VMware.
4. VMware causes a time-drift for applications running on the guest operating system. This can be mitigated
by using dedicated VMware tools for time synchronization. Note: Use of Windows Time service is not
recommended by VMware. However, it is not recommended to run real-time critical functions that are
sensitive to jitter and latency on VMware. This applies in particular to VoIP RTP media processing.
It is assumed that VMware will be deployed mostly within lab or test environments. When production
deployment is planned, it is strongly suggested to carefully perform sizing and dimensioning, and to respect the
above recommendations.