Outlining SAP Integration Suite Capabilities

SAP Integration Suite is a comprehensive, AI assisted enterprise-grade integration platform-as-a-service (iPaaS) offered as part SAP BTP. It helps organizations connect applications, processes, people, and data—across both cloud and on-premise environments as well as within and beyond an organizations enterprise —in a secure, scalable, and flexible manner. Some of its key features and capabilites are:

• Pre-built Integrations

  The availability of a vast library of pre-built integration content (integration flows, APIs, connectors, etc.) for common SAP and non-SAP applications and scenarios. This significantly reduces integration development time and effort

• Low-Code/No-Code Development

  An intuitive graphical interface and drag-and-drop tools to empower citizen integrators and developers to build integrations without extensive coding

• Centralized Governance and Monitoring

  A single pane of glass for managing, monitoring, and troubleshooting integrations across the enterprise. This ensures visibility, control, and compliance

• Security and Compliance

  A single pane of glass for managing, monitoring, and troubleshooting integrations across the enterprise. This ensures visibility, control, and compliance

• Scalability and Reliability

  Robust security features, including encryption, authentication, and authorization, to protect sensitive data. It also supports various compliance standards and regulations

• Extensibility

  Allows developers to create custom connectors and integrations to meet specific business needs

• Integration Flows (iFlows)

  Graphical representation of the integration logic, defining the steps involved in connecting applications and exchanging data

• APIs

  Discover, protect, govern, and publish APIs to developers with API Management and SAP Graph.

• Connectors

  Pre-built adapters that simplify the connection to various systems, databases, and protocols

• Message Mapping

  Tools for transforming data from one format to another, ensuring compatibility between different systems

• Value Mapping

  Capabilities to translate code values from source system to target system

We will now explore the following components that are part of the SAP Integration Suite:

• Cloud Integration
• API Management
• Open Connectors
• Integration Assessment
• Migration Assessment
• Integration Advisor
• SAP Event Mesh*
• SAP Integration Suite, advanced event mesh*

SAP Integration Suite is deployable using two options:

• Public Cloud Deployment

  In this case SAP Integration Suite is deployed in an SAP BTP subaccount and all of its components run there.

• SAP Edge Integration Cell

• SAP Edge Integration Cell is a hybrid integration runtime offered as an optional extension to the SAP Integration Suite. It allows organizations to design and monitor integration content (like APIs and integration flows) in the cloud (using the SAP Integration Suite) while deploying and running the actual execution of these scenarios within their own managed private landscape (on-premise or private cloud). This allows integrations to run with minimal network latency and for sensitive data to be processed within an organizations on premise environment (which may be necessary due to regulatory requirements).

Cloud Integration which is a key component of SAP Integration Suite enables companies to connect SAP and non-SAP applications across the cloud and on-premises landscapes in a secure manner via messages allowing real-time or near-real-time data exchange. The specifics of an integration scenario are contained in an iFlow. An iFlow contains everything about an integration scenario from the systems involved in the message exchange (i.e., sender & receiver) to the adapters used (i.e., SOAP, ODATA, etc.) to the specific sequence of steps executed in processing the message (i.e., a message mapping step, a write message to a data store step, etc.).

One of the more useful features of Cloud Integration is predefined iFlows which save organizations time in implementing solutions for use cases involving SAP products. For example there is a predefined package of iFlows for integrating SAP Cloud for Customer and and SAP Marketing Cloud. A customer would have no need to create their own if an existing SAP iFlow exists. The SAP content has everything that is needed. This predefined SAP content has many of the hallmark characteristics of SaaS in that if the content changes (e.g., a new step added to the iFlow) then SAP will republish the iFlow and customers can then decide whether or not to activate the new version and if so when giving them some control over the timeline.

The content designer tool has everything necessary for customers to create their own iFlows. The tool uses Business Process Modeling Notation (BPMN) a graphical way of modeling the steps involved in an integration scenario. When the iFlow is deployed, the runtime objects are generated. The tool covers the entire end to end process of creating an iFlow. From setting up senders and receivers (and the corresponding adapters) to model syntax checking to simulation before actual deployment the tool encompasses all those capabilities.

One of the most fundamental concepts in iFlow design is establishing the sending and receiving systems and the adapters each will use. The sender is from whom the message originates and therefore from Cloud Integration's point of view it's an "inbound" message. Likewise the receiver is to whom the message will be forwarded to and therefore from Cloud Integration's point of view an "outbound" message.

The video below goes into more detail on connecting potential sending and/or receiving systems to Cloud Integration.

The scope of functionality Cloud Integration provides for processing messages is broad. Just a few of the different step types possible to model in and iFlow to process a message are:

• Message transformation ( JSON to XML conversion for example )
• Calling external systems or subprocesses
• Routing
• Storing data during processing
• Protecting messages via encryption

The sender of a message uses the attribute Quality of Service (QoS) to determine how a message is delivered. The QoS types are:

• BE (Best Effort)

  The message is sent synchronously. The sender waits for a response before it continues processing

• EO (Exactly Once)

  The message is sent asynchronously. The sender does not wait for a response

• EOIO (Exactly Once In Order)

  Multiple messages are sent asynchronously. Messages are processed in the same sequence that they were sent

SAP Cloud Integration supports API-based integration development (as an alternative to coding). The SAP Cloud Integration Design application provides graphical editors for designing the following types of APIs:

• OData API (an OData API-based integration scenario with OData V2 sender adapter).
• REST API (a REST API-based integration scenario with HTTPS sender adapter).
• SOAP API (a SOAP API-based integration scenario with SOAP 1.x sender adapter).

The administrative and monitoring tools of Cloud Integration enable integration developers and administrators to monitor message processing and cloud integration components. Some of its specific capabilities are:

• Monitor message processing
• Manage integration content
• Manage security artifacts and deploy them on the tenant
• Manage keystore entries
• Manage the lifecycle of keys

The figure above is a sample solution diagram. It uses the "Process Integration" integration style and the "Application To Application (A2A)" use case pattern. Integration styles and use case patterns will be explored in the next lesson Exploring SAP Integration Advisory Methodology

Application Programming Interfaces (APIs) are an important part of integration design and development. They act as a bridge, facilitating interaction between different software systems, whether they are on the same computer or across a network. In a way they are the unsung heroes of the digital world, working behind the scenes to power the applications and services that users interact with daily, making complex interactions appear effortless and driving continuous innovation. While this is undoubtedly a good thing organizations needing to create and manage a large number of APIs stand to benefit from an API management solution.

SAP API Management is that solution. API Management as part of SAP Integration Suite enables organizations to secure, manage, and monitor their APIs across their entire lifecycle. It provides a centralized platform for API providers to expose their business processes and data as APIs, and for developers to discover and consume these APIs in a secure and controlled manner.

Think of it as a gatekeeper and manager for your APIs, ensuring they are:

• Secure:Protected from unauthorized access and malicious attacks.
• Accessible:Easily discoverable and usable by developers.
• Managed:Governed and controlled to ensure performance and reliability.
• Monitored:Tracked to understand usage patterns and identify potential issues.

In the above graphic API Management is used to provide and API that in turn provides data to both a product microservice as well as an application client via an API that either can call directly.

As mentioned earlier in the lesson SAP Cloud Integration provides a large number of adapter for connectivity to various systems. While these adapters will suffice for a large number of integration scenarios in some cases more specialized adapters are preferred particularly with non-SAP systems and applications. Open Connectors capability within SAP Integration Suite makes it easy to build seamless integrations with over 150 non-SAP systems and applications using prebuilt connectors. One of the main advantages of working with Open Connectors is that it allows developers and citizen integrators to focus on building business processes rather than struggling with integration details. Other key features include:

• Pre-built Connectors:
  • Provides a library of over 170+ pre-built connectors to popular business applications, SaaS platforms, and data sources, spanning CRM, ERP, marketing automation, social media, collaboration tools, and more. These connectors handle authentication, data mapping, and error handling.
• Unified API:
  • Presents a consistent API across all connectors. You interact with a standardized interface, regardless of the underlying application or the type of backend. This simplifies development and reduces the learning curve.
• Security and Compliance:
  • Provides enterprise-grade security features, including encryption, access control, and compliance certifications.
• Accelerated Integration:
  • Upload and download data in bulk in a normalized way, regardless of the underlying service architecture.

The above graphic illustrates a sample use case utilizing Open Connectors. An application executed by an end user retrieves its data by utilizing an API (created and maintained via API Management). The API in turn uses a connector provided by Open Connectors to ultimately retrieve the data from a backend non-SAP source system. The same connector is used by SAP SuccessFactors (Employee Service Center component in the graphic) to also retrieve data from a backend non-SAP source system.

The SAP Integration Assessment tool, part of SAP Integration Suite, is a guided approach to evaluating an organizations integration strategy. It leverages the SAP Integration Solution Advisory Methodology (ISA-M) (discussed in more detail in the next lesson) to help define, document, and govern an integration technology strategy. This tool assists in selecting suitable integration technologies, defining patterns for consistent usage, and documenting decisions.

One of the tool's key features is its web based user interface that guides uses through the assessment process. Specifically it helps in:

• Defining integration patterns and ensuring consistent technology usage.
• Collecting requirements for integration scenarios.
• Identifying the appropriate integration technologies for your needs.
• Documenting your decisions and implementation approach.
• Providing recommendations for implementation.

The Integration Assessment tool can be used by various roles within an organization, including: Integration Architects, Business Domain Experts, and Integration Developers.

As mentioned earlier SAP Integration Suite is the comprehensive, AI-assisted integration platform as a service (iPaaS) offered by SAP and is recommended for all new integration projects. While the Integration Assessment Tool as just mentioned in the previous section is helpful in defining an enterprise wide integration strategy many organizations have successfully used integrations created with Process Orchestration / Process Integration (PO/PI) for many years. PO/PI is the precursor to SAP Integration Suite and the recommendation from SAP is to migrate all PO/PI scenarios to SAP Integration Suite. Migration projects require additional tools. The migration process of PO/PI scenarios to SAP Integration Suite is centered around three steps and for each step tools are available:

• Assessing and Planning Step
• Migration Step
• Testing Step

For the second step the Migration Tool is available. This tool --also a capability of SAP Integration Suite-- actually does the technical migration of integration artifacts from SAP PO/PI to SAP Integration Suite. In cases where only a few integration scenarios need to be migrated it is suggested that a separate SAP Cloud Integration iFlow (one for each scenario) be created. For a large number of integration scenarios, the pipeline concept can speed up the migration project and reduce effort and cost. Under the pipeline concept rather than a separate iFlow (each of which requires its own JMS queue) being created for each integration scenario a small number of JMS queues can be used to support just one iFlow where each "step" in the iFlow represents a unique integration scenario. This concept effectively combines many PO/PI iFlows into one SAP Cloud Integration iFlow. This strategy minimizes the number of JMS queues thus benefiting overall performance.

For the final step SAP provides customers with Regression and Test Tools from partner companies like INT4 or Figaf. SAP has worked with these partners to provide our SAP Process Orchestration customers with free use of their test automation tools during the duration of the migration project, to SAP Integration Suite, up to a maximum of 12 months.  Any continued use of the test tools for ongoing testing, or other capabilities, beyond the migration project would require a license from the partner. Additional test tools are available from certified partners at the SAP Store.

Integration Advisor is a powerful and unique cloud service within the SAP Integration Suite that revolutionizes integration development by leveraging machine learning and a crowd-sourced integration knowledge base. Think of it as a smart assistant that helps you accelerate and simplify the creation of integration flows between systems, especially when dealing with complex B2B and A2A scenarios.

Here's a breakdown of how Integration Advisor works within the context of SAP Integration Suite:

• Discovery & Guidance
  • • Integration Flow Designer: Guides you through the process of creating integration flows by suggesting relevant artifacts, patterns, and best practices based on your selected systems and use cases. It helps you choose the right integration technology (e.g., API Management, Event Mesh, Cloud Integration) for your specific needs.
    • Message Implementation Guideline (MIG) DiscoveryHelps you find existing MIGs (Message Implementation Guidelines) related to your industry or business processes. This significantly reduces the effort of defining message structures from scratch.
• Content Suggestion & Mapping
  • Crowd-Sourced Knowledge: Taps into a vast and ever-growing repository of integration knowledge, built from SAP's own expertise and contributions from a global community of integration experts. This knowledge covers various industry standards, message formats, and system interfaces.
  • Message Mapping Recommendations: Uses machine learning to analyze message structures and automatically suggest field mappings between different systems. This significantly reduces the manual effort required for creating complex data transformations.
  • Value Mapping Recommendations: Extends beyond field mappings to suggest value mappings for code lists, units of measure, and other complex data transformations. For example, it can automatically map country codes from ISO to a proprietary format.
• Prototyping and Validation
  • Simulation: Allows you to simulate the behavior of your integration flows and validate your mappings before deploying them to production. This helps identify and fix errors early in the development cycle.
  • Testing Framework: Provides a framework for creating automated tests to ensure the quality and reliability of your integrations.
• Testing Framework:
  • Integration Content Library: Enables you to create and share your own integration assets, such as message mappings and integration flows, within your organization or with external partners.
• Community Contributions: Allows you to contribute your own knowledge and expertise to the crowd-sourced knowledge base, further enhancing the capabilities of Integration Advisor.

• Browse the Library of Type Systems
  • The Library of Type Systems is a collection of standardized message templates for B2B, A2A, and B2G that are developed and maintained by the respective agencies. For example, SAP IDoc from SAP SE or ASC X12 from ANSI ASC X12. These standards facilitate the implementation of B2B integrations when used by business partners.
• Message Implementation Guidelines (MIGs)
  • The Message Implementation Guideline (MIG) is used in the Integration Advisor capability within SAP Integration Suite as the basis for creating a Mapping Guideline (MAG) and defines all the necessary information for implementing a customized message interface.
• Mapping Guidelines (MAGs)
  • The Message Implementation Guideline (MIG) is used in the Integration Advisor capability within SAP Integration Suite as the basis for creating a Mapping Guideline (MAG) and defines all the necessary information for implementing a customized message interface.
• Exporting Runtime Artifacts
  • Once you have created the Message Implementation Guidelines (MIG) and Mapping Guidelines (MAG), the next step is to use these artifacts in the integration solution to enable integrations with your business partners. Currently, the Integration Advisor capability within SAP Integration Suite supports the export of runtime artifacts for SAP Cloud Integration and SAP Process Orchestration. By exporting the runtime artifacts, the application automatically generates a set of schemas, scripts, and examples from a mapping guideline, including:
    • Schemes for syntax conversion, for example, from EDI syntax to XML or vice versa.
    • Schemes for the precise validation of user data based on the rules and constraints defined in the message implementation guidelines.
    • Preprocessing and postprocessing scripts for presorting payload data or enriching it with additional information required for mapping.
    • Main script for XSLT mapping.
    • Examples for testing the artifacts in the runtime.

The above figure is the landing page of Integration Advisor within SAP Integration Suite. In it usable type systems are displayed.

SAP Event Mesh enables event-driven integration and communication between different systems. It supports the creation of real-time applications and the orchestration of business processes.

SAP Event Mesh is a fully managed cloud service that enables applications to communicate through asynchronous events. The service offers the following main functions:

Publish business events

Publish business events from SAP and non-SAP sources in hybrid landscapes from digital core to extension applications through an event-driven architecture.

Consume business events

Consume business events from SAP and non-SAP sources across SAP's event-driven ecosystem including SAP Extension Suite, SAP Integration Suite and select inbound-enabled SAP back ends.

Seamless connection

Provides reliable data transfer for extension and integration scenarios through decoupled communication.

The following is an event mesh with a configured queue.

The following is a solution diagram with the use of the event mesh.

SAP Event Mesh

The Advanced Event Mesh extends the functions of the SAP Event Mesh by offering greater scalability and extended integration options.

Take advantage of a complete event streaming, event management, and monitoring platform that combines best practices, expertise, and technology for event-driven architectures (EDA) on a single platform. The following features are available for Advanced Event Mesh:

Event Streaming

Deploy event broker services, create event meshes, and optimize and monitor your event-driven system.

Event Management

Discover, visualize, share and manage various aspects of your event-driven architecture (EDA). You can also model your EDA to visualize the relationships between component relationships.

Event monitoring and insights

Use monitoring dashboards and confidential notes to identify potential issues before they negatively impact your brokers and event broker services.

The following is a sample solution diagram using the Advanced Event Mesh.

You can see from the comparison table that Advanced Event Mesh has significantly more features than Event Mesh.

SAP Integration Suite, Advanced Event Mesh

We've covered a lot of ground in this lesson. SAP Integration Suite has a complete set of tools for every aspect of integration design and development. We conclude the lesson by exploring one final tool, SAP Application Interface Framework (AIF). While integration developers and administrators deal with the development and administration of scenarios respectively, "citizen integrators" are capable of monitoring actual incoming and outgoing messages. Oftentimes they are in the best position to correct errors in messages as they have a strong and deep knowledge of the business data contained in the message. AIF is a tool within SAP S/4HANA that enables the creation, deployment, monitoring, and management of application interfaces. It simplifies the interface landscape, improves error handling, and enhances governance by separating technical and business aspects of interface management. While in theory integration developers and administrators can use AIF it It is specifically designed with citizen integrators in mind. Some of its key features are:

• Centralized Monitoring: AIF provides a single platform for managing all application interfaces, offering a message monitor for overview and detailed analysis.
• Error Handling: It allows for efficient error detection, correction, and re-processing, reducing the need for IT intervention in business-related errors.
• Interface Modeling: AIF supports interface modeling, data mapping, and value mapping, facilitating the transformation of data between different systems.
• Role Based Access: It enables role-based access control, allowing business users to monitor and manage interfaces relevant to their roles.
• Integration with SAP Focused Run: AIF messages can be monitored through SAP Focused Run, providing centralized monitoring for a wider SAP landscape.
• Guided Deployment: AIF offers a guided, template-based approach for adding logic to interfaces, simplifying the development process for IT users.
• Technology Agnostic: AIF supports various integration technologies (i.e., SOAP, IDOC) allowing reuse of logic and customizations across different interface types.

SAP Integration Suite is SAP's strategic Integration Platform as a Service (iPaaS) solution. It is a cloud-based solution that runs on the SAP BTP and is designed to connect and integrate applications, data, and business processes across diverse and complex IT landscapes.