The authors of Designing Forms for SharePoint and InfoPath: Using InfoPath Designer 2010, 2nd Edition share the story of InfoPath, a tool that helps end users interact with and share XML data.
As everyday business activities spread outside the traditional office, we need flexible ways to access our data, share it, and collaborate. Eric Geier examines five of the most popular services for storing and sharing files online.
This chapter includes case studies to illustrate the effectiveness of SONAR, a content distribution model designed to improve ROI on existing web content.
In this chapter, the authors first explore the concept of service orientation and then analyze how the emergence of different architectures' combined paradigm shifts in enterprise technologies led to the evolution of web services and SOA.
At some point during its lifetime a service might need to be enhanced or modified as a result of an external or an internal stimulus. The Service Refactoring design pattern addresses this issue in a manner so that the existing service consumers are not affected by the required change.
James Mathewson gets a lot of questions about what it means for the reader to be in control. In this article, he unpacks this truth in terms of a user behavior that is common and growing in digital media.
This chapter from 100 SOA Questions answers the questions,
what is SOA, is SOA an architectural style, what are fundamental constructs (the DNA) of SOA, what is the difference between a Web Service and an SOA service and what makes a project an SOA implementation?
Get a brief overview of the various Drupals (the project, the websites, and the association) and what they mean to you. You'll also see some examples of Drupal in action and get an overall look at how Drupal works.
The Views 2 user interface is significantly different from the original Views UI. This chapter talks about the Views user interface, shows how each function works, and explains how to create displays.
The Event-Driven Messaging design pattern attempts to address the inefficiencies related to the use of the traditional polling based model by suggesting a publisher-subscriber based model whereby a service interaction occurs only when an event occurs within the boundary of the service provider.
vSphere 4.0 is VMware's successor to Virtual Infrastructure 3 (VI3). In this chapter, Eric Siebert and Simon Seagrave introduce the many new features of vSphere 4.0.
You adopted MVC to get better control over your URL structure. Then you're asked to provide REST access over the same data. Instead of developing a new API and set of endpoints that mirrors what you already have, you can augment the existing application to respond to requests for JSON and XML as well as handle data updates and deletes. Scott Seely shows you how.
The Canonical Protocol design pattern is one of the inventory standardization patterns that aims to elevate the composition-centric characteristic of SOA by making services interoperable with each other. By enforcing the use of a common communication framework, it eliminates the need for protocol bridging and increases the reusability and the recomposability potential of services in a service inventory.
The Enterprise Inventory design pattern attempts to maximize the reusability and recomposition of services by proposing the development of services based on a single enterprise-wide service inventory.
This chapter provides an introduction to general governance concepts and terms, as well as fundamental topics regarding governance systems for SOA projects.
Legal expert Robert McHale discusses the principal federal and state laws regulating cloud activities, and the legal security and privacy risks associated with cloud computing.