Dashboard

The Integration Cockpit Dashboard provides a centralized, real-time snapshot of key components and metrics across your entire integration landscape.

Designed with Integration Experts in mind, it delivers instant visibility into the purpose and usage of each component.

By monitoring your most critical KPIs, the Dashboard empowers you to:

• Quickly identify bottlenecks, outliers or deviations

• Proactively address areas that may require attention, optimization or cleanup

Customizing Overview Start Page

The appearance of your cockpit may differ. To tailor your view, customize the Start Page under

Settings → Configuration → Start Page

Recommendation
Enable all checkboxes in the Start Page Settings (see screenshot above) to ensure that all key KPIs and metrics are fully displayed on your Dashboard.

KPIs

A KPI (Key Performance Indicator) is a measurable value used in the Integration Cockpit to assess the performance, reliability and efficiency of your integration landscape.

This section provides a summary of your most important KPIs.

Note: Click on the KPI names in the "KPI Quick Links" to jump to the detailed explanation for each metric. The right sidebar can also be used for navigation.

Robustness

Robustness is a KPI that indicates how stable and reliable an interface has been over the past 30 days. It helps identify unstable interfaces that may require attention.

The calculated Robustness value on the overview page is an aggregated value across all productive interfaces. It is showing the relation between successfully processed messages and their errors, helping you identify unstable or potentially flawed integrations.

Static Ranges

Robustness scores fall into one of the following four predefined categories, referred to as Static Ranges. These show the robustness as a percentage of success vs. failure in percent:

The four ranges and the period are currently static and not configurable.

Robustness Bar Color Ranges

You can define your own Robustness bar colors with specific thresholds under

Settings → Configuration → Start Page → Robustness

With the configuration shown above:

• Green is applied to values 95 and above

• Red applies to values 0 to 50

• The Yellow range (51–94) is assigned automatically as the span between the red and green thresholds.

Where else you see Robustness

On Interface level

You can view the robustness of individual interfaces within the Reporting & Metadata section:

Inventory → Interfaces → Catalog → <Select Interface> → Reporting & Metadata

This screen displays a list of interfaces available in your environment.

The Robustness score reflects the stability of the selected interface based on recent message processing performance.

On End-to-End level

A total robustness score is calculated across all interfaces within an End-to-End process.

This is displayed in the following section:

Inventory → End-to-End → <Select E2E> → Reporting

In the Reporting Section – Robustness Overview

In the Reporting Overview, only robustness scores from interfaces in the PRODUCTION category are displayed. This is displayed in the following section:

Reporting → Overview

This dashboard displays the following:

• Robustness distribution across four Predefined Score Ranges

• Top 10 interfaces by volume or relevance

• Insights such as Adapters and Traffic Evolution over the last 12 months (based on message count)

In the Reporting Section - Robustness

The Reporting – Robustness dashboard provides a centralized view of robustness scores across all interfaces, regardless of environment.

This dashboard provides:

• An aggregated robustness score across all interfaces

• A calculated total robustness value for each selected environment category (e.g. Production)

Robustness score classification

• 0–50 → Low

• 51–70 → Medium

• 71–90 → High

• 90+ → Very High

You can filter this view by:

• Data Source

• Environment Category:

  • DEVELOPMENT

  • PRODUCTION

  • QUALITY

Additionally, you can select your own custom environment if configured.
For setup and customization, see 2.5 Environments in the Onboarding guide.

Supported Data Sources for Robustness

• SAP_IS_CI: SAP Integration Suite (Cloud Integration)
  Robustness Formula:
  Robustness = COMPLETED / TOTAL

  • Note: RETRY and ENDED statuses are ignored.

• SAP_IDOC: SAP ABAP Backend IDocs
  Robustness Formula:
  Robustness = (Success + Warning * 0,5) / TOTAL

  • Note: Ignores IDocs with 'Ready' status.

Decommissioning

Decommissioning is a KPI that tracks the number of interfaces in the Production environment that have not processed any messages (no traffic) over the past 30 days.
It helps identify inactive, outdated or unused interfaces that may be candidates for cleanup or retirement.

The KPI supports cost optimization, reduces system complexity and helps improve overall integration quality.
A high number of inactive interfaces may indicate technical debt - components that are no longer in use but still exist in the current landscape. These can include temporary workarounds (such as the use of “No Fit” adapters) that were never properly replaced.
The more unused or outdated interfaces remain, the harder and riskier it becomes to maintain, scale or even troubleshoot your integration landscape.
By removing what is no longer needed, you keep your integration environment clean and stable.

Decommissioning Threshold Configuration

You can define the threshold ranges and bar colors for the Decommissioning KPI under

Settings → Configuration → Start Page → Decommissioning

With the configuration shown above:

• 🟩 Green: Fewer than 20 inactive interfaces (no traffic in Production in the last 30 days)

• 🟥 Red: More than 100 inactive interfaces

• 🟨 Yellow: Automatically spans between Green and Red thresholds

Note: The “value” refers to the number of inactive interfaces.

Complexity

Complexity is a KPI that shows how technically complicated an interface is within your integration landscape. It is based on various factors, such as the number of connected systems, types of adapters used and whether mapping logic or transformations are involved. This metric aids in assessing the development and maintenance effort required for each interface.

Each interface is automatically classified into one of four categories:

• Low

• Medium

• High

• Very High

This classification gives you a quick overview of how simple or complex your interfaces are to manage, monitor and maintain.

The Complexity KPI helps to:

• Spot technically complex interfaces that may become bottlenecks

• Support simplification efforts by identifying where redesign might reduce effort or risk

• Improve stability and maintainability by reducing unnecessary complexity

Simpler interfaces are typically easier to support, faster to adapt and more reliable in production.

Complexity Classification by Interface Type

Depending on the Data Source, interfaces in the Inventory can be classified as more or less complex. The following table shows the criteria by interface type:

Frequency

Frequency is a KPI that measures how often each interface is executed within the monitored period (past 30 days). It provides a quick overview of runtime activity across the integration landscape and helps identify how actively interfaces are being used.

Interfaces are automatically classified into four static frequency categories based on message volume:

• Low

• Medium

• High

• Very High

This classification is calculated using live traffic data and is updated regularly to reflect current usage patterns.

The Frequency KPI helps to:

• Identify high-traffic, business-critical interfaces that are executed frequently and may require extra monitoring or safeguards

• Prioritizing monitoring and alerting coverage for high-frequency flows

• Detect underused or inactive interfaces that may be outdated or no longer needed

• Plan resources and capacity (e.g. scaling, performance tuning) based on how much traffic each interface handles

Interfaces in the Very High category typically handle significant volumes of traffic and may require additional safeguards, such as:

• Custom alert thresholds tailored to high activity levels

• Robust error-handling mechanisms to prevent cascading failures

• Performance tuning or infrastructure scaling to maintain system stability

On the other hand, low-frequency interfaces may indicate limited business relevance or outdated use. These should be reviewed - especially when combined with other KPIs like Complexity or Decommissioning - to determine whether they are still needed or can be retired.

Adapter Usage (Top 5)

Adapter Usage is a KPI that displays the five most frequently used adapters in your integration environment - for example, SOAP, SFTP, File, HTTP_AAE or Mail.

It highlights the technology distribution and dependency concentration across your landscape.

Adapter Usage KPI helps to:

• Identify dominant protocols and technologies

• Detect potential single points of failure due to over-reliance on specific adapter types

• Support standardization and modernization by reducing fragmented or legacy adapter usage

Adapter Usage (Strategy Fit)

The Strategy Fit indicator displays how well the adapters used in your interfaces align with your enterprise’s integration strategy.

Defining clear fit categories supports future design decisions, identifies modernization needs and helps detect strategic misalignment early.

Recommendation
Use this feature to ensure consistent and fit adapter usage across your integration landscape. Regularly review and adjust fit levels to stay aligned with your evolving technology standards and strategic priorities.

To define or edit your strategy fit categories:

Settings → Configuration → Start Page → Adapter Strategy

Integration Cockpit Dashboard

The Dashboard Panel in the Integration Cockpit provides a centralized dashboard with customizable Quick Links for easy access to the external resources most relevant to your organization.

In the displayed example, the following resources are added as Quick Links:

• SAP Integration Suite – Direct access to the SAP Integration Suite environment.

• Documentation – Link to the Integration Cockpit user documentation.

• Integration Strategy – Link to the organization’s documented integration approach.

• SAP Cloud ALM – Link to SAP Cloud Application Lifecycle Management.

• Team Space – Link to a collaborative workspace.

Recommendation
Make sure to add your own relevant Quick Links for the most frequently used resources in your organization.

Managing Quick Links

You can modify and customize Quick Links under

Settings → Configuration → Start Page → Links

Add a Link:

Click the “+” icon, enter a Name and URL, then click Save.

Remove a Link:

Select the checkbox next to the link you want to remove and click the “−” icon.

Traffic

Traffic provides visibility into the number of messages processed across your productive interfaces over the past three months. It helps you identify usage patterns, monitor integration activity and support capacity planning across all your integration landscape.

The calculated Traffic value on the overview page is based on the Message Count from the Production environment and includes the current and previous two calendar months. It reflects the total number of messages processed, helping you monitor fluctuations in system load and usage.

Inventory

The Inventory is the central repository of the Integration Cockpit. It collects and displays all discovered integration interfaces and related metadata from connected systems and landscapes - forming the foundation for visibility, enrichment and governance across your integration environment.

Explanation of Metrics

These metrics represent:

• Interfaces → Discovery coverage

• To‑Do → Transform and Enrichment completeness

• End-to-End → Business-level integration maturity

Recommendation
Use the Inventory as a strategic entry point into your integration landscape.

Focus on:

• Enriching interfaces with metadata and creating Transformation Rules

• Defining complete End‑to‑End flows

• Monitoring To‑Do volume as a maturity indicator

Landscape Check

The Landscape Check provides an overview of your integration environment across tenants. It helps you assess consistency and completeness of integration artifacts in both Design- and Runtime for each integration component.

Artifacts are evaluated in two scopes:

These checks are grouped into the following categories:

The displayed values are based on the number of integration artifacts found in each environment and their version status.

The Landscape Check helps to:

• Validate whether integration content is consistently deployed across tenants

• Monitor Designtime and Runtime alignment within each tenant

• Detect outdated, inconsistent or missing integration artifacts

Color indicators

These visual markers help you quickly interpret version status:

• 🟨 Yellow: Version mismatch

• 🟥 Red: artifact is missing or has been deleted

Note: For detailed analysis, see Landscape Check for SAP Cloud Integration in WHINTIC

Footer Information

The footer of the Integration Cockpit provides quick access to critical metadata and organizational context:

• Bottom Left – Company Branding:
  Displays the brand identity, such as WHINT Solutions, reinforcing platform origin and credibility.

• Bottom Right – Logged-in User Identification:
  Shows the active user's full name (e.g. Farzin Abrishami-Kashani), ensuring session transparency and audit clarity.

This area serves as a persistent reference point, especially helpful in shared environments where user accountability and platform ownership are crucial.

Last Updated: August 26, 2025