ABSTRACT
Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 6.2.2.3 Distributed Using Multiple Application
Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Before distributed services can be integrated into workflow applications, there needs to be a middleware available that allows definition and deployment of services to which various types of software can be mapped as proposed in Section 3.3. For cooperation of services, the middleware would need to support the key functions outlined in Section 3.4.1. The following functions allow implementation of the aforementioned requirements within the middleware:
1. Publishing various types of services (especially scientific and business ones) from servers managed by users very easily. It is possible to define access rights to others on a per-user or per-group policy. It is desired that the provider publishes a resource (application-sequential or parallel, files, etc.) from their own accounts which allows others invoking such a service on their accounts but alternatively allows us to publish installation versions for others to download and use services on their own accounts.
