-
SAP’s integration strategy for intelligent enterprises
- 1) Predefined integration: alignment of domain models helps to ensure that master data can be exchanged in an efficient and convenient way between SAP applications, including prebuilt integrations in SAP Business Accelerator Hub.
- 2) Open integration: SAP is open for any third-party integration as well as for custom extensions that leverage public APIs. Open Connectors: prebuilt connectors for more than 170 third-party
- 3) Holistic integration: SAP Integration Suite supports a variety of integration use cases, ranging from process, data, user, and "thing" to analytics-centric integration
- 4) AI-driven integration: SAP is using AI techniques to simplify the development of integration scenarios. One example is the Integration Advisor capability of SAP Integration Suite
-
SAP Integration Solution Advisory Methodology (ISA-M)
- It is a template in PowerPoint, aimed at integration architects, existing integration solutions can be documented and described, as well as integration requirements can be determined and mapped to specific services.
- 1) A collection of typical integration styles and patterns
- 2) The assignment to integration services
- 3) Architectural designs for integration, including decision criteria
- 4) Define roles and your responsibility within integration scenarios
- 5) Openness to SAP and third-party integration technologies
- 6) Use by target groups such as corporate architects and integration architects
- 7) Use as a template for defining custom integration policies
- 8) Reusability within organizations, projects, or services Adaptation to specific needs
-
ISA-M Cycle
- 1) Assess your integration strategy: document/review your architecture, scoping of focus areas/building blocks, use case driven approach
- 2) Design your hybrid integration platform: map use case patterns, derive integration guidelines, reflect customer context
- 3) Define integration practices: define solution architecture blueprint, add decision criteria and key characteristics, establish integration as recognized discipline
- 4) Enable a practice of empowerment: democratize integration delivery, define areas for service integration, establish a shared developer comunity
-
Positioning of the Integration Suite from a more technical perspective
- 1) Cloud-Integration: Seamless integration of everything and everyone (A2A/B2B) in real time.
- 2) API-Management: Make your data and processes available as APIs. Manage the E2E lifecycle.
- 3) Integration Assessment: Tool support for ISA-M to define and execute an integration strategy for companies.
- 4) Integration Advisor: Accelerate the implementation and maintenance of B2B scenarios through machine learning.
- 5) Trading Partner Management: Accelerate onboarding and maintenance of B2B integration scenarios with trading partners.
- 6) Open Connectors: Accelerate connectivity to non-SAP applications.
-
Integration Suite add-on capacities
- 1) Master Data Integration: Ensure a consistent view of master data within an integrated intelligent suite and its ecosystem.
- 2) SAP Data Intelligence: Extract, transform, and load ETL scenarios for data lakes and data warehouses.
- 3) Event Mesh: Event-based integrations with predefined events from SAP applications.
- 4) Connectivity: Establish secure connectivity between cloud applications and On-Premise systems.
- 5) SAP Graph: Unified API for accessing SAP-managed data that can be used to create new extensions and applications using SAP data.
- 6) Alert Notification: Provides a common API for providers to publish alerts and for consumers to subscribe to these alerts.
- 7) Cloud Transport Management: Management of software products between accounts in different environments by transporting them over different terms.
- 8) Internet of Things: Bring raw sensor data into the context of business objects and use the data in analytical or transactional business applications.
-
SAP API Management
- 1) Building APIs: API portal is an application that provides a common platform for API designers to define and publish APIs
- 2) Publishing APIs: A Product is a bundle of APIs. It contains metadata specific to your business for monitoring or analytics. For example, all APIs related to CRM can be bundled as one CRM Product.
- 3) Analyzing APIs: API Management provides comprehensive analytics capabilities to understand the various patterns of API consumption.
- 4) Consuming APIs: API Business Hub Enterprise is an application that provides a common platform for application developers to consume APIs
- 5) Monetizing APIs: SAP API Management provides a monetization feature to all API providers in order to generate revenue on the use of APIs
- 6) Discover API Packages: In API Management, you can discover API Management platform supported API packages available in SAP Business Accelerator Hub on the API Portal.
- 7) API Designer: The API designer is based on the OpenAPI Specification (OAS) standard, which may not be limited to conversion of APIs from one format to another (for example, from RAML to YAML, JSON to YAML and vice versa)
-
SAP API Management use cases
- 1) Enterprise Digital Apps: Build Enterprise Digital Apps for employees (Field Sales/Services/Support) customers, partners.
- 2) Real-time API Integrations: Share enterprise data from data lakes, business system to suppliers, partners and customers. Expose enterprise transactions and processes as APIs for suppliers and customers.
- 3) Enterprise Microservices: Build and manage API-first micro-services. Enable DevOps of micro-services.
-
Components of SAP API Management
- 1) API Provider - Summarizes many different sources
- 2) API - The new API with URL (No. 4)
- 3) API Designer - An openAPI definition
- 4) The new API URL - Acts as proxy
- 5) Policies - Edit the request and response message
- 6) Product - Implementation of an API
- 7) Application based on a product
- 8) Additional services such as monitoring, testing, and more
- 9) Entry in API Business HUB Enterprise.
-
Sources of API provider
- 1) Open Connectors.
- 2) Through Cloud Connector to all SAP On-Prem Backends ( ECC, SAP S/4HANA On-Prem, PI, PO and more).
- 3) Cloud Integration which delivers an OData or SOAP API.
- 4) APIs from Internet.
- 5) From the SAP Business Accelerator Hub for prototyping.
-
Creation of APIs Based on the API Provider
- 1) Create an API using the Create button with the following options:
- 1.1) API provider (No. 1 at concept diagram)
- 1.2) URL (No. 2 at concept diagram)
- 1.3) API proxy
- 2) Create an API using menu links with the following options
- 2.1) Create in API Designer (No. 3 at concept diagram)
- 2.2) Import an external API
-
What are Policies?
- A policy is a program that executes a specific function at runtime. They provide the flexibility to add common functionalities on an API without having to code them individually each time.
- Policies provide features to secure APIs, control the API traffic, and transform message formats. You can also customize the behavior of an API by adding scripts and attaching them to policies.
- You can apply a policy on the request or response stream. You can also specify if it is applicable on the proxy endpoint or target endpoint. For information on the types of policies supported by API Management, see Policy Types.
-
What are Products in Context SAP API Management?
Products are artifacts that appear on the SAP API Business Hub Enterprise portal. The SAP API Business Hub Enterprise portal is accessed using its own URL. This is accessible in the SAP Integration Suite Cockpit through the navigation in the upper right corner of the interface.
-
Procedure for creating an Product
- 1) Create a Product using the Create button.
- 2) Add the entries under the Overview tab.
- 3) Add an API under the APIs tab.
- 4) Choose the Publish button.
- 5) Open the API Business Hub Enterprise portal.
- 6) Check out your Product.
-
API Business Hub Enterprise portal
- offers a platform to deploy products with your associated APIs, centrally in the company. This should be the only place where developers search, find, and test APIs, and ultimately consume the corresponding proxy URL in their own processes.
- 1) Your own user management
- 2) A role-based access to the products
- 3) An additional authentication Layer with its own API key
- 4) A self-registration Unknown developer
-
What Is SAP Cloud Integration?
- 1) SAP Cloud Integration support end-to-end process integration through the exchange of messages.
- 2) It is based on the open source framework Camel from the Apache Software Foundation.
- 3) It is one of the core capabilities of the SAP BTP Integration Suite.
- 4) The development, deployment, and monitoring takes place in the browser with graphical tools.
- 5) It is one of the LowCode/No Code tools
-
Explore Predefined Integration Content in SAP Business Accelerator Hub
- 1) Open the SAP Business Accelerator Hub at: API.SAP.com
- 2) Navigate to the Discover Integrations tab.
-
SAP Cloud Integration API for Message Processing Logs
The Monitor itself is based on a cloud integration API. To investigate this, navigate to: api.sap.com and search for the SAP Cloud Integration API. Find the APIs here: API.SAP.com
-
Build-In Monitor for Message Monitoring
- 1) Monitor Message Processing
- 2) Manage Integration Content
- 3) Manage Security - Admin Place
- 4) Manage Stores
- 5) Access Log.
|
|