This Repository is meant to provide a single repository for all the iDaaS Connect design patterns/reference architecture(s).
iDaaS Connect is intended to be the way systems integrate with each other, this coulld entail the way systems exchange data from
either an industry standards perspective or common industry based protocols/adapters. The key that we want to provide is a consistent
with the ability to have small components that provide base capabilities. Do not think of these capabilities as anything more than a set of
design patterns to provide comprehensive connectivity and routing of data. Data is the asset and this set of repositories is intended to help anyone connect and build innovative platforms.
Below please find a visual that does visualize the entire iDaaS capabilities set.
The key thing to note is while each specific iDaaS capability is purpose built and designed
for any type of customer public or hybrid cloud our focus is on meeting data where it is securely
and at scale.
scripts
For all iDaaS design patterns it should be assumed that you will either install as part of this effort, or have the following:
- An existing Kafka (or some flavor of it) up and running. Red Hat currently implements AMQ-Streams based on Apache Kafka; however, we
have implemented iDaaS with numerous Kafka implementations. Please see the following files we have included to try and help:
Kafka
KafkaWindows
No matter the platform chosen it is important to know that the Kafka out of the box implementation might require some changes depending upon your implementation needs. Here are a few we have made to ensure:
In /config/consumer.properties file we will be enhancing the property of auto.offset.reset to earliest. This is intended to enable any new system entering the group to read ALL the messages from the start.
auto.offset.reset=earliest - Some understanding of building, deploying Java artifacts and the commands associated. If using Maven commands then Maven would need to be intalled and runing for the environment you are using. More details about Maven can be found here
- An internet connection with active internet connectivity, this is to ensure that if any Maven commands are
run and any libraries need to be pulled down they can.
We also leverage Kafka Tools to help us show Kafka details and transactions..
This section covers the running any of the design patterns/accelerators. There are several options to start the Engine Up!!!
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
KafkaWindows
This section covers how to get the application started.
- Maven: go to the directory of where you have this code. Specifically, you want to be at the same level as the POM.xml file and execute the
following command:
mvn clean install
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.
- Code Editor: You can right click on the Application.java in the /src/ and select Run
Each design pattern/accelerator has a unique and specific application.properties for its usage and benefit. Please make sure to look at these as there is a lot of power in these and the goal is to minimize hard coded anything.
Below are the specific iDaaS Connect branded repositories designed to solve data connectivity issues.
BlueButton is intended to be a very specific implementation to support puling of data to support
several defined and specific government initiatives. We have implemented a reusable open source
design pattern to help meet this critical mandated set of requirements.
Blue Button Readme
EDI has been a standard around for decades, this repository does not introduce capabilities that compete
with capabilities vailable for claims processing or other EDI very specific needs. The intent
of this repository it to enable the processing of EDI data such as cliams and
Supply chain.
EDI Readme
HL7 is a very legacy based client server socket protocol.
HL7 Readme