Configuration

The process for ingestion is as follows.

Prerequisites

The following components must be up and running:

• Party Microservice: Ingester topic must be pre-configured. For more information, refer to the Deployment Guide.
• Data Event Stream (DES)
• Transact

The order of ingestion must be as follows:

• CUSTOMER
• PARTY.RELATIONSHIP
• CUSTOMER.REL.GROUP
• CUSTOMER.GROUP
• EB.LOOKUP
• DE.ADDRESS

To implement ingestion, follow these steps:

1. Create a record in the RR.PARAM application for FXXX.CUSTOMER, FXXX.CUSTOMER.GROUP, FXXX.CUSTOMER.REL.GROUP, and FXXX.PARTY.RELATIONSHIP applications with ILP.REQUIRED set to YES.

   

2. After the successful commit, the schema registry in DES is updated with CUSTOMER, CUSTOMER.GROUP, CUSTOMER.REL.GROUP, and PARTY.RELATIONSHIP schemas.

   Schema Registry - localhost:8081/subjects

   ["DesInstallEvent","CATEG_ENTRY","SECTOR","CUSTOMER","CUSTOMER_GROUP", "DataEventIdEot","AA_PRODUCT","AA_PRODUCT_LINE","AA_PRODUCT_GROUP","DataEvent","STMT_ENTRY","RE_CONSOL_SPEC_ENTRY","SchemaInfoEvent","DataEventIdRecovery"]
   

3. Start the TSM and BNK/RR.TAKEON services in T24.

   

   

4. Launch the TSM tRun START.TSM –DEBUG.

   

5. Launch the agent allocated for the BNK/RR.TAKEON service by using the commane tRun tSA <AgentNumber>.

   

6. After the completion of the service, the CUSTOMER, CUSTOMER.GROUP, CUSTOMER.REL.GROUP, EB.LOOKUP, DE.ADDRESS and the published PARTY.RELATIONSHIP records are loaded into the Party Microservice.