Event Publishing Process

To publish an event to an external system, the 3DEXPERIENCE platform uses a Secured Message Server. The server validates and stores the events until the data associated with the event has been indexed, then publishes the events.

Event Publishing uses Service Integration Agents created using Credential Lifecycle Management (CLM) to connect and consume event messages from a Secured Message Server.

All 3DEXPERIENCE platform services that need to publish public events use a Secured Message Server to send the events as text messages. The Event Publishing service validates and stores the events (centralized event staging) until the data related to the data associated with the event is indexed.

If a message does not require indexing (indexSource in the message is empty), it is published to the public topic without waiting for the indexing process.

When complete, the 3D Indexing Server notifies Event Publishing that data has been indexed for a service, for a tenant. The Event Publishing service then retrieves events from the staging table for that particular service and tenant that are older than the indexing date. It then uses the Secured Message Server to publish the events to the destination topic.

External applications that subscribe to the message server consume the published messages from the server.