Table of Contents

Search

  1. Preface
  2. Data Replication Overview
  3. Understanding Data Replication
  4. Sources - Preparation and Replication Considerations
  5. Targets - Preparation and Replication Considerations
  6. Starting the Server Manager
  7. Getting Started with the Data Replication Console
  8. Defining and Managing Server Manager Main Servers and Subservers
  9. Creating and Managing User Accounts
  10. Creating and Managing Connections
  11. Creating Replication Configurations
  12. Materializing Targets with InitialSync
  13. Scheduling and Running Replication Tasks
  14. Implementing Advanced Replication Topologies
  15. Monitoring Data Replication
  16. Managing Replication Configurations
  17. Handling Replication Environment Changes and Failures
  18. Troubleshooting
  19. Data Replication Files and Subdirectories
  20. Data Replication Runtime Parameters
  21. Command Line Parameters for Data Replication Components
  22. Updating Configurations in the Replication Configuration CLI
  23. DDL Statements for Manually Creating Recovery Tables
  24. Sample Scripts for Enabling or Disabling SQL Server Change Data Capture
  25. Glossary

Creating a Configuration for Replicating Data to Multiple Targets

Creating a Configuration for Replicating Data to Multiple Targets

From the Informatica Data Replication Console, you can create a configuration that replicates data to multiple targets.
Data Replication does not support replicating data from a single source to multiple Amazon Redshift or Apache Kafka targets.
On the
Target Database
tab, select the connection that you previously defined for the primary target on the
Server Manager
tab >
Connections
view. Then add the secondary targets on the
Routing
tab.
Instead of creating a new configuration, you can modify an existing configuration file that has a single target. In this case, you must rename the target schema for each secondary target to a name that matches the schema name of the primary target.
  1. In the
    Server Manager
    tab >
    Configs
    view, click
    New
    on the main toolbar.
  2. On the
    Source Database
    tab, connect to the source database.
  3. On the
    Target Database
    tab, in the
    Connections
    list, select the connection that you defined for the primary target.
  4. Map tables and columns, set the extract range, and enter runtime and logging settings, as usual.
  5. Save the configuration and switch to
    Edit
    mode.
    The
    Routing
    tab becomes available.
  6. On the
    Routing
    tab, specify the Server Manager subserver and connection for a secondary target:
    1. Click
      New
      .
    2. In the
      New
      dialog box, select the Server Manager subserver and database connection that you previously defined for the target.
    3. Click
      OK
      .
    The target appears in the upper list box on the
    Routing
    tab.
    The following image shows the
    Routing
    tab with the secondary target:
    Routing tab with the secondary target in the upper list box
    If the target type uses a recovery table, the Data Replication Console prompts you to specify the recovery table name and schema.
  7. To define a recovery table for a target, enter the schema name and recovery table name in the appropriate fields. Then click
    OK
    .
    When you start the Applier later, it generates the recovery table on the target.
    Create a separate recovery table for each target.
  8. Repeat Step 6 for each secondary target. For each secondary target that uses a recovery table, also repeat Step 7.
From the subtabs on the
Routing
tab, you can filter table rows, exclude tables, and override the apply mode and log table schema for a secondary target.

0 COMMENTS

We’d like to hear from you!