Resources

OpenShift Credentials

  • username: username
  • password: user-password

Dev Spaces

Developer Console

Matrix

Rocket.Chat

BGCreated with Sketch.

Tasks to complete

Get Started
BGCreated with Sketch.

Congratulations!

Return to the dashboard to continue your journey.

Go to home

Introduction

Ingest data from customers, store it in a backend database, and generate PDF policy documents — all orchestrated by Apache Camel with secure cross-cluster connectivity powered by Red Hat Service Interconnect.


The Business Need

Customers send Policy Applications in EDI format to the platform. These applications need to be ingested, transformed, stored in a backend database, and rendered as PDF policy documents for archival. The database resides on a separate infrastructure and is not directly accessible from OpenShift — a secure connectivity solution is required.


The Technical Solution (To Build)

An Apache Camel integration exposes an API endpoint that receives incoming EDI policy applications. The flow transforms the EDI data into XML format, stores it in a backend Database via Red Hat Service Interconnect, and renders PDF policy documents that are uploaded to S3 object storage (OpenShift Data Foundation).

Red Hat Service Interconnect enables secure connectivity between the OpenShift cluster and the remote backend database without exposing the database to the public network.


Architecture Overview


flowchart LR

    Customer --> Portal -->|"EDI message"| Camel

    subgraph LocalEnvironment [OpenShift]
        Portal
        Camel --> |"① XML data"|ServiceInterconnect{{"Service\nInterconnect"}}
        Camel --> |"② PDF policy documents"|Storage
    end

    subgraph RemoteEnvironment [Remote Environment]
        ServiceInterconnect2{{"Service\nInterconnect"}} --> Database
    end

    ServiceInterconnect --- |"🔒 secure link"| ServiceInterconnect2{{"Service\nInterconnect"}}

    Camel@{ img: "../../_images/module-03/common/integration-icon.svg", label: "Camel Integration", pos: "b", h: 80, w: 80, constraint: "on" }
    Customer@{ img: "../../_images/module-03/common/customer-icon.svg", label: "Customer", pos: "b", h: 80, w: 80, constraint: "on" }
    Portal@{ img: "../../_images/module-03/common/shop-icon.svg", label: "Portal", pos: "b", h: 80, w: 80, constraint: "on" }
    Storage@{ img: "../../_images/module-03/common/s3-icon.svg", label: "OpenShift<br>Data Foundation", pos: "b", h: 80, w: 80, constraint: "on" }
    Database@{ img: "../../_images/module-03/common/database-icon.svg", label: "Database", pos: "b", h: 70, w: 70, constraint: "on" }

    style LocalEnvironment fill:#fce4e4,stroke:#EE0000
    style RemoteEnvironment fill:#fce4e4,stroke:#EE0000
    style ServiceInterconnect2 fill:#f8b4b4,stroke:#EE0000,color:#333
    style ServiceInterconnect fill:#f8b4b4,stroke:#EE0000,color:#333
    style Customer fill:none,stroke:none
    style Camel fill:none,stroke:none,font-weight:bold
    style Portal fill:none,stroke:none
    style Storage fill:none,stroke:none
    style Database fill:none,stroke:none


What you will do in this lab:

  1. Enable connectivity — Configure Red Hat Service Interconnect to establish a secure link to the backend database.

  2. Complete the flow — Implement the Camel integration that ingests, transforms, stores, and renders policy applications.

  3. Test and validate — Run the flow locally and validate the results.