12 Oracle Banking Microservices Architecture Deployments
This topic describes about the Oracle Banking Microservices Architecture deployments.
Prerequisites
- Please note that the app-shell and
api-gateway are updated with new encoding/decoding
logic in the platojwtauth call. By default, the new
encoding/decoding logic will be used, but if you
want to use the previous encoding/decoding format,
you can do so by adding the below property in the
managed servers where app-shell and api-gateway are
deployed.
Property Value -DEncryptionFlag true - new encoding/decoding logic will be applied(more secure)
OR
false - old encoding/decoding logic will be applied
- Before proceeding, make sure that the previous steps are completed.
Oracle Banking Microservices Architecture Applications Deployment Order
Table 12-1 Installation Summary for Oracle Banking Microservices Architecture Services
| Application | Archive name | OSDC path | Targets |
|---|---|---|---|
| Plato-config-service | plato-config-service-{version}.war | {unzip the file}PLATO\plato-config-service\ | Config Server |
| Plato-discovery-service | plato-discovery-service-{version}.war | {unzip the file}PLATO\plato-discovery-service\ | Discovery Server |
| Plato-api-gateway | plato-api-gateway-{version}.war | {unzip the file}PLATO\plato-api-gateway\ | Api Gateway |
| Plato-ui-config-service | plato-ui-config-service-{version}.war | {unzip the file}PLATO\plato-ui-config-service\ | Plato UI Config |
| Plato-apigateway-router | plato-apigateway-router-{version}.jar | {unzip the file}PLATO\plato-apigateway-router\ | Plato-Apigateway-Router |
|
Plato-Orch-Service (To be deployed after sms-service is deployed) |
plato-orch-service-{version}.war | {unzip the file}PLATO\plato-orch-service\ | Plato-Orch-Service |
| Plato-Feed-Services | plato-feed-services-{version}.war | {unzip the file}PLATO\plato-feed-services\ | Plato-Feed-Services |
| Plato-Batch-Server | plato-batch-server-{version}.war | {unzip the file}PLATO\plato-batch-server\ | Plato-Batch-Server |
| Plato-Alerts-Management-Services | plato-alerts-management-services-{version}.war | {unzip the file}PLATO\plato-alerts-management-services\ | Plato-Alerts-Management-Server |
| Plato-Rule-Services | plato-rule-service-{version}.war | {unzip the file}PLATO\ plato-rule-service\ | Plato-Rule-Server |
| Plato-Report-Services | plato-report-services-{version}.war | {unzip the file}PLATO\ plato-report-services\ | Plato-Report-Server |
| Plato-EDP-Services | plato-edp-services-{version}.war | {unzip the file}PLATO\ plato-edp-services\ | Plato-EDP-Server |
| Plato-Transport-Services | plato-transport-services-{version}.war | {unzip the file}PLATO\ plato-transport-services\ | Plato-Transport-Services |
| Plato-Swagger-Api | plato-swagger-api-{version}.war | {unzip the file}PLATO\ plato-swagger-api\ | Plato-Swagger-Api Server |
| Appshell | app-shell-{version}.war | {unzip the file}UI\app-shell-{version}.war | Appshell Server |
Note:
Refer to OSDC file for the exact version number for each service.Eventhub based applications should not be deployed in the admin server.Steps to Deploy as Application
To deploy application, refer to Deploy Application section in Configuration and Deployment Guide.
SSL Configuration
Table 12-2 SSL Configuration - Parameters
| Key | Default Value | Purpose |
|---|---|---|
| ${apigateway.protocol} | https | Only for API gateway protocol. it must be https only. |
| ${eureka.protocol} | https | For inter-service communication protocol. Values can be http or https. |
| ${prefer.ip.address.enabled} | false | For prefer IP address flag. it must be false only. |
| ${nonsecure.port.enabled} | false | For disabling inter-service communication on non secure port. Values can be false or true |
| ${secure.port.enabled} | true | For allowing inter-service calls on secure port. Values scan be false or true |
We recommend only https-based connections. Below are the recommendations:
- Appshell needs to be secured with SSL.
- Api-Gateway needs to be secured with SSL.
- Appshell to Api-gateway communication should happen over SSL.The api-gateway url mentioned as -D parameter for appshell should be ssl enabled (i.e. https-based) and must point to plato-apigateway-router.