SAS/CONNECT User's Guide

Introduction

In its simplest form, messaging requires that both the client and the server portions of the application be active at the same time. The client cannot send a message unless a server is listening for a message. This is referred to as direct messaging.

The direct-messaging facility allows basic and flexible message construction, transmission, and notification services that span operating system and hardware boundaries across the enterprise. Messages are free-form. Their structure, which is defined by the application developer, may range from a simple collection of variables to complex hierarchies of SCL lists. Additionally, messages may include one or more attachments that can take the form of SAS data sets or filtered subsets, catalogs or catalog entries, external files, MDDB files, DMDB files, FDB files, and SQL Views.

These applications can run on a single platform or on separate platforms of the same or of a unique type. Also, any number of applications can be simultaneously communicating using direct messaging.

SAS/CONNECT provides tools that enable application developers to deploy multi-tiered distributed applications based on a message-passing paradigm. This multi-tiered design allows you to separate and centralize business logic and data access from the client environment.

The application developer tools include a Station class and a Cnction class. Direct messaging allows messages to be sent (using SCL methods) between two or more instances of the Station class. After station initialization has occurred, the Cnction class is used to make a connection. A server station can service any number of client stations.

Chapter Contents
Previous
Next
Top of Page