Browse Prior Art Database

Web services component assembly tool

IP.com Disclosure Number: IPCOM000016120D
Original Publication Date: 2002-Oct-06
Included in the Prior Art Database: 2003-Jun-21
Document File: 5 page(s) / 162K

Publishing Venue

IBM

Abstract

In general, in most software development tools, the concept of application or software component assembly relies on the component as the unit of assembly (assembly occurs at the component level). In this context applications or components can be created as a result of the assembly of components; this is most often thought of as the process of using components to build applications or larger grained components. A component created as a result of the assembly of components inherently contains the artifacts that makes up the components used as building blocks (sub components); the new component is delivered as a deployable unit containing sub components. Presumably assembly occurs from components that have a certain configuration. Picture 1. Software components made of other software components Component A is assembled from components(C,D,E) Component B is assembled from components(G,H,F) What is described here is an assisted way to create a server side business component from the assembly of web services (see http://www.uddi.org/ for more information on web services). By assisted way is implied the concept that the software component is not programmatically created but rather generated from a software development tool. In this context, the unit of assembly becomes the web service (assembly occurs at the web services level); this is also often described as the process of bringing multiple web services together in support of a much broader or specialized web service. This concept implies that web services can be composed and/or aggreagated (dynamically or non dynamically) with other web services; this can be acheived from deployed or non depoyed web services.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 38% of the total text.

Page 1 of 5

Web services component assembly tool

  In general, in most software development tools, the concept of application or software component assembly relies on the component as the unit of assembly (assembly occurs at the component level). In this context applications or components can be created as a result of the assembly of components; this is most often thought of as the process of using components to build applications or larger grained components. A component created as a result of the assembly of components inherently contains the artifacts that makes up the components used as building blocks (sub components); the new component is delivered as a deployable unit containing sub components. Presumably assembly occurs from components that have a certain configuration.

Picture 1. Software components made of other software components

Component A is assembled from components(C,D,E) Component B is assembled from components(G,H,F)

What is described here is an assisted way to create a server side business component from the assembly of web services (see http://www.uddi.org/ for more information on web services). By assisted way is implied the concept that the software component is not programmatically created but rather generated from a software development tool. In this context, the unit of assembly becomes the web service (assembly occurs at the web services level); this is also often described as the process of bringing multiple web services together in support of a much broader or specialized web service. This concept implies that web services can be composed and/or aggreagated (dynamically or non dynamically) with other web services; this can be acheived from deployed or non depoyed web services.

The distinction here is that the tool creates a server side business component (conforming to a specific component standard) by stringing together web services in a common process (an in-component process) that becomes part of the newly created component. The tool outputs a server side business component and, optionally, a WSDL based definition of the component services so that the new component services can be exposed as web services. The new component is not made of component (sub components), hence no sub component artifacts are being delivered as part of the newly created component (the deployment unit does not contain artifacts from sub components). The generated business component has unique identity and is instanciable in the runtime environment; it can be statefull or stateless.

1

Component A

Component

C

Component

D

Component

E

Component B

Component

G

Component

H

Component

F

Component Platform

[This page contains 7 pictures or other non-text objects]

Page 2 of 5

Picture 2. Software component assembled from web services

Published/deployed web services

o o o o

Component A

Internet/Intranet

Service provider logic implementation (application components, others)

Component Platform

The tool promotes use of both a top-down and a bottom-up app...