Overview of the SAS Integration Technologies: Developer's Guide

This Developer's Guide provides guidance and reference materials for performing the various types of development tasks that might be required for an Integration Technologies implementation, including:

• using the Stored Processes interface to enable client applications to execute SAS programs that are stored centrally on a server. Instructions are provided for the following tasks:

  • creating a SAS program that can execute as a stored process

  • implementing a repository for stored processes

  • creating a client application that invokes a stored process and which processes the results of a stored process

  • using the Publishing Framework to publish the results of a stored process

• using SAS BI Web Services to enable client applications to obtain metadata about and execute SAS Stored Processes using the XML for Analysis (XMLA) Version 1.1 interface.

• using the Publishing Framework to implement proactive delivery of information to users throughout the enterprise. Instructions and reference documentation are provided for the following tasks:

  • using SAS CALL routines and third-party programs to publish and retrieve packages of digital content by way of archive locations, channels, e-mail, message queues, and WebDAV-compliant servers

  • using SAS CALL routines to publish electronic events

  • creating viewer templates to format package content for display

  • using the SAS Publisher, SAS Package Reader, and SAS Package Retriever applications to publish and retrieve packages

  • using the SAS Subscription Manager to manage users' subscriptions to publication channels

    Note: Subscription Manager will not be supported in future releases of SAS Integration Technologies. The Subscription Manager functionality will be delivered via a new interface that will continue to allow users to manage their own channel subscriptions.

• using the CALL routines in the Application Messaging Interface to incorporate messaging services into your SAS programs. Instructions and reference documentation are provided for the following interfaces:

  • IBM WebSphere MQ Interface

  • Microsoft Message Queuing Services (MSMQ) Interface

  • Common Messaging Interface, which supports TIBCO TIB/Rendezvous as well as WebSphere MQ and MSMQ.

• using the IOM Java client interface to write applets, stand-alone applications, servlets, and Enterprise JavaBeans that interact with IOM servers. This interface supports industry standards such as CORBA and Java Database Connectivity (JDBC). Instructions and reference documentation are provided for the following tasks:

  • installing SAS Java client components

  • using the Connection Factory to connect a Java client to an IOM server

  • using Java CORBA stubs for IOM objects and JDBC connection objects to exploit SAS analytical and reporting functions in the IOM server

  • returning a connection to the Connection Factory

  • encrypting messages that are exchanged with IOM servers

  Instructions are also provided for using the Workspace Factory to access an IOM server.

• using the IOM Windows client to write Microsoft Windows applications that interact with IOM servers. The Microsoft Component Object Model (COM), on which the Windows client interface is based, is built into the Windows operating system and into all of the leading programming language products. Instructions and reference documentation are provided for the following tasks:

  • installing SAS Windows client components

  • implementing security through the use of server user IDs, client user IDs, and encryption

  • developing client applications in the Visual Basic, C++, and VBScript environments

  • using the Object Manager or Workspace Manager to access an IOM server

  • using the SAS IOM Data Provider to access SAS data sets on IOM servers in conformance with Microsoft's OLE DB specification

• using the Directory Services to incorporate LDAP directory services functions into your SAS programs. Instructions and reference documentation are provided for the following tasks:

  • using LDAP CALL routines to add, delete, modify, and search entries on an LDAP server

  • using the LDAPSERVICES class of the SAS Component Language (SCL) to add, delete, modify, and search entries on an LDAP server

For high level overviews of the Integration Technologies features, refer to the SAS Integration Technologies Technical Overview. For guidance in performing the system administration tasks associated with Integration Technologies, refer to the SAS Integration Technologies: Administrator's Guide, the SAS Integration Technologies: Server Administrator's Guide or the SAS Integration Technologies: Administrator's Guide (LDAP version).