Summary

The Summary Page serves as the concluding stage in the integration service creation process. Following the successful configuration of the data target, users are prompted to meticulously provide and review essential details on the Summary Page. This meticulous step ensures a comprehensive overview before finalizing and submitting the integration bridge, marking the culmination of the integration setup process.

The following details are required to be entered in this step:

Integration Bridge Name:
Assign a fitting and descriptive name to the integration bridge within the designated space. This step is crucial as it not only helps in identifying the integration bridge accurately but also contributes to the organization and clarity of the overall integration process. Choose a name that succinctly reflects the purpose or nature of the integration, facilitating easy reference and management in future interactions with the integration service.

Description:
Provide a concise yet comprehensive description of the integration service within the allocated space. Craft a description that encapsulates the key functionalities, objectives, and any pertinent details about the integration, aiding both current and future users in understanding the purpose and scope of the service. A well-crafted description enhances documentation, streamlines communication, and fosters a clear understanding of the integration service's role and significance.

Enable/Disable Integration Bridge 

The "Enable/Disable" feature lets users temporarily turn an Integration Bridge on or off. When disabled, the bridge is inactive but can still be edited. 

When disabled, the Integration Bridge behaves like a draft, it's inactive and cannot be run or interacted with, but it can still be edited. 

Enable/Disable Integration Bridge feature has following characteristics: 

Enable/Disable Integration Bridge behaves as follows: 

Schedule:
Within the scheduling section, users have the flexibility to tailor the integration service to meet their specific requirements. Currently, two distinct scheduling types are available: interval and schedule. This versatility empowers users to define timeframes and recurrence patterns that align precisely with their operational needs.

Interval: In the interval scheduling type, users are prompted to input the duration in seconds for which they intend to schedule their integration service. It's imperative to note that the input must be a non-negative value, ensuring that it cannot be less than 0.

Schedule: Within the scheduling feature, users enjoy a comprehensive array of options to finely tailor the execution of their integration service. They can select the specific year, month, date, and day of the week to precisely define when the service should run. Additionally, users can leverage preset options for hours, minutes, and seconds, offering a granular level of control over the scheduling parameters.
To accommodate global operations, users are empowered to choose from various timezones, ensuring that the integration service aligns seamlessly with diverse geographical locations and organizational requirements. This multifaceted scheduling functionality not only enhances user autonomy but also facilitates the optimization of the integration service to match the intricacies of different timeframes and time zones.

Event Emails:
Within the designated space for event emails, users can configure the notification system. Here, users are required to enter the email address of the designated recipient who should receive triggered emails whenever the integration service is initiated or halted. This personalized notification mechanism ensures that the right individuals stay informed in real-time about crucial events related to the integration service lifecycle.

Advanced Setting

The Advanced Settings section is available under the Summary tab of the Integration Bridge page. It provides additional configuration options for fine-tuning the execution of data streaming jobs.

Advance Setting Feature has the following characteristics:

• Select Worker Capacity: Users can select the number of records workers will process.

• Number of Workers: This option allows users to select how many workers will work on their data processing. More the number of workers, lesser the time of processing.

• Source Response Wait Time: Users can set how long the system should wait for source data to arrive before moving forward.

• Log Stream Size per Line (in KB): This option allows the user to specify the amount of data that should be displayed in each log line.

• Log Rotation Size (in MB): This option allows users to configure the maximum size of each log file. Once the defined size is reached, the log file is compressed into a zip file, and a new active log file is created.

Example:
If you have a large dataset, say, 1 million records, you can speed up processing by enabling Advanced Settings from the Summary tab in the Integration Bridge.
In this example, the chunk size is 50,000 records, meaning the source system sends 50,000 records per processing cycle.

You can configure the following settings based on your requirements:

• Streaming Worker Capacity: 10000

• Number of Workers: 4

• Source Response Time: 1000 (in milliseconds)

• Log Stream Size per Line: 300

• Log Rotation Size: 50

With this configuration:

• The 50,000-record chunk will be split evenly across 4 workers.

• Each worker will process 10,000 records in parallel.

• Log lines are capped at 300 KB each.

• Once the log file reaches 50 MB, it is automatically zipped, and a new file is created.

• This leads to faster data processing and optimized storage.

---

Activate Parallel Processing

The Activate Parallel Processing allows data to be processed simultaneously for faster and more efficient execution.

Activate Parallel Processing feature has the following characteristics:

• Improves Performance for Large Datasets: Efficiently handles high volumes of data by distributing workload across multiple CPU cores.

• Minimizes Processing Bottlenecks: Reduces delays caused by single-threaded data operations.

• Ideal for Batch Jobs or Heavy Transformations: Especially useful in scenarios where complex data transformations or bulk operations are involved.

---

Log Stream Size per Line Parameter

This feature allows users to set the maximum size of each log line directly in the eZintegrations UI. This helps control how much information each log line holds, reducing delays caused by very large log entries during data pipeline execution.

Log Stream Size per Line Feature has the following characteristics:

• Helps manage logs efficiently in high-volume data integration environments.

• Prevents logging from becoming a bottleneck when large data sets pass through the pipeline.

• Allows users to configure and limit the size of each log line via the UI.

• Reduces delays in file writing caused by overly large log entries.

• Helps prevent excessive memory usage during logging.

• Improves readability and maintainability of log files for easier debugging.

Note: Log Stream Size per Line should not be less than 20KB.

---

Log Rotation Size (in MB)

This feature allows users to configure the size of each log file directly from the UI. Users can define the threshold at which a log file should be compressed into a zip file.

• Once the specified size is reached, the log file is zipped, and a new active log file is created.

• The zipped content will still be reflected in the dashboard for monitoring.

• When downloading logs, only the most recent (active) log file is downloaded, while older files are available in compressed format.

• By specifying a smaller size, users can optimize storage and improve performance by ensuring older logs are automatically zipped.