Deploying Savings Pot Microservice on J2EE

This section explains how to deploy the Savings Pot microservice on the J2EE cloud. To deploy, you must perform the following tasks:

• Deployment Artefacts
• Deploying Savings Pot Microservice on J2EE Compliant Application Server

Deployment Artefacts

Savings Pot Microservices for J2EE deployment is available as single release bundle  ms-savingspot-package-j2ee-<release_number>.zip.

The ms-savingspot-package-j2ee-<release_number>.ear file will be available after extracting the deployment package. This .ear can be deployed in J2EE compliant application server.

Deployment of Savings Pot Microservice on J2EE Complaint Application Server

Prerequisites

You must setup the following before deploying Savings Pot microservice on J2EE Compliant Application Server.

• Application Server and Standalone Mongo Server must be setup and running. Refer to Application Server and Mongo Standalone server installation guide to setup.
• As a one time setup, run setup.bat/setup.sh in the cql folder to create the database, collections, and to load the default reference data (master data) in the Mongo server for the Savings Pot microservice.
  • For Windows: setup.bat
  • For Linux : setup.sh

To deploy Savings Pot microservice on J2EE Compliant Application Server, follow these steps:

1. To create the database, collections, and to load reference date in Mongo Server for Savings pot microservice, run the DB scripts in cql folder.
2. Open the ear file using any archive readers.
   
3. In all the war files, navigate to the \ms-savingspot-package-j2ee.ear\xxxx.war\WEB-INF\classes\properties\ path and update the following properties,

api.properties

DATABASE_KEY: mongodb
MONGODB_DBNAME: ms_savingspot
MONGODB_CONNECTIONSTR: mongodb://localhost:27017,localhost:27018,localhost:27019

4. Deploy the J2EE artefact (.ear) in the application server.
   • For JBOSS, download the artefact to the jboss/standalone/deployments folder.
   • For WebLogic, navigate to the following url http://localhost:9001/console based on the URL configured while installing the server, and click Install to deploy the artefact.
5. After the WAR file is deployed, check the APIs in the package.

The URL of APIs follows the below structure

• Base Path: http://<IP_ADDRESS>:<PORT>/<context-root>/api/<version>/
• For Example: http://localhost:9089/ms-savingspot-api/api/v1.0.0/.
• Resource path of the endpoint can be found in the APIs.
• A sample endpoint of savingspot can be http://localhost:9089/ms-savingspot-api/api/v1.0.0/holdings/savingPots.