Migrating ThingWorx Flow
You can migrate ThingWorx Flow 8.4.x installed on one machine to ThingWorx Flow 8.5.x installed on a separate machine by exporting the storage from ThingWorx Flow 8.4.x and importing it in ThingWorx Flow 8.5.x.
 |
For the purpose of this document, assume that the machine where ThingWorx Flow 8.4.x is installed is Machine A, and the machine where ThingWorx Flow 8.5 is installed is Machine B.
|
Prerequisites
Before you migrate ThingWorx Flow, ensure that you meet the following prerequisites:
• On machine A, there is an installation of ThingWorx Flow 8.4.x with different workflows that are created using different connections, triggers, authorizations and contain conditions, loops, custom actions, private connections (using users) and so on.
• On machine B, there are the necessary privileges to install ThingWorx Foundation and ThingWorx Flow.
• The appropriate ThingWorx Foundation 8.5.x version is downloaded from the PTC Software Downloads website.
• The appropriate ThingWorx Flow 8.5.x version is downloaded from the PTC Software Downloads website.
The main steps of the process follow:
Step 1: Export ThingWorx Flow data to ThingWorx Storage
1. On machine A, log in to ThingWorx Composer as Administrator. Ensure that the Administrator belongs to the Administrators group.
2. Click > . The Export window opens.
3. In the Export Option list, select To Thingworx Storage.
4. Select the Universal Export check box to ensure that sensitive information is not exported.
5. Click Export. The exported folder named with current timestamp is created under <Thingworx_installation_path>\ThingWorx<DBtype>-<8.4.x>\ThingworxStorage\exports folder.
6. From <Thingworx_installation_path>\ThingWorx<DBtype>-<8.4.x>\ThingworxStorage\logs, open the relevant ApplicationLog.log file to verify that the export process completed successfully.
7. Back up the exported folder to a different machine or storage.
Step 2: Install ThingWorx Foundation and ThingWorx Flow on machine B
|
|
You can install ThingWorx Foundation and ThingWorx Flow on the same machine, or you can install them on different machines. However, ensure that ThingWorx Foundation and ThingWorx Flow are installed on the same domain.
|
3. Start the ThingWorx Flow server
4. Run the LoadOAuthConfiguration service in ThingWorx Composer to load OAuths to the ThingWorx Flow server.
(Optional) Step 3: Deploy custom connectors on machine B
|
|
Complete the steps in this section only if you have developed custom connectors using the ThingWorx Flow SDK.
|
1. Copy the custom connector source code to Machine B.
2. Navigate to the root directory of the connector and run the flow-deploy connector command.
For more information, see Deploying Connectors.
3. Run the following command to seed the custom connector in the database:
flow-deploy migrate -u <Flow DB username> -p <Flow DB password> -s <Flow installation Directory>
Step 4: Import the exported data to the ThingWorx Foundation 8.5.x installation on machine B
1. Copy the backed up exported storage folder from Step 1 to <Thingworx_installation_path>\ThingWorx<DBtype>-<8.5.x>\ThingworxStorage\exports on machine B.
2. On machine B, log in as Administrator to ThingWorx Composer. Ensure that the Administrator belongs to the Administrators group.
3. Click > . The Import window opens.
4. In the Import Option list, select From Thingworx Storage.
5. Select the folder that you copied to <Thingworx_installation_path>\ThingWorx<DBtype>-<8.5.x>\ThingworxStorage\exports.
6. Click Import.
7. From <Thingworx_installation_path>\ThingWorx<DBtype>-<8.5.x>\ThingworxStorage\logs, open the relevant ApplicationLog.log file to verify that the import process completed successfully.
(Optional) Step 5: Make configuration changes to ThingWorx Foundation and ThingWorx Flow
If needed, proceed to make configuration changes to the ThingWorx Foundation and the ThingWorx Flow services. For ThingWorx Flow information, see Administering ThingWorx Flow. For information about ThingWorx Foundation updates, see ThingWorx Configuration Resources.
Step 6: Update authorizations, connections, and triggers on machine B
1. On machine B, log in to ThingWorx Flow as Administrator.
2. On the ThingWorx Flow dashboard, click the user menu 
in the header, and then click Settings.
in the header, and then click Settings.3. Verify that all authorizations, connections and triggers are imported. Notice that each item has a 
icon in front of them. This indicates that they are incompletely configured since sensitive information was not exported, which is the result of selecting Universal Export during export.
icon in front of them. This indicates that they are incompletely configured since sensitive information was not exported, which is the result of selecting Universal Export during export.4. Edit all authorizations and connections, and provide correct credentials for each authorization and connection.
5. Edit all triggers to provide appropriate authorization or connection, and provide lookup information.
Step 7: Verify that all ThingWorx Foundation and ThingWorx Flow data Is imported, and workflows can be executed on machine B
1. On machine B, log in to ThingWorx Composer as Administrator.
2. In ThingWorx Composer, browse to Things and make sure that workflows under the Thing entities are imported.
3. On the ThingWorx Flow dashboard, verify that all workflows are imported.
Alternatively, open the Workflows entity, click Services and open any service. The workflow should appear and execute correctly.
4. Open the workflows and verify that you can edit and execute them.
5. Verify that triggers are working correctly.
6. Verify that you can create a workflow, and while creating the workflow, add a category in the Workflow Editor.
You successfully migrated ThingWorx Flow to machine B.