Enabling Kafka on IIM

You can enable Kafka connection properties with SSL on an IIM setup.

Using Customization UI

Follow these steps to configure SSL-enabled Kafka:
  1. Copy the truststore and keystore (jks) certificates to a directory on the file system where Sterling B2B Integrator instance is running.
    
    For example:
    /ibm/resources/certificates/common-ca/truststore.jks
    /ibm/resources/certificates/kafka-consumer-1/kafka-consumer-1.jks
    
  2. Update SSL connection related properties in the Customization UI and use /ibm/resources/ in the path.
  3. Log in to the Customization UI as a user with APIUser permission and click customer_overrides. Navigate to the Property tab.
  4. Create a property using the property key nosql_prop for kafka.properties file as mentioned below:
    Property Key Property Value
    nosql_prop.ssl.truststore.location /ibm/resources/certificates/common-ca/truststore.jks
    nosql_prop.ssl.keystore.location /ibm/resources/certificates/kafka-consumer-1/kafka-consumer-1.jks
    Similarly, you can update other Kafka properties including the other SSL properties using the Customization UI.
    Property Key Property Value
    nosql_prop.bootstrap.servers  
    nosql_prop.security.protocol SSL
    nosql_prop.ssl.truststore.password  
    nosql_prop.ssl.keystore.password  
    nosql_prop.ssl.key.password  
    nosql_prop.ssl.enabled.protocols TLSv1.2,TLSv1.1,TLSv1
    nosql_prop.ssl.truststore.type JKS
    nosql_prop.ssl.keystore.type JKS
  5. Restart Sterling B2B Integrator for the changes to take effect.

Using properties file

Follow these steps:
  1. Update the properties in the kafka.properties.in file on the file system located in directory.
    <Path_to_B2BI_Directory>/properties
  2. Run the below command.
    
    Windows platform:
    setupfiles.cmd
    
    Linux/Unix platform:
    ./setupfiles.sh
    
  3. Restart Sterling B2B Integrator for the changes to take effect.