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

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.