Skip to main content

Home/ In-the-Clouds-with-SOA-XML-and-the-Open-Web/ Group items tagged SOA

Rss Feed Group items tagged

Philipp Arytsok

8 SOA mistakes architects should avoid - 0 views

  • 8 SOA mistakes architects should avoid
  •  
    A pessimistic approach towards SOA seems to prevail in some blogs. But these opinions strike me by surprise. In the industries I am working for - public sector, healthcare and Defense/ public security - SOA is predominant and you will find only rare examples of tenders where SOA is not highlighted as the guiding principle for the whole architecture. SAP's CTO Vishal Sikka has already provided the community with some very helpful insights concerning these discussions. I just want to add some points from an architect's point of view: From my point of view it is not the SOA approach itself which should be questioned but the way how we architects sometimes work on SOA. Some of the mistakes that are listed below I have encountered during my SOA projects. Others are based on discussions with other architects and decision makers inside and outside SAP, from customers and from partners. My intention is simple: I want to help to avoid these mistakes in the future and to strengthen the SOA approach which is for me without an alternative.
Philipp Arytsok

SOA ist nicht tot - SOA ist Mainstream || IT-Republik - Business Technology - News - 0 views

  • SOA ist nicht tot – SOA ist Mainstream
  •  
    SOA ist nicht tot - SOA ist Mainstream
Gary Edwards

XML-Empowered Documents Extend SOA's Connection to People and Processes | BriefingsDire... - 0 views

  • We're going to talk about dynamic documents. That is to say, documents that have form and structure and that are things end-users are very familiar with and have been using for generations, but with a twist. That's the ability to bring content and data, on a dynamic lifecycle basis, in and out of these documents in a managed way. That’s one area.The second area is service-oriented architecture (SOA), the means to automate and reuse assets across multiple application sets and data sets in a large complex organization.We're seeing these two areas come together. Structured documents and the lifecycle around structured authoring tools come together to provide an end-point for the assets and resources managed through an SOA, but also providing a two-way street, where the information and data that comes in through end-users can be reused back in the SOA to combine with other assets for business process benefits.
  • Thus far we’ve been talking about the notion of unstructured content as a target source to SOA-based applications, but you can also think about this from the perspective of the end application itself -- the document as the endpoint, providing a framework for bringing together structured data, transactional data, relational data, as well as unstructured content, into a single document that comes to life.Let me back up and give you a little context on this. You mentioned the various documents that line workers, for example, need to utilize and consume as the basis for their jobs. Documents have unique value. Documents are portable. You can download a document locally, attach it to an email, associate it with a workflow, and share it into a team room. Documents are persistent. They exist over a period of time, and they provide very rich context. They're how you bring together disparate pieces of information into a cohesive context that people can understand.
  •  
    There is a huge productivity jump to be had by sinking data management into the "system"!
  •  
    Dana Gardner transcript of podcast interview with JustSystems and Phil Wainwright. Covers the convergence of the portable XML document model with SOA. It's about time someone out there got it. You know the portable XML document has arrived when analyst finally get it.
Gary Edwards

Microsoft SOA Products & Investments: Oslo - 0 views

  • Microsoft is investing some of the top engineering talent at the company to make two key investments: Deliver a world class SOA platform across client, server, and cloud. Microsoft has been a thought leader in Web services and SOA technologies since the very beginning and has delivered industry leading technologies such as the Windows Communication Foundation and BizTalk Server. Deliver a world class and mainstream modeling platform that helps the roles of IT collaborate and enables better integration between IT and the business. The modeling platform enables higher level descriptions, so called declarative descriptions, of the application.
  •  
    SOA platform that extends across client, server and cloud. Scary stuff that preceeded the Live Mesh - Silverlight announcement at Web 2.0 (2008)
Gary Edwards

Open source SOA infrastructure project CXF elevated to full Apache status | Dana Gardne... - 0 views

  • CXF is really designed for high performance, kind of like a request-response style of interaction for one way, asynchronous messaging, and things like that. But it’s really designed for taking data in from a variety of transports and message formats, such as SOAP or just raw XML. If you bring in the Apache Yoko project, we have CORBA objects coming in off the wire. It basically processes them through the system as quickly as possible with very little memory and processing overhead. We can get it to the final destination of where that data is supposed to be, whether it’s off to another service or a user-developed code, whether it’s in JavaScript or JAX-WS/JAXB code. That’s the goal of what the CXF runtime is — just get that data into the form that the service needs, no matter where it came from and what format it came from in, and do that as quickly as possible.
  • the fascinating intersection of SOA and WOA — with on-premises services and cloud-based resources (including data) supporting ecologies of extended enterprises business processes
  • Creating federated relationships between private and public clouds and their services and resources requires more than just industry standards. It requires visibility and access, the type that comes from open source communities and open use licenses.
  •  
    The Apache CFX "Interoperability Framework" for SOA Project is ready. We really could have used CFX in the 2003 Comcast project where a Tomcat/MYSQL Web-Stack connected to many disparate blackboxes. The blackboxes were standalone "Inventory and Billing" transaction processing data centers aquired by Comcast during a five year burst of acquisitions. Of course, none of these blackboxes could talk to any other! Enter SOA with XMLHTTPRequest streams. 2002-2003. We needed CFX to scale!
Paul Merrell

Service Component Architecture: Making SOA easier | InfoWorld | News | 2008-04-30 | By ... - 0 views

  •  
    Service Component Architecture (SCA), an SOA specification for transforming IT assets into reusable services, was hailed Tuesday as a way to build services with lower barriers to adoption and link SOA to Web 2.0. ... SCA provides an executable model for assembling services and supports multiple languages such as BPEL (Business Process Execution Language for Web Services), Java and PHP scripts, said Edwards. "It's simplified because it has this principle of removing middleware APIs," said Edwards. ... There are multiple implementations of SCO and SDO, said Edwards. Official 1.0 versions of SDO and SCA from OASIS are expected by the end of the year.
Gary Edwards

The Enterprise- Cloud Duo: SOA plus WOA | Dana Gardner - 0 views

  • Cloud providers and mainstay enterprise software vendors could make sweeter WOA plus SOA music together. They may not have a choice. If Microsoft acquires Yahoo!, there will be a huge push for Microsoft Oriented Architecture that will double-down on “software plus services.” And MSFT combined with Yahoo would have an awful lot in place to work from — from the device and PC client, to the server farm, business applications, developer tools and communities, and ramp-up of global cloud/content/user metadata resources. I think Microsoft already understands the power of WOA plus SOA.
  • The cloud that can manage data in way that allows both user-level and process-level access, with granular permissioning — and allows CXOs to feel good about it all — gets the gold ring. The cloud business is a 50-year business.
  •  
    Review of Dion Hinchcliffe's article, "Web 2.0 driving Web Oriented Architecture and SOA".
Philipp Arytsok

SAP Network Blogs-Future of SOA - 0 views

  •  
    Recent musings in the blogosphere on the demise of service-oriented architecture (SOA) have prompted many of you to ask me for my views on this topic. While I don't want to address any specific article, I do want share a few of my thoughts on the future of SOA.
Gary Edwards

'Enough with WOA, stick to SOA,' say IT architects - I say drop WOA and SOA | Dana Gard... - 0 views

  • So, true, WOA, isn’t an architecture, it’s a webby style of apps and integration, of mashups and open APIs, of using REST and RIA clients, all from a variety of Internet sources. It’s integration as a service, too. These can all be composited, accessed and managed by an enterprise’s internal SOA, or not. The services can come from a cloud, public or private. Forrester says the growth curve for Enterprise 2.0 is steep, but I think it will be even steeper. These webby assets could just as well come together as portals, standalone Web apps, SaaS, or RIA front ends for composited ecology services that support extended enterprise processes. The point is there’s no need to wait.
  • rapid ramp-up of services hybrids — of public/private clouds, services ecologies, internal and external hosting, social enterprise media tools, mashups in myriad forms, integration of services regardless of origins or types of aggregation. You can today begin a business online and scale it without an IT department, or an on-premises datacenter. You just can.
  • The fact is that the definitions of and distinctions between applications, platforms, services, tools, clouds, portals, integration, middleware are — all up for grabs. IT as a concept is up for grabs. The shifts in the software arena at that disruptive. It’s why Microsoft is seeking to buy Yahoo, and not Oracle.
Gary Edwards

Web 2.0 success stories driving WOA and informing SOA | Enterprise Web 2.0 | ZDNet.com - 0 views

  • Organizations clearly want to leverage high levels of interoperability to seize new business opportunities, innovate on top of existing assets, and properly leverage the extensive landscape of software, data, and infrastructure that most organizations have accumulated in large quantities over the years. But we are still having a great deal of difficulty doing so and SOA investments are just not reaping the types of return on investments that most businesses would like to have.
Gary Edwards

Has Microsoft lost its way on desktop computing? | The Apple Core | ZDNet.com - 0 views

  • OM MALIK: You outlined Microsoft’s software-plus-services strategy, but what I want to know about is the changing role of the desktop in this service’s future. RAY OZZIE: I think the real question is (that) if you were going to design an OS today, what would it look like? The OS that we’re using today is kind of in the model of a ’70s or ’80s vintage workstation. It was designed for a LAN, it’s got this great display, and a mouse, and all this stuff, but it’s not inherently designed for the Internet. The Internet is this resource in the back end that you can design things to take advantage of. You can use it to synchronize stuff, and communicate stuff amongst these devices at the edge. A student today or a web startup, they don’t actually start at the desktop. They start at the web, they start building web solutions, and immediately deploy that to a browser. So from that perspective, what programming models can I give these folks that they can extend that functionality out to the edge? In the cases where they want mobility, where they want a rich dynamic experience as a piece of their solution, how can I make it incremental for them to extend those things, as opposed to learning the desktop world from scratch?
  •  
    ZDNet's David Morgenstern must have missed ISO approval of OOXML! MS has a desktop strategy, but involves proprietary protocols, formats and API's as the protective barrier for transitioning desktop bound client/server business processes to MS Web Stack bound SaaS-SOA business processes. Welcome to the Microsoft Cloud!
Philipp Arytsok

SAP Network Blogs - 0 views

  •  
    Keep SOA as simple as possible!
Gary Edwards

When SOAs rule the world - 0 views

  • TCG Advisors envisions a new computing model for when the inter-enterprise becomes the basis of all IT infrastructure. Where can we expect the most change? All the action is going to be in the middle [layer] in preparation for a significant change at the top in about five years. We are all [preparing] for a new business model: the inter-enterprise network value chain. For the inter-enterprise network value chain, traditional business applications need to be re-architected so they can cross company boundaries. When people look at this re-architecting, they see two huge barriers: the middleware, because our software doesn't work this way, and the business process layer, because people don't have a lot of experience [with it]. There will be a fair amount of trial and error before we figure this out. Even thought leaders are struggling.
  • The goal has been managing information. We're shifting from managing information to managing processes. Information is an important attribute in process management, but it's not the goal. So trying to turn data into information is the wrong way to look at the problem. What we are trying now is to manage processes across multiple states, where any portion of the process can be in multiple states. So you have to keep state - which is a computing idea - and you have to coordinate actions among self-managing logic. That's the service-oriented architecture paradigm.
  • What service-oriented architectures let you do is recombine - they are like Legos - to make all kinds of innovations out of the existing components of the world. This is very productive. If you're stuck in a client/server system you can't participate in that.
  • ...1 more annotation...
  • The classic microprocessor architecture that Intel dominated is going to become much less relevant. More relevant will be a network processing style of architecture. Everything is going to become a router.
Gary Edwards

Independent study advises IT planners to go OOXML: The Bill Gates MSOffice "formats and... - 0 views

  • 3.2.2.2. A pox on both your houses! gary.edwards - 01/22/08 Hi Robert, What you've posted are examples of MSOffice ”compatibility settings” used to establish backwards compatibility with older documents, and, for the conversion of alien file formats (such as various versions of WordPerfect .wpd). These compatibility settings are unspecified in that we know the syntax but have no idea of the semantics. And without the semantic description there is no way other developers can understand implementation. This of course guarantees an unacceptable breakdown of interoperability. But i would be hesitant to make my stand of rejecting OOXML based on this issue. It turns out that there are upwards of 150 unspecified compatibility settings used by OpenOffice/StarOffice. These settings are not specified in ODF, but will nevertheless show up in OpenOffice ODF documents – similarly defying interoperability efforts! Since the compatibility settings are not specified or even mentioned in the ODF 1.0 – ISO 26300 specification, we have to go to the OOo source code to discover where this stuff comes from. Check out lines 169-211. Here you will find interesting settings such as, “UseFormerLineSpacing, UseFormerObjectPositioning, and UseFormerTextWrapping”. So what's going on here?
  • From: Bill Gates Sent: Saturday, December 5 1998 To: Bob Muglia, Jon DeVann, Steven Sinofsky Subject : Office rendering "One thing we have got to change in our strategy - allowing Office documents to be rendered very well by other peoples browsers is one of the most destructive things we could do to the company. We have to stop putting any effort into this and make sure that Office documents very well depends on PROPRIETARY IE capabilities. Anything else is suicide for our platform. This is a case where Office has to avoid doing something to destroy Windows. I would be glad to explain at a greater length. Likewise this love of DAV in Office/Exchange is a huge problem. I would also like to make sure people understand this as well." Tuesday, August 28, 2007
  •  
    The IOWA Comes vs. Microsoft antitrust suit evidence is now publicly available. This ZDNet Talkback posts an extraordinary eMail from Bill Gates concerning the need to control MSOffice formats and protocols as Microsoft pushes onto the Web. The key point is that Chairman Bill understands that the real threat to Microsoft is that of Open Web formats and protocols outside of Microsoft's control. It's 1998, and the effort to "embrace and eXtend" W3C HTML, XHTML, SVG and CSS isn't working well. The good Chairman notifies the troops that MSOffice must come up with another plan. Interestingly, it's not until 2001, when OpenOffice releases an XML encoding of the OpenOffice/StarOffice imbr that Microsoft finally sees a solution! (imbr = in-memory-binary-representation) The MSOffice crew immediately sets to work creating a similar XML encoding of the MSOffice binary (imbr) dump. The first result is released in the MSOffice 2003 beta as "WordprocessingML and SpreadsheetML". XML was designed as a structured language for creating specific structured languages. OpenOffice saw the potential of using XML to create an OpenOffice specific XML language. MSOffice seized the innovation and the rest is history. Problem solved! So what was the "problem" the good Chairman identified in this secret eMail? It's that the Web is the future, and Microsoft needed to find a way of leveraging their existing desktop document "editor" monopoly share into owning and controlling the Web formats produced by Microsoft applications. MSOffice OOXML is the result. ISO approval of MSOffice OOXML is beyond important to Microsoft. It establishes MSOffice "editors" as standards compliant. It also establishes the application, platform and vendor specific MSOffice OOXML as an international "open" standard. Many will ask why this isn't a case of Microsoft actually opening up the MSOffice formats in compliance with government antitrust demands. It is "compliance", but not in the sense of what
Paul Merrell

Future of the Web | Diigo Group - 0 views

  • Watching the grand convergence of the desktop, the server, devices, and the Web. Topics addressed include events and emerging trends in universal interoperability, standards development, SOA, Clouds, Web-Stacks, RIA run-times, etc.
    • Paul Merrell
       
      New group with overlapping subject matter, the Future of the Web.
  • Watching the grand convergence of the desktop, the server, devices, and the Web. Topics addressed include events and emerging trends in universal interoperability, standards development, SOA, Clouds, Web-Stacks, RIA run-times, etc.
  •  
    New Diigo group with overlapping subject matter, more focused on the web.
Gary Edwards

Web 2.0 Stovepipe System: Sir Tim Berners-Lee: Semantic Web is open for business | The ... - 0 views

  • “Web 2.0 is a stovepipe system. It’s a set of stovepipes where each site has got its data and it’s not sharing it. What people are sometimes calling a Web 3.0 vision where you’ve got lots of different data out there on the Web and you’ve got lots of different applications, but they’re independent. A given application can use different data. An application can run on a desktop or in my browser, it’s my agent. It can access all the data, which I can use and everything’s much more seamless and much more powerful because you get this integration. The same application has access to data from all over the place.”
  •  
    podcast with Sir Tim discusses the "linked Data Project" and the Semantic Web contrast to Web 2.0 Social Stovepipe Systems
Gary Edwards

Live Mesh: Windows Becomes the Web | Microsoft Watch - Web Services & Browser - - 0 views

  • simply: Microsoft is launching a synchronization platform that the company claims is technology-agnostic. That absolutely is not true. Live Mesh is Microsoft's attempt to turn operating system and proprietary services platforms into hubs that replace the Web. It's the most anti-Web 2.0 technology yet released by any company. Microsoft is building a services-based operating system that transcends and extends Windows and also the function of Web browsers. It's bold, brilliant and downright scary. Microsoft has identified the right problem, synchronization, but applied a self-serving solution.
  • The services platform doesn't seek to keep the Web as the hub, but replace it with something else. The white paper is wonderfully misleading, by implying that Microsoft supports the Web as the hub. Live Mesh is the hub.
  • Live Mesh is competitively important to Microsoft because of companies like Google, whose services shift computational and informational relevancy from desktop software to the Web. But there is something missing as data spreads out across the Web platform to millions of devices: simple synchronization.
  • ...3 more annotations...
  • This mesh of services compromises the overlaying platform, which is supported by proprietary Microsoft APIs.
  • APIs, desktop software and Mesh run-time take on real importance. Users must install Live Mesh software on their PC, which includes the synchronization run-time and makes extension changes to Windows Explorer.
  • Microsoft's broader Mesh vision extends the operating system to cloud services. Microsoft's PR information refers to the "Mesh Operating Environment," which would presumably grant end users access to applications anytime, anywhere and on anything. Access includes the Web browser, provided it's from Live Desktop. End users would designate devices in their Mesh that would be permitted to run applications. And, yes, it does foreshadow hosted applications as well as those accessed from a Mesh-designated PC.
  •  
    Joe Wilcox takes on MS "Live Mesh" in a series of articles. Clearly he gets it but one has to wonder about the rest of the techno crowd.
Gary Edwards

Web 2.0 Silos! Sir Tim Berners-Lee addresses WWW2008 in Beijing | The Semantic Web | ZD... - 0 views

  •  
    Perpetuating current data silos by continuing to "give your data to a site" was, Berners-Lee asserted, "not ideal." He argued instead for wider adoption of new or existing Web specifications such as OAuth and RDFAuth, enabling the individual to store data relevant to themselves wherever they felt fit, and assemble it at will within one or more Web and local applications of their choosing at the point of need. "Acquaintance-based social networks," Berners-Lee suggested, were "the tip of the iceberg," with his notion of the emerging Giant Global Graph "exist[ing] above the Web" and creating opportunities for far richer functional and role-based interconnections. Turning to consideration of the Web itself, Berners-Lee remarked that "Openness tends to be an inexorable movement through time" He juxtaposed the 'Web Application Platform' with proprietary solutions to parts of the problem such as Flash, AIR and Silverlight. This Web Application Platform, he argued, relies upon W3C specifications and other open standards, and it is increasingly moving toward specifications that are small, modular, and interoperable. Moving toward his conclusion, Berners-Lee reiterated the importance of Linked Data again saying "Linked Open Data is the Web done as it should be." Returning to his earlier discussion of modularity, he suggested that existing specifications such as those for JavaScript be reworked, carving JavaScript's functionality up into a series of modular packages. Each of those packages should then be assigned a URI, and the Semantic Web should be used to describe the packages, their dependencies, and their interrelationships. Used in conjunction with the resulting applications, Linked Data would provide, "elements of an ability to do things [with data] that cross application boundaries." Turning to Q&A, Berners-Lee was first asked to comment on the concept of 'Web 2.0′, which he did; "Web 2.0 sites a
  •  
    And of course it is the incredible variety in data formats used by Web 2.0 apps that forces the creation of new data silos on the Web. Web 2.0 is bringing us the same kinds of incompatible data format issues forced on software users since the beginning of the proprietary software industry.
Gary Edwards

Meshing the desktop into the cloud | Software as Services | ZDNet.com - 0 views

  • Live Mesh brings that to life, as product director Mike Zintel explains on the brand new Live Mesh blog: “[It] blend[s] the web, Windows and other computing endpoints in a way that preserves the ‘it just works’ feel of the web with seamless integration into my common workflows. The coolest thing about Live Mesh is how it smashes the abrupt mental switch that I have to make today as I move between being ‘on the web’ and ‘in an application’.” At first glance, that may seem a perfectly reasonable and innocuous statement — and indeed it is, if you take a Web-centric view of the world — but coming out of Microsoft, it’s dynamite. Instead of seeing the Web as an extension of the desktop, it includes the desktop as part of the continuum of the Web. Where then does the application sit? Not on the desktop, or on any identifiable server machine, but simply in the mesh. In other words, it becomes a service, capable of running anywhere in the cloud, including on the desktop.
  • “The core philosophy is to make it easy to manage information in a world where people have multiple computing experiences (i.e. PCs and applications, web sites, phones, video games, music and video devices) that they use in the context of different communities (i.e. myself, family, work, organizations) …” “At the core of Mesh is [the] concept of a customer’s mesh, or collection of devices, applications and data that an individual owns or regularly uses.
Gary Edwards

The Mesh lives but the cloud Office is vaporous | Outside the Lines - CNET News.com - 0 views

  • Office Live will bring Office to the web, and the web to Office. We will deliver new and expanded productivity experiences that build upon the device mesh vision to extend productivity scenarios seamlessly across the PC, the web, and mobile devices. Individuals will seamlessly enjoy the benefits of each - the rich, dynamic editing of the PC, the mobility of the phone, and the work-anywhere ubiquity of the web. Office Live will also extend the PC-based Office into the social mesh, expanding the classic notion of "personal productivity" into the realm of the "inter-personal" through the linking, sharing and tagging of documents. Individuals will have a productivity centric web presence where they can work and productively interact with others. This broadly extended vision of Office is being realized today through Office Mobile and Office Live Workspace on the web, augmented by SharePoint, Exchange, and OCS for the connected enterprise.
  •  
    I don't think Dan Farber gets it. ISO approval of MSOffice-OOXML establishes MSOffice as a standards compliant web/cloud/WOA "editor" for client/Web-Stack/server systems. No need to try to squeeze all tha tcomplexity into a browser. Just use the MSOffice SDK OOXML <> XAML conversion component to convert rich, business process loaded, documents to a web ready format. OH my, XAML is proprietary and IE-8 does not support XHTML2, CSS3, SVG, XForms, RDF, SPARQL, SWF, PDF or JavaScript. Bummer. ISO has done the unthinkable and Microsoft can now break the web without worry of anti trust retribution. They are after all, simply implementing an open standard.
1 - 20 of 26 Next ›
Showing 20 items per page