FLEXBridge Integration Flow Chart
This document provides a technical overview of the FLEXBridge Integration Flow, detailing the components and their interactions within the www.flexcutech.com system. This integration facilitates secure and efficient communication between third-party systems and the core FLEX services.
1. Overview
The FLEXBridge Integration enables third-party systems to interact with FLEX services by acting as a secure proxy and data import mechanism. The architecture ensures network segregation and robust data handling.
2. Key Components
The FLEXBridge integration involves the following primary components:
- 3rd Party System:
- Represents external systems or applications that require integration with FLEX services.
- Connects to the Public IP of the Flexbridge/Web server via an API interface.
- 3rd Party Host PC:
- A monitor software PC that resides on the same network as the Flexbridge/Web server.
- Used for managing and interacting with the third-party software.
- Switch:
- Connects the 3rd party host PC and the Flexbridge/Web server to the Firewall.
- Facilitates network connectivity within the integration environment.
- Firewall:
- Segregates network traffic, creating separate network zones for:
- Flexbridge/Web server
- App Server
- IBM Server
- Enhances security by controlling inbound and outbound network access.
- Segregates network traffic, creating separate network zones for:
- Flexbridge/Web Server:
- Acts as a proxy between the 3rd party system and the App Server.
- Provides an API interface for third-party connections.
- Used to import files from the 3rd party host PC.
- App Server:
- Provides core FLEX services.
- Connects to data sources, such as the IBM Server, to retrieve and process data.
- IBM Server:
- Serves as the primary data source for the App Server and FLEX Services.
- Acts as the back-end core for data storage and retrieval.
3. Integration Flow
The integration flow proceeds as follows:
- Third-Party Connection:
- A 3rd party system initiates a connection to the Flexbridge/Web server.
- This connection is established via the Public IP of the Flexbridge/Web server, utilizing an API interface.
- Host PC Connectivity:
- The 3rd party host PC, running monitor software, is connected to the Flexbridge/Web server via a Switch.
- This Switch also connects both the 3rd party host PC and the Flexbridge/Web server to the Firewall.
- Firewall Segregation:
- The Firewall plays a critical role in network segmentation.
- It ensures that the Flexbridge/Web server, App Server, and IBM Server are isolated into distinct network segments, enhancing security and preventing unauthorized access between zones.
- Flexbridge/Web Server Operations:
- The Flexbridge/Web server receives requests from the 3rd party system.
- It acts as a proxy, forwarding these requests to the appropriate App Server.
- Additionally, the Flexbridge/Web server handles the import of files originating from the 3rd party host PC.
- App Server Processing:
- The App Server receives requests from the Flexbridge/Web server.
- It processes these requests by providing the necessary FLEX services.
- To fulfill these services, the App Server connects to the IBM Server.
- IBM Server Data Handling:
- The IBM Server functions as the central data source and back-end core.
- It provides the required data to the App Server and supports various FLEX Services.
4. Security Considerations
- Firewall Segregation: The strategic placement and configuration of the Firewall are crucial for maintaining network security and isolating critical components.
- API Interface: The 3rd party connection to the Flexbridge/Web server is through a defined API interface, ensuring structured and secure communication.
- Proxy Functionality: The Flexbridge/Web server’s role as a proxy adds a layer of security by mediating direct connections between third parties and the App Server.