One-Click Migration from Test Environment to Production Environment

Applicable Scenarios

The test environment and production environment are separated. Report creators develop reports in the test environment and migrate them to the production environment with one click after development is complete.

Prerequisites

Two interconnected environments are available: one test environment and one production environment.

One-Click Migration Rules

The Role Used for Migration Is Administrator

Different levels of control:
The test and production environments require different levels of control. The production environment should be strongly controlled. To avoid interference from the test environment and prevent arbitrary content from being published, ordinary users should develop and test reports in the test environment.
Release admission rules:
When testing is complete and resources need to be migrated to the production environment, they should pass system administrator approval or review. Currently, this is handled by notifying the administrator to publish. Building a full approval process inside BI would be too heavy and is outside the BI scope, so administrators should handle publishing.
Different user roles in the two environments:
In the production environment, most users should only view data, meaning they are read-only users. This helps keep the test and production environments consistent. Resource permissions in the production environment should also be distributed by administrators or group administrators.

Resources Supported for Migration

✅ Data accounts
✅ Datasets (self-built datasets, excluding ETL datasets)
✅ ETL
✅ Dashboards
✅ Data screens
✅ Web apps
✅ Mobile apps
Enterprise resources
✅ Global parameters and custom regions
✅ Custom maps
✅ Enterprise color schemes and theme colors
Visualization plugins
✅ Dashboards, data screens, and ETL are published to their original paths

Publishing Path Notes

Resources are published to their original paths. If the original path cannot be found, the system creates the resource under the corresponding root directory.

During the first publish, publish pages to their original page paths as much as possible. If a folder with the same name does not exist, create the directory and publish the resource there.

Recent Best Practice Example

1. Application scenario characteristics:

For group-style businesses, test and production environments are separated. The goal is to enable all employees to use data, promote self-service analysis, and separate creators from viewers.

2. User and environment usage characteristics:

Test environment: mostly used by data creators to promote self-service analysis. Because this environment runs many ETL tasks and query tasks, the machine configuration may be relatively high. It usually has more ordinary users.

Production environment: mostly used by data consumers, mainly middle and senior managers, to view the reports they need in BI. Performance must be guaranteed to provide a better product experience. It usually has more read-only users.

This solution is also suitable when the test and production environments need to be strongly separated to meet unified IT control requirements.

3. Best practice:

Promote self-service analysis in the test environment. Prepare the corresponding base datasets and self-service analysis datasets so users with self-service analysis capabilities can explore and practice fully in the test environment. Content with practical value can then be published to the production environment.

In the production environment, publish only the dashboards that are truly needed for daily use. This prevents interference with daily work and avoids resource consumption and visual clutter caused by many invalid dashboards or personal test dashboards, keeping the production environment as concise as possible.

Data Migration Methods

Quick One-Click Migration (Version 4.8 and Later)

Enable One-Click Publishing

On the O&M management page, decide whether to expose this feature in the administrator interface by enabling the One-Click Publish button.

Migration Settings

Administrators can configure this by following this path: Admin Settings - System Management - Advanced Settings - Migration Settings. Enable one-click migration so that migration buttons appear on pages such as dashboards, datasets, ETL, data screens, Web apps, and light apps. After the target environment account and password are configured, click Test to run a connection test.