9 Tables
LMM_TM_EVENTS
In the below table, we configure all the events that Oracle Banking Liquidity Management is supporting. Here we can toggle the evt_isEnabled column to “Y” (If we want to publish that event) or “N”(If we want to publish that event).
Table 9-1 LM_TM_EVENTS Table
| COLUMN_NAME | DATA_TYPE | NULLABLE | DATA_DEFAULT | COLUMN_ID | COMMENTS |
|---|---|---|---|---|---|
| ID | VARCHAR2 (36 BYTE) | No | (null) | 1 | (null) |
| EVT_CODE | VARCHAR2 (50 BYTE) | No | (null) | 2 | (null) |
| EVT_CATEGORY | VARCHAR2 (20 BYTE) | No | (null) | 3 | (null) |
| EVT_DESC | VARCHAR2 (100 BYTE) | No | (null) | 4 | (null) |
| EVT_TOPIC | VARCHAR2 (50 BYTE) | Yes | (null) | 5 | (null) |
| EVT_ISENABLED | CHAR (1 BYTE) | No | (null) | 6 | (null) |
| MAKER_ID | VARCHAR2 (12 BYTE) | Yes | (null) | 7 | (null) |
| MAKER_DT_STAMP | DATE | Yes | (null) | 8 | (null) |
| CHEKER_ID | VARCHAR2 (12 BYTE) | Yes | (null) | 9 | (null) |
| CHECKER_DT_STAMP | DATE | Yes | (null) | 10 | (null) |
| RECORD_STAT | CHAR (1 BYTE) | Yes | (null) | 11 | (null) |
| AUTH_STAT | CHAR (1 BYTE) | Yes | (null) | 12 | (null) |
| ONCE_AUTH | CHAR (1 BYTE) | Yes | (null) | 13 | (null) |
| MOD_NO | NUMBER (4,0) | Yes | (null) | 14 | (null) |
LMX_TB_EVENT_LOG
In the below table, all the Oracle Banking Liquidity Management services that wants to publish will store their payload and a scheduler will fetch data from this table and fetch all the records where is_published is “N” and retry_count<=max_retry_configured.
Table 9-2 LMX_TB_EVENT_LOG Table
| COLUMN_NAME | DATA_TYPE | NULLABLE | DATA_DEFAULT | COLUMN_ID | COMMENTS |
|---|---|---|---|---|---|
| ID | VARCHAR2 (36 BYTE) | No | (null) | 1 | (null) |
| EVT_CODE | VARCHAR2 (50 BYTE) | No | (null) | 2 | (null) |
| EVT_TOPIC | VARCHAR2 (50 BYTE) | No | (null) | 3 | (null) |
| EVT_KEY | VARCHAR2 (50 BYTE) | Yes | (null) | 4 | (null) |
| LOG_TYPE | VARCHAR2 (20 BYTE) | Yes | (null) | 5 | (null) |
| LOG_DESCRIPTION | VARCHAR2 (500 BYTE) | Yes | (null) | 6 | (null) |
| LOG_TIME | TIMESTAMP (6) | Yes | (null) | 7 | (null) |
| SERVICE_DATA | CLOB | Yes | (null) | 8 | (null) |
| PUBLISHED_TIME | TIMESTAMP (6) | Yes | (null) | 9 | (null) |
| IS_PUBLISHED | CHAR (1 BYTE) | Yes | 'N' | 10 | (null) |
| RETRY_COUNT | NUMBER | Yes | 0 | 11 | (null) |
PLATO_EVENTHUB_OUT_LOG
The below table is provided in by the plato-event-hub-core (in LMX schema in Oracle Banking Liquidity Management). Here all the events that are to be published are stored along with the publisher service name and status is changed to success once successfully published to kafka.
Table 9-3 LMX_TB_EVENT_LOG Table
| COLUMN_NAME | DATA_TYPE | NULLABLE | DATA_DEFAULT | COLUMN_ID | COMMENTS |
|---|---|---|---|---|---|
| ID | VARCHAR2 (36 BYTE) | No | (null) | 1 | (null) |
| TOPIC_NAME | VARCHAR2 (255 BYTE) | No | (null) | 2 | (null) |
| MESSAGE_KEY | VARCHAR2 (36 BYTE) | Yes | (null) | 3 | (null) |
| EVENT_TYPE | VARCHAR2 (25 BYTE) | Yes | (null) | 4 | (null) |
| PAYLOAD | CLOB | Yes | (null) | 5 | (null) |
| EXCEPTION | VARCHAR2 (512 BYTE) | Yes | (null) | 6 | (null) |
| STATUS | VARCHAR2 (33 BYTE) | Yes | (null) | 7 | (null) |
| RETRY_COUNT | NUMBER | Yes | (null) | 8 | (null) |
| RETRY_DATATIME | DATE | Yes | (null) | 9 | (null) |
| CREATED_BY | VARCHAR2 (12 BYTE) | Yes | (null) | 10 | (null) |
| CREATED_DATE | DATE | Yes | (null) | 11 | (null) |
| UPDATED_BY | VARCHAR2 (12 BYTE) | Yes | (null) | 12 | (null) |
| UPDATED_DATE | DATE | Yes | (null) | 13 | (null) |
| CORRELATION_ID | VARCHAR2 (256 BYTE) | Yes | (null) | 14 | (null) |
| APPLICATION_NAME | VARCHAR2 (120 BYTE) | Yes | (null) | 15 | (null) |
| ACK_COUNT | NUMBER (38, 0) | Yes | 0 | 16 | (null) |
| HEADER | CLOB | Yes | (null) | 17 | (null) |
| CONSUMER_APPL... | VARCHAR2 (512 BYTE) | Yes | (null) | 18 | (null) |
PLATO_EVENTHUB_IN_LOG
The below table is provided in by the plato-event-hub-core (in LMX schema in Oracle Banking Liquidity Management). Here all the events that are consumed are stored along with the consumer service name.
Table 9-4 LMX_TB_EVENT_LOG Table
| COLUMN_NAME | DATA_TYPE | NULLABLE | DATA_DEFAULT | COLUMN_ID | COMMENTS |
|---|---|---|---|---|---|
| ID | VARCHAR2 (36 BYTE) | No | (null) | 1 | (null) |
| TOPIC_NAME | VARCHAR2 (100 BYTE) | Yes | (null) | 2 | (null) |
| MESSAGE_KEY | VARCHAR2 (255 BYTE) | Yes | (null) | 3 | (null) |
| EVENT_TYPE | VARCHAR2 (36 BYTE) | Yes | (null) | 4 | (null) |
| EVENT_PAYLOAD | CLOB | Yes | (null) | 5 | (null) |
| STATUS | VARCHAR2 (36 BYTE) | Yes | (null) | 6 | (null) |
| EXCEPTION | VARCHAR2 (500 BYTE) | Yes | (null) | 7 | (null) |
| MSG_DT_STAMP | DATE | Yes | (null) | 8 | (null) |
| CORRELATION_ID | VARCHAR2 (256 BYTE) | Yes | (null) | 9 | (null) |
| APPLICATION_NAME | VARCHAR2 (100 BYTE) | Yes | (null) | 10 | (null) |