MPX installation on Linux

This topic explains how to install MPX on Linux. For a brief overview about MPX, see About MPX.

Dependencies - Startup order for MPX components

It is essential that you perform the startup of the MPX components in a specific order:

  • The Message Broker is core to everything, so you should start it first. There is no particular order to starting root and remote Message Brokers. In general, if the Message Broker used by an MPX component is not running, the MPX component fails to start. For example, if a Root MPX Cache Agent is installed as an auto-start service and uses a Message Broker on the same computer, the Root MPX Cache Agent may start more quickly than the Message Broker. In this case, the Root MPX Cache Agent fails. The fix is to make the Root MPX Cache Agent service depend on the Message Broker service.
  • You should start the MPX-enabled StarTeam Server configuration next. You must start it at least once before starting the Root MPX Cache Agent to create the CacheJournal.dat file. The first time you start a StarTeam configuration after a MPX File Transmitter has been activated, it creates the CacheJournal.dat file for that server configuration. If the Message Broker it uses is not running, the server configuration starts in non-MPX mode. This means the server will work, but no MPX messages will be broadcast, and "fixing" it requires restarting the server.
  • You should start the Root MPX Cache Agent(s) next. If the Message Broker it uses is not running, or if the CacheJournal.dat file does not exist for the server configuration it is tracking, the Root MPX Cache Agent fails to start. Once the CacheJournal.dat file exists, the root MPX Cache Agent no longer has a start-order dependency with the StarTeam Server configuration. It can start before or after the StarTeam Server configuration has started.
  • You can start the Remote MPX Cache Agent(s) at any time. It is independent of all other MPX components except for the Message Broker to which it connects. If that Message Broker is not running, the Remote MPX Cache Agent fails to start. However, if one of the Root MPX Cache Agent or the StarTeam Server configuration it is tracking are not running, it detects them when they are started.
  • The MPX-enabled StarTeam Server configuration must be running before the MPX Cache Agents or clients can access it.
  • The MPX Cache Agents must be running before the clients can retrieve files from them.

Back to top

Requirements when using ActiveMQ MPX

Adhere to the following guidelines for system configurations that use ActiveMQ MPX:

  • If a remote MPX Cache Agent is used, install the ActiveMQ MPX Message Broker on the remote MPX Cache Agent machine.
  • All MPX Cache Agents (root or remote) must be upgraded to version 15.0 and configured to use the ActiveMQ MPX Message Broker.
  • You must upgrade to StarTeam Agile 15.0, StarTeam Web Client 15.0, and the latest Micro Focus Connect.
  • We recommended that users upgrade to StarTeam Cross-Platform Client 15.0 , which can connect with MPX using any of the brokers.

    Note: If you are using a version of the StarTeam Cross-Platform Client prior to 15.0, MPX will not work in this scenario.

Back to top