4 Migration/Side-by-Side Upgrade for MFT Cloud Service

Learn how to migrate your on-premises MFT application to the cloud or how to do a side-by-side upgrade in the cloud for MFT Cloud Service.

Topics

• Provision MFT Cloud Service

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

• Prepare Your Source for Migration/Side-by-Side Upgrade (MFT)

• Prepare Your Target Environment (MFT)

• Test Your Production Environment (MFT)

• Transition from Old Deployment to New Deployment (MFT)

• Reconfigure Configuration Parameters and Tuning in MFT Cloud Service

• Migrate Data Components in MFT Cloud Service

Provision MFT Cloud Service

Provision a new MFT Cloud Service instance before starting the other migration and side-by-side related tasks. You’ll migrate or recreate configurations from your old source environment into this newly provisioned instance of MFT Cloud Service.

Perform the following steps:

• Provision a new Oracle MFT Cloud Service instance and configure the Oracle Cloud Infrastructure environment. Use the Oracle SOA Cloud Service provisioning wizard and select MFT Cluster as the service type. See Provision Oracle SOA Cloud Service Instances in Oracle Cloud Infrastructure in Administering Oracle SOA Cloud Service in a Customer-Managed Environment.
• Create a simple hello world application (MFT transfer) and test to make sure it works.

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.

Prepare Your Source for Migration/Side-by-Side Upgrade (MFT)

Prepare your source for migration/side-by-side upgrade by exporting or capturing the needed artifacts from the source environment.

To prepare your source:

1. Export all metadata from the source environment.

   See Importing and Exporting the MFT Configuration in Using Oracle Managed File Transfer.

   In earlier versions of MFT, a configuration plan (that the user can edit) is not generated during export. However, you’ll require a configuration plan for import. In such cases, the easiest way to generate a configuration plan is to import it into a test 12.2.1.2 deployment and generate the configuration plan from the test deployment.

2. Grab the domain file system artifacts such as Java callouts.
3. Adjust the configuration plans for deployment to MFT Cloud Service.

   Change URLs to values appropriate for MFT Cloud Service.

Prepare Your Target Environment (MFT)

Prepare your target environment by importing or recreating all the configurations of your source. This will ensure successful deployment of the target MFT Cloud Service instance.

To prepare your target environment:

1. Implement any security configurations.

   Security configurations can be: custom Oracle Web Service Manager (OWSM) policies, Credential Store Framework (CSF) keys, certificates, users, groups, custom Oracle Platform Security Service (OPSS) roles, custom OPSS permissions, group memberships, enterprise roles, OPSS credentials and so on.

   For information on OPSS commands to migrate keystores , see Managing Keystores with WLST in Securing Applications with Oracle Platform Security Services.

   For information on OPSS commands to migrate credentials, see Managing Credentials with WLST in Securing Applications with Oracle Platform Security Services.

   For information on OWSM commands to migrate custom policies, see Migrating Policies in Administering Web Services.

   Note:

   If the source environment is MFT Cloud Service, the internal LDAP data can be migrated into the target environment MFT Cloud Service instance. Migration is supported for MFT Cloud Service 12.1.3, 12.2.1 and 12.2.1.2.
2. Import artifacts with the configuration plan. Do not deploy yet.
3. Add file system artifacts captured from source environment – Java callouts.
4. Test by creating a simple hello world application (MFT transfer). Ensure that it works.
5. Set your tuning settings if they are available.
6. Redo any Enterprise Manager configuration steps manually.

   For details, see Reconfigure Configuration Parameters and Tuning in MFT Cloud Service.

7. If MFT Cloud Service is going to access endpoints on-premises then you may need VPN.

   You can setup VPN through VPNaaS.

8. Apply UMS configuration manually to the target environment.
9. Enable the embedded SFTP server by making any documented changes.

Test Your Production Environment (MFT)

You can test your production environment at this point to check if everything is working as expected after the migration. It is assumed that you have already tested in a stage system (test environment).

To test your production environment:

1. Use endpoints to test in the configuration plans of the steps that you have completed till now. Deploy and enable everything.
2. Test and check if everything is working as expected.
3. Apply tuning settings.
4. Switch to production endpoints.
   This may require projects to be redeployed with appropriate configuration plans.

Transition from Old Deployment to New Deployment (MFT)

After you have prepared your source and target environments for the migration/side-by-side upgrade, you can transition your production system from old deployment to new deployment.

To transition from old to new deployment:

1. Disable inbound sources in the source environment, if the inbound address in both old and new deployment is same.

   For inbound sources which are remote FTP/SFTP servers, ensure that already processed files in the directory are not processed again after transitioning to the target environment by removing them from the directory.

2. Complete deployment and enable everything in the target environment.

   Note that for some inbound sources, the address is different and clients have to change the address in the source and switch.

3. Switch the DNS.

   The DNS switch is not instantaneous and may take a while (depending on TTL settings in routers) to propagate across the internet.

4. Note that the source environment will continue processing backlogged transfers while new messages are processed by the target environment. When all backlogged transfers are processed and there is no need to rollback, you can destroy the source environment.
   Switch external clients of the embedded FTP and SFTP server that read files to the new deployment, after all files in the old deployment have been processed.
5. If you have directories in the embedded FTP server for storing data that is not processed by MFT, it is up to you to either copy these files or deal with them as you see fit.

Reconfigure Configuration Parameters and Tuning in MFT Cloud Service

Re-configure any tuning and configuration parameters that you had previously set in the source environment or you need to change in the target environment.

You’ll perform these steps as part of preparing your target environment for transitioning from the old to the new environment.

• Schedule Purge

• See Tuning Oracle Managed File Transfer in Fusion Middleware Tuning Performance Guide.

Migrate Data Components in MFT Cloud Service

Migrate your data components such as LDAP, OPSS and OWSM from your source to the target environment.

You’ll perform these tasks as part of preparing your target environment for transitioning from the old to the new environment.

Note:

The migration steps described here are for target version of MFT Cloud Service 12.2.1.2. If you want to do the migration for other versions, refer to the product documentation.

Move LDAP Data

The tasks for migrating LDAP data in MFT Cloud Service are similar to the tasks for migrating LDAP data in SOA Cloud Service.

See Move LDAP Data.

Move OPSS Data

The tasks for migrating OPSS data in MFT Cloud Service are similar to the tasks for migrating OPSS data in SOA Cloud Service.

See Move OPSS Data.

Move OWSM Data

The tasks for migrating OWSM data in MFT Cloud Service are similar to the tasks for migrating OWSM data in SOA Cloud Service.

See Move OWSM Data.