Contents Administering SAS Servers Previous Next

* Server Requirements
* Summary of Setup Steps
* Metadata Overview

* Creating the Metadata
** Using the IT Administrator
** Wizard
** Using IT Administrator
** Using a Configuration File

* Enabling DCOM on the
* Server and Client

* Configuring COM/DCOM
* for Active Server Page Access 

* Setting SAS Launch Policies
* on the Server
** Global
** Per Application

 Administering the Server:
* Using the Configuration
* Application *
* Testing and Troubleshooting 
* Tips

 Reference Materials:
Arrow bullet Attributes for
* sasLogicalNameInfo
Arrow bullet Attributes for sasServer
      

Setting Up a COM/DCOM Server: Introduction

SAS can be configured to enable client access through Component Object Model (COM) interfaces. A COM connection can be established either locally (on the same machine) or remotely (on a different machine). For remote connections, the Distributed Component Object Model (DCOM) interface is used.

Since COM launches the SAS object server, spawners are not used in the COM/DCOM server environment. However, you can (and should) use the Workspace Manager to obtain a DCOM server. The server definitions can be administered through LDAP.

DCOM must be enabled on both the client machine and on the machine where the IOM server runs. The server machine requires additional configuration for DCOM object access and launch permissions.

When to Use a COM/DCOM Server Configuration

You can configure an object server as a COM/DCOM server if:

  • The object server will be installed on a Windows machine and will be accessed by Windows client applications running on remote machines. In this situation, the connection uses DCOM.

  • The object server will be installed on a Windows machine and will be accessed by Windows client applications running on the same machine. In this situation, the connection uses COM.

If you use a Java client, you must use an IOM Bridge server configuration instead.