Aside from the specific hardware and software requirements listed below, there is one other essential pre-condition for running GX3 Enterprise. You must currently be running GX3 Professional.
• If your site has GX2 or earlier Worldox version installed, the first step is to upgrade to GX3 Professional.
• If you are a new customer, you need to install GX3 Professional first, then install GX3 Enterprise.
Sample Scenarios for Servers and Users
Client Machines -WDSAAS Workstations
Required: At least one terminal server (dedicated or virtual) running Windows Server 2008 R2.
Also, it is highly recommended – though not required – that each server have an SSL certificate.
There is no one best answer, as that depends on a complex interaction of hardware capabilities, expected usage patterns and requirements (if any) for redundancy and uninterrupted access to Worldox.
As best practices, we recommend:
• Use dedicated servers (machines or virtual) for GX3 Enterprise.
• Plan for redundancy; use multiple servers even in low-usage, few user scenarios.
Note: While we recommend multiple servers for redundancy, we defer to Microsoft for specific site planning.
• When anticipating higher use levels and many users, split the server load to multiple servers AND have at least one backup server on hand.
Factors to consider:
1. Total number of users expected to access GX3 Enterprise
2. Maximum number of GX3 Enterprise users expected at peak load times
3. Access strategy: Will GX3 Enterprise be used as a secondary, remote access point for users – from home offices, at client sites, on the road – or will Enterprise be the primary Worldox access from all points?
4. Server specifications, capacity, configuration
5. Need for uninterrupted access; if your sole Worldox terminal server goes down, what is the impact? If one of multiple Worldox terminal servers goes down, can the remaining server(s) handle the load?
|
Conditions |
Servers |
Detail |
A |
• 5 Worldox users • Enterprise provides partial access to Worldox, supplementing local network access. |
1 or 2 |
One dedicated terminal is sufficient to handle the load. To add redundancy and a safety factor, add a second terminal server. |
B |
• 18 Worldox users • Enterprise provides partial access to Worldox, supplementing local network access |
2 |
One dedicated terminal MAY BE sufficient to handle the load. To add capacity, add a second server. That second server also serves as backup, adding redundancy and a safety factor. |
C |
• 18 Worldox users • Enterprise is the sole access point to Worldox. |
2 or 3 |
One dedicated terminal MAY NOT BE sufficient to handle the load. To add capacity, add a second server. That second server also serves as backup, adding redundancy and a safety factor. Given expected higher loads, consider adding a third server. |
D |
• 35 Worldox users • Mixed access: Enterprise is the sole access point to Worldox for some users, and offers remote access to all users. |
3 |
Two dedicated terminal servers MAY BE sufficient to handle the load. To add capacity, add a third server. That third server also serves as backup, adding redundancy and a safety factor. |
Required: A Remote Desktop Server role has to be added on each server. Under that role, the Remote Desktop Session Host is the role that has to be added.
Required: Desktop Experience has to be enabled on each server.
Required: Client Access Licenses (CALs) to cover all users or devices, on one server.
Required: One, dedicated machine (workstation class):
• Running Windows Vista or newer OS
• Minimum 4 gigs of RAM
• Multi-core processor
Required: For each workstation:
• Running Windows XP, Service Pack 3 or newer OS
• Minimum RAM: 2 gigs for XP, 4 gigs for Vista or Windows 7
• Remote Desktop Client v.7 installed
Required: For each terminal server used, leave the default port 3389 or a port of your choice open.
Required: On the dedicated WDSERVER machine, leave ports 5010 – 5011 or two other ports of your choice open.
Required: Minimum 3 megabits per second.
Consider the bandwidth requirement as a bare minimum. It might be enough at a small office, where GX3 Enterprise is used as a secondary, remote access point for users. That bandwidth may be not nearly enough in larger offices with more users and more activity.
It is difficult to state bandwidth requirements, since what will be acceptable or optimal at your site depends on a complex interaction of factors, not all strictly Worldox-related:
1. Communication hardware, capacity and configuration used
2. Total number of users, all applications
3. Number of users expected to access GX3 Enterprise
4. Number of GX3 Enterprise users expected at peak load times
5. Total volume of traffic now (all applications, not including Worldox) at your site, average and peak load
6. Expected DMS usage patterns … will most users be uploading/downloading documents frequently?
7. Average file size of Worldox-managed documents
In terms of bandwidth, there are few helpful guidelines available. Microsoft recommends that 128kb be reserved for each user on remote access. However, that recommendation covers screen transfers only. Bandwidth required for GX3 Enterprise would clearly have to be much higher, given that Worldox sends and receives much more than just screen data.
We recommend that you get more bandwidth than you think you need and as much as you can afford. Extra capacity affects speed, which directly correlates to workflow efficiency and user satisfaction.