Sharing data between systems has never been easier. Consume data from multiple systems, route messages according to logic you define, and connect using common protocols and multiple languages. With InterSystems IRIS® data platform, you can:
Cameras on traffic lights have been installed to automatically identify red light violations. This data needs to be stored in a database for further analysis. If the violator is not an emergency vehicle, the data also needs to be sent to another application to issue a ticket.
InterSystems IRIS is being used to route the data, apply business rules to determine which violations result in tickets, and automatically transform data to the appropriate format needed for the downstream systems. For this activity, you will use the InterSystems Management Portal from an instance of InterSystems IRIS to see some of the key features of interoperability.
In InterSystems IRIS, an integration solution is known as a production. A production provides built-in connections to a wide variety of message formats and communications protocols. You can easily add other formats and protocols, and define business logic and message transformations either by coding or using graphic wizards. Productions provide persistent storage of messages, which allow you to trace the path of a message and audit whether a message is successfully delivered.
A production consists of business services, processes, and operations:
When the integration solution was started in Set Up, the production consumed a
.txt file and processed it. We’re going to take a look at the message passed through.
shared/Samples-Integration-RedLights/data/Infolder (you may have to create the
The Record Map UI allows you to easily generate code to consume and produce delimited files. While this particular record map already exists, notice there is the option to select a sample file and see how data in the file will be parsed. Additionally, a CSV wizard can read headers and generate the corresponding record map on the fly.
/home/project/shared/Samples-Integration-RedLights/data/SampleFiles/LocalRedLightViolation1-copy.csv. This utility makes it easy to build your record map and verify files will correctly be parsed. Unable to find it? Make sure to change the File of type drop-down to All Files (*) in the file selection dialog.
Each business service has configuration settings that can easily be modified while the integration system is running, only impacting the particular service you need to work on. No code had to be written for this business service to work, allowing you to quickly consume and send delimited files.
Data received from traffic lights needs to be sent to the ticket application and stored in an archive for further analysis. However, a ticket should only be sent if the vehicle that ran the red light is not an authorized vehicle, such as a police car or fire truck. InterSystems IRIS can appropriately route, apply logic, and transform data to ensure this process happens smoothly.
While the business services and business operations in this sample production consumed data using no code, you can also write code to completely customize your own business components, letting you consume and send data in just the way you need. This allows you to use prebuilt adapters for TCP, FTP, SQL, and REST data input and output.