Upgrading to ActiveMQ MPX Messaging in version 17.1 and above

Starting with StarTeam Server version 17.1, we only support MPX messaging with ActiveMQ message broker. Legacy StarTeamMPX (SmartSockets technology) is no longer supported.

Upgrading to ActiveMQ MPX Messaging using default port 61616

Configurations that are still using StarTeamMPX will automatically be converted to ActiveMQ during StarTeam Server and Cache Agent startup. ActiveMQ broker installs by default on port 61616, and the configuration files will be upgraded to use port 61616 as well.

The following files will be upgraded, and a backup copy of the file will be created:

  1. Event Transmitter configuration file: MPXEventTransmitter.xml

    This file is located in the folder EventServices under the repository folder for each configuration.

    1. Update to the Name property in the <Handler> section. This indicates what type of messaging will be used with this configuration. The type will be set to ActiveMQ MPX Transmitter, which designates the use of ActiveMQ MPX-type messaging and brokers.

    2. Update to the server_names property in all profiles: the ports will be changed to 61616, which is the default port for ActiveMQ MPX Message Brokers.

    3. The version of the file will be upgraded to 3.0.

  2. Root Cache Agent and Remote Cache Agent configuration files:

    1. In the <MessageBroker> section, the Name property is updated to ActiveMQ MPX Transmitter.
    2. Update to the server_names property in all profiles: the ports will be changed to 61616, which is the default port for ActiveMQ MPX Message Brokers.
    3. The version of the file will be upgraded to 3.0.

The following changes must be done manually to complete the conversion to ActiveMQ MPX:

  1. Stop and disable the StarTeamMPX Message broker service. If using multiple message brokers, all of the StarTeamMPX brokers must be stopped and disabled.

  2. Install ActiveMQ broker using default port 61616 (option during Server install). If you previously used multiple message brokers, install ActiveMQ brokers to replace the old ones.

  3. If using CacheAgents, make sure to install version 17.1 Cache Agents to replace the Root Cache Agent and the Remote Cache Agent older version(s).

After server startup, check the server log to verify that StarTeam Serve correctly connected to the new broker.

Back to top

Configuring ActiveMQ with a custom port number (not 61616)

ActiveMQ installation and upgrade use the default port 61616. If you already have another port available and open (for example port 5101 was previously used for StarTeamMPX and is already approved for use), the following steps are needed:

  1. Stop and disable the StarTeamMPX Message broker service. If using multiple message brokers, make sure all heritage StarTeamMPX brokers are stopped and services disabled.

  2. Install ActiveMQ broker and select the desired port during installation (option during Server install). If you previously used multiple message brokers, install/update the port for all ActiveMQ brokers to replace the old ones. If ActiveMQ is already installed, see Changing the Endpoint of a Message Broker for details how to change the port.

  3. Update EventTransmitter file to ActiveMQ, and edit the port in the section <server_names>. See System Configuration Requirements for details. Make sure to set the file version to 3.0.

  4. Update all Cache Agent settings (both root and remote) to ActiveMQ, and edit the port in the section <server_names>. See System Configuration Requirements for details. Make sure to set the file version to 3.0.

  5. Restart StarTeam Server and all Cache Agents.

Back to top