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
Overview of vFabric Suite 5.2 9
9
Component and Version Description
vFabric Suite Standard
Component
vFabric Suite Advanced
Component
clouds and in dynamic virtual
environments.
vFabric tc Server 2.8 (Spring Edition)
VMware® vFabric™ tc Server is 100-percent compatible with Apache Tomcat 7. It has all the runtime advantages of Tomcat,
plus operational management, advanced diagnostics, mission-critical support, and unmatched visibility into Spring-powered
applications — none of which are available in the open source product. vFabric tc Server Spring Edition includes all of the
components and features of tc Standard Edition, plus Spring Insight Operations, Elastic Memory for Java (EM4J), and Spring
commercial support.
tc Server harnesses the power of traditional JEE architectures while eliminating their complexity and performance drawbacks,
making it easier, faster, and more cost-effective to build and run cloud-ready applications. With its lean architecture and small,
10MB memory footprint, tc Server requires significantly fewer resources than conventional servers, which allows for greater
server density in virtual and cloud environments. tc Server supports integration with VMware tools and vFabric Hyperic, and
provides templates for vFabric GemFire session replication.
Main features of vFabric tc Server (Spring Edition):
• Compatible with existing Apache Tomcat applications, thus eliminating migration costs and cycles.
• Parallel deployment. Deploy multiple revisions of the same application at the same time so you can roll out a new revision of
an application without affecting users.
• Automatic instance upgrades. A new script lets you easily upgrade earlier instances to function with tc Server 2.8.
• Automated deployment of applications to multiple instances of tc Server and standardized templates for rapid provisioning of
new instances.
• Commercial support for vFabric tc Server and Spring Framework.
• Elastic Memory for Java (EM4J). Included with tc Server Spring Edition, EM4J allows Java workloads to cooperate more fully
with ESXi advanced memory-sharing technologies. EM4J helps maintain Java application performance and reliability while
freeing memory so you can run more VMs per host, improving your consolidation ratio.
• Spring Insight Operations, a Web application that gives you real-time, detailed visibility into application behavior and
performance. Insight Operations is optimized for monitoring and tuning Spring-built applications in production.
For new feature information, see vFabric tc Server Release Notes.
EM4J 1.2 for Improved Memory Management of Java Workloads
Elastic Memory for Java (EM4J) revolutionizes the virtualization of Java applications.
With EM4J and tc Server, you can run more Java applications on your ESXi servers than previously possible, and Java
applications can leverage ESXi's industry-leading memory sharing technology.
Previously if you ran Java on VMware ESXi, you had to reserve 100% of the configured memory for a VM running Java
applications or risk serious performance problems. To determine the optimum size of the Java heap, you determined the
application's peak requirement. Allocating less could mean unacceptable performance, errors, or crashes; allocating more than
was necessary wasted memory.
EM4J changes all that. It is a balloon that sits directly in the Java heap and works with a new memory-sharing interface
introduced in ESXi 5.0. EM4J allows ESXi to share available memory in the Java heap among VMs as needed, while preserving