Streamlining Development for Voice and Data Services
Configurable Application Footprints
The SOA provides flexibility during deployment. One such way is through configurable application footprints. These footprints allow turning off unused services in situations where they go unused.
In an example, let's say we needed a Web application server supporting servlets and JSPs, but didn't require EJB or CORBA component support. In this case, we could turn off or remove the EJB container, the ORB service, the transaction manager, and so forth, to effectively create an optimal environment. An application server designed using a service-oriented approach would support this flexibility.
Service-Oriented Approach to Digital Content Management
The next step is creating and may include many types of content capture and creation vehicles as well as workflow, authoring, layout, access control, and copyright/trademark management. Publishing includes activities such as proofing, editing, rights management, watermarking, and assembling. Collecting is the aggregation and organization of separate pieces of content into groups relative and meaningful to users. Distribution includes all forms of deployment of content required to get content effectively to the proper customers. The final step in the process is the receiving of the content, which can take many forms and require multiple delivery applications.
We have mentioned many separate functions required to effectively process and manage digital content which, in the past, have been served up by separate applications and were generally managed manually. The service-oriented approach, however, could provide an integration platform for this digital value chain.
Services can be created that not only allow for the modular assembly and automation of these digital processes but also could facilitate swapping some of the components on the back end with little or no distruption on the client side. For example, accessing digital content can be achieved via a service interface that represents the WebDAV (Web Distributed Authroing and Versioning) protocol. Implementations of this interface then can provide access to multiple WebDAV-supporting content management systems. Similarly, services can be created to facilitate integration of other digital content applications such as digital rights management, content distribution, and so on. The flow of digital assets through the system would potentially be governed by a workflow service that interacts with the other services.
About the Author
Jonathan Maron is a Distinguished Engineer with Hewlett-Packard's Middleware Division. He was the principle architect of the Bluestone EJB 1.1 Server and has been a member of the EJB and J2EE expert groups. He is currently serving as the Specification Lead for the Java Services Framework, a Java Community Process (JCP) Java Specification Request (JSR).
Page 2 of 2