To use server extensibility, you must have an Advanced Message Queuing Protocol (AMQP)
1.0 compatible broker service installed and configured for your system.
Server extensibility provides a mechanism for a third-party server to communicate and react to application system events and perform actions, such as finding data, creating objects, overriding default application server behavior, auditing, and so on.
-
A user interacts with the client application which makes a request to the application server.
-
The application server requests trigger events that are sent to the Advanced Message Queuing Protocol (AMQP) message broker.
-
The AMQP message broker sends the events to an external event subscriber, which receives the events and triggers actions based on the event type.
-
To use server extensibility, the server extensibility events are sent to the AMQP 1.0 compatible broker service. You can subscribe to these events using an AMQP 1.0 client library.
-
For more information on the broker services listed by Awesome AMQP 1.0 resources, see https://github.com/xinchen10/awesome-amqp/blob/master/README.md#brokers.
-
Server extensibility samples are available from Smart Community. For more information, see Find sample data on Smart Community.
-
HTTP responses from OData requests return the header X-Correlation-ID. This value can be compared with the Correlation ID of the AMQP event so you can work out the origin of the event. By doing this, you can select which events you can ignore.