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

Integration Strategy

1. API Strategy (published Nov. 2016) 

   1. Draft next version (unpublished google doc)

Architectural Standards

TODO: Turn each of these into a formal AAG/ASC approved and published standard:

1. Enterprise Integration Methodology

2. API Specification ({json:api} and RAML 1.0)

3. Schema Standards (json-schema.org)

4. API/Integration Domain Names

5. OAuth 2.0 Protection Standard

   1. CU-STD-INTR-001: OAuth 2.0 Scope Standards: API Coarse-grained Authorization

6. Interface Specification Template

7. Data Mapping Template

Restful API - Best Practices attempts to integrate the above standards in a single document.

Integration Processes

1. API - InTake Process

2. API - Process Flow

Public APIs

Resources

• Introduction to Deploying Mule: From Workstation to Production

• Mulesoft Product Documentation

• Mulesoft Developer collaboration

• CUIT Mulesoft API developer notes