Event Inbox Processor Service

   Journey Manager (JM) The transaction engine for the platform. |   System Manager / DevOps |  24.04 This feature was introduced in 24.04

Manager comes with the Event Inbox Processor service that consumes events that are added to its queue after being read by Event Listener Configuration services. The Event Inbox Processor executes REST API calls using properties defined in each topic and an endpoint configured in a service connection of the Event Listener Configuration services. The service runs in a background thread.

Each event contains the following parameters:

• className:
• method:
• body: a payload of the REST API call.

For more information, see REST API.

An example of an event is shown below:

{
"className": "txnupdater",
"method": "update",
"body": "{ \"setId\": \"2\", \"setDeliveryStatus\": \"Ready\" , \"setProperty\": [\"named\", \"My Name\"]}"
}

To configure the Event Inbox Processor service:

1. Select Services > Core Global Services.
2. Select the Inbox Processor from the Type dropdown list to shown only services of this type.
3. Locate the Event Inbox Processor service and click Edit.
4. Click the Service Definition tab to configure the service.

   

5. Select the HTTP Endpoint service connection from Service Connection dropdown list. In this example, it's called JM, but it could be any name you used to create it. If it doesn't exist, create a new HTTP Endpoint service connection using the following endpoint: https://my-domain/manager/secure/rest/fluentapi.
6. Click Save to update the changes.
7. Click the Parameters Edit tab to configure the service parameters.

   

8. Edit a maximum number of events to be processed in the Fetch Limit field. The default is 10000.
9. Specify how long to wait for an event to be processed (in milliseconds) in the In Progress Timeout field.
   Note

   The event's status is set to In Progress when Manager starts sending it to Kafka

10. Specify a maximum number of retries to process an event if it failed in the Max Retry field.
11. Specify how long to wait in the event queue (in milliseconds) in the Queue Timeout field.
12. Specify how long to wait to add an event to the event queue (in milliseconds) in the Wait For Queue Timeout field.
13. Click Save to update the changes.

Next, learn how to view all core global services.