You are here: Download Volt MX Foundry Installer

Pre-Installation Tasks

Download Volt MX Foundry Installer

Download VoltMXFoundrySetup.tar.gz file from MHS Portal and extract the file. To download Volt MX Foundry installer from the community portal, follow these steps:
1. Log in to Downloads. You can obtain a user name and password from your sales representative or partner.
2. Click the Files tab.
3. Click on the specific file name to download the Foundry Installer file.
The VoltMXFoundrySetup.tar.gz file contains the following files:
- VoltMXFoundryInstaller-x.x.x.x_GA.bin
- installer.properties - This file is required for silent installation.
- README.txt

Steps before installing (or) upgrading Volt MX Foundry with the existing database

Perform the following activities before installing (or) upgrading Volt MX Foundry with the existing database:

Take database backup
Make sure you have previously installed directory
Take a backup of applications deployed at the server level. (Post installation, take backup of the changes done to the binaries).
Post installation (or) upgrade process, replace old authService.key, workspaceService.key, and ACCOUNTS_ENCRYPTION_KEY (applicable only for identity and workspace components).

Create /tmp Folder

Volt MX Foundry Installer required a /tmp folder in Linux environment to unpack installer. When the /tmp folder is not found, the Installer shows I/O exception at the time of unpack exception, shown below:

This must specify in the pre-req of installation. Installation must required temp folder to unpack MF installer (either default / custom temp folder).

Install Memcached Server

Memcached is a high-performance, distributed memory object caching system, generic in nature, but intended for use in speeding up dynamic web applications by alleviating database load.

libevent (memcached dependency)

The libevent API provides a mechanism to execute a callback function when a specific event occurs on a file descriptor or after a timeout has been reached. Furthermore, libevent also support callbacks due to signals or regular timeouts.

libevent is meant to replace the event loop found in event driven network servers. An application just needs to call event_dispatch() and then add or remove events dynamically without having to change the event loop. Refer to http://libevent.org/

To install libevent (memcached dependency), follow these steps:

First, check whether libevent is installed on your computer. To check, type the below command in your Linux terminal:

whereis libevent
If you do not find libevent on your system, download and install it. Download libevent-1.4.8-stable.tar.gz. Refer to http://libevent.org/
Extract the libevent-1.4.8-stable.
In your Linux terminal, type the below command:

cd libevent-1.4.8-stable

./configure

make

make install
Type the below command to create a symlink to libevent

ln -s /usr/local/lib/libevent-1.4.so.2 /usr/lib

Now that you have installed the dependencies, install the memcahced server.

Memcached Server

To install Memcached Server, follow these steps:

Download the memcached server.
Extract the zip file.
Open the Linux terminal.
Go to ../memcache directory.
Run the following command:

tar xfz memcached-1.2.6.tar.gz

cd memcached-1.2.6

./configure

make

make install

memcached -d -m 1024 -u root -l 127.0.0.1 -p 11211

Important: Run Memcached as a daemon (d = daemon, m = memory, u = user, l = IP to listen to, p = port)

Configure Load Balancers for Sending Host Information in Multinode

When user is installing Volt MX Foundry on multinode environment, the user should check whether the parameter: proxypreserveHost is set to On in the Loadbalancer configuration file to send host in the headers.

If the proxypreserveHost is not configured, the loadbalancer will not send host in the headers. Users cannot launch Volt MX Foundry Console.

The above configuration is based on the loadbalancer.

For example:

For Apache: preserveHost On
For HAProxy: preserve host flag is not required.

For database and app server related prerequisites, refer to the following sections:

MCP Server prerequisites (optional component)

Complete these steps only if you plan to enable the MCP Server. Skip if MCP will not be installed.

Application server — Select the bundled Tomcat or bundled JBoss option during installation. MCP is not supported with WebSphere, WebLogic, or externally managed Tomcat/JBoss.
HTTPS — Configure Foundry to use HTTPS. The MCP Server refuses to bootstrap against a plaintext HTTP Foundry base URL.
Python 3.12 or 3.13 — Install CPython in the 3.12.x – 3.13.x range on the target machine.
- Linux: install via the OS package manager (for example, python3.12) or from python.org; ensure python3.12 (or python3.13) is on PATH.
- Windows: install from python.org and select Add python.exe to PATH in the installer.
pip on the same interpreter — Verify pip is bound to the same interpreter:
```
python --version
python -m pip --version
```
Both commands must succeed and report the same 3.12.x or 3.13.x version. On Linux you may need to install python3-pip (or python3.12-pip) via the OS package manager.
Port 9093 free — Ensure TCP port 9093 (or your chosen MCP_PORT) is not in use and is opened on the host firewall for the clients that will connect.
(Optional) Redis — If you plan to use Redis for MCP state, install and start Redis, and record its URL in the form redis://:password@host:6379/0.

Scope reminder:

MCP is supported only with the bundled Tomcat and bundled JBoss application servers. It is not available with WebSphere or WebLogic, and is not supported on external / pre-existing Tomcat or JBoss installs.
The MCP Server requires HTTPS on the Foundry base URL.
The target machine must have Python 3.12 – 3.13 with pip on the same interpreter (python -m pip --version must succeed and report the same version).
MCP is never auto-selected. It must be explicitly enabled.