SAS 9.1.3 Integration Technologies » Administrator's Guide (LDAP Version)


Setting up a COM/DCOM Server
Server and Client Requirements
Summary of Setup Steps
Metadata Overview
Creating the Metadata for a COM/DCOM Server
Using the IT Administrator Wizard
Using IT Administrator
Using a Configuration File
Configuration File Example: Minimal Configuration
Configuration File Example: Using Logical Names
Enabling DCOM on the Server and the Client
Configuring SAS for DCOM
Setting SAS Permissions on the Server
Global on Windows NT/2000
Per Application on Windows NT/2000
Global 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 Server from an Active Server Page
Accessing a DCOM Server from an Active Server Page
Administering the Server:
Using the IT Configuration Application
Troubleshooting
Reference Materials
AppIDs for Configuring DCOM
Object Server Parameters
Attributes for Servers
Attributes for Logical Names
COM/DCOM

Metadata Overview (COM/DCOM)

The metadata that supports Integration Technologies consists of objects, each defined by a collection of attributes that define the object. If you require metadata, the metadata for a COM/DCOM server configuration must include a sasServer object, which contains startup and connection information for a particular instance of a SAS object server.

For each instance of an object server, the following information is defined in the metadata:

  • Server name
  • Machine name
  • Logical name
  • Connection information
  • Encryption and pooling information, if required.

For detailed information about the attributes included in the metadata for a server, see the sasServer Attributes List.

The sasLogicalNameInfo object is created automatically if you use IT Administrator to assign a logical name to a server. Logical names are used to create resource groupings.