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
Installing vFabric License Server and
Activating Your License
31
31
vfabric.licensing.server.address=https://host:port
where:
• host is the hostname of the vFabric License Server RHEL computer.
• port is the secure port number that the License Serve listens to for HTTPS requests.
For example, if your License Server is on host myhost, listening at the default HTTPS port 8443, the file would look like
the following:
vfabric.licensing.server.address=https://myhost:8443
Location of vflicense.properties File
The vflicense.properties file points an installed vFabric component to the location of the standalone vFabric License
Server. You create the vflicense.properties file in the same directory in which the vFabric component keeps its events
file; this events file records particular events, such as the component start and stop times, as well as when it used its license.
The events file directory differs for each vFabric component. Depending on the component, the events file might be relative to an
instance (such as tc Server) or relative to the component installation directory, as shown in the following table.
Table 5.1. Location of the vflicense.Properties File
vFabric Component Location of vflicense.properties File
vFabric Web Server INSTALL_DIR/instance-name/conf, where INSTALL_DIR refers to the main installation directory of vFabric
Web Server (such as /opt/vmware/vfabric-web-server on RHEL), and instance-name refers to the
name of the Web Server instance.
vFabric tc Server INSTANCE_DIR/instance-name/logs, where INSTANCE_DIR refers to the directory that contains vFabric tc
Server instances (such as /var/opt/vmware/vfabric-tc-server-standard on RHEL), and instance-
name refers to the name of the tc Server instance.
Spring Insight Operations INSTANCE_DIR/instance-name/logs, where INSTANCE_DIR refers to the directory that contains the vFabric
tc Server instance that is hosting Spring Insight (such as /var/opt/vmware/vfabric-tc-server-standard
on RHEL), and instance-name refers to the name of the tc Server instance.
Note that the name Spring Insight Operations will not show up on the vFabric License Server usage report; rather,
the tc Server instance in which Spring Insight is running will show up instead.
vFabric EM4J INSTANCE_DIR/instance-name/logs, where INSTANCE_DIR refers to the directory that contains the vFabric
tc Server instance that is hosting EM4J (such as /var/opt/vmware/vfabric-tc-server-standard on
RHEL), and instance-name refers to the name of the tc Server instance.
vFabric GemFire GemFire Cache Server working directory.
vFabric SQLFire SQLFire Server working directory.
vFabric RabbitMQ /opt/vmware/vFabric (RHEL) or c:\ProgramData\VMware\vFabric (Windows)
vFabric Postgres /opt/vmware/vFabric (RHEL) or c:\ProgramData\VMware\vFabric (Windows)
Activate vFabric Suite Licenses
VMware offers VMware V8 production licenses for the vFabric Suite Standard and vFabric Suite Advanced platform packages.
The license is perpetual for a particular version and package of vFabric Suite.
The following procedures describe how to active your vFabric licenses, depending on the environment in which you installed the
License Server:
• Activate a vFabric Suite License in vCenter
• Activate a vFabric Suite License with a Standalone License Server