Running Thoughts

Tim Bauer's webcast summaries/insights

Live Mesh: Goodbye Facebook & Friendfeed?

Ask 3 people what Live Mesh is you’ll get three answers. Ask 97 more and you’ll get blank looks. Good thing innovation is not a democracy.

Live Mesh was put to a ‘technical release’ last week to perhaps 20,000 of your closest friends. The interesting thing was as you listened to the jabber they all portrayed it differently. Some boring and some hinting at what could be. It was the latter that got my interest but it took three different webcasts (raw scribble from each below) to boil it down for me.

Details Notable Points
Webcast(s)

Duration(s) Respectively:

  • ~40m, ~10m, ~35m

Speaker(s) Repectively:

  • Vid 1 – Who knows. Guys on Mesh Team.
  • Vid 2 – Amit Mital. Faceman on Mesh for MSFT.
  • Vid 3 – Ray Ozzie. Head man @ MSFT (came from Groove).

Recommend to Watch? Depends.

  • Each one is a different audience. Vid 1is for the average consumer, vid 2 is for the companies that are in similar spaces (ISVs, partners of MSFT), and vid 3 is more of a strategist view.
1. The Basics – A very transparent file share, remote PC control

  • For those looking for the quick answer. The features that are here and now is a very transparent sharing of files between your devices (phone, laptops, tower) AND friends (email em and they get a virtual folder of your folder). Plus you can login to that rig similar to remote desktop but via the mesh. Through firewalls (DOH! I just logged into my work PC without my RSA / VPN login – can you say security breach).

2. Now add some spice – Updates native with the folder view.

  • So the first thing isn’t too exciting (sharing folders) unless you are in charge of security (then its a headache). For those not grabbing aspirin, you more spice from the seamless injection of Mesh into typical tasks (excellent usability after MSFT’s Ribbon debacle). An example is how the any folder shared by mesh shows you automatically what changes your ‘mesh’ of friends have done to the folder at a document level. Holy smokes. Now we are starting to enable very nicely basic, document centric collaboration. This is like automatic twitters (I’m timbauer on twitter by the way) to the group you are collaborating on documents with. “Hey, I changed this file”, “I added this one”, “I nuked that one”

3. Now add some sizzle – You Become Facebook.

  • People in the blogsphere get their panties in a bind over the aggregation sites taking advantage of their pieces of content. Like the debate (nicely written by Louis Gray) around aggregation sites allowing conversations on content produced elsewhere (they lose potential visibility and traffic revenue). What if your comments on XYZ thing were shared to all people in your mesh peer-to-peer? Instead of a central site like Twitter or Facebook or Friendfeed … you just had a backbone like Live Mesh? The development style would shift to consuming peer to peer facades … facades that pulled from the mesh and synch your thoughts (basically files of data) back to the originating peers. You, in short, become facebook without facebook as it is today. All you need is your favorite “Live Mesh” facade on the local device. Presto.

3. MSFT Strategery – Use What They Have (Documents) To Get What They Don’t (Marketplace/Search).

  • MSFT is losing at this time the battle in search and social networks. The beauty of live mesh is the strategy it enables for them. They have always controlled a large share of the desktops and with it the digital assets that reside there. What they have realized (I think) is that if they can rebuild the social network into a social PEER-to-PEER network (where they provide the ‘to’ infrastructure) they can regain control or at least relevance. Ozzie’s tenure w/ Groove has to be behind this mindshift. Enable people share the chunks of social network activity (files, posts, articles, comments, etc) in a peer-to-peer synch model … not some push to a central site concept like Facebook. In doing so MSFTs software plays a central role. And with a central role they can inject things like … say … how to do an AdSense on the stuff you share on the mesh that gets views leading to commerce. I wonder what Google thinks about that … hehe.

In summary, Live Mesh is worth pondering. What you see now is misleading. It is NOT is just a repackaging of what has been around for awhile (synching files between PCs, remote desktop connectivity). If what is hinted at above is realized it could become the platform for transparency of sharing all files … links, tweets, comments, images, blog posts, docs … across all devices … pcs, phones, OTHER SYSTEMS. If you ponder that prior sentence you can see how it disrupts the current centralized model (sites like MySpace, Facebook, Friendfeed) for social networking. There is no facebook or friendfeed required. All the pieces are pushed around … peer to peer … via live mesh. All you need is your favorite “Mesh” reader to see all the ‘file data’ being synch’d to you and rolled up the way you want it. And MSFT has leverage in that market (PC devices per consumer).

Consider me sold. MSFT’s vision of peer-to-peer when fully baked will trump the current centralized sites that drive it today.

** START OF RAW SCRIBBLE TAKEN WHILE RUNNING **

***********************************************
******** 1st VID – HANDS ON WITH LIVE MESH **********
***********************************************
http://on10.net/blogs/nic/Hands-on-with-Live-Mesh/
• 4/24/2008, 6:13 AM
………………○ Live Mesh Team
………………………………§ Noah
………………………………§ George
………………○ Referenced at MIX a few months back
• 4/24/2008, 6:14 AM
• Goal put you at center of your computers and stuff
………………○ Data
………………○ Application / Computer access
• Use cases
………………○ Tie to your rigs
………………○ Data synch
………………○ Remote Desktop (Bauer words)
• BAUER COMMENT – ISNT THIS A FANCY UI ON EXISTING FUNCTIONS?
• 4/24/2008, 6:16 AM
• Demo
………………○ Blue folders allow synch and share across mesh
………………○ BAUER COMMENT – Team file sharing?
………………○ Uses remote desktops (through firewalls and NATs)
………………○ BAUER COMMENT – Might press AMZN’s AMI model … relative to vendor play of on demand usage … but AMZN has payment engine behind usage .. Not clear here if they can
………………○ Through a browser
• 4/24/2008, 6:19 AM
• Browser
………………○ Browser experience is slower
………………○ Also have client experience
• 4/24/2008, 6:19 AM
• Folders
………………○ Live on ALL machines
………………○ Auto replication?
………………○ INCLUDING VIRTUAL DEVICE
………………○ Bauer comment — So they are pushing to virtual storage (backup) …
• Timeline
………………○ See members
………………○ See timeline
………………○ See presence
………………○ Bauer comment – Looks like office live
• 4/24/2008, 6:21 AM
• Data
………………○ See anywhere
………………○ BAUER COMMENT – Might be a killer for sharepoint … alfresco … for users that use those tools soley around document share
………………○ BAUER QUESTION – File locking … edit conflicts
• 4/24/2008, 6:23 AM
• How hard to add device to mesh
………………○ Add piece of software … connects to cloud
………………○ BAUER ? – can you connect to multiple mesh’s
………………○ Not on mobile and Mac yet
………………………………§ Working on it
• 4/24/2008, 6:25 AM
• Roadmap
………………○ They say this is the 1st step to putting users in center of all their stuff
• How convert folders to mesh
………………○ Simple right click ‘add to mesh’
………………○ Choose what machines get the ‘push’ (versus pull) and force immediate
• Sharing to friends
………………○ Use LiveID … but to invite just send via email
………………○ Share (bauer ? – not edit)
• Location of files
………………○ In the cloud … right now … for sharing outside of mesh
………………○ You can synch to your mesh machines
………………○ So they do push down to devices AND the cloud (offline file)
• 4/24/2008, 6:29 AM
• File types supported, size limits
………………○ None
………………○ Initial release is 5GB of data in cloud
• 4/24/2008, 6:30 AM
• How did this come about / fit into SaaS vision of MSFT
………………○ Everyone has many devices
………………○ How make work as one
………………○ Bauer comment – Kills (depending if not tied to workflow, tagging, etc functions) the salesforce ‘content management’ play … why would you do that .. Create a mesh for you company and put the files there
• 4/24/2008, 6:32 AM
• Products and Solutions that Work Now
………………○ Windows Live … exists and augments
………………○ This is a platform to bring together data and devices
………………○ Then build from there
………………○ Easier file / data sharing platform
• 4/24/2008, 6:33 AM
• Platform .. Will we see different solutions making products from it
………………○ Live Mesh based on synch feeds (ATOM, RSS, etc)
………………○ Other people can plug in and store data in feeds
………………○ App to synch favorites
………………○ App to store todo lists
………………○ App to track stuff
………………○ Could have apps in their UI (Bauer comment – requires MSFT) or as an API (Bauer Comment – like AMZN)
• 4/24/2008, 6:36 AM
• How get access
………………○ Mesh.com … invitation only
• 4/24/2008, 6:38 AM
………………○ SkyDrive / Foldershare
………………………………§ They are all one group
………………○ Bauer comment – If they are all one group it is unlikely this is a free play (pricing not mentioned … key in what isn’t said). However office live is free (but its in beta) and does a similar function (w/o synch local, provides cloud).
***********************************************
******** 1st VID – END — *************** **********
***********************************************
**
**
***********************************************
******** 2nd VID – AMIT KEYNOTE ******************
***********************************************
http://blip.tv/file/854328/
Web 2.0 Expo
10m
…………..○ 4/25/2008, 6:30 AM
…………..○ Bauer comment – how about that pump up music at the start [wink]
…………..○ Amit
…………..○ 4/25/2008, 6:31 AM
……………………….§ Web is center
……………………….§ We connect via many devices
……………………….§ How to keep those devices in synch
……………………….§ Ours
……………………….§ And our trusted friends
…………..○ Settings and local favorites
…………..○ Device types – picture frames, macs, phones, laptops, towers, etc
……………………….§ Bauer comment – how many of those devices are on the web?
…………..○ Unified Device management
…………..○ 4/25/2008, 6:34 AM
…………..○ Feeds
……………………….§ Unified feeds
…………..○ Apps
……………………….§ Web based app management
……………………….§ Apps know devices and their capabilities
…………..○ Drop dead simple
……………………….§ Bauer comment – doesn’t jive w/ commentary so far on blog space
…………..○ Demo
……………………….§ Capture video of kid w/ phone
……………………….§ Dad sees on laptop real time on airport
……………………….§ Ims back
……………………….§ Shares a song to his daughter … next second
……………………….§ While kids next room are gaming
…………..○ 4/25/2008, 6:36 AM
…………..○ Everyone gets access to tech preview that is @ Web 2.0 Expo
…………..○ Device Ring is Core Metaphor
……………………….§ On windows PC
……………………….§ Mac / Mobile Next
……………………….§ Future more devices
……………………….§ Folder for anywhere access
……………………………………□ Bauer comment – interesting play … mesh compatible play on device sales like picture frames, touch tables, etc … fully compatible you get more features … becomes an iphone/ipod angle / barrier for MSFT devices
…………..○ 4/25/2008, 6:39 AM
…………..○ Mesh Bar
……………………….§ Single view of devices
……………………….§ Members in folder
……………………….§ News and events in the folder
……………………….§ Notifier lives on task bar … all up view of action on mesh
……………………….§ Also avail on live desktop to get webview
…………..○ 4/25/2008, 6:39 AM
…………..○ Use case shown is just ONE scenario
…………..○ Their focus is PLATFORM
……………………….§ Define model digital relationship between devices, people, assets
……………………….§ OpenAPI
……………………………………□ Yes, MSFT is about Open
……………………………………□ Shows Datamodel browser for Livemesh … dev can mesh format (xml, rss, atom, etc) … so you choose lang/tools … how you interact w/ live mesh
……Bauer comment – How is different than friendfeed?
***********************************************
******** 2nd VID – END ***************************
***********************************************
**
***********************************************
******** 3rd VID – AMIT KEYNOTE *******************
***********************************************
Channel9
John Udell Interviews
http://channel9.msdn.com/ShowPost.aspx?PostID=399578
4/23
36m
…………..○ 4/25/2008, 6:43 AM
…………..○ Whats it like to be @ MSFT (3yrs now)
……………………….§ Was @ IBM. Tremendous on potential impact
……………………….§ He does business, product strategy … intersection
……………………….§ So great job for him
…………..○ 4/25/2008, 6:45 AM
…………..○ What like taking over Gates role
……………………….§ SKIP
…………..○ GOTO 7:30 IN (MESH STARTS)
…………..○ Talk about environment MSFT faces
……………………….§ Mainframe was todays sexy utility. Timesharing. All was there in 70’s.
……………………….§ PC revolution was empowerment to consumer.
……………………….§ Swing of pendulum
……………………….§ Web grew in era of dialup … so built for that … force decentralized .. Thin terminal
……………………….§ Broadband penetration allows fatter clients
……………………….§ Both sides have good power (CPU, Storage) now
……………………….§ What design patterns work for backend and frontend
……………………….§ PC started for one computer for a subset
……………………….§ Moving now to not just one pc person … multiple devices per user … how to tie together … data … personal and cloud … MSFT wants to enable those solutions that balance leverage both
…………..○ 4/25/2008, 6:51 AM
…………..○ Internet OP SYS Space (AMZN, Google). How does MSFT history enable or drive action for them.
……………………….§ MSFT’s Approach.
……………………….§ Knew Bill / Steve since 1981
……………………….§ DNA of MSFT is a platform company … so need ISV community
……………………….§ Platform
……………………….§ Discussions of what different industry models will look like, be built like … given cloud computing … no specifics
……………………….§ MSFT wants to just enable that building … not be the buildings
……………………….§ AMZN. Ground up. Make raw resources (VMs, AMIs) to the developer. Power play.
……………………….§ Google. Tries to simplify cloud w/ constraints. So they serve a niche
…………..○ 4/25/2008, 6:55 AM
…………..○ 16:30 in
…………..○ LIVE MESH … folder share … screen share … can confuse true vision
……………………….§ MSFT core environment — multi device environment
……………………….§ Enterprise side … solved by MSFT via SMS
……………………….§ Now solve for consumer (device management)
……………………….§ So that is one path
……………………….§ 2nd is devices don’t / aren’t built well to work together
……………………………………□ Bauer comment – Is this their trump of OPENID … or could they push to use mesh to push data to various devices (including SYSTEMS)
……………………….§ Data flow … like feeds
……………………….§ Applications … be configured and liscensed
……………………………………□ Bauer comment … again … is this a slow entry to single user
……………………………………□ Bauer comment … msft takes what they have (user content, consumer) and uses mesh to push into systems they don’t control … devices they don’t control … they maintain relevance by owning/channelling the user profile
……………………….§ 4/25/2008, 7:01 AM
……………………….§ File and folder synch gives user a taste of power
……………………………………□ Bauer comment – I think it just allows the user to dismiss … now if the goal is to addict and get them using it (fits theories above) … then this is smart
…………..○ 4/25/2008, 7:02 AM
…………..○ Go beyond files/machines … bring people into the equation … Less obvious … connection to the web … How to optimize … spell that out
……………………….§ Two things (1) rich apps enable on PCs to share settings across devices (2) also websites extend their function to the world of devices
……………………….§ Groove reference … stumbled on … centralized websites … provision workspaces .. Invite users in … users want to take offline … wanted website to go offline … groove was peer sharing … so it do that well
……………………….§ Live mesh fills void of groove … infra … one service … manage synch to devices … data might be peer-to-peer or encrypted or through the cloud … but devices don’t care … developers don’t care … use infra … to push to devices
……………………………………□ Bauer comment – This is alert thingy on steriods … if all apps are synching real time … you go to your mesh console to see the same activity
……………………………………□ Bauer comment – majority of consumers are not sharing over web … in theory … msft has high ground if they can convert that user base via mesh
……………………….§ Use that simple tech … website … device … website … cloud
……………………….§ A feed of feeds … one thing a “mesh object” … represents a site … an element of that feed is other feeds … so an app can have many feeds … members, news, calendar, etc … or custom ones (transactions, recommended links, comments on a site)
…………..○ 4/25/2008, 7:08 AM
……………………….§ Folder is a mesh enabled Object
……………………….§ Item in feed is sub feed
……………………….§ Standard schema by item
……………………….§ News feed off a folder … see to right of folder … item by entry
……………………………………□ Bauer comment — So it would be like alertthingy or twitter offline
…………..○ 4/25/2008, 7:10 AM
…………..○ Banking example …
……………………….§ Local host and do stuff w/ an offline app
……………………….§ Developers want one way of working w/ mesh
……………………….§ Web version of live mesh … and client … same code
……………………………………□ Bauer comment — like AIR
……………………….§ Called MOE (mesh operating environment) … cloud MOE or client MOE same one
…………..○ 4/25/2008, 7:11 AM
…………..○ Synch problems .. How evolved from mistakes of groove
……………………….§ New team … he sponsored
……………………….§ There is a DNA trail … playdoh, lotus notes, groove, live mesh
……………………….§ More work w/ them during his CTO tenure not as much lately
……………………….§ Basic synch, interaction … that is similar
……………………….§ Groove power of adhoc invites … bypass centralized security … so groove users will get that part of mesh
……………………….§ Hope people feel that mesh is very lightweight … notthing there … works across firewalls, nats, double nats … few knobs to turn
……………………….§ Developer kit is NOT on mesh.com right now
***********************************************
******** 3rd VID – END ***************************
***********************************************

** END RAW SCRIBBLE TAKEN WHILE RUNNING **

April 26, 2008 Posted by | 1-Definitely Watch This | , , , , , , , , | 2 Comments

Apple / MSFT Faceoff: Kawasaki vs Ballmer (staged?)

Interesting, antagonistic, yet somewhat staged keynote @ MSFT’s Mix a few weeks back. They had Kawasaki (an Apple evangelist) interview Steve Ballmer (CEO MSFT) on the state of MSFT. Here was the net of their verbal banter in the first 35-40 minutes.

Webcast Details Notable Points
Title: Kawasaki Interviews Ballmer

Speaker: Guy Kawasaki

Variety of notches in Guy’s belt. Head of marketing for Apple on Macintosh product in 80’s. VC now as well as writer. Handful of startups he is driving but none have done much.

Speaker: Steve Ballmer

CEO of MSFT since 2000. Not sure if I would give him a stellar rating in that role over that period — Google taking search space, Apple taking consumer products, Open Source pressing into Enteprise Stack, not gaining foothold in enterprise app market.

Where: URL

Recommend to Watch? Maybe.

  • If you like a staged banter, this might amuse.
1. MSFT befuddled on how to get share of search market

It was interesting how Steve shifted off Guy’s questioning around the Yahoo bid. To me MSFT seems befuddled on next steps .. leading them to a buy reflex. It may be better for them to innovate a search angle around micro markets like blogs. The blog authors (or similar microsites like social networks) will go w/ a different advertising provider if greater value can be produced than Ad Words. That could take the form of a price war … but hey if they are serious.

2. Recruiting Struggles @ MSFT?

Guess even the big dogs struggle with attracting top talent. Interesting how he points out landing people is rarely about the top compensation package … rather the role and potential to impact. Implies that startups can innovate but can’t reap/scale that innovation. How much do you have the scale an innovation Steve to be successful Steve? Is scale where fulfillment is for hires?

3. Ballmer’s Week: 1 day personal study, 1 day customer, 1 day internal meetings.

This was an interesting point from Steve on how he tries to create balance in his weekly calendar. Stephen Covey would be proud. He has sharpening the saw, relationships, and operations.

They blathered on around other topics – Vista, Firefox Emergence, Silverlight, etc. But really, the key was watching Ballmer continuing to demonstrate transparency and portraying MSFT as the underdog. I suspect they are concerned with the partner base beginning to shift to other alternatives (SaaS, ERP, Open Source, etc) and are tyring to calm the troops.

As always, here are my raw notes for those amused.

** START OF RAW SCRIBBLE TAKEN WHILE RUNNING **

http://wm.istreamplanet.com/customers/ms/300_microsoft_mix_080306.asx
Kawasaki Interviews Ballmer
*Garage Ventures, Trumors.com
*Ballmer
–Why Yahoo? Search and advertising on internet. Will be next big thing. They need to be in there. They made an offer. Waiting.
–Zero Sum Game requires Killing Google? Yes we have to have a strong position.
–Who is primary competitor? Google? Apple? Four things – desktop (no google, apple yes), server/enterprise (ibm, linux..no google), entertainment/devices (no google has emerging via youtube/etc), online (google dominants .. little engine that could)
–Apple thoughts? Apple does a good job … entertainment / devices … could be losing market … to iphone … desktop
–Guy? Acknowledges need for exchange server w/ mobile … which gives MSFT the enterprise market (better)
–Facebook? An advertising focused partner. Partner with them. Buy small piece of the company. put a few $100M. Ford guy (father works for ford). Few $100M not small. For MSFT w/ $60B in year not huge.
–What drives him? silverlight 2.0 excited. change the world #1. Works w/ the smartest people around. #2. Challenge and competition is good. #3.
–Describe day? Three types. (1) customer meeting day. (2) doctor in office internal days (3) think/write/research day.
–Email. 60-70 pieces. got mail from spam. distro lists abusive not people. no virtual assistant.
–where is bill / post bill msft? this year goes part time. focus on foundation.
–Different way to have whole > sums.
–Recruiting young employees. Best brightest. Work on things that change the world. People need $. Most people think they wouldn’t get $. 1990. Stock was flat. Get rich isn’t primary source of recruiting value.
–Most startups fail.
–Guy’s son won the tournament ..for Halo.
–OS Wars, Anti Trust, etc — no history w/ kids. Young people should know MSFT does more than XBOX. Ballmer –> Opp is same. Make great products. 10-15 years ago what was hot isn’t good now?
–How does guitar hero, xbox, fit in? 17M xbox owners, 11M live subscribers, 1B windows users so opp is there. % of users are free w/ live.
–Silverlight? PC/Internet. Design/develop for mass adoption (HTML) or do RIA. WPF + Silverlight … gets best of PC and WWW in one form as a dev/designer.
–Silverlight launched last year? Last year. 1M downloads a day. Broaden # of desktops w/ silverlight. WPF is high % as part of windows update.
–vista? Heavier than my PC. Heavy. Powerful. Missing drives (talking about AIR). DVDs are passe.
–MSFT lost focus. Move forward or become less relevant. No thing like specialization. Established in desktop/enterprise. Going for two new … consumer (appl) and search ().
–Windows market share. EU.
–Vista. Consumer issues is app compatibility and driver issues. Drivers getting upgraded. SP1 shipped. App compatibility. Uptake will increase. Consumer market.
–Firefox. IE. What is happening there. Built presence and position. Firefox position.
–Browser innovation. Firefox. Safari.

33M in (continue)
** END RAW SCRIBBLE TAKEN WHILE RUNNING **

March 24, 2008 Posted by | 3-No Go (unless you are bored) | , , | 3 Comments

MSFT VSTS and Macroscope

Well I guess you know you have arrived when MSDN will do a webcast on your extension to one of thier products. See below for details but basically they are going to do a review of the Macroscope Process template for VSTS on MSDN.

Definitely a consideration for a shop that is (1) MSFT and (2) looking for more methodology rigor around the VSTS toolset. Basically, Fujitsu has taken their Macroscope methodology and baked it into VSTS. Not bad.

Tim


From: Ajoy Krishnamoorthy [mailto:Ajoy.Krishnamoorthy@microsoft.com]
Sent: Tuesday, August 08, 2006 9:00 AM
Cc: Masayuki Katayama; John Voorhies; Brooke Banbury
Subject: MSDN Webcast on Macroscope for VSTS – Announced at http://msdn.microsoft.com

The announcement for our upcoming (Sept 5th) MSDN web cast on “Macroscope for VSTS” is announced in MSDN. Please check the “Events and Web Casts” section at http://msdn.microsoft.com/vstudio/teamsystem/.

FYI

ajoy krishnamoorthy
Enterprise Strategy Consultant
Microsoft Consulting Services
Email: ajoyk@microsoft.com
Cell Phone: (614) 403-8164
Blog: http://blogs.msdn.com/ajoyk

September 5, 2006 Posted by | Uncategorized | , , , | Leave a comment

MSFT InfoPath – Sinker w/o a Hook?

I continue to watch webcasts like this occasionally

Office InfoPath Webcast LINK

as I am intrigued with how MSFT is trying to position it. Adoption rates on this enabler of data capture via email and the web is not high but they are continuing to press so its worth watching. Really the only two keys I took away today was this:

    1. Angle = Rapid Development They clearly want to continue to move to a model that allows layman (non techs) to control the UI while the technical team moves more into the application stack (don’t start the religious debate to if both roles can be one person). I don’t doubt that we could get a better form result quicker by leveraging InfoPath and getting the business side to prototype in it (which then is further tweaked by the tech team).
    2. The Hook (or lack thereof) — Plan for the future Thats what MSFT wants you to do. They realize most apps are either browser or client server in nature. However, they want you to ponder the value of building in a manner (that, per the above might be quicker) that also can automatically (basically) deploy w/ full features to a browser. Also detached processing where a form in an app could go off an be sent to someone in an email without the surrounding application. Blah blah you might say … but that might ring interest with some tech leadership.

Here are the rough notes for those amused:

• Pradeep Rasam. Program Mgr Office InfoPath
• Recommended Webcast April .. Gray Nelson … (details of infopath)
• Agenda
………….○ Rapid Development
………….○ Smart (client) or Browser deployment
………….○ Post Back Control
………….○ Deployment
………….○ Hosting Client in Windows App in browser or client app
• 3:00 – Enable Infopath to Browsers / Mobile
• 4:45 – Demo – Infopath in a Browser
………….○ Rich Text Boxes
………….○ Drop down fields
………….○ Dynamic fields (insert row)
………….○ Data Validation
………….○ Conditional Formatting
………….○ Firefox has same capabilities
• 8:00 – Overview
………….○ InfoPath Designer (publish xsn)
………….○ Browser
………….○ InfoPath Client
………….○ MSFT Office System Server (publish to, xsn gens aspx)
• 12:30 – Submitting Forms
………….○ Smart client talks directly to database
………….○ Browser goes through infopath office server .. Which talks to the db server
• (bauer thought – design once is what they are pushing but I can’t say if client’s really have a ton of applications that need forms that are online live (browser) and that exact form needs to go offline for field use for example. Occasional but not large volume … their push is that build it so YOU COULD go to web … or vice versa … )
• 16:00 – DesignOnce Demo
………….○ No more MSFT XML Parser
………….○ 24:00 – Some coding examples inside of InfoPath (against system.xml)
• 25:00 – Deployment
………….○ Sharepoint Deploy
……………………..§ Publish to doclib
……………………..§ Form templates
……………………..§ No code
……………………..§ Domain trust
……………………..§ Data connections via data connection library
………….○ Server Deploy
……………………..§ Prepare form for admin deployment
………….○ 29:00 – Deployment Model Demo
……………………..§ Central Admin Page in InfoPath Admin (on Office Server?)
……………………..§ Goto Manage form templates
……………………..§ Site collection with form
• 32:00 – Hosting
………….§ Windows
……………………..§ Doc lifecycle in Office uses this. Word property editors are infopath forms
……………………..§ No ink entry (IRM)
……………………..§ No loading activeX in browsers
……………………..§ VB App example .. 2 form controls .. In VS .. Show how you load infopath into the form (open XML directly) .. 1 liner ..
……………………..§ Can also route InfoPath forms to another page at completion
………….§ Browser
……………………..§ Launching forms from links
……………………..§ Query parms control behavior such as (XsnLocation, XmlLocation, OpenIn, SaveLocation, Source)
………….§ ASPX pages can also Host
45:00 – Demo Complex Scenario
………….○ In VS
………….○ Add XMLFormView control
………….○ MultiView Control .. Changes based on data keyed
• 53:00 – Summary
………….○ Complex Scenarios possible
………….○ Rapid Deploy
………….○ Host in Browser or Client Apps
• 54:00 – Q&A
………….

August 17, 2006 Posted by | Uncategorized | , | Leave a comment

People Ready Processes – MSFT Biztalk + Sharepoint?

Watched this webcast today due to my ongoing desire to understand how MSFT is positioning the integration of BizTalk Server (BTS) and Sharepoint (SP).

People Ready Processes

It was a nicely done deck w/ a mix of MSFT’s angle on why the two (SP and BTS) go together in solutions. I recommend watching it. The keys I took away were:

    1. People Ready Processes Interesting angle here. Hanging off the overall marketing blitz of people ready software coming out of MSFT. Basically they are saying that bringing BTS (system focused process automation) and SP (people focused process automation) together creates people ready processes. Not bad. Amusing how they pointed out (not exactly true) that BPR was about removing people. People Ready Process automation is about enabling them (not true entirely either). Still nice spin.
    2. There is that System Analysts Modelling Processes Live Again. To do this they focused on a demo by one partner showing how the System Analyst can push processes to BTS and not stomp the definition that was evolved, in there, by the developer. So a custom solution (implied by earlier webcasts) is not the only means to achieve this.

Again a solid presentation. Worth watching regardless of camp. For those amused here are my detail notes:


• BTS & Office Sharepoint Server
• Agenda
………….○ Overview of BPM
………….○ Office Sharepoint + BTS
………….○ Partner solutions
• 1:30 – BPM Overview
………….○ Strategy / Org Design / Processes
………….○ Enable via tech
• BPM = People Ready Business
• 4:00 – Why Process Matters
• 4:30 – Next Era of Automation
………….○ Old – Replace paper (doc scan)
………….○ Old – System centric auto (EAI)
………….○ New – Both (People Ready Processes)
• 7:30 – People Ready Process
………….○ BPR Removed People
………….○ People Ready Processes Enables them
………….○ Steps
……………………..§ Model/Design – same tools
……………………..§ Develop/Deploy – same tools
……………………..§ Manage/Interact –
……………………..§ Analyze/Optimize – Drill down
• 10:30 – Breadth of Processes
………….○ Spectrum – Collab to Transactional
………….○ Spectrum – Adhoc, (two in middle) to Fixed
………….○ Spectrum – Individual, Team, Cross Team, to Cross Division
• 14:00 – Tool Layer
………….○ Spectrum – Sharepoint to Process Svr
………….○ Common tools (design, monitor, run)
• 17:00 – Customer Example
………….○ OHA (Oncology Hematology Assoc)
………….○ Clinical Medical App.
………….○ End to end … unstructured team enablement to connection to backend systems
………….○ Tablet PCs used for capture. Sharepoint for teaming. VS & BTS for system integration.
………….○ www.microsoft.com/customerevidence
• 19:30 – Loan Approval Demo
………….○ From unstructured to structured
………….○ Process
……………………..§ Website to
……………………..§ Sharepoint to
……………………..§ WWF to
……………………..§ BTS to
……………………..§ End Tran systems
………….○ Infopath form in webpage
……………………..§ [bauer comment – very slow – claimed vpc issues]
……………………..§ [bauer comment big push to move forms in sites to be infopath based]
………….○ Save to SP
………….○ BTS picks up transaction on save to SP
……………………..§ Checks credit
……………………..§ Reviews customer history etc
……………………..§ Credit score wait, when receive decides what to do
……………………..§ 27:00 – Creates (BTS) a word doc w/ a credit report that someone should review (based in Sharepoint) … put information panel @ top to enable the workflow in the document.
………….○ Want to analyze the workflow in aggregate and see where optimization of workflow (auto approvals, time per step, etc)
……………………..§ BTS can provide inform from BAM in SP what the key statistics being tracked (like loans requiring loans requiring human review)
………….○ If a very system focused process maybe just BTS … if human exception processes tied for notable volumes SP is viable
• 33:00 – Partner Solutions
………….○ BPMS Partners
……………………..§ ITP
……………………..§ ProActivity
……………………..§ ProForma
……………………..§ Semtation
……………………..§ Simul8
……………………..§ K2.net
……………………..§ Captaris
……………………..§ Skelta
……………………..§ inRule
……………………..§ RuleBurst
………….○ 35:00 – ITP Commerce – Process Modelling Solutions
……………………..§ Product – Process Modeller for Visio …
…………………………………□ BPMN syntax in visio
…………………………………□ BPEL, XPDL, XLANG mapping
…………………………………□ Word integ / excel integ
…………………………………□ Team repository
…………………………………□ Model analysis
……………………..§ Show Visio w/ their BPMN stencil … How KPI go to excel
……………………..§ Export to BTS (from Visio). Include BAM KPI definition file.
…………………………………□ Creates instrumented orchestration in BTS
……………………..§ Import BAM data to Excel (BAM data). Via Process Modeller (their tool)
……………………..§ 42:00 – Summary
…………………………………□ Model in Visio
…………………………………□ To BTS via XLANG
…………………………………□ Push BAM def to BAM AddIn for Excel
• 44:00 – Roadmap
………….○ BTS 2006 release (3/06)
………….○ Next – o12, .NET 3.0, BTS r2
………….○ Beyond – Modelling, WWF integration, Commoditization of low level integration
• 48:00 – References
………….○ WWw.microsoft.com/BPM
………….○ Partners list —
……………………..§ www.microsoft.com/biztalk/solutions/bpm/partners
……………………..§ [bauer comment – are we on that list]
• 50:00-Q&A
………….○ How developer in BTS takes visio and imports?
……………………..§ Use the BPEL lang or the tool demo’d. Superset of BPEL is XLANG (their partner supports that too).
………….○ Integration of BAM to BI capabilities in o12 (business scorecard and forms point)?
……………………..§ Easy BAM is based on sqlserver analytics cube. So any BI client can hit.

August 1, 2006 Posted by | Uncategorized | , , , | Leave a comment

MSFT and WSS 3.0

Watched this webcast

LINK


today around WSS 3.0 due to our project w/ a client in Milwaukee kicking off. Goal is to base thier lead management system on the WSS infrastructure. Key question being do we need 3.0 or not. After watching this I would say yes. Outside of that tactical info … here were the keys I saw:

    1. Sharepoint 2007 as Framework. It was interesting to see them begin to demo how a SP server could become the piece of framework for ALL custom applications … especially basic ones for data management, content management, collaboration functions, etc. Database and code generated on the fly.

    2. Many ECM issues solved. In this release, if all is true I would agree that SP 2007 becomes a viable platform for doing medium level ECM tasks (viable for middle market). Issues like global meta models (via content types), cross site searching, have been solved.

    3. Alot of good reasons for upgrade to WSS 3.0. See details below but things like enforced check out option, or versioning models, are key.

I would recommend this one to all our dev team. While a bit long in the the tooth (1:20) clearly is an enabler for all your work. Here are the rough notes.

Quote:
Agenda
………….○ DataStore
………….○ Content Management
………….○ APIs
………….○ Pages / User Intfcs
………….○ Provisioning
• Developer Map (PDF) http://msdn.microsoft.com/office/server/moss/
• 5:00 – Site Model
………….○ SPFarm
………….○ SPWEbApplications
……………………..§ SPSIte
…………………………………□ SPList
…………………………………………….¨ SPListItem
…………………………………□ SPFolders
…………………………………………….¨ SPFile
………….○ Forms a security boundry (SPsite)
………….○ Limited to 1 DB
• 10:30 – Can move sites around SPWebs around (list views to sub spwebs)
• 12:00 – Sample Hierarchy
………….○ SPWeb
……………………..§ SPWeb – Portal
……………………..§ SPWeb – Blog
……………………..§ SPWeb – TeamSite
…………………………………□ SPWeb – TeamSite
………….○ Again the key of SPSites being the physical delimiter (can’t move across boxes or share.. So plan accordingly)
• 16:00 – Infrastructure Improvements
………….○ Old – Can hit Sharepoint via WebDAV
………….○ Two Stage Recycle
………….○ Folders in Lists
………….○ Cross List Query
………….○ Folders in Lists gives you the meta on documents. In WSS 3.0. Integrate lists and doc libs. For example discussion boards posts are folders and replies are items in the folders. Provides performance gains.
………….○ Cross List. The single index on SPWeb. Also can index specific columns on a list field.
• 19:00 – Lists and Librarires
………….○ New features in 3.0 –
……………………..§ Append only (cant change … only append comments)
……………………..§ Multi – value lookups
……………………..§ Custom field types
………….○ So this is infra supporting models earlier provided that didn’t work. A central list store that is shared out in various areas. Meta on columns on the field. ECM lite.
………….○ Can have fields in one list lookup values in another list (tie em together)
• 25:00 – Security
………….○ Cross site groups
………….○ List level security
………….○ Web level security
………….○ New in 3.0
……………………..§ Item level security
……………………..§ Web application policy
……………………..§ Permission levels (site groups are deprecated)
……………………..§ ASP.NET authentication
• 27:00 – Demo WSS 3.0
………….○ Key template sites basically make Sharepoint a framework generation (w/ hosted enterprise backing) for key functions of apps … ecm, forums, wiki, blogs, shared tables, content, etc.
………….○ Shows forms. Can be customized. Get em default. Shows how one form can pick valid values and data from another list.
• 35:00 – Content Management in WSS 3.0
………….○ Workflow (WWF)
………….○ Forms (use ASPX for forms)
……………………..§ Via Infopath you can work w/ forms in word or excel
………….○ Use VS or SP Designer to design workflows
• 37:00 – Libraries
………….○ Check in / Check Out (enhanced)
……………………..§ Required check out an option now
………….○ Required properties (blocks upload )
………….○ Versioning
……………………..§ Major / Minor versions
……………………..§ Allow readers to see up to one level while the same doc place can have versions beyond that for authors to work
……………………..§ Trimming allowed (only track X versiosn)
……………………..§ Available on lists
………….○ Schema Management
……………………..§ So another issue resolved (global ECM model). Schema Management. Change in one place and push down.
……………………..§ Content type (enforces a well known meta structure as a base for that content type).
…………………………………□ Assoc behaviors (events, templates, workflows)
…………………………………□ Multiple content types per list
……………………..§ Column templates (centralized field management)
………….○ Object Model and Web Services
……………………..§ Sharepoint List
……………………..§ New
…………………………………□ Property Bags
…………………………………□ Impersonation and Elevation
…………………………………□ System updates
…………………………………□ SPContext (use this in WebPages)
…………………………………□ SPUtility
…………………………………□ Extensible admin objects
………….○ 46:00 Events
……………………..§ Post Asynch Events for Libraries
…………………………………□ Events at item level
…………………………………□ (much more power here)
………….○ 50:00 – APS.NET integration w/ WSS
……………………..§ Better than 2.0 (integrates more directly)
……………………..§ Pages
…………………………………□ Master Page Arch
…………………………………………….¨ One page that can be overriden by the child pages
…………………………………□ Stored in file system and DB
……………………..§ Master Page Tokens
…………………………………□ Two Dynamic Tokens
…………………………………………….¨ So you change on page and they all pick it up
…………………………………□ Two Static Tokens
………….○ 54:00 – Web Parts
……………………..§ New in v3 — UI for Webparts
……………………..§ ASPX allows usage of user controls (which doesn’t work in WSS v3).
………….○ 58:00 – Provisioning
……………………..§ Site Definition (defines site). XML.
……………………..§ Site Templates (defines templates).
……………………..§ In v3
…………………………………□ Refactored to concept of ‘features’ … single component of doc libs for example. As build site definition all sites pull from the master (versus being embedded into each)
………….○ 1:00 – Solution Deployment
……………………..§ CAB up and hand to admin
………….○ 1:01 – Demo – User Interface Lightup
……………………..§ Define a number of custom actions
……………………..§ Bring custom features to sharepoint directory … then you need to register them ..
……………………..§ Activate feature in specfic feature
……………………..§ (all batch commands)
………….○ 1:05 – Summary of what was covered
………….○ 1:06 – Q&A
……………………..§ More info on other products like CRM?
…………………………………□ Part of functionality … so not really something you need to worry about unless you are using it.
……………………..§ Does SP 2007 replace CMS?
…………………………………□ Now there is wss3.0 and sp 2007. So yes sp2007 does replace cms.
……………………..§ Example of ASP.NET auth in SP?
…………………………………□ No great example. Google shows some random non-MSFT MVPs.
……………………..§ Wiki is a site w/ a doc lib?
…………………………………□ Yes, you can inside teamsite create a wiki site. Better default nav that way. Or use as a lib.
……………………..§ WSS 3.0 works on?
…………………………………□ SQL Server. No files.
……………………..§ WWF has to be installed for WSS 3.0 to work?
…………………………………□ Yes
……………………..§ Does schema management affect the document? Ie a priority field in the doc?
…………………………………□ Yes from the document to the list … works … then if it changes in the list … it will change the word doc. Impressive.
……………………..§ 1:19 – Ghosting?
…………………………………□ Yes still exists. Rather use master pages.
……………………..§ Good site for complex sites examples?
…………………………………□ Look @ SP SDK
……………………..§ Go live license for WSS 3.0?
…………………………………□ Not right now
……………………..§ Need windows 2003 for development.

July 18, 2006 Posted by | Uncategorized | , | Leave a comment

MSFT: UX via Expression

I noticed an early webcast on the Expression line coming out of MSFT in 2007. For those not aware it is a set of 3 products they are positioning to enable Designers and Developers to finally work in the same toolset and base framework (XAML, etc) … versus seperate ones today (ie Photoshop and VS 2005).

After watching it … i would say its only for the die hards of UX since it was rather mundane … but quick in 1.4 speed (20 minutes). It was so mundane I don’t really have notables about it. Imagine that. My raw notes are below.

Keep in mind, we need to track this (and other tools like it) in order to continue to build our UX message. We are in the right position at this time (UX compentency building in advance of notable marketing coming from MSFT on that front w/ the Vista and 2007 set release). What we need to hone is the compelling reason to bring in support by our clients. Championing this tool line might be one.

Quote:
• Jon Byrum – Expression Product Mgr (7/14/06(
• Agenda
……………○ UX
……………○ .NET 3.0 – WPF
……………○ Dev / Designer collab via xaml
• 1:30 – Example of UX
• 4:30 – Discussions of richest experience for UX via applications that leverage the client (not just browser)
• 5:45 – .NET 3.0 (basis of UX)
……………○ WPF <– Key
……………○ WWF
……………○ Info Card (card space)
……………○ WCF – web services
• 7:00 – XPF Details
• 8:00 – Examples
……………○ MSFT MAX (WPF Example)
……………○ Health care demo (live monitors, overlayed)
…………………………§ Drag drop charts to aggregate charts
……………○ Northface prototype (kiosk)
…………………………§ Video to product swapping (contextual usage sales & click through)
• 13:00 – UX and Coder Collaboration
……………○ XAML allows both users (ui designer and dev) to be in same tool
……………○ Mock up UI rough (dev) pass to UI team (in XAML)
• 16:00 – Tools
……………○ Graphic Designer
…………………………§ Allow vector and bit net graphics
…………………………§ Allow to add dynamic effect on selection for example
……………○ Interactive Designer
…………………………§ Talk again in 2 wks (28th) with demos
……………○ Web Designer
…………………………§ Cascading style sheets
…………………………§ Supports ASP.NET tools
…………………………§ No connectivity to DB
…………………………§ XML support (so could pull real data)
• 22:00 – Next Steps
……………○ CTP – Comm Tech Preview
……………○ Review Vista, Expression, .NET 3.0, Max Photo sites
• 24:00 – Questions

July 16, 2006 Posted by | Uncategorized | , , | Leave a comment

MSFT: SP/MOSS – Advanced Search

Watched this webcast this morning.

Advanced Search in MOSS 2007 — Bill English MVP, MSCE, MCT MindShare


I was just looking for background noise but this one turned out to be quite intriguing. Here are some key thoughts.

    1. Value in Knowledge Aggregation I wouldn’t have put together the value of a singular aggregator embedded in the framework for collaboration till I watched this. Consider our Communities of practice. Would love to be able to embed into a give team site (say Project Services) an aggregated search index for ALL sources known to the big guy (intranet, extranet, web, ERP, etc). One stop shop for knowledge. Definite value message to clients … stop surfing the web for tidbits … have it be crawled for you.

    2. No MOSS on this Stone. Sharepoint 2003 search was weak … due to indexes by site w/ no cross index relevance. Listening to the improvements this guy rattled off (including one index for all — so relevance will work) made me raise my eyebrow. I think they have really improved thier product here (still has gaps … but doesn’t everyone?)

    3. Clarity of Why Help is Needing Setting Up MOSS? It was an interesting point by the speaker. If you deploy a search solution and it doesn’t work well to start … users will stop using it. MOSS can work well if you THINK about it awhile (model how your users will be searching, etc). Clients risk spending a ton of money rolling out content aggregators but not having a solid search design on top of it … and getting no ROI from the investment. We need to help them understand the complexity of setting up search CORRECTLY and play from there.


As always, here are my detail notes. I actually didn’t get to the end of this one (doh!) I suspect he kept going to around 1:20. I included a screen shot of search differences (2003 to MOSS).

Search Features in Sharepoint

Quote:
• Bill English MVP, MSCE, MCT MindShare
• Tech Ed (live in Boston)
• Mindsharp

• 2:00 – MOSS / SP 2007
………….○ 50% MOSS
………….○ 50% wss v3
• 4:00 – Search Strat
………….○ Content on desktop / fileservers (unstructured)
………….○ ERP content (Structured)
………….○ Desktop, Team, Division, Enterprise, Extranet, Internet
………….○ In short, crawl structured/unstructured data at any of these levels.
• 7:00 – Search Consistent
………….○ New core search engine is in WSS
………….○ Install MOSS on Top of WSS … add functions for enterprise
………….○ Majority investment in relevance / ranking (#1 customer issue due to multiple index files so no cross ranking across files). Create one index
• 10:00 – New Search Concepts
………….○ Click distance. Lower in result set if authoritative site resource is multiple clicks away. For example MySite (far away), Portal home (good).
……………………..§ Need to edit (in admin) the relevance sites (top, 2nd, 3rd are the groups)
………….○ Anchor Text. URL hyperlink text (on hover) will be indexed.
………….○ URL Depth. Higher in hierarchy rates higher.
………….○ URL Matches. Query matches words in URL name.
………….○ Metadata. Extracts from docs titles / authors .. 1st slide is title author on 1st slide. Not talking about meta fields (it derives it). By file type look in certain locations of file.
………….○ File Type Bias. PPT is more relevant.
………….○ Text. Typical full text.
• 20:00 – Other improvements
………….○ Hit highlights
………….○ Search center
………….○ Duplicate collapse
………….○ Did you mean (google)
………….○ Alerts (result set changes … only once a day or week)
……………………..§ Immediate wasn’t really happening in 2003 (depends on how often you crawled)
• 22:30 – Indexing
………….○ Choose what to crawl, rules, log
………….○ One index per SSP (Shared Svcs Provider). It is a ‘farm service’.
………….○ SSP design is key. One index per SSP.
………….○ Multiple start addresses per content source … so you can crawl segments of a source. Don’t need to create multiple content sources (ie 2003 way).
……………………..§ So you could crawl all the SP blogs on the web under one content source
………….○ Search scopes are from managed properties. In 2003 URN. So you can roll up same ‘content’ fields but separate fields and search it as one field (so multiple system definitions of ‘author’).
• 29:46 – Crawl Process
………….○ Load (protocol, index, site path rules, crawl settings, site hit freq).
………….○ Connect
………….○ Stream meta, content (pass to plug ins – indexer, archival plug in (schema plugin)). No more persistent query service. No category assisstant / topic assistant.
………….○ Meta in sql (not sps.edb)
• 32:20 – Arch Updates
………….○ Alerts daily
………….○ Shadow indexes (resolves network down issues) … continuous propagated to query server (chunking) … scheduling w/ 200-300 content sources is resolved (problems in 2003 at least). More available … quicker to end user (chunking). Query server in MOSS>
• 36:00 – Demo – Creating a Content Source
………….○ Types (sharepoint servers)
………….○ Web sites
………….○ File shares
………….○ Exchange public folders
………….○ Business Data (BDC searching of ERP)
………….○ Q&A
……………………..§ Unique security for above done by site path rule
……………………..§ File extension defaults 2003 and above (pdf filter, and others are still 3rd party)
……………………..§ 2003/2001 .. Add on for notes … in 2007. Don’t know if can crawl in 2007. Assume can via BDC.
………….○ Add site path rule
……………………..§ Hit page but only index below
……………………..§ Crawl complex pages (ie ones w/ question marks).
……………………..§ Sp as http
……………………..§ Add account pw (https certificate)
………….○ Search center
……………………..§ Pick site(s)
……………………..§ Get folder and doc
……………………..§ To customize page (search results).. Can edit page now
……………………..§ Flag ignoring of buss words (like G&R)
……………………..§ Stemming was always on … in 2003 ” was indicating proximity (so you can’t look for exact phrases still)
……………………..§ Q&A
…………………………………□ Will it crawl SP Service? Hit top but wouldn’t go lower in 2003. Not sure in 2007.
…………………………………□ Customize Search Interface? Yes. Just like results page.
• 58:00 – Broader Content Aggregation
………….○ Blogs
………….○ Wiki’s
………….○ ERP systems
………….○ Colleagues and Partners (people search)
……………………..§ Search people and their expertise
……………………..§ Reporting structure
……………………..§ Teams in past
……………………..§ Teams now
……………………..§ Who knows who
……………………..§ External contacts
……………………..§ Connections
• 1:03 – Shared Search Services
………….○ Indexing is resource intensive.
………….○ Avoid redundant
………….○ Always on
………….○ Control central, managed by consumer
………….○ Users can define search scope. Tied to content source. You can search pieces of the index. Scope by any meta data you want (authoer, project, customer, etc)
………….○ 1st impression of search is key [deployment point, weave into discussions w/ clients] … if it isn’t good the 1st or 2nd time they will leave or stop trying … [push UX]
• 1:09 – Demo Create Scope
………….○ Show how fields map to one field (for singular search)
• 1:12 – Query Reporting
………….○ See what people are looking for

June 27, 2006 Posted by | Uncategorized | , , | Leave a comment

MSFT: WWF Overview

Watched this webcast today

Intro to WWF


Not so much as it was new material but I was curious on if the message had matured since earlier (intro to WWF webcasts). It had a bit. The keys I took away were

    1. Good Overview Slides. Had two good overview slides that I captured for you (see below). One on Biztalk vs WWF. The other on base execution view.

    2. Domain Specific Activities. Its interesting that the Domain Specific Activities might be a way to seperate ourselves from the pack. For example, our investment in Patient Intelligence Registry (BI Play) will have Domain specific workflows (or could). Nice way to extend that play (as we are right now trying to build a Sharepoint front end based on Business Data Catalogue).

    3. State. It’s interesting that this time around I began to think our messaging should be around state. Sequential is in there (granted). But state can be the forest business layer that triggers sequential flows when appropriate.


Detail notes are below:

Quote:
Gerald Walsh. Developer Evangelist.
Introduction to WWF (100)
…………..○ 1:30 – Agenda
……………………….§ Intro
……………………….§ Integration
……………………….§ Workflow basics
……………………….§ Building a workflow
……………………….§ Activities
……………………….§ Execution and Control Flow
……………………….§ Workflow design tools
……………………….§ Integration w/ Office
……………………….§ Summary
……………………….§ Resources
…………..○ What is a workflow? Activities to coordinate people and/or software.
…………..○ Two categories
……………………….§ Flow chart
……………………….§ State diagram (less transactional, more human)
…………..○ 4:30 Challenges
……………………….§ Long running & Stateful
……………………….§ Flexible control flow
……………………….§ Transparency
…………..○ Release
……………………….§ Beta 2.2
……………………………………□ WinFX dropped
……………………………………□ Launced in .NET 3.0 (put in WCF, WWF, WPF, etc)
…………..○ BizTalk vs WWF
……………………….§ BizTalk superset of WWF
……………………………………□
…………..○ 10:30 – WWF
……………………….§ Compiled DLL (reside in host process)
……………………….§ Workflow, Activity Library, Workflow Runtime Engine, Runtime Services (state mgmt, persistance, tracking, timer svcs, transaction svcs, intfc for custom run time svcs)
……………………….§ Interfaces to work on workflow
……………………………………□ Sharepoint Designer (Frontpage next release)
……………………………………□ VS 2005 plug in
…………..○ 15:00 – 2 ways to define
……………………….§ Code
……………………….§ Markup (XML). Nice (enables the external app definition of a workflow)
…………..○ 17:00 – Demo
……………………….§ 17:30 – 2 types of projects
……………………………………□ Console (prog file to allow run in console file)
……………………………………□ Workflow library (where you have a host)
……………………….§ Review of Activities that could be done in workflow (part of VS2005)
……………………….§ 25:30 – End demo (shows console firing up, msg, and closing)
…………..○ 26:00 – Authoring Modes
……………………….§ XAML only
……………………….§ XAML and Code
……………………….§ Code Only
……………………….§ Application Generated
…………..○ 28:00 – Activities Basics
……………………….§ Activities Building Blocks of Workflows
……………………….§ Activities are Classes
……………………………………□ Base
……………………………………□ Custom Activities
………………………………………………..¨ Compose Activities (aggregate)
………………………………………………..¨ Extend
………………………………………………..¨ Author New
……………………………………□ Domain Specific Workflow Packages
………………………………………………..¨ Opp for GR/FC?
…………..○ 33:30 – Workflow Execution
……………………….§
……………………….§ 35:30 – Dehydrate / Rehydrate the workflow (where the workflow is saved to disk after inactivity)
…………..○ 37:00 – Flexible Control Flow
……………………….§ Sequential (flowchart)
……………………….§ State Machine
……………………………………□ setup external comm
……………………………………□ Event drive (host is beefier)
……………………….§ Rules Driven
……………………………………□ Complex policies
……………………………………□ CAG (Constrained Activity Group) is key foundation
…………..○ 39:00 – State Demo
……………………….§ 43:30 – Bumbling around.
……………………….§ Couldn’t link the states (in GUI) … DOH!
…………..○ 45:00 – Taking Workflow Mainstream
……………………….§ Design – VS 2005
……………………………………□ Sequential Designer
……………………….□ State Machine Designer
……………………………………□ Activity Designer
……………………….§ Office
……………………………………□ Sharepoint Server manages workflow typically (outlook can be a client using VB tools for office)
……………………………………□ Example, invoice in word, save to sharepoint, trigger workflow, etc
……………………………………□ Sharepoint Designer allows non-tech to design workflows (employee tracking, invoice tracking, etc)
…………..○ 53:00 – Q&A
……………………….§ Remoting
……………………….§ Nothing else notable

June 26, 2006 Posted by | Uncategorized | , | Leave a comment

MSFT: MOSS – WCM

Watched this webcast

Preparing for Web Content Management w/ Microsoft Office Sharepoint Server 2007

today based on (1) the set of our annuity accounts that are currently on CMS 2002 and (2) the rumor that certain clients are migrating from tier1 ECM products (like Documentum) to the o2007 Microsoft Office Sharepoint Server (MOSS) suite.

So here is what i took away:

    1. Solid Marketing vs ECM Space. Good slides and discussion (at a high level) on how the pieces of MOSS can provide not just WCM (focus of this presentation) but the macro view of ECM in ways. For example records management.
    2. WSS / WWF Based … AGAIN. Another product that is basing off the core of Windows Sharepoint Services and Windows Workflow foundation. It is clear that MSFT is standardizing on this infrastructure. If you aren’t grappling with what these features can do for you in an application framework — get on it.
    3. Sizzle No Steak? Interesting how they didn’t show the product (this was captured in March however). So at that time it was probably too unstable for demo. Has anyone looked at it (Ruska? Baldwin?) since then?

Anyway, here is my detail list:

    • Preparing for Web Content Management w/ Microsoft Office Sharepoint Server 2007

    • Manish Sharma – Sr. Product Mgr
    • Arpan Shah – Group Product Mgr

    • 1:44 Agenda
    …………….○ Evolution of WCM (cms2001, moss 2007)
    …………….○ Features in MOSS
    …………….○ New capabilities
    …………….○ Migration cms 2002 to MOSS
    • 2:00 Evolution
    …………….○ CMS 2001
    …………….○ CMS 2002
    …………….○ MOSS 2007
    • 3:30 Overview of MOSS 2007
    …………….○ Collab
    …………….○ Portal
    …………….○ Search
    …………….○ Content Management
    …………….○ Business Processes
    …………….○ Business Intelligence
    • 7:00 ECM
    …………….○ User Intfc : office, Web, 3rd party
    …………….○ ECM: Doc Mgmt, WCM, Records Management, Forms Mgmt
    …………….○ Svcs: Workflow, Meta, Policies, Library Svcs, Search, security, IRM, Collab
    …………….○ Unified Storage: WSS + SQL Server
    …………….○ [bauer comment – 1st time I have seen a ECM vision slide from MSFT, similar to Documentum and Stellent angles (at least in marketing points)]
    • 10:00 – Author web content
    …………….○ Talks to RM impacting (being available)
    …………….○ WSIWYG editor (new)
    • 11:45 – In Place Authoring Editing
    …………….○ Author content with WSIWYG editor
    …………….○ Spell check /tables
    …………….○ Server side conversions (word to web page leveraging master page of site)
    • 13:00 – Publish
    …………….○ Templates – separate content and presentation
    • 17:00 – Deploy and Manage
    • 18:00 – Present content to Web Users
    …………….○ High scale / performance
    • 20:00 – Benefits
    …………….○ Lower mgmt costs multi site / multi lang
    …………….○ Business Driven content
    • 20:30 – Liscensing Models
    …………….○ Server / Cal (intranet models)
    …………….○ Per Server (internet sites)
    • 22:30 – Q&A
    …………….○ Migration
    …………….○ Availability – End 2006
    …………….○ Public Beta – End of 6/30
    …………….○ SQL Server 2005 Supported
    • 23:30 – Key Arch Points (CMS and MOSS)
    …………….○ No client footprint this time
    …………….○ Editing – Users can add webparts and content (applications)
    …………….○ Sharepoint Designer = Next Version of FrontPage
    …………….○ Page Layouts = Templates
    …………….○ WSS based = for example web content in WSS lists so you get page lock down, recycle bin, RSS feeds on page, workflow on pages, etc … all via WSS .. Also auth provider model works (could write a app provider in asp .net 2.0).
    …………….○ Built on WWF. O2007 features. Configurable workflow templates. Serial, parallel, events, create workflows (via designer, or vs2005).
    • 30:00 – Coexistance
    …………….○ Can run in parallel (CMS and SP 2007)
    …………….○ CMS – content, cms files (templates, etc), config
    …………………………..§ Will have tools to move content
    …………………………..§ Incremental or big bang content movements
    …………………………..§ Templates – Get a blank template for every CMS templates (will generate). Won’t move code behinds. Manual apply code, styles (css files could port).
    …………….○ Custom Code
    …………………………..§ Search (Out of Box – OOB)
    …………………………..§ Nav – OOB (plus Whidbey provider)
    …………………………..§ Summary Roll Up – OOB (listings, TOC, rollup)
    …………………………..§ Deploy Scripts – OOB
    …………………………..§ Form Login – OOB
    …………………………..§ Workflow – Better OOB
    …………………………..§ Console Customizations – OOB
    …………………………..§ Custom Placeholder Server Controls – Rewrite as WSS field control
    • 42:00 – Application Code Migration
    …………….○ Key point not 100% migration of customization on CMS
    • 43:00 – Best Practices
    …………….○ Get on SP2
    …………….○ Minimize Templates (less than 30 per site)
    …………….○ Get rid of going directly to the DB (use API’s and workarounds)
    …………….○ Don’t put login in pages
    …………….○ Leverage Whidbey provider models for navigation and forms (via SP2)
    …………………………..§ Enables cool OOB Whidbey Nav
    …………………………..§ Makes Nav and Form Login Simple
    • 48:00 – Migration Resources
    …………….○ Migration Whitepapers
    …………….○ Public Beta is avail on 7/5
    …………….○ Assessment Tool
    …………………………..§ Application that you run on a dev machine and it looks at CMS2002 … tells you what you need to look at (in a way)
    …………….○ Arch Guidance
    …………….○ Review Reusability and ECM Whitepaper
    …………………………..§ ECM – www.microsoft.com/office/preview/ecmwhitepaper.mspx
    …………………………..§ BETA – get that
    • 51:00 – QA
    …………….○ What is Whidbey? ASP .NET 2.0
    …………….○ Browser support better than CMS2002 (subscribers supports all models)
    …………….○ WSS v2 to v3 is an upgrade … beta2 will address. Reuse on WSS will also be addressed.
    …………….○ Blogs.msdn.com/arpans
    …………….○ Highly distributed? Can publish to multiple farms
    …………….○ Multi Lingual? O2007 on wss.v3 … can have different areas (called sites now) can have different languages. Page level translation is workflow. Control to switch to lang (in template)
    …………….○ CM2001 migration. Write ASP code to asp.net.
    …………….○ Offline. Take any stuff offline (groove, wss features, etc)

June 23, 2006 Posted by | Uncategorized | , , | Leave a comment