Flow Diagram

The following diagram depicts the flow.




In this diagram, Client 1 contacts a Specialized Application Factory Web Service(SAFWS) that has static information about a genre of application and the client needs to supply only dynamic information. Client 2 contacts a Generic Application Factory Web Service(GAFWS) which can be used to deploy any type of application.

Steps involved are

  1. Clients contact a Registry Service to get the location of the service they need to use,

  2. Client 1 invokes reateApplication method on SAFWS port and passes an XML document with dynamic information pertaining to the specific instance of the application.

  3. SAFWS invokes createApplication method on Generic Application Factory Web Service(GAFWS) and passes both static and dynamic information to it. In the case of Client 2, it directly invokes this method with XML documents describing both the static and dynamic information about the application.

  4. GAFWS launches the Application Coordinator Component(ACC) using the information extracted from the XML documents.
  5. The ACC then launches the constituent components of the application, connects them and exports the relevant ports. To accomplish this task it uses information from the XML documents and the Component Browser(a directory service). It then generates a WSDL describing the Application Instance and itself and returns it to the GAFWS.

  6. The GAFWS returns it to the SAFWS, which passes it to Client 1 or the GAFWS returns the WSDL to Client 2 ,as the case may be



[ IU CS ] [ Extreme! Computing ] [ XGWS ] Application Factory Service   Architecture

Last modified: Tue Jul 9 10:56:05 EST 2002