Client Installation

Installation Methods

The SAS Integration Technologies client for the Windows operating environment can be installed in multiple ways:
  • Install Base SAS for Windows. The SAS Integration Technologies client is installed with Base SAS software.
  • Install an enterprise client (such as SAS Enterprise Guide). The setup program for the enterprise client component installs the SAS Integration Technologies client.
  • Install 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.
If you have not previously installed SAS 8.2 or earlier, the default installation directory is C:\Program Files\SAS\Shared Files.
If you have previously installed SAS 8.2 or earlier, the default installation directory is C:\Program Files\SAS Institute\Shared Files.
Note: If you are using the SAS Integration Technologies client with 64-bit SAS, then additional 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:
  • the Integration Technologies Configuration Utility (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 (StoredProcessService.dll, help file in StoredProcessService.chm)
  • SAS Logging Service (LoggingService.dll)
  • SAS Metadata Service (SAS.Metadata.dll)
  • SAS IOM Data Provider
  • SAS
  • SAS type libraries (sas.tlb with Help in SAS.chm, arbor.tlb, asp.tlb, gms.tlb, IMLPlusServer.tlb, LoggingService.tlb, mdx.tlb, mqx.tlb, ObjectSpawner.tlb, olap.tlb, omi.tlb, sascache.tlb, SASIOMCommon.tlb, sastableserver.tlb, stp.tlb, tst.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 that was developed by the Apache Software Foundation. For more details, see the Apache Web site at www.apache.org.

Encryption Support

Windows clients (and Windows servers) that use strong encryption need additional support, which is supplied through SAS/SECURE software. SAS/SECURE software enables SAS Integration Technologies to use encryption algorithms that are available through the Microsoft Cryptographic Application Programming Interface (CryptoAPI).
If you have 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.
The SAS/SECURE client 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 at www.sas.com/products/secure on the SAS Products and Solutions Web site.