Platform Services Facade

Overview

Configuration File

The PlatformServices facade class is constructed with a parameter designating a configuration file that designates the platform service deployment(s) that are to be either instantiated locally within the application or looked up remotely. The facade configuration file describes the metadata source to be queried to obtain data describing a platform service deployment.

Starting and Terminating Services

The facade class is constructed with a parameter designating a facade configuration file. This file designates the metadata sources from which platform service deployment data is to be queried (file or directly from OMR). There are three methods that can be used to start services:

The startServices() method first calls startLocalServices() then lookupRemoteServices(). This is probably the most typical scenario.

To terminate services invoke the terminateServices() method. This method will invoke the local discovery service's destroy() method which in turns causes all locally instantiated services to be destroyed. and remote service references to be cleared.

Discovering Services

The services facade implements com.sas.services.discovery.FindServiceInterface delegating all requests to its local discovery service. Services are registered with the local discovery service as a result of executing one of the methods to start or lookup services. If the facade configuration file specifies that some services are to be looked up remotely the facade will attempt to re-lookup remote services in the event that a find request fails to return any results. This is intended to address a case where remotely deployed services become unavailable perhaps due to a server being bounced.