ILM Core Concepts and Architecture

Challenges: No formal relationship between the language of the enterprise and the system. We don't know what we dont know. People interpret policy. Policies are interpreted. Policies are often nebulous. Systems cant understand policy unless people who program them understand policy.

Wait, isnt this an “under the covers” look at ILM2? Don't give me marketing technobabble!!!

Communication = Contracts

Workflows = Process

Policy = ????

Assertions: Common Patterns

• Provisioning
• Group Management
• Password Management
• White Pages
• Policy Management
  

“We react to events on sets of identity with processes.”

What are the issues presuming this axiom is true

• collection of resources
• request model on collection
• sets which organize data
• blah blah blah

ILM 2 Steps

1. Resources you want to manage

• regulate your processes
• synchronize with environment
• CRUD on identity in ILM2
• core object types and schema
• you can modify types or create new ones

2. requests on resources has three phases

• authorization
• authentication
• action

3. sets organize resources
4. events trigger processes

• request events are defined as a quad
• transition events are a double
  processes formalize responses to events

5. Demo

Now Demo of the tool...again

What happened to architecture?

What if the language you create to mirror the business process isn't granular enough to reflect your needs?

how do you manage these processes? You dump them and they have to resubmit?!?! NFW!!

Clients Outlook, Sharepoint, Windows, Custom, Office 2007 (IE 6, Firefox, Windows XP SP2+)

ILM 2 will use web service standards (Windows Communication Framework, Windows Workflow Foundation)

ILM 2 will be server heavy up to 5 servers minimum – Sharepoint (WSS not MOSS), Resource Management Service, Resource Management DB, Metadirectory Service, MetaDirectory DB, **Exchange Server 2007**

Longhorn Server Standard with SQL 2005 SP2+ 64 bit ONLY

They MIGHT cluster MIIS **NO COMITTMENT and NO commitment on SQL Clustering with Support on MIIS

No event based model for MA's. No error handling for MIIS. Here's what we get maybe

“codeless” provisioning, improved performance, more adapters