5.2
Table Of Contents
- Getting Started with vFabric Suite
- Table of Contents
- 1. About Getting Started with vFabric Suite
- 2. Quick Start Guide
- 3. Overview of vFabric Suite 5.2
- vFabric Suite Editions and Components
- vFabric Administration Server for Easier Component Management
- Simplified VM-Based Licensing Model
- vFabric Suite Product Integration and vSphere Integration
- Engineered for Spring-Built Applications
- VMware Support for Apache Tomcat, Apache HTTP Server, and RabbitMQ
- 4. vFabric Licensing
- 5. Installing vFabric Suite
- Install vFabric License Server on Your vCenter Server
- Activate vFabric Suite Licenses
- RHEL: Example Walkthrough of Installing Component From the VMware RPM Repository
- Windows/Linux: Example Walkthrough of Installing Component from Download Page
- RHEL: Optionally Configure VM to Track Open-Source Software Component Usage
- Upgrade vFabric License Server
- Uninstall vFabric License Server from vCenter Server
- 6. Monitoring vFabric License Usage
32 vFabric Suite
32 Installing vFabric Suite
For example:
prompt$ mkdir /opt/vmware
7. Extract the tc Server distribution file into the new directory.
This action installs tc Runtime; there is no installer program.
For example, if you created a directory called /opt/vmware in the preceding step, and downloaded the Standard Edition
file in the /opt/Downloads directory:
prompt$ cd /opt/vmware
prompt$ unzip /opt/Downloads/vfabric-tc-server-standard-2.8.0.RELEASE.zip
This action creates a directory called vfabric-tc-server-standard-version in the main tc Server installation
directory that contains the tc Runtime utility scripts, the templates directory, the Tomcat directory, and so on.
What to do next
• The component-specific next steps depend on the component you installed. For example, if you installed vFabric tc Server,
you might enable EM4J in the VM, create an instance, start it, and deploy a Web application to the instance.
See the vFabric component-specific documentation for details.
• If your vFabric license includes open-source software (OSS) support, optionally configure the Red Hat Enterprise Linux
(RHEL) VM on which you have installed one or more OSS components to track their usage. OSS components you can track
include Apache Tomcat, Apache HTTP Server, and RabbitMQ. See RHEL: Optionally Configure VM to Track Open-Source
Software Component Usage.
RHEL: Optionally Configure VM to Track Open-Source Software
Component Usage
If your vFabric license includes support for open-source software (OSS) components, you can also monitor the usage of the OSS
components on Red Hat Enterprise Linux (RHEL) VMs. To do this you must first install a vFabric OSS license agent on the VM,
as described in this section. Subsequently, when you monitor the vFabric license usage using the monitoring commands or the
user interface, the open-source components will also be included in the usage numbers along with the vFabric components.
You can monitor usage of the following open-source components; click on the links to view the supported versions and
additional information about the support provided by VMware:
• Apache Tomcat
• Apache HTTP Server
• RabbitMQ
Prerequisites
• See the Prerequisites for the sample walkthrough of installing a vFabric component on RHEL from the VMware RPM
repository.
The OSS license agent RPM is called vfabric-agent.
• Ensure that crontab is installed and running on your RHEL VM. The vFabric OSS license agent runs as a cron job.
Procedure
1. Log in as the root user on the RHEL VM on which you are going to install the OSS license agent and start a terminal.