5 Deployments

This topic describes the deployments for Oracle Banking Virtual Account Management Installation.

Prerequisites

Before proceeding with the below setup, make sure that Kafka is configured and the related properties are present in the Oracle Banking Microservices Architecture schema.

To avail feature of record level approval functionality in Plato-Feed, the below property would need to be maintained as part of weblogic VM argument by each product domain including plato. If not maintained, the default behavior will be of file level approval only.

Property name - feed.recordLevelApprovalReqd

Property value - true or false

Default value - false

Deployments List

The below table gives the details of the deployments required on each domain to run the Oracle Banking Virtual Account Management application. Deploy one after the other in the given order.

Note:

For the exact version of the archive name, refer to the OSDC file available as a part of the release.

Table 5-1 Deployments List

Application	Archive name	OSDC Path	Targets
OBVAM Account Services	obvam-account-services-{version}.war	obvam_services/	OBVAM Account Server
OBVAM Transaction Journal Services	obvam-transaction-journal-services-{version}.war	obvam_services/	OBVAM Transaction Journal Server
OBVAM Statement Services	obvam-statement-services-{version}.war	obvam_services/	OBVAM Statement Server
OBVAM Statement Entity Adapter	obvam-stmt-ent-adapter-{version}.war	obvam_services/	OBVAM Statement Server
OBVAM Internal Transfer Services	obvam-internal-transfer-services-{version}.war	obvam_services/	OBVAM internal Transfer Server
OBVAM External DDA Services	obvam-external-dda-services-{version}.war	obvam_services/	OBVAM External DDA Server
OBVAM External Credit Assessment and Block(ECA) Services	obvam-eca-services-{version}.war	obvam_services/	OBVAM ECA Server
OBVAM Core Services	obvam-core-services-{version}.war	obvam_services/	OBVAM Core Server
OBVAM Identifier Services	obvam-identifier-services-{version}.war	obvam_services/	OBVAM Identifier Server
OBVAM Entity Services	obvam-entity-services-{version}.war	obvam_services/	OBVAM Entity Server
OBVAM Inter Entity Positions Domain	obvam-iep-services-{version}.war	obvam_services/	OBVAM Inter Entity Positions Server
External Interest Engine Services	external-interest-engine-service-{version}.war	obvam_services/	OBVAM EIE Server
External Liquidity Management Services	external-liquidity-management-service-{version}.war	obvam_services/	OBVAM ELM Server
OBVAM Projection Services	obvam-projection-services-{version}.war	obvam_services/	OBVAM Projection Server
VAM LM Charge Services	vamlm-charge-services-{version}.war	obvam_services/	OBVAM Charge Server
OBVAM UI	app-shell-{version}.war cmc-component-server-{version}.war moc-component-server-{version}.war sms-component-server-{version}.war obvam-component-server-{version}.war obvamlm-component-server-{version}.war	ui/	OBVAM Appshell Server

Note:

To deploy the application, refer to the Deploy Application section in Configuration and Deployment Guide.

Deployment Instruction for vamlm-charge-services:

vamlm-charge-services is the common service for Oracle Banking Virtual Account Management and Oracle Banking Liquidity Management. In a co-deployed situation, it must be deployed from only one of the packages.

Both the product packages contain the exact same version of this service. If you deploy it from the one of the product packages, then do not deploy it from the other one.

The value of deployment type in the property table is dependent on the type of deployment.

• If the deployment is standalone for Oracle Banking Virtual Account Management, the value should be vamchg.
• If the deployment is standalone for Oracle Banking Liquidity Management, the value should be lmchg.
• If the deployment is common for both the products, the value should be codeployed.

Deployment Instruction for obvamlm-component-server:

obvamlm-component-server is the common component server for Charges in Oracle Banking Virtual Account Management and Oracle Banking Liquidity Management. In a co-deployed situation, it should be deployed from only one of the packages.

Both the product packages contain the exact same version of this component server. If you deploy it from the one of the product packages, then do not deploy it from the other one.