Tim Bauer’s Running Thoughts

Semi-daily webcast summaries/insights

JBoss & SOA

Watched this in that there is an ongoing market swell in all technology stacks around SOA, ESB, BPEL, etc. Go here:

LINK

or hit http://www.jboss.com/services/online_education and look for SOA Part II. That said this webcast is definitely worth watching for a variety of reasons.

1. Burr has clarity. Burr is thier evangelist on the technology stack and he does a great job pulling it all together (what it is, why to use it, how JBoss does it, etc). More so than other vendors I have seen speaking on the topic. So just for that you should watch (as many of us also don’t have clarity — i wont name names).
2. The Power of Open Source a BizTalk Competitor overnight? Later in the webcast they demo’d thier beta ESB product and its pretty robust. Will be available in q4 of this year. The key “AH HA!” was that thier code base came from an insurer that donated thier custom ESB to JBoss. DONATED. Welcome to the next generation of software. Companies build out complex CUSTOM frameworks and then lobby to get it adopted (for free) into the overall community champion (JBoss).
3. Nice BPEL Overview Alot of clients are starting to jawbone on BPEL. GE for example. Keep in mind that BPEL is, in short, a variant of what BizTalk does. Enables orchestrations etc. Rather impressive demostration of how that integrates w/ Eclipse (beta designer granted but BPEL spec isn’t formal to q4 - nov - anyway) with a similar look and feel to MSFT VS and/or BTS Designer. I was suprised with how close it was in look and feel.

In summary, it is clear that JBoss is moving faster than I thought possible. Powered by the contribution of the community and large code base donations I think they will make a strong run at maintaining thier hold on current clients from the MSFT push while stealing other clients from both camps (BEA/IBM, MSFT) for a Total Cost of Ownership play. Will be fun to watch over the next few years.

Here are my detail notes for those amused


Quote:
• Bruce Sutter - Tech Evangelist for JBOss
• Agenda
…………..○ Catalysts
…………..○ WS-*
…………..○ BPEL
…………..○ Service Bus
• 2:00 Catalysts
…………..○ Agility
…………..○ M&A
…………..○ Current Hundreds of technologies
…………..○ Users might be many roles
……………………….§ Data scattered across enterprise
……………………….§ EVPs Budgets create fragmentation
…………..○ Portals spawning (6 per BU, 10-12 Bus per org)
……………………….§ Customers want single point of entry
……………………….§ B2B, B2C, etc
…………..○ Swivel Chair Integration
……………………….§ Fax, Web, Call 4 Report, Web Service,
…………..○ JBoss SOA Engines
……………………….§ jBPM. Process driven. Human or batch
……………………….§ jBPM BPEL. Unique orchestration for web services (Have to have WSDLs). All communication to BPEL process is SOAP call. Invoke Ruby, etc.
……………………….§ Rules Engine. Production Rules Engine.
……………………….§ J2EE / Java EE 5 Services (JMS, EJB, WS, Hibernate JPA)
……………………….§ JBOss App Server (Swing, Browser, .NET, Batch, External)
• 11:30 - WS-*
…………..○
…………..○ Use JIRA to vote on functionality
…………..○ WS-Eventing.
…………..○ WS-Security.
……………………….§ Before, had a login process to get security token. Encryption via SSL (tying to HTTP transport). So if you go to ESB you might have segments that don’t support HTTP.
…………..○ WS-Addressing (JSR 261)
……………………….§ Before, endpoint was in HTTP Header. Take SOAP to server and goto post command parm at end. Problem multiple stopping points not easy (Service BUS enables this)
…………..○ WS-Policy.
…………..○ MTOM
…………..○ WS-Context. Maintain state conversations. Like a cookie.
…………..○ WS-Coordination. Business activity for long running compensating transactions.
…………..○ WS-AtomicTransaction. Two phase commit
• BPEL
…………..○ JBOSS resources on committee. November 2006 will get ratified.
…………..○ BPEL is part of jBPM. Beta 1.1
…………..○ BPEL fixes WSDL
……………………….§ Creates ordering.
……………………….§ Concurrency
……………………….§ Choreography w/ external entities
…………..○ XML, WSDL API to it, Can consume other WSDLs, allows for state, allows asynch of other web services (forking) and rejoin
…………..○ Key words -
…………..○ BPEL file overview - import, partnerlinks (anyone interacting with in/out), sequence tag — receive, assign, invoke, replay, flow, etc.
…………..○ 21:00 — DEMO - Eclipse - BPEL Designer (Alpha)
……………………….§ He will send you doco if asked to setup a basic model
……………………….§ Very similar look and feel to BTS (MSFT)
……………………….§ Task definition deploys par file to app server.
……………………….§ Example of a form doing BPEL (invoke a BPEL process). Add webservice to form. See WSDL file w/ BPEL process. Code is basically a call to the PROXY.
……………………….§ There are differences in BPEL spec and Designer (again he can send doc to cross chasm for now)
…………..○ 26:00 - JBoss ESB Beta 1
……………………….§ Came out just last week
……………………….§ Rosetta code base donated by a Large Insurance company. Running thousands of transactions. 3000 employees, 40 locations, 2 million customers.
……………………….§ Donation June 2006
……………………….§ Beta 3q 2006
……………………….§ First GA is 4th 2006
……………………….§ ESB - Listeners and Actions provide transport and message mediation
……………………………………□ Listeners - Some connectors - like file, http, ftp, jms, email, soap … are avail now. Seam in front of web/portal is also there
……………………………………□ Actions - Pluggable Arch — Transform, route, security, mgmt, JBoss ESB, Service Registry, Event Log, Composition Engine (BPEL, Seam, jPDL, Scripting, Process Store)
……………………….§ Out of Box - Listeners
……………………………………□ File
……………………………………□ SQL Table Poller
……………………………………□ JMS Queue topic listener
……………………………………□ Web Service Invoke to Bus
……………………………………□ Working on HTTP Listener (REST calls)
……………………………………□ FTP / SFTP (coming)
……………………….§ Core Services
……………………………………□ Service Registry
……………………………………□ Persistent Event Repository
……………………………………□ Notification Service - Msg queue to msg queue notification of a process
……………………….§ Messages
……………………………………□ Serializable Java Objects and/or XML
……………………………………□ Transformation declarative and java based
……………………….§ Usage
……………………………………□ NOW–File System -> JBoss ESB -> File System
………………………………………………..¨ FUTURE - add notifications, transformation
……………………………………□ Message Queue - MQ Cluster - MQ
………………………………………………..¨ Same as above
………………………………………………..¨ Registering in specific transaction events .. Listen for certain events … decoupled integration
……………………………………□ Combined Usage Example
………………………………………………..¨ Multiple listeners and multiple actions
………………………………………………..¨ FTP Poll, persist msg, log, email on rcpt, transform, post to file repository. Now you can do that in ESB.
……………………….§ 36:00 - Getting Started
……………………………………□
……………………………………□ Need latest version of EJB3.
……………………………………□ There is a a JEMS Installer (gui installer that installs EJB3)
……………………….§ 38:00 - Demo
……………………………………□ Config File (listener) review
……………………………………□ Show how ESB picks up files in momements, acts on it through ESB process, and spools out. In CMD window.
……………………………………□ Email example w/ notification. 4 lines in the config file of ESB listener to get it working.
……………………………………□ Notification to JMS. Same config file for listener. Different config lines (4) to push to JMS Queue. JMX console shows the messages going through. Then you could have a bean or process respond to that message.
……………………………………□ Multiple steps in same listener (hard code or via GUI in Eclipse). File listener sends alert to queue. The listener on that queue. Show how they bat the message back and forth between the listeners and the associated code behind the listener.
……………………….§ 47:00 - Trail Blazer Demo
……………………………………□ Advanced demo of capability
……………………………………□ Customer interact w/ web or vb that hits services that hits ESB gets persisted then gets managed from there in ESB. Multiple listeners act on the single message (partner network model)

August 21, 2006 Posted by bauertim | Uncategorized | , | No Comments

Methodology Players - Serena

MSFT did a webcast on Serena last week.

WEBCAST

They seem to be a product (~300M in sales I guess) focused on requirements mgmt, change mgmt, config mgmt. They have integrated to some degree w/ VSTS as we seem to be planning to do w/ our upcoming release of Macroscope. The only keys I took away were:

1. Competitor to Macroscope? Interesting niche player for sure just on the requirements and conceptual design phase. What I am curious about is how much our next release of macroscope can do the core features they are strutting. I believe there is quite a bit of overlap. Macroscope seems to be more integrated with MSFT (doing forms based on infopath and synch requirements to VSTS that way) while they have a proprietary tool to model from. Their tool is more visual than Fujitsu’s (you can tag requirements to a visual wireframe and then synch that to VSTS) but I am not sure how much that buys you (some granted).
2. No validation of cost of lost requirements So the integration of VSTS to a requirements doc (be it theirs or stone tablets) is really about loss of detail in handoff. Thats the big ROI anyway however they didn’t have stats on that. They had stats on how it takes 8 times longer to fix something coded. However there are many ways to get more detail out earlier in requirements (UX, Agile, etc). So more proof in the pudding please.

Here are my detail notes for those amused.


Quote:
• Serena - Partner
• Global ISV - Partner Manager (Peter Koen). Talks to how they are cooperating.
• Extend VSTS for Requirements
• 2:00 - VSTS Overview
• 3:00 - Serena - 300M company
…………..○ Team Track
…………..○ CVS
• Review Serena Composer, RTM (requirements tracking)
• Change impacts
…………..○ Application
…………..○ Operations
• Collaboration is Key
• Composer offers a visual collaboration
• 8 times to fix something versus getting it right during the requirements process
• 7:30 - Serena RTM
…………..○ Automate requirements lifecycle
…………..○ Track
…………..○ Word based to a central repository
• 9:10 - Composer - Visualization of Process flows
…………..○ Simulate events.
…………..○ Show interactive aspects
• 11:00 - Integrated Requirements Lifecycle
…………..○ Store req in RTM
…………..○ Use Composer to do conceptual designs
…………..○ Agile or Iterative or Waterfall
• 13:00 - Composer
…………..○ Appl Plan
…………..○ Business Model
…………..○ Prototype
…………..○ Visualize Requirements
…………..○ Doc Pub
• 14:00 - Demo
…………..○ Designed targetting MSFT Office Tool
…………..○ Objects you can model (1 editor per)
……………………….§ Models are created in context of projects …
……………………….§ Processes
……………………….§ Interfaces
……………………….§ Decisions Rules
……………………….§ Action
……………………….§ Data
…………..○ Swim lanes by role
…………..○ More ‘business focused’ widget for the flow
…………..○ 21:00 - Activities defined by drag drop (decision, communicate, connect, calc, return to, activity, etc)
…………..○ [how is this different than BTS?]
…………..○ Modular (so processes can be embedded in processes)
…………..○ Use Wireframes (capture from webpages or start from scratch)
…………..○ [demo issues - 2min - cant show edit of wireframes]
…………..○ 26:00 - Two Modes of Review
……………………….§ Run (prototype)
……………………….§ Assimilate (walk through process)
…………..○ Everything modelled in their tool (controls, text, etc)
…………..○ Shows options
…………..○ Back to composer … when in UI .. [hrm not too excited yet]
…………..○ VSTS Integration (4)
……………………….§ Scenario
……………………….§ Business Model (swin lanes)
……………………….§ Requirements (detail, smmry)
……………………….§ Documents (word). Store and review in VSTS.
…………..○ Ongoing Synch is possible as well. Publish requirements from this Screen to VSTS.
…………..○ 34:00 - Publish demo w/ example of versioning control. Document why requirements are changing here.
…………..○ [bauer-a lot of the control is in VSTS on versioning so the key question is how to integrate business requirements to dev team (xls link??)]
…………..○ (bauer — doh, using VMWare … comment … nice partnering)
…………..○ Shows how docs from serena get into VSTS
…………..○ End of Demo
• 42:00 - Benefits
…………..○ Easier to visualize / prototype
…………..○ High quality less rework
…………..○ (bauer = key question is how many requirements are missed due to handoff … cause this is where this product hangs)
• 44:00 - Q&A
…………..○ Winforms? Not supported. Webforms for now.
…………..○ How to contact serena?
…………..○ Composer - Serena Reviewer. Allows creation of models, proto, docs … allow them to review them and comment and provide feedback. Collaborative (no liscense required) (bauer - basically they export to word)
…………..○ Models only? No you can do via forms. Functional specs can be stored via RTM (tied to wireframe basically)
…………..○ MSFT? Serena how does it position vs WWF? Working to integration of WF to their product (is the answer). However didn’t talk about how WF or BTS can do a % of what was shown. Interesting. Same for Macroscope I guess.

August 19, 2006 Posted by bauertim | Uncategorized | | No Comments

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 bauertim | Uncategorized | , | No Comments

JBOSS & ECM - Anyone Home?

watched this webcast this morning as I was curious how JBOSS was addressing ECM given they really don’t have a ECM product.

LINK

Some keys I took away:

    1. Marketing similar to MSFT They wouldn’t want to admit it but they are going to market similar to MSFT. They own the core infrastructure and then expect vendor partners to build solutions on top of it to address client needs. Alfresco (the vendor talking with them) did just that … building a first version of a ECM suite on top of JBOSS infrastructure.
    2. Alfresco a mini-me Sharepoint? It was interesting to watch the demo (the first 30 minutes was thier spin on the portal market — which i skipped) in that i could see ’some’ of the sharepoint functions at play. The real question (as with all client decisions on investment) is what capabilities do they need from thier, in this case, WCM framework and where there are gaps in needed capabilities from different approaches how much does it cost to close them. This may or may not lead to Alfresco on JBOSS being the right model. Was intriguing though. Did I mention it is free as well $-).
    3. “Support from the Source” Interesting tagline that RedHAT and Alfresco are pushing.

Here are the detail notes for those amused.


• Industry Issues Webinar on Portals
• Alfresco is the partnering vendor
• Overview
………….○ JBOSS
……………………..§ Support from the source
………….○ Alfresco
……………………..§ First opensource cms
……………………..§ Model documentum, filenet
……………………..§ Founded documentum
…………………………………□ Has documentums team now for sdks
…………………………………□ Has interwovens wcm team
• 5:00 - Portal definition
• 8:50 - What is knowledge mgmt
• 34:00 - Demo of Integration of JBOSS portal w/ Alfresco portlets in Jboss
………….○ Team, news, doc library, discussions
………….○ Show 1 portlet jboss wise
………….○ Show editing of static content w/ an ordered approval process
……………………..§ Version control and detail
………….○ Have virtual directory functionality (so explorer view for users)
………….○ Rules are available on drop
……………………..§ Document properties extracted to ecm product
……………………..§ Pdf version created automatically
……………………..§ Mail (via thunderbird)
………….○ RSS feeds that communicates new information in the portal
………….○ Ability to search for a person by skill (not shown how) .. Similar to people finder in MSFT
………….○ Templates (smartplaces) .. That has a similar UI, files, process, auditing etc (ala sharepoint)
………….○ [bauer - key question pricing vs SP for Alfresco, otherwise they are short]
………….○ Concept of ’spaces’ … which is your doc repositories that hoave all the doc versioning / library functions.
………….○ Shows creating a rule in space
……………………..§ Workflow, meta extract, transform, set aspects (like templateabe, versionable, translateable,etc), move to specific space, etc
• 49:00 - Demo done .. Jabber
………….○ Develop rules, aspects, actions are possible in their framework
………….○ Rhino JavaScript engine included
………….○ Really enables record management
……………………..§ For example just a few scripts are required for DOD compliance w/ Records Management
• 50:00 - Q&A
………….○ How compare to other OS CMS? Like OpenCMS …
……………………..§ want to address WCM space but more importantly hit ECM (like RM, and DCM, Image Mgmt, etc). 20% of market is WCM. That is why they hired interwoven for WCM and DCM team for other areas.
………….○ Wiki?
……………………..§ Later this year releasing a WIKI interface. Open up arch later as well to PHP to allow the strong WIKI solutions based on PHP in as well
………….○ Portlets created / embedded?
……………………..§ What was demo’d was out of box
……………………..§ Free market templating lang creates team spaces that pull from the vanilla product
……………………..§ High end solutions can have specialized portlets but using “FreeMarker” since it can process XML and access Java object model in alfresco (talk to and get document properties).
……………………..§ Look in data dictionary. Look at presentation templates. 10-12 lines in .. Iterations, xpath, etc can be done.
……………………..§ Very similar to SEAM (using that as part of the workflow). Get container data. Iterate a documents children (folder, associated docs) and wrap w/ HTML
……………………..
………….○ Smart Folders. Navigation on meta not fixed diretory
……………………..§ In 1.4 release next coupole of months (q4 minimum)
………….○ Cost of product
……………………..§ OpenSource (Free). Going for services contract.
……………………..§ Support is $10k per CPU
………….○ “Support from the Source” team
………….○ When will doc libs and such be their own portlet?
…………………….. (1.4 version in q4)
……………………..§ John.newton@elfresco.org

August 3, 2006 Posted by bauertim | Uncategorized | , | No Comments

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 bauertim | Uncategorized | , , , | No Comments