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. Interactive Data Preparation Service
  11. Enterprise Data Preparation 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

Configuring Developer Tool for HTTPS-enabled Metadata Access Service

Configuring Developer Tool for HTTPS-enabled Metadata Access Service

When the Metadata Access Service is configured to use HTTPS, the Developer tool clients that connect to the Metadata Access Service require security certificates to be present in the client machine truststore.
To connect to the Metadata Access Service to import and preview metadata, the Developer tool requires security certificate aliases on the machine that hosts the Developer tool.
You might need to set the following environment variables on each client host:
INFA_TRUSTSTORE
Set this variable to the directory that contains the
infa_truststore.jks
and
infa_truststore.pem
truststore files.
INFA_TRUSTSTORE_PASSWORD
Set this variable to the password for the truststore. The password must be encrypted. Use the command line program
pmpasswd
to encrypt the password.
If you use the default Informatica SSL certificate, and the
infa_truststore.jks
and
infa_truststore.pem
files are in the default directory, you do not need to set the INFA_TRUSTSTORE or INFA_TRUSTSTORE_PASSWORD environment variables.
If you use a custom SSL certificate, you must set the INFA_TRUSTSTORE and INFA_TRUSTSTORE_PASSWORD environment variables on each client host.