The event listener receives data in XML or JSON format from an external system. Setup is done similar to a Collector but it should be set to Start manually as scheduling will not have any effect.

A listener must be set up with a statistics definition, since VBU will write incoming events directly to the statistics data table.

Parameters

• Listener type (see below)
  • EventHub data from Infor EventHub
  • API  data sent to VBU using HTTP push
• Subscription (only for type EventHub) specific event to listen for (syntax: Publisher:Document:Action)
• Statistics Definition - predefined statistics definition
• Root path root path of data to iterate (blank if data is not in a tree structure)

No output is returned from the Event Listener as all data is written to the statistics data table.

Listener type API

This will listen to HTTP POST requests in JSON or XML format from external sources.

Each message must have a specific body structure to be able to be processed, see below examples.

Request URL format is http(s)://server:port/vb-host/api/duty/N where N is the duty ID.

Request authentication is using basic authentication, a user belonging to a group with API group access is required.

Request header needs to have the following properties:

• Content-Type - either application/xml or application/json

Request body needs to have two parameters:

• queue this can be either
  • true - message will be queued and an immediate response will be presented saying the message was queued
  • false - message will be processed and response will be sent after the duty has completed
• data - this contains your data

It is recommended to always use queue = true to allow for quicker processing.

VBU will automatically convert JSON to XML internally, with a root element named root. The duty processing the data will have a root XPath / mapped to the actual document XPath /root/data.