Defining a Custom Integration Service
This section shows you how you can define your own Integration Service to deliver a set of events that belongs to one or more event types.
By default, there is one integration service per lead company and each integration service is bound to one parameter record defined in IF.INTEGRATION.SERVICE.PARAM. The record ID of the configuration record is either company code or SYSTEM.
This default integration service delivers all undelivered events and does not allows the service to execute for a specific event type that is of highest priority. Custom Integration Service helps you to deliver such events.
You can use this functionality by defining your own integration service. The following steps should be performed to define a custom integration service:
- Create a record in BATCH application
- Create a record in TSA.SERVICE application with the same record ID used in BATCH.
Ensure the content of the record is same as the default integration service except the value in DATA field. When creating a record, the record name can be any name followed by a “-“ and any number between 01 to 99. For example BNK/INTEGRATION.SERVICE-01.
It is recommended to use the same name as integration service with a suffix (-01).
Rules to Define a Custom Parameter Record
- The record ID should start with a company code followed by a “-“ and any number between 01 to 99. For example GB0010001-01, GB0010001-99.
- This custom parameter record should have WHITE.LIST configured to indicate the set of events that need to be processed by the integration service. The rest of the configuration is same as default service.
- On authorizing this custom record, a read-only black list record with the ID Company_Code-BLACK.LIST is created. This black list record holds the event types that are not processed by the integration service. For example GB0010001-GLOBAL.LIST.
In this topic