Enterprise Integration

Objectives

• To define the framework and direction for the architecture and design efforts of all projects on the integration roadmap

• Provide ‘tools’ for traceability from business and IT objectives through architecture to implementation.

• Provide a common vocabulary to communicate overarching Integration Architecture principles and direction across multiple communities within Columbia University including integration teams, web services, academic applications, PeopleSoft and SIS development teams, IT management and business groups.

• Provide the means against which to measure architectural compliance of the work product from the various Columbia University IT teams chartered to produce integration solutions.

• Provide guidance for building the Columbia University Integration Platform consisting of COTS solution (will be selected via RFP).

• Define the Columbia University Integration Reference Architecture

Architectural Standards

Enterprise Integration Methodology

Integration Templates

1. Interface Specification Template

2. Data Mapping Template

Three pronged approach

The preferred approach to integration in CUIT is via APIs if they are available or can be developed in the project time line. The team can explore ETL or custom in collaboration with Enterprise Architecture team. We definitely wants to stay away from file transfers.

• ETL - Use BODs ETL tool to load data
• APIs - Use APIs provided by the target system to get and post data

  • API Strategy (published Nov. 2016) 

  • API - InTake Process

  • API - Process Flow

  • Restful API - Best Practices

  • API Specification ({json:api} and OAS 3.0)

  • Schema Standards (json-schema.org)

  • API/Integration Domain Names

  • Use Architecture Patterns 

    • /wiki/spaces/CUITEA/pages/60130251
    • /wiki/spaces/CUITEA/pages/60130204
  • Security
    • OAuth 2.0 Protection Standard
      • CU-STD-INTR-001: OAuth 2.0 Scope Standards: API Coarse-grained Authorization
• Custom - Implement messaging based solution for real-time integration using one of the design pattern below

• • CQRS

  • Event Sourcing

  • Database per Service

  • Saga