Overview of Central Control, Distributed Execution

What is Central Control, Distributed Execution?

The Central Control, Distributed Execution feature provides a seamless, end-to-end approach to managing and optimizing your integrations, ensuring that they are fully compliant with local regulations, data privacy laws, and performance requirements.

The key concepts of Central Control, Distributed Execution are:

• Central Control: Provides a centralized control or management system that oversees the allocation and utilization of resources. It allows you to make informed decisions about resource provisioning, scaling, and distribution based on factors such as workload demands and performance metrics. The Central Control system acts as a single point of control, ensuring that resources are allocated efficiently and according to predefined policies.

• Distributed Execution: Refers to the practice of spreading out tasks or processes across multiple computing resources or nodes (virtual machines, containers, servers) distributed throughout the cloud infrastructure. In this approach, the workload is divided into smaller parts, and each part is run on a separate node. Each resource operates independently and manages its portion of the workload. This leads to better resource utilization, improved performance, and fault tolerance, as the failure of one node does not necessarily affect the entire system. Thus, it allows your cloud environment to efficiently manage varying workloads by dynamically assigning tasks to available resources.

The Central Control, Distributed Execution feature offers centralized control and management as well as provides better scalability, fault tolerance, and efficient resource utilization for your cloud infrastructure.

Central Control, Distributed Execution Components

The main components of Central Control, Distributed Execution feature are:

Integration Runtimes

A control plane that allows you to manage your entire Integration platform regardless of where the different runtimes are hosted, be it in your IBM webMethods Integration tenant, your own private cloud, or dedicated data centers hosted anywhere across the globe.

The control plane includes:

• User Interface: Allows you to manage and monitor integration runtimes through the graphical user interface (GUI) or web-based console.

• Workflow Management: Allows you to orchestrate complex hybrid integrations across different runtimes.

  For ease of use, the control plane is managed and maintained by IBM as part of your SaaS platform.

Edge Runtime

An edge runtime (execution plane) is an Integration Runtime that is linked to your tenant for remote management and monitoring purposes, thus eliminating the need to manage it individually or connect directly. Your integrations are deployed using an edge runtime.

An edge runtime performs the following tasks:

• Integration Connectors: Hosts connectors, which are software components that integrate with different back-end applications to allow data exchange between them. Connectors hide the proprietary and complex low-level code that is required to connect to the applications.

• Integration Services: Contains services that represent the functional requirements for your integration logic. Integration services include data processing and transformation logic that is used for governing the data exchange between applications, your partners, and apps.

• APIs: Includes option to expose your own APIs through integration services with zero code and host them wherever needed.

You can register multiple edge runtimes and even have multiple instances for a single runtime to provide load balancing and redundancy.

Cloud Runtime

A default runtime (execution plane) that is provided in your tenant to run integrations. You need not require any additional infrastructure to use the Cloud runtime. You can use the Cloud runtime when you do not want to setup an edge runtime in your own environment.

Central Control, Distributed Execution Benefits

• Unified view: Provides a single view to administer and monitor integrations, APIs, and data distributed across hybrid and multi-cloud infrastructures.

• Monitor: Enables to monitor and track the entire flow of data and transactions as they traverse through the various integrated components and systems, regardless of their network topology using webMethods End-to-End Monitoring.

• Seamless Tooling: Provides a unified and consistent approach to managing multiple runtimes, regardless of their deployment location. This includes your iPaaS tenant, private cloud, various regions, or even your own data centers. You can eliminate disconnected integration tools that need specialized dev and ops teams.

• Easier regulatory compliance: Enables organizations to be in compliance with data jurisdiction regulations, allowing businesses to manage data within specified regions or ecosystems, thus promoting adherence to data privacy laws.

• Scalability: Facilitates seamless resource scaling without disrupting the existing cloud integration, reducing costs and resource allocation time, optimizing efficiency.

• Enhances Resilience: Minimizes the impact of unpredictable events such as system failures. This cost-effective solution prevents a single server failure from disrupting interconnected networks, reducing the cumulative risk of failure, and eliminating the necessity for backend capacity preparations, enabling agile adaptation.

Integration Runtimes User Interface Elements

Integration Runtimes is the entry point for utilizing the Develop Anywhere, Deploy Anywhere and Central Control, Distributed Execution capabilities and it resides as a tab on the IBM webMethods Integration home page.

Integration Runtimes Page Layouts

The Integration Runtime page provides you two layout options to view the runtime instances:

• Card view

• List view

The Card View is the default view that displays the runtime instances as cards. However, you can switch to List View by clicking the List icon () located on the upper-right corner of the Integration Runtimes page.

Access Desired Data on the Integration Runtimes Page

The Integration Runtimes page can precisely display the data you need by utilizing the filters and search options.

Using Search

You can search runtimes based on the matching words entered in the Search text box on the top of the page. For example, if the runtime name is RHES_990POK001, you can either enter 990 or POK in the text box and click Search. The matching results appear.

Using Filters

You can use filters to view the desired runtimes based on the status and category types.

1. Go to Integration Runtimes. A list of all registered runtimes appears.

2. Select the applicable filter options.

   You can use a combination of these filter options. The sample screen that follows displays the runtimes based on the Offline and Enabled filter types.