Session #1 - CampusLink APIs

This session was intended to be an overview of the technical components of CampusManagement's APIs. The sessions were presented by:

Phil Cutajar
Louis Ziggenhardt (? aka Ziggy)

Phil started the session out with an overview of the progression of systems architecture.

• 1st generation - mainframe
• 2nd generation - client server
• 3rd generation - Web Based (Portal)
• 4th Generation - Middle Tier
• This is where business rules are applied
• API is an interface to be able to interact with these business rules
  

Ziggy takes over Presentation

• Framework - A new middle tier
• Campus needed to create the business entity layer for the processes and rules
• What do the APIs offer?

1. Security
• Need authentication
• SSL
• Transaction level security (user roles honored, auditing, rollback)
2. Standard Messaging
3. Validations (syntax, semantics, business rules)
4. Error Handling
5. Scalability

What is the Platform

• Currently is .NET 3.0
• Go to .NET 3.5 with V10
• C#.NET
• SQL Server ( 2008)

Future Strategy and Planning

• Consolidate redundant code (remove business rules from client)
• Partners (CRM, Learning, Cornerstone, vantage)
• Use of Biz talk for passing transactions from client

WCF will handle all workflow areas

• Implies that there will be a transition period
  
• Business Process APIs for the "short term"
• All new development will go through WCF and Workflow APIs

API Processing can be scheduled

• Bottleneck becomes the DB
• API architecture handles this better due to more efficient transaction types

Requirements for Deploying APIs

• Software Development group well versed in SOAP based Architecture
• MS IIS and .NET Environment
• Mature CampusVue implementation

Support Resources

• Documentation
• Integration Services Group

When will Documents and Status change APIs be available

• Currently can get these through Integrations Services but they will not be rolled out into the released product for a while.