Table of Contents

Search

  1. Preface
  2. Workflow Manager
  3. Workflows and Worklets
  4. Sessions
  5. Session Configuration Object
  6. Tasks
  7. Sources
  8. Targets
  9. Connection Objects
  10. Validation
  11. Scheduling and Running Workflows
  12. Sending Email
  13. Workflow Monitor
  14. Workflow Monitor Details
  15. Session and Workflow Logs
  16. Appendix A: Session Properties Reference
  17. Appendix B: Workflow Properties Reference

PowerExchange for Kafka Connections

PowerExchange for Kafka Connections

When you configure a Kafka connection, you define the connection attributes that the PowerCenter Integration Service uses to connect to the Kafka cluster. You can configure SSL properties to connect to a Kafka Broker over SSL.
The following table describes the Kafka connection properties:
Property
Description
Kafka Broker List
The IP address and port combinations of the Kafka messaging system broker list.
The IP address and port combination has the following format:
<IP Address>:<port>
You can enter multiple comma-separated IP address and port combinations.
Retry Timeout in seconds
Number of seconds the Integration Service attempts to reconnect to the Kafka broker to write data.
If the source or target is not available for the time you specify, the mapping execution stops to avoid any data loss.
Default is 180 seconds.
Kafka Broker Version
Select
Apache 0.10.1.1 and above
as the Kafka messaging broker version.
Additional Connection Properties
Comma-separated list of connection properties to connect to the Kafka broker.
To connect to a Kafka broker over SSL, ensure that you set the following properties:
  • security.protocol
  • ssl.truststore.location
  • ssl.truststore.password
If the
ssl.client.auth
parameter is set to
required
or
requested
, ensure that you set the following properties:
  • ssl.keystore.location
  • ssl.keystore.password
  • ssl.key.password
For example,
security.protocol=SSL,ssl.truststore.location=<complete path and name of the client.truststore.jks file>,ssl.truststore.password=<client truststore password>,ssl.keystore.location=<complete path and name of the client.keystore.jks file>,ssl.keystore.password=<client keystore password>,ssl.key.password=<password for the individual key>
You can also specify the configuration properties required to connect to a Kerberised Kafka cluster.
Specify the following property:
security.protocol=SASL_PLAINTEXT,sasl.kerberos.service.name=kafka,sasl.mechanism=GSSAPI
SSL Mode
Specifies whether the PowerCenter Integration Service establishes a secure connection to the Kafka broker.You can select one of the following options:
  • disabled. The PowerCenter Integration Service establishes an unencrypted connection to the Kafka broker.
  • require. The PowerCenter Integration Service establishes an encrypted connection to the Kafka broker without verifying the identity of the server.
  • one-way. The PowerCenter Integration Service establishes an encrypted connection to the Kafka broker using truststore file and truststore password.
  • two-way. The PowerCenter Integration Service establishes an encrypted connection to the Kafka broker using truststore file and truststore password.
SSL TrustStore File Path
Applicable only if you select
one-way
or
two-way
as the SSL mode.
The complete path and file name of the truststore file. The truststore file contains the SSL certificate that the Kafka cluster validates against the Kafka broker certificate.
SSL TrustStore Password
Applicable only if you select
one-way
or
two-way
as the SSL mode.
The password for the truststore file.
SSL KeyStore File Path
Applicable only if you select
two-way
as the SSL mode.
The complete path and name of the Java keystore file. The keystore file contains the certificate that the Kafka broker validates against the Kafka cluster certificate
SSL KeyStore Password
Applicable only if you select
two-way
as the SSL mode.
The password for the keystore file.
Additional Security Properties
Optional. Comma-separated list of connection properties to connect to the Kafka broker in a secured way.
For example,
security.protocol=SASL_PLAINTEXT,sasl.kerberos. service.name=<kerberos name>,sasl.mechanism=GSSAPI, sasl.jaas.config=com.sun.security.auth.module.Krb5LoginModule required useKeyTab=true doNotPrompt=true storeKey=true client=true keyTab="<Keytab Location>" principal="<principal>";