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
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.
Integration Processes
- ETL - Use BODs ETL tool to load data
- APIs - Use APIs provided by the target system to get and post data
...
Architectural Standards
Enterprise Integration Methodology
Patterns
...
/wiki/spaces/CUITEA/pages/60130204
...
...
APIs
...
...
Use Architecture Patterns
- Security
Messaging
...
Documentation
- API Portal
Integration Templates
...
- Custom - Implement messaging based solution for real-time integration using one of the design pattern below