Introduction to FLEXBridge Integration Flowchart

FLEXBridge FLEXBridge Introduction to FLEXBridge Integration Flowchart

The FLEXBridge Integration establishes a connection between third-party systems and the Flex environment, enabling seamless data exchange and service utilization. This integration is structured to ensure secure communication and efficient operation through a defined set of components and network configurations.

Core Components of FLEXBridge Integration

The FLEXBridge integration architecture comprises several key components, each serving a specific function in facilitating secure data flow and service provision:

  • Third-Party Components:

    • Third-Party Host PC: This external computer is involved in initiating connections and is specifically used for importing files into the Flex system. It connects to the network via a Switch.
    • Third-Party Host Monitor Software PC: This machine is situated on the same network segment as the FLEXBridge/Web Server.
  • Networking & Security Components:

    • Switch: This network device is essential for connecting the Third-Party Host PC and the FLEXBridge/Web Server to the Firewall.
    • Firewall: A critical security measure, the firewall is responsible for segregating the network. It divides the network into distinct, secure environments for the FLEXBridge/Web server, the App Server, and the IBM Server. This segregation helps to isolate and protect each part of the system.
  • FLEX System Components:

    • FLEXBridge/Web Server:
      • Acts as a proxy, mediating communications between the third-party system and the internal App Server.
      • Is also used to import files that originate from the Third-Party Host PC.
      • Third parties can establish an API interface by connecting to its Public IP.
      • Resides on a network that is segregated by the firewall.
    • App Server:
      • Provides core FLEX services.
      • Connects to various data sources, including IBM Servers.
      • Operates within a network segregated by the firewall.
    • IBM Server:
      • Functions as the primary data source for the App Server.
      • Serves as the back-end core for both the App Server and the overall FLEX Services.
      • Is located on a network segment isolated by the firewall.

How FLEXBridge Integration Works: The Data Flow

The integration process follows a precise flow to ensure secure and efficient operations:

  1. External Connection Initiation: A third-party system, typically from the Third-Party Host PC, initiates a connection. This connection passes through a Switch.
  2. API Interface: The third-party accesses the Flex system by connecting to the Public IP of the FLEXBridge/Web Server, which acts as an API interface.
  3. Security Segmentation: All network traffic between external systems and the core Flex components is managed by the Firewall. The firewall enforces network segregation, ensuring that the FLEXBridge/Web server, App Server, and IBM Server each reside in separate and secure network environments.
  4. Proxy and File Transfer: The FLEXBridge/Web Server plays a dual critical role:
    • It functions as a proxy, directing and managing communication between the external third-party system and the internal App Server.
    • It is also utilized to import files directly from the Third-Party Host PC into the Flex system.
  5. Service Provision: The App Server is responsible for delivering the core FLEX services to the system. It processes requests and manages interactions with the underlying data infrastructure.
  6. Data Backend Operation: The IBM Server serves as the fundamental data source and the back-end core for both the App Server and all FLEX Services. It is where all essential data is stored and managed.

This methodical approach ensures that all interactions with the Flex system, from third-party connections to core data operations, are handled with security and efficiency.