1.2 Steps to Deploy Conductor Process

Use steps to deply conductor process to deploy common and all workflow specific task definitions.

Pre-Requisite

PLATO-O and PLATO-ORCH-SERVICE services should be up and registered in the Eureka registry.

For the installation of PLATO-O and PLATO-ORCH-SERVICE, refer to Plato Infrastructure Services Installation Guide.

Post-Requisite

CLMO-ORCHESTRATION-SERVICE should be deployed after registering common task definitions and all workflow specific task definitions (total of 26 task definitions listed above) as this service would have worker implementation for all the simple tasks. Presently this service has 26 worker implementations with 36 threads configured for worker coordinator to manage these workers.

Note:

Steps to deploy a process remains the same for all the process files.

In OBCLPM, for every workflow a workflow definition json (e.g. LoanDraftProposal.JSON) file and if required its own worker tasks definition json (TaskDefinitions.JSON) file will be maintained. Also, there is a SharedSimpleTaskDefinitions.JSON file having simple task definitions that are used across all workflows. To deploy all or any workflow definition.

1. Firstly shared simple tasks definitions should be done. for that below endpoint can be invoked from postman tool with header and payload as described below.

   Note:

   The host name and port number of the PLATO-ORCH-SERVICE from the eureka registry should be used in this endpoint

   Task definitions end point:
   http://whf00mdj:9009/plato-orch-service/api/metadata/taskdefs 
   HTTP Method: POST 
   Header parameters: 
   Content-Type:application/json 
   appId:platoorch 
   branchCode:004 
   userId:USER1 
   Payload:SharedSimpleTaskDefinitions.JSON content 

   Figure 1-1 HTTP Method: POST

   
   Description of "Figure 1-1 HTTP Method: POST"
2. To verify if any of the task is registered , http://whf00mdj:9009/plato-orch\u0002service/api/metadata/taskdefs/{taskname} endpoint can be invoked with GET HTTP Method as shown below.

   Figure 1-2 GET HTTP Method

   
   Description of "Figure 1-2 GET HTTP Method"
3. Next workflow specific task definitions should be done. for that use the task definition endpoint mentioned at step 1 and provide workflows specific TaskDefinitions.JSON file content as payload.
4. Next workflow definitions should be done. for that use the workflow definition endpoint mentioned below and provide workflows definition json (e.g. LoanDraftProposal.JSON) file content as payload.

   k definitions end point:
   http://whf00mdj:9009/plato-orch-service/api/metadata/workflow 
   HTTP Method: POST 
   Header parameters: 
   Content-Type:application/json 
   appId:platoorch 
   branchCode:004 
   userId:USER1
   Payload: LoanDraftProposal.JSON content
       

   Figure 1-3 Post HTTP Method

   
   Description of "Figure 1-3 Post HTTP Method"
5. To verify if the workflow is registered , http://whf00mdj:9009/plato-orch\u0002service/api/metadata/workflow/DRFTPR?version=1 endpoint can be invoked with GET HTTP Method and check if workflow definitions is available. The workflow name to be used in this GET can be referred from name property workflow definition json. Similarly, all the workflow definitions can be registered and verified one by one.

   Figure 1-4 Get HTTP Method

   
   Description of "Figure 1-4 Get HTTP Method"