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

Domain Selection

Domain Selection

After you review the Pre-Installation summary, you can enter the domain information.
  1. Press
    1
    to create a domain.
    When you create a domain, the node that you create becomes a gateway node in the domain. The gateway node contains a Service Manager that manages all domain operations.
  2. Select whether you want to enable secure communication for services in the domain.
    1. Press
      1
      to disable secure communication for the domain.
    2. Press
      2
      to enable secure communication for the domain.
    By default, if you enable secure communication for the domain, the installer sets up an HTTPS connection for the Informatica Administrator. You can also create a domain configuration repository on a secure database.
  3. Specify the connection details for Informatica Administrator.
    1. If you do not enable secure communication for the domain, you can specify whether to set up a secure HTTPS connection for the Informatica Administrator.
      The following table describes the options available to enable or disable a secure connection to Informatica Administrator:
      Option
      Description
      Enable HTTPS for Informatica Administrator
      Set up a secure connection to Informatica Administrator.
      Disable HTTPS
      Do not set up a secure connection to Informatica Administrator.
    2. If you enable secure communication for the domain or if you enable HTTPS connection for the Informatica Administrator, enter the keystore file and port number for the HTTPS connection to Informatica Administrator.
      The following table describes the connection information you must enter if you enable HTTPS:
      Option
      Description
      Port
      Port number for the HTTPS connection.
      Keystore file
      Select whether to use a keystore file generated by the installer or a keystore file you create. You can use a keystore file with a self-signed certificate or a certificate signed by a certification authority.
      1 - Use a keystore generated by the installer
      2 - Specify a keystore file and password
      If you select to use a keystore file generated by the installer, the installer creates a self-signed keystore file named Default.keystore in the following location:
      <Informatica installation directory>/tomcat/conf/
    3. If you specify the keystore, enter the password and location of the keystore file.
    4. If you enabled secure communication for the domain, the
      Domain Security - Secure Communication
      section appears.
    5. If you did not enable secure communication for the domain, the
      Domain Configuration Repository
      section appears. Skip to Domain Configuration Repository.
  4. Select whether to enable SAML authentication to configure Security Assertion Markup Language (SAML)-based single sign-on (SSO) support for web-based Informatica applications in an Informatica domain.
    Press
    1
    to disable SAML authentication and skip to Domain Security - Secure Communication. Press
    2
    to enable and configure SAML authentication.
  5. Enter the Identity Provider URL for the domain.
  6. Specify the relying party trust name or the service provider identifier for the domain as defined in the identity provider. If you choose No, the service provider identifier is set to "Informatica" .
  7. Specify whether IdP will sign SAML assertion or not.
  8. Enter the identity provider assertion signing certificate alias name.
  9. Select whether to use the default Informatica SSL certificates or to use your SSL certificates to enable SAML authentication in the domain.
    The following table describes the SSL certificate options for SAML authentication:
    Option
    Description
    Use the default Informatica SSL certificate file.
    Select to use the default Informatica truststore file for SAML authentication.
    Enter the location of the SSL certificate file.
    Select to use a custom truststore file for SAML authentication. Specify the directory containing the custom truststore file on gateway nodes within the domain. Specify the directory only, not the full path to the file.
  10. If you provide the security certificates, specify the location and passwords of the keystore and truststore files.
    The following table describes the location and password of the truststore and keystore files:
    Property
    Description
    Truststore Directory
    Specify the directory containing the custom truststore file on gateway nodes within the domain. Specify the directory only, not the full path to the file.
    Truststore Password
    The password for the custom truststore file.
    Keystore Directory
    Specify the directory containing the custom keystore file.
    Keystore Password
    The password for the custom keystore file.
  11. To specify the Authentication Context Comparison, specify the strength comparison of the authentication mechanism used by the user with the IdP server.
    Supported values are MINIMUM, MAXIMUM, BETTER, or EXACT option. Default is MINIMUM.
  12. To set the Authentication Context Class, specify the expected mechanism of first time authentication of the user with the IdP server.
    Supported values are PASSWORD or PASSWORDPROTECTEDTRANSPORT. Default is PASSWORD.
  13. Specify if you want to enable the webapp to sign the SAML authentication request or not?
    Default is disabled.
  14. Specify the alias name of the private key that was imported to the node SAML keystore using which the SAML request should be signed.
  15. Specify the password to access the private key used for signing the SAML request.
  16. Specify the algorithm that the web application uses to sign the SAML request.
    Supported values are
    RSA_SHA256, DSA_SHA1, DSA_SHA256, RSA_SHA1, RSA_SHA224, RSA_SHA384, RSA_SHA512, ECDSA_SHA1, ECDSA_SHA224, ECDSA_SHA256, ECDSA_SHA384, ECDSA_SHA512, RIPEMD160, or RSA_MD5
    .
  17. Specify whether you want IdP to sign the SAML response or not?
    Choose to select to enable the webapp to receive the signed SAML response or not. Default is disabled.
  18. Specify whether IdP will encrypt SAML assertion or not.
    Select to enable the webapp to receive an encrypted SAML assertion. Default is enabled.
  19. Specify the alias name of the private key present in the gateway nodes gateway node SAML truststore that used for Informatica uses to decrypt decrypting the SAML assertion.
  20. Provide the password to access the private key to use when decrypting the assertion encryption key.
  21. Click
    Next
    .
The
Domain Security - Secure Connection
section appears.