Scenario: Stand-alone Application

A stand-alone application deploys services locally, uses the services, and terminates the services when they are no longer needed. If an application does not need to interact with any other applications, then it can be a stand-alone application with its own exclusive local service deployment. Services locally deployed by this application are not available to any other application; in addition, no remote services are available.

Note: A foundation service-enabled application can be either a standard client application or a Web client application that runs in a servlet container.

To deploy local services for its own exclusive use, the application:

1. Uses the service loader to query service deployment metadata from either a SAS Metadata Server or XML file (that contains exported metadata).
2. Uses the service loader to instantiate services defined in the service deployment metadata and registers them with the local Discovery Service.
3. Uses the local Discovery Service to find services based upon their service interfaces and optionally, their service attributes.

When the application no longer needs the services or is ready to exit, it terminates the local Discovery Service; the local Discovery Service then destroys all locally instantiated services.

Figures 1 and 2 show standalone applications that access their service deployments from a SAS Metadata Repository or XML file respectively. Figure 3 shows two standalone Web applications that access their service deployments from a SAS Metadata Repository and each deploy their own local services for their own exclusive use.