Site Visits
Home Page IC SOA - Click Arrow to Expand
Home Page | All Pages | Authors
Welcome to the IC SOA
A Global Community of Practice among like minded peers.
Collaborating closely with end-users, leading standards organizations, industry associations, vendors, academia, and business and technology consultancies - this initiative harvests best practices, demonstrates the SOA value proposition, and raises the level of professionalism across both Business and IT teams.
The IC SOA is a global community of practice comprised of senior IT leaders dedicated to the ideals of Service Oriented Architecture (SOA) as the prevalent IT-model for transforming business and improving IT practices. The IC SOA explores the value of SOA by sharing and delivering real world experiences
Webinar: Mainframe SOA Roundtable:
Best Practices and Real-Life Experience from The Trenches
DOWNLOAD NOW!
SOA’s are all the rage – but what about your mainframe? Including the mainframe in your SOA strategy may or may not be in your plans, but one thing is certain: if you have critical applications and data on this time-tested platform, there is much to be gained by planning for seamless integration with the rest of your architecture.
Like most large banks, SunTrust relies on their IBM mainframe system for many of their applications and core banking systems. By applying service-oriented techniques, with their proven systems, SunTrust is delivering new, advanced applications, using the mainframe as the cornerstone.
Join us for a roundtable discussion on success strategies and best practices for Mainframe SOA featuring:
Glenn Schneck, SunTrust &
Steve Craggs, IC European Chairman
.jpg)
Previous Calls:
September 26, 2007
Topic: EDA Part II - Gaining Support From the Business
Presenters: Dr. Ronan Bradley & Steve Craggs, Lustratus Research
Moderated by: Rob Morris, GT Software
As we experienced on our last call, EDA (Event Driven Architecture) is a topic that certainly provides a foundation for a great technical dialog. But as we all know, we will all have to “sell” the value of this new / additional architectural approach to the business. Many of us still struggle with explaining the benefits of SOA, adding EDA to the mix will not be easy. This call will be led by Ronan Bradley and Steve Craggs from Lustratus Research and will offer conversation provoking ideas so we discuss how, when, and why to sell the merits of EDA to the business.
Topic: EDA
EDA (Event Driven Architecture) is a hot topic again - unfortunately the discussion often revolves around whether EDA is superset, subset or alternative to SOA rather than how EDA can augment SOA. To discuss this topic sensibly, first it is essential to define the different meanings of EDA - as there are multiple definitions - and how these different definitions of EDA fit with SOA. At least three can be identified: EDA as an implementation technology used within SOA; EDA as an approach to application integration and EDA - and more particularly Complex Event Processing - as a way of analysing and controlling the flows of information in a SOA deployment. The last (using CEP and EDA within a SOA analysis/control layer) provides a platform upon which to build a new generation of Business Activity Monitoring (BAM) capable of dealing with the potential greatly increased complexity within SOA. However, questions remain: Can an EDA-based BAM deliver sufficient value to justify wide adoption and when will this type of functionality be needed in SOA deployments (if ever)? And more generally, what are the patterns of EDA use that make sense within the SOA context?
June 27, 2007
Topic: REST vs SOA
We will continue the dialog concerning REST at this call. Santhosh Kumeran from IBM's T.J. Watson Research Center will review the design of a RESTful solution for the Sample Decisioning Scenario that is somewhat different from those presented in earlier calls.
June 8, 2007
Topic: REST vs SOA
The recent IC SOA conference calls on REST has application in the real world from the perspective that REST is a resource-oriented architecture style. Relating to SOA's foundation (discussed in earlier conference calls), Business-Data-Technology Architectures, a resource maps to a Business Domain Object which is the output of Business Architecture. But Business Domain Objects are not well-defined in the sense that there is no reference taxonomy at the moment. One approach to arrive at a Business Domain Object taxonomy is to abstract it and view it as a resource. What is the definition of a resource? This conference call presents one definition of a resource from an IBM Systems Journal article on Business Architecture 1994. This is probably somewhat out-dated and the purpose of the call is to initiate a discussion to gather more up-to-date information either from literature or from the real world.
May 11, 2007
Postponed due to Global Integration Summit
April 27, 2007
Topic: REST and APP
We will continue the dialog concerning REST at this call. Anthony Starks will lead a discussion on APP - the Atom Publishing Protocol (APP for short) is a simple HTTP-based protocol for creating and updating Web resources. Click here http://icsoawiki.icmembers.org/document/download/1197 to view the presentation during the meeting.
All interested attendees are also encouraged to review, and comment, on the Software Ecologist BLOG on this topic. We will also review the BLOG interactions at this conference call.
April 13, 2007
John Schmidt will present an introduction to the topic of REST - Representational State Transfer based on Roy Fielding's 2000 doctoral dissertation on the architecture of the web. The presentation will include a discussion among the attendees on what lessons could be learned from REST and how they might be applied to improve the success of SOA implementations.
REST as a case study for improving SOA practices:
As Roy Fielding states in his Doctoral Disseration on REST http://icsoawiki.icmembers.org/document/download/1098,
Understanding the key architectural principles underlying the Web can help explain its technical success and may lead to improvements in other distributed applications, particularly those that are amenable to the same or similar methods of interaction.
REST contributes both the rationale behind the modern Web’s software architecture and a significant lesson in how software engineering principles can be systematically applied in the design and evaluation of a real software system.
Members are encouraged to participate in this discussion by commenting on the Software Ecologist BLOG http://www.icmembers.org/blog/software-ecologist/2007/3/20/soa-vs-rest and by joining one of the upcoming IC SOA Conference calls.
Looking for information on how to participate and join?
Contact Leanne MacDonald at lmacdonald(at)integrationconsortium.org.
IC Members are encouraged to consider presenting at an upcoming IC SOA conference call, exclusively for other IC members. Calls are typically held monthly and are 60-90 minutes including time allotted for Q & A at the end of the presentation. Topics of discussion must be educational in nature and must be applicable to a broad cross-section of members including end-users, suppliers, integrators, academics and analysts.
"IC SOA is a forum for sharing information on anything related to SOA. I have found nuggets of information that are hard to come by as this is information born of practicing in the field versus what some vendor or academician's vision is of what SOA is about."
Irene WongBushby, NJIT
Sub-Topics
| Title | Summary |
|---|---|
| IC SOA Collaboration Wiki | IC SOA Collaboration Wiki |
