The following control files are critical to the configuration of a Beeks Analytics appliance:

<confdir>/vmx-servers.cfg

<bindir>/env-instances.sh

Configuring multi-instance and multi-appliance deployment using vmx-servers.cfg

The same env-instances.sh and vmx-servers.cfg files can be installed on multiple appliances, even if there are different services running on different servers. This can make configuration versioning and control much easier. This can be achieved because the <confdir>/vmx-servers.cfg file provides a mapping of appliance host to instance type and instance name. The vmxadmin command uses this configuration file to determine which instances should run on any particular appliance.

Here is an example vmx-servers.cfg file: 

# 

# Server configurations: 

# <machine-name from: uname -n> <vmx-server|vmx-network> [<instance>] 

# 

# Eg: 

vmx104.abank.com vmx-server 

vmx105.abank.com vmx-pmux capAB

If running the Unix command ‘uname -n’ produces the hostname ‘vmx104.abank.com’, then the vmxadmin script will only start the vmx-server service. It will not ever attempt to start the capAB vmx-pmux service.

It’s particularly important for the operation of VMX-Prism that the vmx-servers.cfg file is consistent on all servers, and that the hostnames within the file are resolvable from all servers.

Configuring appliance environment parameters in env-instances.sh

Appliance environment variables are configured in <bindir>/env-instances.sh .

The file provided with your appliance will contain some example values that you can refer to in this file. Here are some of the different appliance level environment variables which can be useful to edit:

Variable

Usage

VMX_JAVA_HOME

Specifies what version of Java will be used. Some Beeks Analytics deployments use the zing version of Java for increased performance.

VMX_CPUS

Sets CPU affinity for ALL Beeks Analytics processes. You can also set this per process for more granular CPU affinity.

VMX_DB_SUFFIX

Set this row to the env name in a multiple environment setup.

This file also configures the startup parameters (memory, ports, interfaces etc) for the various VMX-Capture probes - see VMX-Capture: Capture and Base Configuration and VMX-Capture: Stack Probes, Aggregations, Statistics and Agent Events for more information.