VMware VCLOUD REQUEST MANAGER 1.0.0, Configuration Manual

Page: 19 / 70

Based on these average scan times, scanning 100 vApps can take 4 minutes. Scanning 5000 vApps can take 3
hours.
Scan updates are reflected when the next scheduled scan is run. By default, scans are set to run hourly. See
“Create or Modify a vCloud Director Synchronization Schedule,” on page 40.
Request Manager maintains a cached copy of the data within vCloud Director for better responsiveness. This
cache is populated by scheduled scans and is only as current as the latest scan. An exception is the status display
of each vApp, which is retrieved live from vCloud Director.
N
OTE
vCloud Director permits consumers of the vCloud API to be logged in for maximum period of 24 hours.
If a scheduled scan of vCloud Director by Request Manager were to take longer than 24 hours, Request
Manager's session would expire and the scan would abort without completing. However, a new scan would
begin shortly after and resume where the previous scan had completed.
Database Sizing
Running a scan on a large number of vApps and resources can consume a lot of database space. The following
test data provides some idea of how much space.
n
Scanning 30,000 resources consumes approximately 270 MB, or 9.21 KB/resource.
n
A scan of 100 vApps can consume 1 MB. A scan of 5000 vApps can consume 45 MB.
Security
Security certificates must be manually installed.
Security Certificates
Request Manager communicates with vCloud Director over a secure connection with SSL. Optionally, Request
Manager can communicate with the Active Directory server using SSL. Communication over SSL can only
succeed if the Request Manager server is able to trust the certificates utilized by those servers.
A server's certificate will be trusted by the Request Manager server if it meets the following prerequisites:
n
The certificate or the certificate of its issuer must be installed to the Trusted Root Certificate Authorities
store for the local machine. See “Installing a Security Certificate,” on page 20 for directions on how and
where the certificate should be installed.
n
The certificate must be issued to either the host name (fully qualified by domain) of the remote server or
the domain to which it belongs. For example,
server1.mydomain.com
or
mydomain.com
. Furthermore, when
connecting via SSL the same fully qualified host name must be specified in the Active Directory Connection
String or the vCloud Director server URL.
n
The certificate be valid and must not have expired.
N
OTE
If either of the Active Directory or vCloud Director server certificates have not been issued to fully
qualified host name, these certificates will need to be re-issued on those servers by the administrator of those
servers. Please consult the documentation for these products for instructions on how to re-issue these
certificates.
Chapter 2 Request Manager System Requirements
VMware, Inc. 19