How to migrate configurations between environments
Applies to Write-Back Server
Summary
We are actively working on ways to improve this process and automate it as part of the product road map. As of now this is the procedure required to migrate configurations between environments.
Write-Back is an agile tool that can be used by the Tableau Creators and Explorers to allow inputs on dashboards created. This means that depending on the usage Write-Back datasets might be created directly in production. In this case the typical promotion between environments is not applicable and the test or qa environment will be mainly used to test product upgrades. Please ensure that based on Write-Back usage at your organization you follow the right procedure.
This article describes how the Write-Back setup and configurations can be migrated between environments. This type of data is stored:
Setup Information - Is stored inside the Write-back manager and then converted to files that are placed on Write-Back server for a proper execution. Typically some of these settings will change from one environment to another as they contain, addresses, certificates, IPs, etc that are environment dependent.
Configurations - These correspond to all the metadata that allows to drive datasets, define user roles for authorization, etc, and is stored on Write-Back internal database. These configurations don't have reference to environments so they can be transferable between environments without any changes.
Tableau dashboards (trex) - Inside each Tableau dashboard is stored the URL to reach Write-Back, the URL is placed there by adding the trex file to the dashboard.
Data set tables and data - The actual data inside the datasets as well as the table structure is stored on the database that you have configured on Write-Back and typically it will be external to Write-Back.
More details are available here: