When Implementing Siebel Kafka CRM Pub Events No Information Is Logged In The Tomcat eventLogger.txt Log
(Doc ID 2987540.1)
Last updated on NOVEMBER 16, 2023
Applies to:
Siebel CRM - Version 23.9 and laterInformation in this document applies to any platform.
Symptoms
When attempting to implement AI Sidecar in Kafka Secure Communication, the AI tomcat the operation is not recorded.
The information was however logged in the AOM log (in this case, eEnergyObjMgr_enu), as confirmed in the following log lines:
SrmLayerLog Info 3 000001d865460edc:0 2023-11-06 09:47:40 [SrmConn::SendEvent Calling SUBEVT Notification]
SisnTcpIp SisnSockDetail 4 000001d865460edc:0 2023-11-06 09:47:40 -708842688: [TCPIP-client] Send() descriptor = 87
GenericLog GenericInfo 3 000001d865460edc:0 2023-11-06 09:47:40 [SAIEgressService::SendNotification] Notification successfully sent in trail = 0
The issue can be reproduced at will with the following steps:
1. Perform the implementation steps in:
https://docs.oracle.com/cd/F26413_43/books/SystAdm/c-Siebel-CRM-Event-Publication-and-Subscription.html#concept_b1d_1cb_5xb
2. Implement a Runtime Event with trigger Event Handler - SendEvent.
3. Notice that AI Sidecar is not logging any event for this action. The logging would be expected in EventLogger.log in the Tomcat logs.
Changes
Try to implement demo AI Sidecar implementation of Kafka CRM Pub Events as per the available documentation:
https://docs.oracle.com/cd/F26413_43/books/SystAdm/c-Siebel-CRM-Event-Publication-and-Subscription.html#concept_b1d_1cb_5xb
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |