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 REST API
  10. Data Integration Service Applications
  11. Data Privacy Management Service
  12. Enterprise Data Preparation Service
  13. Interactive Data Preparation Service
  14. Informatica Cluster Service
  15. Mass Ingestion Service
  16. Metadata Access Service
  17. Metadata Manager Service
  18. Model Repository Service
  19. PowerCenter Integration Service
  20. PowerCenter Integration Service Architecture
  21. High Availability for the PowerCenter Integration Service
  22. PowerCenter Repository Service
  23. PowerCenter Repository Management
  24. PowerExchange Listener Service
  25. PowerExchange Logger Service
  26. SAP BW Service
  27. Search Service
  28. System Services
  29. Test Data Manager Service
  30. Test Data Warehouse Service
  31. Web Services Hub
  32. Application Service Upgrade
  33. Appendix A: Application Service Databases
  34. Appendix B: Connecting to Databases from Windows
  35. Appendix C: Connecting to Databases from UNIX or Linux
  36. Appendix D: Updating the DynamicSections Parameter of a DB2 Database

HTTP Configuration Properties

HTTP Configuration Properties

The HTTP configuration properties for a Mass Ingestion Service process specify whether the process uses a secure connection or a non-secure connection to communicate with external components. The properties also specify the keystore file to use when the Mass Ingestion Service process uses the HTTPS protocol.
The following table describes the HTTP configuration properties for a Mass Ingestion Service process:
Property
Description
HTTP Port
Unique HTTP port number for the Mass Ingestion Service process when the service uses the HTTP protocol. Default is 9050.
Enable Transport Layer Security (TLS)
Enables the Transport Layer Security protocol to encrypt connections between the Mass Ingestion Service and external components.
If you enable the TLS protocol, you must specify an HTTPS port and a keystore file. You do not specify an HTTP port.
HTTPS Port
Unique HTTPS port number for the Mass Ingestion Service process when the service uses the HTTPS protocol.
When you set an HTTPS port number, you must also define the keystore file that contains the required keys and certificates.
Keystore File
Path and file name of the keystore file that contains the keys and certificates required if you use HTTPS connections for the Mass Ingestion Service.
You can create a keystore file with a keytool. keytool is a utility that generates and stores private or public key pairs and associated certificates in a keystore file. You can use the self-signed certificate or use a certificate signed by a certificate authority.
Keystore Password
Password for the keystore file.