Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

Action items:

  1. Scott to send out a message on the ja-sig listserv re: ITANA SOA survey
  2. Piet to send out a reminder on the ITANA listserv
  3. Survey closes on Oct 15
  4. Piet and Leo will work on:
    1. Tabulating results
    2. An executive summary of the results
  5. Group to review Piet and Leo’s work on Oct 10 (we may want to book additional meetings in October)
  6. Deadline for f-2-f materials: Nov 6

Discussion around the results so far:
Rough notes…I’ve provably missed a lot of the detail, but there are some key insights/thoughts that Piet and Leo will be able to use in the write-ups.

Piet: the fundamental question: Is SOA alive and well.
Glen: alive and well based on the responses. Cloud is a big driver
Scott: what is called SOA is in the eye of the beholder. It may not even be called SOA: it may be called enterprise integration
Leo: it is about loose coupling and re-usability
Scott: SOA cannot be so general as loose coupling. But it is a fellow traveler
Rich: SOA may be dead but services are alive and well
Piet: thriving in terms of solutions but maybe not in terms of grand strategy
Glen: a balancing act. Some schools have walked away from high-level strategy
Leo: Enterprise SOA suites tend to be very complex and hard to implement.
Philip: Cornell has had a real struggle with the Oracle SOA suite. Really impressed by the Dell Boomi offering (www.boomi.com/) which seems a lot simpler. Cornell is using Oracle SOA suite for ERP and Cloud integration (Kuali Financials, Workday and multiple shadow systems)
Very difficult to get simple things done
Security is very complex
Leo: UofT may be having similar issues with IBM websphere
Scott: UC Irvine (also using Oracle SOA suite): the technology was the easy part. Business alignment was the difficult part.
Leo: similar issues around the complexity of standards
Scott: PESC useful for inter-institution communications. Sometimes these standards are useful internally, sometimes not. Common enterprise definitions would be helpful.