SAS 9.1.3 Integration Technologies » Developer's Guide

Developing Windows Clients
Client Requirements
Client Installation
Selecting a Windows Programming Language
Programming with Visual Basic
Programming in the .NET Environment
Using VBScript
Programming with Visual C++
Using the Object Manager
Creating an Object
Object Manager Interfaces
Using a Metadata Server with the Object Manager
Metadata Configuration Files
Error Reporting
Code Samples
Using Connection Pooling
Choosing Integration Technologies or COM+ Pooling
Using Integration Technologies Pooling
Using Com+ Pooling
Pooling Samples
Using the IOM Data Provider
Using the Workspace Manager
Class Documentation
Windows Clients

Client Installation

The SAS Integration Technologies client for the Windows operating environment can be installed in multiple ways:

  • Installing Base SAS for Windows

    On a Windows platform, the SAS Integration Technologies client is installed with Base SAS software.

  • Installing an enterprise client (such as SAS Enterprise Guide)

    The setup program for the enterprise client component will install the SAS Integration Technologies client.

  • Installing the SAS Integration Technologies client by itself

    The SAS Integration Technologies client is packaged into a single executable file that can be copied to Windows machines for easy installation of the SAS Integration Technologies client.

The default installation directory is as follows:

  • C:\Program Files\SAS Institute\Shared Files\ (if you have previously installed SAS 8.2 or earlier)
  • C:\Program Files\SAS\Shared Files\ (if you have NOT previously installed SAS 8.2 or earlier)

Note: If you are using the SAS Integration Technologies client with 64-bit SAS, extra setup steps are required for IOM COM servers on 64-bit Windows. For details, see the SAS installation documentation.

Components of the SAS Integration Technologies Client

Regardless of which method is used to install the SAS Integration Technologies client, the core function is installed via the inttech.exe file. When this file executes, it unbundles and installs the following components:

  • An executable to test IOM connections and edit the parameters that client applications use to connect to a metadata server (itconfig.exe)
  • SAS Package Reader (SASspk.dll, with Help in sasspk.chm)
  • IOM Bridge for COM (SASComb.dll)
  • Object Manager (SASOMan.dll, help file in sasoman.chm)
  • Workspace Manager (SASWMan.dll, help file in saswman.chm)
  • SAS Stored Process Service (sassps.dll, help file in sassps.chm)
  • SAS Metadata Service (SAS.Metadata.dll)
       Note: Using this component directly is experimental for 9.1.
  • SAS IOM Data Provider (sasaorio.dll)
  • SAS type libraries (sas.tlb with Help in SAS.chm, asp.tlb, gms.tlb, iml.tlb, mqx.tlb, olap.tlb)
  • An executable to register type libraries (RegTypeLib.exe)
  • Scripto (Scripto.dll)
  • The Encryption Algorithm Manager (tcpdeam.dll) and the SAS Proprietary Encryption Algorithm (tcpdencr.dll), which are used by the IOM spawner and the IOM Bridge for COM components for encrypting the communication across the network
  • The Xerces library from Apache Software Foundation

Note: The SAS Integration Technologies Windows client includes software developed by the Apache Software Foundation. For more details, see the Apache Web site at

Encryption Support

Windows clients (and Windows servers) that need to use strong encryption need additional support that is supplied through SAS/SECURE software. SAS/SECURE software supplies the support necessary to enable SAS Integration Technologies to use encryption algorithms that are available through the Microsoft Cryptographic Application Program Interface (CryptoAPI).

If you have also licensed SAS/SECURE software, you should install the SAS/SECURE client for Windows. You can install the SAS/SECURE client from the SAS Installation Kit.

When executed on the client, this program installs the tcpdcapi.dll file that is necessary for the IOM Bridge for COM to use the CryptoAPI algorithms to communicate with the IOM server. The file is installed to the shared file area on the client.

For more information, see the online product overview for SAS/SECURE Software on the SAS Products and Solutions Web site.