Deploying Due Diligence Microservice in J2EE Complaint Application Server

This section helps you to deploy Due Diligence microservice in J2EE Complaint application server.

NOTE: Prior to the deployment, ensure to run Application Server and Standalone Mongo Server. 
IMPORTANT: As a one time setup, run setup.bat or setup.sh in cql folder to create the database, collections and to load the default reference data (master data) in Mongo Server for Due Diligence microservice.
  • For Windows, run setup.bat.
  • For Linux, run setup.sh.

Procedure:

  1. Open the ms-duediligence-package-j2ee-<release_number>.ear file using any archive readers.
  2. In all the WAR files, navigate to \ms-duediligence-package-j2ee.ear\xxxx.war\WEB-INF\classes\properties\ and update the following property,
    Closedapi.properties
    MONGODB_CONNECTIONSTR=mongodb://localhost:27017,localhost:27018,localhost:27019

    S.No

    Property

    Description

    1

    MONGODB_CONNECTIONSTR

    This property notifies the connection string of mongo server to API server.

  3. Enable JWT Authentication in api.properties.
  4. Deploy the J2EE artefact (.ear) in the application server.
    • For JBOSS, copy the artefact to the jboss/standalone/deployments folder.
    • For WebLogic, navigate to http://localhost:9001/console based on the URL configured while installing the server, and using the Install button, deploy the artefact.
  5. Once the WAR is deployed, check the API's in the package.
NOTE:

The format of API's URL is given below:

  • Base Path

    http://<IP_ADDRESS>:<PORT>/<context-root>/api/<version>/

    For example: http://localhost:9089/ms-duediligence-api/api/v1.0.0/

  • Resource path of the endpoint can be found in the APIs document. A sample endpoint of Due Diligence is http://localhost:9089/ms-duediligence-api/api/v1.0.0/party/parties/{partyId}/assessmentEvents.

Bookmark Name Actions
BACK

In this topic

Feedback
x

Are you sure you want to log-off?