5.3. Event objects flow#
Nubus uses Event objects to inform other Nubus applications or Third-party applications not part of Nubus about changes in the Identity Store and Directory Service. This section describes the flow relationships for Event objects between the functional components in Nubus, as shown in Fig. 5.9.
Within the Provisioning Service, the UDM Transformer creates Event objects and passes them to the Dispatcher, which duplicates the Event objects for the respective consumers. The Prefill Service also creates Event objects to provide an initial data state to consumers. For details, see Prefill Service.
Event objects leave the Provisioning Service through the Events and Consumer API to the Consumer of Provisioning Service. Such consumers can be Third-party applications not part of Nubus or other Nubus applications.
Fig. 5.9 Data flow for Event objects on the application component level#
See also
- Provisioning Service in the components section
for detailed information of the functional component and its behavior.
- Event objects in data objects section
for information about Event objects.
5.3.1. Event objects processing#
Fig. 5.10 shows the processing of Event objects on the behavioral level. It provides one additional level of details compared to the figure before.
Event objects have the following data flow:
The UDM Transformer creates Event objects and stores them in the internal Incoming queue.
The Dispatcher, consumes the Incoming queue and distributes the Event objects in queues for each registered consumer.
The Consumer Messages HTTP REST API retrieves the events, and sends messages with Event objects to consumers.
In the case of a first-time provision of a data state, the Prefill Service component creates Event objects and stores them in the Prefill Service queue for each consumer. From that queue, the Consumer Messages HTTP REST API takes over and continues as described before.
You can see the chain of flow relationships from Transform directory objects to UDM objects to Send messages to consumer and which queue each behavior uses for write and read operations.
Fig. 5.10 Data flow for Event objects on the application behavior level#
To enlarge the figure, follow the tips in How to use the document.
5.3.2. Event objects consumers#
The Provisioning Service provides Event objects. Consumer are all systems, that have registered with the Provisioning Service. These can therefore be internal Nubus applications and Third-party application not part of Nubus.
For more information about the consuming of Event objects, see Consumer Messages HTTP REST API.
Fig. 5.11 Consumers of Event objects outside the Provisioning Service, application component level#
Fig. 5.12 Consumers of Event objects outside the Provisioning Service, application behavior level#