Specifications

Configuring VMware vCenter Server - tc Server Settings in vCenter
Server
Starting with vCenter Server 5.1, VMware Tomcat Server settings can no longer be configured through the
Windows user interface. vCenter Server versions 5.1 and later use VMware vCenter Server - tc Server, an
enterprise version of Apache Tomcat 7. Tomcat version 7 does not provide a control panel in the Windows
user interface. Instead, you configure Tomcat by editing configuration files manually.
You can adjust the JVM maximum heap size for vCenter Server, vCenter Inventory Service, and Profile-
Driven Storage Service. For JVM heap size recommendations, see “Hardware Requirements for vCenter
Server, the vSphere Web Client, vCenter Inventory Service, and vCenter Single Sign-On,” on page 17.
Settings for Java options are stored in the following files.
n
vCenter Server. installation_directory\VMware\Infrastructure\tomcat\conf\wrapper.conf
n
vCenter Inventory Service. installation_directory\VMware\Infrastructure\Inventory
Service\conf\wrapper.conf
n
Profile-Driven Storage Service. installation_directory\VMware\Infrastructure\Profile-Driven
Storage\conf\wrapper.conf
n
The vSphere Web Client.
installation_directory\VMware\vSphereWebClient\server\bin\service\conf\wrapper.conf
Table 5‑2. Inventory Service and Profile-Driven Storage Service Java Maximum JVM Heap Size Setting in
the wrapper.conf Files
Java Option Setting and Default Value
maxmemorysize
The maximum JVM heap size, in megabytes. This setting
controls the maximum size of the Java heap. Tuning this
parameter can reduce the overhead of garbage collection,
improving server response time and throughput. For some
applications, the default setting for this option is too low,
resulting in a high number of minor garbage collections.
Inventory Service: wrapper.java.maxmemory=2048
Profile-Driven Storage Service:
wrapper.java.maxmemory=1024
The vSphere Web Client: For large deployments you might
need to set this option to wrapper.java.maxmemory=2048
ping.timeoutduration
The vSphere Web Client: For large deployments you might
need to set this option to wrapper.ping.timeout=120
vCenter Server security and port settings are stored in the following files.
n
installation_directory\VMware\Infrastructure\tomcat\conf\server.xml
n
installation_directory\VMware\Infrastructure\tomcat\conf\catalina.properties
Table 5‑3. vCenter Server Port and Security Settings in the server.xml and catalina.properties Files
vCenter Server Port or Security Setting Setting and Default Value
Base shutdown port base.shutdown.port=8003
Base JMX port. The listener implemented by the
com.springsource.tcserver.serviceability.rmi.JmxSocketList
ener class is specific to tc Server. This listener enables JMX
management of tc Server, and is the JMX configuration that
the AMS management console uses to manage tc Server
instances. The port attribute specifies the port of the JMX
server that management products, such as AMS, connect
to. The variable ${jmx.port} is set to 6969 in the default
catalina.properties file. The bind attribute specifies the
host of the JMX server. By default, this attribute is set to the
localhost (127.0.0.1).
The default -1 setting disables the port.
base.jmx.port=-1
Chapter 5 After You Upgrade vCenter Server
VMware, Inc. 137