1 Placeholder Update for Oracle Banking Microservices Architecture Services
This topic provides the information about the various methods to perform the placeholder update for Oracle Banking Microservices Architecture services.
- Method 1 – Via setUserOverrides.sh file
This topic provides the systematic instructions to run Oracle Banking Microservices Architecture services through setUserOverrides.sh file. - Method 2 – Via Passing the -D params in the Server Start Argument
This topic provides the systematic instructions to run the Oracle Banking Microservices Architecture services by passing the -D params in the Server start argument. - Method 3 – Using env files and setUserOverrides.sh file
This topic provides the systematic instructions to run Oracle Banking Microservices Architecture services by using env files and setUserOverrides.sh file. - Method 4 – Workflow Configuration
This topic provides the systematic instructions to run Oracle Banking Microservices Architecture services through workflow configuration.
1.1 Method 1 – Via setUserOverrides.sh file
This topic provides the systematic instructions to run Oracle Banking Microservices Architecture services through setUserOverrides.sh file.
1.2 Method 2 – Via Passing the -D params in the Server Start Argument
This topic provides the systematic instructions to run the Oracle Banking Microservices Architecture services by passing the -D params in the Server start argument.
All the above mentioned -D parameters can be passed through the Server start argument in the respective managed server.
- On Domain Structure, click Environment. Under Environment, click Servers.The Summary of Servers screen displays.
- On the Servers (Filtered - More Columns Exist) table, click managed server to pass the values.The Settings for managed server tab displays.
- Edit the Arguments field and pass all the environment parameters required for the service to run.
1.3 Method 3 – Using env files and setUserOverrides.sh file
This topic provides the systematic instructions to run Oracle Banking Microservices Architecture services by using env files and setUserOverrides.sh file.
1.4 Method 4 – Workflow Configuration
This topic provides the systematic instructions to run Oracle Banking Microservices Architecture services through workflow configuration.
- Create Metadata of the workflow.The sample DSL for workflow creation is given below:
{ "name": "initialTest", "description": "Test workflow", "version": 4, "tasks": [ { "name": "TEST", "taskReferenceName": "TESTING3", "description": "TESTING2", "inputParameters": { "FUNCTIONAL_CODE": "TEST_FA_ILS_REGTN2", "processRefNo": "${workflow.input.transactionModel.txnIdentification.processRefNo}", "processName": "Testing Process2", "processCode": "${workflow.input.transactionModel.txnIdentification.processName}", "transactionModel": "${workflow.input.transactionModel}", "stage": "TESTING2", "priority": "${workflow.input.transactionModel.transactionData.moduleData.taskPrioirty}", "applicationDate": "${workflow.input.transactionModel.txnIdentification.applicationDate}", "applicationNumber": "${workflow.input.transactionModel.txnIdentification.processRefNo}", "processRefNumber": "${workflow.input.transactionModel.txnIdentification.processRefNo}", "branch": "${workflow.input.transactionModel.txnIdentification.branchCode}", "user": "${workflow.input.transactionModel.txnIdentification.currentUser}", "customerNumber": "${workflow.input.transactionModel.transactionData.moduleData.customerId}", "amount": "${workflow.input.transactionModel.transactionData.moduleData.amount}", "currencyCode": "${workflow.input.transactionModel.transactionData.moduleData.currency}", "TASK_OUTCOMES": [ "PROCEED" ], "moduleCode": "OBTFPM", "customFilter": [ { "key": "contractRefNo", "label": "Back Office Reference" }, { "key": "otherRefNo", "label": "External Reference" } ] }, "type": "WAIT", "startDelay": 0, "optional": false, "asyncComplete": false } ], "outputParameters": { "stage": "CLMO_FA_SNPOAR_APPEN", "taskOutcome": "PROCEED_WITH_PARTICIPANT" }, "schemaVersion": 2, "restartable": true, "workflowStatusListenerEnabled": false }Call the API (/api/metadata/workflow) and pass the DSL in body.The below screen depicts the sample workflow - For workflow creation, call the API (/api/workflow) to create the workflow. This API provides the information to the workflow metadata which is created using previous call.
{ "name": "initialTest", "description": "initialTest", "version": 4, "input": { "transactionModel": { "transactionData": { "moduleData": { "amount": 122, "currency": "GBP", "customerId": "001506", "customerName": "MARKS AND SPENCER", "taskPrioirty": "H" } }, "txnIdentification": { "branchCode": "000", "currentStage": "TEST_FA_ILS_REGTN2", "currentUser": "SWAGATIKA", "key1": "Desk", "moduleCode": "TRMO", "processName": "Testing Process2", "processRefNo": "300ILCI012260", "applicationDate": 1588582461960, "taskOutcome": "PROCEED", "taskPrioirty": "H" } } } }Pass the DSL in body. The below screen depicts the sample workflow:
