5.0

Installing vFabric Platform 25
25
The license keys are displayed in the main vCenter Licensing window under the name VMware vFabric Standard|
Advanced, depending on the vFabric Platform package you purchased.
The vCenter Licensing page displays only the capacity of your vFabric Platform license; it does not actually keep
track of the number of licenses currently assigned. See Monitor vFabric License Usage for information on using
the monitoring commands.
What to do next
• Install one or more vFabric components on one or more VMs. See RHEL: Installing vFabric Components from the VMware
YUM Repository or Windows/Linux: Example Walkthrough of Installing Component from Download Page.
RHEL: Installing vFabric Components from the VMware YUM Repository
If your guest operating system is Red Hat Enterprise Linux (RHEL), VMware recommends that you use yum to install vFabric
components.
After you install the vFabric License Server in your vCenter environment, the high-level steps for installing vFabric components
using RPMs are as follows:
1. Read the important information about using RPMs to install vFabric components.
2. Install the vFabric repository RPMs so that your yum command can find the vFabric component RPMs.
3. Perform any required pre-installation tasks.
4. Install one or more vFabric component from RPM on one or more virtual machines (VM). The vFabric License Server
automatically keeps track of the number of VMs on which you install the components.
5. Perform any required post-Installation tasks.
Important Information About Installing Using RPMs
When you install vFabric components on RHEL from the VMware RPM repository, the components are installed into different
directories and are owned by different users in different groups. For example, the vFabric Web Server installation is owned
by the root user and the vFabric Hyperic Server installation is owned by the hyperic user, which is a non-interactive user
created by the RPM install.
The following table lists the vFabric components that you can install from the VMware RPM repository and their corresponding
RPM package name, which you will need when you use the yum install command. The table also includes important post-
installation information, such as the installation owner and group, and the directory in which the yum command installed the
component. You need this information later when you start to actually use the component.
In the table, the RPM package name for each component does not include the architecture suffix, such as .noarch or
.x86_64, but rather, just the base name, which is what you need to install the component.
Table 5.1. vFabric Components and RPM Package Information
vFabric Component RPM Package Name
Installation
Directory User Group Notes
vFabric tc Server
(Spring Edition)
vfabric-tc-server-
standard
/opt/vmware/
vfabric-tc-
server-standard
root tc-server In addition to features
provided in the tc
Server Standard
Edition package,
the vFabric Platform
offering (tc Server
Spring Edition)
includes commercial
support for tc
Server and Spring
Framework, as well