SAS 9.2 Integration Technologies: Overviewsupport.sas.com/documentation/cdl/en/itechov/60309/... ·...

SAS® 9.2 Integration TechnologiesOverview

The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2009.SAS ® 9.2 Integration Technologies: Overview. Cary, NC: SAS Institute Inc.

SAS® 9.2 Integration Technologies: OverviewCopyright © 2009, SAS Institute Inc., Cary, NC, USAISBN 978-1-59994-851-5All rights reserved. Produced in the United States of America.For a hard-copy book: No part of this publication may be reproduced, stored in aretrieval system, or transmitted, in any form or by any means, electronic, mechanical,photocopying, or otherwise, without the prior written permission of the publisher, SASInstitute Inc.For a Web download or e-book: Your use of this publication shall be governed by theterms established by the vendor at the time you acquire this publication.U.S. Government Restricted Rights Notice. Use, duplication, or disclosure of thissoftware and related documentation by the U.S. government is subject to the Agreementwith SAS Institute and the restrictions set forth in FAR 52.227-19 Commercial ComputerSoftware-Restricted Rights (June 1987).SAS Institute Inc., SAS Campus Drive, Cary, North Carolina 27513.1st electronic book, February 20092nd electronic book, May 2010

1st printing, March 2009SAS® Publishing provides a complete selection of books and electronic products to helpcustomers use SAS software to its fullest potential. For more information about oure-books, e-learning products, CDs, and hard-copy books, visit the SAS Publishing Web siteat support.sas.com/publishing or call 1-800-727-3228.SAS® and all other SAS Institute Inc. product or service names are registered trademarksor trademarks of SAS Institute Inc. in the USA and other countries. ® indicates USAregistration.Other brand and product names are registered trademarks or trademarks of theirrespective companies.

Contents

What’s New v

Overview v

General Product Enhancements v

Documentation Enhancements vi

Chapter 1 � Overview of SAS Integration Technologies 1What is SAS Integration Technologies? 1

Accessibility Features of SAS Integration Technologies 1

What SAS Integration Technologies Includes 1

Support for SAS Open Metadata Architecture 2

Support for Industry Standards 3

Chapter 2 � Components of SAS Integration Technologies 5IOM Servers 5

Using IOM to Develop Applications 10

Foundation Services 13

Publishing Framework 14

Application Messaging 16

Stored Processes 17

SAS BI Web Services 18

Directory Services 19

SAS Web Infrastructure Platform 19

Glossary 21

Index 41

v

What’s New

OverviewNew features for SAS Integration Technologies in SAS 9.2 include a number of

general product enhancements and documentation enhancements.

General Product EnhancementsThe following enhancements have been added to SAS Integration Technologies:� SAS Stored Processes provides enhancements to the SAS Stored Process Web

Application and to stored process metadata, as well as several generalenhancements.

� SAS 9.2 BI Web Services provide generated Web services, as well as generalenhancements.

� The Publishing Framework provides enhancements to security and to the supportof the HTTPS protocol and IPV6 addresses.

� The following software components are obsolete:� Integration Technologies Administrator (IT Administrator)� SAS Publisher� SAS Subscription Manager

� The Lightweight Directory Access Portal (LDAP) is no longer supported as ametadata store for SAS applications. For example, using LDAP to configurepublication channels, Integrated Object Model (IOM) servers, and SAS InformationDelivery Portal is no longer supported. You must use the SAS Metadata Server.The SAS Metadata Server can still use LDAP as an authentication provider, andLDAP connection from SAS is still supported for data loading and extraction.

vi What’s New

Documentation EnhancementsThe following enhancements have been made to the SAS Integration Technologies

documentation:� The SAS Integration Technologies: Developer’s Guide has been divided into the

following books, which are available in the SAS online documentation, as well asin PDF form:

� SAS Stored Processes: Developer’s Guide

� SAS BI Web Services: Developer’s Guide� SAS Publishing Framework: Developer’s Guide

� Application Messaging with SAS� SAS Integration Technologies: Java Client Developer’s Guide� SAS Integration Technologies: Windows Client Developer’s Guide

� SAS Integration Technologies: Directory Services Reference

� The SAS Integration Technologies: Administrator’s Guide has been divided. SASStored Process and Publishing Framework topics have been incorporated into theSAS Stored Processes: Developer’s Guide and SAS Publishing Framework:Developer’s Guide, respectively. SAS Foundation Services topics are covered in theSAS Foundation Services: Administrator’s Guide.

� Information from the SAS Integration Technologies: Server Administrator’s Guidehas been incorporated into the SAS Intelligence Platform: Application ServerAdministration Guide.

� The SAS Integration Technologies: Administrator’s Guide (LDAP Version) has beendiscontinued.

1

C H A P T E R

1Overview of SAS IntegrationTechnologies

What is SAS Integration Technologies? 1Accessibility Features of SAS Integration Technologies 1

What SAS Integration Technologies Includes 1

Support for SAS Open Metadata Architecture 2

Support for Industry Standards 3

What is SAS Integration Technologies?SAS Integration Technologies, in combination with other SAS software and solutions,

enables you to make information delivery and decision support a part of the informationtechnology architecture for your enterprise.

SAS Integration Technologies provides you with software that enables you to build asecure client/server infrastructure on which to implement SAS distributed processingsolutions. With SAS Integration Technologies, you can integrate SAS with otherapplications in your enterprise; provide proactive delivery of information from SASthroughout the enterprise; extend the capabilities of SAS to meet your organization’sspecific needs; and develop your own distributed applications that leverage the analyticand reporting powers of SAS.

SAS Integration Technologies is part of the SAS Intelligence Platform. For anoverview of the SAS Intelligence Platform and the products it contains, see the SASIntelligence Platform: Overview.

Accessibility Features of SAS Integration TechnologiesThis product has not been tested for compliance with U.S. Section 508 standards. If

you have specific questions about the accessibility of SAS products, send them [email protected] or call SAS Technical Support.

What SAS Integration Technologies IncludesSAS Integration Technologies includes the following integration and system

development tools, which are based on a combination of industry-standard technologiesand technology developed by SAS:

� the Integrated Object Model (IOM), which provides distributed object interfaces toSAS software features. IOM enables you to use industry-standard languages,

2 Support for SAS Open Metadata Architecture � Chapter 1

programming tools, and communication protocols to develop client programs thataccess these services on IOM servers. The IOM Bridge communications protocolenables diverse clients to connect transparently to IOM servers on multipleplatforms.

� two types of IOM servers: the SAS Workspace Server, which surfaces the SASprogramming environment to calling clients through an application programminginterface (API); and the SAS Stored Process Server, which enables clients toexecute parameterized SAS programs without having to know the SAS language.

Note: Other types of IOM servers include the SAS Metadata Server, which isprovided with Foundation SAS, and the SAS OLAP Server, which is provided withSAS Intelligent Storage products. �

� SAS Foundation Services, which is a set of core infrastructure services that Javaprogrammers can use to write distributed applications that are integrated with theSAS platform. The services provide client connections to IOM servers, dynamicservice discovery, user authentication, profile management, session contextmanagement, metadata and content repository access, activity logging, eventmanagement, information publishing, and stored process execution.

� the Publishing Framework, which consists of SAS CALL routines and graphicaluser interfaces that enable you to publish information and events proactively byusing a subscription channel model.

� the Application Messaging interface, which provides three sets of CALL routinesthat enable you to incorporate messaging services into your SAS programs.

� SAS Stored Processes, which enable client applications to execute SAS programsthat are stored centrally on a server.

� SAS BI Web Services, which enable client applications to send XML requests andparameters in a SOAP envelope. Web services can discover and execute SASStored Processes.

� the SAS Web Infrastructure Platform, which enables you to develop Webapplications and components using portal technology.

� the Directory Services interface, which enables you to incorporate LDAP directoryservices functions into your SAS programs.

Support for SAS Open Metadata ArchitectureSAS Integration Technologies supports the SAS Open Metadata Architecture, which

is a metadata management facility that provides common metadata services to SASapplications. This architecture is required in order to do the following tasks:

� use the SAS Metadata Server to store configuration information for SASIntegration Technologies and other SAS products

� use SAS Management Console as a central interface to administer configurationand security information for SAS Integration Technologies and other SAS products

� use new security features for user registration, authentication, and authorization(access control)

� configure new types of IOM servers (SAS Metadata Servers, SAS Stored ProcessServers, and SAS OLAP Servers) in addition to SAS Workspace Servers

� use load balancing for workspace servers and spawners, as well as stored processservers and spawners

� operate stored processes on a stored process server to produce streaming outputfor use in Web applications

Overview of SAS Integration Technologies � Support for Industry Standards 3

� use the SAS Web Infrastructure Platform to create Web applications that useportal technology

� use SAS Foundation Services to implement Java applications that are integratedwith the SAS Intelligence Platform

� install and operate other SAS products that depend on the SAS IntelligencePlatform

For more information about the SAS Open Metadata Architecture, see the SASIntelligence Platform: System Administration Guide.

Support for Industry StandardsSAS Integration Technologies supports the following industry standard technologies,

allowing you to leverage your existing infrastructure investments and skill sets toprovide application interoperability:

� client development by using any programming environment that supports bindingsto the COM and DCOM or Java object model. The programming environmentsthat are supported include the following:

� Microsoft Visual Basic for Applications, VBScript, Visual C++ .NET, VisualBasic .NET, and Visual C# .NET

� any Java integrated development environment (IDE), including Eclipse, SunONE Studio, IBM VisualAge, Borland JBuilder, and SAS webAF (which ispart of SAS AppDev Studio)

� proprietary Windows programming environments such as Borland Delphi,Sybase PowerBuilder, and others

� asynchronous message queuing through the use of IBM WebSphere MQ (formerlycalled MQSeries), Microsoft MSMQ, and TIBCO Rendezvous.

� file management that uses Web-based Distributed Authoring and Versioning(WebDAV). The publish and subscribe features of SAS Integration Technologiescan access any WebDAV server. Two specific types of WebDAV servers aresupported for use by SAS business intelligence Web applications:

� Xythos Software’s WebFile Server (WFS) can be used to store content for theSAS Web Infrastructure Kit and the SAS Information Delivery Portal. It canalso be used to store reports that have been created with SAS Web ReportStudio. The SAS User Management Customization enables a Xythos WebFileServer to interact with the SAS Metadata Server for authorization andauthentication.

� Apache HTTP Server (with its WebDAV module enabled) can also be used tostore reports that have been created with SAS Web Report Studio.

� Web services development based on the XML for Analysis interface.� Web application development on Web servers that are compatible with the Java 2

platform.

5

C H A P T E R

2Components of SAS IntegrationTechnologies

IOM Servers 5Overview of IOM Servers 5

Configuring and Using IOM Servers 6

Connecting Clients to IOM Servers 8

Overview of Communication between Clients and IOM Servers 8

Windows Clients 9Java Clients 10

Using IOM to Develop Applications 10

IOM Scenario 10

Workspace Object Hierarchy 11

Foundation Services 13

Publishing Framework 14Overview of the Publishing Framework 14

Channel Definition 15

Subscription Management 15

Package Publishing 15

Package Retrieval and Viewing 16Event Publishing 16

Application Messaging 16

Overview of Application Messaging 16

WebSphere MQ Functional Interface 17

MSMQ Functional Interface 17Common Messaging Interface 17

Stored Processes 17

SAS BI Web Services 18

Directory Services 19

SAS Web Infrastructure Platform 19

IOM Servers

Overview of IOM ServersThe Integrated Object Model (IOM) in SAS Integration Technologies provides

distributed object interfaces to SAS software features. To call these interfaces, clientscan use industry-standard languages, programming tools, and communication protocols.The interfaces are built into SAS and are available to clients whenever SAS is executedas an object server.

6 Configuring and Using IOM Servers � Chapter 2

An IOM server is an object server that is launched in order to fulfill client requestsfor IOM services. There are four types of IOM servers:

SAS WorkspaceServer

is provided with SAS Integration Technologies and is accessedthrough the IOM workspace interface. This interface provides accessto Foundation SAS software features such as the SAS language,SAS libraries, the server file system, results content, and formattingservices. A SAS workspace represents a session with the SASSystem, and it is functionally equivalent to a SAS Display Managersession or the execution of the SAS System as a batch job.

SAS StoredProcess Server

is a multi-user server that is provided with SAS IntegrationTechnologies and is used to execute SAS Stored Processes anddeliver the results. A SAS Stored Process is a SAS program that isstored on a server and can be called by client applications. SASStored Processes enable clients to execute parameterized SASprograms without having to know the SAS language.

SAS OLAPServer

delivers pre-summarized cubes of data to OLAP clients like SASEnterprise Guide using OLE DB for OLAP. Cubes are logical sets ofdata that are organized and structured in a hierarchical,multidimensional arrangement. You can query cubes by using themultidimensional expression (MDX) language. The SAS OLAPServer, which is provided with SAS Intelligent Storage products, isdesigned to reduce the load on traditional back-end storage systemsby delivering summarized views of data to business intelligenceapplications, irrespective of the amount of data underlying thesesummaries.

SAS MetadataServer

is a multi-user server, provided with SAS Foundation, that enablesusers to read metadata from or write metadata to one or more SASMetadata Repositories. SAS Metadata Repositories containmetadata that represents items such as SAS application servers(including SAS Workspace Servers, SAS OLAP Servers, and SASStored Process Servers), users in the metadata environment,libraries, tables, stored processes, and cubes.

Configuring and Using IOM ServersYou can use the SAS Deployment Wizard to plan, install, and define the

configurations for your IOM servers. Detailed documentation is provided to help youperform these tasks either with or without the wizard. Documentation is also providedto help you manage and administer your server configurations after installation, and toassist you in developing application programs that use the IOM servers.

The following table provides information about the documentation that is availablefor IOM servers:

Components of SAS Integration Technologies � Configuring and Using IOM Servers 7

Table 2.1 Documentation for IOM Servers

Server Type Type of Information Documentation

using SAS Deployment Wizardto plan and configure

SAS Intelligence Platform:Installation and ConfigurationGuide

securing SAS Intelligence Platform:Security Administration Guide

starting SAS Intelligence Platform:System Administration Guide

developing applications “IOM Scenario” on page 10 inthis overview

connecting a client application “Connecting Clients to IOMServers” on page 8 in thisoverview

SAS Integration Technologies:Java Client Developer’s Guide

SAS Integration Technologies:Windows Client Developer’sGuide

all IOM server types

implementing distributedsecurity for clients



planning and configuringwithout SAS Deployment Wizard

SAS Intelligence Platform:Application ServerAdministration Guide

modifying and administering theconfiguration after installation


modifying the configuration toimprove the performance of SASbusiness intelligenceapplications


SAS Workspace Server

developing clients “Workspace Object Hierarchy”on page 11 in this overview



8 Connecting Clients to IOM Servers � Chapter 2

Server Type Type of Information Documentation

planning and configuringwithout SAS Deployment Wizard




modifying the configuration toimprove the performance of SASbusiness intelligenceapplications


SAS Stored Process Server

developing clients SAS Stored Processes:Developer’s Guide


SAS OLAP Server modifying and administering theconfiguration after installation



SAS Intelligence Platform:System Administration Guide

SAS Metadata Server

developing clients SAS Open Metadata Interface:Reference

SAS Java Metadata Interface:User’s Guide

Connecting Clients to IOM Servers

Overview of Communication between Clients and IOM ServersThe information that is needed to connect to an IOM server is obtained from the SAS

Metadata Server. SAS Integration Technologies supports additional SAS softwarefeatures by enabling Java and Windows clients to connect to and request objects fromvarious types of IOM servers including other SAS Metadata Servers, SAS OLAPServers, SAS Stored Process Servers, and SAS Workspace Servers.

SAS Integration Technologies facilitates client/server communication across multiplevendor architectures by supporting multiple client/server interoperability standards.The following figure shows the different ways that clients and IOM servers cancommunicate.

Components of SAS Integration Technologies � Connecting Clients to IOM Servers 9

Figure 2.1 Communication between Clients and IOM Servers

Windows ClientsAs shown in the figure, Windows clients that are written in languages such as Visual

Basic or Visual C++ access IOM servers that are running in the Windows operatingenvironment by using the Microsoft Component Object Model (COM). Windows clientinterfaces provided in SAS Integration Technologies support two leading industrystandards: ActiveX Data Objects (ADO) and Object Linked Embedding for Databases(OLE DB).

Windows clients accessing IOM servers on other server platforms use the IOMBridge for COM. This bridge allows you to develop native COM and DCOM applicationsthat access server data, for example, on UNIX and mainframe platforms. Thistransparency is a key feature of SAS Integration Technologies. It enables applicationdevelopers to have full access to the architectural elements that are available in theWindows environment, even when their clients communicate with servers in other

10 Using IOM to Develop Applications � Chapter 2

operating environments. The bridge makes other operating environments appear to beextensions of the client’s native operating environment.

With SAS Integration Technologies, Windows clients can use the Windows ObjectManager to connect to IOM servers.

Note: In SAS®9, SAS Integration Technologies still supports the SAS 8 interface forusing the Windows Workspace Manager. However, it is recommended that you use theWindows Object Manager interface in order to take advantage of the new features. �

Java ClientsJava clients that access IOM servers use the Common Object Request Broker

Architecture (CORBA). CORBA is an architecture for an open software bus on whichobjects can interoperate across networks and operating systems.

The Object Request Broker (ORB) is the key element of CORBA. It provides theinfrastructure for distributed object computing by enabling software components(objects) on one machine to locate and communicate with components on other machines.This infrastructure enables you, as an application developer, to focus on implementingyour business logic instead of worrying about all the underlying technology.

SAS Integration Technologies provides an ORB called the IOM bridge for Java. ThisORB implements the standard CORBA ORB interface defined by the ObjectManagement Group (OMG). It uses a proprietary inter-orb protocol (called the IOMBridge protocol) to communicate with the IOM server.

With SAS Integration Technologies, Java clients can use the Java Connection Factoryto connect to IOM servers.

Note: In SAS®9, SAS Integration Technologies still supports the SAS 8 interface forusing the Java Workspace Factory. However, it is recommended that you use theConnection Factory interface in order to take advantage of the new features. �

Using IOM to Develop Applications

IOM ScenarioOne of the chief benefits of building component-based applications by using the

Integrated Object Model (IOM) is that it enables you to de-couple your businessapplication logic from your presentation methods. This enables you to reuse coreapplication functionality in multiple presentation personalities and, as a result, itextends your application’s deployment options.

For example, consider the following figure. Using SAS Integration Technologiessoftware, you can develop applications in which Web browsers, desktop GUIs, andmiddle-tier Web and application server presentation platforms can all become clients ofSAS software server components.

Components of SAS Integration Technologies � Workspace Object Hierarchy 11

Figure 2.2 Clients of SAS Software Server Components

Within the Web browser context, you can use client-side scripting such as VBScript,local components such as ActiveX controls, and Java applets to implement access toserver components.

Similarly, you can assess server components from desktop application environmentsincluding custom applications that are written in Visual Basic, Java, C++, Delphi, andPowerBuilder. Further, any desktop application container that supports Visual Basicfor Applications (VBA), including those in the Microsoft Office suite and manythird-party offerings, can also participate.

Finally, you can deploy middle-tier Web and application servers, such as theMicrosoft Internet Information Server (IIS), Microsoft Transaction Server (MTS), andvarious .NET servers to host logic that accesses SAS software server components.

This level of deployment flexibility enables you to distribute your logic componentsacross the enterprise in order to realize the performance advantages that are associatedwith data source co-location. This component distribution can be accomplished in amanner that is transparent to the client.

Workspace Object HierarchyThe principal IOM interfaces of the SAS Workspace Server include the following:

� Workspace (a SAS session)� LanguageService (submit, list/log, stored processes)� DataService (librefs, plus access through ADO, OLE-DB or JDBC)� FileService (filerefs and directories)� Utilities (result packages, formats, host info)

The following figure depicts the object hierarchy for these interfaces.

12 Workspace Object Hierarchy � Chapter 2

Figure 2.3 Workspace Object Hierarchy

Components of SAS Integration Technologies � Foundation Services 13

In the figure, the number 1 indicates that that part of the hierarchy has exactly onechild per parent. An asterisk (*) indicates that that part of the hierarchy has zero orgreater children per parent.

The LanguageService defines methods for submitting SAS procedural scriptinglanguage statements (to execute SAS DATA and procedure steps) and for retrieving theassociated LOG and LIST outputs.

Applications that produce sophisticated results such as HTML and graphs generatedby using the SAS Output Delivery System can use the ResultPackageService to retrievecollected elements. Program execution progress events such as step begin, step end, anderror conditions can also be monitored with a LanguageService event interface.

The FileService defines methods for managing SAS file references (FILEREFs) andreading or writing files on the server’s host file system. A client can exploit SASexternal file access methods and host-specific fileref assignment options to access thewide variety of specialized features in SAS external file I/O on the various server hostplatforms. The DataService surfaces similar control over SAS library references(LIBREFs).

IOM uses standard interface mechanisms within the Microsoft COM and Javaapplication environments to expose the object hierarchy. This enables you to use theActiveX Data Objects (ADO) and OLE DB access protocols in the Windows COMenvironment. In Java environments, the JDBC 2.0 access protocol is supported. Thesestandard mechanisms provide semantic richness, including read, write, update, andquery services. All components that support the same standards can easily interoperate.

Application hierarchies are also available through specialized SAS product offeringsand custom applications developed with the SAS/AF software.

SAS Integration Technologies provides the middleware necessary to connect clientsand servers across multiple vender architectures, as described in “Connecting Clients toIOM Servers” on page 8.

Foundation Services

The SAS Foundation Services are a set of infrastructure and extension serviceswhich support the development of integrated, scalable, and secure Java applications.The SAS Foundation Services are based on the following design principles:

� implementation modularity

� location transparency� robust and adaptive resource management

� runtime monitoring

� consistent deployment methodology

� client neutrality

The design model of the SAS Foundation Services supports both local and remoteresource deployment and promotes resource sharing among applications. Sharing canoccur for a specific session, for a specific user, or globally, as appropriate. At the sametime, the model controls access to protected resources based on privileged-user statusand group membership.

The SAS Foundation Services are as follows:

� Connection Service� Discovery Service

14 Publishing Framework � Chapter 2

� Event Broker Service� Information Service� Logging Service� Publish Service� Security Service� Session Service� Stored Process Service� User Service

The Connection, Publish, and Stored Process services are extensions of similarservices that are part of the Integrated Object Model (IOM) Services published withSAS Integration Technologies 8.2. The IOM Services continue to be supported.However, the SAS Foundation Services provide enhanced features, including support forthe use of a SAS Metadata Server for storing configuration information, and support forthe use of shared remote service deployments.

For information about configuring and administering SAS Foundation Services, seethe SAS Foundation Services: Administrator’s Guide. For information about using SASFoundation Services to develop applications, see the SAS Integration Technologies:Java Client Developer’s Guide.

Publishing Framework

Overview of the Publishing FrameworkThe Publishing Framework feature of SAS Integration Technologies provides a

complete and robust publishing environment for enterprise-wide information delivery.The Publishing Framework consists of SAS CALL routines, application programminginterfaces (APIs), and graphical user interfaces that enable both users and applicationsto publish SAS files (including data sets, catalogs, and database views), other digitalcontent, and system-generated events to a variety of destinations:

� e-mail addresses� message queues� publication channels and subscribers� WebDAV-compliant servers� archive locations

The Publishing Framework also provides tools that enable both users andapplications to receive and process published information. For example, users canreceive packages with content, such as charts and graphs, that is ready for viewing. Inaddition, SAS programs can receive packages with SAS data sets that might in turntrigger additional analyses on that data.

The functions of the Publishing Framework include channel definition, subscriptionmanagement, package publishing, package retrieval, package viewing, and eventpublishing.

For information about how to perform publishing tasks, or how to incorporatepublishing tasks into your SAS programs or applications, see the SAS PublishingFramework: Developer’s Guide. For information about how to administer publication

Components of SAS Integration Technologies � Package Publishing 15

channels and subscriber information, see the product help for the PublishingFramework plug-in in SAS Management Console.

Channel DefinitionThe Publishing Framework enables you to define SAS publication channels, which are

conduits for publishing particular categories of information. You can set up a channelfor a particular topic, organizational group, user audience, or any other category.

To define a channel, use SAS Management Console to define a name for the channel,a description, a subject, the path in which the channel’s archived packages are to bestored, and one or more key words. The channel definition, or metadata, is stored onthe SAS Metadata Server. SAS Management Console can also be used to specify whichgroups of users are authorized to subscribe to the channel.

Subscription ManagementOnce publication channels have been defined, authorized users can subscribe to them

and automatically receive information whenever it is published to those channels.First, you must define the users who are eligible subscribers. To do so, use SAS

Management Console to enter user authentication information.If your organization has installed the SAS Information Delivery Portal, users can

manage their subscriptions from within the portal. The portal enables users to selectchannels to subscribe to channels, specify the desired delivery transport (such as ane-mail address or message queue), and specify filters that indicate which information isto be included or excluded.

Administrators can also use the Publishing Framework plug-in for SAS ManagementConsole to manage subscriptions. Using this application, administrators can creategroups of subscribers, subscribe individual users or groups to a channel, and specifydelivery transport and filtering options.

Package PublishingThe Publishing Framework enables you to create packages that contain one or more

information entities, including SAS data sets, SAS catalogs, SAS databases, and almostany other type of digital content. You can also define viewers that make the informationentities easier to display.

After creating a package, you can publish the package and its associated viewers toone or more channels. Publishing the package causes the information to be delivered toeach user who has subscribed to those channels if the package and its contents meetthe subscriber’s filtering criteria. In addition to channels, you can publish packagesdirectly to one or more e-mail addresses, message queues, WebDAV-compliant servers,and archive locations.

To create and publish packages, you can use any of the following methods:

� use the publish CALL routines to create packages and publish them from within aSAS program

� use the APIs that are provided with SAS Integration Technologies to createpackages and publish them from within a third-party application

You can also use SAS Enterprise Guide or the SAS Information Delivery Portal tocreate and publish packages via the Publishing Framework.

16 Package Retrieval and Viewing � Chapter 2

Package Retrieval and ViewingThe Publishing Framework provides SAS Package Retriever, which is a graphical

user interface that enables users to extract and save information from packages thathave been published through the Publishing Framework. The SAS Package Readeruser interface enables users to display the contents of packages. If the SAS InformationDelivery Portal has been installed, users can view published information from theportal.

In addition, you can use CALL routines to extract and process published informationfrom within SAS programs. APIs are provided to enable third-party programs to extractand process published information.

Event PublishingSAS Integration Technologies includes the Publish Event Interface. This interface

consists of CALL routines that enable you to write SAS programs, including storedprocesses, that create and publish events. Events can be generated and publishedexplicitly, or they can be generated implicitly as part of the publication of a package.Implicit event generation occurs when packages are published to a channel that hasevent subscribers defined.

Events are published as well-formed XML documents. They can be published toHTTP servers, to message queues, or to publication channels and their associatedsubscribers. You can develop custom applications that receive and process events thatare generated by the Publishing Framework.

Application Messaging

Overview of Application MessagingThe Application Messaging Interface includes three sets of CALL routines that

enable you to incorporate messaging services into your SAS programs. The interfacessupport asynchronous message queuing through the use of the following messagingsoftware: IBM WebSphere MQ (formerly called MQSeries); Microsoft Message QueuingServices (MSMQ), which are part of the Windows NT® Server product; and TIBCOTIB/Rendezvous.

Application messaging enables two or more applications to communicate with oneanother indirectly and asynchronously using message queues. The applications do nothave to be running at the same time or even in the same operating environment. Anapplication can communicate with another application by sending a message to aqueue. The receiving application retrieves the message when it is ready.

SAS Integration Technologies provides three messaging interfaces: the WebSphereMQ Functional Interface, the MSMQ Functional Interface, and the Common MessagingInterface.

For complete documentation of the SAS application messaging interfaces, includingCALL routine syntax and program samples, see the Application Messaging with SAS.

Components of SAS Integration Technologies � Stored Processes 17

WebSphere MQ Functional InterfaceWith the SAS interface to IBM WebSphere MQ (formerly called MQSeries), SAS

programs can create new WebSphere MQ message queues or take advantage of existingones that are available throughout the enterprise. This interface was designed to be assimilar as possible to the WebSphere message queuing interface (MQI).

MSMQ Functional InterfaceWith the SAS interface to Microsoft MSMQ, SAS programs can create new MSMQ

message queues or take advantage of existing ones that are available throughout theenterprise. The CALL routines in this interface interact directly with the MSMQapplication programming interface (API).

Common Messaging InterfaceThe SAS Common Messaging Interface provides a seamless environment for writing

SAS programs that access message queues of the IBM WebSphere MQ, MicrosoftMSMQ, and TIBCO TIB/Rendezvous transports. The CALL routines in this interfaceenable programs to interact in a consistent manner that is independent of theapplication messaging transport being used.

The Common Messaging Interface also includes CALL routines that enable your SASprogram to use the local SAS registry or a distributed LDAP repository to store andretrieve messaging information.

Stored ProcessesA stored process is a SAS program that is stored centrally on a server. A client

application can then execute the program and receive and process the results. Storedprocesses enable you to centrally maintain and manage code, give you better controlover changes, enhance security and application integrity, and ensure that every clientexecutes the latest version of code that is available.

Stored processes are like other SAS programs except they have an additional featurethat enables customization of the program’s execution. This feature enables theinvoking application to supply parameters at the time that the stored process isinvoked. For example, if you have a stored process that analyzes monthly sales data,you could create a MONTH variable in the stored process. At execution time, the usercould supply the parameter MONTH=MAY to analyze May sales data.

You can use stored processes for Web reporting, analytics, building Web applications,delivering packages to clients or the middle tier, and publishing results to channels orrepositories. Stored processes can access any SAS data source or external file and cancreate new data sets, files, or other data targets supported by the SAS System.

You can use the following clients to invoke stored processes:

� SAS Add-In for Microsoft Office� SAS BI Web Services� SAS Data Integration Studio� SAS Enterprise Guide� SAS Information Delivery Portal

18 SAS BI Web Services � Chapter 2

� SAS Information Map Studio� SAS Stored Process Web Application� SAS Web Report Studio� Stored Process Service application programming interface (API)

Stored processes can generate output files in a variety of formats. They can alsoproduce streaming output for Web applications, as well as package output forpublishing. Stored processes can operate either on a SAS Workspace (IOM) Server or aSAS Stored Process Server.

For information about how to create a stored process and invoke it in a clientapplication, see the SAS Stored Processes: Developer’s Guide. For information abouthow to create the metadata to define a stored process, see the product help for the NewStored Process Wizard or the Stored Process Properties dialog box in SAS ManagementConsole.

SAS BI Web ServicesSAS BI Web Services enable client applications to obtain metadata about and execute

SAS Stored Processes by using the XML for Analysis (XMLA) Version 1.1 interface.A Web service is an interface that enables communication between distributed

applications. Web services provide cross-platform integration by enabling applicationswritten in various programming languages to communicate by using a standardWeb-based protocol. This functionality makes it possible for businesses to bridge thegaps between different applications and systems.

SAS Integration Technologies includes two implementations of SAS BI Web Services:a Java implementation, which requires a servlet container, and an implementation thatuses the .NET framework. These implementations use the Simple Object AccessProtocol (SOAP) communication protocol.

Before SAS 9.2, you could write only XMLA Web services. Starting with SAS 9.2, youcan use SAS Management Console to deploy a set of stored processes as a generatedWeb service.

With XMLA Web Services, two methods, Discover() and Execute(), are provided. TheDiscover method calls the SAS Metadata Server to obtain the requested metadata, andthe Execute method calls the SAS Stored Process Server to invoke a stored process.Stored processes that are called by these methods must be registered on the SASMetadata Server with XMLA Web Service as a keyword and Streaming as the outputtype. The output from a stored process that is called by a SAS BI Web Service is alwaysan XML stream.

To create generated Web services, you can select a set of stored processes in SASManagement Console and deploy them to the Web Service Maker. The Web ServiceMaker generates a new Web service that contains one operation for each stored processthat you selected. A new Web Service Description Language (WSDL) document isgenerated when you deploy the Web service. The generated WSDL document containsall the information that would be obtained if you were using the Discover method.

For detailed information about using SAS BI Web Services, including instructions forcreating stored processes that Web services can access, see the SAS BI Web Services:Developer’s Guide.

Components of SAS Integration Technologies � SAS Web Infrastructure Platform 19

Directory Services

If your organization uses an enterprise directory that conforms to the LightweightDirectory Access Protocol (LDAP), you can use the directory services interfaces of SASIntegration Technologies to incorporate enterprise directory services into your SASapplications. Through these interfaces, distributed SAS applications can share acommon enterprise directory with components that might be executing in otherrun-time environments across the enterprise.

SAS Integration Technologies provides two interfaces that you can use to interactwith an LDAP server from a SAS program:

� The LDAP CALL Routine Interface, which is set of CALL routines that you canuse to add, delete, modify, and search entries in the LDAP server.

� The LDAPSERVICES class for the SAS Component Language (SCL). This classprovides methods that add, delete, modify, and search entries in the LDAP server.

For documentation about the syntax and use of these interfaces, refer to the SASIntegration Technologies: Directory Services Reference.

SAS Web Infrastructure Platform

The SAS Web Infrastructure Platform is a collection of services and applications thatprovide common infrastructure and integration features to be used by SAS Webapplications. These services and applications provide the following benefits:

� consistency in installation, configuration, and administration tasks for Webapplications

� greater consistency in users’ interactions with Web applications

� integration among Web applications as a result of the ability to share commonresources

The following services and applications are included in the SAS Web InfrastructurePlatform:

SAS BI Web Services for Javacan be used to enable your custom applications to invoke and obtain metadataabout SAS Stored Processes. Web services enable distributed applications that arewritten in different programming languages and that run on different operatingsystems to communicate using standard Web-based protocols. The most commonprotocol is the Simple Object Access Protocol (SOAP).

The SAS BI Web Services for Java interface is based on the XML for Analysis(XMLA) Version 1.1 specification.

SAS Shared Web Assetscontains graph applet JARs that are shared across SAS Web applications. Theydisplay graphs in stored processes and in the SAS Stored Process Web application.

SAS Web Infrastructure Platform Servicesprovide a common infrastructure for SAS Web applications. The infrastructuresupports activities such as auditing, authentication, configuration, status andmonitoring, e-mail, theme management, and data sharing across SAS Webapplications.

20 SAS Web Infrastructure Platform � Chapter 2

SAS Logon Managerprovides a common user authentication mechanism for SAS Web applications. Itdisplays a dialog box for user ID and password entry, authenticates the user, andlaunches the requested application. SAS Logon Manager supports a single sign-onauthentication model. When this model is enabled, it provides access to a varietyof computing resources (including servers and Web pages) during the applicationsession without repeatedly prompting the user for credentials.

You can configure SAS Logon Manager to display custom messages and tospecify whether a logon dialog box is displayed when users log off.

In addition, you can use third-party products in conjunction with SAS LogonManager to enable users to access multiple Web applications within the samebrowser session.

SAS Preferences Managerprovides a common mechanism for managing preferences for SAS Webapplications. The feature enables administrators to set default preferences forlocale, theme, alert notification, and time, date, and currency display. Within eachWeb application, users can view the default settings and update their individualpreferences.

SAS Stored Process Web Applicationexecutes stored processes on behalf of a Web client and return results to a Webbrowser. The SAS Stored Process Web application is similar to the SAS/IntrNetApplication Broker, and has the same general syntax and debug options.

SAS Web Administration Consoleprovides features for monitoring and administering middle-tier components. Thisbrowser-based interface enables administrators to do the following:

� view a list of users who are logged on to SAS Web applications, and sende-mail to active users

� create, delete, and manage permissions for folders on the SAS Content Server

� view configuration information for each middle-tier component

SAS Content Serverstores digital content (such as documents, reports, and images) that is created andused by SAS Web applications. For more information, see the SAS content servertopic in SAS Intelligence Platform: Overview.

The following documentation is provided for the SAS Web Infrastructure Platform:

� the SAS Information Delivery Portal: Introduction, which provides a high-leveldescription of the features of the SAS Information Delivery Portal

� the SAS Intelligence Platform: Web Application Administration Guide, whichdescribes the configuration and administration tasks that are necessary toimplement Web applications (including the SAS Information Delivery Portal) thatwere developed using the SAS Web Infrastructure Platform

� Developing Portlets for the SAS Information Delivery Portal, which describes howto use the platform to develop a portal-like Web application or to customize orextend the functionality of the SAS Information Delivery Portal

� help files, accessible through the SAS Web Infrastructure Platform and SASInformation Delivery Portal’s user interface, which provide instructions for pagenavigation, logging on and logging off, metadata searching, bookmarking,personalization, and content administration

21

Glossary

access control entrya set of identities and permissions that are directly associated with a particularresource. 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 templatea reusable named authorization pattern that you can apply to multiple resources. Anaccess control template consists of a list of users and groups and indicates, for eachuser or group, whether permissions are granted or denied. Short form: ACT.

ACESee access control entry.

ACTSee access control template.

administered objecta pre-configured Java Message Service (JMS) object that is created by a systemadministrator for use by client applications. Administered objects handle thecomplexities of using JMS in conjunction with proprietary messaging systems so thatclient applications can focus on business logic. See also Java Message Service andEvent Broker Service.

alertan automatic notification of an electronic event that is of interest to the recipient.

archivein the Publishing Framework, a package that is compressed and saved to a directory.The archive contains the contents of a package, plus metadata that is necessary forextracting the contents.

archive pathin the Publishing Framework, the complete path of the location to which a user orprogram can publish an archive package.

asynchronous logginga process that enables log messages to be queued within and delivered from a threadother than the main application thread. See also Logging Service.

22 Glossary

authenticationthe process of verifying the identity of a person or process within the guidelines of aspecific authorization policy.

authentication domaina 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 beclassified as belonging to an OracleAuth authentication domain.

authentication providera software component that is used for identifying and authenticating users. Forexample, an LDAP server or the host operating system can provide authentication.

authorizationthe process of determining which users have which permissions for which resources.The outcome of the authorization process is an authorization decision that eitherpermits or denies a specific action on a specific resource, based on the requestinguser’s identity and group memberships.

backgrounda mode of computer processing that does not require user interaction and whichallows users to perform multiple tasks on the computer concurrently. In the SASInformation Delivery Portal, some stored processes run in the background so thatyou can perform other portal tasks during processing.

basethe distinguished name (DN) to use as a starting place for searches of an LDAPdirectory. Searches can begin at any point in a directory tree. Beginning the searchlower 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 orldapBase.

bindto create an association among two or more entities for a particular scope of time andplace. For example, an association could be created between two or moreprogramming objects, between a variable name and an object, between a symbolicaddress and a real machine address, or between a client and a server.

bookmarka placeholder that stores either the address and name of a document or the addressof a location within a document so that you can quickly and easily return to thatdocument or location later.

chaininga process by which a log message is passed to the current logging context and to eachcontext in the hierarchy of the current logging context. If chaining is not specified ata particular level in the hierarchy, then the log message is not passed beyond thatlevel. See also logging context and Logging Service.

channela virtual communication path for distributing information. In SAS, a channel isidentified with a particular topic (just as a television channel is identified with aparticular radio frequency). Using the features of the Publishing Framework,authorized users or applications can publish digital content to the channel, andauthorized users and applications can subscribe to the channel in order to receive thecontent. See also publish and subscribe.

Glossary 23

clienta computer or application that requests services, data, or other resources from aserver. See also server.

clustera group of machines that participate in load balancing. Each machine in the clusterruns an object spawner that handles client requests for connections.

COMSee Component Object Model.

Common Object Request Broker Architecturea standard API for distributed object communication. CORBA was created by theObject Management Group. It is the most widely used distributed object standard forconnecting operating system platforms from multiple vendors. Short form: CORBA.

componenta self-contained, reusable programming object that provides some type of service toother components in an object-oriented programming environment.

Component Object Modelan object-oriented programming model that defines how software componentsinteract within a single process or between processes. For example, COM includesstandard rules of communication that enable a user-interface object to be draggedand dropped from one application window to another. Short form: COM.

Connection Factoryan application interface that enables Java programs to make IOM bridge connectionsto IOM servers. The interface provides the scalability features of pooling and serverfailover as well as support for load-balancing spawners. The interface is part of theSAS Foundation Services Connection Service. See also SAS Foundation Services andConnection Service.

Connection Serviceone of the SAS Foundation Services. This service enables applications to (1) connectto IOM servers that use the IOM Bridge protocol, (2) use the Connection Factory toaccess existing connection objects and to create new connection objects for variousserver configurations, and (3) use advanced connection management features, such asconnection pooling, failover, and load balancing, which are available through theConnection Factory. See also SAS Foundation Services and Connection Factory.

containera software application environment in which a component such as an applet, anapplication client, a servlet, a JavaServer page, or an Enterprise Java Bean isexecuted. Containers provide specific services that can be exploited by the types ofcomponents that they support.

content typea value that tells a client’s Web browser how to interpret and display a transferredobject 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 Multipurpose Internet Mail Extensions.

contextthe set of facts or circumstances that surround a situation or event. In Javaapplications, context generally refers to a collection of settings and attributes thatdescribe a container or service that is currently executing.

CORBASee Common Object Request Broker Architecture.

24 Glossary

DCOMSee Distributed Component Object Model.

delivery transportin the Publishing Framework, the method of delivering a package to the consumer.Supported transports include e-mail, message queue, and WebDAV. Although not atrue transport, a channel also functions as a delivery mechanism. See also e-mail,message queue, WebDAV (Web Distributed Authoring and Versioning), and channel.

directory information treethe entries that an LDAP directory server contains. These entries are stored in ahierarchical, tree-like structure. Short form: DIT.

directory schemathe set of defined attributes and object classes that defines the content of acceptableentries within an LDAP directory server.

Discovery Serviceone of the SAS Foundation Services. This service enables applications to (1) findimplementations of the SAS Foundation Services based on specified servicecapabilities and, optionally, service attributes, and (2) rediscover a previouslydiscovered service by using the service’s Discovery Service ID. The Discovery Servicecan find service implementations that have been deployed locally for the application’sexclusive use, as well as service implementations that have been deployed remotelyfor the use of multiple applications. See also SAS Foundation Services.

distinguished namea unique identifier of an entry in an LDAP network directory. In effect, adistinguished name is the path to the object in the directory information tree. Shortform: DN.

Distributed Component Object Modelan extension to the Component Object Model (COM) that enables components torequest services from components that are on other computers in a network. Shortform: DCOM. See also component and Component Object Model.

DITSee directory information tree.

DNSee distinguished name.

DNS namea name that is meaningful to people and that corresponds to the numeric TCP/IPaddress of a computer on the Internet. For example, www.alphaliteairways.commight be the DNS name for an Alphalite Airways Web server whose TCP/IP addressis 192.168.145.6.

domaina database of users that has been set up by an administrator by using a specificauthentication provider such as LDAP or the host operating system. The domainname should be unique within your enterprise. For example, you should not have aWindows domain and a UNIX domain that are both named “SALES”. See alsoauthentication domain.

e-maila system for transmitting messages electronically, usually between two computers.

encryptionthe act or process of converting data to a form that only the intended recipient canread or use.

Glossary 25

entrya set of name/value pairs that describe a resource that is defined on an LDAPdirectory server. See also name/value pair.

entry filterSee package entry type filter, MIME type filter.

eventa type of notification that triggers an Event Broker Service to take a particularaction. An event is specified as well-formed XML that contains the name of theevent, associated headers and properties, and the message body. See also EventBroker Service and XML (Extensible Markup Language).

Event Broker Serviceone of the SAS Foundation Services. This service enables applications to send anddeliver events to the appropriate handling agents for processing. The handling agentcan be (1) a statically defined process flow that runs in its own thread within theEvent Broker Service to process the event or (2) an application that has registereditself with the Event Broker Service at run time so that it can receive events. Seealso SAS Foundation Services and event.

event message specificationa well-formed XML representation of an event. The event message specificationcontains attributes of the event such as name, version, identity, credentials, sender,send time, and response type. See also Event Broker Service.

Extensible Markup Languagea markup language that structures information by tagging it for content, meaning, oruse. Structured information contains both content (for example, words or numbers)and an indication of what role the content plays. For example, content in a sectionheading has a different meaning from content in a database table. Short form: XML.

factoryan object that controls the creation of other objects, access to other objects, or both.See also Connection Factory.

filterin the Publishing Framework, a named set of criteria that are used for selectingeither a package or specific package entries for a subsequent operation. Filters areuseful in the following contexts: channel subscription properties, viewer fileprocessing, stored processes, and LDAP directory searches. For example, a channelsubscriber can define a name/value filter that controls the types of packages that heor she receives. See also name/value pair, package entry type filter, and MIME typefilter.

foundation servicesSee SAS Foundation Services.

groupin the Publishing Framework, a collection of subscribers. When a group is subscribedto a channel, each member of the group who has a defined subscriber entry in thePublishing Framework will receive the information that is published to that channel.Only metadata administrators have the authority to add members or to removemembers from a group.

26 Glossary

HTTPSee HyperText Transfer Protocol.

HTTP servera server that handles an HTTP request from a client such as a Web browser. Usuallythe client’s HTTP request indicates that the client wants to retrieve information thatis pointed to by a URL. An example of a popular HTTP server is the Apache HTTPServer from the Apache Software Foundation. See also Web server.

HyperText Transfer Protocola protocol for transferring data to the Internet. HTTP provides a way for servers andWeb clients to communicate. It is based on the TCP/IP protocol. Short form: HTTP.

information mapa collection of data items and filters that provides a user-friendly view of a datasource. When you use an information map to query data for business needs, you donot have to understand the structure of the underlying data source or know how toprogram in a query language.

Information Serviceone of the SAS Foundation Services. This service enables applications to perform afederated search of any repositories that a user has a connection to. The termfederated means connected and treated as one. The classes in the InformationService package enable applications to create a single filter that can search disparaterepositories (for example, SAS Metadata Repositories and LDAP repositories). Seealso SAS Foundation Services.

input streama 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 Modela set of object-based interfaces to features or services that are provided by Base SASsoftware. IOM enables application developers to use industry-standard programminglanguages, programming tools, and communication protocols to develop clientprograms that access these services on IOM servers. Short form: IOM.

Integrated Object Model servera SAS object server that is launched in order to fulfill client requests for IOMservices. Short form: IOM server.

IOMSee Integrated Object Model.

IOM bridgea software component of SAS Integration Technologies that enables Java clients andWindows clients to access an IOM server.

IOM bridge for COMthe 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 DCOMspecifications to access SAS servers in operating environments such as z/OS andUNIX that do not support the COM or DCOM specifications. See also IntegratedObject Model, Component Object Model, and Distributed Component Object Model.

Glossary 27

IOM bridge for Javaa software component of SAS Integration Technologies that enables Java clients toaccess IOM servers.

IOM serverSee Integrated Object Model server.

Java Development Kita software development environment that is available from Sun Microsystems, Inc.The JDK includes a Java Runtime Environment (JRE), a compiler, a debugger, andother tools for developing Java applets and applications. Short form: JDK.

Java Message Servicean application programming interface (API) that enables client applications to accessthe facilities of a message service. This interface provides a standard way for Javaprograms to create, send, receive, and read messages. Short form: JMS.

Java Naming and Directory Interfacea standard extension to the Java platform that enables developers to createapplications that can interact with a number of different naming services anddirectory services, such as the Domain Name System (DNS) and the LightweightDirectory Access Protocol (LDAP). Short form: JNDI.

Java RMISee remote method invocation.

Java Virtual Machinea program that interprets Java programming code so that the code can be executedby the operating system on a computer. The JVM can run on either the client or theserver. The JVM is the main software component that makes Java programsportable across platforms. A JVM is included with JDKs and JREs from SunMicrosystems, as well as with most Web browsers. Short form: JVM.

JavaServer pagea type of servlet that enables users to create Java classes through HTML. Shortform: JSP.

JDKSee Java Development Kit.

JMSSee Java Message Service.

JNDISee Java Naming and Directory Interface.

JSPSee JavaServer page.

JVMSee Java Virtual Machine.

keywordin BI Manager, a descriptive word or phrase that can be stored in the metadata forone or more BI objects and which can subsequently be used in a filtered search. Forexample, ’XMLA Web Service’ is a reserved keyword that is used to identify andlocate stored processes that can be used as Web services.

layout patterna feature of the Logging Service that enables you to associate a layout with aparticular logging output destination. The layout specifies how the output is to beformatted before it is sent to the output destination. The layout is specified as a

28 Glossary

pattern string similar to the pattern strings that are used in the C language<code>printf</code> statement. See also Logging Service.

LDAPSee Lightweight Directory Access Protocol.

LDAP Data Interchange Formata file format that is widely used for building a database of directories that are storedon multiple servers, for adding large numbers of directories to a directory database,and for synchronizing the contents of those directories. The servers on which thedirectories are stored must support the LDAP protocol. Short form: LDIF.

LDAP directorya repository that contains data about an enterprise’s users and resources, as well asrelated security information, and that stores this data and information in a formatthat clients on a network can access by using the Lightweight Directory AccessProtocol (LDAP).

LDAP directory servera server that provides access to one or more LDAP directories.

LDAP serverSee LDAP directory server.

LDIFSee LDAP Data Interchange Format.

Lightweight Directory Access Protocola protocol that is used for accessing directories or folders. LDAP is based on the X.500standard, but it is simpler and, unlike X.500, it supports TCP/IP. Short form: LDAP.

link(1) a portal content item that can be accessed using a URL; (2) a character string in aportal that you can click to initiate an action.

load balancingfor IOM bridge connections, a program that runs in the object spawner and that usesan algorithm to distribute work across object server processes on the same orseparate machines in a cluster.

local service deploymenta service deployment that supports an application’s exclusive access to a set of SASFoundation Services that are deployed within a single Java Virtual Machine (JVM).See also service deployment.

localhosta keyword that is used to specify the machine on which a program is executing. If aclient specifies localhost as the server address, the client connects to a server thatruns on the same machine.

logging contexta collection of attributes and settings that define a particular way in which theLogging Service is to be used. The logging context specifies where and in whatformat logging calls will be written. See also Logging Service.

Logging Serviceone of the SAS Foundation Services. This service enables applications to (1) sendrun-time messages to one or more output destinations, including consoles, files, andsocket connections; (2) configure and control the format of information that is sent toa particular destination, either by using static configuration files or by invokingrun-time methods that control logging output; and (3) perform remote logging, which

Glossary 29

involves sending log messages that are generated in one Java Virtual Machine (JVM)to another JVM. See also SAS Foundation Services.

logical namea unique name that can be assigned to related resources in order to manage theresources as a group.

logical serverin 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, suchas one or more SAS Workspace Servers.

logina SAS copy of information about an external account. Each login includes a user IDand belongs to one SAS user or group. Most logins do not include a password.

message nodein a process flow diagram, a node that encapsulates inputs and outputs to one ormore process nodes. See also process node and process flow.

message queuein application messaging, a place where one program can send messages that will beretrieved by another program. The two programs communicate asynchronously.Neither program needs to know the location of the other program nor whether theother program is running. See also delivery transport.

message queue pollinga feature of the object spawner that monitors message queues and distributesmessage queue tasks efficiently among SAS processes.

metadataa description or definition of data or information.

metadata repositorya collection of related metadata objects, such as the metadata for a set of tables andcolumns that are maintained by an application. A SAS Metadata Repository is anexample.

metadata servera server that provides metadata management services to one or more clientapplications. A SAS Metadata Server is an example.

middle tierin a SAS business intelligence system, the tier in which J2EE Web applications andJ2EE enterprise applications execute.

MIMESee Multipurpose Internet Mail Extensions.

MIME type filterin the Publishing Framework, a filter that specifies which file entries of a specificMIME type to include in packages that are published to a subscriber. See alsoMultipurpose Internet Mail Extensions.

Multipurpose Internet Mail Extensionsa method of registering content types and their associated actions with mechanismsfor actions such as retrieval and display. Short form: MIME. See also content type.

30 Glossary

name/value filterin the Publishing Framework, a subscription property that determines whichpackages are published to that subscriber. In order to receive a particular package, asubscriber’s name/value filter must contain the name/value pair that the publisherspecifies in the package. See also name/value pair and filter.

name/value pairin the Publishing Framework, an attribute and value that the publisher uses todescribe 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 containsproduction data. One or more site-specific name/value pairs can be assigned to anentire package or to a selected package entry. Subscribers can use name/value pairsto define name/value filters, which control the types of packages that are delivered tothem. See also filter.

named servicea SAS Foundation Service that is bound to the service registry by name. Namedservices are defined by named service bindings. Named service bindings enableapplications to locate a service based on the name that is bound to the registry. Seealso bind, named service binding, and service registry.

named service bindingthe method that is used to bind one of the SAS Foundation Services to a serviceregistry when the service has been deployed remotely. Named service bindingsenable applications to locate a service by using the name that is bound to theregistry. See also bind, named service, and service registry.

namespacea URL that identifies an entry in a WebDAV package.

naming hierarchya naming system that the Event Broker Service uses to map events to an eventconfiguration. The event names that are included in the hierarchy are separated byperiods, as in this example: <code>Animals</code>, <code>Animals.Dogs</code>,<code>Animals.Dogs.Retriever</code>. See also event and Event Broker Service.

objectin object-oriented programming, an instantiation or specific representation of a class.

object classa definition of a type of object that can be stored in an LDAP directory. Each objectclass consists of a set of attributes (for example, name and description) to which youcan assign values in order to define a specific instance of the object. The attributescan be either mandatory or optional. The complete set of object classes for a directorydefines its schema.

Object Management Groupa nonprofit industry consortium formed in April 1989 that develops standards fordistributed objects. OMG standards include the Common Object Request BrokerArchitecture (CORBA) and the Internet Inter-ORB Protocol (IIOP). Short form: OMG.

Object Request Brokerin object-oriented programming, a middle-tier component that supportscommunication between clients and servers. When a client invokes a method that issupported by an object server class, the ORB finds an instance of the object serverclass, invokes the requested method, and returns the results to the requesting client.An ORB enables clients and servers to dynamically discover each other and tocommunicate with each other across a network. Short form: ORB.

Glossary 31

object spawnera program that instantiates object servers that are using an IOM bridge connection.The object spawner listens for incoming client requests for IOM services. When thespawner receives a request from a new client, it launches an instance of an IOMserver to fulfill the request. Depending on which incoming TCP/IP port the requestwas made on, the spawner either invokes the administrator interface or processes arequest for a UUID (Universal Unique Identifier).

OMGSee Object Management Group.

ORBSee Object Request Broker.

overridein the Publishing Framework, a subscription property that is assigned to a singlechannel and that is used in place of a default property that is otherwise assigned tochannel subscriptions.

packagea container for data that has been generated or collected for delivery to consumers bythe SAS Publishing Framework. Packages can contain SAS files (SAS catalogs; SASdata 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 SASprograms), and viewer files (HTML templates that format SAS file items forviewing). Packages also contain metadata such as a description, an abstract, anduser-specified name/value pairs.

package entryin the Publishing Framework, an item within a package.

package entry type filterin the Publishing Framework, a filter that specifies which types of package entries topublish to a subscriber. See also filter.

parametera data item that is passed to a routine.

permanent packagea container for content that was produced by a SAS program or by a third-partyapplication, and that is written to a specific location. Permanent packages remain inexistence even after the stored process completes execution and the client disconnectsfrom the server. See also transient package.

permissionthe type of access that a user or group has to a resource. The permission defineswhat the user or group can do with the resource. Examples of permissions areReadMetadata and WriteMetadata.

PFDSee process flow diagram.

plug-ina 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 mustmeet design criteria specified by the developers of the application program. In SASManagement Console, a plug-in is a JAR file that is installed in the SASManagement Console directory to provide a specific administrative function. Theplug-ins enable users to customize SAS Management Console to include only thefunctions that are needed.

32 Glossary

poola group of server connections that can be shared and reused by multiple clientapplications. A client-side pool consists of one or more puddles. See also puddle.

poolingthe act or process of creating a pool. See also pool.

portala 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 theinterface to meet individual or role-based needs. See also portlet.

portleta Web component that is managed by a Web application and that is aggregated withother portlets to form a page within the application. Portlets can process requestsfrom the user and generate dynamic content.

Process Editora utility that is used for configuring process flows for the Event Broker Service. Seealso Event Broker Service and process flow.

process flowprogramming logic that is executed in response to an event message and that insome cases returns a result. See also Event Broker Service and event.

process flow diagramin SAS Foundation Services, a diagram in the Process Editor that illustrates theorder in which process nodes and message nodes are to be executed within aparticular process flow. Short form: PFD. See also Event Broker Service, processflow, process node, and message node.

process nodein a process flow diagram, a node that represents run-time processing that isperformed on messages. See also process flow diagram, process flow, and messagenode.

prompta parameter that enables a user to specify one or more values, which can be used byconsumers such as applications, stored processes, and reports.

publication channelan information repository that has been established using the SAS PublishingFramework and that can be used to publish information to users and applications.See also publish.

publishto deliver electronic information, such as SAS files (including SAS data sets, SAScatalogs, and SAS data views), other digital content, and system-generated events toone or more destinations. These destinations can include e-mail addresses, messagequeues, publication channels and subscribers, WebDAV-compliant servers, andarchive locations.

publisherany person, SAS program, or application that uses the Publishing Framework todistribute information.

Publishing Frameworka component of SAS Integration Technologies that enables both users andapplications to publish SAS files (including data sets, catalogs, and database views),other digital content, and system- generated events to a variety of destinations. The

Glossary 33

Publishing Framework also provides tools that enable both users and applications toreceive and process published information.

puddlea group of servers that are started and run using the same login credentials. Eachpuddle can also allow a group of clients to access the servers.

queueSee message queue.

queue manageran application that enables programs to send messages to and receive messages frommessage queues.

remote method invocationa Java programming feature that provides for remote communication betweenprograms 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 adifferent host. Short form: RMI. See also Java Virtual Machine.

remote service deploymenta service deployment that supports shared access to a set of SAS Foundation Servicesthat are deployed within a single Java Virtual Machine (JVM), but which areavailable to other JVM processes. Applications use the remote service deployment todeploy and access remote foundation services. See also service deployment.

repositorya location in which data, metadata, or programs are stored, organized, andmaintained, and which is accessible to users either directly or through a network.See also metadata repository, SAS Metadata Repository, and WebDAV repository.

resourceany object that is registered in a metadata repository. For example, a resource can bea server, a stored process, or a login.

result typethe kind of output that is produced by a stored process. Result types include none,streaming, permanent package, and transient package.

RMISee remote method invocation.

SAS application servera server that provides SAS services to a client. In the SAS Open MetadataArchitecture, the metadata for a SAS application server specifies one or more servercomponents that provide SAS services to a client. See also component.

SAS BI Web servicea Web service that adheres to the XML for Analysis (XMLA) specification forexecuting SAS Stored Processes.

SAS Foundation Servicesa set of core infrastructure services that programmers can use in developingdistributed applications that are integrated with the SAS platform. These servicesprovide basic underlying functions that are common to many applications. Thesefunctions include making client connections to SAS application servers, dynamicservice discovery, user authentication, profile management, session contextmanagement, metadata and content repository access, activity logging, eventmanagement, information publishing, and stored process execution. See also service.

34 Glossary

SAS loga file that contains a record of the SAS statements that you enter as well asmessages about the execution of your program.

SAS Management Consolea Java application that provides a single user interface for performing SASadministrative tasks.

SAS Metadata Repositoryone or more files that store metadata about application elements. Users connect to aSAS Metadata Server and use the SAS Open Metadata Interface to read metadatafrom or write metadata to one or more SAS Metadata Repositories. The metadatatypes in a SAS Metadata Repository are defined by the SAS Metadata Model.

SAS Metadata Servera multi-user server that enables users to read metadata from or write metadata toone or more SAS Metadata Repositories. The SAS Metadata Server uses theIntegrated Object Model (IOM), which is provided with SAS Integration Technologies,to communicate with clients and with other servers.

SAS OLAP Servera SAS server that provides access to multidimensional data. The data is queriedusing the multidimensional expressions (MDX) language.

SAS Open Metadata Architecturea general-purpose metadata management facility that provides metadata services toSAS applications. The SAS Open Metadata Architecture enables applications toexchange metadata, which makes it easier for these applications to work together.

SAS packageSee package. Short form: SPK.

SAS Stored Processa SAS program that is stored on a server and which can be executed as requested byclient applications. SAS Stored Processes can be used with either a SAS WorkspaceServer or a SAS Stored Process Server.

SAS Stored Process Servera SAS IOM server that is launched in order to fulfill client requests for SAS StoredProcesses. See also IOM server.

SAS Stored Process Web Applicationa Web application that enables you to execute stored processes and have the resultsreturned to a Web browser.

SAS Workspace Servera SAS IOM server that is launched in order to fulfill client requests for IOMworkspaces. See also IOM server and workspace.

schemaSee directory schema.

servera 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 anetwork, users might log on to a file server (to store and retrieve data files), a printserver (to use centrally located printers), or a database server (to query or updatedatabases). In a client/server implementation, a server is a program that waits forand fulfills requests from client programs for data or services. The client programsmight be running on the same computer or on other computers. See also service.

Glossary 35

serviceone or more application components that an authorized user or application can call atany time to provide results that conform to a published specification. For example,network services transmit data or provide conversion of data in a network, databaseservices provide for the storage and retrieval of data in a database, and Web servicesinteract with each other on the World Wide Web. See also SAS Foundation Services.

service configurationa set of values that can be customized for a particular service in SAS FoundationServices. By editing a service configuration, you can override the defaultconfiguration for the foundation service. See also SAS Foundation Services.

service deploymenta collection of SAS Foundation Services that specifies the data that is necessary inorder to instantiate the services, as well as dependencies upon other services.Applications query a metadata source (a SAS Metadata Server or an XML file) toobtain the service deployment configuration in order to deploy and access foundationservices. See also SAS Foundation Services.

service deployment groupa group of SAS Foundation Services within a service deployment. Service deploymentgroups are used to organize foundation services within a deployment hierarchy.Applications can use service deployment groups in order to deploy only specificgroups of foundation services. See also service deployment.

service interfacean interface that defines the services that one of the SAS Foundation Services isproviding to its users. Each of the foundation services implements one or moreservice interfaces. See also SAS Foundation Services.

service loadera utility that can be invoked by client applications that use SAS Foundation Services.The service loader enables client applications to (1) instantiate services and registerthem with a local Discovery Service or (2) locate a remote Discovery Service that hasbeen 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. Servicenames (named services) are defined by named service bindings. Applications use thenamed service binding to locate the service based on the name that is bound to theservice registry. (2) a TCP/IP port identifier. Service names are defined in the TCP/IPSERVICES file. See also bind.

service registrya searchable registry of service descriptions that is used to register named servicebindings. Applications use the service registry to locate (via named service bindings)SAS Foundation Services that have been deployed remotely. See also named serviceand named service binding.

servleta Java program that runs on a Web server. Servlets can be considered acomplementary technology to applets, which run in Web browsers. Unlike appletcode, servlet code does not have to be downloaded to a Web browser. Instead, servletssend HTML or other appropriate content back to a browser or to another type ofWeb-based client application.

servlet containeran execution environment for Java servlets that contains a Java Virtual Machine.The servlet container also provides other services for servlets and for the Web

36 Glossary

applications that those servlets are part of. For example, the servlet containerconverts HTTP requests that are sent by clients to Java objects that servlets canwork with, and it converts the output of servlets to HTTP responses. An example of apopular servlet container is the JBoss server.

session contexta context that serves as a control structure for maintaining state within a boundsession. ’State’ includes information about the latest status, condition, or content of aprocess or transaction. Session Services, User Services, and Logging Services use thesession context to facilitate resource management and to pass information amongservices. See also context and bind.

Session Serviceone of the SAS Foundation Services. This service enables applications to (1) create asession context, (2) bind objects to a session context, (3) use the session context as acontainer for passing multiple contexts or for passing other services (such as UserServices and Logging Services), and (4) notify bound objects when they are removedfrom the session context or when the session context is destroyed, so that objects canperform any necessary cleanup. See also SAS Foundation Services, session context,and bind.

Simple Object Access Protocola standard, Web-based protocol that enables applications written in variousprogramming languages to communicate. Short form: SOAP.

single sign-onan authentication model that enables users to access a variety of computingresources without being repeatedly prompted for their user IDs and passwords. Forexample, single sign-on can enable a user to access SAS servers that run on differentplatforms without interactively providing the user’s ID and password for eachplatform. Single sign-on can also enable someone who is using one application tolaunch other applications based on the authentication that was performed when theuser initially logged on.

smart objectan object that acts as a wrapper for metadata entries in order to hide details thatpertain to a specific type of metadata repository. The Information Service uses smartobjects to specify implementation details for specific types of repositories. See alsoInformation Service.

SOAPSee Simple Object Access Protocol.

source code repositorythe location on the application server that contains stored process source code.

source filethe SAS program that contains the stored process source code.

SPKSee SAS package.

stored processa SAS program that is stored on a server and which can be executed as requested byclient applications. There are two types of stored processes: IOM Direct InterfaceStored Processes and SAS Stored Processes.

Stored Process Serviceone of the SAS Foundation Services. This Java-based interface enables applicationsto synchronously or asynchronously execute a stored process. Execution can include

Glossary 37

accessing SAS data sources or external files and creating new data sets, files, orother types of output that are supported by SAS. Clients of the service can pass inputparameters and data streams to an executing stored process and can receive outputstreams or result packages from the stored process. See also SAS FoundationServices.

streaming resulta type of output that is generated by a stored process. In a streaming result, thecontent that the stored process generates is delivered to the client through an outputstream. The output stream is generally accessible to the stored process as the_WEBOUT fileref. See also result type.

Strutsa public-domain framework for building Web applications. The Information DeliveryPortal and the Web Infrastructure Platform (provided with SAS IntegrationTechnologies) use this framework. Struts is based on standard technologies such asJava servlets, JavaBeans, resource bundles, and Extensible Markup Language(XML). It supports the Model 2 variation of the Model-View-Controller (MVC) designparadigm. Struts is part of the Apache Jakarta Project, which is sponsored by theApache Software Foundation.

stuba Java class that acts as an interface for a remote software object. Stubs areinstantiated on the client. The client passes method calls to the stubs, and the stubsthen repackage the method calls for delivery through an Object Request Broker(ORB) to remote software objects. In many distributed object systems, stubs arereferred to as proxies.

subscribeto sign up to receive electronic content that is published to a SAS publication channel.

subscribera recipient of information that is published to a SAS publication channel.

subscriber profilea set of personal preferences for subscribing to SAS publication channels. Asubscriber profile includes the method by which you want published information tobe delivered and filtering criteria (in the form of name/value pairs) to limit the typesof information that you receive. You can create multiple subscriber profiles if youwant to subscribe to channels in different ways.

subscriptionthe association of a subscriber with a group or a channel.

threada single path of execution of a process in a single CPU, or a basic unit of programexecution in a thread-enabled operating system.

transient packagea container for content that was produced by a SAS program or by a third-partyapplication for immediate use, and that is not saved. After the client programdisconnects from the server, the transient package disappears. See also permanentpackage.

transport(1) in SAS Foundation Services, a communication protocol through which the EventBroker Service can listen for, receive, and respond to external events. Each transportthat 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 ’deliverytransport.’ See also Event Broker Service and delivery transport.

38 Glossary

Unicode Transformation Format 8a method for converting 16-bit Unicode characters to 8-bit characters. This formatsupports all of the world’s languages, including those that use non-Latin 1characters. Short form: UTF-8.

Uniform Resource Identifiera string that identifies resources such as files, images, and services on the World WideWeb. A URL is a type of URI. Short form: URI. See also Uniform Resource Locator.

Uniform Resource Locatora character string that is used by a Web browser or other software application toaccess or identify a resource on the Internet or on an intranet. The resource could bea Web page, an electronic image file, an audio file, a JavaServer page, or any othertype of electronic object. The full form of a URL specifies which communicationsprotocol to use for accessing the resource, as well as the directory path and filenameof the resource. Short form: URL.

Universal Unique Identifiera 128-bit identifier that is comprised of date/time information and a host’s IEEE nodeaddress. The 128 bits can represent 1x10**39 unique identifiers. UUIDs are alsoreferred to as Global Unique Identifiers (GUIDs). Short form: UUID.

URISee Uniform Resource Identifier. See also Uniform Resource Locator.

URLSee Uniform Resource Locator.

usera person who is registered in a SAS metadata environment.

user contexta context that contains information about the user who is associated with an activesession. The user context contains information such as the user’s identity, profile,and active repository connections. See also context.

User Serviceone of the SAS Foundation Services. This service enables applications to (1) create,locate, maintain, and aggregate information about users of the SAS FoundationServices, (2) store and retrieve user context objects for sharing between applications,(3) manage and access user profiles, and (4) access group profiles. See also SASFoundation Services.

UTF-8See Unicode Transformation Format 8.

UUIDSee Universal Unique Identifier.

viewerin the Publishing Framework, a custom-written template that contains HTML tagsfor formatting package content for view-only delivery transports such as e-mail.

Web Distributed Authoring and Versioningan emerging industry standard, based on extensions to HTTP 1.1, that enables usersto collaborate in the development of files and collections of files on remote Webservers. Short form: WebDAV. See also delivery transport.

Web servera server machine and software that enable organizations to share informationthrough intranets and through the Internet.

Glossary 39

Web Service Description Language filea file that is obtained from a Web service. The WSDL describes the methods that areavailable to the client application, the endpoint (where to call the Web service), andthe format of the XML that is required in order to call the Web service. Short form:WSDL file.

WebDAVSee Web Distributed Authoring and Versioning.

WebDAV content portleta portlet that displays the contents of an HTML fragment that is stored in theportal’s WebDAV repository.

WebDAV repositorya collection of files that are stored on a Web server so that authorized users can readand edit them. See also Web Distributed Authoring and Versioning.

wizardan interactive utility program that consists of a series of dialog boxes, windows, orpages. Users supply information in each dialog box, window, or page, and the wizarduses that information to perform a task.

workspacein the IOM object hierarchy for a SAS Workspace Server, an object that represents asingle session in SAS. See also Integrated Object Model.

WSDL fileSee Web Service Description Language file.

XMLSee Extensible Markup Language.

XML for Analysisa standard specification developed by several companies for use as a Web serviceinterface to access online analytical processing (OLAP) functions and data-miningfunctions. Short form: XMLA.

XMLASee XML for Analysis.

41

Index

Aaccessibility features 1application messaging 16

Common Messaging Interface 17MSMQ functional interface 17WebSphere MQ functional interface 17

Application Messaging interface 2applications, developing with IOM 10asynchronous message queuing 3

Cchannel definition 15client development 3clients, connecting to IOM servers 8Common Messaging Interface 17configuration of IOM servers 6

DDirectory Services 19Directory Services interface 2documentation

IOM servers 6SAS Web Infrastructure Platform 20

Eevent publishing 16

Ffile management 3

Iindustry standards 3Integrated Object Model (IOM) 1

developing applications 10IOM servers 1, 5

configuring and using 6connecting clients to 8documentation for 6types of 6

JJava clients, connecting to IOM servers 10

Mmessaging

See application messagingMSMQ functional interface 17

Ppackage publishing 15

package retrieval and viewing 16Publishing Framework 2, 14

channel definition 15event publishing 16

package publishing 15package retrieval and viewing 16subscription management 15

SSAS BI Web Services 2, 18SAS BI Web Services for Java 19SAS Common Messaging Interface 17SAS Content Server 20

SAS Foundation Services 2, 13SAS Integration Technologies 1

accessibility features 1components of 1

support for industry standards 3support for SAS Open Metadata Architecture 2

SAS Logon Manager 20SAS Metadata Server 6

SAS OLAP Server 6SAS Open Metadata Architecture 2SAS Preferences Manager 20SAS Shared Web Assets 19

SAS Stored Process Server 6SAS Stored Process Web Application 20SAS Stored Processes 2SAS Web Administration Console 20

SAS Web Infrastructure Platform 2, 19documentation 20

SAS Web Infrastructure Platform Services 19SAS Workspace Server 6

interfaces of 11stored processes 17subscription management 15

42 Index

WWeb services development 3WebSphere MQ functional interface 17

Windows clients, connecting to IOM servers 9workspace object hierarchy 11

Your Turn

We welcome your feedback.

• If you have comments about this book, please send them to [email protected]. Include the full title and page numbers (if applicable).

• If you have comments about the software, please send them to [email protected].

SAS® Publishing Delivers!Whether you are new to the work force or an experienced professional, you need to distinguish yourself in this rapidly changing and competitive job market. SAS® Publishing provides you with a wide range of resources to help you set yourself apart. Visit us online at support.sas.com/bookstore.

SAS® Press Need to learn the basics? Struggling with a programming problem? You’ll find the expert answers that you need in example-rich books from SAS Press. Written by experienced SAS professionals from around the world, SAS Press books deliver real-world insights on a broad range of topics for all skill levels.

s u p p o r t . s a s . c o m / s a s p r e s sSAS® Documentation To successfully implement applications using SAS software, companies in every industry and on every continent all turn to the one source for accurate, timely, and reliable information: SAS documentation. We currently produce the following types of reference documentation to improve your work experience:

• Onlinehelpthatisbuiltintothesoftware.• Tutorialsthatareintegratedintotheproduct.• ReferencedocumentationdeliveredinHTMLandPDF– free on the Web. • Hard-copybooks.

s u p p o r t . s a s . c o m / p u b l i s h i n gSAS® Publishing News Subscribe to SAS Publishing News to receive up-to-date information about all new SAS titles, author podcasts, and new Web site features via e-mail. Complete instructions on how to subscribe, as well as access to past issues, are available at our Web site.

s u p p o r t . s a s . c o m / s p n

SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. ® indicates USA registration. Otherbrandandproductnamesaretrademarksoftheirrespectivecompanies.©2009SASInstituteInc.Allrightsreserved.518177_1US.0109

http://support.sas.com/saspress

http://support.sas.com/publishing

http://support.sas.com/LE

SAS 9.2 Integration Technologies: Overviewsupport.sas.com/documentation/cdl/en/itechov/60309/... ·...

Documents

Transcript of SAS 9.2 Integration Technologies: Overviewsupport.sas.com/documentation/cdl/en/itechov/60309/... ·...