C1: Migrating Persistence Servers with Dynamic TCP to FTL Servers

If you have Release 5.4 persistence servers that communicate using dynamic TCP transports, you can migrate them to Release 6.x FTL servers without interrupting service to clients. Complete this task.

This task refers to three persistence servers because three is the minimum number for a fault-tolerant persistence cluster. If your enterprise uses a larger cluster, generalize these instructions to the number of servers in your cluster.

Note: When migrating persistence servers with dynamic TCP, a replacement persistence service (6.x) need not remain on the same host computer as the persistence server (5.4) that it replaces. The following example consolidates persistence servers onto the realm service hosts from task B.
Before You Begin

You have installed Release 6.x on every persistence server host computer.

You have upgraded all realm servers (5.4) to FTL servers (6.x).

    Procedure
  1. Make a reference copy of the FTL server configuration file from the previous stage.
  2. Modify your working copy of the FTL server configuration file to include the three new persistence services (6.x) that will replace persistence servers (5.4).
    In the servers section, add a persistence parameters section so that each FTL server provides a persistence service. For each server, specify a unique service name from the realm's persistence cluster definition. For example: 
    globals:

    core.servers:
        ftl1: host1:8080 # 5.x client port
        ftl2: host2:8080 # 5.x client port
        ftl3: host3:8585

servers:

    ftl1:
        - realm: {}
        - persistence:
            name: psvc1
            data: /myhome/ftlserver/data

    ftl2:
        - realm: {}
        - persistence:
            name: psvc2
            data: /myhome/ftlserver/data

    ftl3:
        - realm: {}
        - persistence:
            name: psvc3
            data: /myhome/ftlserver/data
    Incorporate the other relevant persistence server command line arguments into persistence parameter sections in the configuration file.
  3. Determine which existing persistence server (5.4) is the quorum leader.
    Use the FTL server GUI to view the status of the persistence servers.
  4. Stop one of the non-leader persistence servers (5.4).
  5. Stop and restart the FTL server (6.x) that provides a persistence service to replace the stopped server (5.4).
    The FTL server will read the modified configuration file when it restarts, and provide the persistence service (6.x).
    Wait for the persistence quorum to synchronize data.
  6. Repeat steps 4 and 5 until you have replaced all the persistence servers.
    Begin by replacing all the non-leaders, and end by replacing the quorum leader.
  7. Verify that persistence clients can publish and receive messages through the persistence service.
ResultWhen these steps are complete, all three FTL servers provide a realm service and persistence service.