ThingWorx Flow > ThingWorx Flow Installation and Administration > Moving ThingWorx Flow Preproduction System Data to Production
Moving ThingWorx Flow Preproduction System Data to Production
Prerequisites
Before you move data from your ThingWorx Flow preproduction system to production, ensure that you meet the following prerequisites:
• You have a ThingWorx Flow preproduction system with different workflows that use connections or authorizations.
• You have necessary privileges to export data from your preproduction ThingWorx Flow system.
• You have installed ThingWorx Flow on a production system and performed the following tasks, if required:
◦ Uploaded customization metadata files of the third-party service to the ThingWorx Flow server.
◦ Updated all ThingWorx Flow configuration settings similar to what you had in the preproduction server. For example, modifications to trigger polling time.
◦ Imported ThingWorx Flow SSL certificates to the Java TrustStore of your third-party service.
◦ Customized the third-party service to ensure correct workflow execution.
Process
Complete the following steps to move a ThingWorx Flow preproduction system to production:
1. Compile the list of authorizations and connections that are used in your workflows in the preproduction system.
2. Define authorizations and connections in the production system with the same names as in the preproduction system. Ensure that you specify the correct production URLs and account credentials, or application keys for authentication.
For more information about creating authorizations and connections, see Creating and Managing Authorizations and Creating and Managing Connections.
3. From ThingWorx Composer in the preproduction system, perform a Universal Export of the ThingWorx Flow data. For more information, see Importing and Exporting Data, Entities, and Extensions.
Only authorization and connection names are exported. Other details, such as URL, user name, password, or application key are not exported.
4. Import the exported ThingWorx Flow data from the preproduction system to the production system. With the import process, the following tasks are performed:
◦ The authorizations and connections that you created in the production system are automatically linked to be used in the exported workflows from the preproduction system. This works only if you define authorizations and connections with the same name as in the preproduction system.
◦ Custom actions that are used in workflows in the preproduction system are available for use in the workflows in the production system.
5. Verify that all workflows are imported, and they are using the connectors that you defined in step 2.
Was this helpful?