7 Plato Orchestration Services

This topic describes about the Plato Orchestration Services.

Migration Endpoint

Note:

This topic is applicable only to the existing customers.

The task blob usage is removed for GET endpoints in plato-orch-service for task list screens. The table HTASK_ADDN_DTLS contains the task-related details. A migration endpoint must be executed to populate the data for the completed tasks in this table. In-Progress tasks, the data is automatically populated by the poller. This improves the performance in Free Tasks/My Tasks/Completed Tasks/Supervisor Tasks inquiry.

To populate the table HTASK_ADDN_DTLS with previously COMPLETED tasks (for tasks not present in task_in_progress table), a migration API needs to be executed.

GET Request:

Endpoint: http://<host>:<port>/plato-orch-service/api/v1/extn/migrate

Headers: Sample inputs shown below.

appId: platoorch

branchCode: 000

Content-Type: application/json

entityId: DEFAULTENTITY

To verify if the HTASK_ADDN_DTLS table entries are consistent with others, execute the following script and check if the count comes as zero.

SELECT COUNT(*) FROM TASK t 
WHERE JSON_VALUE(json_data, '$.status') = 'COMPLETED' 
AND JSON_VALUE (json_data, '$.taskType') = 'WAIT' 
AND TASK_ID NOT IN (SELECT TASK_ID FROM HTASK_ADDN_DTLS);

Note:

For future tasks and previous non-completed tasks present in task_in_progress table, poller keeps checking the task_in_progress table and populates the HTASK_ADDN_DTLS table.