Software Configuration, Distribution, and Deployment of WebServices

1
Software Configuration, Distribution, and
Deployment of Web-Services
Authors Rainer Anzbock,
D.A.T.A Corporation,
Schahram Dustdar Harald Gall, Distributed
Systems Group, Vienna University of Technology
Source Anzböck,Schahram Dustdar,
Harald Gall, ACM International Conference
Proceeding Series, SEKE 02, Proceedings of the
14th international conference on Software
engineering and knowledge engineering, July
15-19, 2002, Ischia, Italy., Pages 649-656

• Priya Parasuram
• ppb52_at_umkc.edu

2
History ..

• Previous attempts at distributed computing
  resulted in systems with high coupling, hence
  less effective for B2B over the Internet.
• The current trend in the application is moving
  towards loosely-coupled, dynamically bound
  components.
• IBM believes that applications will be based on
  composition of services discovered dynamically at
  runtime. Application integration is the
  innovation of next generation e-business.
• History dates back from 2000, with the publishing
  of WSDL to development of various working groups
  for different purposes.
• WS advancement over e-B2B.

Craig Dorato, Chief Executive Officer, Grand
Central Communication
3
What is Web-Service?

• Web-services can be seen as a newly emerging
  distributed computing model for the Web (Authors).

Distributed computing is a science which solves a
large problem by giving small parts of the
problem to many computers to solve then
combining the solutions for the parts into a
solution for the problem.

• Web-services are self-contained,
  self-describing, modular
  applications that can be published, located and
  invoked across the Web. (IBM)

A Modular Application is one that contains
several components that can be independently
licensed. An example of this is an accounting
package.

• Loosely-coupled software applications that use
  open standards to describe an interface for
  accessing them and a messaging format for
  communication.

Connection of two or more computers, each with
its own resources (e.g., memory, I/O), which
operate more or less autonomously (typically
using multiple operating systems).
WSDL XML SOAP Web-Services
4
Why Web-Services?

• Support both software developers and systems
  integration.
• Support exchanges cross-platform and data-driven
  focus.
• Concordance with existing Internet
  infrastructure.
• Tolerance to failure, a serious problem for
  heterogeneous networks.
• Strong support in software development and
  business workflow management.
• Good for most trivial request/responses exchanges
  as well as handling most sophisticated
  transaction and security concerns.

Craig Dorato, Chief Executive Officer, Grand
Central Communication
5
This paper talks about

• Architectural issues and requirements of Software
  configuration for Web-Services.
• The purpose of this paper is to develop an
  architecture for Web-services based on Internet
  standards.
• The authors present WebDAV as a solution to
  versioning this IETF working group works towards
  providing extensions to HTTP protocol, to use
  Internet standard.
• Integration standards can be provided using HTTP
  based SOAP protocol.

6
Architecture for Web-Services

• Web-service architecture targets the development
  of applications based on Web standards and eases
  the construction of distributed systems.
• Constituents of Web-Service architecture

7
Architecture Case Study

• Configuration Management selects the correct
  Web-service component version by incorporating a
  Version Management System.
• The customer database needs to be taken care of
  for installation, configuration during
  instantiation of the service and un-installation
  when de-activating the service, which is taken
  care of by the distribution tasks.
• Version Management Control Takes care of the
  versions with respect to the database,
  application services provided to the customer,
  and specific configuration operations.
• The changes made need to be consistently
  maintained between the Internet portal and
  integration of contents.

8
Architecture A Case Study
Fig 1 Web-service process
9
Architecture A Case Study

• Restricted areas can be accessed for testing
  purposes, then the site is made available to all
  clients.
• Registration information for Web-Services, needs
  to be updated with WSDL.
• Activation time is given so that the customers
  can get used to the new service, then the
  de-activation follows.
• Now the contents are removed from the Web-service
  and state information is sent to the distribution
  system.
• Application server removes the component and the
  database server updates and removes the database.

10
Analysis of Architecture

• The larger the created area, higher the overall
  requirements with respect to it.
• Frequent software changes demand version changes,
  hence need for integrated Version Management.
• Points to be noted
• Need to provide continuous availability of
  Web-service to the customer.
• Security to prevent non-authorized
  users, from misusing the system

Fig2 Architecture Analysis
11
Logical View of Model
Fig3 Logical View
12
Logical View of Model

• Logical View describes the classes used in the
  configuration process
• Software abstraction content, service,
  component, policy.
• Customer abstraction
• Distribution process Distributable services,
  Content Management, installer, Plan,

13
Model Process View - Configuration

• Distributable definition is created.
• Customer definition identified.
• Software definition identified.
• Update Common repository.
• The distributable creation is similar to the
  Client-Server interaction, and once the different
  components are identified the distributable is
  created.

Fig5 Process View - configuration
14
Process View - Distribution
Fig6 Process View - distribution
15
Process View - Distribution

• Phases in distribution process Create plan,
  Execute plan Activity enabled.
• Create Plan Select a distributable and
  initialize it. The description of Web-service
  related activities is noted. This plan is stored
  in the repository.
• Execute Plan Initialize, execute the plan based
  on the activity definition. Database and
  registration related issues to be noted.
• Enable Activity Configuration, back-up and
  restoration of database, maintain state of the
  activities and update the records.

16
Deployment View
Fig7 Deployment View
17
Deployment View

• Web-Service system application servers, database
  servers, components and databases.
• Application Server hosts the common services,
  Web based application, HTTP support, transaction
  support.
• Distribution Process provides installer
  applications and distributables.
• Repository replication to allow on-site
  installation of components.
• Nodes are clustered to provide fault tolerance
  and load balancing.

18
Limitations of Case Study

• The case study not include client server
  interaction used by the customer.
• The kind of platform the Web-Service supports is
  not included as Microsoft Operating System,
  Database systems and Web-Services are the terms
  in generic used.
• The case study does not extend for the developers
  to look through the payment and licensing issues
  with respect to the customer.

19
Current Trends Research

• Eastman Chemicals apply Web-Service to improve
  the way they wire interaction with the clients.
  B2B being more expensive and inefficient,
  Web-services is providing them better
  interaction, distribution still cheaper.
• Akamai, The Globus Alliance, HP, IBM, Sonic
  Software and TIBCO propose new Web services
  specifications "that will integrate Grid and Web
  services standards". The two new specifications
  provide a "foundation for the Open Grid Services
  Architecture.
• Mobile web-service applications and Multimedia
  Messaging Service.

20
Summary

• Internet provides personal productivity, whereas
  WebServices provide co-operative productivity.
• Distribution environments have become an integral
  part for vendors to distribute the latest
  software versions, and provide up-gradations.
• An architecture based on the current requirements
  is presented, with the aim of supporting
  customization, configuration, version management
  and consistency.

21
References

• http//webservices.xml.com/pub/a/ws/2001/04/04/web
  services/index.html webservices a primer by Venu
  Vasudevan, April 24, 2001
• http//www-306.ibm.com/software/solutions/webservi
  ces/grandcentral_svideos.html Web services by
  IBM, Customer Example, Speed to Market, Business
  Benefits.
• http//www.w3.org/TR/2004/NOTE-ws-arch-20040211/i
  d2260892 W3C Working Group Note 11 Feb 2004.
  David Booth, W3C Fellow / Hewlett-Packard, Hugo
  Haas, W3C, Francis McCabe, Fujitsu Labs of
  America, Eric Newcomer (until October 2003),
  Iona, Michael Champion (until March 2003),
  Software AG, Chris Ferris (until March 2003),
  IBM, David Orchard (until March 2003), BEA
  Systems
• http//www-106.ibm.com/developerworks/webservices/
  library/w-ovr/ Web Services architecture
  overview, The next stage of evolution for
  e-business. IBM Web Services Architecture Team
  (karlgott_at_us.ibm.com), IBM 1 September 2000
• http//firebird.rit.edu/EAIWiki/WebServicesExample
  s WebServices Examples, last edited 11 months ago
  by Luis Batista

22
Thank You