BladePipe 1.6.0 supports Snowflake, Hologres and CloudBerry.
跳到主要内容

Quickstart (On-Premise)

BladePipe On-Premise offers two local deployment editions: Community (free) and Enterprise. Both editions allow you to keep BladePipe and all your data securely within your own network environment.

Follow this quickstart to create your first DataJob and perform database synchronization using BladePipe On-Premise in just a few steps.

Step 1: Install BladePipe

Deploy BladePipe by following the instructions in Install All-In-One (Docker).

Alternatively, you can deploy BladePipe using the Kubernetes or Binary methods.

Step 2: Add a DataSource

  1. In the top navigation bar, click DataSource.

  2. Click Add DataSource.

  3. Configure the following information:

    • Deployment: Choose Self Maintenance or a cloud provider.
    • Type: Select your database type.
    • Host: Enter the IP Address and port necessary to connect to your DataSource.
    • Account & Password: Enter the username and password.
  4. Click Test Connection to verify your database connection.

  5. Click Add DataSource.

    Add Self-Managed DataSource MySQL

Step 3: Create a DataJob

  1. In the top navigation bar, click DataJob.

  2. Click Create DataJob.

  3. Select your added MySQL instance as both the Source and Target, and click Test Connection.

  4. Select the databases to be synchronized, and click Next.

    Select Databases for Synchronization

  5. Choose Incremental as the DataJob type, and select Initial Load. Click Next.

    Select Incremental and Full DataJob Type

  6. Select the tables you want to sync, and click Next.

    Select Tables for Database Synchronization

  7. Select all required columns, and click Next.

    Select Columns for Data Integration

  8. Click Create DataJob.

  9. Navigate to the DataJob list page to monitor the progress of your DataJob.

    Monitor DataJob Synchronization Progress

Step 4: Verify the Data

  1. Perform insert, update, and delete operations in your source database.
  2. Verify that the changes dynamically replicate to the target database and ensure data consistency.