Glossary
- access control entry
-
a set of identities and permissions that are directly
associated with a particular resource. Each access control entry is
directly associated with only one resource. More than one ACE can
be associated with each resource. Short form: ACE.
- access control template
-
a reusable named authorization pattern that you
can apply to multiple resources. An access control template consists
of a list of users and groups and indicates, for each user or group,
whether permissions are granted or denied. Short form: ACT.
- ACE
-
See access control entry.
- ACT
-
See access control template.
- administered object
-
a pre-configured Java Message Service (JMS) object
that is created by a system administrator for use by client applications.
Administered objects handle the complexities of using JMS in conjunction
with proprietary messaging systems so that client applications can
focus on business logic.
- alert
-
an automatic notification of an electronic event
that is of interest to the recipient.
- archive
-
a package that is compressed and saved to a directory.
The archive contains the contents of a package, as well as metadata
that is necessary for extracting the contents.
- asynchronous logging
-
a process that enables log messages to be queued
within and delivered from a thread other than the main application
thread.
- authentication
-
See client authentication.
- authentication domain
-
a SAS internal category that pairs logins with
the servers for which they are valid. For example, an Oracle server
and the SAS copies of Oracle credentials might all be classified as
belonging to an OracleAuth authentication domain.
- authentication provider
-
a software component that is used for identifying
and authenticating users. For example, an LDAP server or the host
operating system can provide authentication.
- authorization
-
the process of determining which users have which
permissions for which resources. The outcome of the authorization
process is an authorization decision that either permits or denies
a specific action on a specific resource, based on the requesting
user's identity and group memberships.
- background processing
-
processing in which you cannot interact with the
computer. Background sessions sometimes run somewhat slower than foreground
sessions, because background sessions execute as processor time becomes
available.
- base
-
the distinguished name (DN) to use as a starting
place for searches of an LDAP directory. Searches can begin at any
point in a directory tree. Beginning the search lower in the tree
can dramatically reduce both the search time and spurious results.
For example, the base might be specified in SAS system options as
BaseDN or ldapBase.
- bind
-
to create an association among two or more entities
for a particular scope of time and place. For example, an association
could be created between two or more programming objects, between
a variable name and an object, between a symbolic address and a real
machine address, or between a client and a server.
- bookmark
-
a stored placeholder for either the address and
name of an electronic document or the address of a location within
an electronic document. Bookmarks provide convenient access and retrieval.
- chaining
-
a process by which a log message is passed to
the current logging context and to each context in the hierarchy of
the current logging context. If chaining is not specified at a particular
level in the hierarchy, then the log message is not passed beyond
that level.
- channel
-
a virtual communication path for distributing
information. In SAS, a channel is identified with a particular topic.
Using the features of the Publishing Framework, authorized users or
applications can publish digital content to the channel, and authorized
users and applications can subscribe to the channel in order to receive
the content.
- client
-
an application that requests either resources
or services from a server, possibly over a network.
- client authentication
-
the process of verifying the identity of a person
or process for security purposes.
- cluster
-
a group of computers that participate in load
balancing. Each computer in the cluster runs an object spawner that
handles client requests for connections.
- COM
-
See Component Object Model.
- Common Object Request Broker Architecture
-
a standard API for distributed object communication.
CORBA was created by the Object Management Group. It is the most widely
used distributed object standard for connecting operating system platforms
from multiple vendors. Short form: CORBA.
- component
-
a self-contained, reusable programming object
that provides some type of service to other components in an object-oriented
programming environment.
- Component Object Model
-
an object-oriented programming model that is used
for building component-based applications. This programming model
defines how software components interact and enables other applications
and processes to access the component-based application. Short form:
COM.
- Connection Factory
-
an application interface that enables Java programs
to make IOM bridge connections to IOM servers. The interface provides
the scalability features of pooling and server failover as well as
support for load-balancing spawners. The interface is part of the
SAS Foundation Services Connection Service.
- Connection Service
-
one of the SAS Foundation Services. This service
enables applications to (1) connect to IOM servers that use the IOM
Bridge protocol, (2) use the Connection Factory to access existing
connection objects and to create new connection objects for various
server configurations, and (3) use advanced connection management
features, such as connection pooling, failover, and load balancing,
which are available through the Connection Factory.
- container
-
a software application environment in which a
component such as an applet, an application client, a servlet, a JavaServer
page, or an Enterprise Java Bean is executed. Containers provide specific
services that can be exploited by the types of components that they
support.
- content type
-
a value that tells a client's Web browser how
to interpret and display a transferred object such as an image file,
a sound file, or a video file. For example, GIF, JPG, TIFF, MIDI,
and WAV are content types.
- context
-
the set of facts or circumstances that surround
a situation or event. In Java applications, context generally refers
to a collection of settings and attributes that describe a container
or service that is currently executing.
- CORBA
-
See Common Object Request Broker Architecture.
- DCOM
-
See Distributed Component Object Model.
- delivery transport
-
in the Publishing Framework, the method of delivering
a package to the consumer. Supported transports include e-mail and
WebDAV. Although not a true transport, a channel also functions as
a delivery mechanism.
- diagram
-
See process flow diagram.
- directory information tree
-
the entries that an LDAP directory server contains.
These entries are stored in a hierarchical, tree-like structure. Short
form: DIT.
- directory schema
-
the set of defined attributes and object classes
that defines the content of acceptable entries within an LDAP directory
server.
- Discovery Service
-
one of the SAS Foundation Services. This service
enables applications to (1) find implementations of the SAS Foundation
Services based on specified service capabilities and service attributes,
and (2) rediscover a previously discovered service by using the service's
Discovery Service ID. The Discovery Service can find service implementations
that have been deployed locally for the application's exclusive use,
as well as service implementations that have been deployed remotely
for the use of multiple applications.
- distinguished name
-
a unique identifier of an entry in an LDAP network
directory. In effect, a distinguished name is the path to the object
in the directory information tree. Short form: DN.
- Distributed Component Object Model
-
an extension to the Component Object Model (COM)
that enables components to request services from components that are
on other computers in a network. Short form: DCOM.
- DIT
-
See directory information tree.
- DN
-
See distinguished name.
- DNS name
-
a name that is meaningful to people and that corresponds
to the numeric TCP/IP address of a computer on the Internet. For example,
www.alphaliteairways.com might be the DNS name for an Alphalite Airways
Web server whose TCP/IP address is 192.168.145.6.
- domain
-
a database of users that has been set up by an
administrator by using a specific authentication provider such as
LDAP or the host operating system. The domain name should be unique
within your enterprise. For example, you should not have a Windows
domain and a UNIX domain that are both named "SALES".
- encryption
-
the act or process of converting data to a form
that is unintelligible except to the intended recipients.
- entry
-
a set of name/value pairs that describe a resource
that is defined on an LDAP directory server.
- entry filter
-
See package entry type filter.
- event
-
a type of notification that triggers an Event
Broker Service to take a particular action. An event is specified
as well-formed XML that contains the name of the event, associated
headers and properties, and the message body.
- Event Broker Service
-
one of the SAS Foundation Services. This service
enables applications to send and deliver events to the appropriate
handling agents for processing. The handling agent can be (1) a statically
defined process flow that runs in its own thread within the Event
Broker Service to process the event or (2) an application that has
registered itself with the Event Broker Service at run time so that
it can receive events.
- event message specification
-
a well-formed XML representation of an event.
The event message specification contains attributes of the event such
as name, version, identity, credentials, sender, send time, and response
type.
- Extensible Markup Language
-
See XML.
- factory
-
an object that controls the creation of other
objects, access to other objects, or both.
- filter
-
See package filter.
- foundation services
-
See SAS Foundation Services.
- global unique identifier
-
a 16-byte (128 bit) number that is used in software
applications to provide a unique reference number for various types
of computer data and objects. GUIDs are usually, but not always, associated
with Microsoft's implementation of the UUID standard.
- group
-
in the Publishing Framework, a collection of subscribers
who receive information that is published to that channel.
- GUID
-
See global unique identifier.
- HTTP
-
a protocol for transferring data to the Internet.
HTTP provides a way for servers and Web clients to communicate. It
is based on the TCP/IP protocol. Short form: HTTP.
- HTTP server
-
a server that handles an HTTP request from a client
such as a Web browser. Usually the client's HTTP request indicates
that the client wants to retrieve information that is pointed to by
a URL. An example of a popular HTTP server is the Apache HTTP Server
from the Apache Software Foundation.
- HyperText Transfer Protocol
-
See HTTP.
- information map
-
a collection of data items and filters that provides
a user-friendly view of a data source. When you use an information
map to query data for business needs, you do not have to understand
the structure of the underlying data source or know how to program
in a query language.
- Information Service
-
one of the SAS Foundation Services. This service
enables applications to perform a federated search of any repositories
that a user has a connection to. The term federated means connected
and treated as one. The classes in the Information Service package
enable applications to create a single filter that can search disparate
repositories (for example, SAS Metadata Repositories and LDAP repositories).
- input stream
-
a connection that enables a client application
to stream data into a stored process. The input stream is visible
to the stored process as a SAS fileref.
- Integrated Object Model
-
the set of distributed object interfaces that
make SAS software features available to client applications when SAS
is executed as an object server. Short form: IOM.
- Integrated Object Model server
-
See IOM server.
- IOM
-
See Integrated Object Model.
- IOM bridge
-
a software component of SAS Integration Technologies
that enables Java clients and Windows clients to access an IOM server.
- IOM bridge for COM
-
the software component of SAS Integration Technologies
that is used (transparently) when a Windows client accesses an IOM
server on a platform other than Windows. The bridge enables applications
that conform to the Microsoft COM or DCOM specifications to access
SAS servers in operating environments such as z/OS and UNIX that do
not support the COM or DCOM specifications.
- IOM bridge for Java
-
a software component of SAS Integration Technologies
that enables Java clients to access IOM servers.
- IOM server
-
a SAS object server that is launched in order
to fulfill client requests for IOM services. Short form: IOM server.
- Java Development Kit
-
See JDK.
- Java Message Service
-
See JMS.
- Java Naming and Directory Interface
-
See JNDI.
- Java RMI
-
See remote method invocation.
- Java Virtual Machine
-
See JVM.
- JavaServer page
-
a type of servlet that enables users to create
Java classes through HTML. Short form: JSP.
- JDK
-
a software development environment that is available
from Oracle Corporation. The JDK includes a Java Runtime Environment
(JRE), a compiler, a debugger, and other tools for developing Java
applets and applications. Short form: JDK.
- JMS
-
an application programming interface (API) that
enables client applications to access the facilities of a message
service. This interface provides a standard way for Java programs
to create, send, receive, and read messages. Short form: JMS.
- JNDI
-
a standard extension to the Java platform that
enables developers to create applications that can interact with a
number of different naming services and directory services, such as
the Domain Name System (DNS) and the Lightweight Directory Access
Protocol (LDAP). Short form: JNDI.
- JSP
-
See JavaServer page.
- JVM
-
a program that interprets Java programming code
so that the code can be executed by the operating system on a computer.
The JVM can run on either the client or the server. The JVM is the
main software component that makes Java programs portable across platforms.
A JVM is included with JDKs and JREs from Oracle Corporation, as well
as with most Web browsers. Short form: JVM.
- keyword
-
a word or phrase that can be stored in the metadata,
that will describe one or more objects or stored items such as processes
or content items, and that can subsequently be used in a filtered
search.
- layout pattern
-
a feature of the Logging Service that enables
you to associate a layout with a particular logging output destination.
The layout specifies how the output is to be formatted before it is
sent to the output destination. The layout is specified as a pattern
string similar to the pattern strings that are used in the C language
printf statement.
- LDAP
-
a protocol that is used for accessing directories
or folders. LDAP is based on the X.500 standard, but it is simpler
and, unlike X.500, it supports TCP/IP. Short form: LDAP.
- LDAP Data Interchange Format
-
a file format that is widely used for building
a database of directories that are stored on multiple servers, for
adding large numbers of directories to a directory database, and for
synchronizing the contents of those directories. The servers on which
the directories are stored must support the LDAP protocol. Short form:
LDIF.
- LDAP directory
-
a repository that contains data about an enterprise's
users and resources, as well as related security information, and
that stores this data and information in a format that clients on
a network can access by using the Lightweight Directory Access Protocol
(LDAP).
- LDAP directory server
-
a server that provides access to one or more LDAP
directories.
- LDAP server
-
See LDAP directory server.
- LDIF
-
See LDAP Data Interchange Format.
- Lightweight Directory Access Protocol
-
See LDAP.
- load balancing
-
for IOM bridge connections, a program that runs
in the object spawner and that uses an algorithm to distribute work
across object server processes on the same or separate machines in
a cluster.
- local service deployment
-
a service deployment that supports an application's
exclusive access to a set of SAS Foundation Services that are deployed
within a single Java Virtual Machine (JVM).
- localhost
-
the keyword that is used to specify the machine
on which a program is executing. If a client specifies localhost as
the server address, the client connects to a server that runs on the
same machine.
- log
-
See SAS log.
- logging context
-
a collection of attributes and settings that define
a particular way in which the Logging Service is to be used. The logging
context specifies where and in what format logging calls will be written.
- Logging Service
-
one of the SAS Foundation Services. This service
enables applications to (1) send run-time messages to one or more
output destinations, including consoles, files, and socket connections;
(2) configure and control the format of information that is sent to
a particular destination, either by using static configuration files
or by invoking run-time methods that control logging output; and (3)
perform remote logging, which involves sending log messages that are
generated in one Java Virtual Machine (JVM) to another JVM.
- logical name
-
a unique name that can be assigned to related
resources in order to manage the resources as a group.
- logical server
-
the second-level object in the metadata for SAS
servers. A logical server specifies one or more of a particular type
of server component, such as one or more SAS Workspace Servers.
- login
-
a SAS copy of information about an external account.
Each login includes a user ID and belongs to one SAS user or group.
Most logins do not include a password.
- message node
-
in a process flow diagram, a node that encapsulates
inputs and outputs to one or more process nodes.
- message queue
-
in application messaging, a place where one program
can send messages that will be retrieved by another program. The two
programs communicate asynchronously. Neither program needs to know
the location of the other program nor whether the other program is
running.
- message queue polling
-
a feature of the object spawner that monitors
message queues and distributes message queue tasks efficiently among
SAS processes.
- metadata
-
descriptive data about data that is stored and
managed in a database, in order to facilitate access to captured and
archived data for further use.
- metadata repository
-
a collection of related metadata objects, such
as the metadata for a set of tables and columns that are maintained
by an application. A SAS Metadata Repository is an example.
- metadata server
-
a server that stores information about servers,
users, and stored processes and that provides this information to
one or more client applications.
- middle tier
-
in a SAS business intelligence system, the architectural
layer in which Web applications and related services execute. The
middle tier receives user requests, applies business logic and business
rules, interacts with processing servers and data servers, and returns
information to users.
- MIME
-
a method of registering content types and their
associated actions with mechanisms for actions such as retrieval and
display. Short form: MIME.
- MIME type filter
-
in the Publishing Framework, a filter that specifies
which file entries of a specific MIME type to include in packages
that are published to a subscriber.
- Multipurpose Internet Mail Extensions
-
See MIME.
- name/value filter
-
in the Publishing Framework, a subscription property
that determines which packages are published to that subscriber. In
order to receive a particular package, a subscriber's name/value filter
must contain the name/value pair that the publisher specifies in the
package.
- name/value pair
-
in the Publishing Framework, an attribute and
value that the publisher uses to describe the contents of a package
or a package entry. For example, a 'type=production' name/value pair
might be used to specify that a package contains production data.
One or more site-specific name/value pairs can be assigned to an entire
package or to a selected package entry. Subscribers can use name/value
pairs to define name/value filters, which control the types of packages
that are delivered to them.
- named service
-
a SAS Foundation Service that is bound to the
service registry by name. Named services are defined by named service
bindings, which enable applications to locate a remote service based
on the name that is bound to the registry.
- named service binding
-
the method that is used to bind one of the SAS
Foundation Services to a service registry when the service has been
deployed remotely. Named service bindings enable applications to locate
a service by using the name that is bound to the registry.
- namespace
-
a URL that identifies an entry in a WebDAV package.
- naming hierarchy
-
a naming system that the Event Broker Service
uses to map events to an event configuration. The event names that
are included in the hierarchy are separated by periods, as in this
example: Animals, Animals.Dogs, Animals.Dogs.Retriever.
- object
-
an entity that can be manipulated by the commands
of a programming language. In object-oriented programming, an object
is a compilation of attributes (object elements) and behaviors (methods)
that describe an entity. Unlike simple data types that are single
pieces of information (e.g. int=10), objects are complex and must
be constructed.
- object class
-
a definition of a type of object that can be stored
in an LDAP directory. Each object class consists of a set of attributes
(for example, name and description) to which you can assign values
in order to define a specific instance of the object. The attributes
can be either mandatory or optional. The complete set of object classes
for a directory defines its schema.
- Object Management Group
-
a nonprofit industry consortium formed in April
1989 that develops standards for distributed objects. OMG standards
include the Common Object Request Broker Architecture (CORBA) and
the Internet Inter-ORB Protocol (IIOP). Short form: OMG.
- Object Request Broker
-
in object-oriented programming, a middle-tier
component that supports communication between clients and servers.
When a client invokes a method that is supported by an object server
class, the ORB finds an instance of the object server class, invokes
the requested method, and returns the results to the requesting client.
An ORB enables clients and servers to dynamically discover each other
and to communicate with each other across a network. Short form:
ORB.
- object spawner
-
a program that instantiates object servers that
are using an IOM bridge connection. The object spawner listens for
incoming client requests for IOM services. When the spawner receives
a request from a new client, it launches an instance of an IOM server
to fulfill the request. Depending on which incoming TCP/IP port the
request was made on, the spawner either invokes the administrator
interface or processes a request for a UUID (Universal Unique Identifier).
- OMG
-
See Object Management Group.
- ORB
-
See Object Request Broker.
- package
-
See SAS package file.
- package entry
-
in the Publishing Framework, an item within a
package.
- package entry MIME type filter
-
See MIME type filter.
- package entry type filter
-
in the Publishing Framework, a filter that specifies
which types of package entries to publish to a subscriber.
- package file
-
See SAS package file.
- package filter
-
specified criteria that are applied to data in
order to identify the subset of data for a subsequent operation, such
as continued processing.
- permanent package
-
a container for content that was produced by a
SAS program or by a third-party application, and that is written to
a specific location. Permanent packages remain in existence even after
the stored process completes execution and the client disconnects
from the server.
- permanent result package
-
See permanent package.
- permission
-
the type of access that a user or group has to
a resource. The permission defines what the user or group can do with
the resource. Examples of permissions are ReadMetadata and WriteMetadata.
- PFD
-
See process flow diagram.
- plug-in
-
a file that modifies, enhances, or extends the
capabilities of an application program. The application program must
be designed to accept plug-ins, and the plug-ins must meet design
criteria specified by the developers of the application program. In
SAS Management Console, a plug-in is a JAR file that is installed
in the SAS Management Console directory to provide a specific administrative
function. The plug-ins enable users to customize SAS Management Console
to include only the functions that are needed.
- pool
-
a group of server connections that can be shared
and reused by multiple client applications. A client-side pool consists
of one or more puddles.
- pooling
-
the act or process of creating a pool.
- portal
-
a Web application that enables users to access
Web sites, data, documents, applications, and other digital content
from a single, easily accessible user interface. A portal's personalization
features enable each user to configure and organize the interface
to meet individual or role-based needs.
- portlet
-
a Web component that is managed by a Web application
and that is aggregated with other portlets to form a page within the
application. Portlets can process requests from the user and generate
dynamic content.
- Process Editor
-
a utility that is used for configuring process
flows for the Event Broker Service.
- process flow
-
programming logic that is executed in response
to an event message and that in some cases returns a result.
- process flow diagram
-
a graphical sequence of interconnected symbols,
that represent an ordered set of steps or tasks, that when combined
form a process designed to yield an analytical result.
- process node
-
in a process flow diagram, a node that represents
run-time processing that is performed on messages.
- prompt
-
a parameter that enables a user to specify one
or more values, which can be used by consumers such as applications,
stored processes, and reports.
- publication channel
-
an information repository that has been established
using the SAS Publishing Framework and that can be used to publish
information to users and applications.
- publish
-
to deliver electronic information, such as files
and system-generated events, to one or more destinations. These destinations
can include e-mail addresses, message queues, publication channels
and subscribers, WebDAV-compliant servers, and archive locations.
- publisher
-
any person, SAS program, or application that uses
the Publishing Framework to distribute information.
- Publishing Framework
-
a component of SAS Integration Technologies that
enables both users and applications to publish SAS files (including
data sets, catalogs, and database views), other digital content, and
system- generated events to a variety of destinations. The Publishing
Framework also provides tools that enable both users and applications
to receive and process published information.
- puddle
-
a group of servers that are started and run using
the same login credentials. Each puddle can also allow a group of
clients to access the servers.
- queue
-
See message queue.
- queue manager
-
an application that enables programs to send messages
to and receive messages from message queues.
- remote method invocation
-
a Java programming feature that provides for remote
communication between programs by enabling an object that is running
in one Java Virtual Machine (JVM) to invoke methods on an object that
is running in another JVM, possibly on a different host. Short form:
RMI.
- remote service deployment
-
a service deployment that supports shared access
to a set of SAS Foundation Services that are deployed within a single
Java Virtual Machine (JVM), but which are available to other JVM processes.
Applications use the remote service deployment to deploy and access
remote foundation services.
- repository
-
a storage location for data, metadata, or programs.
- result type
-
the kind of output that is produced by a stored
process. Result types include none, streaming, permanent package,
and transient package.
- RMI
-
See remote method invocation.
- SAS Application Server
-
a logical entity that represents the SAS server
tier, which in turn comprises servers that execute code for particular
tasks and metadata objects.
- SAS BI Web service
-
a Web service that adheres to the XML for Analysis
(XMLA) specification for executing SAS Stored Processes.
- SAS Foundation Services
-
a set of core infrastructure services that programmers
can use in developing distributed applications that are integrated
with the SAS platform. These services provide basic underlying functions
that are common to many applications. These functions include making
client connections to SAS application servers, dynamic service discovery,
user authentication, profile management, session context management,
metadata and content repository access, activity logging, event management,
information publishing, and stored process execution.
- SAS IOM workspace
-
in the IOM object hierarchy for a SAS Workspace
Server, an object that represents a single session in SAS.
- SAS log
-
a file that contains a record of the SAS statements
that you enter, as well as messages about the execution of your program.
- SAS Management Console
-
a Java application that provides a single user
interface for performing SAS administrative tasks.
- SAS Metadata Repository
-
a container for metadata that is managed by the
SAS Metadata Server.
- SAS Metadata Server
-
a multi-user server that enables users to read
metadata from or write metadata to one or more SAS Metadata Repositories.
- SAS OLAP Server
-
a SAS server that provides access to multidimensional
data. The data is queried using the multidimensional expressions (MDX)
language.
- SAS Open Metadata Architecture
-
a general-purpose metadata management facility
that provides metadata services to SAS applications. The SAS Open
Metadata Architecture enables applications to exchange metadata, which
makes it easier for these applications to work together.
- SAS package file
-
a container for data that has been generated or
collected for delivery to consumers by the SAS Publishing Framework.
Packages can contain SAS files, binary files, HTML files, URLs, text
files, viewer files, and metadata.
- SAS publication channel
-
See publication channel.
- SAS Stored Process
-
a SAS program that is stored on a server and defined
in metadata, and which can be executed by client applications. Short
form: stored process.
- SAS Stored Process Server
-
a SAS IOM server that is launched in order to
fulfill client requests for SAS Stored Processes.
- SAS Stored Process Web Application
-
a Web application that enables you to execute
stored processes and have the results returned to a Web browser.
- SAS Workspace Server
-
a SAS IOM server that is launched in order to
fulfill client requests for IOM workspaces.
- server
-
software that provides either resources or services
to requesting clients, possibly over a network.
- service
-
one or more application components that an authorized
user or application can call at any time to provide results that conform
to a published specification. For example, network services transmit
data or provide conversion of data in a network, database services
provide for the storage and retrieval of data in a database, and Web
services interact with each other on the World Wide Web.
- service configuration
-
a set of values that can be customized for a particular
service in SAS Foundation Services. By editing a service configuration,
you can override the default configuration for the foundation service.
- service deployment
-
a collection of SAS Foundation Services that specifies
the data that is necessary in order to instantiate the services, as
well as dependencies upon other services. Applications query a metadata
source (a SAS Metadata Server or an XML file) to obtain the service
deployment configuration in order to deploy and access foundation
services.
- service deployment group
-
a group of SAS Foundation Services within a service
deployment. Service deployment groups are used to organize foundation
services within a deployment hierarchy. Applications can use service
deployment groups in order to deploy only specific groups of foundation
services.
- service interface
-
an interface that defines the services that one
of the SAS Foundation Services is providing to its users. Each of
the foundation services implements one or more service interfaces.
- service loader
-
a utility that can be invoked by client applications
that use SAS Foundation Services. The service loader enables client
applications to (1) instantiate services and register them with a
local Discovery Service or (2) locate a remote Discovery Service that
has been deployed by a server application and register it with a local
Discovery Service.
- service registry
-
a searchable registry of service descriptions
that is used to register named service bindings. Applications use
the service registry to locate (via named service bindings) SAS Foundation
Services that have been deployed remotely.
- servlet
-
a Java program that runs on a Web server. Servlets
are a complementary technology to applets, which run in Web browsers.
Unlike applet code, servlet code does not have to be downloaded to
a Web browser. Instead, servlets send HTML or other appropriate content
back to a browser or to another type of Web-based client application.
- servlet container
-
the component of a Web server that manages the
lifecycle of servlets, mapping a URL to a particular servlet and ensuring
that the URL requester has the correct access rights. All servlet
containers must support HTTP as a protocol for requests and responses,
but they can also support additional protocols such as HTTPS.
- session context
-
a context that serves as a control structure for
maintaining state within a bound session. 'State' includes information
about the latest status, condition, or content of a process or transaction.
Session Services, User Services, and Logging Services use the session
context to facilitate resource management and to pass information
among services.
- Session Service
-
one of the SAS Foundation Services. This service
enables applications to (1) create a session context, (2) bind objects
to a session context, (3) use the session context as a container for
passing multiple contexts or for passing other services (such as User
Services and Logging Services), and (4) notify bound objects when
they are removed from the session context or when the session context
is destroyed, so that objects can perform any necessary cleanup.
- Simple Object Access Protocol
-
See SOAP.
- single sign-on
-
an authentication model that enables users to
access a variety of computing resources without being repeatedly prompted
for their user IDs and passwords. For example, single sign-on can
enable a user to access SAS servers that run on different platforms
without interactively providing the user's ID and password for each
platform. Single sign-on can also enable someone who is using one
application to launch other applications based on the authentication
that was performed when the user initially logged on.
- smart object
-
an object that acts as a wrapper for metadata
entries in order to hide details that pertain to a specific type of
metadata repository. The Information Service uses smart objects to
specify implementation details for specific types of repositories.
- SOAP
-
a standard, Web-based protocol that enables applications
written in various programming languages to communicate. Short form:
SOAP.
- source code repository
-
the location on the application server that contains
stored process source code.
- source file
-
the SAS program that contains the stored process
source code.
- spawner
-
See object spawner.
- SPK
-
See SAS package file.
- SSO
-
See single sign-on.
- stored process
-
See SAS Stored Process.
- Stored Process Service
-
one of the SAS Foundation Services. This Java-based
interface enables applications to synchronously or asynchronously
execute a stored process. Execution can include accessing SAS data
sources or external files and creating new data sets, files, or other
types of output that are supported by SAS. Clients of the service
can pass input parameters and data streams to an executing stored
process and can receive output streams or result packages from the
stored process.
- streaming result
-
a type of output that is generated by a stored
process. In a streaming result, the content that the stored process
generates is delivered to the client through an output stream. The
output stream is generally accessible to the stored process as the
_WEBOUT fileref.
- Struts
-
a public-domain framework for building Web applications.
The Information Delivery Portal and the Web Infrastructure Platform
(provided with SAS Integration Technologies) use this framework. Struts
is based on standard technologies such as Java servlets, JavaBeans,
resource bundles, and Extensible Markup Language (XML). It supports
the Model 2 variation of the Model-View-Controller (MVC) design paradigm.
Struts is part of the Apache Jakarta Project, which is sponsored by
the Apache Software Foundation.
- stub
-
a Java class that acts as an interface for a remote
software object. Stubs are instantiated on the client. The client
passes method calls to the stubs, and the stubs then repackage the
method calls for delivery through an Object Request Broker (ORB) to
remote software objects. In many distributed object systems, stubs
are referred to as proxies.
- subscribe
-
to sign up to receive electronic content that
is published to a SAS publication channel.
- subscriber
-
a recipient of information that is published to
a SAS publication channel.
- subscriber profile
-
a set of personal preferences for subscribing
to SAS publication channels. A subscriber profile includes the method
by which you want published information to be delivered and filtering
criteria (in the form of name/value pairs) to limit the types of information
that you receive. You can create multiple subscriber profiles if you
want to subscribe to channels in different ways.
- subscription
-
the association of a subscriber with a group or
a channel.
- thread
-
a single path of execution of a process that runs
on a core on a CPU.
- transient package
-
a container for content that was produced by a
SAS program or by a third-party application for immediate use, and
that is not saved. After the client program disconnects from the server,
the transient package disappears.
- transport
-
(1) in SAS Foundation Services, a communication
protocol through which the Event Broker Service can listen for, receive,
and respond to external events. Each transport that is specified in
the service configuration runs in its own thread of execution. (2)
In the Publishing Framework, this term is a short form of the term
'delivery transport.'
- Unicode Transformation Format 8
-
See UTF-8.
- Uniform Resource Identifier
-
See URI.
- Uniform Resource Locator
-
See URL.
- URI
-
a string that identifies resources such as files,
images, and services on the World Wide Web. A URL is a type of URI.
Short form: URI.
- URL
-
a character string that is used by a Web browser
or other software application to access or identify a resource on
the Internet or on an intranet. The resource could be a Web page,
an electronic image file, an audio file, a JavaServer page, or any
other type of electronic object. The full form of a URL specifies
which communications protocol to use for accessing the resource, as
well as the directory path and filename of the resource. Short form:
URL.
- user context
-
a set of information about the user who is associated
with an active session. The user context contains information such
as the user's identity, profile, and active repository connections.
- User Service
-
one of the SAS Foundation Services. This service
enables applications to (1) create, locate, maintain, and aggregate
information about users of the SAS Foundation Services, (2) store
and retrieve user context objects for sharing between applications,
(3) manage and access user profiles, and (4) access group profiles.
- UTF-8
-
a method for converting 16-bit Unicode characters
to 8-bit characters. This format supports all of the world's languages,
including those that use non-Latin 1 characters. Short form: UTF-8.
- viewer
-
in the Publishing Framework, a custom-written
template that contains HTML tags for formatting package content for
view-only delivery transports such as e-mail.
- Web server
-
a computer program that delivers (serves) content,
such as web pages, over the World Wide Web. It can also refer to the
computer or virtual machine that runs the program.
- Web service
-
a programming interface that enables distributed
applications to communicate even if the applications are written in
different programming languages or are running on different operating
systems.
- Web Service Description Language file
-
See WSDL file.
- Web-distributed authoring and versioning
-
See WebDAV.
- WebDAV
-
a set of extensions to the HTTP protocol that
enables users to collaboratively edit and manage files on remote Web
servers. Short form: WebDAV.
- WebDAV content portlet
-
a portlet that displays the contents of an HTML
fragment that is stored in the portal's WebDAV repository.
- WebDAV repository
-
a collection of files that are stored on a Web
server so that authorized users can access them.
- wizard
-
an interactive utility program that consists of
a series of dialog boxes, windows, or pages. Users supply information
in each dialog box, window, or page, and the wizard uses that information
to perform a task.
- workspace
-
See SAS IOM workspace.
- WSDL file
-
a file that is obtained from a Web service. The
WSDL describes the methods that are available to the client application,
the endpoint (where to call the Web service), and the format of the
XML that is required in order to call the Web service. Short form:
WSDL file.
- XML
-
a markup language that structures information
by tagging it for content, meaning, or use. Structured information
contains both content (for example, words or numbers) and an indication
of what role the content plays. For example, content in a section
heading has a different meaning from content in a database table.
Short form: XML.
- XML for Analysis
-
See XMLA.
- XMLA
-
a standard specification developed by several
companies for use as a Web service interface to access online analytical
processing (OLAP) functions and data-mining functions. Short form:
XMLA.
Copyright © SAS Institute Inc. All rights reserved.