SAS 9.1.3 Integration Technologies » Server Administrator's Guide

Setting up a COM/DCOM Connection
Server and Client Requirements
Summary of Setup Steps
Planning Your Server Configuration Metadata
Standard Server Metadata
Creating Metadata Using SAS Management Console
Defining Servers
Modifying Servers
Custom Workspace Servers
OLAP Servers
Enabling DCOM on the Server and the Client
Configuring SAS for DCOM
Setting SAS Permissions on the Server
Default on Windows NT/2000
Per Application on Windows NT/2000
Default on Windows XP  Server 2003
Per Application on Windows XP / Server 2003
Configuring DCOM on Windows XP SP2 / Server 2003 SP1
Configuring COM/DCOM for Active Server Page Access
Accessing a Local COM IOM Server from an Active Server Page
Accessing a Remote DCOM IOM Server from an Active Server Page
Administering the Server:
Creating a Metadata Configuration File in SAS
Using ITConfig
Troubleshooting
Reference Materials
AppIDs for Configuring DCOM
Object Server Parameters
Fields for the Server Definition
COM/DCOM

Configuring COM/DCOM for Active Server Page Access

Note: You can also configure your Active Server Page (ASP) application to access SAS using the IOM Bridge for COM. You might want to use IOM Bridge for COM if either of the following are true:

  • SAS is running on z/OS or a UNIX machine
  • you want to share a configured SAS server with Java applications.
If you are using the IOM Bridge for COM, the configuration in this section is not required. See Choosing a Server Configuration for details.

COM/DCOM Configuration

To configure a Windows Active Server Page (ASP) client running in Microsoft Internet Information Services (IIS) for access to a Windows server using DCOM, you must perform two different types of configuration:

  1. A basic configuration that is similar to a standard Windows client that accesses a Windows server using DCOM.

    To perform this basic configuration, follow the instructions in Enabling DCOM on the Server and the Client.

  2. Additional configuration steps that will enable a Web client to access an IOM server. There are two ways that you can access a Windows Server using COM/DCOM:

Permissions

Use dcomcnfg to configure the SAS.Workspace (SAS Version 9.1) application. To configure the DCOM or COM when using ASP, you must change access and launch permissions for the SAS.Workspace (SAS Version 9.1) application. Therefore, you should also familiarize yourself with Setting Permissions per Application on Windows NT/2000 or Setting Permissions per Application on Windows XP.

If you are experienced with using IIS and DCOM and only need to know the permissions required for your setup, see the following table for details about these permissions.

IOM Server Web Server DCOM Access Permission
(on IOM Server)		 DCOM Launch Permission
(on IOM Server)		 Other Notes
Local COM IIS 4
All Authentication Methods
  • System
  • System
  
IIS 5 using
Anonymous Access
  • IUSR_<machine_name>
  • IWAM_<machine_name>
  • IUSR_<machine_name>
  • IWAM_<machine_name>
 The COM+ application can be configured so it is launched as a different user; however, this is not necessary. Refer to Configure your IIS Application to use High (isolated) Application Protection for details.
IIS 5 using
Basic Authentication and Integrated Windows Authentication
  • IWAM_<machine_name>
  • Any valid NT user account that will be accessing the ASP
  • IWAM_<machine_name>
Remote DCOM IIS 4
All Authentication Methods
  • System
  • Network
  • System
  • Network
 If you are setting up the remote DCOM IOM server on a Windows 2000 or XP computer, you must configure the DCOM server to run as a different user than the launching user.
IIS 5
All Authentication Methods
  • User account launching IIS COM+ application
  • Network
  • User account launching IIS COM+ application
 The COM+ application must be configured so it is launched as a user that exists on both the Web server and DCOM IOM server. Refer to Configure your IIS Application to use High (isolated) Application Protection for details.