Objective and steps of the process
Our IT Integration Design guide aims to select and use Reference Blueprints to deliver the proper design of the IT integration flows.
Reference Blueprints align with Integration Domain, Integration Styles and Use-Case Pattern to offer detailed, prescriptive architectures. They help architects and integration teams design, implement, and standardise integrations using Integration's best practices.
- Integration Domains → Typical integration areas based on deployment models.
- Integration Styles → Ways in which integration is performed.
- Use-Case Patterns → Predefined reusable integration patterns for common scenarios based on best practices.
- Reference Blueprints → Architectural templates that prescribe the best integration approach.
Why This Matters
✅ Structured Integration Approach → Ensures standardisation across the enterprise.
✅ Predefined Use-Case Patterns → Reduces integration complexity by following Integration best practices.
✅ Prescriptive Reference Blueprints → Provides guided architectures for each scenario.
✅ Governance & Security → Ensures integrations are secure, scalable, and compliant.
✅ Technology Alignment → Selects the right integration solutions "automatically" based on use cases.
📌 Reference Blueprints fit between Integration Domains, Integration Styles and Use-Case Patterns, ensuring integration is implemented using standardised integration architecture principles.
How These Works Together
🔹 Step 1: Identify the Integration Domain
- Determine whether the integration is Cloud2Cloud, Cloud2OnPremise, etc.
- Example: SAP S/4HANA Cloud integrating with SAP ECC → Cloud2OnPremise.
🔹 Step 2: Select the Integration Style
- Identify if the exchange is process-based, data replication, event-driven, user-centric, or IoT-based.
- Example: If the goal is to synchronize business transactions, use Process Integration.
🔹 Step 3: Choose the Use-Case Pattern
- Select the predefined best practice pattern that fits the scenario.
- Example: If SAP S/4HANA Cloud needs to expose APIs for on-premise ERP, use API-based Integration.
🔹 Step 4: Apply the Reference Blueprint
- Design the integration flow with the recommended architecture, security, and governance model.
- Example: Use Hybrid Integration Blueprint with SAP Integration Suite and Cloud Connector.
🔹 Step 5: Implement Using Integration Platform Technologies
- Follow prescribed best practices and governance policies.
Reference Blueprints
Reference Blueprints serve as the architecture backbone of the Integration design process, ensuring that Integration Domains and Integration Styles are implemented efficiently and securely.
They provide our IT projects with prescriptive guidelines to build scalable, governed, and efficient integrations.
They are all based on existing or validated Integration Components of the Integration platform.
Examples
| Examples | |
|---|---|
| Integration Domains | Cloud2Cloud, Cloud2OnPremise, OnPremise2OnPremise, User2Cloud, User2OnPremise, Thing2Cloud, Thing2OnPremise |
| Integration Styles | Process Integration, Data Integration, Event-Driven, User, Thing |
| Use-Case Patterns | API-based Integration, Event-Driven Messaging, Data Replication, UI Integration, IoT Edge Processing |
| Reference Blueprints | Cloud Integration Blueprint, Hybrid Integration Blueprint, B2B Integration Blueprint, Event-driven Integration Blueprint |
