You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Overview

This working area is a broad investigation of the SOA and API spaces jointly.  The popularity of commercial APIs, lightweight interfacing techniques  have both overtaken and reinvigorated the need to apply SOA principles in the enterprise.  Below is a general grouping of SOA API areas followed by an outline of the initial groups and content.

SOA API Stages

Areas of investigation

Architecting/Selling

Determination of capabilities needed in an SOA API environment
Leveraging Business Drivers (Analytics, Evidence-based decisions, monetizing access to enterprise data)
Leveraging IT Drivers (better security, reduce complexity)
Investigation of overlap with teaching and learning

Constructing/Deploying

Enterprise data defintion and management
WS02 solution (selection, integrations, operations)
Design of common API across higher education
Securing APIs (authentication and especially authorization)
Messaging (role of ESB solutions, push vs pull direction)
Mobile device integration

Using/Governing

Creating public APIs (use cases, balancing openness and resource control)
How to move enterprise from old techniques (ftp, direct database links) to SOA
Impact on data custodians and new governance opportunities

Working Groups

High-level Group (Contact: Jim Phelps)

For Evaluation work - Share what you went through in selecting your ESB software.
Why did you pick WS02? What else did you look at?
How are you using your ESB
Sharing Design Documents and Patterns
Sharing business cases and use cases used to make the case for investment
Are folks planning on single instance of an ESB or Federated so other Departments/Colleges can have their own?
And who locally (within University) manages/administers the ESB and other aligned software/services.
Best practices on integration between ESB and ETL.
What about changing out the infrastructure? What should I plan ahead for if I think we are going to change out our ESB?
What are the design concerns you should consider if you want to make the infrastructure swappable?
What about cloud deployment of the infrastructure either IaaS or Amazon WS / EC3?
Public access to data and API supporting community of developers

WS02 Subgroup (Contact: Jon Torrones)

Current participants
U. Michigan
U. Chicago
U. Buffalo
U. Madison
Ohio State

Core modules to be implemented
Technical support (via WS02 or community?)
Selection and evaluation - priorities and selection process with respect to WS02 and ESB software.
Brokerage service/directory of APIs (registry for discovery by the world)
Shared Performance and Security , work arounds, etc.
Workday Integration

Data Definition and API Design Subgroup (seeking a leader for this sub-group)

Best practices on integration between ESB and ETL.
What higher education specific standard data models have you come across? IMS, EduPerson, etc.
How are people leveraging open standards? Did any of the standards come out-of-the-box from the vendor source system

  • No labels