Re-platforming TIBCO EMS to Amazon MQ - Amazon MQ
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Re-platforming TIBCO EMS to Amazon MQ

You can use the following procedure to migrate the TIBCO EMS architecture shown here to an equivalent Amazon MQ architecture without impacting App 1 or App 2:

  1. Create an active/standby broker in us-east-1 and another in us-east-2 named as AMQ_ORANGE and AMQ_APPLE.

  2. Create a Network Bridge between 2 brokers by adding a duplex network connector definition to one of the queues:

    <networkConnectors> 
    <networkConnector duplex="true" name="connector_AMQ_ORANGE_to_AMQ_APPLE" uri="masterslave:(ssl://b-d63bcc4d-682b-40a2-8227-31386bcf1e3d-1.mq.us-east-2.amazonaws.com:61617,ssl://b-d63bcc4d-682b-40a2-8227-31386bcf1e3d-2.mq.us-east-2.amazonaws.com:61617)" userName="amqadmin"/> 
</networkConnectors>

    After the reboot of AMQ_ORANGE, there should be a Network Bridge created between both brokers as illustrated below: Network Bridges table showing one remote broker AMQ_APPLE with TCP address and no messages.

    Note

    Steps 1 and 2 can be replicated using a Amazon CloudFormation template. For more information about using Amazon CloudFormation to set up Amazon MQ brokers, see the Amazon MQ Amazon CloudFormation Template Reference.

  3. Retrieve the list of static TIBCO EMS server destinations from the config files, queues.conf and topics.conf or by using the following tibemsadmin commands: 

    show queues * static
show topics * static

    When finished, update the Amazon MQ broker AMQ_ORANGE configuration file to add startup destinations as shown here: 

    <destinations>
    <queue physicalName="FOO.BAR"/>
    <topic physicalName="SOME.TOPIC"/>
</destinations>

  4. Destination properties for TIBCO EMS can be found in queues.conf and topics.conf files. Per Destination level Policy can be set in Amazon MQ using the destinationPolicy section in the configuration file.

  5. Retrieve the list of TIBCO EMS Bridges from bridges.conf. For example, the Bridge from source topic NOTIFY.FOOBAR to target queues FOO and BAR is shown as: 

    [topic:NOTIFY.FOOBAR]
queue=FOO
queue=BAR

    When finished, up the Amazon MQ broker AMQ_ORANGE configuration file to add Composite Destinations that match TIBCO EMS bridges.

    Note

    Simple Topic to Queue bridges are needed in TIBCO EMS to support m-hop routing. In Amazon MQ this is not needed and queues can be used directly with a Network of Brokers.