XML and Web services research firm ZapThink said reliability, along with process definition and execution, makes up the third critical roadblock to Web Services adoption after security and management.
“It’s interesting that there are no common members between today’s announcement and the WS-Policy/Trust/SecureConversation announcement last month [Sonic, Hitachi, Fujitsu, NEC, Oracle and Sun for today's announcement, and IBM, Microsoft, Verisign, BEA, SAP, and RSA Security for the December announcement],” said ZapThink Senior Analyst Jason Bloomberg. “This divergence may indicate a continuation of some of the infighting that has gone on between these groups, but then again, it may turn out that everybody is willing to cooperate on this one. In the grand scheme of things, WS-Reliability doesn’t present much of a threat to anyone, so ZapThink predicts that the IBM/Microsoft group is likely to accept this specification with little or no significant changes requested.”
Read more at: Internetnews.comJason Bloomberg, senior analyst for ZapThink, a web services analyst group, believes that while the WS-Reliability specification isn’t breaking any new ground, it is providing a standard that can be applied to all Web messaging. Bloomberg believes that the only major controversy associated with this project is the fact that none of the members of this particular group are members of any other major Web standards partnerships that include industry giants like IBM and Microsoft.
Read more at: destinationCRMBusiness processes have always been an important, if understated, asset of enterprises. The nature and methods by which a company runs its business changes on a daily basis at various different levels in the company — from high-level strategic changes to lower-level implementation details. As a result of these changes, enterprises constantly struggle to make their businesses more responsive to business changes by connecting their business requirements to their IT and human capabilities.
However, automating business processes has historically been a difficult-to-achieve goal for most enterprises due to the flexibility of their IT infrastructure. Fortunately, businesses have a solution in Service-Oriented Process: a separate abstraction layer for business process definition and execution that leverages the capabilities of Service-oriented Architectures. Service-Oriented Process provides businesses an approach to tying business requirements to the Service model represented in the SOA metamodel, thereby providing a flexible approach towards implementing architectures that promote business agility.
SOA Implementation Roadmap