Indice degli argomenti

• Receiving and Routing Data in a Production

  Receiving and Routing Data in a Production

  Content Type
  Exercise

  Duration
  10m

  Level
  Introductory

  Sharing data between systems has never been easier than it is with InterSystems IRIS® data platform. Consume data from multiple systems, route messages according to logic you define, and connect using common protocols and multiple languages. With InterSystems IRIS, you can:
  

  • Route messages based on metadata or message contents.
  • Apply and update business logic in a low-code UI.
  • Transform data programmatically for downstream systems.
  • Use out-of-the-box components for quick integrations or code your own for even more flexibility.
  • Act on data flowing through the system with machine learning algorithms.
  • Store consolidated data to one repository for deeper analysis.
  • Track messages to troubleshoot or audit with ease.

  Learning Objectives

  • Use InterSystems IRIS interoperability tools to integrate multiple systems.
  • Consume delimited data using the built-in record mapper.
  • Route messages, apply business logic, and transform data using a low-code editor.

  
  

  Prerequisites

  • None

  
  
  

  Watch the video and try the exercise below!
• Start the Exercise

  Start the Exercise

  In this exercise, you will develop a smart ticketing system that processes red light violation data. Traffic cameras detect violations, and InterSystems IRIS will be used to store, route, and process this data. Violations involving emergency vehicles will be excluded from ticketing, and data will be transformed into the appropriate format for downstream systems.

  • Launch the virtual machine (VM) below to begin working on the exercise. For responses to common questions on using VM-based Learning Labs, visit FAQ: Using Learning Services Virtual Machines.

    Your login information for the VM is the following:

    • Username: student
    • Password: LearningServices7
  • You must be logged in to launch this VM.

    • Log in with your existing account.
    • Don't have an InterSystems account? Create a new account.
  • Get set up

    1. Open the virtual machine and log in using the credentials provided above.
    2. In the VM, open Chrome, then click the IRIS bookmark to open the InterSystems IRIS Management Portal.
    3. Log in to the Management Portal with the following credentials:
       • Username: tech
       • Password: demo
    4. To verify the production has started, navigate to Home > Interoperability > Configure > Production and open the production configuration screen for Demo.RedLights.
    5. If the box in the top left says Production Stopped or Production Suspended, start the production using the Start button.
  • Use InterSystems IRIS interoperability tools with little to no coding knowledge
    

    When the integration solution started, the production consumed a local text file and processed it.

    1. Take a look at the message that passed through:
       1. Navigate in the Management Portal to Interoperability > View > Messages.
       2. Select the top-most message that has source equal to RealTimeRedLightViolation.
    2. On the Trace tab, click View Full Trace.
       This opens what is known as the Visual Trace and shows how the data is passed between InterSystems IRIS production components. All messages are stored to the database, which makes troubleshooting and auditing easy. A message has been consumed by the RedLightViolation business service.
       Can you tell which business process the message is then sent to? Which property is not used when sending data to the To_TicketApplication business operation? (Hint: Select message [1] and click the Contents tab on the right. Then compare this to [2].)
       Answer: Demo.TicketBPL and CarType, respectively.
       
    3. Optional: If you'd like to send another message through the interface, open the Samples-Integration-RedLights folder on the desktop. In this folder, open the data folder, and copy SampleFiles/LocalRedLightViolation1-copy.csv to the In folder.
       
  • Use the built-in record mapper to quickly and easily consume delimited files
    

    1. Navigate to Home > Interoperability > Build > Record Maps and open Demo.RedLightViolationsRecordMap.
       
       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 which allows you to 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.
       
       
    2. Click Select a Sample File. In the file selection dialog, use the File of type dropdown to choose All files (*).  Then, choose the message: LocalRedLightViolation1-copy.csv. You can find it in /external/data/SampleFiles/.
       
       
    3. Navigate to Home > Interoperability > Configure > Production. Select the RealTimeRedLightViolation business service. On the Settings tab on the right, find the RecordMap setting and note that it is set to the record map, Demo.RedLightViolationsRecordMap, that you just viewed.
       
       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.
       
       
  • Easily route messages, apply business logic and transformations using a low-code editor

    Data received from traffic lights need to be sent to both the ticket application as well as 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.

    1. Still on the Production Configuration page, select the Demo.TicketBPL business process. On the Settings tab on the right and find Class Name setting under Informational Settings. Click the magnifying glass to open the business process.
       Using the low-code editor, you can easily add logic, flow control, and send messages to business operations, which ultimately send data out to other applications.
    2. Select the Check if whitelisted rule activity and open the Rule Editor using the blue button on the right. Rules can be applied to modify particular aspects of how messages are processed. Security can be set up so certain people can only edit the rules, allowing you to easily divide tasks and provide access to the right people while keeping the rest of your application secure. CHALLENGE: See if you can add a new rule to also allow vehicles with CarType equal to SWAT.
    3. Go back to the Demo.TicketBPL business process. If you no longer have the tab open, you can choose Home > Interoperability > Build > Business Processes > Go. Select Call To_TicketApplication.
       Call activities, such as here, can easily convert data to a format that can be used by downstream systems. Data transformations can be created, leveraging the same UI, for more advanced transformation of data, allowing you to reuse transformations throughout your applications.

    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. In this code, you are able to leverage common pre-built adapters to easily retrieve and send data via protocols such as TCP, FTP, SQL, and REST.

• What's next?

  What's next?
  • • Continue working with this code to build a basic integration (exercise, 45m).
    • See how to use multiple data models in InterSystems IRIS (exercise, 10m).
    • Learn the basics of connecting systems using interoperability productions (documentation, 15m).
      
  • Share Your Feedback!