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
  • PowerCenter 10.5.2
  • All Products

Table of Contents

Search

  1. Preface
  2. Part 1: Installation Getting Started
  3. Part 2: Before You Install the Services
  4. Part 3: Run the Services Installer
  5. Part 4: After You Install the Services
  6. Part 5: Informatica Client Installation
  7. Part 6: Uninstallation
  8. Appendix A: Starting and Stopping Informatica Services
  9. Appendix B: Connecting to Databases from UNIX or Linux
  10. Appendix C: Connecting to Databases from Windows
  11. Appendix D: Updating the DynamicSections Parameter of a DB2 Database

Installation for PowerCenter and Data Quality

Installation for PowerCenter and Data Quality

Back Next

Domain Configuration Repository

Domain Configuration Repository

After you configure domain security, you can configure domain repository details.
  1. Select the database to use for the domain configuration repository details.
    The following table lists the databases you can use for the domain configuration repository:
    Prompt
    Description
    Database type
    Type of database for the domain configuration repository. Select from the following options:
    1 - Oracle
    2 - Microsoft SQL Server
    3 - IBM DB2
    4 - Sybase ASE
    5 - PostgreSQL
    The Informatica domain configuration repository stores metadata for domain operations and user authentication. The domain configuration repository must be accessible to all gateway nodes in the domain.
  2. Enter the properties for the database user account.
    The following table lists the properties for the database user account:
    Property
    Description
    Database user ID
    Name for the domain configuration database user account.
    User password
    Password for the domain configuration database user account.
  3. Select whether to create a secure domain configuration repository.
    You can create a domain configuration repository in a database secured with the SSL protocol. To create a domain configuration repository in a secure database, press 1 and skip to step to create a domain configuration repository.
    To create a domain configuration repository in an unsecure database, press 2.
  4. If you do not create a secure domain configuration repository, enter the parameters for the database.
    1. If you select IBM DB2, select whether to configure a tablespace and enter the tablespace name.
      The following table describes the properties that you must configure for the IBM DB2 database:
      Property
      Description
      Configure tablespace
      In a single-partition database, if you select No, the installer creates the tables in the default tablespace. In a multi-partition database, you must select Yes.
      Select whether to specify a tablespace:
      1 - No
      2 - Yes
      Tablespace
      Name of the tablespace in which to create the tables. Specify a tablespace that meets the pageSize requirement of 32768 bytes.
      In a single-partition database, enter the name of the tablespace in which to create the tables.
      In a multipartition database, specify the name of the non-partitioned tablespace that resides in the catalog partition of the database.
    2. If you select Microsoft SQL Server or PostgreSQL, enter the schema name for the database.
      The following table describes the properties that you must configure for the database:
      Property
      Description
      Schema name
      Name of the schema that will contain domain configuration tables. If this parameter is blank, the installer creates the tables in the default schema.
    3. To enter the JDBC connection information using the JDBC URL information, press
      1
      . To enter the JDBC connection information using a custom JDBC connection string, press
      2
      .
    4. Enter the JDBC connection information.
      • To enter the connection information using the JDBC URL information, specify the JDBC URL properties.
        The following table describes the database connection information:
        Prompt
        Description
        Database host name
        Host name for the database.
        Database port number
        Port number for the database.
        Database service name
        Service or database name:
        • Oracle: Enter the service name.
        • Microsoft SQL Server: Enter the database name.
        • IBM DB2: Enter the service name.
        • Sybase ASE: Enter the database name.
        • PostgreSQL: Enter the database name.
        Configure JDBC Parameters
        Select whether to add additional JDBC parameters to the connection string:
        1 - Yes
        2 - No
        If you select Yes, enter the parameters or press Enter to accept the default. If you select No, the installer creates the JDBC connection string without parameters.
      • To enter the connection information using a custom JDBC connection string, type the connection string.
        Use the following syntax in the JDBC connection string:
        IBM DB2
        jdbc:Informatica:db2://<host name>:<port number>;DatabaseName=
        Oracle
        jdbc:Informatica:oracle://<host name>:<port number>;ServiceName=
        Use the following connection string to connect to the Oracle database through the Oracle Connection Manager:
        jdbc:Informatica:oracle:TNSNamesFile=<fully qualified path to the tnsnames.ora file>;TNSServerName=<TNS name>;
        Microsoft SQL Server
        jdbc:Informatica:sqlserver://<host name>:<port number>;SelectMethod=cursor;DatabaseName=
        Microsoft SQL Server with Windows NT credentials
        If you specified the Windows NT credentials for the Model repository database on Microsoft SQL Server, specify the connection string syntax to include the authentication method as NTLM.
        Microsoft SQL Server that uses the default instance with Windows NT credentials:
        "jdbc:informatica:sqlserver://<host name>:<port number>;DatabaseName=<database name>;SnapshotSerializable=true;authenticationMethod=NTLM"
        Microsoft SQL Server that uses a named instance with Windows NT credentials:
        "jdbc:informatica:sqlserver://<host name>\<named instance name>;DatabaseName=<database name>;SnapshotSerializable=true;authenticationMethod=NTLM"
        Microsoft Azure SQL
        jdbc:Informatica:sqlserver://<host name>:<port number>;SelectMethod=cursor;DatabaseName=<database name>;SnapshotSerializable=true;EncryptionMethod=SSL;HostNameInCertificate=*.database.windows.net;ValidateServerCertificate=false
        Azure SQL Database with Active Directory authentication
        jdbc:informatica: sqlserver://<host_name>:<port_number>;database=<database_name>;encrypt=true;AuthenticationMethod=ActiveDirectoryPassword;trustServerCertificate=false;hostNameInCertificate=*.database.windows.net;loginTimeout=<seconds>
        PostgreSQL
        jdbc:Informatica:postgresql://<host name>:<port number>;DatabaseName=
        Azure PostgreSQL
        jdbc:Informatica:postgresql://<host name>:<port number>;DatabaseName=<database name>;EncryptionMethod=SSL;ValidateServerCertificate=true;CryptoProtocolVersion=TLSv1.2;
        Sybase
        jdbc:Informatica:sybase://<host name>:<port number>;DatabaseName=
        Verify that the connection string contains all the connection parameters required by your database system.
  5. If you create a secure domain configuration repository, enter the parameters for the secure database.
    If you create the domain configuration repository on a secure database, you must provide the truststore information for the database.
    The following table describes the options available to create a secure domain configuration repository database:
    Property
    Description
    Database truststore file
    Path and file name of the truststore file for the secure database.
    Database truststore password
    Password for the truststore file.
    Custom JDBC Connection String
    JDBC connection string to connect to the secure database, including the host name and port number and the security parameters for the database.
    In addition to the host name and port number for the database server, you must include the following secure database parameters:
    EncryptionMethod
    Required. Indicates whether data is encrypted when transmitted over the network. This parameter must be set to
    SSL.
    ValidateServerCertificate
    Optional. Indicates whether Informatica validates the certificate that the database server sends.
    If this parameter is set to True, Informatica validates the certificate that the database server sends. If you specify the HostNameInCertificate parameter, Informatica also validates the host name in the certificate.
    If this parameter is set to False, Informatica does not validate the certificate that the database server sends. Informatica ignores any truststore information that you specify
    Default is True.
    HostNameInCertificate
    Optional. Host name of the machine that hosts the secure database. If you specify a host name, Informatica validates the host name included in the connection string against the host name in the SSL certificate.
    cryptoProtocolVersion
    Required. Specifies the cryptographic protocol to use to connect to a secure database. You can set the parameter to
    cryptoProtocolVersion=TLSv1.1
     or
    cryptoProtocolVersion=TLSv1.2
     based on the cryptographic protocol used by the database server.
    You must also provide a JDBC connection string that includes the security parameters for the database. You can use the following syntax for the connection strings:
    • Oracle:
      jdbc:Informatica:oracle://<host name>:<port number>;ServiceName=<service name>;EncryptionMethod=SSL;HostNameInCertificate=<database host name>;ValidateServerCertificate=<true or false>
    • IBM DB2:
      jdbc:Informatica:db2://<host name>:<port number>;DatabaseName=<database name>;EncryptionMethod=SSL;HostNameInCertificate=<database host name>;ValidateServerCertificate=<true or false>
    • Microsoft SQL Server:
      jdbc:Informatica:sqlserver://<host name>:<port number>;SelectMethod=cursor;DatabaseName=<database name>;EncryptionMethod=SSL;HostNameInCertificate=<database host name>;ValidateServerCertificate=<true or false>
    • Microsoft SQL Server with Windows NT credentials:
      If you have previously specified the Windows NT credentials for the Model repository database on Microsoft SQL Server, specify the connection string syntax to include the authentication method as NTLM.
      • Microsoft SQL Server that uses the default instance with Windows NT credentials:
        "jdbc:informatica:sqlserver://<host name>:<port number>;DatabaseName=<database name>;SnapshotSerializable=true;authenticationMethod=NTLM"
      • Microsoft SQL Server that uses a named instance with Windows NT credentials:
        "jdbc:informatica:sqlserver://<host name>\<named instance name>;DatabaseName=<database name>;SnapshotSerializable=true;authenticationMethod=NTLM"
    • Microsoft Azure SQL:
      jdbc:Informatica:sqlserver://<host name:port number>;SelectMethod=cursor;DatabaseName=<database name>;SnapshotSerializable=true;EncryptionMethod=SSL;HostNameInCertificate=<database host name>;ValidateServerCertificate=<true or false>
    • PostgreSQL:
      jdbc:Informatica:postgresql://<host name>:<port number>;DatabaseName=<database name>;EncryptionMethod=SSL;HostNameInCertificate=<database host name>;ValidateServerCertificate=<true or false>
    • Azure PostgreSQL:
      jdbc:Informatica:postgresql://<host name>:<port number>;DatabaseName=<database name>;EncryptionMethod=SSL;ValidateServerCertificate=true;CryptoProtocolVersion=TLSv1.2;
    The installer does not validate the connection string. Verify that the connection string contains all the connection parameters and security parameters required by your database.
  6. If the database contains a domain configuration repository for a previous domain, select to overwrite the data or set up another database.
    1. Press 1 for OK to enter the connection information for a new database.
    2. Press 2 for Continue for the installer to overwrite the data in the database with new domain configuration.
The
Domain Security - Encryption Key
 section appears.
0 COMMENTS
We’d like to hear from you!