SAS 9.1.3 Integration Technologies » Administrator's Guide

SAS Foundation Services
Understanding
Service Deployments
Service Deployment Configuration
Managing Service Deployments
Defining
Importing
Exporting
Duplicating
Redistributing
Installing and Running Foundation Services as a Windows Service
Understanding How Applications
Deploy Foundation Services
Locate Services
Scenario: Stand-alone application
Scenario: Remote-accessible Services
Scenario: Local and Remote-accessible Services
Share Foundation Services
Modifying Service Configurations
Event Broker Service
Events and Process Flows
Modifying the Configuration
Creating Events and Process Flows
Information Service
Logging Service
Pattern Layouts
Session and User Service
Monitoring Applications
Foundation Services

Understanding How Applications Locate Foundation Services

Applications can access services that are deployed locally or remotely.

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

To locate local and remote services:

  1. The application uses a service loader to instantiate and initialize local services, including its local Discovery Service.

  2. The application initializes and registers the local Discovery Service with a remote Discovery Service. The application locates the remote Discovery Service by obtaining the Remote Method Invocation (RMI) registry location from a SAS Metadata Repository (or XML file that contains exported metadata) and performing an RMI name lookup on the remote Discovery Service. The remote Discovery Service enables the client to locate remotely deployed SAS Foundation Services.

  3. When the application requests a service, its local Discovery Service first checks to see if the service is a locally registered service.
    • If the requested service is a locally registered service, the application binds to the local service.
    • If the requested service is not a locally registered service, then the local Discovery Service uses the remote Discovery Service to search the remote services deployment for the requested service.
      • If the requested service is not registered with the remote Discovery Service, an error is returned.
      • If the requested service is registered with the remote Discovery Service, a stub to the remote service is returned and the application can then use the remote service.

For example, in the following diagram, if an application requests the Logging Service, the application will bind to the local Logging Service. If an application requests the Session Service, the application will use the remote Discovery Service to locate and bind to the remote Session Service.

Diagram showing how Applications Deploy, Access and Use Foundation Services

Note: If the application that deploys the remote services also starts the service registry, the service registry must exist on the same machine as that application.

The following scenarios show examples of local and remote service deployment and access.