SAS 9 Integration Technologies

Version 9 Glossary

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

access control entry (ACE): 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.
access control template (ACT): 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.
ACE: See access control entry (ACE).
ACI rule: a program statement that defines users' access rights to a specific object on an LDAP server. Any number of ACI rules can be entered for an object. Each ACI rule specifies: 1) whether permission is allowed or denied, 2) the specific rights that are allowed or denied (read, write, add, delete, search, compare, and/or self-write), 3) the distinguished names (DNs) of the users or groups of users to whom the rule applies.
ACT: See access control template (ACT).
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. See also JMS (Java Message Service), Event Broker Service.
administrative user: a special user of a metadata server who can create and delete user definitions and logins. An administrative user can also perform administrative tasks such as starting, stopping, pausing, and refreshing the metadata server. Unlike an unrestricted user, an administrative user does not have unrestricted access to the metadata. You are an administrative user if your user ID is listed in the adminUsers.txt file or if you connect to the metadata server using the same user ID that was used to start the metadata server.
alert: an automatic notification of an electronic event that is of interest to the recipient.
archive: in the Publishing Framework, a result set package that is compressed and saved to a directory. The archive contains the contents of a package, plus metadata that is necessary for extracting the contents.
archive path: in the Publishing Framework, the complete path of the location to which a user or program can publish an archive package.
asynchronous logging: a process that enables log messages to be queued within and delivered from a thread other than the main application thread. See also Logging Service.
authentication: the process of verifying the identity of a person or process within the guidelines of a specific authorization policy.
authentication domain: a set of computing resources that use the same authentication process. An individual uses the same user ID and password for all of the resources in a particular authentication domain. Authentication domains provide logical groupings for resources and logins in a metadata repository. For example, when an application needs to locate credentials that enable a particular user to access a particular server, the application searches the metadata for logins that are associated with the authentication domain in which the target server is registered.
authentication provider: a software component that is used for identifying and authenticating users. For example, Windows NT and LDAP both 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: a mode of computer processing that does not require user interaction and which allows users to perform multiple tasks on the computer concurrently. In the SAS Information Delivery Portal, some SAS stored processes run in the background so that you can perform other portal tasks during processing.
banner: a colored, rectangular area that appears at the top of some Web pages. Banners typically contain titles and navigation links.
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.
base path: the location, relative to a WebDAV server's URL, in which packages are published and files are stored.
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 placeholder that stores either the address and name of a document or the address of a location within a document so that you can quickly and easily return to that document or location later.
bookmarks portlet: a portlet that displays bookmarks that you have created. From the bookmarks portlet, you can retrieve bookmarked items, publish them to other users, create new portlets, and remove bookmarks that you no longer need.
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. See also logging context, Logging Service.
channel: a virtual communication path for distributing information. In SAS, a channel is identified with a particular topic (just as a television channel is identified with a particular radio frequency). 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. See also publish, subscribe.
client: a computer or application that requests services, data, or other resources from a server. See also server.
cluster: a group of machines that participate in load balancing. Each machine in the cluster runs an object spawner that handles client requests for connections.
collection path: the location to which a package is published. The collection path is relative to the base path, which is relative to the WebDAV server's URL.
collection portlet: a portlet that contains a list of portal content items. The items can be of any content type or combination of types.
COM (Component Object Model): an object-oriented programming model that defines how software components interact within a single process or between processes. For example, COM includes standard rules of communication that enable a user-interface object to be dragged and dropped from one application window to another.
COM/DCOM client: a program that uses the Microsoft Component Object Model (COM) or Distributed Component Object Model (DCOM) to make requests to a server. COM/DCOM clients can be written in Visual Basic, C++, Perl, or other programming languages in the Windows environment. See also COM (Component Object Model), DCOM (Distributed Component Object Model).
component: a self-contained, reusable programming object that provides some type of service to other components in an object-oriented programming environment.
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. See also 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. See also SAS Foundation Services, 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 administrator: See group content administrator.
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. See also MIME (Multipurpose Internet Mail Extensions).
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 (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.
custom portlet: a portlet in the SAS Information Delivery Portal that does not fit in any of the portal's standard portlet categories (collection, navigation, bookmarks, and alert). Some custom portlets simply display data, text, or graphics, and other custom portlets have interactive features.
custom repository: in the SAS Open Metadata Architecture, a metadata repository that must be dependent on a foundation repository or custom repository, thus allowing access to metadata definitions in the repository or repositories on which it depends. A custom repository is used to specify resources that are unique to a particular data collection. For example, a custom repository could define sources and targets that are unique to a particular data warehouse. The custom repository would access user definitions, group definitions, and most server metadata from the foundation repository. See also foundation repository, project repository.
DCOM (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. See also component, COM (Component Object Model).
default access control template: the access control template (ACT) that controls access to a particular repository and to resources for which definitive access controls are not specified. You can designate one default ACT for each metadata repository. The default ACT is also called the repository ACT.
default page: a page that is automatically added to each user's personal portal. You can remove a default page from your personal portal if you do not need it.
delivery method: another term for delivery transport. See delivery transport.
delivery transport: in the Publishing Framework, the method of delivering a package to the consumer. Supported transports include e-mail, message queue, and WebDAV. Although not a true transport, a channel also functions as a delivery mechanism. See also e-mail, message queue, WebDAV (Web Distributed Authoring and Versioning), channel.
directory information tree (DIT): the entries that an LDAP directory server contains. These entries are stored in a hierarchical, tree-like structure.
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, optionally, 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. See also SAS Foundation Services.
distinguished name (DN): 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.
DIT: See directory information tree (DIT).
DN: See distinguished name (DN).
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". See also authentication domain.
dynamic listener: an application that has registered itself with an Event Broker Service in order to receive events at run time. See also Event Broker Service.
e-mail: in the Publishing Framework, a common method of delivering a result set package to recipients whose identities are known to the publisher. See also delivery transport.
encryption: the act or process of converting data to a form that only the intended recipient can read or use.
entry: a set of name/value pairs that describe a resource that is defined on an LDAP directory server. See also name/value pair.
entry filter: See package entry type filter, MIME 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. See also Event Broker Service, XML (Extensible Markup Language).
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. See also SAS Foundation Services, event.
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. See also Event Broker Service.
factory: an object that controls the creation of other objects, access to other objects, or both. See also Connection Factory.
filter: in the Publishing Framework, a named set of criteria that are used for selecting either a result set package or specific package entries for a subsequent operation. Filters are useful in the following contexts: channel subscription properties, viewer file processing, stored processes, and LDAP directory searches. For example, a channel subscriber can define a name/value filter that controls the types of packages that he or she receives. See also name/value filter, package entry type filter, MIME type filter.
foundation repository: in the SAS Open Metadata Architecture, a metadata repository that is used to specify metadata for global resources that can be shared by other repositories. For example, a foundation repository is used to store metadata that defines users and groups on the metadata server. Only one foundation repository should be defined on a metadata server. See also custom repository, project repository.
foundation services: See SAS Foundation Services.
global resource: a widely used resource, such as a server that is used to access many tables in a data warehouse. See also resource.
group: in the Publishing Framework, a collection of subscribers. When a group is subscribed to a channel, each member of the group who has a defined subscriber entry in the Publishing Framework will receive the information that is published to that channel. Only metadata administrators have the authority to add members or to remove members from a group.
group content: content that a group of portal users can access. Users who are designated as group content administrators can use the SAS Information Delivery portal's Share option to convert their personal content to group content. Group content can be edited and deleted only by the group content administrator who created it.
group content administrator: a portal user who is authorized to share pages, portlets, and other portal content items with all portal users or with other users in a group. After an item is shared, only the group content administrator can edit or delete the item.
group page: a page that has been shared with a particular group of portal users. The label Shared, followed by the name of the group, appears in the upper right corner of group pages.
HTML fragment: an HTML file that does not include opening and closing HTML tags, HEAD tags, or BODY tags and which can be displayed successfully in the cell of an HTML table.
HTTP (HyperText Transfer Protocol): 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.
identity: See metadata identity.
IFRAME: See inline frame (IFRAME).
inbound login: a login that is used to determine your metadata identity. The login is inbound to a SAS Metadata Server. A login that functions only as an inbound login does not need to include a password or to specify an authentication domain.
information map: a collection of data items and filters that describes and provides a business-relevant view of physical data. Users of query and reporting applications such as SAS Web Report Studio can easily build business reports by using information maps as the building blocks for their reports.
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). See also SAS Foundation Services.
inline frame (IFRAME): a browser feature that enables an HTML page to be displayed within its own rectangle anywhere on another HTML page. Inline frames are created by using the HTML IFRAME tag. When necessary, inline frames contain horizontal and vertical scrollbars to enable users to view all of the page's contents within the frame. See also URL display portlet.
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: See IOM (Integrated Object Model).
Integrated Object Model server: See IOM server.
IOM (Integrated Object Model): a set of object-based interfaces to features or services that are provided by Base SAS software. IOM enables application developers to use industry-standard programming languages, programming tools, and communication protocols to develop client programs that access these services on IOM servers.
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 OS/390 and UNIX that do not support the COM or DCOM specifications. See also IOM (Integrated Object Model), COM (Component Object Model), DCOM (Distributed Component Object Model).
IOM bridge for Java: a software component of SAS Integration Technologies that enables Java clients to access IOM servers.
IOM Direct Interface Stored Process: a SAS program that is stored on a server and which can be executed as requested by client applications. IOM Direct Interface Stored Processes are a limited form of stored processes that run on a SAS Workspace Server and that produce result set packages.
IOM server: a SAS object server that is launched in order to fulfill client requests for IOM services. See also IOM (Integrated Object Model).
Java Development Kit: See JDK (Java Development Kit).
Java Message Service: See JMS (Java Message Service).
Java Naming and Directory Interface: See JNDI (Java Naming and Directory Interface).
Java RMI: See RMI (remote method invocation).
Java Virtual Machine: See JVM (Java Virtual Machine).
JavaServer page: See JSP (JavaServer page).
JDK (Java Development Kit): a software development environment that is available from Sun Microsystems, Inc. The JDK includes a Java Runtime Environment (JRE), a compiler, a debugger, and other tools for developing Java applets and applications.
JMS (Java Message Service): 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.
JNDI (Java Naming and Directory Interface): 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).
JSP (JavaServer page): a type of servlet that enables users to create Java classes through HTML.
JVM (Java Virtual Machine): 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 Sun Microsystems, as well as with most Web browsers.
keyword: in the Stored Process Manager, a descriptive word or phrase that can be stored in the metadata for one or more stored processes and which can subsequently be used in a filtered search. For example, 'XMLA Web Service' is a reserved keyword that is used to identify and locate stored processes that can be used as Web services.
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. See also Logging Service.
LDAP (Lightweight Directory Access Protocol): 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.
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 (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.
Lightweight Directory Access Protocol: See LDAP (Lightweight Directory Access Protocol).
link: (1) a portal content item that can be accessed using a URL; (2) a character string in a portal that you can click in order to initiate an action.
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 portlet: a portlet that (1) is deployed within the same Web application that displays the portlet, (2) executes inside the portlet container, and (3) consumes the computing resources (for example, CPU, memory, and disk storage) of the server machine on which the portal Web application runs. See also remote portlet.
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). See also service deployment.
locale: a value that reflects the language, local conventions, and culture for a geographic region. Local conventions can include specific formatting rules for dates, times, and numbers, and a currency symbol for the country or region. Collating sequences, paper sizes, and conventions for postal addresses and telephone numbers are also typically specified for each locale. Some examples of locale values are French_Canada, Portuguese_Brazil, and Chinese_Singapore.
localhost: a 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.
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. See also Logging Service.
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. See also SAS Foundation Services.
logical name: a unique name that can be assigned to related resources in order to manage the resources as a group.
logical server: in the SAS Metadata 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 combination of a user ID, a password, and an authentication domain. Each login provides access to a particular set of computing resources. In a SAS metadata environment, each login can belong to only one individual or group. However, each individual or group can own multiple logins. A login can function as an inbound login, an outbound login, or as both an inbound login and an outbound login. See also inbound login, outbound login.
message node: in a process flow diagram, a node that encapsulates inputs and outputs to one or more process nodes. See also process node, process flow.
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. See also delivery transport.
message queue polling: a program that runs in the object spawner, monitors message queues, and distributes message queue processing across SAS processes.
metadata: a description or definition of data or information.
metadata administrator: a person who defines the metadata for servers, metadata repositories, users, and other resources.
metadata configuration file: a file that enables users to specify which SAS metadata server they want to connect to by default. The connection to the metadata server enables users to access and run stored processes and to access SAS data sources on remote computers.
metadata identity: a metadata object that represents an individual user or a group of users in a SAS metadata environment. Each individual and group that accesses secured resources on a SAS Metadata Server should have a unique metadata identity within that server.
metadata profile: a client-side definition of where a metadata server is located. The definition includes a host name, a port number, and a list of one or more metadata repositories. In addition, the metadata profile can contain a user's login information and instructions for connecting to the metadata server automatically.
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 provides metadata management services to one or more client applications. A SAS Metadata Server is an example.
middle tier: in a SAS business intelligence system, the tier in which J2EE Web applications and J2EE enterprise applications execute.
MIME (Multipurpose Internet Mail Extensions): a method of registering content types and their associated actions with mechanisms for actions such as retrieval and display. See also content type.
MIME type filter: in the Publishing Framework, a filter that specifies which file entries of a specific MIME type to include in result set packages that are published to a subscriber. See also MIME (Multipurpose Internet Mail Extensions).
multi-user server: a server that enables multiple clients to use the same SAS process at the same time. For example, the SAS Stored Process Server, SAS OLAP Server, and SAS Metadata Server are all multi-user servers. See also single-user server.
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. See also name/value pair, filter.
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. See also filter.
named service: a SAS Foundation Service that is bound to the service registry by name. Named services are defined by named service bindings. Named service bindings enable applications to locate a service based on the name that is bound to the registry. See also bind, named service binding, service 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. See also bind, named service, service 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. See also event, Event Broker Service.
navigation portlet: a portlet that displays content items in a hierarchical (tree) arrangement of folders and subfolders. Examples of this content might include stored processes, information maps, files that are stored in WebDAV repositories, and SAS reports.
object: in object-oriented programming, an instantiation or specific representation of a class.
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 (OMG): 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).
Object Request Broker (ORB): 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.
object server: another term for IOM server. See IOM server.
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 (Object Management Group): See Object Management Group (OMG).
ORB: See Object Request Broker (ORB).
outbound login: a login that applications can retrieve from a SAS Metadata Server and send to other systems that need to verify a user's identity. The login is outbound from the SAS Metadata Server to the other systems. An outbound login must specify an authentication domain and must include credentials that are appropriate for the systems to which the login provides access.
override: in the Publishing Framework, a subscription property that is assigned to a single channel and that is used in place of a default property that is otherwise assigned to channel subscriptions.
package: a container for data that has been generated or collected for delivery to consumers by the SAS Publishing Framework. Packages can contain SAS files (SAS catalogs; SAS data sets; various types of SAS databases, including cubes; and SAS SQL views), binary files (such as Excel, GIF, JPG, PDF, PowerPoint and Word files), HTML files (including ODS output), reference strings (such as URLs), text files (such as SAS programs), and viewer files (HTML templates that format SAS file items for viewing). Packages also contain metadata such as a description, an abstract, and user-specified name/value pairs.
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. See also filter.
package filter: See filter.
PAR (portlet archive) file: an archive (zipped) file with the suffix '.par' which includes all of the elements needed to deploy a new portlet (or group of portlets) into the SAS Information Delivery Portal, or into other applications that have been developed with the Web Infrastructure Kit. The elements in a PAR file can include a portlet deployment descriptor, JavaServer Pages (JSPs), custom Java classes, and associated resources such as images, resource bundles, HTML files, and style sheets. See also portlet.
parameter: a data item that is passed to a routine.
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. See also transient package.
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.
personal content: content that a portal user creates for his or her own use. As a portal user, you can create your own pages, your own collection portlets, and your own links. After you create these items, you can access them from the portal, edit them, remove them from your personal portal, use the Search tool to find them, or delete them permanently. Other portal users cannot access your personal content.
personal portal: a portal that has been personalized for or by a specific user.
personalization: the process of customizing a Web application or Web page to meet the needs and preferences of an individual user.
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 pool consists of one or more puddles. See also puddle.
pooling: the act or process of creating a pool. See 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. See also portlet.
portlet: a Web component that is managed by a Web application and which is aggregated with other portlets to form a page within the application. A portlet processes requests from the user and generates dynamic content.
portlet archive (PAR) file: See PAR (portlet archive) file.
portlet container: on a Web server, the execution environment in which portlets execute (in the same way that servlets execute in a servlet container). This environment enables session information and state information to be maintained and shared among portlet actions and across HTTP requests. See also portlet.
portlet deployment descriptor: an XML file that specifies the actions of a portlet, as well as the portlet's initialization, path, access control, and search information. See also PAR (portlet archive) file.
predefined page: a portal page that has already been created. Predefined pages might include public pages, which are available to all users, pages that have been shared with a group of users, and pages that you created.
predefined portlet: a portlet that has already been created. Predefined portlets might include public portlets, which are available to all users, portlets that have been shared with a group of users, and collection portlets that you created.
Process Editor: a utility that is used for configuring process flows for the Event Broker Service. See also Event Broker Service, process flow.
process flow: programming logic that is executed in response to an event message and that in some cases returns a result. See also Event Broker Service, event.
process flow diagram (PFD): in SAS Foundation Services, a diagram in the Process Editor that illustrates the order in which process nodes and message nodes are to be executed within a particular process flow. See also Event Broker Service, process flow, process node, message node.
process node: in a process flow diagram, a node that represents run-time processing that is performed on messages. See also process flow diagram, process flow, message node.
project repository: a repository that must be dependent on a foundation repository or custom repository that will be managed by the Change Management Facility. A project repository is used to isolate changes from a foundation repository or from a custom repository. The project repository enables metadata programmers to check out metadata from a foundation repository or custom repository so that the metadata can be modified and tested in a separate area. Project repositories provide a development/testing environment for customers who want to implement a formal change management scheme. See also foundation repository, custom repository.
public content: content that all SAS Information Delivery portal users can access. Users who are designated as content administrators can use the SAS Information Delivery portal's Share tool to convert their personal content to public content. Public content can be edited and deleted only by the content administrator who created it.
Public Kiosk: a public page that is displayed when a user starts the SAS Information Delivery Portal but has not yet logged on.
public page: a page that all SAS Information Delivery portal users are authorized to access.
publication channel: an information repository that has been established using the SAS Publishing Framework and which can be used to publish information to users and applications. See also publish.
publish: to deliver electronic information, such as SAS files (including SAS data sets, SAS catalogs, and SAS data views), other digital content, 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. See also pool.
queue: See message queue.
remote method invocation: See RMI (remote method invocation).
remote portlet: a portlet that executes outside of the portal container. Remote portlets enable data from external applications to be incorporated into a Web application. When a user interacts with a remote portlet, the remote portlet appears to be the same as a local portlet. See also local portlet, portlet.
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. See also service deployment.
report: See SAS report.
repository: a location in which data, metadata, or programs are stored, organized, and maintained, and which is accessible to users either directly or through a network. See also metadata repository, SAS Metadata Repository, WebDAV repository.
resource: any object that is registered in a metadata repository. For example, a resource can be a server, a stored process, or a login.
result package: See package.
result type: the kind of output that is produced by a SAS Stored Process. Result types include none, streaming, permanent result package, and transient result package.
RMI (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. See also JVM (Java Virtual Machine).
round-robin: a scheduling algorithm that iterates through all available choices before beginning again with the first choice. For example, if there are three choices, A, B, and C, the scheduler would process A the first time, B the second, and C the third. The process would then repeat, starting with A.
SAS application server: a server that provides SAS services to a client. In the SAS Open Metadata Architecture, the metadata for a SAS application server specifies one or more server components that provide SAS services to a client. See also component.
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. See also service.
SAS IOM object: in the IOM object hierarchy, a root object that represents a single session within SAS. In function, a SAS IOM object is similar to the Application object, which is available in many Microsoft products.
SAS IOM workspace: See workspace.
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: one or more files that store metadata about application elements. Users connect to a SAS Metadata Server and use the SAS Open Metadata Interface to read metadata from or write metadata to one or more SAS Metadata Repositories. The metadata types in a SAS Metadata Repository are defined by the SAS Metadata Model.
SAS Metadata Server: a multi-user server that enables users to read metadata from or write metadata to one or more SAS Metadata Repositories. The SAS Metadata Server uses the Integrated Object Model (IOM), which is provided with SAS Integration Technologies, to communicate with clients and with other servers.
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 report: a report that has been stored in the SAS Report Model format. A SAS report might be available for viewing in the portal if your organization has installed SAS Web Report Studio.
SAS Stored Process: a SAS program that is stored on a server and which can be executed as requested by client applications. SAS Stored Processes can be used with either a SAS Workspace Server or a SAS Stored Process Server.
SAS Stored Process Server: a SAS IOM server that is launched in order to fulfill client requests for SAS stored processes. See also IOM server.
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. See also IOM server, workspace.
schema: See directory schema.
server: a computer system that provides data or services to multiple users on a network. The term 'server' sometimes refers to the computer system's hardware and software, but it often refers only to the software that provides the data or services. In a network, users might log on to a file server (to store and retrieve data files), a print server (to use centrally located printers), or a database server (to query or update databases). In a client/server implementation, a server is a program that waits for and fulfills requests from client programs for data or services. The client programs might be running on the same computer or on other computers. See also service.
server administrator: a person who installs and maintains server hardware or software. See also metadata administrator.
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. See also SAS Foundation Services.
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. See also SAS Foundation Services.
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. See also SAS 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. See also service deployment.
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. See also SAS Foundation Services.
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. See also Discovery Service.
service name: (1) a SAS Foundation Service that is bound to the service registry by name. Service names (named services) are defined by named service bindings. Applications use the named service binding to locate the service based on the name that is bound to the service registry. (2) a TCP/IP port identifier. Service names are defined in the TCP/IP SERVICES file. See also bind.
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. See also named service, named service binding.
servlet: a Java program that runs on a Web server. Servlets can be considered 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: an execution environment for Java servlets that contains a Java Virtual Machine. The servlet container also provides other services for servlets and for the Web applications that those servlets are part of. For example, the servlet container converts HTTP requests that are sent by clients to Java objects that servlets can work with, and it converts the output of servlets to HTTP responses. An example of a popular servlet container is the Apache Tomcat server.
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. See also context, bind.
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. See also SAS Foundation Services, session context, bind.
Simple Object Access Protocol: See SOAP (Simple Object Access Protocol).
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.
single-user server: a server that provides access to a single user. For example, the SAS Workspace Server is a single-user server. See also multi-user server.
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. See also Information Service.
SOAP (Simple Object Access Protocol): a standard, Web-based protocol that enables applications written in various programming languages to communicate.
spawner configuration file: an LDIF file that contains the information needed to launch an object spawner. See also LDIF (LDAP Data Interchange Format).
stored process: a SAS program that is stored on a server and which can be executed as requested by client applications. There are two types of stored processes: IOM Direct Interface Stored Processes and SAS Stored Processes.
Stored Process Manager: a SAS Management Console plug-in that enables administrators to register and manage metadata for stored processes.
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. See also SAS Foundation Services.
streaming result: a type of SAS Stored Process result in which 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. See also result type.
Struts: a public-domain framework for building Web applications. The Information Delivery Portal and the Web Infrastructure Kit (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. See also Web Infrastructure Kit.
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.
Subscription Manager: a Java applet that enables subscribers to create and manage their own subscriptions.
syndication channel: a channel that provides syndicated, continuously updated Web content from a content provider.
system configuration file: a file that contains information for connecting to a metadata server.
theme: a collection of specifications (for example, colors, fonts, and font styles) and graphics that control the appearance of an application.
thread: a single path of execution of a process in a single CPU, or a basic unit of program execution in a thread-enabled operating system.
thread-enabled operating system: an operating system that can coordinate symmetric access by multiple CPUs to a shared main memory space. This coordinated access enables threads from the same process to share data very efficiently.
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. See also permanent package.
transient result package: See transient package.
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.' See also Event Broker Service, delivery transport.
trusted user: a special user of a metadata server who can acquire credentials on behalf of other users in a multi-tier server environment.
Uniform Resource Identifier (URI): See URI (Uniform Resource Identifier).
unrestricted user: a special user of a metadata server who can access all metadata on the server (except for passwords, which an unrestricted user can overwrite but cannot read). An unrestricted user can also perform administrative tasks such as starting, stopping, pausing, and refreshing the metadata server. You are an unrestricted user if your user ID is listed in the adminUsers.txt file and is preceded by an asterisk.
URI (Uniform Resource Identifier): a string that identifies resources such as files, images, and services on the World Wide Web. A URL is a type of URI. See also URL (Uniform Resource Locator).
URL (Uniform Resource Locator): 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.
URL display portlet: a portlet that accesses a specific URL and displays the returned information inside the portlet's borders. If the URL points to a complete HTML page, then the portlet can be set up to display the URL contents inside an inline frame (IFRAME). If the URL points to an HTML fragment that is allowed by the portal's security policies, then the portlet can display the URL contents without an IFRAME. See also portlet, inline frame (IFRAME), HTML fragment.
user: a person who is registered in a SAS metadata environment.
user configuration file: a file that contains security information for connecting to a metadata server. You can create separate user configuration files to enable users to access the same metadata server but still use their own logins.
user context: a context that contains 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. See also context.
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. See also SAS Foundation Services.
UTF-8 (Unicode Transformation Format 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.
UUID (Universal Unique Identifier): a 128-bit identifier that is comprised of date/time information and a host's IEEE node address. The 128 bits can represent 1x10**39 unique identifiers. UUIDs are also referred to as Global Unique Identifiers (GUIDs),
viewer: in the Publishing Framework, a custom-written template that contains HTML tags for formatting result set package content for view-only transports such as e-mail.
Web Distributed Authoring and Versioning: See WebDAV (Web Distributed Authoring and Versioning).
Web Infrastructure Kit: a set of infrastructure components that can be used to develop new portlets for the SAS Information Delivery Portal, to customize the SAS Information Delivery Portal, or to build new Web applications using portal technology. The kit includes common Java components as well as SAS Foundation Services. It is included with SAS Integration Technologies.
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.
WebDAV (Web Distributed Authoring and Versioning): an emerging industry standard, based on extensions to HTTP 1.1, that enables users to collaborate in the development of files and collections of files on remote Web servers. See also delivery transport.
WebDAV repository: a collection of files that are stored on a Web server so that authorized users can read and edit them. See also WebDAV (Web Distributed Authoring and Versioning).
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: in the IOM object hierarchy for a SAS workspace server, an object that represents a single session in SAS. See also IOM (Integrated Object Model).
WSDL (Web Service Description Language) 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.
XML (Extensible Markup Language): 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.
XML for Analysis (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.