<?xml version="1.0"?>

 
<rss version="2.0">
<channel>
<title>IBM developerWorks : Web services : Articles</title>
<link>http://www.ibm.com/developerworks/</link>
<description>The latest content from IBM developerWorks</description>
<pubDate>27 Nov 2009 01:15:56 +0000</pubDate>
<language>en</language>
<copyright>Copyright 2004 IBM Corporation.</copyright>
<image>
<title>developerWorks</title>
<url>http://www.ibm.com/developerworks/i/dwlogo-small.gif</url>
<link>http://www.ibm.com/developerworks/</link>
</image>

	<item>
		<title><![CDATA[SOA meets situational applications, Part 1: Changing computing in the enterprise]]></title> 
		<description><![CDATA[As Service-Oriented Architecture (SOA) comes of age, gaining wider
      acceptance in the enterprise, the Web 2.0 buzz grows louder -- perhaps matching the
      SOA hype of two years ago. Many clients and colleagues are asking, &quot;What&apos;s the
      relationship between the SOA and situational applications?&quot; &quot;Are they orthogonal or
      complementary?&quot; &quot;Who cares about the distinction, and are these relevant to two
      totally different audiences?&quot; This article covers the applicability of Web-based
      situational applications (SAs) to the enterprise, their relationship to SOA, and how
      you can use them to improve the current state of corporate IT. Learn about the IBM
      experience in building the Situational Applications Environment (SAE), which was
      developed to support the community-based computing that takes advantage of both
      traditional SOA and emerging Web 2.0 technologies and approaches. Also, examine
      several SAs, and learn about their business situations and challenges,
      architectures, tangible business results, technologies that enabled the solution,
      and the lessons learned.]]></description> 
		<link><![CDATA[http://www.ibm.com/developerworks/webservices/library/ws-soa-situational1/index.html?ca=drs-]]></link> 
		<pubDate>23 Aug 2007 04:00:00 +0000</pubDate>               
	</item>

</channel>
</rss>


