Planning An Ace Management Server Deployment; Deployment Components - VMware ACE Management Server Administrator's Manual

2
Planning an ACE Management Server
Deployment
This chapter provides guidelines for deploying VMware ACE Management Server instances, including
capacity planning and best practices. This chapter includes the following topics:

"Deployment Components" on page 13

"Performing Capacity Planning" on page 15

"Security Features and Considerations" on page 17

"Accessing ACE Management Server from Outside the Corporate Firewall" on page 19

"Deployment Planning Worksheet" on page 19

Deployment Components

A typical ACE Management Server deployment has the following components:

One or more ACE Management Server instances – Configuring multiple servers to use the same
database increases the number of ACE clients you can manage and guarantees high availability.

Database server – For production deployments, VMware recommends Oracle Database 10g or MS‐SQL
for ACE Management Server installed on a Windows host, and Postgres for ACE Management Server
installed on a Linux host.

(Optional) Active Directory domain controller – To enable the ACE Management Server Active
Directory integration, you must configure ACE Management Server to communicate with your domain
controller.

(Optional) HTTP load balancer – Use a load balancer to help scale the capacity of your ACE Management
Server deployment.

(Optional) HTTP proxy – If clients will access ACE Management Server from outside the corporate
firewall, VMware recommends using an HTTPS proxy in the DMZ. You can use ACE Management Server
with Apache Proxy and Zeus Technology Load Balancer.
For an example of an ACE Management Server deployment, see Figure
VMware, Inc.
2‐1.
2
13