Table of Contents

Search

  1. Preface
  2. Analyst Service
  3. Catalog Service
  4. Content Management Service
  5. Data Integration Service
  6. Data Integration Service Architecture
  7. Data Integration Service Management
  8. Data Integration Service Grid
  9. Data Integration Service Applications
  10. Data Preparation Service
  11. Enterprise Data Lake Service
  12. Informatica Cluster Service
  13. Mass Ingestion Service
  14. Metadata Access Service
  15. Metadata Manager Service
  16. Model Repository Service
  17. PowerCenter Integration Service
  18. PowerCenter Integration Service Architecture
  19. High Availability for the PowerCenter Integration Service
  20. PowerCenter Repository Service
  21. PowerCenter Repository Management
  22. PowerExchange Listener Service
  23. PowerExchange Logger Service
  24. SAP BW Service
  25. Search Service
  26. System Services
  27. Test Data Manager Service
  28. Test Data Warehouse Service
  29. Web Services Hub
  30. Application Service Upgrade
  31. Appendix A: Application Service Databases
  32. Appendix B: Connecting to Databases from Windows
  33. Appendix C: Connecting to Databases
  34. Appendix D: Updating the DynamicSections Parameter of a DB2 Database

Before You Create the Data Preparation Service

Before You Create the Data Preparation Service

Before you create the Data Preparation Service, complete the prerequisite tasks for the service.
Perform the following tasks before you create the Data Preparation Service, if Oracle is the database for the Data Preparation Service Repository:
  • Set up the Oracle server database version 12cR2 or 11gR2 that the Data Preparation Service connects to. Ensure that the database is case insensitive.
  • Set up the required user account for the Oracle database with create, drop, and alter permissions for tables and views.
Perform the following tasks before you create the Data Preparation Service, if MySQL is the database for the Data Preparation Service Repository:
  • Set up the MySQL server database version 5.6.26 or above that the Data Preparation Service connects to. Ensure that the database is case insensitive. For MySQL version 5.6.26 and above, set lower_case_table_names=1 and for MySQL version 5.7 and above, set explicit_defaults_for_timestamp=1 in the my.cnf file.
  • Set up the required user account for the MySQL database with create, drop, and alter permissions for tables and views.
If the domain is secure, you must secure the services that you create for use by
Enterprise Data Lake
.
  • The following services in the domain and the YARN application must share the same common truststore file:
    • Data Integration Service
    • Model Repository Service
    • Catalog Service
    • Data Preparation Service
    • Enterprise Data Lake Service
  • The Data Preparation Service and
    Enterprise Data Lake Service
    must also share the same keystore file.
  • You can use different keystore files for the Data Integration Service, Model Repository Service, and Catalog Service. If you use different keystore files, you must add certificates corresponding to each of the keystores into a common truststore file.
  • If you have configured
    Enterprise Data Lake
    with one primary node and one or more backup nodes, you must copy the truststore files to a common directory and specify the same directory path for all nodes assigned to
    Enterprise Data Lake
    .