-
OVERVIEW
Introduction to ArenaCore Platform Integration -
INTEGRATION ADMINISTRATIONIntroduction to Integration Administration
-
Creation of Policy (Kafka Topic & User) Domain Operation Items2 Topics
-
Creation and configuration of Domain Roles
-
Creation and configuration of ArenaCore Management Domains
-
INTEGRATION IMPLEMENTATIONIntroduction to Integration Implementation
-
INTEGRATION DEVELOPMENTIntroduction to Integration Development
Participants 31
ArenaCore generates Kafka topic names in the following format:
platform.downstream.<unique root org name>.<topicsegment1>.<topicsegment2>
The ‘platform’ prefix identifies the topic name as being one that is being used to communicate with an external management platform.
The second segment named ‘downstream’ indicates that messages are flowing from the ArenaCore core environment down to the associated management platform system.
The <unique root org name>segment is setup automatically to contain the unique name identifier for the root organisation within which the topic has been created. This name is one that will have had all special characters and whitespace removed, and will potentially have had a numeric suffix added to it in order to ensure uniqueness across the entire ArenaCore platform.
<topicsegment1> is replaced with the topic specified within the Policy Item definition for relevant topic definition.
<topicsegment2> is replaced with the topic specified within the Policy Item Value definition for relevant topic definition.
Therefore a real Kafka topic name could look something like:
platform.downstream.ibmaustralia.victoria.DC01Room10Rack47