5.3
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.3
- vFabric Suite Editions and Components
- Component Integration and Cross-Platform Consistency
- Optimized for vSphere and Spring-Built Applications
- Product Overviews
- vFabric tc Server 2.9 (Spring Edition)
- vFabric EM4J 1.3
- Spring Insight Operations 1.9
- vFabric Hyperic 5.0
- vFabric GemFire 7.0 (Application Cache Node)
- vFabric RabbitMQ 3.0
- vFabric Web Server 5.3
- vFabric SQLFire 1.1 (Professional)
- vFabric Application Director 5.0 (Provisioning)
- vFabric Postgres 9.2 (Standard Edition)
- 4. vFabric Suite Licensing
- 5. Installing vFabric License Server and Activating Your License
- Installing vFabric License Server on Your vCenter Server
- RHEL Only: Installing vFabric License Server Standalone
- Activate vFabric Suite Licenses
- Optionally Configure Computer to Track License Usage of OSS Components on RHEL
- Upgrade vFabric License Server on vCenter Server
- Uninstall vFabric License Server from vCenter Server
- Uninstall Standalone vFabric License Server
- 6. Monitoring vFabric License Usage
- 7. FAQ: vFabric Suite Integration and Off-Cycle Releases
46 vFabric Suite
46 Monitoring vFabric License Usage
Prerequisites
• If necessary, install a JDK or JRE on the computer on which the vFabric component is installed.
Be sure the JAVA_HOME and PATH environment variables point to the JDK or JRE.
For example, if you installed the JDK in /usr/java/jdk1.6.0_24, you can set the environment variables in the user's
Linux profile as follows:
export JAVA_HOME=/usr/java/jdk1.6.0_24
export PATH=$JAVA_HOME/bin:$PATH
Procedure
1. On the computer on which the vFabric component is installed, download the vFabric License Check Tool from
the Drivers and Tools tab of the download page for vFabric Suite Advanced or Standard.
The file is called vfabric-vfchksn-version.bin.zip.
2. Unzip the file into a directory.
The utility and supporting files are unzipped into the vfabric-vfchksn-version child directory.
3. Open a command (Windows) or terminal (Linux) window, change to the directory in which you unzipped the utility, and run
the following (Linux):
prompt$ vfabric-licensetool printevents -f events-file
On Windows:
prompt> vfabric-licensetool printevents -f events-file
In the preceding commands, events-file refers to the full pathname of the component events file that you want to
display. Each component names and stores its events file differently. See Location of vflicense.properties File for the
location of the events file for each component (it is the same location as that of the vflicense.properties file). The
following table shows the name of the events file for each vFabric component:
Table 6.5. Name of the Events File For Each vFabric component
vFabric Component Name of Events File
vFabric Web Server vf.ws-events.txt
vFabric tc Server vf.tc-events.txt
Spring Insight Operations vf.ins-events.txt
vFabric EM4J vf.emj-events.txt
vFabric Hyperic vf.hyp-events.txt
vFabric GemFire Data Management Node vf.gf.dmn-events.txt
vFabric GemFire Application Cache Node vf.gf.acn-events.txt
vFabric SQLFire vf.sf-events.txt
vFabric RabbitMQ vf.rmq-events.txt
vFabric Postgres vf.vpg-events.txt
For example, to display event log information in readable fashion for a vFabric tc Server component in which the events file
is in its default RHEL location, run the following (Linux):