Recommended Operational Practices

While editing aieventconfig.txt file, it is suggested that one validates it with JSON lint or from Notepad++ or any other online tool to ensure it is syntactically correct and that it does not have unwarranted special characters introduced.

Set the correct JAVA_HOME for Kafka server to start properly.

In case of failures, one can check EventLogger file in AI sidecar and the appropriate component (OM) log file of Siebel server to know what went wrong. By default, only error logs are dumped. However, the user may increase the logging level as follows:

Sidecar AI: Update the log4j2-siebel.xml file and set the logging level to INFO for EventLogger.
OM: Increase the logging level for the OM component you are using to 5.

aieventconfig file OM passwords: Check the OM mode first and then use the encrypted password for the security authentication profile type (DB or ldap) of the OM.

When a new AI sidecar is created, server.xml file should have all different ports other than the base AI, otherwise the new AI sidecar will not start properly.

Start sidecar AI after Kafka server is running and stable.

When configuration changes are done, services need to be started:

aieventconfig.txt file changes > restart only corresponding sidecar AI
eventpayloadconfig.txt file changes > restart the specific Siebel Server

In Web Tools while creating Business Service, copy Event Handler and modify such that Business Service Name, Display name, Display Name String Override all be same.

Topic names in aieventconfig file and in the Event Subscription view's Event field value should match.

In Linux OS , make sure to give appropriate permission for below:

eventconfig folder and eventpayloadconfig.txt file
aiconnection folder and aiconnection.txt file
Kafka server (broker) configuration changes (number of partitions, for example) : restart sidecar AIs