Transcript Web Services

Web Services
MnSCU Web Services Roundtable
David Purcell, OoC IT
JoDee Haugrud, MN State Moorhead
Gary Hayden-Sofio, MCTC
Dave Kruse, SCTC
Introduction
- Why are we here?

Provide specific info on our services

Discuss realities of implementing

Discuss options, directions
Overview of Web Services

What is It?
 App
to App Communication
 Part of a Services Oriented Architecture
(SOA)
 Typically implemented using common
protocols and languages (HTTP and XML)
 A Tool for Integration – Loosely coupled apps
Overview of Web Services –
Simple Example
Types of Web Services

Using SOAP standards



SOAP Types



Because of the standard protocol, toolkits can handle SOAP
layer
Many Standards being built on top of SOAP infrastructure
(security, transactions, etc.)
RPC – Remote Calls – (MnSCU services)
Document Style – you define and transfer an XML document
REST





Applications define their own specs - typically a custom XML
response
Resource oriented
HTTP protocols – HTTP Get and Post
Simple to use
Doesn’t require any special tools
Web Services and the Campus





Useful for Application Development
May replace some needs for LADE services
Not a tool for Reporting – Should use Brio where
possible
Provides access to ISRS data – real time
Independent of Campus Programming
Languages
Web Services and the Campus Appropriate Uses
Small, discrete data sets
 Web applications
 Need real-time data
 Need to use a common function
(authentication, etc.)

Web Services and the Campus –
Not Appropriate For…



Large data sets (10k records, for
example)
Batch Processing
High Performance Needs
Current Web Services

Detailed Auth
 Used
for: Student/Staff can authenticate
against ISRS
 Inputs: user id, password, RC_ID
 Returns: user’s TECH ID
 Status: In Production
Current Web Services

Student Master
 Used
for: Getting demographic and academic
data for a student
 Inputs: RC_ID, Institution PIN, TECH_ID
 Returns: status, status message, and user
details (array of info)
 Status: In Production
Current Web Services

Course Searching (suite of services)
 Used
for: performing searches for courses
 Services Include:




Get General Search Options
Get Campus Search Options
Get Course List (performs search)
Get Course Detail (returns all info about a course)
arrays of special elements – include
relationships to others (not simple arrays)
 Status: In Production
 Returns:
Current Web Services

Course Searching (continued)
Search – Can search across all campuses
 Search On:
 General







Institution
Year/Term
General Subject (uses cip codes)
Keyword
Credit/non Credit
Graduate/Non Graduate courses
Offered/Cancelled/Suspended
Current Web Services

Course Searching (continued)
Search – Searches only in one campus
 Search On:
 Campus






Course Number
Institution Subjects
General Education Code
Open/Closed
Year/Term
Offered/Cancelled/Suspended
Current Web Services

Course Enrollment
 Used
for: getting enrollment numbers on
individual course or all courses in a term
 Returns: simple arrays of Strings
 Status: In Testing
Current Web Services

ISRS Query
 Used
for: Generic Query Platform for ISRS
 Inputs: RC_ID, Institution PIN, Query Name,
Query parameters (defined by query – simple
array)
 Returns: Arrays of information representing
database rows
 Status: Beginning a Proof-of-Concept Pilot
Current Web Services

ISRS Query (Continued)
 Expected
Process:
Campus developer determines query need
 Campus works with OoC IT staff to get query into
system
 Campus will need to get security access approved
for data needs
 Query tested by OoC IT and campus
 Campus includes query in their app

Resource

MnSCU Office of the Chancellor ITS Web
Services Site:
 http://its.mnscu.edu/isrs/webservices
Discussion – MnSCU Services


Implementation Challenges, Learnings
Technical Options