|
|
| Service Oriented Enterprise |
|
|
Thursday, April 10, 2003 Bob Sutor on Web Service Standards Taken from, http://news.com.com/2008-1082-995956.html But is there any one hot-button issue that people can't agree on?The one spot where people are still facing off is on choreography and that really goes to the politics of the standards organizations themselves. But the momentum for standards for Web services has clearly shifted to OASIS (Organization for the Advancement of Structured Information Standards). The W3C has decided that it wants to start a group around Web services choreography; IBM doesn't necessarily think that's the right choice or right venue, but we'll see how it works out. Will IBM abide by the decision? In what sense? If they decide on something that's not to IBM's liking, will you be good soldiers and abide by the decision of the group? Who's the group though? The W3C staff or the 500 member companies? That's where it gets little difficult because if you look at the models of the W3C and OASIS, they are very different. The W3C has a very strong centralized model of control; OASIS is far more decentralized so it doesn't necessarily make any difference what the OASIS staff feels about standards. They are more focused on providing the environment for people to get together. So you have this tension between them. posted by jeff | 7:17 AM Monday, April 07, 2003 Process Driven Organization I'm proud to announce that we are launching a new educational site called the "Process Driven Organization". This site is part of a series of sites Momentum Software is launching to paint a vision for the future of enterprise computing. A Process Driven Organization treats its business processes as a portfolio of valuable corporate assets. Business Process Management techniques are used to explicitly define and execute processes in a manner that creates significant benefits. The fundamental shift made by a Process Driven Organization is that business processes are built for agility and they are liberated from the IT applications that support them. posted by jeff | 6:34 PM Sunday, April 06, 2003 HP & Web Services "Hewlett-Packard (HP) plans aggressive investments to position itself as the dominant vendor in Web services management. To succeed, HP must execute better than it has done on other software initiatives." See: http://www4.gartner.com/DisplayDocument?doc_cd=113541 posted by jeff | 4:54 PM Sun News Letter - Web Services Expo Taken from, System News for Sun Users, Vol 62 Issue 1 9437: Vaughn Spurlin Reports on the Second Annual Web Services Expo Event Focuses on Currently Operational Web Services Projects "In his account of the Second Annual Web Services Expo,sponsored by the Software Development Forum, Vaughn Spurlin reports that the focus was on currently up-and-running Web Services; the huge ROI that well-placed Web Services projects can deliver; the need for a detailed, convincing business plan if obtaining funding is the object; the pall on buying technology simply because it is new and different; and the emergence of SOAP as a four-letter word not to be used in polite company. Spurlin also includes summaries of each of the 14 presentations, among which were: Intel Chief Strategist, Chris Thomas, stressed the need for "occasionally connected computing" (OCC), which would enable work to continue when no net connection was available. Web-based ordering should download data by subscription, he said, eliminate server lag and use drag and drop to enable completion of forms offline. Reggie Hutcherson, manager of the Technology Evangelism team in the Technology Outreach Group at Sun Microsystems, outlined the phases of Web Services adoption: Web Services over HTTPS (happening now), Enterprise Application Integration (EAI) Web Services (beginning), and business Web Services --including UBL and ebXML (2004 plus). He said more work is needed in Quality of Service, security and Identity Management and stressed Sun's focus on Java TM 2 Platform, Enterprise Edition (J2EE TM ), ebXML and UBL, and the Liberty Project. The Sun TM Open Net Environment (Sun ONE) provides a deployment mechanism for Web Services, he said. Finally, Christine Clevenger, SAP VP for Industry Business Unit High Tech, explained her company's new solution, NetWeaver, which she said customers will use to integrate existing multiple SAP installations within their enterprise. Synchronizing master data is the key to interoperability. posted by jeff | 9:18 AM P2P & Web Services - - Was I wrong? Some time back, I wrote an article on, "The Convergence of Peer and Web Services". At the time I was trying to build some software on top of JXTA and realized that what it really needed was web service interfaces. The JXTA team (Sun) was willing to have web service capabilities as add-on's but refused to have it in the core. It was clear to me that this was a failing proposition - my team attempted some things like creating a bridging framework (see Jockey). Jockey was a hack - don't get me wrong - considering the fact that the web service designers were thinking "centrally distributed" (UDDI) while the P2P guys were thinking "resiliency first" it was a happy medium. I recently had to write some code to parse up WS-Inspection documents and it hit me that WS-Inspection was a first step towards P2P based web services. I was happy that the location of the inspection document was easy to find, easy to parse and physically close to the service it described. Ultimately I think that WS-Inspection was designed correctly - however, it needs complementary specifications to address some additional aspects - like: - Show me the services that have consumed me lately (a most recently used-by list) - Show me other endpoints that agree to this contract (a list of same service, but other providers) Now, some of this is covered in UDDI - and perhaps that is where this stuff will land. However, the UDDI spec seems to be growing and growing and growing. It's growth seems to be more around how to make one big ass, formal UBR. This is good and bad - the requirements for a golden repository with slaves are similar to a peer-to-peer contract repository. Thus, UDDI (although overkill) might just do it. One of the things that the P2P guys got right (IMHO) is that they realized that finding services (peer or web) isn't always a formal process. In a P2P world, as you bump into servers, you are informed of additional services. In essence, each peer brags about the services it knows about. In the Web Services world this doesn't happen - the only way find a service is by intentionally hitting a UDDI, WS-Inspection or knowing a URL. This sucks. Perhaps it is time to formalize, "My Favorite Web Services". All in all, I don't think I was wrong - perhaps early. One thing that is clear to me is that it will be web services in the forefront and p2p used as an add-on (e.g., SOAP binding for JXTA, SOAP binding for Jabber, etc.) Then, each of these transport providers will have to provide translation services (translate idl contracts, translate transaction contracts, etc.) Eventually the concepts between these domains will merge. Now the question is, will it be Graham Glass setting the standard or Microsoft? posted by jeff | 7:59 AM |
|
|
|
|
||||||||||||
|
 |
|||||||||||||||
|
||||||||||||||||
