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

Creating a Source or Target Connection from the Server Manager Tab

Creating a Source or Target Connection from the Server Manager Tab

You can create a source or target connection under a unique name from the
Server Manager
 tab >
Connections
 view.
  1. On the
    Server Manager
     tab >
    Connections
     view, click the
    New
     icon button on the Connections toolbar.
    The
    New
     dialog box appears.
    For the Oracle connection type only, the
    New
     dialog box contains a
    Database
     tab and an
    ASM Settings
     tab.
  2. Enter the database connection information.
    The following table describes the fields for all source and target connection types:
    Field
    Source and Target Types
    Description
    Usage
    Name
    All
    A unique name for the connection.
    Required. Connection names can contain the digits 0-9, Latin letters A-Z and a-z, and the underscore (_) character. The Data Replication Console truncates connection names that are longer than 120 characters.
    Owner
    All
    The Data Replication user who is designated as the owner of the connection.
    Required.
    The idradmin user can use any predefined connection.
    Type
    All
    The source or target type. Options are:
    • Amazon Redshift
    • Apache Kafka
    • Cloudera
    • DB2 for LUW
    • Flat File
    • Greenplum
    • Hortonworks
    • Microsoft SQL Server
    • MySQL
    • Netezza
    • Oracle
    • PostgreSQL
    • Teradata
    • Vertica
    Required.
    Version
    • Cloudera
    • Hortonworks
    The version of the selected target type.
    Required.
    Host
    All, except for
    Apache Kafka
     and
    Flat File
    The host name or IP address of the machine where the source or target runs.
    Required.
    Port
    All, except for
    Apache Kafka
     and
    Flat File
    The port number that Data Replication uses to connect to the source or target. Valid values are integers from 1 through 65535. The value that is displayed by default depends on the
    Type
     value.
    Required.
    User
    All, except for
    Apache Kafka
     and
    Flat File
    A user name that has the authority to write to the source or target.
    Required.
    Password
    All, except for
    Apache Kafka
     and
    Flat File
    A valid password for the specified user.
    Required.
    Path
    • Cloudera
    • Hortonworks
    The HDSF directory that contains the data files that Data Replication generates.
    Required.
    The user ID that you specify for connecting to HDFS must have write permissions on this directory.
    To browse HDFS, the Data Replication Console requires Java Runtime Environment (JRE) 1.7 or 1.8.
    Instance/DB
    • Amazon Redshift
    • DB2 for LUW
    • Greenplum
    • PostgreSQL
    • Netezza
    • Oracle
    • Vertica
    An Oracle instance name or a database name.
    Required if this field is displayed for the selected database type.
    Use Custom URL
    All, except for
    Apache Kafka,
     Cloudera and Hortonworks
    Select this check box to provide custom connection strings for the JDBC or ODBC drivers. Use custom connection strings in the following situations:
    • You use a Data Source Name (DSN) with an ODBC driver to connect to the source or target.
    • You use a user name for connecting to the source or target from the Data Replication Console that is different from the user name under which the replication job runs.
      In this case, the user that connects to the source or target from the Data Replication Console must have privileges to read metadata. Also, the user that connects to the source or target when the replication job runs must have privileges to write DML changes to the target.
    • Multiple ODBC driver versions are installed on one Windows system. In this case, specify the name of the driver that you want to use in the
      Custom connection string
       field.
    After you select this check box, the
    JDBC custom URL
     and
    Custom Connection String
     fields become available.
    For a DB2 source connection, select this check box if you need to specify an authentication method in a connection string.
    JDBC custom URL
    All, except for
    Apache Kafka,
     Cloudera and Hortonworks
    A connection URL for the JDBC driver that the Data Replication Console uses. This URL has the following format:
    jdbc:
    <subprotocol>
    :
    <subname>
    This field is available only if you selected
    Use custom URL
    .
    JDBC custom connection strings always use the values that are specified in the
    User
     and
    Password
     fields. Ensure that any JDBC custom connection string that you enter does not include a user name and password.
    The Data Replication Console does not validate JDBC custom connection strings. Ensure that any JDBC custom connection string that you enter is valid for the current connection.
    Custom Connection String
    All, except for
    Apache Kafka,
     Cloudera and Hortonworks
    A connection string for the ODBC driver that the Applier uses to access the source or target.
    If you use an ODBC Data Source Name (DSN) to connect to the source or target, provide the DSN connection string.
    On Windows, if you installed multiple ODBC driver versions on one system, use this setting to specify a name for the driver that you want to use.
    This field is available only if you selected
    Use Custom URL
    .
    Ensure that any custom connection string that you specify includes a user name that has the authority to write to the target database. A custom connection string can include the password for this user, or you can specify the password in the
    Password
     field. If you specify the password in both the custom connection string and
    Password
     field, Data Replication uses the password in the custom connection string.
    For Microsoft SQL Server Cluster sources and targets, provide the connection string in the following format: 
    DRIVER=
    SQL_Server_ODBC_driver
    ;Server=
    virtual_IP
    ;Network=DBMSSOCN;Trusted_Connection=Yes;Port=
    port
    ;Address=
    virtual_IP,port
    ;
    For Oracle sources, if the Extractor fails to connect to the source by using the custom connection string, the Extractor tries to connect to the source again. For the second connection attempt, the Extractor builds the connection string based on the database connection or the connection information that you manually enter. To disable connection retries, set the
    global.fallback_connection
     runtime parameter to 0.
    For DB2 sources that use UTF-8 accented and non-Latin characters, if you run InitialSync on Linux or UNIX, add the
    IANAAppCodePage
     parameter to the connection string with a setting of 106. For example: 
    DRIVER={DB2};IpAddress=
    IP_address
    ;port=
    port
    ;UID=
    user
    ;
PWD=
    password
    ;Database=
    db_name
    ;IANAAppCodePage=106
    For Oracle targets, if the Applier fails to connect to the target by using the custom connection string, the Applier tries to connect to the target again. For the second connection attempt, the Applier builds the connection string based on the database connection or the connection information that you manually enter. To disable connection retries, set the
    global.fallback_connection
     runtime parameter to 0.
    For Teradata targets, if you use a version of the Teradata ODBC driver that is earlier than 15.00.00.04 and include special characters in the user name or password for connecting to the target, you must specify a custom connection string. In the connection string, enclose the user ID or password that contains the special characters with double quotation marks.
    The Data Replication Console does not validate ODBC custom connection strings. Ensure that any ODBC custom connection string that you enter is valid for the current database connection.
    Connect directly
    Oracle
    Reserved for future use.
    -
    Force log switch
    Oracle
    Select this check box if you capture data only from Oracle archived redo logs in a RAC environment.
    Required for Oracle RACs. The Extractor issues the command to archive online redo logs prior to capturing the change data.
    Use SID instead of SERVICE_NAME
    Oracle
    Select this check box to use the Oracle SID instead of the SERVICE_NAME to build the connection string.
    Optional for Oracle connections.
    Use SSL
    • Amazon Redshift
    • Greenplum
    Select this check box to use an HTTPS connection that is secured by the Secure Sockets Layer (SSL) to safely send SQL requests to Amazon Redshift or Greenplum targets.
    If you clear this check box, Data Replication uses a connection that is not secured by SSL. Transmission of SQL requests to Amazon Redshift or Greenplum targets is insecure.
    Data Replication always uses a secure HTTPS connection to load source data to the Amazon Simple Storage Service (Amazon S3).
    If the source or target is in an Oracle RAC, you can enter connection information for any running Oracle instance in the RAC.
  3. Click
    Test Connection
     to verify the database connection.
  4. If you use Oracle ASM, configure a connection to an Oracle ASM instance. Click the
    ASM Settings
     tab and then enter ASM connection information. For more information, see Configuring a Connection to an Oracle ASM Instance.
  5. Click
    OK
     to save the connection under the specified name.
    In the
    Connections
     view, the new connection appears in the connections list under the appropriate database type.
0 COMMENTS
We’d like to hear from you!