kaldesai commented on code in PR #685:
URL: 
https://github.com/apache/incubator-kie-kogito-docs/pull/685#discussion_r1829470246


##########
serverlessworkflow/modules/ROOT/pages/cloud/operator/supporting-services.adoc:
##########
@@ -180,6 +180,241 @@ When you use the common PostgreSQL configuration, the 
database schema for each s
 For example, `sonataflow-platform-example-data-index-service`.
 ====
 
+== Configuring the Supporting Services Eventing System
+
+In general, the following events are produced in a {product_name} installation:
+
+* Workflow outgoing and incoming business events.
+* {product_name} system events sent from the workflow to the Data Index and 
Job Service respectively.
+* {product_name} system events sent from the Jobs Service to the Data Index 
Service.
+
+The {operator_name} is designed to use the link:{knative_eventing_url}[Knative 
Eventing] system to resolve all the event communication between these services.
+
+[NOTE]
+====
+In a regular {product_name} installation, the preferred method is to use the 
<<platform-scoped-eventing-system-configuration, Platform scoped Eventing 
System Configuration>>, while the 
<<service-scoped-eventing-system-configuration, Service scoped Eventing System 
configuration>> is reserved only for advanced use cases.
+====
+
+[#platform-scoped-eventing-system-configuration]
+=== Platform scoped Eventing System Configuration
+
+To configure a platform scoped eventing system, you must use the field 
`spec.eventing.broker.ref` in the `SonataFlowPlatform` CR to refer a Knative 
Eventing Broker.

Review Comment:
   ```suggestion
   To configure a platform-scoped eventing system, you must use the field 
`spec.eventing.broker.ref` in the `SonataFlowPlatform` CR to refer to a Knative 
Eventing Broker.
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to