How to Implement Salesforce Integration Project
What is System Architecture
- System architecture is supported by a number of architecture domains, including system architecture.
- It explains how a company’s systems are interconnected and puts emphasis on their interactions and communication.
- It focuses on how systems exchange information with one another.
- It outlines the security measures for system integrations and the methods for user authentication and task authorization.
What is Integration
It is the process of integrating several different systems.
Real-World Integration
Internal ESB to 3rd Parties
- Salesforce to DMZ
- DMZ Relay to internal system
- Internal SOA Infrastructure
- On-Premises Data Access
- ESB (or Internal Apps) to Salesforce
- Batch Integration
- Data Replication
- On-Premises Data Staging
- Multi-Org
- Salesforce Point-to-Point
- Integration to Cloud Hub
- Hub to Each Endpoint
- Internal ESB to 3rd Parties
Integration Architectures
- Point-to-Point
- Hub-and-Spoke
- Enterprise Service Bus (EBS)
Architectural Overview – How to Document?
When working on a major corporate project, an architectural overview document is crucial.
- Documents the project’s scope.
- Explains the state architectures of the present, interim, and future.
- Links to pertinent documents and artifacts
- Brings a project team together
Key Artifacts
- Context of the system: optional
- Current and target system landscape diagram: Suggested
- Data model: required
- Logical data model – optional
- Physical data model/Entity Relationship Diagram – Required
- Role hierarchy: strongly advised
- Process flows or sequence diagrams are advised.
- A test plan is typically represented in a document or as a model in test management software.
- Mapping functional and nonfunctional requirements to solution components is known as the traceability matrix.
- Documentation for handover and release notes
- Others as required
System Context Diagram
In engineering, a system context diagram (SCD) is a diagram that illustrates the entities that interact with a system and establishes the boundaries between the system or a portion of a system and its surroundings. This diagram shows a system at a high level.
- Specify the scope,
- The main “actors,”
- The system components,
- Refrain from attempting to explain the technical design.
System Landscape
- Essential elements (systems and applications)
- Existing and being deactivated is new
- Existing and being deactivated is new
- Necessary Salesforce licenses and participants:
- Which actor uses which license(s)
- One or more organizations
- Essential third-party apps or systems
