Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Data Replication 9.8.0
  • All Products

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

User Guide

User Guide

Back Next

Importing a Configuration File

Importing a Configuration File

You can import a configuration file in XML or SQLite database format for Server Manager use. The file can be from the local replication environment or from another replication environment.
For example, you can import a configuration .xml file that you created in a test environment for use in the production environment.
If you import a configuration that has multiple targets, Data Replication skips information about the secondary targets and imports information only for the primary target.
  1. On the
    Server Manager
     tab >
    Configs
     view, click the
    Import
     icon button on the Replication Configurations toolbar.
    The
    Import Configuration
     dialog box appears.
  2. In the
    Name
     field, enter a name that you want to use for the imported configuration file.
    Configuration names are not case-sensitive. They can contain the digits 0-9, Latin letters A-Z and a-z, and the underscore (_) character. The Data Replication Console truncates configuration names that are longer than 100 characters.
  3. In the
    Owner
     list, select the configuration owner.
    If you are a regular non-administrative user and select idradmin as the owner, you will not be able to edit the configuration later.
  4. For the
    File path
     field, click the
    Browse
     button to browse to the configuration file that you want to import.
  5. In the
    File System for Server Manager 'name'
     dialog box, perform the following substeps:
    1. To filter the configuration files, enter a configuration name mask in the
      Filter
       field.
      You can use the asterisk (*) wildcard in the mask.
    2. Select one of the following options to indicate the format of the configuration files to display in the directory tree:
      • *.xml files
         to display only XML configuration files
        On Solaris systems only, the directory from which you import the XML configuration file must also contain the config.xsd schema file.
      • *.db files
         to display only SQLite configuration files
    3. In the directory tree, select the configuration file that you want to import.
      The
      File
       field displays the configuration file name.
    4. Click
      OK
      .
  6. If you want to remove replication processing information for all replication tasks from the configuration, select the
    Clean Configuration
     check box.
  7. Select the source server from the
    Source Server Manager
     list. Then select the environment variables list for the source from the
    Runtime environment
     list on the left.
  8. Select the target server from the
    Target Server Manager
     list. Then select the environment variables list for the target from the
    Runtime environment
     list on the right.
  9. In the
    Source Database Connection
     and
    Target Database Connection
     lists, select a connection that has been defined for the source database or target database in the destination environment or retain the default value of
    <connection from config>
    .
    If you use
    <connection from config>
    , the Console uses the imported connection information to generate a connection with a name that has the following format: <
    configuration_name
    >_source_connection or <
    configuration_name
    >_target_connection.
  10. Click
    OK
    .
    The
    Report of Operation
     dialog box displays the status of each import operation. Statuses are: done, failed, or skipped. The
    Total
     row indicates whether the overall configuration import operation succeeded.
  11. If the import succeeded, click
    Close
    .
    The configuration appears on the
    Server Manager
     tab >
    Configs
     view, and the Data Replication Console opens the imported configuration in Edit mode.
    If the import failed, resolve any issues and try to import the configuration again.
  12. Save the imported configuration to complete the import operation.
0 COMMENTS
We’d like to hear from you!