Organization
Party Services
This guide would allow you to install the below mentioned Party services, UI, process flow in the specified order. It is recommended to use dedicated managed server for each of the Party Services.
-
obpy-party-maintenance-service
-
obpy-stage-services
-
obpy-party-services
-
obpy-party-kyc-services
-
obpy-businessprocess-services
-
obpy-party-handoff-services
-
obpy-party-publisher-services
-
obpy-party-adapter-services
-
obpy-party-corporate-view-services
obpy-party-batch-services
Note:
It is recommended to use a dedicated managed server for each of the Party Services.User Interface
The following war files need to be deployed to migrate from the existing app-shell build to the foundation app-shell. The UI war is divided into individual component server war files using the foundation app-shell. The user need to delete any single UI app-shell war version that is installed previously and follow the below steps. All the component server war files should be deployed in the same managed server.
-
app-shell
-
cmc-component-server
-
moc-component-server
-
sms-component-server
Deploy the obpy-component-server
war file for the party domain.
Similarly, the other domain component war files can be deployed.
Process Workflow
Table - Conductor Process Flows
Serial Number | Process Flow Name | Description |
---|---|---|
1 |
|
Corporate Onboarding |
2 |
|
Financial Institute Amendment |
3 |
|
Financial Institute Onboarding |
4 |
|
Retail Party Onboarding |
5 |
|
Retail Party Amendment |
6 |
|
Corporate Party Amendment |
7 |
|
Small and Medium Business Party Amendment |
8 |
|
Small and Medium Business Party Onboarding |
9 |
|
Small and Medium Enterprise Party Amendment |
10 |
|
Small and Medium Enterprise Party Onboarding |
11 | Review_SubWorkflow.json |
Review sub workflow |
12 | Recommendation_SubWorkflow.json |
Recommendation sub workflow |
13 | Approval_SubWorkflow.json |
Approval sub workflow |
Parent topic: Preface