Skip to content

Latest commit

 

History

History
140 lines (122 loc) · 6.39 KB

CloningBuildingRunningSolution.md

File metadata and controls

140 lines (122 loc) · 6.39 KB
Raw

Return to the Main GitHub Org. Site

General

This content is designws to cover the specific topic of Building and Running an iDaaS solution. While there are references to specific solutions named within this content it is meant to show how to implement specifics.

Step 1: Kafka Server For Data Routing

In order for ANY processing to occur you must have a Kafka server running that this accelerator is configured to connect to. Please see the following files we have included to try and help:
Kafka Non-Windows
Kafka Windows

Step 2: Cloning or Downloading the Code Repository

This section covers how to get the application cloned and downloaded.

  • Maven: The following steps are needed to run the code. Either through your favorite IDE or command line. The following command will clone the iDaaS-Connect repository and all it's submodules:
git clone <repo name>
For example to clone iDaaS-Connwct:
git clone https://github.com/Project-Herophilus/iDaaS-Connect.git
  • You can also go ahead and download the code from a specific repository and then unzip it as well. To download just click on the Code button and select the Download Zip option.

Step 3: Building the App: Command Line

This section covers how to get the application built.

  • Maven: The following steps are needed to run the code. Either through your favorite IDE or command line You can either compile at the base directory or go to the specific iDaaS-Connect acceelerator. Specifically, you want to be at the same level as the POM.xml file and execute the following command:
  • Here is the command to run the design pattern in Dev mode from the command line. This uses the settings in the resources/application-dev.properties
mvn spring-boot:run -Dspring-boot.run.profiles=dev
  • Depending upon if you have every run this code before and what libraries you have already in your local Maven instance it could take a few minutes. From a code editor you also can right click on the Application.java in the /src/ and select Run

Additional or Advanced Design Pattern/Accelerator Configuration

All iDaaS Design Pattern/Accelelrators have application-dev.properties files to enable some level of reusability of code and simplfying configurational enhancements. The following section is designed around the application.properties ssupporting iDaaS Connect HL7; however, it is applicable across all iDaaS-Connect assets. iDaaS Connect HL7 uses 9980 for its server port (where the user management interface will run from). You can change this, but you will have to ensure other applications are not using ports you specify.

# Kafka Details and Topics
idaas.kafka.brokers=localhost:9092
idaas.ccdapost.topic.name=ccdapost
idaas.ccdaconversion.topic.name=ccdaconverted
idaas.hl7conversion.topic.name=hl7converted
idaas.hl7post.topic.name=hl7post
idaas.publiccloud.topic.name=cloud
idaas.terminology.topic.name=terminologies
idaas.deidentification.topic.name=deidentification
idaas.processacks.topic.name=hl7acks
idaas.datatier.topic.name=datatier
idass.heda.topic.name=hedainbound
idass.sdoh.topic.name=sdoh
idaas.hl7adt.topic.name=adt
idaas.hl7mdm.topic.name=mdm
idaas.hl7mfn.topic.name=mfn
idaas.hl7orm.topic.name=orm
idaas.hl7oru.topic.name=oru
idaas.hl7rde.topic.name=rde
idaas.hl7sch.topic.name=sch
idaas.hl7vxu.topic.name=vxu
# HL7 Ports
idaas.port.adt=10001
idaas.port.mdm=10002
idaas.port.mfn=10003
idaas.port.orm=10004
idaas.port.oru=10005
idaas.port.rde=10006
idaas.port.sch=10007
idaas.port.vxu=10008
# Processes
idaas.process.PublicCloud=true
idaas.process.Terminologies=true
idaas.process.Sdoh=true
idaas.process.Deidentification=false
idaas.process.Empi=false
idaas.process.Acks=true
idaas.process.DataTier=false
idass.process.HEDA=false
# Conversions
idaas.convert.CCDAtoFHIR=true
idaas.convert.HL7toFHIR=true
# External APIs
idaas.api.deidentification=http://localhost:8001/api/deidentification
idaas.api.empi=http://localhost:8001/api/empi
idaas.api.cloud=urlendpoint
# Other Settings
aws.access.key=
aws.secret.key=
aws.region=US_EAST_1
aws.region.lower=us-east-1
aws.bucket=public-idaas

Step 4: Deployment Locally

You can compile the code through the maven commands above to build a jar file. Then, go to the /target directory and run the following command:

  • If you want the local management UI you will need to uncomment the hawtio and jokolia dependencies from both the mater POM.xml file and the specific modules POM.xml file as well.
  • Run the jar file with the standard command:
java -jar <jarfile>.jar

Deploying Locally and Changing Params

  • To specify one different attribute being changed
java -jar <jarfile>.jar --idaas.port.adt=10001
  • To use a properties file in a custom location
java -jar <jarfile>.jar --spring.config.location=file:./config/application.properties`

Step 4: Deploying To OpenShift (Using The Maven Plugin)

There are a few steps.

Before beginning there are a few key things:

Item Specific Details
OpenShift CLI https://docs.openshift.com/container-platform/4.11/cli_reference/openshift_cli/getting-started-cli.html
Create a Project in OpenShift https://docs.openshift.com/container-platform/4.11/applications/projects/working-with-projects.html

Here are the steps:

  • Be in the specific directory of the module/submodule you will be deploying
  • Login into the OpenShift console, underneath the user account select the Copy Login Command
  • Select Display Token Link
  • Copy the key login details from the OpenShift console underneath the "Log in with this token" section
  • From a command line copy the entire command and press Enter. This will login you into the OpenShift specific environment
  • oc project (your project name)
  • Run the mvn command below
mvn clean oc:deploy -P openshift -Djkube.generator.from=openshift/fuse7-java11-openshift:1.10 -Djkube.generator.fromMode=istag