5.6 Enabling Event Messaging for PlateSpin Migration Factory

PlateSpin Migrate provides an event messaging service based on RabbitMQ for use in the PlateSpin Migration Factory environment. Each PlateSpin Migrate server can publish workload migration state change messages to PlateSpin Migrate Connector instances that subscribe to the service on behalf of PlateSpin Transformation Manager projects. For information about how communications work for PlateSpin Migration Factory, see PlateSpin Migration Factory in the PlateSpin Transformation Manager 2 Administrator Guide.

The RabbitMQ message queues are pre-configured and start automatically when you start the PlateSpin service for a PlateSpin Migrate server. No messages are published unless you open port 61613 on the Migrate server to allow registration by subscribers, and a PlateSpin Migrate Connector subscribes.

NOTE:The messaging function starts, stops, and restarts automatically with its parent PlateSpin Migrate server service. Do not modify the default settings for event messaging.

In PlateSpin Transformation Manager, you configure the PlateSpin Migrate server as a Migration Server resource for a project. The project’s assigned PlateSpin Migrate Connector subscribes to RabbitMQ event messaging. After RabbitMQ has an active subscriber and there are workload migration activities to report, RabbitMQ begins publishing event messages and registered subscribers can receive them. Migrate Connector passes messages to Transformation Manager only for workloads in the appropriate project.

To enable event messaging for migration jobs on the Migrate server:

  1. Set up your PlateSpin Migration Factory environment.

    See PlateSpin Migration Factory in the PlateSpin Transformation Manager 2 Administrator Guide.

  2. As the Administrator user, open TCP port 61613 for incoming STOMP traffic on the Migrate server host.

  3. (Azure) For a cloud-based Migrate Server in Azure, allow inbound connections for STOMP traffic (TCP port 61613) in the Migrate server’s Network Security Group.

  4. Open TCP port 61613 in your network.

    See Requirements for Event Messaging.

  5. In PlateSpin Transformation Manager, configure the PlateSpin Migrate server as a Migration Server resource for a transformation project.

    The PlateSpin Migrate Connector subscriber component registers automatically with RabbitMQ on the PlateSpin Migrate server.

    See Managing Migration Server Resources in the PlateSpin Transformation Manager 2 User Guide.

  6. (PTM Automated Mode) In PlateSpin Transformation Manager, configure one or more workload Transformation Plans to use the Migration Server resource you created, or use Auto-Assign to allow it to be considered from among the pool of Migrate servers that you have similarly configured.

  7. (PTM Planning Mode) In PlateSpin Transformation Manager, import the workloads that you configure for migrations manually in PlateSpin Migrate. The Migrate Connector scans periodically to match the external migrations to the imported workloads, and status information is tracked for them.

  8. Begin workload migrations.

    Whether the execution is automated or manual, the Migrate server generates event messages for workload migration actions performed on that server. RabbitMQ publishes the messages. Migrate Connector receives the messages and passes them to the appropriate project in Transformation Manager, where they are displayed for tracking progress and reporting status.