SAS^® Integration Technologies

Features

Integration of asynchronous business processes

• APIs to use the market-leading message-queuing products: Microsoft’s MSMQ, IBM’s WebSphere MQ and Tibco’s Rendevous.
• Integrate asynchronous processes with the SAS platform via the SAS call routines.
• Publish information to message queues using the SAS Publishing Framework.
  

Interoperability with Enterprise Directory Servers

• Support for industry-standard Lightweight Directory Access Protocol (LDAP)-compliant directories such as Microsoft Active Directory, Sun ONE, IBM SecureWay and Netscape Directory Server.
• SAS call routines to read and write metadata in/from an Enterprise Directory server.
• SAS Information Service, a Java API, allows easy access to metadata stored in the LDAP repositories from a Java program.
  

SAS Publishing Framework for targeted information delivery

• Supports publishing information of any form, including data sets, OLAP data, HTML reports, any mime-type (PDF, XLS, Word documents, etc.).
• SAS call routine for publishing that information.
• SAS Publishing Service, a Java API, supports publishing of information from Java programs.
• Publishing to different targets (e-mail, storage, message queue, WebDAV repositories). Interested people can subscribe to information channels. Published information is delivered automatically to subscribers.
  

Service-oriented architecture via Web services

• SAS Stored Processes can be called via Web services.
• Any client can make use of SAS capabilities via SAS BI Web services, a middleware broker component available for J2EE and .Net frameworks.
  

A comprehensive set of infrastructure-oriented Foundation Services

• SAS Connection Service is a Java API that accesses SAS servers.
• SAS Information Service is a Java API that accesses the SAS Metadata Server and performs read/write tasks on metadata, such as modifying the role of a user.
• SAS Publishing Service is a Java API that publishes information to e-mail, channels and the Web via WebDAV, etc.
• SAS Stored Process Service is a Java API that runs SAS code and returns results.
• Alert and Event Service allows dynamic, event-driven runstreams and alerting.
• Services to manage users, security, sessions and logging.
• Developers can use the services API to easily extend and add additional services.
  

SAS Stored Process Server for executing SAS Stored Processes

• Centrally manage stored processes in the SAS Metadata Repository using SAS Management Console.
• Define input and output parameters.
• Name/value pairs.
• Data streams (XML streams, data sets, HTML, PDF, etc.).
• Result packages containing multiple entries, including text, images, data sets, etc.
• Exploit stored resources from any client (Web clients, Java applications or Windows applications) via the Stored Process Service API.
• Surfaced via any of the SAS BI tools, such as SAS Information Map Studio or SAS Add-In for Microsoft Office.
  

Powerful scalability options

• Load balancing: allows distributing workload across multiple processes, processors and machines.
• Pooling: allows clients to share “pooled” connections instead of restarting SAS with every single request.
• Fault tolerance: during server downtimes the workload can be redirected to another one on the chain.
  

SAS Web Infrastructure Kit for building SAS Java Web applications

• A framework to build SAS Java Web applications that support single sign-on and role-based business views.
• Leverages the SAS security model and metadata.
• Ability to execute and display content such as stored processes, reports, links and Web applications.
  

Choice of programming languages for developers to leverage SAS Analytics remotely

• Deliver the entire capability of the SAS platform to virtually any client across an enterprise.
• Utilizes open communication protocols for both Windows clients and Java clients to give developers the ability to use SAS analytical power whether they’re programming in Java, C++, C#, VisualBasic.Net, Delphi or other languages.
• SAS jobs and runstreams can easily be called and executed remotely without developers having to know the SAS programming language.