The Rabbit MQ server used by PlateSpin Transformation Manager 1.2 is unable to connect to PlateSpin Migrate 12.2

  • 7018515
  • 24-Jan-2017
  • 09-Feb-2017

Environment

PlateSpin Migrate  12.2
PlateSpin Transformation Manager 1.1

 

Situation

The Rabbit MQ server used by PlateSpin Transformation Manager 1.1 is unable to connect to PlateSpin Migrate 12.2.

Event Messaging components are not configured properly if you install or upgrade PlateSpin Migrate Server on a drive that is not the C: drive. PlateSpin Transformation Manager 1.1 is the only consumer of the Event Messaging feature.

Resolution

To resolve this issue  you need to install the RabbitMQ Fix.

https://dl.netiq.com/Download?buildid=YEjOyq56-cA~

This patch addresses an issue where the Event Messaging components RabbitMQ and Erlang are not installed and configured properly after you have installed or upgraded PlateSpin Migrate Server on a drive that is not the C: drive. PlateSpin Transformation Manager 1.1 is the only consumer of the Event Messaging feature.

Run the Fix Message Queue Install utility (FixMessageQueueInstall.exe) on the PlateSpin server in order to fix the RabbitMQ installation and properly configure the components for use by PlateSpin Transformation Manager. The utility performs the following tasks:

  •     Synchronizes Erlang cookie values
  •     Reconfigures and restarts the RabbitMQ Windows Service
  •     Enables the STOMP protocol
  •     Creates a PlateSpinMigrate virtual host instance
  •     Creates and configures a PlateSpinPublisher user account
  •     Creates and configures a PlateSpinSubscriber user account
  •     Creates the PlateSpin message exchange
  •     Tests the connection to the PlateSpin message exchange


Detailed information about what the utility does can be found in the ${progName}.log file that is generated in the utility's directory.

After a successful patch, the PlateSpin Migrate server's Event Messaging components are installed and configured properly for use by PlateSpin Transformation Manager. Event messages are not published until you have configured a project in Transformation Manager to work with this PlateSpin Migrate server, and migration activities have begun.




Cause

This problem issue occurs when, the PlateSpin Migrate Server  that you plan to use with PlateSpin Transformation Manager 1.1. is not installed on the C: drive.