Prepare Clients for Migration/Side-by-Side Upgrade (MFT)

Configure and prepare your clients such that the transition of HTTP clients from the old deployment to the new deployment is smooth and happens by switching the DNS entry.

These changes can be done gradually over time because after these changes are completed everything continues to work as before the changes. This includes some changes to the source environment.

To prepare clients:

1. Get a DNS name issued from DNS issuing authority. Point this DNS name to the source environment load balancer.

   If you are already using a DNS name in clients skip this step. This step is required only if you are using an Oracle Traffic Director (OTD) IP address.

2. Create a new port in the source environment load balancer that matches the target MFT Cloud Service port number. Add routing role to this new port to route to the original load balancer port in the source environment.

   Note that on-premises MFT applications can use a different port number than the target MFT Cloud Service environment. This makes it impossible to switch clients during transition from the old to the new deployment by switching the DNS.

3. Change all clients to use the DNS name and new port.

   Note that the DNS name will also be used by clients of the embedded FTP and SFTP server that write files.

   For SSL, it might be required that the trust certificate for the target environment server has to be pre-configured at the client so that transition from the source to the target environment works smoothly.