1. Presented by: SIF 3.0 Environments, Zones & Contexts Melbourne Developer’s Workshop November 2013 Joerg Huber

2. © Systemic Pty Ltd November 2013 Melbourne MCG: SIF 3.0 - Env., Zone & Context 2 Overview  What is an Environment?  What is a Zone? Compare it to SIF 2.x Zone Default Zone  What is a Context? Default Context  How do these relate to each other? Do I need all of these?

3. © Systemic Pty Ltd November 2013 Melbourne MCG: SIF 3.0 - Env., Zone & Context 3 What is an Environment? The “SIF 3.0 Environment” the totality of every service the Consumer might possibly provision itself to access. Based upon authentication constraints however, the Consumer’s access to some services it can see might be restricted. It is provided by:  Provider in a direct Environment  Environment Provider in a brokered Environment Holds mainly  Service URLs scoped for each zone  Access Rights for each Service scoped for each zone

4. © Systemic Pty Ltd November 2013 Melbourne MCG: SIF 3.0 - Env., Zone & Context 4 What is a Zone? – Consumer’s Point of view An Environment has 1 or Many zones!  There is always a DEFAULT Zone. If no zoneId is provided in the REST URL then the default Zone is assumed.  A Zone is a collection of Services a consumer has some sort of access to In SIF 2.x they were a collection of SIF Objects an agents had access to. Access rights are allocated in each zone for each service Context may be assigned to each service.  Various types of Services Object Services (StudentPersonal, SchoolInfo etc.) Utility Services (Alerts, Zone Registry etc) Functional Services (i.e. Endo-Of-Year rollover).

5. © Systemic Pty Ltd November 2013 Melbourne MCG: SIF 3.0 - Env., Zone & Context 5 What is a Context? – Consumer’s Point of view A Context is an optional Data Model-specific metadata that may accompany a Consumer Request as a way of further scoping and restricting the possible Provider.  There is always a DEFAULT Context for each Service. If no contextId is provided in the REST URL then the default Context is assumed.  In a zone there can be more than one Provider for the same “SIF Object” as long as they operate in a different context! Current Students Special Ed Students  Contexts are NOT global they apply to a specific Service Provider in a zone

6. © Systemic Pty Ltd November 2013 Melbourne MCG: SIF 3.0 - Env., Zone & Context 6 Relationships…  A consumer may connect to one or many Environments.  An Environment may have many Zones.  A Zone may have many services.  Within a zone there can be more than one provider for the same SIF Object (i.e StudentPersonal) as long as they use a different context.  A consumer who creates a SIF Object in more than one Zone or Context may be given more than one RefId for the same Object! One RefId per service it calls for the same object. A service is scoped per environment, zone and context.  May sound complicated but most of the time you will operate in the DEFAULT Zone and Context.

7. © Systemic Pty Ltd November 2013 Melbourne MCG: SIF 3.0 - Env., Zone & Context 7 Question Time… Questions?