IBM Support

How to configure Kafka for Maximo Manage in IBM Cloud

How To


Summary

Steps to set up Kafka for integration

Environment

Manage 8.6.x

Steps

1) Go to External Systems application
Select "Add/Modify Message Providers" from the Select Actions menu.
Add a row and select KAFKA in Provider Type.
Enter the values according to the Kafka services and security configuration on IBM Cloud.
image-20231017105254-3
For example:
SASL_MECHANISM = 
SECURITY_PROTOCOL = SASL_SSL
BOOTSTRAPSERVERS = comma-separated list of host and port from a Kafka broker
PASSWORD = Encrypted value
USERNAME = token
2) Go to Add/Modify Queues action and add the Kafka queues. For example, cqin,cqinerr, sqin,sqqout
Select KAFKA as the Message Provider 
Expand CQIN queue, enable "Multi Part"
image-20231017105703-4
3) Enter the kafka queue names in an external system
image-20231017105028-2
4) Go to the Kafka CronTask in the Cron Task Setup application

Setup 3 CQIN instances.  For example, kafkacqin,kafkacqin1,kafkacqin2

image-20231017110503-6

kafkacqin has partition set to 0 and topic set to CQIN 

image-20231017110731-7

kafkacqin1 has partition set to 1 and topic set to CQIN 

image-20231017110953-8

kafkacqin2 has partition set to 2 and topic set to CQIN 

image-20231017111053-9

Enter cqinerr as the TOPIC for the kafkacqinerr instance 

image-20231027104825-1

Enter SQIN as the TOPIC for the SQIN instance

The sequential queue must have a partition value. The value is always 0.

image-20231017111513-10

Enter sqout as the TOPIC for the SQOUT instance

image-20231017111812-12

NOTE: Do not activate the KAFKAERROR crontask

5) Set the mxe.kafka.txtimeoutms system property to 900000 (15 minutes) to match the default value of transaction.max.timeout.ms in Kafka broker

Additional Information

Troubleshooting:

1)  

Error while fetching metadata with collection id XXX : {Seqqout=UNKOWN_TOPIC_OR_PARTITION}

* The TOPIC for the Kafka cron instances needs to match with the Kafka queue name set in the Kafka broker.

2)  

com.ibm.db2.jcc.am.SqlIntegrityConstraintViolationException: One or more values in the INSERT statement, UPDATE statement, or foreign key update caused by a DELETE statement are not valid because the primary key, unique constraint or unique index identified by "1" constrains table "MAXIMO.TASKSCHEDULER" from having duplicate values for the index key.. SQLCODE=-803, SQLSTATE=23505, DRIVER=4.32.28

* Delete the records from MAXINTMGSTRK, MAXINTMSGTRKDTL, TASKSCHEDULER tables 

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSKLMX","label":"IBM Maximo Asset Health Insights on Cloud"},"ARM Category":[{"code":"a8m0z000000cxVqAAI","label":"Maximo Application-\u003EIntegrations - Configuration\/Investigation\/Troubleshooting"}],"ARM Case Number":"TS014104636","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Product Synonym

TPAEKAFKA

Document Information

Modified date:
08 April 2024

UID

ibm17053293

Page Feedback